EasyManua.ls Logo

Abeeway Micro Tracker - Page 10

Abeeway Micro Tracker
39 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Micro Tracker Reference Guide FW 1.7 V1.1
Page 10 of 39
11th october 2018
Restricted distribution
4.3.3.1 Disconnection with bonded device
The usual BLE keepalive mechanism between the central device and the tracker is done at the frequency of
one message per second (Maximum connection interval).
The BLE connection is said lost if no messages are received for 6 seconds (Supervision timeout).
30 seconds after a secured connection is lost, the last configured operational mode of the tracker is restored.
4.3.3.2 Clear bond event
The bond information can be cleared by:
A LoRa Downlink (see Debug command section for more details)
A specific BLE command, (see details here)
Once cleared the tracker is disconnected from the central device and switches to its configured operational
mode.
The bonding procedure restarts.
4.3.4 Retrieve data from the tracker
4.3.4.1 Device Information
The tracker exposes the Device Information Service allowing a bonded Client application to read information
summarized in the table below:
Device Information Service (UUID 0x180A)
UUID
Value
Perm
Content
0x2a24
Model Number String
READ
MicroTracker
0x2425
Serial Number String
READ
Device EUI-64 (DevEUI) (ex: 20635f01020015f2)
0x2426
Firmware Revision String
READ
BLE Firmware version (ex: 1.0.0)
0x2A28
Software Revision String
READ
Main processor Firmware version (ex: 1.0.0)
0x2A29
Manufacturer Name String
READ
Abeeway
4.3.4.2 Tx Power Level
The tracker exposes the Tx Power Service allowing a bonded Client application to retrieve the Tx power level.
Tx Power Service (UUID 0x1804)
UUID
Value
Perm
Content
0x2a07
Tx Power Level
READ
Refer to the description