Skip to content
Hebbian-RoboticsPublic

Repository files navigation

SO-101 drivers and setup

Connect, calibrate and control SO-101 arms from your own application. Use the hardware driver with your policy or teleoperation stack, or run the calibration tool on its own. No RUA installation is required.

Included

  • Rust hardware driver: servo I/O, joint feedback, preflight, torque control and recovery.
  • Rust setup CLI with terminal commands, a bundled browser UI, and a read-only 3D model.
  • TypeScript model-rendering helpers for React/Three.js viewers.

Calibrate an arm

Download the so101 archive for your platform from GitHub Releases, extract it, and put the executable on your PATH. The executable contains the browser UI and robot models.

so101 setup

The command opens a local browser page. With the arm supported and torque off, connect its USB controller, match the reference pose, record safe joint travel and gripper endpoints, then review and save. The setup tool never powers or moves the arm.

Use so101 setup --no-browser to run the same workflow via terminal commands. See the setup instructions for the headless workflow, motor ID programming, servo reset, and source builds.

For a directly installed executable, run so101 update to install the latest GitHub release for your platform. Use so101 update --check to see whether an update is available. If you installed using a package manager, update it there.

Each controller gets its own arms/<serial>/setup.toml and LeRobot-compatible calibration.json. See the setup guide for saved files, backups and calibration details.

Use the Rust driver

In an existing Rust project, add the driver from this release:

cargo add hebbian-so101 --git https://github.com/Hebbian-Robotics/so101 --tag v0.1.5

Use Servos to open the configured bus, run preflight and read joint angles and motor health. Enabling torque and sending joint/gripper goals are explicit operations. Start with the Rust usage example and configuration contract.

The driver handles hardware operations. Your application owns motion limits, workspace checks, timing and process supervision. The setup CLI is optional when using the driver.

Use the model helpers

In an existing React/Three.js project:

pnpm add '@hebbian/so101-model@github:Hebbian-Robotics/so101#v0.1.5'

Import helpers from @hebbian/so101-model/robot-model. For example, useRobotModel loads robot/so101/robot.urdf relative to your page. Serve the URDF and meshes at that path and preserve their Apache license. These helpers render the model; use the Rust driver or your control stack to communicate with the arm.

The optional TPU gripper and wrist-camera assembly is bundled as robot-soft-gripper-camera.urdf, alongside the stock model. Select model_variant = "soft-gripper-camera" in calibration configuration and use the same URDF in your control application. useRobotModel(modelUrl) can load either variant. Keep the optional model's separate attribution notice with its meshes.

Hardware and development

For assembly and the official setup workflow, follow the LeRobot SO-101 guide and The Robot Studio hardware repository. Servo transport uses rustypot. This library's coordinate conventions explain its model alignment; physical calibration and tuning still need checks on the particular arm. Per-arm configs are user-owned and aren't shipped here.

See contributing to build from source and run checks.

License

Software is MIT. Robot URDF/mesh assets retain their Apache-2.0 license; third-party browser notices accompany the setup executable. See NOTICE for provenance.

Releases

Packages

Contributors

Languages