🔨 tlogsmith

Forge synthetic MAVLink .tlog files from raw message definitions.

Pick messages from the anvil (the ardupilotmega.xml message set), shape their fields, order the sequence, and hammer out a .tlog ready for replay testing.

Quickstart

python3 -m venv .venv && .venv/bin/pip install -r requirements.txt
.venv/bin/python app.py

Open http://localhost:5000.

At the forge

• Browse the stockpile — search 319 message types from ardupilotmega (with all includes)
• Shape each piece — set field values, enum dropdowns resolve automatically
• Stamp the header — default sys_id/comp_id/interval, override per message
• Reorder the sequence — drag to arrange
• Hammer it out — download as .tlog
• Melt down existing work — open a .tlog to inspect and rework it

What goes in, what comes out

In: MAVLink XML definitions (mav_messages/, matching rust-mavlink 0.17.1 ardupilotmega dialect)

Out: Binary .tlog files — timestamped MAVLink v2 frames, ready for mavlogdump.py or any MAVLink replay tool