Skip to main content

Galaxea A1 SO-Leader for LeRobot

A third-party LeRobot Teleoperator plugin for the modified A1 leader arm.

LeRobot 0.6 Apache-2.0 License

Modified six-axis SO-101 leader paired with a Galaxea A1 follower

This package registers the LeRobot Teleoperator type galaxea_a1_so_leader. It owns the leader's serial bus, calibration, setup, action reads, optional feedback, and connection lifecycle. It does not import ROS, start an A1 Runtime, record datasets, or map leader values into robot coordinates.

Install

python -m pip install lerobot_teleoperator_galaxea_a1_so_leader

LeRobot integration

Convention Value
Distribution lerobot_teleoperator_galaxea_a1_so_leader
Type galaxea_a1_so_leader
Config GalaxeaA1SOLeaderConfig
Teleoperator GalaxeaA1SOLeader
Supported LeRobot >=0.6,<0.7

The distribution prefix, module layout, config registration, class names, and package exports follow LeRobot's third-party hardware conventions. LeRobot CLI entrypoints discover the plugin after installation.

Hardware contract

Channel Hardware Reported value
joint0 ... joint5 Feetech STS3215 IDs 0...5 degrees
gripper Feetech STS3215 ID 6 calibrated RANGE_0_100

The seven-motor topology is fixed. The config supplies lifecycle identity, serial port, and write retries; it does not redefine motor IDs or units.

To calibrate the leader by itself:

lerobot-calibrate \
  --teleop.type=galaxea_a1_so_leader \
  --teleop.id=a1-leader \
  --teleop.port=/dev/serial/by-id/your-device

This command opens the serial device. Run it only with the leader connected and its workspace clear.

Pairing with Galaxea A1

Leader outputs are not A1 commands. The leader reports degrees and its calibrated gripper range; the A1 Robot plugin accepts radians and a normalized 0..1 gripper target.

Use make_galaxea_a1_processors() from lerobot-robot-galaxea-a1 with LeRobot's programmatic APIs, or use the tracked Galaxea A1 Runtime workflow. Do not pair these devices through the identity processor in the generic LeRobot 0.6 CLI.

Development

uv sync --dev
uv run pytest
uv run ruff check .
uv run ruff format --check .
uv build

Metadata

Release files for lerobot-teleoperator-galaxea-a1-so-leader 0.1.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for lerobot-teleoperator-galaxea-a1-so-leader 0.1.3
File Size Uploaded
lerobot_teleoperator_galaxea_a1_so_leader-0.1.3.tar.gz 10.2 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for lerobot-teleoperator-galaxea-a1-so-leader 0.1.3
File Interpreter ABI Platform
lerobot_teleoperator_galaxea_a1_so_leader-0.1.3-py3-none-any.whl Python 3 none any Details

Total release size: 20.6 kB

Release files / lerobot_teleoperator_galaxea_a1_so_leader-0.1.3.tar.gz

Download URL lerobot_teleoperator_galaxea_a1_so_leader-0.1.3.tar.gz
Size 10.2 kB
Tags Source
SHA-256 checksum
How to use checksums
53f2f6ae04f80e90f27e2bb14b57bfac27ddd7d26774df312150de02571a3aa0
BLAKE2b-256 checksum
How to use checksums
ec90a2a22ec412d218c2f23fa6fe3bf47cbd46b301670369f607c054a7376a0b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 4, 2026.

Transparency log

Release files / lerobot_teleoperator_galaxea_a1_so_leader-0.1.3-py3-none-any.whl

Download URL lerobot_teleoperator_galaxea_a1_so_leader-0.1.3-py3-none-any.whl
Size 10.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
0f2e64e13512851d8a9f9fa3d1ff4cd74abd485c5156499083fa380868ae5e4a
BLAKE2b-256 checksum
How to use checksums
8e7768c4df8c2a4950f59adee368a6b24ab283c83f70b5a0c9f2d5c436f10b2e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 4, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.3 This release

2 release files

0.1.2

2 release files

0.1.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page