Open
Description
On ZED-based hardware, the code uses the u-blox GNSS library to store the RTCM 1005 / 1006 ARP using setRTCM1005InputcallbackPtr
and setRTCM1006InputcallbackPtr
If I'm reading the code right, we would lose this functionality on non-ZED platforms that support logging
Should we parse incoming RTCM centrally, using the semp, and update the ARP there?
Follow newARPAvailable
and settings.enableARPLogging
for the links
Metadata
Metadata
Assignees
Labels
No labels