Version 3.1.2

This release:

• Makes the library compatible with Particle - thank you @niabassey #48

Version 3.1.1

This release:

• Corrects the NEO-F10N example (NEO-F10N is UART-only)
• Adds a new example for the NEO-F9P which shows how to enable GPS L5 and mark it as healthy
• Increases the size of MAX_PAYLOAD_SIZE and moduleSWVersion_t firmwareTypeLen to cope with the longer UBX-MON-VER and firmware type (e.g. SPGL1L5) returned by the NEO-F10N
• Updates parseSPARTN so it can return sfe_ublox_spartn_header_t if desired
• Corrects multiple (fixType == 4) errors in the examples - thank you @niabassey #46

Version 3.1.0

Merry Christmas!

This release:

• Adds additional examples showing how you can deliver PMP or parsed SPARTN correction data from a NEO-D9S to (e.g.) a ZED-F9P
  • See Example7, Example8 and Example9
• Adds new Configuration Interface keys for the NEO-F10N
• Adds a new example which shows how to enable L5 signals on the NEO-F10N
  • The example displays UBX-RXM-RAWX signal-strength data from the NEO-F10N
  • Note: the engineering sample of the NEO-F10N supports RAWX. Production modules may not...
  • The same example shows how to configure the Low Noise Amplifier on the NEO-F10N
• Adds additional code comments showing how to call the "Auto" message helper methods safely
• Adds better "Auto" support for UBX-RXM-SFRBX
  • Up to 14 SFRBX messages can now be buffered internally in the library and accessed via the callback
  • This is very useful for the PointPerfect Library which needs ephemeris data from SFRBX (or RTCM 1019, 1020, 1042, 1046)
• Adds better "Auto" support for UBX-ESF-MEAS
  • Up to 6 ESF-MEAS messages can now be buffered internally in the library and accessed via a callback
  • See the new example for more details
• Adds the method parseSPARTN
  • We were using this multiple times in the PMP examples. Integrating it into the library is the right thing to do...

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