@ne0fhyk I've run into a problem which seems to be related to mavlink/mavlink@88c648e where the upper nibble of uint32's are parsed incorrectly (ie onboard_control_sensors_health in sys_status). Before the parsing code changed to this version it worked but after the change it stopped interpreting the upper nibble correctly. Do you have any idea why these changes could have broken it/why were they needed?
@WickedShell the test should attempt to validate the parsing.. could you take a look and see which part it's missing. We can use that to isolate which part of the parsing code is not working as expected.
@ne0fhyk Yeah I'm doing a quick bisection to verify that is the exact commit thats causing me problems, (it is the major commit between the dates I updated my jars) but I do need to show exactly which it is