You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit d7be32e
Browse filesBrowse the repository at this point in the historyBrowse files
Improve camera viewing, developer tooling and packaged robot assets
Use the LiveKit room viewer for camera previews. Add development commands for setup, validation and contract generation, bundle pinned SO-101 assets, and simplify installation and integration guides.
- Follow [CONTRIBUTING.md](./CONTRIBUTING.md) for code style and validation. Use targeted checks first; avoid redundant environment syncs, builds and full test runs.
4
+
- We also maintain the public [livekit-cameras](https://github.com/Hebbian-Robotics/livekit-cameras) repository. Make coordinated changes there when the camera integration needs them, and update this repository's pinned Git revision. Keep the public repository generic and free of private project details.
5
+
- We also maintain [mcap-tools](https://github.com/Hebbian-Robotics/mcap-tools), which owns generic MCAP grouping and standard message encodings. Make coordinated changes there and update the pinned Git revision here; recording policy and robot-specific topics stay in this repository.
6
+
- We also maintain [so101](https://github.com/Hebbian-Robotics/so101), which owns the SO-101 driver, calibration/setup tool and model helpers. Make changes there, validate its standalone packages, and update the pinned Rust/TypeScript revisions and Python wheel here. Keep per-arm data in the separate config repository.
7
+
- For SO-101 hardware, use the [per-arm setup guide](./docs/hardware.md). Every arm needs its own serial port and LeRobot calibration. The station loads calibrated joint limits at startup; the bundled URDF supplies geometry. Check signs, offsets and gripper endpoints on that arm with torque off.
8
+
- If an SO-101 tracks poorly, moves jerkily or runs hot, gather evidence before changing anything: the arm's command outcomes, the target and measured angle of each joint, load, temperature, supply voltage and mechanical clearance. Then compare the servos' actual PID registers with the profile (`expected_position_gains` only verifies them; it does not write them). Servos differ between arms, so tune per arm from measurements; do not copy another arm's gains or loosen safety limits to hide a problem.
9
+
- A station or hardware-profile change takes effect only after `hebbian-robot-use-server serve` restarts (it is the control process). Support the arm and disable it before restarting; when the viewer is included, changes to it alone do not need a restart, since the station reads `dist/viewer` from disk.
- Follow [CONTRIBUTING.md](./CONTRIBUTING.md) for code style and validation. Use targeted checks first; avoid redundant environment syncs, builds and full test runs.
4
+
- We also maintain the public [livekit-cameras](https://github.com/Hebbian-Robotics/livekit-cameras) repository. Make coordinated changes there when the camera integration needs them, and update this repository's pinned Git revision. Keep the public repository generic and free of private project details.
5
+
- We also maintain [mcap-tools](https://github.com/Hebbian-Robotics/mcap-tools), which owns generic MCAP grouping and standard message encodings. Make coordinated changes there and update the pinned Git revision here; recording policy and robot-specific topics stay in this repository.
6
+
- We also maintain [so101](https://github.com/Hebbian-Robotics/so101), which owns the SO-101 driver, calibration/setup tool and model helpers. Make changes there, validate its standalone packages, and update the pinned Rust/TypeScript revisions and Python wheel here. Keep per-arm data in the separate config repository.
7
+
- For SO-101 hardware, use the [per-arm setup guide](./docs/hardware.md). Every arm needs its own serial port and LeRobot calibration. The station loads calibrated joint limits at startup; the bundled URDF supplies geometry. Check signs, offsets and gripper endpoints on that arm with torque off.
8
+
- If an SO-101 tracks poorly, moves jerkily or runs hot, gather evidence before changing anything: the arm's command outcomes, the target and measured angle of each joint, load, temperature, supply voltage and mechanical clearance. Then compare the servos' actual PID registers with the profile (`expected_position_gains` only verifies them; it does not write them). Servos differ between arms, so tune per arm from measurements; do not copy another arm's gains or loosen safety limits to hide a problem.
9
+
- A station or hardware-profile change takes effect only after `hebbian-robot-use-server serve` restarts (it is the control process). Support the arm and disable it before restarting; when the viewer is included, changes to it alone do not need a restart, since the station reads `dist/viewer` from disk.
`a758567c3978dfeefe282ede0500085a48fe8f78`, under Apache-2.0.
8
-
See [model attribution](robots/so101/README.md) and its included license files.
8
+
See [model attribution](https://github.com/Hebbian-Robotics/so101/blob/main/setup/src/so101_setup/assets/robot/so101/README.md) and its included license files.
9
9
10
10
Camera components use the separately maintained
11
11
[livekit-cameras](https://github.com/Hebbian-Robotics/livekit-cameras) and
0 commit comments