[Feature Request] getting data from unimplemented packets

[saaaji]

I'm using this firmware version as my reference for polling the UBX-MON-SYS packet from a ublox zed f9p via a custom command, as it isn't currently implemented in the library. These would be useful to monitor current HW stats on the ublox in our operating environment. However, I'd prefer it to automatically send updates rather than poll it manually. Configuring this is easy enough by sending a custom CFG-VALSET command to set the rate of the MON-SYS message (e.g. to 1). This seems to succeed in configuring the zed f9p to send the packet, but as far as handling that packet when it arrives, there does not seem to be an easy way, either via checkUbloxI2C, or process, or processUBX, or processUBXpacket to actually store the incoming MON-SYS packets. It seems, that if autoLookup doesn't recognize a packet class or ID, then that packet is discarded rather than parsed completely, unless i'm misunderstanding how unimplemented UBX packets are handled. Subclassing doesn't seem very effective at adding new UBX packet types, as it seems none of the base class methods in SFE_UBLOX_GNSS have been marked as virtual. I'm wondering if there is any practical way to get these automatic MON-SYS packets, or any unimplemented auto packet for that matter.

[PaulZC]

Hi @saaaji ,

This library has grown into a monster - over the past 7 years or so. If we were starting again, we'd structure it very differently, with each UBX message type being handled by its own class. Each message would be processed within that class, instead of being processed by monsters like processUBXpacket.

The only way to add full "auto" support for MON-SYS would be to follow the notes here.

But, most of the bones of what you need already exist. The library can log any UBX message - even ones without "auto" support. enableUBXlogging allows any UBX message to be added to the internal fileBuffer. See DataLoggingExample9. It wouldn't be much extra work to adapt this so that the UBX data is passed to a virtual or weak function - in addition to or instead of being added to the fileBuffer.

In the interim, Example9 does most of what you need. Strip out the SD-write parts. Enable (UBX_CLASS_MON, UBX_MON_SYS) for logging. Keep checking fileBufferAvailable. When it's > 0, you have MON_SYS data which you can read using extractFileBufferData. You can read a byte at a time if you want to, or read all 24+8 bytes all in one go. MON-SYS is always 24+8 bytes. It's length is fixed.

Best wishes,
Paul

[PaulZC]

Hi @saaaji ,

I have added support for this in Release 3.1.11. Please see the Release Notes for details and the MON-SYS example.

Best wishes,
Paul

[saaaji]

Thanks - appreciated the quick turnaround!