Version 2.2.6

This release:

• Updates Example18_PointPerfectClient to include the Client ID for the new encrypted PointPerfect service - thank you @mazgch
• Adds Example5_AssistNowOnline_MQTT to demonstrate how to receive AssistNow Online (MGA) data via secure MQTT connection
• Adds support for UBX-MON-HW2 (getHW2status)

Version 2.2.5

This release corrects the leap year calculation error in getUnixEpoch

• Please see issue #125 for details

Version 2.2.4

This release:

• Adds a fix to allow the auto-NMEA examples to compile on ATmega2560/1280
• Clarifies the memory usage
• Clarifies that the auto-NMEA examples will not work on Arduino Uno (ATmega328)

Version 2.2.3

This release:

• Adds full auto support for the RMC, VTG and ZDA NMEA messages - as requested in #120
• Adds support for the UBX-MON-HW and UBX-MON-RF messages, plus UBX-CFG-ITFM, allowing the jamming / interference status to be monitored - as suggested in #121
  • Please see the new Example29 for more details
• Please note: adding the above changes exceeded the program memory on the Arduino Uno (ATmega328) once again... To save memory and allow the library to compile, support for auto-NMEA is now automatically disabled on Uno platforms.

Version 2.2.2

This release:

• Allows the code to compile on AVR DA and DB (DxCore) hardware - based on #114 - thank you @nabelekt
• Adds the message class and IDs for the PUBX u-blox proprietary NMEA-format messages - based on #116 - thank you @nabelekt
• Adds support for survey-in durations longer than 65535 seconds
  • To maintain backward-compatibility and avoid ambiguity errors, the longer durations are accessed via new functions: setSurveyModeFull, enableSurveyModeFull and getSurveyInObservationTimeFull
  • Please see the updated Example3 for details
  • Based on #117 - thank you @russ396
  • Resolves this old issue :-)

Version 2.2.1

This release:

• Adds a new example showing how to request SPARTN correction data from u-blox's PointPerfect service using MQTT - thank you @mazgch
• Adds preliminary support for the UBX-RXM-PMP data provided by the NEO-D9S correction data receiver
• Adds preliminary support for UBX-RXM-SPARTNKEY, allowing the PMP SPARTN encryption keys to be passed to a ZED-F9x
• Adds a new example showing how PMP data provided by the NEO-D9S can be pushed to a ZED-F9x using callbacks - thank you @mazgch
• Corrects "auto" support for UBX-NAV-PVAT - see issue #97
• Corrects an error in the private extract functions - resolving issue #109
• Adds new setAuto...callbackPtr functions which allow the message callbacks to be passed a pointer to the UBX data, instead of a full copy of the data
  • This is much kinder on the stack and prevents some badness seen on Apollo3 / Artemis
  • Please see the modified callback examples for more details
• Adds setOutputPort as a way of outputting all UBX and NMEA data to a Serial port - thank you @mazgch

Version 2.2.0

This release:

• Adds full "auto" support for UBX-NAV-PVAT plus an example - see issue #97
• Adds a new how-to guide for adding support for new messages
• Adds "auto" support for NMEA messages GPGGA and GNGGA
  • This makes it easy to push your location to an NTRIP Caster
• Adds new functions:
  • setMainTalkerID - which changes GNGGA to GPGGA
  • setHighPrecisionMode - which adds extra decimal places to the GGA lat, lon and alt
  • setDGNSSConfiguration - which tells the module to use fixed or floating RTK (Differential) carrier solutions
• Adds new examples for "auto" NMEA
• Adds a new NTRIP Caster example showing how to use the GGA callback to full effect
• Adds the two new dynamic models (mower and e-scooter) supported by HPS 1.21 (UDR / ADR modules only)

Version 2.1.5

This release:

• Corrects a gremlin in pushAssistNowDataInternal - it wasn't using numDataBytes correctly when pushing offset or a sub-set of data.

Version 2.1.4

This release:

• Cleans up ZED-F9P/Example14 and adds ZED-F9P/Example16 (NTRIP Client with GGA)
  • ZED-F9P/Example16 tests good with RTK2Go, Emlid, and the Sachsen corrections caster
• Changes the way the .begin assumeSuccess parameter works
  • .begin will now return true if assumeSuccess is true and if _signsOfLife is also true
  • _signsOfLife is set true if any valid UBX packet or any valid NMEA header is received
  • This allows the user to be confident that the module is connected and communicating - even if the port is congested
  • (Port congestion on Serial is usually a sign that the baud rate is too low for the enabled messages and navigation rate)

Version 2.1.3

This release:

• Adds softwareResetGNSSOnly
• Includes maxWait and assumeSuccess as parameters for the three .begin functions
  • If you are using Serial and the port is already outputting messages at high rate, .begin can often fail
  • You can now either set maxWait to a large value (5000ms seems to work well) and wait for success
  • Or set maxWait to a small value (e.g. 100ms) and/or set assumeSuccess to true