Documentation
Read the robot, not the tutorial.
Botopsy Lab teaches robotics by breaking real systems. These docs are the reference behind that: the method the labs run on, a debugging reference for the ROS 2 subsystems that fail most, and a guide to authoring your own case.
Where to start
If you have never used the platform, read the failure-first method first. It is the one page that explains why every lab hands you something already broken instead of a blank file. After that, the reference pages stand alone. Jump to whichever subsystem is currently ruining your afternoon.
Start
ROS 2 debugging reference
Frames & tf2
The transform tree, static vs dynamic frames, the most common tf2 failures, and the commands that expose them.
QoS & DDS
Why a publisher and subscriber that look identical never talk: reliability, durability, history, and QoS incompatibility.
Lifecycle nodes
Managed-node states, transitions, and the silent failures that come from a node stuck in unconfigured or inactive.
Nav2 navigation
The Nav2 stack as a set of failure points: costmaps, the behavior tree, planners vs controllers, and why a robot spins in place.
Fault-class glossary
A quick index of the recurring robotics fault classes the labs are built around, each with a one-line tell and where to look.
Build your own
These docs describe a live product
Everything here maps onto labs you can open right now. When a page names a fault, there is almost always a case in the catalogue where you fix exactly that fault in a real container. Browse the learning paths