Rig mechanical design
Camera brackets, cable routing, and operator sight lines that survive daily use.
Imitation models need logs from the grippers and camera mounts you will ship, not a rental arm with different kinematics.
Teleoperation capture hardware records synchronized video, joint states, and success labels while an operator drives the same end effector your fleet will use. Hardware Form designs the rig, electronics, and production path so capture volume can scale with your build program.
Most teams underestimate sync and mounting. A wrist camera that slips half a degree between sessions will show up as label noise months later.
| Layer | Typical choices | Production tie-in |
|---|---|---|
| Leader interface | Exoskeleton, spacemouse, second arm | Ergonomic fixtures you can bolt to a work cell |
| Follower robot | Your production arm or AMR manipulator | Same motor drivers and gearboxes as field units |
| Logging | MCAP, ROS 2 bags, custom HDF5 | Edge recorder with deterministic timestamps |
| QA | Golden trajectories, dropped frame checks | Factory functional test hooks |
See also robotics training data programs and sim-to-real HIL manufacturing.
Camera brackets, cable routing, and operator sight lines that survive daily use.
PPS, hardware trigger lines, or PTP on a dedicated logging subnet.
On-robot buffer, checksums, and upload policies that match your security model.
From five bench units to PCBA, assembly, and test for a capture fleet.
No. We build and manufacture the hardware and logging stack that produces data on your tasks and your mechanisms.
Yes, when you share the control interface and safety limits. We align recorder schemas with your training pipeline.
The rig uses your production end effector, camera extrinsics, and lighting targets so policies transfer to units you actually ship.