> For the complete documentation index, see [llms.txt](https://docs.kpnthings.com/kpn-things/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kpnthings.com/kpn-things/building-blocks/devices/trackers/kpn-global-tracker-autonomous.md).

# KPN Global Tracker Autonomous

<figure><img src="https://portal.kpnthings.com/assets/images/device-types/kpn-global-tracker-autonomous.png" alt="" width="375"><figcaption><p>KPN Global Tracker Autonomous</p></figcaption></figure>

A battery powered 2G/LTE-M device with GPS.

* Supported network type(s): `KPNSTREAMLINEM2M`
* Device Specification ID: `kpn-global-tracker-autonomous`
* Device Specification UUID: `e60e392e-c738-49ae-839e-54363638ae88`

| Decoders                                      | decoderSpecificationUUID               | Description                                            |
| --------------------------------------------- | -------------------------------------- | ------------------------------------------------------ |
| Decoded M2M Data for GlobalTracker Autonomous | `d1f88fc7-cb8c-56ad-8f51-abd3d68e130c` | Decoder for M2M KPN Global Tracker Autonomous devices. |

### Decoded M2M Data for GlobalTracker Autonomous

Decoder for M2M KPN Global Tracker Autonomous devices.

The following SenML records can be present, amongst others:

<table><thead><tr><th width="175">name</th><th width="90">type</th><th width="62">unit</th><th>example</th><th>description</th></tr></thead><tbody><tr><td>altitude</td><td></td><td>m</td><td></td><td>The measured altitude</td></tr><tr><td>batteryVoltage</td><td>number</td><td>V</td><td><code>3.59</code></td><td></td></tr><tr><td>firmwareVersion</td><td>string</td><td></td><td></td><td>not present in detail level 1 messages</td></tr><tr><td>gpsTime</td><td>number</td><td>s</td><td></td><td>Unix EPOCH time in seconds</td></tr><tr><td>gsmNetworkId</td><td>number</td><td></td><td></td><td></td></tr><tr><td>eventDescription</td><td>number</td><td></td><td><ul><li><code>Start moving</code></li><li><code>Stop moving</code></li><li><code>While moving</code></li><li><code>While not moving</code></li></ul></td><td>Description of the device event. Not present in detail level 1 messages.</td></tr><tr><td>eventId</td><td>number</td><td></td><td><ul><li><code>40</code> (Stop moving)</li><li><code>41</code> (Start moving)</li><li><code>44</code> (While moving)</li><li><code>45</code> (While not moving)</li></ul></td><td>Id of the device event. Not present in detail level 1 messages</td></tr><tr><td>gpsStatus</td><td>number</td><td></td><td><ul><li><code>0</code> (OK)</li><li><code>1</code> (Speed/heading invalid)</li><li><code>32</code> (Accuracy not met)</li><li><code>33</code> (Accuracy not met + Speed/heading invalid)</li></ul></td><td>Identifier indicating the GPS Status</td></tr><tr><td>gpsNotes</td><td>number</td><td></td><td><ul><li><code>OK</code></li><li><code>Accuracy not met</code></li><li><code>Speed/heading invalid</code></li><li><code>Accuracy not met + Speed/heading invalid</code></li></ul></td><td>Description of the GPS Status</td></tr><tr><td>heading</td><td>number</td><td>rad</td><td></td><td>Direction in radials. Not present in detail level 1 messages</td></tr><tr><td>latitude</td><td>number</td><td>lat</td><td></td><td>Latitude of the device. Not present in detail level 1 messages</td></tr><tr><td>longitude</td><td>number</td><td>lon</td><td></td><td>Longitude of the device. Not present in detail level 1 messages</td></tr><tr><td>radius</td><td>number</td><td>m</td><td></td><td>Radius indicating the precision of the positition. Not present in detail level 1 messages</td></tr><tr><td>switch</td><td>number</td><td></td><td><ul><li><code>0</code> (Position)</li><li><code>53</code> (SV_CountersUser)</li><li><code>64</code> (SV_Network)</li><li><code>77</code> (TimeAlive)</li></ul></td><td>Identifier indicating the record-type. In case Switch=77, there has been no GPS Fix and the Geo coordinates belong to the previous GPS Fix.</td></tr><tr><td>switchName</td><td>number</td><td></td><td><ul><li><code>SV_Position</code></li><li><code>SV_CountersUser</code></li><li><code>SV_Network</code></li><li><code>SV_TimeAlive</code></li></ul></td><td>Name of this record-type.</td></tr><tr><td>temperature</td><td>number</td><td>Cel</td><td></td><td>The measured temperature</td></tr><tr><td>velocity</td><td>number</td><td>m/s</td><td></td><td>Velocity of the device. Not present in detail level 1 messages</td></tr></tbody></table>

#### Example SenML

{% hint style="info" %}
SenML can be structured in different ways, and we do not guarantee the examples below will look the same as what you will receive on your Destination. To make sure you can handle the SenML optimally, take a look at our documentation about [Understanding and Interpreting SenML Data](/kpn-things/building-blocks/data-processing/thingsml-and-senml/senml/understanding-and-interpreting-senml-data.md).
{% endhint %}

**Detail level 1 (SV\_Network)**

```json
[
  {
    "bn": "urn:dev:IMEI:863740062764946:",
    "bt": 1664818024.4,
    "n": "batteryVoltage",
    "u": "V",
    "v": 3.87
  },
  {
    "n": "firmwareVersion",
    "vs": "69"
  },
  {
    "n": "gpsTime",
    "u": "s",
    "v": 1696499019.6799998
  },
  {
    "n": "gsmNetworkId",
    "vs": "0"
  },
  {
    "n": "switch",
    "vs": "64"
  },
  {
    "n": "switchName",
    "vs": "SV_Network"
  }
]
```

**Detail level 2 (SV\_TimeAliveTripMeters)**

```json
[
  {
    "n": "batteryVoltage",
    "u": "V",
    "v": 4.16,
    "bn": "urn:dev:IMEI:863740069962824:",
    "bt": 1664818024.4
  },
  {
    "n": "eventDescription",
    "vs": "Start moving"
  },
  {
    "n": "eventId",
    "vs": "41"
  },
  {
    "n": "firmwareVersion",
    "vs": "564"
  },
  {
    "n": "gpsNotes",
    "vs": "OK"
  },
  {
    "n": "gpsStatus",
    "vs": "0"
  },
  {
    "n": "gpsTime",
    "u": "s",
    "v": 1696854457.92
  },
  {
    "n": "heading",
    "u": "rad",
    "v": 5.897816608339239
  },
  {
    "n": "latitude",
    "u": "lat",
    "v": 52.0405
  },
  {
    "n": "longitude",
    "u": "lon",
    "v": 4.40833
  },
  {
    "n": "radius",
    "u": "m",
    "v": 9.5
  },
  {
    "n": "switch",
    "vs": "36"
  },
  {
    "n": "switchName",
    "vs": "SV_TimeAliveTripMeters"
  },
  {
    "n": "velocity",
    "u": "m/s",
    "v": 0
  }
]
```

**Detail level 3 (SV\_Position)**

```json
[
  {
    "bn": "urn:dev:IMEI:863740062764946:",
    "bt": 1664818024.4,
    "n": "altitude",
    "u": "m",
    "v": 63
  },
  {
    "n": "batteryVoltage",
    "u": "V",
    "v": 3.87
  },
  {
    "n": "eventDescription",
    "vs": "?1?"
  },
  {
    "n": "eventId",
    "vs": "1"
  },
  {
    "n": "firmwareVersion",
    "vs": "69"
  },
  {
    "n": "gpsNotes",
    "vs": "OK"
  },
  {
    "n": "gpsStatus",
    "vs": "0"
  },
  {
    "n": "gpsTime",
    "u": "s",
    "v": 1696499003.04
  },
  {
    "n": "heading",
    "u": "rad",
    "v": 0
  },
  {
    "n": "latitude",
    "u": "lat",
    "v": 52.04044
  },
  {
    "n": "longitude",
    "u": "lon",
    "v": 4.40817
  },
  {
    "n": "radius",
    "u": "m",
    "v": 9.5
  },
  {
    "n": "switch",
    "vs": "0"
  },
  {
    "n": "switchName",
    "vs": "SV_Position"
  },
  {
    "n": "temperature",
    "u": "Cel",
    "v": 22.5
  },
  {
    "n": "velocity",
    "u": "m/s",
    "v": 0
  }
]
```


---

# 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.kpnthings.com/kpn-things/building-blocks/devices/trackers/kpn-global-tracker-autonomous.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.