In productionProadvancedCAN error recovery
The interface repeatedly enters bus-off
Stop the recovery loop and preserve the evidence that identifies the bad transmitter.
Pairs with SocketCAN and bus diagnostics in Hardware Integration & CANopen. Read the concept first, then diagnose it here.
Unlock this lab with ProOperator report
`can0` recovers every second, then returns to bus-off under command traffic.
Ubuntu 24.04, ROS 2 Jazzy, SocketCAN vcan, CANopen drive simulator, ros2_control
System boundary
Trace only the relevant path.
faulty transmitter timingTX error counterbus-off recovery
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.
Verification
Your repair must pass more than the visible symptom.
- No new bus-off events
- Command frames receive acknowledgements
- Hidden regression behavior
- Root cause explanation