Skip to main content
Basic troubleshooting via Raw Data
Albert Basiul avatar
Written by Albert Basiul
Updated over 7 months ago

Description:

Specialist should be familiar with raw data report and common IO parameters to diagnose common problems (power supply voltage, battery voltage, GSM signal level, satellites, input trigger, HDOP).

To enable raw data please consult the following article: How to enable Raw Data in TT2

List of common problems:

  1. Object is gray / Device is not sending data and does not respond to SMS.

  2. Data delay.

  3. High data consumption.

  4. Coordinates not updating / location jumps on the map / inaccurate route on the map.

Steps:

  1. If device has internal battery, you can check raw data report to see if device was disconnected from power supply, example can be found here. If power supply was disconnected ask customer to check connection (for end-users ask if vehicle battery is not disconnected, if not – submit a repair to UVS).

  2. Check what was GSM signal level in raw data report for the period when data delay occurred.

  3. Load raw data report for the period with high data consumption and check what is the most frequent input trigger to identify the problem.

  4. Check number of visible satellites and HDOP in raw data report.
    GPS antenna must be checked if device is constantly losing connection to satellites or GPS signal is very inaccurate. Possibly antenna is damaged or incorrectly installed. For recommendations on how to install GPS antenna you can refer to device user manual, which can be found in our documentation website.

  5. Power supply voltage and battery voltage

Power supply:
Power supply voltage must be above 10v for all devices except ECO4 S (ECO4 S models can be connected to 6v).

Battery voltage:
Voltage of fully charged battery should be 4v or above. If battery voltage is below 3.7v it indicates that battery is discharged.

Example of raw data report where device was disconnected from power supply and switched to internal battery:

blobid0.png

GSM signal level:

This parameter can be used to identify data delay issues. GSM signal level = 0 indicates that device had no GSM/GPRS and could not send data to server.


For OTA FW/CFG updates GSM signal level should be above 10.

Example of raw data report with data delay:

blobid1.png

GPRS status and Operators

This is a binary parameter, 0 means not to GPRS, 1 means connected to GPRS. Device needs to be connected to GPRS to send data (however, he might still be able to receive and answer SMS commands even without GPRS).

Check if there are some operators that are not providing GPRS reliably and blacklist them.

mceclip0.png
mceclip1.png

Satellites:

Device must be connected to at least 4 satellites to get coordinates. If number of visible satellites is <4, device will send last known good coordinates to server.

Example of raw data report with 0 satellites:

blobid2.png

Input trigger:

Input trigger represents ID of event which generated record. You can refer to FM IO list to find out, which IO parameter has triggered the record:

blobid3.png


Input trigger 7,8 and 9 represent data collection coefficients:

blobid4.png


Input trigger can be used to identify what is causing high data consumption. Example of raw data report, where DIN4 is short-circuiting and records are generated every second:

blobid5.png

HDOP:

HDOP – horizontal dilution of precision, indicates how accurate GPS signal is. The closer to 1, the more accurate the signal.

Did this answer your question?