This issue will track the integration of new u-blox GNSS generations like the MAX-M8.
I disabled NAV-SVINFO and MAX-M8 seems to work fine now. There's still some work to do because one msg format (MON_HW) has changed substantially vs. the xxx-6 systems and I'd like to automatically adjust for the type of GNSS connected. Problem is that there doesn't seem to be a straight & simple way to read the GNSS protocol version: MON-VER returns an arbitrary number of long and undocumented ASCII strings. To account for the differences in the MON-HW format, I will probably just look at the the msg length (68 = u-blox-6, 60 = u-blox 7 and up).
This issue will track the integration of new u-blox GNSS generations like the MAX-M8.
I disabled NAV-SVINFO and MAX-M8 seems to work fine now. There's still some work to do because one msg format (MON_HW) has changed substantially vs. the xxx-6 systems and I'd like to automatically adjust for the type of GNSS connected. Problem is that there doesn't seem to be a straight & simple way to read the GNSS protocol version: MON-VER returns an arbitrary number of long and undocumented ASCII strings. To account for the differences in the MON-HW format, I will probably just look at the the msg length (68 = u-blox-6, 60 = u-blox 7 and up).