Troubleshooting
Check the failed stage before changing configuration or repeating a movement.
Connection problems
| Symptom | Check |
|---|---|
| No USB/Bluetooth option | Browser API support, site permissions and organization restrictions. |
| No ports listed | Data cable, driver, board connection and supported USB-chip filters. |
| Port busy | Another Lab tab, serial monitor or application already using it. |
| Motor not responding | Motor power, device cable and its ID. |
| Incorrect IDs | Assign IDs one motor at a time using Set motor IDs. |
| Lockout after STOP | Follow the recovery message, including power cycling if requested. |
Incorrect movement
Stop. Compare the selected model, IDs, direction, calibration and mechanical assembly. Do not rerun the full trajectory hoping the error will disappear.
Camera unavailable
Check browser permission, the selected device and other applications using the camera. A lesson’s virtual scene may be an alternative for that exercise, but cannot replace calibrating a real camera.
Missing class, assignment or access
Check email, active class membership, publication and assignment recipients. Locked indicates an unlocking condition; a missing assignment is a different state.
Report a problem
In Feedback, include the page, action, expected result, exact error, browser/OS and connection type. Inspect screenshots before sending: remove other people’s data and active remote-control codes.
Controls
| Button or field | Action and result |
|---|---|
| Back in the wizard | Correct the selected model, profile or transport before connecting again. |
| Retry | After fixing the problem, repeat polling. Compare ID rows and statuses, not just the Connected label. |
| Current tool’s Stop | Stop unexpected movement before investigating. Go home sends a new command and cannot replace stopping. |
| Profile → Email | Check the account if progress, a group or an assignment is missing. Compare the address with the teacher’s record. |
| Feedback | Include the page, button clicked, entered values, connection type and exact result. Add the expected result and error message. |
Example of a useful report: “In Control robot, Virtual SO-ARM101, no result appeared after selecting Node and clicking Compute position.” For hardware problems, also include the board model and motor statuses.