Record MAVLink telemetry in a `.tlog` file
This is generally expected functionality for control station software, and provides some data security in the case of a lost vehicle.
Not sure how hard it is to continuously write to a file from a web-app, but hopefully it’s possible and not too problematic.
We don't have access to the raw MAVLink messages right now, so we would have to save a JSON file with messages coming from mavlink2rest and them parse them to raw messages.
I suggested patrick that we add support for saving and downloading .tlog files in mavlink2rest itself, as it would be relatively easy and would provide this feature universally to others using it. Issue opened here.
The priority is recording the input and output data in some form, even if that means we have to create a custom format/parser for it (.tlog just happens to be how it's done currently in other control station softwares, so could be nice for user familiarity).
#546 will likely help with this.
@patrickelectric would the embedded mavlink2rest be able to generate a tlog file?
It's doable, but not in my priority list
It's doable, but not in my priority list
Yup, agree.
Just a reminder that mavlink-server has the code
Just a reminder that mavlink-server has the code
the point that we are, probably, talking is that mavlink2rest, as we are currently using as a webasm solution for the serial/tcp/udp port to transcode raw mavlink to mavlink2rest structures can also be used to do the other way around, from mavlink2rest structures to raw mavlink.