01 · DEVICE
Raw footage and synchronization
Native frame-rate video, IMU, calibration, and time synchronization. This is the default delivery foundation.
Hardware-verifiable Ego data
Delivery format and recording specifications
TOBI remains a production Ego hardware company. This page explainsWithout modifying the device hardware parameterspremise, how to package the same capture output into a training-ready package — not a substitute for written specifications, calibration records, or SOW acceptance.
Delivery tiers (buyer selects)
Purchase by depth. Sample fields = delivered fields. Leave missing columns blank; do not fill in fake values.
02 · HUMAN
Narrative and keyframes
Cross-check wearer-viewpoint sentences and keyframes. Do not rewrite them as detector outputs.
03 · ESTIMATE
Estimation layer (optional)
Hand points, privacy masking, SGBM distance, etc., tagged with method; not treated as device measurements. This layer can be toggled per project.
04 · INDEXES
Indexing, Quality Control, and In-Stock
time_sync, validity, and hourly ordering in the store. Quotes and scheduling are confirmed in writing.
Same hardware, three packaging options
No changes to public hardware parameters such as E2 / E6 camera channel count, synchronization method, or weight. Enterprise buyers select a bundled tier based on their own ingestion pipeline; the sensor content is identical in origin — the differences lie in directory structure, encoding conventions, and container format.
A · In stock by default
Episode raw footage package
Native frame-rate video, IMU (by SKU), time synchronization and calibration fields. Suitable for rapid evaluation and hourly ordering in the marketplace. Missing columns are left blank; no fake values are written.
B · Enterprise Training
List + encoding conventions
Building on A, the SOW specifies encoding (e.g., on-device H.265), bitrate/GOP strategy, stream name and clock domain list, and task/scenario metadata fields. Hardware parameters remain unchanged.
C · Pipeline integration
Robot-native container
The same sensor stream can be exported, as contractually agreed, into ROS2 / MCAP or other buyer-specified containers, with transforms and calibration included. Enterprise-tier defaults are negotiable; the written topic / field list is authoritative, and no verbal commitments beyond specification will be made.
Delivery method
Direct object storage delivery
Complete deliverables are delivered to your storage bucket or TOBI relay. Pipeline control stays with you; we provide the manifest.
Episode catalog
Episode directory structure with a meta/info.json-style manifest (schema confirmed with the project), ready for immediate training upon opening. Corresponds to packaging methods A/B above.
Robot-native container
Corresponds to packaging method C: after specifying topics / fields in the SOW, align video, calibration, coordinate transforms, and labels for export to ROS2/MCAP. Hardware parameters remain unchanged; only the packaging changes.
Recording specifications (E6 preliminary v0.1)
| Field | Expectation |
|---|---|
| Camera | E6: 4× grayscale GS (with infrared) + 2× RGB (rolling/global shutter versions). E2: 2 RGB global-shutter cameras at 1600×1200@30fps, per-camera HFOV 139° / VFOV 111°, IMU 800Hz, stereo baseline 65mm. E8: subject to the written engineering specifications. |
| Time synchronization | E6 head-mounted microsecond-level hard sync; wrist PPS+UART; other links must specify the soft-sync budget. |
| IMU / Pose | Specify the IMU rate and on-device SLAM/gestures (E6) or offline reconstruction (E2) per SKU; silent defaults are prohibited. |
| Calibration | Devices ship with calibration records keyed by serial number; intrinsic and extrinsic parameters are exported within the data package scope. |
| Encoding | Codec confirmed per project (e.g., H.265 on this device). The list specifies stream names and clock domains. |
| QA rejection criteria | Examples: severe synchronization loss, severe hand occlusion when a wrist is required, missing calibration, corrupted timestamps. |
This page is for evaluation only. Specifications, versions, test conditions, pricing, and supply are subject to the written document confirmed by both parties; R&D-stage targets do not constitute a supply commitment.