Wireshark Disscector Issue

[Michael Nunan]

I am testing a mavlink application that handles parameters.

I am looking at the wireshark decoding of a PARAM_REQUEST_READ message.

The dissector is missing the payload system_id, and component_id values (or more precisely, it is interpretting the first 2 characters of the PARAMETER NAME as the system_id, and Component_id, even though the corred values are in the message (2 bytes are being skipped in the disection).

Here is a screen capture.

The system_id and component_id are 1, 1 in the message, but are being skipped in the dissection.

Am I correct? Circled in red)

 

[Hamish Willee]

It looks like it. Can you test this with a fresh generated library for XML that matches the flight stack you are talking to. If it still happens, please create an issue in https://github.com/ArduPilot/pymavlink