Repository navigation
Conversation
Port of mavlink#147 to 0.x-dev. Adds --tlog <FILE>: every message received from the vehicle is written to a .tlog file (8 byte big-endian microsecond timestamp before each frame, the format QGroundControl and MAVProxy read), appending to an existing file. GET /v1/tlog flushes and downloads it while the service runs. Without --tlog nothing changes and the endpoint returns 404.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Port of #147 to
0.x-dev, so it can go into a 0.11.x release. BlueOS pins 0.11.28 (core/tools/mavlink2rest/bootstrap.sh).Same behavior as #147:
--tlog <FILE>records every message received from the vehicle to a .tlog file (8 byte big-endian microsecond timestamp before each frame, the format QGroundControl, Mission Planner and MAVProxy read), appending to an existing fileGET /v1/tlogflushes and downloads it while the service runs--tlognothing changes and the endpoint returns 404Differences from the master version, forced by mavlink 0.10.14 on this branch:
mavlink::ardupilotmegainstead ofmavlink::dialects::ardupilotmegamavlink::read_versioned_msg(0.10 has noMavlinkReader), and wraps the commonHEARTBEATin the ardupilotmega message typeTested on Linux (Ubuntu 24.04, rustc 1.99.1):
And against a running service:
mavlink2rest -c udpin:127.0.0.1:14551 --tlog /tmp/t.tlog, five MAVLink 2 HEARTBEAT frames sent over UDP, thenGET /v1/tlogreturned 200application/octet-streamwith the five timestamped frames, and/v1/mavlink/vehicles/1/components/1/messages/HEARTBEATshowed the same message. Without--tlog,GET /v1/tlogreturned 404 with the hint text.Asked for by @rafaellehmkuhl on #147.