Configuration Files - ArduSimple

COVID 19 update (01/10/2020): We keep shipping worldwide and we have plenty of stock of all our products. Read more.

Configuration Files

Our Starter Kits which contain a base, a rover or a heading unit, are shipped pre-configured to make your life more plug and play.

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

If you “revert to default” a simpleRTK2B board, note that it will revert to the u-blox ZED-F9P default, not to the ArduSimple default. For getting back to the ArduSimple default you will have to upload the configuration files in this page.

Firmware version check:

The first step is to check that you have the latest firmware version on your boards. As any new technology, new firmware with improvements are released on a regular basis, and it’s common that the hardware you just received doesn’t have the latest version.

Have a look at this tutorial to check your firmware version and update if necessary.

Loading a configuration file:

Download the Windows tool u-center: https://www.u-blox.com/en/product/u-center

Go to Menu Bar > Tools > “Receiver Configuration” (“GNSS Configuration…” in older u-center versions)
Select Generation “u-blox Generation 9”
Select the configuration file from your hard disk
Click “Transfer file -> GNSS”

When finished, the simpleRTK2B will start using the new configuration immediately. But if you remove the power, it will revert back to the previous one. To store permanently our new configuration, we need to:

Go to Menu Bar > View > Message View
Find the message UBX-CFG-CFG
Select “Save Current Configuration”
Click “Send”

NOTE for simpleRTK2Blite users: when loading configuration files to simpleRTK2Blite board, 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.

Configuration files:

Base

Filename simpleRTK2B_FW113_Base-00.txt

Starting from a default ZED-F9P configuration:

Enable survey-in with target accuracy 2.5m (should take no more than 5-10min)
Change UART2 baudrate to 115kbps. This improves the buffer use of the radio links.
Activate following RTCM messages
- 1005: Stationary RTK reference station ARP
- 1074: GPS MSM4
- 1084: GLONASS MSM4
- 1094: GALILEO 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 more constellations (e.g. remove Galileo), or increase 1005 to only be sent once every 5 seconds.

Rover

Filename simpleRTK2B_FW113_Rover_1Hz-00.txt

Starting from a default ZED-F9P configuration:

Change UART2 baudrate to 115kbps. This improves the buffer use of the radio links.
Disable SBAS, to avoid position jumps during short RTK corrections interruptions.
Disable Beidou, to make it simpler to increase navigation rate to 10Hz without troubles.

Rover sending back its position to the base

Filename simpleRTK2B_FW113_Rover_sends_GGA_to_base_1Hz-00.txt

Same as Rover plus:

Disable all NMEA messages except GGA on UART2.
Enable NMEA output on UART2.

MB (Moving Base) of a simpleRTK2B+heading kit

Filename simpleRTK2B_FW113_HeadingKit_MovingBase_1Hz-00.txt

This is the files that goes into the simpleRTK2Blite mounted on top of the simpleRTK2B in the kit. Note that depending on your previous configuration you might have to upload the configuration file twice, because in the middle of the configuration file there is a baudrate change.

Starting from a default ZED-F9P configuration:

Disable SBAS, to avoid position jumps during short RTK corrections interruptions.
Disable Beidou, to make it simpler to increase navigation rate to 5Hz without troubles.
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
- 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)
Enabled UBX-NAV-RELPOSNED to read relative positions.

Rover of a simpleRTK2B+heading kit

Filename simpleRTK2B_FW113_HeadingKit_Rover_1Hz-00

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 USB and UART1:
- UBX-NAV-RELPOSNED
- UBX-NAV-PVT

Bluetooth on simpleRTK2B or simpleRTK2Blite

Filename simpleRTK2B_FW113_Bluetooth-00.txt

Starting from a default ZED-F9P configuration:

Disable SBAS, to avoid position jumps during short RTK corrections interruptions
UART2 activate NMEA output via UBX-CFG-PRT
Activate GST so accuracy estimates are also visible
Enabled High Precision NMEA with one extra decimal digit

simpleSSR 1Hz

Filename simpleRTK2B_FW113_simpleSSR_1Hz-00.txt

UART1 outputs GGA and ZDA. (XBee switch must be on “XBEE TO GPS UART1”).
UART2 disabled. Can be enabled from UBX-CFG-PRT.
USB outputting NMEA+UBX.

simpleSSR 10Hz

Filename simpleRTK2B_FW113_simpleSSR_10Hz-00.txt

UART1 outputs GGA and ZDA. (XBee switch must be on “XBEE TO GPS UART1”).
UART2 disabled. Can be enabled from UBX-CFG-PRT. Increase baudrate to avoid buffer overflow at 10Hz. Contact us if in doubt.
USB outputting NMEA+UBX.