4.1 log format changed

[EosBandi]

Log messages not contains Instance field and store data from multiple instances in the same message id.
For example XKF1 now contains log from all EKF lanes...

[khancyr]

Hello,
I will look at that but normally the parsing is done with the information from the message type itself, so if the definition is done correctly the parsing should be correct too.

[Georacer]

It's not an issue on the parser itself. But recently the following messages have added an "instance" field that refers to different instances/core relaying the same fields but referring to different variables. But since they all write to the same topic the automated decoder dumps them all in the same topic, making it hard to visualize and use.

Here's what I did for the issue in Ardupilog: Georacer/ardupilog@46e1584

[EosBandi]

Indeed, but even ardupilog is outdated at the moment, since now IMU, MAG, GPS and other sensor messages are having instance field as well. (Make it worst, the field name is not C but with sensors)

[EosBandi]

From UAVLogViewer, it seems that a '#' unit type indicates instance, so you can automate detecting "instanced" messages....
https://github.com/ArduPilot/UAVLogViewer/blob/d09775cfc392b285d1244e2c8e16f935c194f2f6/src/tools/parsers/dataflashParser.js#L142
But have to process FMTU messages as well.

[Georacer]

Indeed, but even ardupilog is outdated at the moment, since now IMU, MAG, GPS and other sensor messages are having instance field as well. (Make it worst, the field name is not C but with sensors)

There was a feature branch that addressed this, I just merged it to master.

[Georacer]

From UAVLogViewer, it seems that a '#' unit type indicates instance, so you can automate detecting "instanced" messages....
https://github.com/ArduPilot/UAVLogViewer/blob/d09775cfc392b285d1244e2c8e16f935c194f2f6/src/tools/parsers/dataflashParser.js#L142
But have to process FMTU messages as well.

I didn't know this. Good info, thanks!