Multi-view manipulation
Specify views, occlusion and workspace before selecting cameras and output modes.
TOBI E8 / MULTIMODAL CAPTURE
E8 multimodal
Ego capture platform
Bring vision and motion into one capture design.
For research projects combining multiple views, depth and motion. Define cameras, outputs and timing before validating the setup against a real task.
Supply and configuration require confirmation · development targets are not measured results
MULTIMODAL / EGO DATAE8
DESIGN THE CAPTURE WORKFLOW
Define the research task.
Then choose the data.
Human demonstrations
Define joints, coordinate frames, calibration and validity. Human joints are not directly usable robot actions.
Timing and acceptance
Confirm rates, timestamps and errors for each stream. Test synchronization, tracking and training outcomes independently.
CONFIGURATION / EVIDENCE
Configuration and evidence
This summary uses existing product materials and explicitly identifies discrepancies. Use the latest mutually confirmed specification for procurement.
| Vision configuration | The product matrix lists 10 cameras plus TOF; the former detail page said eight. Resolve this discrepancy against the latest specification before procurement. |
|---|---|
| Tracking figure | 1.5mm is a development target in the product matrix, not a verified accuracy result. |
| Data modalities | Planning materials list video, TOF, SLAM, IMU, timestamps, calibration and audio; confirm fields against the firmware version. |
| Motion-capture expansion | Evaluate additional motion-capture modules; confirm node count, installation, calibration, joint output and validity. |
| Wearability & power | The matrix lists 280g total and a rear 5500mAh battery; confirm the final configuration, accessory weight and runtime in writing. |
| Current supply | September 2026 was a historical production plan, not confirmation of production or stock. Confirm evaluation availability, lead time and support per project. |
Compare alternative capture setups
DATA & PROJECT READINESS
From specifications to an acceptable capture plan.From specifications to a testable capture setup.
View specifications on this pageRead specificationsDeveloper DocsDeveloper documentationDelivery Format GuideDelivery formatCompare other devicesCompare devices
Can it be used directly for robot training?Is this data ready for robot training?
Device observations do not automatically equal robot action labels. First confirm the data fields, timestamps, coordinate frames, target action space and data quality, then validate the conversion and training pipeline.Device observations are not automatically robot-action labels. Validate fields, timestamps, coordinate frames, target action space and quality before conversion and training.
How do I confirm supply and delivery scope?How do I confirm supply and scope?
Provide the task, quantity and planned delivery date. Confirm the device version, firmware, accessories, support scope and acceptance method in writing. Historical prototypes or production plans do not mean current stock is available.Provide the task, quantity and delivery window. Confirm the version, firmware, accessories, support and acceptance method in writing. Historical production plans do not confirm current stock.
How do I sync with other devices?How is cross-device synchronization verified?
Starting together does not mean clock synchronization. For a combined solution, confirm the clock source, interfaces, timestamp definitions, error statistics and dropped-frame handling; single-device metrics cannot substitute for full-system acceptance.Starting together is not clock synchronization. Confirm clock source, interfaces, timestamp definitions, error statistics and dropped-frame handling for the complete system.