Symptoms

• Screen remains off when power is applied
• No LED activity
• The unit does not respond to input

Possible Causes

• No power supplied to the unit
• Faulty power cable or connector
• Insufficient supply voltage
• Internal hardware fault

Resolution

1. Verify that the power source is active
2. Check all power connections are secure
3. Inspect the power cable for damage
4. Confirm the supply voltage meets requirements
5. Try an alternative power source if available
6. Remove the SD card and attempt to power on again

Applies To

• VBOX Touch V2
• VBOX Touch V3
• VBOX Touch RTK

Symptoms

• The unit powers off during operation
• The unit restarts without user input

Possible Causes

• Unstable power supply
• Loose power connection
• Overheating
• Internal fault

Resolution

1. Check power connections are secure
2. Verify the power source is stable
3. Ensure the unit is not overheating
4. Inspect installation environment for excessive heat

Applies To

• VBOX Touch V2
• VBOX Touch V3
• VBOX Touch RTK

Symptoms

• The unit powers on but does not progress past boot screen
• The screen remains static after startup

Possible Causes

• Corrupt SD card
• Firmware issue
• Internal system fault

Resolution

1. Power off the unit
2. Remove the SD card
3. Power on the unit again
4. If the unit boots as expected, replace or reformat the SD card
5. Reinstall firmware if required

Applies To

• VBOX Touch V2
• VBOX Touch V3
• VBOX Touch RTK

Symptoms

• No satellites detected
• Speed remains at 0 when moving
• Position does not update

Possible Causes

• Antenna not connected
• Obstructed sky view
• Damaged antenna cable
• Poor installation location

Resolution

1. Verify the GNSS antenna is connected correctly
2. Ensure the antenna has a clear view of the sky
3. Check the antenna cable for damage
4. Reposition the antenna if necessary
5. Allow sufficient time for satellite acquisition

Variant Notes

VBOX Touch RTK

GNSS lock must be achieved before RTK can function

Applies To

• VBOX Touch V2
• VBOX Touch V3
• VBOX Touch RTK

Symptoms

• The unit takes an unusually long time to obtain satellite lock

Possible Causes

• Poor antenna placement
• Obstructed sky view
• Environmental conditions
• Coldstart condition

Resolution

1. Make sure that the antenna has an unobstructed sky view
2. Avoid mounting the antenna near metallic obstructions
3. Leave the unit powered on to allow acquisition
4. Relocate the antenna if necessary

Applies To

• VBOX Touch V2
• VBOX Touch V3
• VBOX Touch RTK

Symptoms

• Reported speed does not match expected values
• Position data appears incorrect or inconsistent

Possible Causes

• Poor satellite signal
• Antenna placement issues
• Multipath interference
• Loss of RTK correction (VBOX Touch RTK only)

Resolution

1. Check antenna placement and sky visibility
2. Make sure the antenna is mounted securely
3. Avoid reflective surfaces near the antenna
4. Verify GNSS signal strength

Variant Notes

VBOX Touch RTK

If RTK correction is not active, accuracy will revert to standard GNSS.

Applies To

• VBOX Touch V2
• VBOX Touch V3
• VBOX Touch RTK

Symptoms

• Signal is lost during operation
• Data becomes inconsistent or interrupted

Possible Causes

• Obstructions blocking satellite view
• Loose antenna connection
• Cable damage
• Electrical interference

Resolution

1. Check that the antenna connection is secure
2. Inspect cable for damage
3. Ensure the antenna has clear sky visibility
4. Avoid routing cables near high-interference sources

Applies To

• VBOX Touch V2
• VBOX Touch V3
• VBOX Touch RTK

Symptoms

• RTK status not achieved
• Accuracy does not improve beyond standard GNSS

Possible Causes

• No correction data received
• Incorrect configuration
• Network or modem issue
• Base station unavailable

Resolution

1. Verify correction data source is active
2. Check network or modem connection
3. Confirm RTK configuration settings
4. Make sure that the antenna has a clear sky view

Applies To

VBOX Touch RTK only

Symptoms

• RTK fix is lost during operation
• Accuracy decreases

Possible Causes

• Interruption in correction data
• Network instability
• Signal obstruction

Resolution

1. Check network or radio connection
2. Verify correction source availability
3. Ensure antenna remains unobstructed

Applies To

• VBOX Touch RTK only

Symptoms

• The unit does not recognise the SD card
• Logging cannot start

Possible Causes

• SD card not inserted correctly
• Corrupt or incompatible SD card
• Card failure

Resolution

1. Remove and reinsert the SD card
2. Try a known working SD card
3. Format the SD card if required
4. Replace the SD card if faulty

Applies To

• VBOX Touch V2
• VBOX Touch V3
• VBOX Touch RTK

Symptoms

• The unit does not begin recording data
• No files created on SD card

Possible Causes

• No SD card detected
• Incorrect settings
• Storage full

Resolution

1. Confirm SD card is installed and detected
2. Check available storage space
3. Verify logging settings
4. Restart the unit

Applies To

• VBOX Touch V2
• VBOX Touch V3
• VBOX Touch RTK

Symptoms

• Data files cannot be opened
• Files are missing or incomplete

Possible Causes

• SD card corruption
• Improper shutdown
• Storage failure

Resolution

1. Remove and inspect the SD card
2. Try reading the card on another device
3. Format or replace the SD card

Applies To

• VBOX Touch V2
• VBOX Touch V3
• VBOX Touch RTK

Symptoms

• Screen does not respond to input
• Display appears frozen

Possible Causes

• System error
• Firmware issue
• SD card issue

Resolution

1. Power cycle the unit
2. Remove the SD card and retry
3. Reinstall firmware if required

Applies To

• VBOX Touch V2
• VBOX Touch V3
• VBOX Touch RTK

Symptoms

• No data received on CAN bus

Possible Causes

• Incorrect configuration
• Wiring issue
• CAN bus not active

Resolution

1. Verify CAN wiring connections
2. Check CAN configuration settings
3. Ensure connected system is operational

Applies To

• VBOX Touch V2
• VBOX Touch V3
• VBOX Touch RTK

Symptoms

• Data values are incorrect or inconsistent

Possible Causes

• Incorrect configuration
• Scaling or mapping mismatch

Resolution

1. Verify CAN configuration
2. Check scaling and mapping settings
3. Confirm compatibility with receiving system

Applies To

• VBOX Touch V2
• VBOX Touch V3
• VBOX Touch RTK

Symptoms

• Update does not complete
• The unit reports update error

Possible Causes

• Corrupt update file
• SD card issue
• Power interruption

Resolution

1. Verify the integrity of the update file
2. Use a known working SD card
3. Ensure stable power during update
4. Retry the update process

Applies To

• VBOX Touch V2
• VBOX Touch V3
• VBOX Touch RTK

Symptoms

• The unit behaves unexpectedly after update
• Features are missing or not working

Possible Causes

• Incomplete update
• Configuration reset required

Resolution

1. Restart the unit
2. Reapply configuration settings
3. Reinstall firmware if necessary

Applies To

• VBOX Touch V2
• VBOX Touch V3
• VBOX Touch RTK

Symptoms

• You are unsure which hardware variant you are using
• The unit's behaviour does not match documentation
• You need to confirm compatibility or features

Possible Causes

• Multiple hardware variants exist (V2, V3, RTK)
• Firmware version may differ from documentation

Resolution

Identify hardware variant

1. Check the product label on the unit, this typically includes the variant
2. Confirm whether the unit is an RTK variant, RTK units will include additional GNSS/RTK hardware or configuration options

Check firmware version

1. Power on the unit
2. Navigate to the Diagnostics screen
3. Note the firmware version number displayed

Compare with documentation

• Make sure that the firmware version matches the version referenced in the documentation
• If the firmware is older, some features or behaviour may differ

Applies To

• VBOX Touch V2
• VBOX Touch V3
• VBOX Touch RTK

Symptoms

• Lap Timing mode shows no available track
• The unit cannot start lap timing
• Track list is empty or unavailable

Possible Causes

• No track database loaded
• GNSS position not established
• The unit is not within range of a known track
• SD card or database issue

Resolution

1. Make sure that the unit has a valid GNSS lock
2. Confirm that the unit is located at or near a recognised track
3. Check that the track database is present and correctly loaded
4. Verify that the SD card is installed and functioning
5. Restart the unit

Applies To

• VBOX Touch V2
• VBOX Touch V3
• VBOX Touch RTK

Symptoms

• Test stops before completion
• End conditions are not reached
• Run resets or cancels unexpectedly

Possible Causes

• GNSS signal instability
• Start or end conditions not maintained
• Test configuration incorrect
• Loss of speed or inconsistent input data

Resolution

1. Ensure stable GNSS signal before starting the test
2. Verify test configuration (start/end conditions)
3. Maintain consistent vehicle motion throughout the test
4. Avoid sudden interruptions or signal loss
5. Repeat the test under stable conditions

Applies To

• VBOX Touch V2
• VBOX Touch V3
• VBOX Touch RTK

Symptoms

• GNSS acquisition is unusually slow
• Position data appears incorrect after startup
• The unit has been moved a large distance while powered off

Possible Causes

• GNSS data is outdated
• The unit has not been used for an extended period
• The unit has changed location significantly

Resolution

1. Place the unit in a location with a clear view of the sky
2. Power on the unit
3. Leave the unit stationary
4. Allow sufficient time for full satellite acquisition

Applies To

• VBOX Touch V2
• VBOX Touch V3
• VBOX Touch RTK

Symptoms

• Satellite icon flashes red
• GNSS status indicates an issue
• Position or speed data may be unavailable

Possible Causes

• No GNSS lock
• Poor satellite signal
• Antenna issue
• Obstructed sky view

Resolution

1. Check that the GNSS antenna is connected
2. Ensure the antenna has a clear view of the sky
3. Inspect antenna cable for damage
4. Relocate the antenna if necessary
5. Allow time for satellite acquisition

Applies To

• VBOX Touch V2
• VBOX Touch V3
• VBOX Touch RTK

Symptoms

• LEDs do not illuminate
• No visual indication of unit status

Possible Causes

• LEDs disabled in settings
• Firmware issue
• Hardware fault

Resolution

1. Check unit settings to ensure the LEDs are enabled
2. Restart the unit
3. Update or reinstall firmware if required
4. If LEDs remain inactive, the unit may require service

Applies To

• VBOX Touch V2
• VBOX Touch V3
• VBOX Touch RTK

Symptoms

• No data recorded
• No files created on SD card
• Logging does not start

Possible Causes

• SD card not detected
• SD card full or corrupted
• Logging not enabled
• Incorrect configuration

Resolution

1. Confirm the SD card is inserted correctly
2. Check that the SD card is recognised by the unit
3. Verify available storage space
4. Ensure logging is enabled in settings
5. Try a known working SD card
6. Restart the unit

Applies To

• VBOX Touch V2
• VBOX Touch V3
• VBOX Touch RTK

Symptoms

• An error screen appears on the unit
• The unit operation is interrupted
• The unit may become unresponsive

Possible Causes

• Internal system error
• Firmware issue
• SD card problem
• Unrecoverable system fault

Resolution

Restart the Unit

1. Remove power from the VBOX Touch
2. Reapply power to restart the unit
   
   In most cases, this will return the unit to normal operation

Capture Error Information (Recommended)

To assist with diagnosing the issue:

1. Make a note of the actions performed before the error occurred
   
   For example: selected mode, settings changes, or operations performed
   
2. Take a picture of the error screen, ensure the QR code is clearly visible
   
3. Provide this information to Racelogic for analysis, this helps identify the root cause of the error

Check SD Card

1. Remove and reinsert the SD card
2. If the issue persists, try a known working SD card

Reinstall Firmware

(if issue repeats)

1. Reinstall the VBOX Touch firmware
2. This restores the default app and configuration

Applies To

• VBOX Touch V2
• VBOX Touch V3
• VBOX Touch RTK

Symptoms

• Features are missing or unavailable
• Settings or menu options do not match documentation
• The unit behaves differently to expected operation

Possible Causes

• Firmware version mismatch
• Documentation refers to a different firmware version
• A different VBOX Touch application is installed
• Configuration differences

Resolution

Check Firmware Version

1. Navigate to the Diagnostics screen
2. Note the firmware version
3. Compare this with the version referenced in the documentation

Check Installed App (VBOX Touch App)

1. Identify which application is currently installed on the unit
2. Confirm whether it is the default Performance App or an alternative VBOX Touch app

Align With Correct Documentation

• If a different application is installed:
  • Locate and use the documentation specific to that application
• If using the Performance App:
  • Ensure documentation matches the installed firmware version

Restore Default Configuration (if required)

1. Reinstall the VBOX Touch firmware
2. This will restore the default Performance App
3. Recheck behaviour against the documentation

Applies To

• VBOX Touch V2
• VBOX Touch V3
• VBOX Touch RTK

Symptoms

• Expected data is missing from CAN ID 0x305
• Data fields are incomplete or not updating
• Output does not match expected CAN specification

Possible Causes

• Known firmware issue affecting CAN output on ID 0x305
• Firmware version does not include the fix

Resolution

Check firmware version

1. Navigate to the Diagnostics screen
2. Note the installed firmware version

Install Beta firmware (recommended fix)

1. Download the latest VBOX Touch Beta firmware
2. Install the firmware following the standard update procedure
3. Restart the device after installation
   
   The Beta firmware includes a fix for this issue

Verify CAN output

1. Recheck CAN output on ID 0x305
2. Confirm that all expected data fields are present

Applies To

• VBOX Touch V2
• VBOX Touch V3
• VBOX Touch RTK