Skip to content
Solutions · Physical AI & Robot Data

OpenArm Datasets and Bimanual Teleoperation Data

OpenArm dataset options for robot learning teams: a ready-made two-arm set recorded on OpenArm-class arms, or custom teleoperation collection for your own tasks. Each episode pairs two wrist cameras, scene cameras and the joint states and actions of both arms on one clock, delivered in LeRobot format for training robot policies.

Book an OpenArm Data Strategy Session Free 30-minute call · mutual NDA included
BimanualTwo OpenArm-class arms per episode, with joint states and actions for both.
Add-onsDepth, plus tactile or force-torque streams, agreed per program.
LeRobotDelivery format, with MCAP, HDF5 and RLDS on request.
The Hardware

OpenArm-Class Bimanual Arms We Record With

OpenArm is Enactic's open-source robot arm for physical AI research and contact-rich work. We record with OpenArm-class arms in a two-arm tabletop setup, and the specs below are Enactic's own.

Seven joints and a gripper

Enactic's repo describes a 7-DoF arm with human-scale proportions, built for teleoperation, imitation learning and real-world data collection. Its dataset format logs seven joint positions plus the gripper per arm.

Backdrivable joints and payload

The joints are compliant and backdrivable, with DAMIAO motors chosen per joint from shoulder to end effector. Enactic's docs for the current release list a nominal payload of 4.1 kg and a peak of 6.0 kg, end effector included.

Leader-follower teleoperation

Enactic documents 1:1 teleoperation from a leader arm to a follower arm. Unilateral control sends position commands one way. Bilateral control adds two-way force feedback, so the operator feels what the follower touches, and Enactic's site lists real-time gravity compensation.

Open hardware and code

Enactic publishes the CAD under the CERN-OHL-S-2.0 license and its control, ROS 2, teleoperation and dataset code under Apache-2.0.

For the policies trained on these episodes, our page on ACT and Diffusion Policy training data covers what each one expects from an episode.

Ready-Made or Custom

The Ready-Made OpenArm Dataset and Custom Collection

Start from two-arm episodes we have already recorded, or commission new collection. Both arrive with per-episode provenance and consent records.

Ready-made OpenArm bimanual set

Teleoperation episodes recorded on two OpenArm-class arms, ready to license. The set is licensed non-exclusive and can be sublicensed to your own client. A representative sample pack with the same modalities, calibration and delivery format is available on request.

A new task on an existing robot

We record your task list on a robot we already record with, such as OpenArm-class arms. Each task is written as the objects, actions and success conditions your policy is evaluated on.

A new robot or embodiment

When your policy runs on another arm, gripper or layout, we set up collection on that embodiment. ARX, PiPER and SO-101 are among the arms we record with on request.

Our robot data collection services page covers the ready-made UMI, G1 and YAM sets of kitchen, bedroom and staged retail tasks. For two-arm data on a second arm family, see our page on YAM arm data.

Compare the Options

Ready-Made and Custom OpenArm Data Compared

Both options record the same core streams and differ in who sets the tasks and how the data is licensed.

OptionReady-made OpenArm setCustom collection
What you getTwo-arm teleoperation episodes already recorded on OpenArm-class armsEpisodes recorded to your task list, on an existing robot or a new embodiment
TasksThe tasks recorded in the set, which the sample pack shows before you licenseYour objects, actions and success conditions, written with your team before the pilot
StreamsTwo wrist cameras, scene cameras and joint states and actions for both armsThe same core streams, with depth and tactile or force-torque added where the program calls for them
LicenseNon-exclusive, and you can sublicense it to your own clientNon-exclusive or exclusive. Exclusivity covers the data and its resale rights, separate from the robot
Delivery formatLeRobot, with MCAP, HDF5 and RLDS on requestLeRobot, with MCAP, HDF5 and RLDS on request
Best fitTeams that want real two-arm episodes to train and evaluate on nowTeams with their own task list, evaluation or embodiment
Per-Episode Streams

What Each OpenArm Episode Records

Each episode is one synchronized recording of a two-arm task, from what the cameras saw to what the operator commanded. Streams are agreed per program.

Two wrist cameras

A view from each wrist, the close-up a robot has at execution time.

Scene cameras

Views of the whole workspace, with both arms and the objects in frame.

Joint states for both arms

Joint positions for each arm and its gripper at every step.

Actions for both arms

The commands the operator sent to each arm at each step, the targets a policy learns to reproduce.

One clock

Cameras, joint states and actions share one clock, so every frame lines up with the arm state behind it.

Provenance and consent

Every episode carries provenance and consent records, with a chain of custody you can audit.

Add-Ons

Depth, Tactile and Force-Torque Add-Ons

Custom programs can add streams to the cameras and joint data, agreed in scoping and recorded on the same clock as the rest of the episode.

Depth

Metric per-frame depth on bimanual arms, so positions and distances in each episode come out at true scale.

Tactile or force-torque streams

Contact force for grasps where the policy needs to register contact as well as see it. Our tactile manipulation data page covers that capture in depth.

Delivery and Licensing

Delivery Formats and License Terms

OpenArm episodes ship in LeRobot format, so they load into the training stack your team already runs. Other formats and the ready-made license work like this:

1 MCAP, HDF5 and RLDS on request, for loaders, replay tools or pipelines that expect them.
2 Ready-made data is licensed non-exclusive, so other teams can license the same episodes.
3 Ready-made data can be sublicensed to your own client, for teams that build models for others.
Custom Collection

Recorded to your tasks, on the terms you choose.

Custom collection runs on non-exclusive or exclusive terms. Exclusivity covers the data and its resale rights, separate from the robot that recorded it. Exclusive terms are priced above non-exclusive, and term and scope are agreed once the pilot is defined.

Non-exclusive or exclusive terms
Exclusivity covers the data and its resale rights
Term and scope set once the pilot is defined
Scoping

What Shapes the Engagement

We scope every program against these factors with you, then quote it as a whole.

1

Ready-made or custom

The ready-made set, a new task on an existing robot, or a new robot or embodiment.

2

Embodiment and gripper

OpenArm-class arms in a two-arm setup, or another arm such as ARX, PiPER or SO-101.

3

Tasks and objects

Your task list, written as the objects, actions and success conditions your policy is evaluated on.

4

Streams, add-ons and format

Which streams each episode carries, which add-ons join them, and the delivery format.

5

Episode length

How much of a task one episode covers, from one grasp or handover to a multi-step routine.

6

Acceptance and QC criteria

What counts as a reject, such as a dropped object, a collision, a stream out of sync or an incomplete task.

7

Pilot size

How many episodes and task variations the pilot covers, so your team can train and evaluate on it.

8

Exclusivity and sublicense rights

Non-exclusive, sublicensable ready-made data, or custom collection on non-exclusive or exclusive terms.

Start Today

Have a Two-Arm Task to Record?

Send us the task, the objects and the arms your policy runs on. We'll send a representative sample pack with the same modalities, calibration and delivery format you'd get in production, so your team can check the episodes before any commitment.

Book a Strategy Session →
Ask us about
The ready-made two-arm set and its sample pack
A new task on arms we already record with
Collection on a new robot or embodiment, including ARX, PiPER and SO-101
Depth and tactile or force-torque add-ons
LeRobot delivery, with MCAP, HDF5 and RLDS on request
Non-exclusive or exclusive terms and sublicense rights for your client
Questions

Frequently Asked Questions on OpenArm Datasets

Teleoperation episodes recorded on two OpenArm-class arms, each with two wrist cameras, scene cameras and joint states and actions for both arms on one clock. A representative sample pack with the same modalities, calibration and delivery format is available on request.

Yes. Custom collection follows two paths: a new task on a robot we already record with, or a new robot or embodiment. Each task is written as the objects, actions and success conditions your policy is evaluated on, and depth and tactile or force-torque streams can be added.

Ready-made data is licensed non-exclusive, and you can sublicense it to your own client. Custom collection runs on non-exclusive or exclusive terms. Exclusivity covers the data and its resale rights, separate from the robot used to record it, and exclusive terms are priced above non-exclusive. Term and scope are agreed once the pilot is defined.

Our episodes ship in LeRobot format, with MCAP, HDF5 and RLDS on request. Enactic's OpenArm Dataset format is the one its own recording tools write, storing joint positions, velocities and torques in Parquet files with camera frames, and Enactic's converter turns it into LeRobot v2.1 or v3.0.

Scope Your OpenArm Data

A 30-minute strategy call. Tell us the tasks, arms and streams your policy needs, and we'll scope a pilot or a sample pack from the ready-made set.

Discuss Your Project