Geometry
STEP or native CAD for editable geometry; STL for printing; drawings for tolerances and interfaces.
Open engineering references · 01
Manipulators, robot arms & bimanual systems
Compare accessible arm designs, robot-learning interfaces and bimanual research systems without confusing an assembly guide with a production release package.
Read the asset type first
Different files answer different questions; one cannot stand in for another.
Robot description
URDF, MJCF or USD expresses links, joints, limits, meshes and estimated inertial properties for software and simulation.
Control & data
Drivers, calibration, teleoperation, dataset formats and policy interfaces connect the mechanism to repeatable experiments.
Build evidence
BOM, assembly records, current limits, test fixtures and fault behaviour determine whether a second build can reproduce the first.
Official and first-party project gateways
Every record states what is available—and what it still cannot prove.
Sources checked 4 August 2026. External projects change; confirm version, licence and maintenance status again at the original source before use.
01
The Robot Studio with the open robotics community
Open original source ↗The Robot Studio · SO-100 / SO-101
- STEP and STL files
- BOM and assembly guidance
- Simulation and optional hardware
Repository identifies Apache-2.0; verify every linked vendor file and optional asset separately.
Reproducible learning-platform reference; not production evidence
A practical starting point for low-cost manipulation, teleoperation and data collection.
Printed parts, servo variants, power choices and payload changes alter strength, thermal behaviour and calibration. No certification or product warranty is implied.
Strongest when treated as a controlled educational or research baseline: freeze a revision, record the exact BOM and validate limits on the as-built arm.
- Robot interfaces and processors
- Dataset and policy tooling
- SO-101 setup and calibration guidance
LeRobot code is Apache-2.0; hosted datasets, models and hardware designs can carry different terms.
Actively maintained software ecosystem; hardware maturity varies by platform
Connect supported hardware to a common data, training and evaluation workflow.
Software support does not establish payload, collision safety, reliability or fitness for an application. Check the exact documentation version and platform support table.
Use LeRobot as an experiment interface, then preserve hardware configuration, calibration, dataset provenance and evaluation conditions as separate evidence.
- Teleoperation and data-collection software
- Hardware assembly tutorial links
- Configuration and camera setup
Repository code is MIT; linked hardware, third-party components and later ALOHA variants must be checked separately.
Influential research reference with configuration-specific dependencies
Study bimanual teleoperation, synchronized sensing and demonstration collection.
The public stack documents tested operating-system and ROS configurations; it is not a current universal compatibility or safety guarantee.
Its value is architectural: trace the complete sensor–operator–robot–dataset chain, then revalidate every substituted component and software version.
Before adoption
Move from ‘I found the files’ to ‘I know the next validation step’.
- 01
Confirm editable geometry, dimensions, tolerances and interface drawings—not only printable meshes.
- 02
Record actuator model, voltage, current limits, gear ratio, firmware and calibration for the exact build.
- 03
Measure payload, repeatability, backlash, temperature, stop behaviour and cable life within a bounded task.
- 04
Keep people outside unvalidated motion and pinch zones; use qualified review for human-contact applications.