Skip to main content

PhysicalAI reBot B601 Plugin

Third-party Seeed reBot B601 robot arm plugin for PhysicalAI, the Python library and runtime for robot control, transport, and CLI workflows. It registers with Physical AI Studio, the application that discovers catalog plugins and provides robot setup, teleoperation, and workflow experiences. Part of the physicalai-plugins monorepo.

PyPI version Python versions

Features

  • Concrete implementations of the Robot protocol — no inheritance or registration required
  • B601-DM (Damiao) and B601-RS (RobStride) follower drivers
  • Gravity and velocity feedforward in MIT mode, a smooth start-up move, and a fold into the rest pose on disconnect (see Control)
  • Optional Star Arm leader → follower teleoperation
  • Bundled URDFs for gravity compensation and kinematics

DM and RS expose the same LeRobot-compatible public joint frame. DM motor directions are +1 and RS motor directions are -1; the public gripper range is -270..0 degrees with no additional magnitude conversion in either follower. Commands use LeRobot's DM and RS soft limits in the same public frame. Both variants support an optional public-frame max_relative_target; None or the Studio value -1 disables the limit. RS remains MIT-controlled by default, matching LeRobot's RS defaults, which do not provide POS_VEL velocity settings.

Hardware

Class Arm Motors Protocol
ReBotB601DM B601-DM follower Damiao (via motorbridge) POS_VEL / FORCE_POS (default), or MIT
ReBotB601RS B601-RS follower RobStride (via motorbridge) MIT mode + force-limited gripper

Control

In MIT mode every motor runs a PD law at its own rate:

tau = kp * (q_ref - q) + kd * (dq_ref - dq) + tau_ff

A plain PD law sags under gravity by gravity / kp and lags a moving target by kd / kp seconds. The drivers fill both feedforward terms, the way Trossen's controller does for the WidowX AI:

  • Gravity compensation (gravity_compensation, default 1): tau_ff is the gravity torque of the commanded pose, computed from the bundled URDF's link masses, times this share (0 to 1). Weight the URDF does not include (a wrist camera, a grasped object) is left to the PD gains.
  • Velocity feedforward (velocity_feedforward, default 0.3): dq_ref is this share (0 to 1) of the smoothed velocity of the commanded targets, so kd holds the arm back less behind a moving target. On a real RS arm the full velocity (1) made the arm overshoot fast stops; 0.3 keeps most of the lag reduction without it.

Both apply to MIT mode only: ReBotB601RS always, ReBotB601DM with control_mode="mit". DM's POS_VEL mode runs the motor's own position loop, which has no feedforward input.

More behaviours apply to both modes:

  • Hold on enable: when torque is enabled (on connect, or by enable_torque()), the driver immediately commands the measured pose. An enabled motor otherwise runs its power-up command of zero stiffness and torque, and the arm would hang limp until the first action arrives.

  • Start-up approach (approach_speed, default 30 °/s): after torque is enabled, the first command eases the arm from where it is to the commanded pose along a straight joint-space line, then the driver tracks commands directly. A command that jumps further than any real motion (faster than 480 °/s, or more than 24° at once) eases in the same way. Set -1 to jump straight there.

  • Park on disconnect (park_on_disconnect, default on): before torque is released, the arm folds into its rest (zero) pose in two smooth stages at up to 30 °/s: the base and wrist first, then the shoulder and elbow. In MIT mode it then fades stiffness and gravity feedforward out over a second while keeping damping, so a link the rest pose does not support (such as the wrist) sinks onto its support slowly. It is skipped while torque is already off and stops early if a joint is blocked. Without it, the arm falls when torque is released.

  • Motion limits (motion_limits, default on): every arm command follows its target within per-motor speed and acceleration limits (150 °/s and 1000 °/s² for RS-06 and 4340P, twice that for RS-00 and 4310), braking in time so it does not overshoot a target that holds still. A light leader arm can be swung much faster than the follower should move.

  • Dropout detection: if every arm motor reports no torque while the arm is more than 5° from its command for 10 reads, get_observation() raises ConnectionError (see Troubleshooting).

set_control() changes gravity_compensation, velocity_feedforward, motion_limits and per-joint MIT gains while the arm runs, and returns the settings in effect:

robot.set_control(velocity_feedforward=0.0, mit_kd={"shoulder_lift": 12.0})

The default MIT gains:

Joint RS kp RS kd DM kp DM kd
shoulder_pan 50 3 120 5
shoulder_lift 150 10 120 5
elbow_flex 150 10 120 5
wrist_flex 50 5 30 2
wrist_yaw 50 4 30 2
wrist_roll 50 4 30 2
gripper 30 0.8 8 1

The RS gains are Seeed's and LeRobot's RobStride defaults. The DM gains are Seeed's Damiao values with the shoulder and elbow damping capped at 5 and the wrists stiffened from 18 to 30. A Damiao MIT frame (and an RS-00 one) cannot encode damping above 5, and the drivers reject gains above a motor's range instead of letting motorbridge clamp them silently.

The RS gripper servos on the motor itself and the firmware caps its torque (limit_torque) at gripper_mit_torque_limit (1.5 N·m) while it moves and gripper_mit_hold_torque_limit (0.5 N·m) once it stalls, for example on a grasped object. gripper_max_speed (400 deg/s) limits how fast its target moves, and so how hard the jaws hit an object; 3D-printed fingertips broke at the unlimited speed (about 1000 deg/s). On disconnect the driver restores the motor's full torque range after letting the gripper go.

Screenshots

Placeholder images — replace them with real screenshots.

reBot B601 in the PhysicalAI Studio robot catalog

Connecting to a reBot B601 in PhysicalAI Studio

reBot B601 leader-to-follower teleop in the PhysicalAI CLI

Installation

uv add physicalai-rebot-b601-plugin

motorbridge is included as a core dependency.

Quick start

import numpy as np
from physicalai.robot import Robot, connect
from physicalai_rebot_b601_plugin import ReBotB601DM

robot = ReBotB601DM(port="/dev/ttyACM0", can_adapter="damiao")

with connect(robot) as arm:
    obs = arm.get_observation()
    action = obs.joint_positions.copy()
    arm.send_action(action)

All classes satisfy isinstance(robot, Robot) — no inheritance or registration required. Use with physicalai.robot.connect and physicalai.robot.verify_robot.

Run with the PhysicalAI CLI

The PhysicalAI CLI run subcommand executes a RobotRuntime from a YAML config. The bundled teleop configs relay a StarArm102HDLeader to a B601 follower. They install physicalai-stararm-plugin for the command only:

uv run --with physicalai-stararm-plugin physicalai run --config packages/physicalai-rebot-b601-plugin/examples/runtime/teleop-dm.yaml
uv run --with physicalai-stararm-plugin physicalai run --config packages/physicalai-rebot-b601-plugin/examples/runtime/teleop-rs.yaml

Press Ctrl+C to stop.

Sinusoidal motion and joint reading

uv run physicalai run --config packages/physicalai-rebot-b601-plugin/examples/runtime/move-joints-dm.yaml
uv run physicalai run --config packages/physicalai-rebot-b601-plugin/examples/runtime/move-joints-rs.yaml
uv run physicalai run --config packages/physicalai-rebot-b601-plugin/examples/runtime/read-joints-dm.yaml
uv run physicalai run --config packages/physicalai-rebot-b601-plugin/examples/runtime/read-joints-rs.yaml

Zero-pose calibration

set_zero_position() on either B601 variant disables torque and stores the arm's current pose as zero on every motor. Physical AI Studio runs it from its calibration step when you add a B601 follower: move the arm into its folded rest pose with the gripper closed, then set zero.

URDF Models

Bundled URDF descriptions for gravity compensation and kinematics:

from physicalai_rebot_b601_plugin import get_urdf_path

urdf_dir = get_urdf_path()

# B601-DM / fixend arm (for gravity compensation)
dm_urdf = urdf_dir / "rebot-b601-dm" / "urdf" / "reBot-DevArm_fixend.urdf"

# B601-RS arm
rs_urdf = urdf_dir / "rebot-b601-rs" / "urdf" / "00-arm-rs_asm-v3.urdf"
URDF Model Use
rebot-b601-dm B601-DM (fixend) Gravity compensation for ReBotB601DM
rebot-b601-rs B601-RS v3 Kinematics for ReBotB601RS

rebot-b601-rs/urdf/00-arm-rs_asm-v3_joint_frame.urdf is a copy of the RS URDF with every arm axis reversed to match the joint frame ReBotB601RS reports. Studio uses it for the 3D preview and the driver for gravity compensation. The RS link masses are the ones Seeed corrected and checked against holding torques measured on a real arm (reBotArm_control_py, July 2026).

Development

uv sync
uv run pytest packages/physicalai-rebot-b601-plugin/tests/

Acknowledgments

URDF models for the reBot Arm B601 are from the reBotArm_control_py project, released under the MIT License by vectorBH6.

Metadata

Release files for physicalai-rebot-b601-plugin 0.9.1

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

Source distribution (sdist)

Source distribution for physicalai-rebot-b601-plugin 0.9.1
File Size Uploaded Provenance Actions
physicalai_rebot_b601_plugin-0.9.1.tar.gz 34.9 MB With provenance Details for physicalai_rebot_b601_plugin-0.9.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for physicalai-rebot-b601-plugin 0.9.1
File Interpreter ABI Platform Actions
physicalai_rebot_b601_plugin-0.9.1-py3-none-any.whl Python 3 none any Details for physicalai_rebot_b601_plugin-0.9.1-py3-none-any.whl

Total release size: 69.9 MB

Release files / physicalai_rebot_b601_plugin-0.9.1.tar.gz

Download URL physicalai_rebot_b601_plugin-0.9.1.tar.gz
Size 34.9 MB
Tags Source
SHA-256 checksum
How to use checksums
eab9ba68ed16c27c581faccc55627c6678d3c4f9b130bb255cb03cbc22edb263
BLAKE2b-256 checksum
How to use checksums
504b750ca9b09ad45cbcecd9cf2fa0c552d22dcb3b00bc07ac48b5b9e52c8aa2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 19, 2026.

Transparency log

Release files / physicalai_rebot_b601_plugin-0.9.1-py3-none-any.whl

Download URL physicalai_rebot_b601_plugin-0.9.1-py3-none-any.whl
Size 35.0 MB
Tags Python 3
SHA-256 checksum
How to use checksums
508c7369a1bc84b0ac7ebe1ae1d74c8f94a79fbb6e48c921d6137ce7fc4caed2
BLAKE2b-256 checksum
How to use checksums
d0ea0c3b8cb64d74621c25c536a1af3a82d2d30ac0d17fc4aa2d360a686c2248
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 19, 2026.

Transparency log

Security for physicalai-rebot-b601-plugin 0.9.1

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.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for physicalai_rebot_b601_plugin-0.9.1.tar.gz

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 Nov 19, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

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