Public: anyone can read this; the crew can change it.

Migrated from github.com/Trevato/SO-ARM100

workbenchthis machine

Clone, one command, drive: a guided setup TUI that finds both arms, reuses existing calibration, and starts local teleop #564

Closed opened this has it

Pull #566 was closed

opened this

Owner, 2026-10-25: "I have both of the arms connected to my mac… I wasn't able to get teleop going… it's asking for calibration and stuff even though I already did all that… take me through a guided process… I could clone the repo then just run the TUI or something… is there a TUI? is it good? maybe we just need to lean into that."

Probe, the same day, on the owner's Mac:

  • Only one arm was visible (/dev/cu.usbmodem5B610341251).
  • A clean node bin/so101 … from a snapshot of main crashed at once with ERR_UNSUPPORTED_ESM_URL_SCHEME … 'bun:'. Some import chain still reaches bun:sqlite from the CLI on a laptop. The Pi path was fixed in src/sqlite.ts and node-loads.test.ts; the CLI is not covered.
  • There is no setup or teleop TUI. so101 leader --to ws://… drives a remote follower through serve.

Done when: clone, then one command, then you're driving. bun install && bun so101 setup (and the same under node) is a friendly full-screen guided setup: arrow keys, plain words, a progress line.

  1. Find the arms. List USB serial adapters. If fewer than two are found, say so ("I see 1 arm. Plug in the other one, or check its power. Watching…") and continue as soon as a second appears.
  2. Tell them apart. "Wiggle the arm you'll hold (the leader)." Watch both buses for movement and name them. Remember the choice by USB serial number.
  3. Calibration only if it's needed.

- Reuse what exists: read existing calibrations, both this repo's own and LeRobot's (~/.cache/huggingface/lerobot/calibration/{robots,teleoperators}/*.json). - Validate: check them against the servos' current ranges. - Re-calibrate only a joint that is out of range, one joint at a time with a picture and a live bar, never the whole arm.

  1. Teleop locally. so101 teleop connects the leader to the follower directly in one process at 60 Hz, with a live joint table, lag, and a big "press space to STOP". It needs no serve and no network.
  2. Optionally share it: "Share on the web?" starts serve plus the follower for the hosted app.
  3. It runs on a fresh clone with Node 22.6+ and Bun. A test runs the CLI's --help, ports and setup --dry-run under Node.

Docs: a short "Plug in and play" section in the README, with the HF SO-101 docs linked (https://huggingface.co/docs/lerobot/so101).

commented

Split into #570 (the CLI runs under Node), #571 (so101 teleop) and #572 (so101 setup, which waits on the other two). Pull #566 drew three change requests with no approval in between. After the planner restated its last change, two more runs only merged main, so it is closed and its commits are the starting point for each piece (refs/pull/566/head). Your acceptance criteria are carried over unchanged, except share-on-web, which the pull had already dropped.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs