@Georacer wrote:
Hello everyone,
I am doing some log diagnostics and am going through .bin and .tlog files. Currently I am relying on Mission Planner to generate cleartext but this is not the point.
The first part of a .bin file is the message format definitions, eg:
FMT, 128, 89, FMT, BBnNZ, Type,Length,Name,Format,Columns FMT, 129, 31, PARM, QNf, TimeUS,Name,Value FMT, 130, 50, GPS, QBIHBcLLeeEefB, TimeUS,Status,GMS,GWk,NSats,HDop,Lat,Lng,RAlt,Alt,Spd,GCrs,VZ,U FMT, 131, 50, GPS2, QBIHBcLLeeEefB, TimeUS,Status,GMS,GWk,NSats,HDop,Lat,Lng,RAlt,Alt,Spd,GCrs,VZ,U FMT, 195, 19, GPA, QCCCC, TimeUS,VDop,HAcc,VAcc,SAcc FMT, 196, 19, GPA2, QCCCC, TimeUS,VDop,HAcc,VAcc,SAcc FMT, 132, 49, IMU, QffffffIIfBB, TimeUS,GyrX,GyrY,GyrZ,AccX,AccY,AccZ,ErrG,ErrA,Temp,GyHlt,AcHlt FMT, 133, 75, MSG, QZ, TimeUS,Message FMT, 134, 39, RCIN, Qhhhhhhhhhhhhhh, TimeUS,C1,C2,C3,C4,C5,C6,C7,C8,C9,C10,C11,C12,C13,C14 FMT, 135, 35, RCOU, Qhhhhhhhhhhhh, TimeUS,Ch1,Ch2,Ch3,Ch4,Ch5,Ch6,Ch7,Ch8,Ch9,Ch10,Ch11,Ch12 FMT, 136, 15, RSSI, Qf, TimeUS,RXRSSIand other similar lines.
This is not MAVLink format, so far I can tell. What I am trying to understand is what this is and why it is what it is.
Is there documentation for this specification, or is there just the code?
Is it quasi-stable? How often does it change?
Is there a reasoning behind this specification? Why not just write the same telemetry MAVLink messages onto it?Thanks in advance!
Posts: 4
Participants: 2
