Configuration Files

Our standalone boards are shipped with the default ZED-F9P configuration.

For the Starter Kits which contain a base, a rover or a heading unit, we have prepared special configuration files to make it more plug and play. You will find below:

  • An explanation of how each configuration file was built.
  • A link to download the configuration file, in case you have changed the configuration and you would like to go back to the original setup sent to you.
All files are available in our GitHub: https://github.com/ardusimple
We still use the “old” configuration file format, therefore make sure you use the following screen and buttons to upload the files.
u-center with Menu Bar > Tools > GNSS Configuration… (“Receiver Configuration” in latest u-center version)
Remember to select the checkbox of store in non-volatile memory, so configuration files are stored at next power-up
 
If you are asked the following question:
  • If both versions are the same (e.g. 1.12), then click yes.
  • If both versions are different (e.g. one is 1.12 and the other one is 1.11), you need first to update to the latest firmware.
NOTE: when loading configuration files to simpleRTK2Blite module, you are using UART1 (via USB with a UART-to-USB converter). The configuration files might change the baudrate you had before, leading to a loss of communication in the middle of the configuration file update. When this happens, just change the baudrate of u-center and load again the configuration file at the new baudrate.

Filename: “srtk2b_base_FW_HPG112.txt”

Starting from a default ZED-F9P configuration:

  • Enabled survey-in with target accuracy 2.5m (should take no more than 5-10min)
  • Changed UART2 baudrate to 115kbps (this improves the buffer use of the radio links)
  • Activated following RTCM messages
    • 1005: Stationary RTK reference station ARP
    • 1074: GPS MSM4
    • 1084: GLONASS MSM4
    • 1094: GALILEO MSM4
    • 1124: Beidou MSM4
    • 1230: GLONASS code-phase

We have selected this combination of messages because it’s a good tradeoff between performance and required data link:

  • Performance can be improved by using MSM7 messages
  • RF Bandwidth can be improved by eliminated some constellations (e.g. remove Galileo), or increase 1005 to only be sent once every 5 seconds.

Filename: “srtk2b_rover_FW_HPG112.txt”

Starting from a default ZED-F9P configuration:

  • Changed UART2 baudrate to 115kbps (this improves the buffer use of the radio links)

Filename: “srtk2b_rover_sends_back_GGA_to_base_FW_HPG112.txt”

Starting from a default ZED-F9P configuration:

  • Changed UART2 baudrate to 115kbps (this improves the buffer use of the radio links)
  • Disable all NMEA messages except GGA on UART2.
  • Enable NMEA output on UART2.

Filename: “srtk2b+heading_lite_movingbase_FW_HPG112.txt”

Starting from a default ZED-F9P configuration:

  • UART1 and UART2 increased to 115kbps
  • Activated following RTCM messages on UART1, which is connected from the simpleRTK2Blite to the UART2 of simpleRTK2B:
    • 1077: GPS MSM7
    • 1087: GLONASS MSM7
    • 1097: GALILEO MSM7
    • 1127: Beidou MSM7
    • 1230: GLONASS code-phase
    • 4072.0: Reference station PVT (u-blox proprietary RTCM Message)
    • 4072.1: Additional reference station information (u-blox proprietary RTCM Message)

Filename: “srtk2b+heading_rover_F9P_FW_HPG112.txt”

Starting from a default ZED-F9P configuration:

  • UART1 and UART2 increased to 115kbps
  • Disable NMEA messages in all interfaces, to avoid buffer overflow
  • Enabled on both UART1 and USB:
    • UBX-NAV-RELPOSNED
    • UBX-NAV-PVT

Filename: “srtk2b_bluetooth_FW_HPG112.txt”

Starting from a default ZED-F9P configuration:

  • UART2 activate NMEA output via UBX-CFG-PRT

Filename: “srtk2b_bluetooth_FW_HPG112-v2.txt”

Starting from a default ZED-F9P configuration:

  • UART2 activate NMEA output via UBX-CFG-PRT
  • Activate GST NMEA message to receive position accuracies
  • Enable extra decimal in NMEA strings for higher resolution