Docs menu
Troubleshooting a session
The faults members hit most often in a session on the car, with the cause and the fix for each.
| Symptom | Cause | Fix |
|---|---|---|
command not found for ros2 or colcon |
The terminal was not sourced | Run both source lines from Build and test |
Permission denied on /dev/sensors/vesc or /dev/input/js0 |
Group membership applies only to sessions started after it was added | Open a new terminal, or run newgrp dialout && newgrp input |
Commands published to /drive do nothing |
teleop_launch.py is running in another terminal, and the mux forwards its higher-priority command |
Stop teleop; an autonomy session never launches it |
buttons[4] in /joy never reads 1 |
The F710 is in DirectInput mode | Set the switch on the back of the controller to XInput |
| The build is killed partway through | The Jetson ran out of its 8 GB of RAM | Rebuild with --parallel-workers 1 |
| Far fewer tests ran than exist | ROS was not sourced, so files importing rclpy did not collect |
Source ROS and rerun |
The workspace docs keep a longer troubleshooting reference, ordered by symptom. Check it before changing code to work around a fault.