Roboty software and upstream tools

Use the managed Roboty workflow

A matching Roboty for Mac development build manages its hardware software. Open Robots → Add a robot for supported controller selection, necessary motor configuration and calibration. You do not install Python, conda, LeRobot or LeLab to use this route. Access remains invitation-only and powered commissioning is separately qualified.

A missing or incompatible component needs a matching Roboty build from the installation maintainer. A separate upstream installation cannot repair the bundled component. Ordinary simulation remains separate from the hardware feature.

Optional upstream tools

The official SO-101 documentation and Seeed instructions own their applicable assembly, firmware servicing and repair procedures. Some kits configure motor IDs during assembly. Preserve that order. These tools may have their own software requirements, but they are not a prerequisite for Roboty's supported Add a robot workflow.

An advanced diagnostic needs a concrete purpose and separate device ownership. Stop and reconcile Roboty's original session before another tool acquires the controller. Never use another tool to bypass uncertain effects or unavailable physical permission.

Calibration exchange

Use the exact calibration handoff. Import is inert, verification reads hardware, and application or creation needs an explicit admitted write. Preserve original files and record the actual exporter/version. A working upstream robot still needs Roboty-specific verification and permission.

Assembly resources

Follow your exact supplier's written instructions. The optional note from Gabe preserves his existing personal assembly-video reference.