Teleoperation Data Collection
In teleoperation data collection, an operator uses a teleoperation device to control the robot to perform demonstrations. Actions are produced directly on the target robot, the data includes full robot state, and it is stored as HDF5, so it can be curated as soon as it is ingested.
Supported Devices
| Model | Form factor | Typical data streams |
|---|---|---|
| Station Lite | Dual-arm tabletop workstation | Dual-arm joint states, end-effector poses, gripper opening, top and dual wrist cameras |
| MOS | Wheeled dual-arm mobile manipulator | Dual-arm joint states, end-effector poses, gripper opening, base velocity, head and dual wrist cameras |
All streams are time-aligned to a common clock and written to HDF5, typically at 30 Hz. See Data Formats for the file layout.
Prerequisites
| Requirement | Details |
|---|---|
| Device registered | The device model and SN are in the device inventory, and the device is online |
| Teleoperation device bound | Robot-based devices must be bound to a teleoperation device. Devices without one cannot run collection tasks. |
| Collection task | A collection task bound to the device exists and has a collector assigned |
| Site safety | Bystanders have left the work area and the emergency stop is within reach |
Collecting Data
1. Claim the Task
The collector signs in, opens Data Collection → Collection Tasks, and clicks Claim Task on a task card marked Pending Claim. If the task configuration changed after assignment, the card is marked Changed; review the changes before claiming.
2. Pre-Collection Checks
After the device connects, the collection client runs automatic checks:
| Check | Pass criteria |
|---|---|
| Teleoperation device connection | Teleoperation device and controllers are online and tracking normally |
| Robot communication | Joint states are streaming normally with no errors |
| Cameras | All cameras are streaming at the expected frame rate |
| Storage and network | The client has enough free space and can reach the platform |
If a check fails, the task cannot be set to ready. Resolve the issue and run the checks again.
3. Record Demonstrations
- Click Start Collecting on the task card.
- Once the robot returns to its initial pose, begin an episode.
- End the episode when the action is complete. Each episode is numbered automatically and uploaded according to the task's upload mode.
- Repeat. The task card shows progress as completed / target episodes.
You can pause at any time; data that has already uploaded is not affected.
4. Complete the Task
When the target count is reached and every upload has finished, the task changes to Completed automatically.
Demonstration Quality Requirements
| Requirement | Details |
|---|---|
| Clear start and end | Start each episode from the initial pose and stop once the task is complete; avoid long idle periods at either end |
| Smooth motion | Avoid repeated probing and long pauses |
| One task per episode | Each episode should complete the task exactly once |
| Failures can stay | If a demonstration fails, move on to the next episode; flag the failure during curation |
| Safety first | If anything unexpected happens during teleoperation, release the controllers or press the emergency stop immediately |
After Collection
Once ingested, the data has format HDF5 and status Ready to Curate, and can be added to a curation project directly. See Data Assets and Curation Projects.
Common Issues
| Issue | Resolution |
|---|---|
| The task can't be started | Check the teleoperation device binding and the pre-collection check results |
| Progress reached the target but the task isn't complete | Some data is still uploading or failed to upload; wait or re-upload |
| The device isn't available when creating a task | The device is offline, under maintenance, or decommissioned. See Device Management. |

