Skip to main content

Data streams

This section is for engineers who want to work with EGO1 data directly in Python. It uses the command line. If you just want to capture and review recordings, the operator guide has everything you need.

Overview

EGO1 records in MCAP — a self-describing, open format with message schemas embedded in the file. Messages are protobuf-encoded, and the data can be parsed with the open-source visio-schema Python package.

The same data is reachable over two channels:

ChannelFormUse
TCP (Wi-Fi)192.168.4.1:50001 over the device's Wi-Fi hotspotLive stream over the hotspot
File (MCAP)The .mcap files on the MicroSD cardOffline analysis

Device / hotspot name: GILABS-XXXXXX (last 6 characters of the serial).

USB is power only today

USB-C is currently power only — live access is over Wi-Fi (TCP) and recorded files come off the MicroSD card. USB data transfer is coming in an upcoming release.

Channels recorded

A recording multiplexes the topics below. Schemas are protobuf, embedded in the MCAP file. In a typical session the two cameras run at ~30 fps and the fused IMU quaternion at ~200 Hz.

TopicSchemaContents
/ego/camera/0foxglove.CompressedVideoCamera 0 video (H.265), stereo pair
/ego/camera/1foxglove.CompressedVideoCamera 1 video (H.265), stereo pair
/ego/imu/0/rawvisio_schema.v1.sensor.ImuRawRaw IMU samples (batched)
/ego/imu/0/quatvisio_schema.v1.ros.geometry_msgs.QuaternionFused orientation quaternion
/ego/system_healthvisio_schema.v1.sensor.SystemHealthDevice health (CPU / disk / clients)
/ego/command_resultvisio_schema.v1.control.CommandResultResult of a control command
/device_infovisio_schema.v1.service.device_info.DeviceInfoDevice identifiers / info

See the channel & network reference for the full quick-reference tables.

Next