User's Guide

Abeeway Tracker Reference Guide FW 2.1 V1.1
Page 19 of 23 10
th
November 2020
Restricted distribution
6 UPLINK MESSAGES
This section describes the payload messages supported by the tracker.
Unless otherwise specified, all values are transmitted in network byte order (MSB first).
Each message is composed of two parts:
➢ A common header
➢ A specific data parts
The LoraWAN
TM
port used for the uplinks is the 18.
The tracker supports different types of uplink messages, that are described in the following sections:
Message type Content
Frame pending 0x00
This uplink message is sent to trigger the sending. (and speed up the
configuration of the tracker) if downlink messages are available on gateway
and no other uplink message is on the queue
Position 0x03 GPS, low power GPS, WIFI or BLE position data
Energy status 0x04 No more used
Heartbeat 0x05
Notify the server that the tracker is operational and under LoRaWAN
TM
coverage
Activity Status
(1)
0x07
Reports the activity counter. Used only by the activity tracking operating
mode
Configuration
(1)
0x07 Reports the partial or whole configuration of the trackers,
Shock detection
(1)
0x07 Reports the accelerometer vector (X, Y, Z) of the detected shock
Shutdown 0x09 Sent when the tracker is set off
Event
(2)
0x0A Sent event information about tracker.
Collection scan 0x0B WIFI or BLE collection scan data
Proximity 0x0C
Proximity feature messages (detailed in the application note AN-
007_proximity feature)
Debug 0x0F Internal use only
7 DOWNLINK MESSAGES
These messages are sent from the server to the tracker through the LoRaWAN
TM
network. They are used to either
configure or manage the tracker. Each message contains a header including:
➢ A message type
➢ An acknowledgement token
The remaining of the message depends on the message type described in the following table.
Message type ID Description