https://toitlang.org/ logo
ubx-message parser/ublox-gnss-driver - improvemen...
# general
m
Reverse engineered what was going on with the ublox 6M and why it wasn't getting a fix. Anyone keen to give us a hand to test?
Improvements are really around making sure the driver/parser combination have whats necessary to respect the message definitons, eg, the improvements to the protocol for the M8+ don't work on the 6M. I've added a message type to the parser (from the manual) called "UBX-MON-VER" - produces enough to help us know what SW versions we have, even for the oldest models.
In order for the driver to make intelligent choices I'm thinking to add a small 'minimum version' hard coded entry to each of the message types' definitions.
Additionally - found that there was an error in the NAK handler in the parser, meaning that the NAKs the device was sending back during the driver init couldn't be picked up by the driver. Fine with an M8, but not with an 6M or 7M, haven't got a M8, M9 or M10 to mess with yet.