RoboParty logoRoboParty

ROBOTO

Price
Unknown
Type
Humanoid Robots · Human-scale Humanoid
Applications
Research & Education · Developer Kit / Research & Education · Education Platform / Research & Education · Research Platform
Status
Prototype
Availability
Not released
Purchase
Not disclosed
Release Date
Sep 28, 2026
Country/Region
China
24 DOF
Total degrees of freedom
135 cm
Height
Approx. 39 kg
Weight
3 h
Runtime

RP1 is RoboParty’s open-source bipedal humanoid for research, education and robot development. It stands 1.35 m tall, weighs about 39 kg and has 24 active degrees of freedom. Standard equipment includes a locomotion head, dummy hands and an RK3588 computing module. It supports hot-swappable batteries and modular development.

ROBOTO 01(RP1)

Hardware Specification

Physical Specifications

Arm Length
50 cm
Materials
AL6061/7075 aluminum, engineering plastics and specialty rubber
Total degrees of freedom
24 DOF

Mobility & Payload

Maximum Grade Angle
30 °
Max Speed
≤4 m/s
Step Height
5 cm

Degrees of Freedom

Controllable DOF per Arm
5 DOF
Depth
20 cm
Head DOF
0 DOF
Height
135 cm
DOF per Leg
6 DOF
Waist DOF
2 DOF
Weight
Approx. 39 kg
Width
45 cm

Mechanical Structure

End-Effector
Dummy hands
Internal Wiring
Internal 24 V wiring; adapter board provision
Joint Type
Four in-house two-stage planetary inner-rotor modules

Sensors

Depth Camera
Intel D435i (optional)
IMU
One high-precision 6-axis IMU

Battery and Runtime

Battery Capacity
10 Ah
Battery Type
Dual-battery design
Charging Method
USB-C fast charging and magnetic charging
Charging Power
140 W
Charging Time
1.5 h
Hot-swap Support
Battery hot-swapping without shutdown
Power Supply
Operation while charging supported
Runtime
3 h

Compute Platform

Onboard Compute
RK3588 ×1; optional development computing module

Safety and Protection

Emergency Stop
Remote and portable emergency stop; three-channel redundancy
Operating temperature
-10–40 °C
Pinch Protection
Enclosed, pinch-resistant joints

Interaction and Communication

Communication
Wi-Fi 6, Bluetooth 5.2, 4G
External Port
USB Type-A ×2, USB Type-C ×2, RJ45 ×2

Development and Expansion

Configuration Options
Interchangeable locomotion, interaction, data-collection and perception heads
Secondary Development (SDK)
ROS 2, SDK, simulation environment and training code

Development support

ROBOTO 01(RP1)Current model

Conditional access

Exact existing RP1 record. Official series documentation maps RP1 to24 body joints and RP1 Pro to28 body joints plus2head joints; hand axes are counted separately. This batch covers the corresponding body development configuration only, conditional on matching delivered mechanical revision, LRO CAN-FD controller/firmware, IMU, host SDK ABI, calibrated zero/sign/bus-ID maps and closed-chain ankle conversion. Source pins: inference b3eaa0bb6a9d, motors a5c930a06a16, description8c12d13ae051. The current website and pinned source differ in API defaults, control periods and robot type labels; use one mutually compatible pinned stack and verify its actual contract. Preserves existing physical specifications, price/status and publication state; the two Pro records remain separate. No software/hardware executed.

ROBOTO Origin

Conditional access

Exact existing RobotoOrigin/RPO prototype, not RP1/Pro variants. Pinned deploy95be3502 gitlinks fix inferenceb3eaa0bb and motorsa5c930a0, verified by Git tree without checking out/executing code. RPO reference configuration has23DMmotor slots across4CAN buses plus HIPNUCserialIMU, actualsign/offset/urdf2motor/closed-chain ankles; this does not overwrite physicalDOF. Match delivered motor models/firmware/USB-CAN/zeroing/config and built ROS2Humble-or-Jazzy workspace, one command owner. Parent aggregateGPL does not relicense submodules/binaries/assets; only scoped reviewed code grants apply.

Exact existing RP1 record. Official series documentation maps RP1 to24 body joints and RP1 Pro to28 body joints plus2head joints; hand axes are counted separately. This batch covers the corresponding body development configuration only, conditional on matching delivered mechanical revision, LRO CAN-FD controller/firmware, IMU, host SDK ABI, calibrated zero/sign/bus-ID maps and closed-chain ankle conversion. Source pins: inference b3eaa0bb6a9d, motors a5c930a06a16, description8c12d13ae051. The current website and pinned source differ in API defaults, control periods and robot type labels; use one mutually compatible pinned stack and verify its actual contract. Preserves existing physical specifications, price/status and publication state; the two Pro records remain separate. No software/hardware executed. Body position/hybrid interface: apply_action(p,v,kp,kd,tau), URDF-to-motor permutation and sign conversion, wrapped state and nearest-turn targets. Supply every position and gain entry; actual pinned validation requires finite kp>0 and kd>=0 for every motor. The website says optional gains default from configuration, but this pinned Python binding requires explicit p,v,kp,kd; only tau has a default. Position/velocity targets must match the 24-entry body layout; check finite values, limits and state freshness before invocation. CAN-FD batches use motorID-1 in8slots per bus. Parallel ankles convert desired joint PD+feedforward to actuator position targets with positive gains. This is position development, not an independent zero-kp velocity or pure torque mode. get_joint_tau is derived from get_motor_current; the pinned LRO feedback decodes CurMax amperes, so do not interpret it as measured jointNm or apply a torque-space inverse-transpose to raw current. No independent velocity/Nm/FF, Cartesian, navigation, teleoperation or persistent collection claim is added. Constructor opens hardware interfaces; init status does not aggregate per-driver success, refresh waits then reads cache.

Development capabilities

Joint-level controlConditional support
C++ SDKConditional support
Position commandsConditional support
Sources · 4

Open source & build resources

Software

Partially available

Examples or supporting tools are available; this does not establish access to the core system.

Hardware design

Not verified

There is not enough verified evidence to establish this dimension.

Build resources

Not verified

There is not enough verified evidence to establish this dimension.

TypeResourceLicenseApplicable versionOpen
Coderoboparty_inference · scoped primary-code license

GitHub · Roboparty/roboparty_inference

Complete pinnedGPLv3 grant for primary roboparty_inference C++/pybind source, consistent with parent license inventory. Bundled ONNX/runtime libraries/checkpoints, NPZ/motion data/models and subdependencies remain separately scoped; no execution or whole-robot licensing claim.

GPL-3.0-onlyrp1_24dof_cpp_body_b3eaa0bb, rp1_24dof_python_body_b3eaa0bb, rp1_24dof_ros2_documented_interfacesOpen GitHub

Commercial Status

Status
Prototype
Price
Unknown
Release Date
Sep 28, 2026

Timeline

  1. Robot release
    ROBOTO 01(RP1)
Submit a source or correction