Version 3.0.16

This release:

• Adds a new NAV-SAT example
• Adds the definition for lastCorrectionAge in NAV-PVT flags3
• Updates the Dead Reckoning Example4 to clarify that ESF-ALG reports the alignment of the IMU within the vehicle - not the attitude of the vehicle itself

Version 3.0.15

This release:

• Corrects issue #27
  • pushRawData was attempting to write too much data in one go, when using Serial
  • The solution is to split each push into smaller chunks (if needed) and to call checkUbloxSerial between chunks (to prevent possible data loss during large pushes)
  • Tested with the new Example17_NTRIPClient_With_GGA_Callback__Serial and AssistNow Example4

Version 3.0.14

This release:

• Adds new methods getUniqueChipId and getUniqueChipIdStr to read the unique chip ID from (e.g.) F9, M9 and M10 modules
  • Please see the updated Example8 for more details
  • The ID is five bytes on the F9/M9, and six bytes on the M10. The string returned by the helper method will be ten or twelve Hex characters depending on the module type

Version 3.0.13

This release:

• Adds an additional (missing) compiler guard - to prevent the RTCM-logging functions from being compiled on Uno platforms
  • Uno does not have enough RAM for RTCM logging...

Version 3.0.12

This release:

• Adds callbacks for RTCM 1005 and 1006 Input - parsed from pushRawData
  • Example callbacks are here in Example17
  • The callbacks are configured here in Example17

Version 3.0.11

This release:

• Adds parsing of RTCM 1005 and 1006 from any data pushed to module with pushRawData
  • This allows you to extract the Antenna Reference Position of your NTRIP correction source
  • Please see these lines in the updated Example17 for more details

Version 3.0.10

This release:

• Adds "auto" support for RTCM 1005 - allowing you to monitor the Antenna Reference Position in ECEF coordinates
  • Please see the new ZED_F9P Example24 and Example25 for more details

Version 3.0.9

This release:

• Adds full auto support for MON HW
  • We are using the MON HW callback to monitor the antenna aStatus for short and open circuit
  • You need to enable the antenna short and open detection first using: setVal8(UBLOX_CFG_HW_ANT_CFG_SHORTDET, 1) and setVal8(UBLOX_CFG_HW_ANT_CFG_OPENDET, 1)

Version 3.0.8

This release:

• Adds a dedicated buffer for RTCM messages
  • If the GNSS is connected via SPI, you can not use processRTCM to pass the incoming RTCM characters to another SPI device (e.g. Ethernet) as checkUblox could still be part way through a multi-byte SPI transaction
  • The solution is to create a buffer for RTCM messages using setRTCMBufferSize. Any RTCM messages processed by the library will be placed into the RTCM buffer if enough space is available
  • Only whole, checksum-checked messages are added. You don't need to perform any additional checksum-checking on the data you read from the buffer. You can push it straight to your NTRIP Server
  • rtcmBufferAvailable returns the number of bytes waiting in the buffer. extractRTCMBufferData extracts bytes
  • You can clear the buffer with clearRTCMBuffer and check its size (capacity) with getRTCMBufferSize

Version 3.0.7

This release:

• Adds the configuration keys for NAV2-EELL and NAV2-PVAT
• Enhances the auto-send part of addCfgValsetN
  • addCfgValsetN will return false if the auto-send sendCommand fails
• Updates the examples to use the template version of addCfgValset
• Adds a firmware version warning to the examples which use SPARTN correction data
  • SPARTN is only supported on the ZED-F9P from HPG 1.30 onwards, and on the ZED-F9R from HPS 1.21 onwards
• Updates the examples so that ebno is printed in dB