Loading system evidence
Loading system evidence
Learn ROS 2 fundamentals by diagnosing and repairing realistic robot systems.
Preview first lessonOutcome
Trace failures across processes, names, topics, QoS, configuration, time, and callback execution without guessing.
Build
A verified warehouse incident report with a repaired ROS graph and reproducible evidence bundle.
Sample incident
Determine why `/scan_filter` is absent without reinstalling or rebuilding the workspace.
Full syllabus
Bound the failing system, separate observations from assumptions, and choose the smallest useful diagnostic command.
Learn the concept, then prove it in two labs:Trace fully qualified names through launch scopes, remaps, and component containers.
Learn the concept, then prove it in two labs:Separate discovery, publication, transport, and callback processing using rate and type evidence.
Learn the concept, then prove it in two labs:Reason about reliability, durability, history, depth, and rate as an endpoint contract.
Learn the concept, then prove it in two labs:Trace configuration ownership through YAML roots, namespaces, launch substitutions, and override order.
Learn the concept, then prove it in two labs:Relate message stamps, simulation clocks, transform publication, and buffer windows.
Learn the concept, then prove it in two labs:Inspect callback queues, blocking work, callback groups, and executor thread availability.
Learn the concept, then prove it in two labs:Capture reproducible evidence, align clocks, and reconstruct an incident timeline from multiple sources.
Learn the concept, then prove it in two labs: