Skip to main content
RACELOGIC Support Centre

Common Issues

No ADAS Data

 

Possible Cau se Identification Solution

No GPS on Subject or Target Vehicle

Red Flashing 'Sats' LED on VBOX/Satellite channel is zero.

Ensure the GPS antenna is connected correctly and there are no signs of damage to the cable or antenna.

Ensure the GPS antenna has a clear, unobstructed view of the sky and is located on a metallic groundplane at least 10 cm in diameter.

Power cycle problem VBOX.

ColdStart.

No VBOX to VBOX Radio communication

No flashing Radio Tx/Rx LEDs on the Radios. In normal operation, there should be a flashing Blue Tx LED on the Target radio and a Green Rx LED on the Subject radio.

Ensure both VBOXs are powered on.

Ensure Correct ADAS mode is selected. For correct operation there needs to be a Subject Vehicle and at least one Target Vehicle (Target Vehicle 1 and/or Target vehicle 2).

AND/OR

Ensure the correct connection of the ADAS Radios. Both radios should be connected to the 'SER' port of the VBOX via a RLCAB005 or RLCAB006. If using an RLACS024/1 Splitter on the Subject Vehicle, ensure the radio is connected to the port labelled 'Rx'.

Link Time 'LkTime-tg1' is reporting a zero value. The Link Time channel should constantly increase every time a 'packet' of information is received from the target vehicle. A zero value will indicate that there is no radio communication between the two vehicles.

Ensure there is a clear line of sight between the two antennas and that the antennas are placed on the highest point of the vehicle and away from any obstructions that could block the signal (roof bars, etc.).

Ensure Leap second values are the same in both VBOXs.

Power cycle Radio/VBOX.

Noisy ADAS Data

 

Possible Cau se Identification Solution

No RTK Fix

Range data is very noisy (±1 m movement) when stationary.

Ensure the DGPS Radio is connected to the 'CAN' port.

If using a Static Base Station, ensure that the 'DGPS Mode' on both VBOXs are correctly set to either 'RTCM v3' or 'CMR' and matches the DGPS mode of the Base Station.

AND/OR

If using a Moving Base system, ensure that the 'DGPS Mode' on the Target Vehicle is set to 'MB BASE' and 'MB ROVER' on the Subject VBOX.

DGPS LED is not solid Green on the Subject or Target VBOX/ 'Solution Type' is not 'RTK FIXED'/ 'Status-sv' and/or 'Status-tg1' is not '4'.

Ensure the 'DGPS Rate' matches that of the Radio being used.

Note: This does NOT have to match the Base Station's DGPS Rate.

If using a Static Base Station, ensure that the Base Station is correctly set up as described in the Base Station User Guide.

No Dual Antenna Lock

ADAS data is accurate, but has more noise than usual.

Ensure 'Dual Antenna' mode is enabled.

AND/OR

The 'Dual' LED on the VBOX is NOT solid Green.

Ensure the separation value is accurately measured and correctly entered.

AND/OR

Check that both GPS antennas have a clear, unobstructed view of the sky and are located on a metallic ground plane at least 10 cm in diameter.

'True Heading' channel is a flat zero.

No IMU connected

 

Connect an IMU. Connecting the IMU allows a smoothing routine to take place on the 'True Heading' channel resulting in a cleaner heading signal.

IMU integration is enabled when using Moving Base

Inaccurate Range data when using Moving Base.

Disable IMU integration when using Moving Base.

Inconsistent ADAS Data (repeated values/values dropping to zero)

 

Possible Cau se Identification Solution

Poor VBOX to VBOX Radio communication

Link Time 'LkTime-tg1' is not constantly increasing and instead is repeatedly dropping to zero

Ensure both Radio Antennas are correctly connected and there is no obvious signs of damage to either the antenna or cable.

Ensure there is a clear line of sight between the two antennas and that the antennas are placed on the highest point of the vehicle and away from any obstructions that could block the signal (roof bars etc).

Ensure the area of operation is away from any sources of potential 2.4 GHz interference.

GPS Dropouts

Fluctuating/low number of Satellites when the ADAS data becomes incosistent.

Move the test area to somewhere that has good GPS coverage throughout.

If using a static Base Station, enable IMU integration to provide good position information during short GPS outages.

Range values are stable but look to have an offset/are incorrect

 

Possible Cau se Identification Solution

Contact points not set/set incorrectly

Constant offset in the range values.

Check that both the Subject and Target vehicles have the correct 'Contact Point' offsets entered, using the rear most antenna as the reference point.

OR

Ensure that the 'Set Points' procedure was correctly followed, including the setting of antennas A and B as explained in the User Guide for both the Subject and Target Vehicles.

ANT A and ANT B are back to front

Contact points appear to be projected out the rear of the car.

Drive above the speed threshold and then ensure the vehicle does not change direction when dropping below the speed threshold.

When the vehicle drops below the speed threshold, the last known heading value is used, so any deviation in heading when below this speed will not be used in the ADAS calculations.

OR

True Heading is 180° out from Heading.

Range values are incorrect/noisy when at low speeds or stationary

 

Possible Cause Identification Solution

Single antenna is being used without a smoothing distance or speed threshol   d set

Noisy range values.

Ensure a speed threshold and smoothing distance are set.

The vehicles heading has changed when under the speed threshold with no dual antenna lock

A stable but offset range value.

Drive above the speed threshold and then ensure the vehicle does not change direction when dropping below the speed threshold.

When the vehicle drops below the speed threshold, the last known heading value is used, so any deviation in heading when below this speed will not be used in the ADAS calculations.