Re: [Paparazzi-devel] Openlog flight logs not compatible with Paparazzi v5.2

[Joseph Muhlhausen]

Hi Felix,

Thanks for the quick response and the explanation, I was wondering what had changed in the code since getopenlog seemed to work exactly the same way. I will checkout v5.0 to convert v5.0 logs in the future.

Best,

Joseph

On Sun, Oct 19, 2014 at 2:47 PM, Felix Ruess <address@hidden> wrote:

Hi Joseph,

in v5.2 the NAVIGATION_REF message got an extra field: "ground_alt" and in your log file the message does not have this field.
Since the openlog and sdlog code assumes that the log files were created with the messages defined in conf/messages.xml (to produce the paparazzi .log and .data file), it fails...

I think there are only two options/workarounds:

- use v5.0 to convert the log files to pprz .log and .data which you can then read in v5.2 as well

- temporarily checkout conf/messages.xml to the v5.0 version, run getopenlog, then revert back to proper v5.2 version

Hope that helps,

Felix

On Sun, Oct 19, 2014 at 5:54 PM, Joseph Muhlhausen <address@hidden> wrote:

I have openlog logs made on a Umarim lite running Paparazzi v5.0.1.

If I use the v5.0 branch I can convert the logs using the getopenlog command with no issues, but If I'm on the v5.2 branch I get an error message and no converted log file.

Here is the command I'm running:

sw/logalizer/getopenlog Logs/LOG*

The error code:

Fatal error: exception Failure("Pprz.values_of_payload, too many bytes in message NAVIGATION_REF: 01 09 de 1a 05 00 2a 75 42 00 12 ")

And I also attached a flight log if someone wants to try running getopenlog in v5.2.

Has there been any changes in the openlog2tlm code?

_______________________________________________
Paparazzi-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel

_______________________________________________
Paparazzi-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel