Resolve robot setup problems
Find the next safe setup or recovery step while preserving original operations and calibration.
Start with the exact symptom
Keep the original error, operation and calibration files. Roboty handles supported software setup. Suppliers own assembly access, firmware servicing and repairs. Never reset, flash or repeat uncertain writes to make a check pass.
| Symptom | Next action |
|---|---|
| Hardware facts or power variant are unknown | Leave the affected procedure blocked. Confirm actual servo, supply and controller labels with the supplier. Do not infer voltage from a generic model reply. |
| Assembly is incomplete | Follow the supplier's sequence. Use only a supported isolated-motor initialization step when its instructions call for it. Complete assembly before calibration. |
| No USB controller is listed | Check the selected Mac and supplier cable/driver requirements. A listed port alone does not prove communication. |
| Identical boards or changed port | Review the intended robot/controller binding. Do not select by discovery order or silently reuse a remembered path. |
| Isolated motor is missing or addressing is ambiguous | Stop, follow the safe power-off procedure and inspect the exact isolated wiring. A single replying ID does not prove isolation. |
| Motor configuration was interrupted | Keep the original operation and any completed stages. Use bounded read reconciliation of plausible old/new settings. Do not repeat the write. |
| Motor mapping or calibration does not match | Review the exact arm, role, mapping and selected artifact. A readback mismatch does not authorize applying or recreating calibration. |
| Firmware is incompatible | Use the exact supplier servicing route, then deliberately recheck in Roboty. Roboty does not flash or factory-reset the controller. |
| Controller is busy | Preserve its current owner. Close and reconcile the original session before a new one. Do not kill another process to bypass ownership. |
| Access or local review is unavailable | Follow the displayed host-specific reason. Protected physical review happens on the owning Mac. A paired phone or saved file cannot grant permission. |
| Missing or incompatible Roboty component | Use a matching Roboty for Mac build. Another Python, LeRobot or LeLab installation cannot fill its component slot. |
| Disk full or calibration publication failed | Preserve the original receipt. Device writes may have completed even when no successor file was saved. Free only known disposable data and use the deliberate recovery path. |
| Check unavailable | Save the relevant facts/profile, inspect the stated mode prerequisite and obtain fresh local review. Full-motion qualification is not an initial motor-setup prerequisite. |
| Interrupted or legacy session | Request Stop, inspect/support the arm and retain the original session. Close/reconcile it on the original Mac. Recovery never replays the action. |
| Stale controller profile | Reconcile original work before deliberately reloading the saved profile. Preserve original calibration bytes. |
Setup status could not be updated
Retry the original status read and check the selected Mac connection. Offline Help and drafts remain available. A failed read never completes a hardware check. Keep original Stop available and preserve pending identities.
Return to your stage
What to include when asking for help
Share the exact displayed blocker, app/runtime version, selected robot/role and original operation identity. Exclude pairing credentials and unrelated personal data. Keep device details and calibration private unless you explicitly review a local export.
Ask the supplier about uncertain labels, physical access, wiring, power, firmware or repairs. Ask Roboty about its supported procedure, managed component, compatibility, retained results or recovery. An imported file or checklist cannot certify an unseen arm.
Recover an uncertain original session
Request Stop and follow the profile's support and power-disconnect procedure. Keep unknown effects visible. Open the saved robot on the original Mac and choose Recover the original session on this Mac. Roboty manages its host pause, verifies original worker cessation and requests fresh local authentication before releasing ownership. Recovery does not reconnect hardware, repeat a write or resume motion.
On iPhone, follow the named original Mac and robot in the recovery instructions. A stopped worker and observed power disconnection do not prove whether an earlier uncertain write occurred. Review that outcome through a separately admitted bounded observation.
After protected original-session closure and power review, Recover calibration file can republish retained planned JSON as an unverified candidate. It performs no hardware action. Select the candidate and separately check existing calibration before treating it as verified.
Page tools
Read as Markdown for copying or use with an AI agent.