# Using GPS trackers On-Site

### Basics

Most types of GPS trackers basically operate with the three main components:

1. **GPS module**: Determines the device's location.
2. **GSM modem**: Sends all data such as location, battery level, etc. via mobile network to the RACEMAP. 
3. **Memory:** If the device is unable to establish a TCP connection with RACEMAP, no data can be sent, even if the GPS module is working perfectlyy. In this case, the data is stored in the device’s memory until a connection is re-established.

In [RACEMAP tracker management](/tracker-management.md) system:

* The **CON** (Connection) column shows the duration since when the device established a TCP connection to RACMEAP respectively since when the socket was closed. 
* The **LOCATION** column provides the duration of the most recent known location and the status of the GPS module.

<figure><img src="/files/LZ8dIo7bAVpNJKzGUMbU" alt=""><figcaption><p>Status of GSM modem and GPS module in the tracker dashboard</p></figcaption></figure>

For example, during a trail run with poor reception - such as between the 30K and 38K marks - the tracker may temporarily lose its connection. During this period, real-time data won't be transmitted to RACEMAP but kept in memory. However, once the device reconnects, it will upload the stored data, filling in gaps in the race playback, so all data will be available in the event replay after a short delay.&#x20;

You can see this relationship very well in the [track chart](https://docs.racemap.com/hardware-for-live-tracking/debugging#track-chart).

### Schedule commands&#x20;

You can schedule commands for a group of GPS trackers to automatically adjust the devices' settings according to the time.&#x20;

A couple of days before the race:&#x20;

* Switch on all devices manually.
* Place devices for a good connection.&#x20;
* Select all devices in tracker management.
* Check connection and location in tracker management.&#x20;
* Clear undelivered commands from messages timeline before scheduling new commands with the "Revoke all messages" function. &#x20;

<figure><img src="/files/YJfckZxVlt8j7Jv2FSxI" alt=""><figcaption></figcaption></figure>

* Schedule commands according to SLEEP, AWAKE and RACE profile.&#x20;
* Don't switch devices off after you have scheduled commands.

**SLEEP profile:** "heartbeat", every 10 to 20 min refreshes the connection to Racemap, if there is reception

<table data-full-width="false"><thead><tr><th width="81">#</th><th width="269">Command</th><th width="257">Parameter</th><th>Time</th></tr></thead><tbody><tr><td>S1</td><td>GPS Module</td><td>mode: 1</td><td>Now</td></tr><tr><td>S2</td><td>GPS Report Interval</td><td>3600; 3600</td><td>Now</td></tr><tr><td>S3</td><td>Non-Movement Detection</td><td>10; 3600; 3600</td><td>Now</td></tr></tbody></table>

{% hint style="info" %}

* Participants must not use the power button! When deploying the devices to participants the devices are turned on already.&#x20;
* Devices lose about 5 to 7 % battery level in 24 hrs.&#x20;
  {% endhint %}

**AWAKE profile:** It takes up to 60 min until all devices receive the new configuration. Check the tracker management if there is a device that does not establish a connection. The participant might have turned the device off. You still have time to change the device before the race starts.&#x20;

<table><thead><tr><th width="77">#</th><th width="260">Command</th><th>Parameter</th><th>Not before</th><th>Not after</th></tr></thead><tbody><tr><td>A1</td><td>GPS Report Interval</td><td>180; 180</td><td>4 hrs before race starts</td><td>3 hrs before race starts</td></tr><tr><td>A2</td><td>Non-Movement Detection</td><td>10; 180; 180</td><td>4 hrs before race starts</td><td>3 hrs before race starts</td></tr></tbody></table>

**RACE profile:** It takes up to 10 min until all devices receive the new configuration. &#x20;

<table><thead><tr><th width="84">#</th><th width="258">Command</th><th width="134">Parameter</th><th>Not before</th><th>Not after</th></tr></thead><tbody><tr><td>R1</td><td>GPS Module</td><td>mode: 0</td><td>1 hr before race starts</td><td>no entry</td></tr><tr><td>R2</td><td>GPS Report Interval</td><td>10; 10</td><td>1 hr before race starts</td><td>no entry</td></tr></tbody></table>

{% hint style="info" %}

* Devices lose about 5 % battery level every 1 hr.&#x20;
* With 60; 60 parameter setting, devices lose about 2 % battery level every 1 hr.&#x20;
  {% endhint %}

For stage events you can schedule subsequent SLEEP and RACE profiles for each stage.&#x20;

After the race: Use the "Shut down" command to remotely switch devices off. When the device has received the shot down it must be switched on manually. There is no possibility to remotely turn on a device.&#x20;

### Fix GPS trackers for different types of Sports&#x20;

<figure><img src="/files/haeAU8nQivigmB2IYZLd" alt=""><figcaption><p>Seal GPS Tracker in a waterproof bag and place it under the swimming cap.</p></figcaption></figure>

<figure><img src="/files/fxuSsq8UnIlEM2orFtTg" alt=""><figcaption><p>Fix the GPS tracker to a bag using an adapter with velcro strap.</p></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.racemap.com/gps-devices/using-gps-trackers-on-site.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.