> For the complete documentation index, see [llms.txt](https://docs.racemap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.racemap.com/gps-devices/teltonika-atc700.md).

# Teltonika ATC700

Set up a Teltonika ATC700 asset tracker for live tracking on RACEMAP.

The ATC700 sends its data with Teltonika's Codec 8 Extended protocol. RACEMAP receives positions, battery, movement, signal strength, the SIM ICCID and alarm events.

{% hint style="success" %}
Server of RACEMAP:

* domain racemap.com
* port 5000
* protocol TCP
  {% endhint %}

{% stepper %}
{% step %}

## Add the tracker

In the tracker manager, add a tracker of type **ATC700** with the 15-digit IMEI printed on the device.
{% endstep %}

{% step %}

## Configure the server

Open the device in Teltonika's [Telematics Configuration Tool (TCT)](https://wiki.teltonika-gps.com/view/ATC700_First_Start) or FOTA Web. In the GPRS settings:

* set the APN of your SIM card,
* set the server domain `racemap.com`, the port `5000` and the protocol **TCP**,
* select the data protocol **Codec 8 Extended**.

The ATC700 sends no records until the server is set.
{% endstep %}

{% step %}

## Enable the IO elements

Enable these IO elements so RACEMAP can show the tracker state:

* Battery level, battery voltage, movement, GSM signal, GNSS status and ICCID.
* Set **Alarm** to raise an event, so the SOS button reaches RACEMAP.
* For low-battery events, set the event of **Battery level** to *On Low* with your threshold. Any other event setting sends a low-battery event on every change.
  {% endstep %}

{% step %}

## Keep the connection open

By default, the ATC700 closes the connection after every record. RACEMAP then shows the tracker going online and offline with each record. To keep one connection open:

* set **Sleep mode** to **Online sleep**, so the modem stays connected while the device sleeps,
* set **Open link timeout** to at least `1200` seconds.

An open connection uses more battery.
{% endstep %}

{% step %}

## Choose the send interval

By default, the ATC700 sends one position every 15 minutes. For live tracking, lower the send period for moving. A shorter period drains the battery faster.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
UDP is not supported. The device must use TCP.
{% endhint %}

## Change settings from RACEMAP

Once the ATC700 is connected, you can change its settings in the tracker manager. Send a message with one of these templates:

* **Server**: the domain and port the device sends to.
* **Record and send periods**: seconds between records and between sends, on stop and while moving. They apply on the home network and while roaming.
* **Asset movement mode**: *Basic* sends at the on-stop periods only. *Movement* uses the accelerometer to switch to the moving periods.
* **Open link and sleep mode**: the open link timeout and the sleep mode.
* **IO priority**: the priority of one IO element, for example `1064100` for the ICCID.
* **Get status**, **Get info**: the device answers with a status text.
* **Restart**: restarts the device.

The message is marked complete when the device answers. Its answer is shown with the message. RACEMAP also reads the periods, the movement mode and the server each time the device connects, and shows them in the tracker settings.

{% hint style="warning" %}
A message only reaches the device while its connection is open. RACEMAP sends it right after the device connects, or while the link stays open. With **Power off sleep**, the device is unreachable until it wakes up.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.racemap.com/gps-devices/teltonika-atc700.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.