Repository navigation
Home
Eric Busboom edited this page Aug 31, 2026
·
6 revisions
Rebuilt MCP server and gRPC daemon for AprilTag/ArUco perception on robotics playfields — one daemon owns the cameras and all vision; agents and robot control loops read tag positions, orientation, velocity, and homography through thin clients.
- Daemon Wire Protocol — The gRPC control service and length-prefixed protobuf stream sockets the aprilcam v2 daemon exposes — the wire-level contract beneath the Python client.
- Operating the Daemon — Install, run, configure, and troubleshoot the AprilCam daemon — the single process that owns every camera and does all vision.
- AprilCam v2 Docs — Navigation map for the AprilCam v2 subsystem — daemon, MCP server, robot client library, and the wire protocol.
- Tag Detection Under Variable Lighting — Why tags drop out under glare and low contrast, what the v2 pipeline does about it, and how to tune exposure for your ambient light.
- Using the MCP Server — How an AI agent drives AprilCam over the Model Context Protocol — running the server, the golden path, the full tool catalog, and error behavior.
- Overview — What AprilCam v2 is, how the daemon / MCP server / client library / viewer fit together, the install tiers, and where to start.
- Robot Direct API — The Python client library for robot control loops — discover and connect to the daemon, read tag positions at loop rate, subscribe to streams, and draw shared annotations.