LogoLogo
  • KPN THINGS USER GUIDE
    • Introduction
    • Getting started
      • Registration and setup
      • Device simulator app
      • Connect devices
        • SIM cards
        • Supported devices and KPN Devices
        • SODAQ R412M
        • Smartrak
        • Marvin development board
        • LoPy5
        • Arduino MKR WAN 1300/1310
        • Arduin MKR NB 1500
    • All videos
    • Tutorials
      • Configure a flow
      • Connect a HTTPs destination
      • Create a simple IoT web applicationPage
      • Send instruction to LoRa DevicePage
      • Send your data to Azure SQL
      • Technical overview
        • Management data model
        • Uplink communication
        • Downlink communication
        • Location data
      • Accounts and projects
        • Customer accounts and users
        • Projects
        • Customer management
        • Cost overview and contract
    • Frequently asked
      • Multi Factor Authentication
  • GENERAL FUNCTIONS
    • Quick reference videos
    • APIs
  • THE PORTAL EXPLAINED
    • Things Manager
      • Devices
        • Bulk operations
      • Data
        • Device data graph
      • Connectivity
        • LoRa connectivity configuration
      • Bulk reports
    • Things Creator
    • Support
      • News
      • Release notes
      • Real-time status
      • Service reports
      • Documents
      • Support tickets
      • Invoices
      • Contact info
    • Shop
  • BUILDING BLOCKS
    • Devices
      • Sensors
        • KPN Conditionsensor CO2 II
        • KPN Conditionsensor CO2 III
        • KPN Conditionsensor CO2 III motionPage 1
        • KPN FillTag I
        • KPN FillTag II
        • 1M2M ED1608
        • Elsys ERS
        • Device Simulator (Mobile Phone app)
        • Generic Device (Internet connected)
        • Generic LoRa device (preset connectivity)
        • Generic LoRa device (programmable)
        • Generic M2M device
        • Generic M2M device (with Internet connection)
      • Trackers
        • KPN Global Tracker Autonomous
        • KPN Global Tracker Wired
        • KPN LocationTag I
        • KPN LocationTag II
        • KPN LocationTag II v2
        • KPN LocationTag II v2 Expert Mode
        • KPN LocationTag II v3
        • KPN LocationTag III (with GPS)
        • KPN LocationTag III (without GPS)
        • KPN LocationTag III v2
        • KPN LocationTag III v2 Buffer
        • KPN LocationTag III v3
        • KPN LocationTag III v4
        • KPN LocationTag V
        • KPN LocationTag VI
        • KPN LocationTag WS
        • Streamline LoRa
        • Streamline M2M
        • Viloc
      • Routers
      • Gateways
        • KPN FSK Basestation
      • Device SDK
    • Connectivity
      • Connecting LoRa devices
        • LoRa connectivity configuration
      • Connecting M2M devices
      • Connecting Internet devices
      • Connecting MQTT Devices
    • Data Processing
      • ThingsML and SenML
        • ThingsML
        • SenML
          • Understanding and Interpreting SenML Data
          • Changes in KPN SenML
      • Device Twin
      • Decoders and encoders
        • Common measurements list
        • Decoder migrations
        • DIY Decoder
          • DIY decoder scripts
      • Merger
      • Device data
      • Devices
    • Destinations
      • HTTPS destination
      • MQTT broker
      • Cumulocity IoT Platform
      • Azure Event Hubs
      • Azure IoT Hub
      • Test Endpoint
      • ThingsBoard
      • Datacake
      • AWS Lambda
      • Google Cloud Run functions
  • IOT LINE UP
    • Freemium
      • Test SIM cards
    • Explorer
    • Modular
    • Tailored
    • Terms and Conditions
Powered by GitBook

© 2024 KPN - All rights reserved.

On this page

Was this helpful?

Export as PDF
  1. BUILDING BLOCKS
  2. Devices
  3. Trackers

KPN Global Tracker Wired

PreviousKPN Global Tracker AutonomousNextKPN LocationTag I

Last updated 5 months ago

Was this helpful?

KPN Global Tracker Wired

A wired 2G/LTE-M Tracking device with GPS.

  • Supported network type(s): KPNSTREAMLINEM2M

  • Device Specification ID: kpn-global-tracker-wired

  • Device Specification UUID: 7c81c9a6-02e3-46f2-ac68-a300927b5535

Decoders
decoderSpecificationUUID
Description

Decoded M2M Data for GlobalTracker Wired

58a31b2d-05f1-5e4b-a531-18d4f896dbd7

Decoder for M2M KPN Global Tracker Wired devices.

Decoded M2M Data for GlobalTracker Wired

Decoder for M2M KPN Global Tracker Wired devices.

The following SenML records can be present, amongst others:

name
type
unit
example
description

altitude

m

The measured altitude

batteryVoltage

number

V

3.59

firmwareVersion

string

Not present in detail level 1 messages

gpsTime

number

s

Unix EPOCH time in seconds

gsmNetworkId

string

eventDescription

string

  • "Start moving"

  • "Stop moving"

  • "While moving"

  • "While not moving"

Description of the device event. Not present in detail level 1 messages.

eventId

string

  • "40" (Stop moving)

  • "41" (Start moving)

  • "44" (While moving)

  • "45" (While not moving)

Id of the device event. Not present in detail level 1 messages

gpsStatus

string

  • "0" (OK)

  • "1" (Speed/heading invalid)

  • "32" (Accuracy not met)

  • "33" (Accuracy not met + Speed/heading invalid)

Identifier indicating the GPS Status

gpsNotes

string

  • "OK"

  • "Accuracy not met"

  • "Speed/heading invalid"

  • "Accuracy not met + Speed/heading invalid"

Description of the GPS Status

heading

number

rad

Direction in radials. Not present in detail level 1 messages

latitude

number

lat

Latitude of the device. Not present in detail level 1 messages

longitude

number

lon

Longitude of the device. Not present in detail level 1 messages

radius

number

m

Radius indicating the precision of the positition. Not present in detail level 1 messages

switch

string

  • "0" (Position)

  • "53" (SV_CountersUser)

  • "64" (SV_Network)

  • "77" (TimeAlive)

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.

switchName

string

  • "SV_Position"

  • "SV_CountersUser"

  • "SV_Network"

  • "SV_TimeAlive"

Name of this record-type.

temperature

number

Cel

The measured temperature

velocity

number

m/s

Velocity of the device. Not present in detail level 1 messages

Example SenML

Detail level 1 (SV_CountersUser)

[
  {
    "bn": "urn:dev:IMEI:999999999000090:",
    "bt": 1664818024.4,
    "n": "batteryVoltage",
    "u": "V",
    "v": 0.8
  },
  {
    "n": "gpsTime",
    "u": "s",
    "v": 1696501006.08
  },
  {
    "n": "switch",
    "vs": "53"
  },
  {
    "n": "switchName",
    "vs": "SV_CountersUser"
  }
]

Detail level 2 (SV_Network)

[
  {
    "bn": "urn:dev:IMEI:863740069987078:",
    "bt": 1664818024.4,
    "n": "batteryVoltage",
    "u": "V",
    "v": 15.68
  },
  {
    "n": "firmwareVersion",
    "vs": "564"
  },
  {
    "n": "gpsTime",
    "u": "s",
    "v": 1696582683.52
  },
  {
    "n": "gsmNetworkId",
    "vs": "20408"
  },
  {
    "n": "switch",
    "vs": "64"
  },
  {
    "n": "switchName",
    "vs": "SV_Network"
  }
]

Detail level 3 (SV_Position)

[
  {
    "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
  }
]

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