Device integration
Provide hardware model, firmware, protocol, timestamp definitions, sample rates and example recordings. Validate reading and clock alignment before pairing devices.
Resources
Connect your devices, data standards and compute environment. Start with a representative sample and define the interfaces, versions and validation needed for your workflow.
Provide hardware model, firmware, protocol, timestamp definitions, sample rates and example recordings. Validate reading and clock alignment before pairing devices.
Define the target model schema and action space, then test export. Deliver video, time series, calibration, annotations and a version manifest together.
Agree on inputs, outputs, versions, retries and human review. Keep API keys server-side; third-party transfer of sensitive raw data requires specific authorization.
Specify dependencies, model licenses, compute and runtime. Check latency, action bounds, emergency stop and takeover before physical execution.
One task, one complete episode and the actual device version.
Verify clocks, units, coordinate frames, state and action fields.
Read, replay and export; document unsupported fields.
Deliver adapter notes, test results and maintenance scope.
LeRobot, ROS 2 and multimodal logging tools can be integration targets. Test the actual device, format and version; this does not imply universal compatibility or an official partnership.
Robot learning data and training workflows.
Official documentation →Robot logs and multimodal data visualization.
Official documentation →Share the target device, operating system and model environment so we can confirm available documentation, software versions, license terms and integration work.
Build with Actrium
Define the devices, data and evaluation your project needs.