Increase Bluetooth SPP RX buffer

Note: Release candidate binaries have additional debug messages turned on. Don't be alarmed if you see lots of additional serial output.

Note: If you are running firmware v3.x or greater, you can load the latest firmware or release candidate over the air. If you are using older firmware (2.x or lower) you will need to load v3.x firmware using a USB connection. We have created a Windows GUI to ease this process. Please see Updating Firmware from GUI for a step by step process.

Changes in this release:

• Feature - Allow dynamic allocation of Bluetooth SPP buffers. See issue #469.

Fix logging corruption during BT NTRIP

Note: If you are running firmware v3.x or greater, you can load the latest firmware or release candidate over the air. If you are using older firmware (2.x or lower) you will need to load v3.x firmware using a USB connection. We have created a Windows GUI to ease this process. Please see Updating Firmware from GUI for a step by step process.

Changes in this release:

• Bug #469 - Fix NMEA/UBX data corruptions and multiple log creation when sending RTCM over Bluetooth SPP
• Bug #459 - Detect and remove corrupt L-Band certificates
• Bug #469 - Send RTCM over I2C instead of UART to reduce corruption
• Bug #498 - Won't compile without Bluetooth
• Bug - Fix NTRIP restart over Ethernet
• Feature #483 - Suppress debug messages
• Feature - Move UART and BT task priorities and interrupt core assignments to NVM

Fix multiple logs during BT NTRIP

Note: Release candidate binaries have additional debug messages turned on. Don't be alarmed if you see lots of additional serial output.

Note: If you are running firmware v3.x or greater, you can load the latest firmware or release candidate over the air. If you are using older firmware (2.x or lower) you will need to load v3.x firmware using a USB connection. We have created a Windows GUI to ease this process. Please see Updating Firmware from GUI for a step by step process.

Changes in this release:

• Bug #469 - Fix NMEA/UBX data corruptions and multiple log creation when sending RTCM over Bluetooth SPP

Fix MQTT for L-Band. Add MDNS. Add new coordinate type.

Note: If you are running firmware v3.x or greater, you can load the latest firmware or release candidate over the air. If you are using older firmware (2.x or lower) you will need to load v3.x firmware using a USB connection. We have created a Windows GUI to ease this process. Please see Updating Firmware from GUI for a step by step process.

Changes in this release:

• Expand support for RTK Reference Station hardware (Ethernet, SPI, SD_MMC, etc).
• Bug #459 - Fix failed MQTT connections when getting L-Band key updates.
• Bug #458 - Allow coordinate formats DDMMSS, DD MM SS, and DD-MM-SS (no decimals).
• Bug #473 - Fix common coordinate entry in Config page
• Bug #462 - Detect battery levels outside of limits.
• Bug #474 - Prevent external device from causing I2C failures at boot.
• Bug - Fix naming of reused log to avoid filename 'SFE'.
• Bug - Fix alignment of RTCM message rates during Base mode.
• Bug #443 - Fix RTCM generation due to NAV2 system being enabled.
• Feature #476 - Show ZED-F9x unique ID in system menu and log
• Feature #453 - Add MDNS. Once enabled, device is accessible from 'rtk.local' as opposed to an IP address that may change.
• Feature #458 - Add decimal-less coordinate entry (DDMMSS, DD-MM-SS, and DD MM SS).
• Feature #475 - Disable RTK L-Band auto-reset

Support new commands and messages. Fix L-Band RTK Fix bug.

Note: If you are running firmware v3.x or greater, you can load the latest firmware over the air. If you are using older firmware (2.x or lower) you will need to load v3.x firmware using a USB connection. We have created a Windows GUI to ease this process. Please see Updating Firmware from GUI for a step by step process.

Changes in this release:

• (Bug #455) - Fix GNSS library upstream bug causing Facet L-Band to fail to RTK Fix
• (Bug #454 and #435) - Give up Facet L-Band key retrieval if WiFi not available
• (Bug #424) - Add discrete command and message support for all platforms (F9P vs F9R) and messages (Ex: NAV2 supported after v130 of F9P). This allows a any given ZED-F9P/F9R configuration command to be used/allowed depending on the platform and the firmware running on the ZED-F9x.
• (Bug #445) - Remove Bike dynamic model from platforms that do not support it.
• (Bug #434) - Prevent panic if SD card is being written to while in config menu.
• (Bug #430) - Fix battery icon on WiFi config page.
• (Bug #400) - Fix 0 SIV with 3D Fix.
• (Feature #428) - Allow input of coordinates in multiple formats such as DDMM.mmmm, DDMMSS.ssss, DD-MM-SS.ssss, etc
• (Feature #422) - Add discrete RTCM message rates for Base mode.
• (Feature #423) - Add Mower and E-Scooter dynamic models for ZED-F9R (Express Plus only) hardware with HPG 1.21 and above
• (Feature #441) - During factory reset, warn that the profile config is the only thing that's getting erased.
• (Feature #440) - Write date to log file via custom NMEA message
• (Feature #436) - Show new NGS certified ARP values for RTK Facet in tool tips.
• (Feature #425) - Allow minimum C/N0 for satellite signal to be included in fix calculation.
• (Feature #395) - Allow minimum elevation for satellites to be included in fix calculation.
• Facet L-Band: Properly handle expired keys
• Add support for new messages including NAV2 (navigation solutions without RTK corrections applied). The number of supported messages has risen from 74 to 120. These messages are now auto-generated on the WiFi config page.
• Re-enable debug output for RC binaries

Add MDNS. Add Ethernet.

Note: Release candidate binaries have additional debug messages turned on. Don't be alarmed if you see lots of additional serial output.

Note: If you are running firmware v3.x or greater, you can load the latest firmware or release candidate over the air. If you are using older firmware (2.x or lower) you will need to load v3.x firmware using a USB connection. We have created a Windows GUI to ease this process. Please see Updating Firmware from GUI for a step by step process.

Changes in this release:

• Expand support for RTK Reference Station hardware (Ethernet, SPI, SD_MMC, etc).
• Bug #459 - Fix failed MQTT connections when getting L-Band key updates.
• Bug #458 - Allow coordinate formats DDMMSS, DD MM SS, and DD-MM-SS (no decimals).
• Bug #473 - Fix common coordinate entry in Config page
• Bug #462 - Detect battery levels outside of limits.
• Bug - Fix naming of reused log to avoid filename 'SFE'.
• Bug - Fix alignment of RTCM message rates during Base mode.
• Bug #443 - Fix RTCM generation due to NAV2 system being enabled.
• Feature #476 - Show ZED-F9x unique ID in system menu and log
• Feature #453 - Add MDNS. Once enabled, device is accessible from 'rtk.local' as opposed to an IP address that may change.
• Feature #458 - Add decimal-less coordinate entry (DDMMSS, DD-MM-SS, and DD MM SS).
• Feature #475 - Disable RTK L-Band auto-reset

Adjust RTCM During Base. Add dynamic models.

Note: Release candidate binaries have additional debug messages turned on. Don't be alarmed if you see lots of additional serial output.

Note: If you are running firmware v3.x or greater, you can load the latest firmware or release candidate over the air. If you are using older firmware (2.x or lower) you will need to load v3.x firmware using a USB connection. We have created a Windows GUI to ease this process. Please see Updating Firmware from GUI for a step by step process.

Changes in this release:

• (Bug #455) - Fix GNSS library upstream bug causing Facet L-Band to fail to RTK Fix
• (Bug #454 and #435) - Give up Facet L-Band key retrieval if WiFi not available
• (Bug #424) - Add discrete command and message support for all platforms (F9P vs F9R) and messages (Ex: NAV2 supported after v130 of F9P). This allows a any given ZED-F9P/F9R configuration command to be used/allowed depending on the platform and the firmware running on the ZED-F9x.
• (Bug #445) - Remove Bike dynamic model from platforms that do not support it.
• (Bug #434) - Prevent panic if SD card is being written to while in config menu.
• (Bug #430) - Fix battery icon on WiFi config page.
• (Bug #400) - Fix 0 SIV with 3D Fix.
• (Feature #428) - Allow input of coordinates in multiple formats such as DDMM.mmmm, DDMMSS.ssss, DD-MM-SS.ssss, etc
• (Feature #422) - Add discrete RTCM message rates for Base mode.
• (Feature #423) - Add Mower and E-Scooter dynamic models for ZED-F9R (Express Plus only) hardware with HPG 1.21 and above
• (Feature #441) - During factory reset, warn that the profile config is the only thing that's getting erased.
• (Feature #440) - Write date to log file via custom NMEA message
• (Feature #436) - Show new NGS certified ARP values for RTK Facet in tool tips.
• (Feature #425) - Allow minimum C/N0 for satellite signal to be included in fix calculation.
• (Feature #395) - Allow minimum elevation for satellites to be included in fix calculation.
• Facet L-Band: Properly handle expired keys
• Add support for new messages including NAV2 (navigation solutions without RTK corrections applied). The number of supported messages has risen from 74 to 120. These messages are now auto-generated on the WiFi config page.
• Re-enable debug output for RC binaries

Fix Profile Switching via WiFi Config. Add SDMMC.

Note: If you are running firmware v3.x or greater, you can load the latest firmware over the air. If you are using older firmware (2.x or lower) you will need to load v3.x firmware using a USB connection. We have created a Windows GUI to ease this process. Please see Updating Firmware from GUI for a step by step process.

Changes in this release:

• (Bug #382) - Fix unit reset when change profiles in WiFi Config mode
• (Bug #415) - Fix logging icon
• (Bug #401) - Correctly start new log from WiFi Config button and exiting WiFi Config
• (Feature #391) - Add delete confirm when removing common coordinates
• (Feature #418) - Add ability to calculate HAE based on Mark or Antenna characteristics
• Move to GNSS library v3
• Add support for SDMMC on compatible hardware
• Show bubble menu based on presence of accelerometer
• Determine developer mode based on workflow branch

Fix Profile Switching via WiFi Config.

Note: Release candidate binaries have additional debug messages turned on. Don't be alarmed if you see lots of additional serial output.

Note: If you are running firmware v3.x or greater, you can load the latest firmware or release candidate over the air. If you are using older firmware (2.x or lower) you will need to load v3.x firmware using a USB connection. We have created a Windows GUI to ease this process. Please see Updating Firmware from GUI for a step by step process.

Changes in this release:

• (Bug #382) - Fix unit reset when change profiles in WiFi Config mode
• (Bug #415) - Fix logging icon
• (Bug #401) - Correctly start new log from WiFi Config button and exiting WiFi Config
• (Feature #391) - Add delete confirm when removing common coordinates
• Show bubble menu based on presence of accelerometer

Fix BLE. Fix OTA check. Add NTRIP during Survey In.

Note: Release candidate binaries have additional debug messages turned on. Don't be alarmed if you see lots of additional serial output.

Note: If you are running firmware v3.x or greater, you can load the latest firmware or release candidate over the air. If you are using older firmware (2.x or lower) you will need to load v3.x firmware using a USB connection. We have created a Windows GUI to ease this process. Please see Updating Firmware from GUI for a step by step process.

Changes in this release:

• (Bug #387) - Fix reboots caused by BLE NMEA streaming
• (Bug) - Fix firmware OTA fail from Firmware Menu when Bluetooth is enabled.
• (Bug #386) - Allow NTRIP Client to run during Survey-In for Assisted Survey-In
• (Bug #377) - Allow negative antenna heights
• (Bug #384) - Print file list over Bluetooth from System menu
• (Feature #385) - Show HAE APC in serial menu
• (Feature #381) - Add confirmation to file delete from AP Config page