Troubleshooting
Robotics debugging is part software, part hardware, and part workflow. Most beginner issues come from connection problems, workspace setup, wrong commands, or another process already running.
Cannot SSH into the robot+
Likely cause
The laptop is not on the correct network, the robot is not fully powered on, or the hostname is different.
Fix
Check power, network connection, and the correct SSH command. Try using the robot's IP address if the hostname does not resolve.
VS Code cannot connect+
Likely cause
The SSH extension is not configured correctly or the robot is unreachable.
Fix
Test SSH in a normal terminal first. If terminal SSH works, reopen VS Code and reconnect through the remote SSH menu.
Demo command not found+
Likely cause
The workspace was not sourced or the package name is wrong.
Fix
Run
source install/setup.bash from the workspace, then try the command again.Robot does not move+
Likely cause
The motion node is not running, power is not enabled, or the behavior is blocked by a safety condition or pending queue approval.
Fix
Check terminal output, confirm the robot is powered, verify the motion system is active, and confirm your submission was actually approved — see Validation & Queue.
Camera not detected+
Likely cause
The RealSense camera is not connected, the camera process is not running, or another process is already using the camera.
Fix
Check the camera connection and restart the camera-related node or demo.
Motion stopped halfway+
Likely cause
A safety stop, software error, motion lock, or timeout interrupted the behavior.
Fix
Read the terminal output before restarting. Do not immediately rerun the same script without checking why it stopped.
Permission denied+
Likely cause
The file is not executable or the user does not have permission for that command.
Fix
Check file permissions and confirm the command is being run from the correct environment.
Wrong file edited+
Likely cause
The student edited a copy, a demo file, or a file outside their own project.
Fix
Check the file path and confirm the command is running the same file the student edited — see Student Projects.
Submission stuck in the queue+
Likely cause
Automated validation failed, or the instructor has not yet reviewed the submission.
Fix
Check the validation status and error messages in the queue interface, fix any reported issue, and ask the instructor to review if it has been waiting a while — see Validation & Queue.