Pricing
00
In productionProbeginnerStartup readiness

The robot fails only at boot

Make drive startup wait for a usable CAN interface without a fixed sleep.

Pairs with systemd and startup order in Production ROS Operations. Read the concept first, then diagnose it here.

Unlock this lab with Pro

Operator report

Manual service restart works, but boot startup reports `can0 not found`.

Ubuntu 24.04, ROS 2 Jazzy, Cyclone DDS, containers, systemd, OpenTelemetry fleet sandbox

01

System boundary

Trace only the relevant path.

3 nodes
  1. 01systemd network target→
  2. 02can0 readiness→
  3. 03drive serviceOUT
02

How this lab works

You diagnose it. No command list.

Open the repair workspace and gather your own evidence in a real terminal. No diagnostic commands are handed to you - finding the fault is the exercise. Stuck? Progressive hints unlock inside the workspace.

03

Verification

Pass more than the visible symptom.

4 checks
  • Cold boot starts drive
  • Missing can0 fails clearly
  • Hidden regression behavior
  • Root cause explanation