Debug tracking devices

Analyzing data sent through the mobile network and debug GPS hardware.

Data from Racemap platform

Track Chart

Green to brown: delay of received coordinates, blue battery

The interactive Track Chart provides insights into your GPS devices at running operations. The Track Chart features:

• Delay of received coordinates: The y-axis indicates the delay of received coordinates in seconds.

• Battery History: A dedicated second y-axis displays the battery history of your GPS tracker, enabling you to monitor power consumption.

Access the Track Chart for a specific device directly in the tracker management.

syntax https://racemap.com/admin/track/<appId>?startDate=2023-11-14T12:30:00.000Z&endDate=2023-11-14T16:30:00.000Z

Tracks API

Pull the timestamps when a specific device recorded a location and when Racemap server received the same location, eg. to check the delay in sending live data through the mobile network.

syntax https://racemap.com/api/tracks/trackId/points?startTime=startTime&endTime=endTime

sample https://racemap.com/api/tracks/59e75469c8adf3c73d75fc66/points?startTime=2018-05-05T10:00:00Z&endTime=2018-05-05T10:15:00Z

• startTime and endTime timestamps in UTC of the first and the last location in the query

• trackId unique Racemap ID of all locations of a specific device

copy trackId of the device you want to investigate in participants API

*/starters, athlete data

parameter	description	type
lng	longitude of location	string
lat	latitude	string
elv	elevation	string
time	timestamp in UTC when device recorded the location, in case of interpolation between last two points => linear interpolated	string
receivedAt	timestamp in UTC when Racemap recorded the location, in case of interpolation between last two points => linear interpolated	string

[
{
"lng": 13.818634,
"lat": 51.107761,
"time": "2018-05-05T10:00:09Z",
"elv": 261,
"receivedAt": "2018-05-05T10:00:23.644Z"
},
{
"lng": 13.817738,
"lat": 51.107412,
"time": "2018-05-05T10:00:24Z",
"elv": 276,
"receivedAt": "2018-05-05T10:00:37.785Z"
},
{
"lng": 13.817476,
"lat": 51.107295,
"time": "2018-05-05T10:00:39Z",
"elv": 273,
"receivedAt": "2018-05-05T10:00:52.769Z"
},
{
"lng": 13.817476,
"lat": 51.107295,
"time": "2018-05-05T10:00:53Z",
"elv": 273,
"receivedAt": "2018-05-05T10:01:09.064Z"
},
{
"lng": 13.816854,
"lat": 51.106363,
"time": "2018-05-05T10:01:08Z",
"elv": 245,
"receivedAt": "2018-05-05T10:01:22.696Z"
},
{
"lng": 13.816932,
"lat": 51.105763,
"time": "2018-05-05T10:01:23Z",
"elv": 235,
"receivedAt": "2018-05-05T10:01:37.651Z"
},
{
"lng": 13.816588,
"lat": 51.105129,
"time": "2018-05-05T10:01:38Z",
"elv": 220,
"receivedAt": "2018-05-05T10:04:40.289Z"
}
]

Record logs of tracking hardware

Queclink GL320

Requirements

• Tracking device is turned on.

• UART data cable

• Windows computer

• We use the CoolTerm software to record the logs of the tracking device. Download CoolTerm here https://coolterm.en.lo4d.com/windows
• Enable the USB port of the computer for UART communication. Read documentation.

The device needs to be connected to the computer to record logs. You have to take the computer with you when reproducing specific tracking scenarios.

On Clicking on CoolTerm icon. The first window you see is this

When connecting a powered-on device to the COM port via the UART cable, CoolTerm won't display it automatically. Users must configure CoolTerm each time it's opened, making sure the device is powered on and connected before initiating the application.

Settings in CoolTerm

Options >> Serial Port:

• UART: Select the port which is enabled for UART communication.

• Baudrate: 115200

Terminal:

• Line Mode

• Local Echo

Receive

• Add timestamps to received data

File Capture:

• Select the file in which you want to capture the logs.

Commands:

Send the command to the device to send logs using the command field: AT+UARTLOG=9

Send the command to the device to stop sending battery-related logs: AT+UARTLOG=0,BAT

Send the command to the device to stop sending logs: AT+UARTLOG=0