Troubleshooting

IMU not converging

• Not under RTK Fixed signals

• Insufficient movement

• EMI

• Make sure to move in figure 8 or zigzag under RTK Fixed signals to converge IMU.

• The convergence takes ~3mins in the beginning. VRTK-2 in regular use: ~30 seconds

• Contact support if this does not help

VRTK-2 keeps rebooting

• Insufficient power supply

• Using I/O connector but pin 3 is not driven low

• Make sure to use a stable power supply (5V-36V DC)

• Ground this pin to use the I/O connector. To shutdown the sensor, drive this pin high (3-12V). The sensor will only restart when the pin is driven low again. This behavior applies to all sensors with version number 1.2A/B or later (refer to the label on the sensor). For sensors with version numbers 1.0 and 1.1, the pin must be driven high during operation (3.3 V) and can be driven low to reset the sensor.

VRTK-2 is not powering on

• Insufficient power

• port broken

• cable broken

• Make sure to use a stable power supply (5V-36V DC)

• Try another cable

• Try booting via the USB-C port and contact our support.

Weak signal under open sky

• EMI

• No internet connection

• Wrong NTRIP configuration

• GNSS Antennas defect

• GNSS Antenna cable defect

• Try powering off all other components on your platform except for the Vision-RTK 2. Is the problem persisting?

• Provide a stable internet connection to receive RTCM correction data

• Try other (supported) antennas

• Try different antenna cables. Make sure the cables are not bent

Fusion can not be initialized

• IMU

• Wheelspeed wrong

• Not under RTK Fix

• Move under RTK Fix: The IMU convergence takes ~3mins in first use. VRTK-2 in regular use: ~20 seconds

• See the ‘System > Info > Measurement' field. Is the input labelled as bad measurements?

Can not make changes in webinterface

• Fusion is running

• Stop Fusion

• Make changes and save them

• Start Fusion

VRTK-2 is powered on but cannot be accessed via 10.0.2.1 nor WiFi Access Point

• Ethernet set up as DHCP client and

• Cable broken

• Access Point turned off

• Use the USB-C port for recovery access via 10.0.3.1

• Rework network configuration

• Set up static IP and remember the IP address