Hi all. I am making software for the ground control and telemetry, which will be adapted for my flight platform. As the next automatic pilot will be Ardupilot Mega, I want to make the telemetry log to be compatible with the Ardu Mission Planner. The problem is what I cannot find any explicit documentation about the Ardu Mission Planner output files. As I understand, there are two type of files: *.tlog and *.log.
The *.log file is the ASCII text file downloaded from the hardware unit. It is "intuitive understandable" and has some documentation here (maybe in few days I could implement this protocol form in my solution), but my solution save the telemetry data stream, so maybe more interesting could be use the form of the *.tlog file, which is the telemetry stream too, but I cannot find any documentation about it fields meaning. I can not download any "official" *.tlog file. Some files comes with Mission Planner, so I can assume that *.tlog is a binary file contained literally all stream of telemetry communication (the same idea in my software). As binary file the *.tlog is not very readable by humans and data programs, but it is not a problem to write a converter (or, maybe, somebody have writtent one from *.tlog to *.log?). So the main question is: How to interpret (byte by byte) the *.tlog file?
It's a binary dump of timestamped mavlink packets
Yes this page I am investigating about a week. May be I have not enough experience in how to get useful information in this form, but the only thing I have understand, that mavlink generates messages divided by some titles, the messages are binary and can contain anything (explained in title). By this time I have not find no title explication, nor the byte coding of the message (for example "the byte 1 and 2 of the message are the latitude degrees").
By the way, the Qgroundcontrol software cannot read *.tlog file correctly.
Any luck with this lately?