Integrations

Supported log formats

Read your robot logs as they are

Upload your robot logs in the formats your stack produces, and the agent reads them as they are. You do not write a converter before the agent can help.

What to use it for

  • Upload MCAP, ROS 1 bags and common flight-log formats as a mission. Alloy converts them for you.
  • Investigate a mixed folder of logs from one run in a single mission.
  • Filter and plot any decoded field without a custom parser.
  • Attach CSV, spreadsheets, GNSS files and documents in the chat for analysis.

Example

Fictional example.

A VTOL team uploads one folder per flight: an ArduPilot .BIN, a MAVLink .tlog with a custom dialect, a ROS 2 .mcap from the companion computer, and metadata.json. Alloy reads them as one mission, so the agent can line up the flight controller and the companion computer on one timeline.

How to use it

Upload a folder as a mission, or attach other files in the chat. Each route into Alloy accepts a different set of formats:

Supported formats

FormatFile typesAgent Platform: upload, S3, GCSMesh Storage: web upload, Alloy EdgeAttach in chat
MCAP.mcapYesYesNot as a mission (upload it)
ROS 2 (MCAP storage, the default since ROS 2 Iron).mcapYesYesNot as a mission
ROS 2 (SQLite storage).db3Convert to MCAP firstConvert to MCAP firstNot as a mission
ROS 1 bag.bagYes, converted to MCAPConvert to MCAP firstNot as a mission
ArduPilot DataFlash.binYes, converted to MCAPConvert to MCAP firstNot as a mission
MAVLink telemetry.tlog, plus optional dialect .xmlYes, converted to MCAPConvert to MCAP firstNot as a mission
PX4 ULog.ulg, .ulogYes, converted to MCAPConvert to MCAP firstNot as a mission
Metadata sidecars.json, .yml, .yamlYesYesYes
CSV, JSON, text.csv, .json, .txtTalk to usNoYes, analysed in the chat
Parquet, Excel.parquet, .xlsxTalk to usNoYes, read with Python in the chat
GNSSRINEX (.rnx, .26O), RTCM3 (.rtcm3), Septentrio SBF (.sbf)Talk to usNoYes, analysed in the chat
Documents and archives.pdf, .docx, .zipNoNoYes

On this page