Abeeway Micro Tracker User manual

Micro Tracker Reference Guide
Micro Tracker
Firmware V1.7
ABEEWAY SAS
[e-mail]
www.abeeway.com

Micro Tracker Reference Guide FW 1.7 V1.1
Page 2 of 39
11th october 2018
Restricted distribution
Table of contents
1Introduction..........................................................................................................................................................4
1.1 General Description................................................................................................................................ 4
1.2 Applications............................................................................................................................................... 4
2Features .................................................................................................................................................................4
3Installation............................................................................................................................................................5
3.1 Getting started.......................................................................................................................................... 5
3.2 Fixation........................................................................................................................................................ 5
4Functioning...........................................................................................................................................................6
4.1 Main operating modes........................................................................................................................... 6
4.2 Side operations......................................................................................................................................... 7
4.3 BLE (Bluetooth Low Energy) capabilities ....................................................................................... 8
4.4 Low battery management...................................................................................................................17
4.5 User interface..........................................................................................................................................17
4.6 Geolocation strategies .........................................................................................................................18
5Uplink messages...............................................................................................................................................24
5.1 LoRa uplink transmission ..................................................................................................................24
5.2 Encoded form..........................................................................................................................................25
5.3 Common message header...................................................................................................................25
5.4 Heartbeat messages..............................................................................................................................26
5.5 Position messages .................................................................................................................................26
5.6 Energy Status messages ......................................................................................................................29
5.7 Activity status messages .....................................................................................................................29
5.8 Configuration messages ......................................................................................................................30
5.9 Frame pending messages....................................................................................................................30
6Downlink messages.........................................................................................................................................31
6.1 Acknowledge token ..............................................................................................................................31
6.2 Operational mode configuration .....................................................................................................32
6.3 Position on demand..............................................................................................................................32
6.4 Request device configuration............................................................................................................32
6.5 SOS mode configuration......................................................................................................................33
6.6 Parameters configuration ..................................................................................................................33
6.7 Debug command ....................................................................................................................................35
7Examples of configuration ............................................................................................................................36
7.1 Accurate position using GPS mode only........................................................................................36
7.2 Low power configuration, ..................................................................................................................36

Micro Tracker Reference Guide FW 1.7 V1.1
Page 3 of 39
11th october 2018
Restricted distribution
7.3 Tracking in low power mode (beginning and end of motions only)...................................37
7.4 Indoor only position.............................................................................................................................37
7.5 Fixed frequency positioning..............................................................................................................37
7.6 Activity tracking.....................................................................................................................................38
8Hardware Specifications ...............................................................................................................................39

Micro Tracker Reference Guide FW 1.7 V1.1
Page 4 of 39
11th october 2018
Restricted distribution
1Introduction
1.1 General Description
The Abeeway Micro Tracker is a multi-mode tracker combining GPS/Low power GPS, WIFI, LoRa, BLE radios
with embedded sensors to support accurate outdoor and indoor geolocation. A button, a buzzer and 3 LEDs
are available to interface with the user. The Micro Tracker, with its small size and long battery lifetime, is
the ideal product for many tracking applications.
1.2 Applications
➢Asset tracking at fixed frequency updates or on demand.
➢Personal tracking with help button.
➢Safety monitoring for isolated workers inside facilities or in outdoor.
➢Anti-theft; Notification and location when device is moving.
➢Geofencing applications.
2Features
➢Multiple operating modes
✓Motion tracking: Get the tracker position at a given cycle when motion is detected.
✓Permanent tracking: Get permanently a position of the tracker.
✓Start/End motion tracking: Get position messages during motion start and end events.
✓Activity tracking: Monitor activity rate with embedded sensors.
✓OFF: device stopped
➢Position on demand: Receive the tracker position only when requested (very low power operating
mode).
➢Used geolocation technologies
✓GPS: Precise outdoor position.
✓Low power GPS: Get quick position outdoors and daylight indoor conditions.
✓WIFI: Position indoors and urban area.
✓BLE: Position indoors
➢Buzzer and LEDs
➢Temperature monitoring
➢Embedded antennas
➢LoRa™ Class A radio
➢Water-spray resistant enclosure (IP64)
Note:
1- Low power GPS is referred as LPGPS or LP-GPS in the rest of the document.

Micro Tracker Reference Guide FW 1.7 V1.1
Page 5 of 39
11th october 2018
Restricted distribution
3Installation
3.1 Getting started
➢Charge your device using a micro USB cable. While charging the white LED is ON. When the battery
is fully charged the white LED goes OFF.
➢A long press is needed to turn ON the device (starting in motion tracking mode in standard
configuration).
➢Your network can use two activation modes:
✓OTAA (Over The Air Activation) that requires the following keys to join the network: DEVEUI,
APPEUI and APPKEY for each device. (the most used)
✓ABP (Activation by personalization) that requires the following keys to connect to the
network: DEVEUI, DEVADDR and NWKSKEY for each device
➢Depending on your operator, some actions need to be done to activate the transfer of the data
through Abeeway servers. Please refer to your vendor for more information.
3.2 Fixation
The device can be attached with the provided lanyard or placed in bag, or inside an asset.
Note:
1- the environment and orientation of the tracker can influence the radio performance. For optimum
results keep the zone around the antenna area clear from any conducting material or magnetic fields.
Blue LED
Button
Lanyard
White Charge LED
Micro USB
Antennas area

Micro Tracker Reference Guide FW 1.7 V1.1
Page 6 of 39
11th october 2018
Restricted distribution
4Functioning
4.1 Main operating modes
This section describes the different operational modes supported by the trackers.
OFF mode: The tracker is in deep low power mode. No uplinks are sent in this mode. A long button press is
required to wake it up. Three possibilities to set the tracker in OFF mode:
➢User action (long button press, if bit1 of config_flags is set)
➢Low battery
➢Downlink request
Standby mode: The tracker is sending periodically short LoRa messages, called heartbeat at the chosen
period (lora_period). Device positions can be obtained in this mode by using the side operations features (see
side operations section).
Motion tracking mode: The tracker provides positions when the device is moving. The reporting is done at
the chosen period (ul_period). The positions are acquired based on the geoloc_sensor geolocation
technology. If the device is not moving, heartbeat messages are sent regularly at the lora_period frequency.
End of motion is validated when the device hasn’t moved for 2 minutes.
When the device is static, only heartbeat messages are sent at the chosen period (lora_period). (like in
standby mode)
Note:
1- Whatever the chosen geolocation policy, the first position is always a WIFI one, sent immediately
after the beginning of the motion.
Permanent tracking mode: The device reports its positions at ul_period frequency regardless the motion. It
uses the geoloc_sensor geolocation technology. Heartbeat messages are sent if there are no uplink message
during lora_period seconds.
Note:
1- Having regular position can also be obtained using standby mode + side operation periodic position
See section Example to have an example of configuration
Motion Start/End tracking mode: In this mode, position messages are sent (motion_nb_pos +1)
times at the start and the end of a motion (one WIFI plus motion_nb_pos times using the geoloc_sensor
geolocation technology). The end of the motion is detected when there is no movement during 120 seconds.
Heartbeat messages are sent if there are no uplink message during lora_period seconds.
Activity mode: This mode sends activity reports instead of positions. The tracker focuses on detecting
movements. Each shake detection increases a counter (after applying an integration period). The value of
the counter is reported via the LoRa link at the ul_period frequency. Heartbeat messages are sent if there are
no uplink message during lora_period seconds.
Notes:
1- The accuracy of the different frequencies is not guaranteed as extra delays may be introduced by
the LoRa network duty cycle.
2- In all these modes, side operation can be used to obtain additional positions

Micro Tracker Reference Guide FW 1.7 V1.1
Page 7 of 39
11th october 2018
Restricted distribution
4.2 Side operations
Whatever the operating mode, optional messages can be sent according to the configuration. The side
operations are:
➢Periodic position message
➢Position on Demand
➢Alert positions
➢SOS mode
For Periodic, Position on Demand and Alert position message, sending of the position is driven by the chosen
transmit strategy:
➢Transmit_strat equal to 2 or 3: Position message is sent twice if static, 4 times if moving
➢Transmit_strat equal to 0, 1 or4: Position message is sent 3 times
4.2.1 Periodic position message:
The device sends periodically its position at the periodic_pos_period frequency. Usually, this reporting
frequency is very long. If the periodic_pos_period is set to 0, this message is not sent.
This periodic position uses the geoloc_method geolocation strategy.
It can be accrued to all operational modes
4.2.2 Position on Demand:
Position requests are done via LoRa downlink message. The device answers with its current position.
The geolocation strategy chosen for geoloc_method is used to have this position.
4.2.3 Alert position
After a double short press on the button:
➢The tracker sends its position (using geoloc_method geolocation strategy).
➢LoRa messages is tagged with an alert flag. (see uplink description for more detail)
➢Once done the tracker removes its alert state. There is no server acknowledge. (config_flags, bit2=0)
4.2.4 SOS mode:
Activation/deactivation:
➢using LoRa downlink (See section SOS mode configuration for more details)
➢using double press button (if bit2 of config_flags is set)
When it is activated:
➢Send continuously positions at a fixed period of 120 s.
➢Geolocation strategy: WGPS (WIFI then GPS if WIFI fails).
➢GPS timeout set to 120 seconds (fixed).
➢LoRa messages tagged with an alert flag. (see uplink description for more detail)
Notes:
1- The side operations can be accrued.
2- SOS mode using button press and alert position can’t work at the same time. Both modes are using
the same bit of config_flags:
✓bit2=0: alert position activated
✓bit2=0: SOS mode using press button activated

Micro Tracker Reference Guide FW 1.7 V1.1
Page 8 of 39
11th october 2018
Restricted distribution
4.3 BLE (Bluetooth Low Energy) capabilities
The firmware version 1.7 uses the Bluetooth Low Energy (BLE) capabilities of the micro trackers. Devices,
such as Smart-phones, graphical tablets and so on can communicate with the tracker via this interface.
This connectivity can be enabled or disabled via the bit 5 of the config_flags parameter.
Smartphones or graphical tablets run the Client application and are called Central device in this section.
Unless otherwise specified:
➢all numerical values transmitted through BLE interface shall be in big endian.
➢all string values transmitted through BLE interface shall be composed of unicode characters encoded
with UTF-8.
Note:
1- Wifi scans can’t be performed while it’s advertising and not bonded, to not disturb bonding process.
Terminology used:
➢WRITE_CMD: ATT write command. No answer expected.
➢WRITE_REQ: ATT request command. An answer is expected.
➢WRITE_RESP: ATT response command.
➢NOTIFICATION: ATT notification.
➢SCAN_REQ: ATT scan request.
➢SCAN_RESP: ATT scan response.
➢ERROR_RSP: ATT error response
➢READ_REQ: ATT read request command. An answer is expected.
➢READ_RESP: ATT read response.
4.3.1 Advertisement and connection
When the tracker is powered on, it tries to establish a connection with a central device. The configured
connection interval depends on its bonding state:
➢In absence of bond:
✓ tracker sends advertisements each 500ms for 1 minute. (1)
✓the buzzer beeps periodically
➢If the device is bonded but not connected, it sends advertisements each 2 seconds without any
timeout. This lets the client to use the auto-reconnection capability.
Advertisement packets are sent on each of the 3 advertising channels.
Note:
(1) If the device is not connected within 1-minute delay the BLE module is switch off

Micro Tracker Reference Guide FW 1.7 V1.1
Page 9 of 39
11th october 2018
Restricted distribution
The Client application should scan for all BLE devices containing advertising data with Complete Local Name:
“ABW + 9 latest DEVEUI digit” (e.g. ABW012345678).
The tracker is publishing an encrypted value of its unique Hardware ID within advertising SCAN_RESP. Client
application should proceed with an ACTIVE SCAN to request the related remaining advertising data
(SCAN_REQ). The device authentication can be done by sending a request to an Abeeway server with the
content of the response (SCAN_RESP). Note that this step is not mandatory.
Once authenticated, a connection request should be sent by the Client application.
There is no limitation regarding the connection interval within the connection request.
However, we advise to use a fast connection interval during the service discovery process:
➢Connection interval: 7.5ms
➢Connection latency: 0ms
➢Supervision timeout: 2000ms
4.3.2 BLE Bonding procedure
Once the connection has been established, the Client application should send a bond request within a fixed
delay of 1 minute. If no bond request is received during this period, the BLE module is switched off.
If the bonding fails, the device must be switched off then on to restart the bonding procedure.
4.3.3 BLE Secured connection
A secured connection is established when a known Central device initiates a connection request and
bounded information are present.
Security keys are stored in both tracker and Central device. The connection is encrypted.
When the tracker communicates with the Client application using BLE, it acts as a Bluetooth peripheral and
uses GAP and GATT profiles.
The client application should configure its BLE protocol stack as central.
The tracker sends a connection update request 5 and 30 seconds after a secure connection establishment
using the following parameters:
➢Minimum connection interval: 980ms
➢Maximum connection interval: 1000ms
➢Slave latency: 0
➢Supervision timeout: 6000ms
The Client application should accept the above parameters for energy saving purpose.
As soon as a BLE secure connection is established (with the bond information), the tracker enters in a special
mode where the following applies:
➢Accelerometer and battery monitoring tasks are maintained
➢All LoRa communications are stopped.
➢No geolocation is performed.
Notes:
1- Once connected, the tracker does not accept any other BLE connections.
2- If the tracker has bonding information, only the paired central device can connect to it.
3- Usually the geolocation is done by central device.

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

Micro Tracker Reference Guide FW 1.7 V1.1
Page 11 of 39
11th october 2018
Restricted distribution
4.3.4.3 Battery Information
The tracker exposes the Battery Service allowing a bonded Client application to retrieve the percentage of
the battery level and the battery charging state.
Battery Service (UUID 0x180F)
UUID
Value
Perm
Content
0x2A19
Battery Level
READ
NOTIFY
•Value expressed in percentage.
•0 means fully discharged
•Notification sent for every multiple of 5%
(More details can be found here )
0x2A1A
Battery Power State
READ
NOTIFY
•0x77: Charger present and charging
•0x67: Charger present but not charging
•0x66: Charger not present
•Notifications are sent for every state change.
(More details can be found here )
4.3.4.4 Temperature
The tracker exposes Environmental Sensing Service allowing bonded Client application to retrieve the
current temperature in Degree Celsius.
Environmental Sensing (UUID 0x181A)
UUID
Value
Perm
Content
0x2A1F
Temperature
READ
Current temperature
(More details can be found here)
4.3.4.5 System Event
At any time, the client application must be ready to handle notifications on its Characteristic System Event
(UUID 00002742-1212-efde-1523-785feabcd123). This characteristic is embedded within Abeeway Service:
Abeeway Primary Service (UUID 00008A45-1212-efde-1523-785feabcd123)
System Event Characteristic
UUID
Permission
00002742-1212-efde-1523-785feabcd123
WRITE_REQ
WRITE_CMD,
NOTIFY
Notification content
Value
Description
0x00
SOS Alert Tracker configuration
0x01
Device start moving
0x02
Motion end

Micro Tracker Reference Guide FW 1.7 V1.1
Page 12 of 39
11th october 2018
Restricted distribution
Following diagram explains the procedure to discover the tracker services:
Once a System Event Notification has been received, the client application should retrieve the event type
by reading the notification content.
4.3.5 Immediate Alerts
4.3.5.1 Immediate Alerts sent by the tracker
If the Client application supports a GATT server containing Immediate Alert Service, the tracker will write to
its characteristic value the alert levels as described below:
➢0: No Alert
➢1: Alert Medium. :not used
➢2: Alert High: triggered with a short button press.
It is up to the Client application to decide how it reacts according to the level of alert received.
4.3.5.2 Immediate Alerts received by the tracker
The Client application is allowed to send immediate alerts to the tracker.
Immediate Alert Service (UUID 0x1802)
UUID
Value
Perm
Content
0x2a06
Alert Level
WRITE_CMD
0x00: No Alert
0x02: Alert High
(More details can be found
When the tracker receives an immediate alert, it plays a BLE alert melody. This feature allows the user to
locate the tracker.
4.3.6 Tracker parameters configuration
4.3.6.1 Introduction
The Client application can update and retrieve the tracker parameters by sending the corresponding ATT
Write command (WRITE_CMD).

Micro Tracker Reference Guide FW 1.7 V1.1
Page 13 of 39
11th october 2018
Restricted distribution
Abeeway Primary Service (UUID 00008A45-1212-efde-1523-785feabcd123)
Parameters configuration characteristic
UUID
Permission
00002740-1212-efde-1523-785feabcd123
WRITE_CMD
NOTIFY
The Client application should discover the Abeeway Primary service (UUID: 00008A45-1212-efde-1523-
785feabcd123). This service supports a writable and notifiable characteristic called Parameters configuration
characteristic with UUID: 00002740-1212-efde-1523-785feabcd123.
On every write command on its characteristic value, the tracker sends back the operation result through a
NOTIFICATION.
Before receiving a notification, the Client application must subscribe to the notification handler. This is done
by writing 0x01 to its related Client Characteristic Configuration Descriptor (cccd).
Once done, the Client application can receive such notifications.
The diagram below summarizes the operation described above.
Note:
1- To optimize the throughput during the configuration read or write commands, it is highly
recommended to use WRITE_CMD instead of WRITE_REQ.
4.3.6.2 Write parameters
Once the notifications have been enabled, the Client application can update a parameter by sending a write
command (WRITE_CMD).

Micro Tracker Reference Guide FW 1.7 V1.1
Page 14 of 39
11th october 2018
Restricted distribution
The complete request content is shown below.
Writing parameter value with Write Command
Byte 0
Byte 1
Byte 2-5
WRITE_CMD (always 0x01)
Parameter ID
Parameter Value
Before sending another command, the Client application should wait for the reception of the NOTIFICATION
(containing the write status). Such a message is displayed below.
Writing parameter response from Notification
Status
Bytes 0
Success
0x00
Invalid payload
0x01
Invalid Parameter ID or value
0x03
Example:
To set the parameter having the identifier 0x05 with the value 0x01, the write command (WRITE_CMD)
0x010500000001 should be sent.
A NOTIFICATION will be received in response, with 0x00 if the write operation is a success.
4.3.6.3 Read parameters
Once the notification has been enabled, the Client application can read a parameter value by sending a write
command (WRITE_CMD) containing the parameter identifier to be read.
Reading parameter value with Write Command
Byte 0
Byte 1
Read Command (always 0x00)
Parameter ID
The response is contained within the following NOTIFICATION message.
Remember that the Client application should wait for this NOTIFICATION message before sending another
command.

Micro Tracker Reference Guide FW 1.7 V1.1
Page 15 of 39
11th october 2018
Restricted distribution
The NOTIFICATION message associated to this command is shown below.
Reading parameter value response
Byte 0
Byte 1
Byte 2-5
Status
•0x00: success
•0x01: Invalid payload
•0x02: Invalid Parameter ID
Parameter ID
Parameter Value.
Please check the status before taking
this value in consideration
Example:
To read the value of parameter ID 0x05. The write command 0x0005 should be sent.
A notification will be received in response, containing the parameter value: 0x000500000001.
4.3.7 Tracker Operational modes
4.3.7.1 Introduction
The Client application can change and retrieve the tracker operational mode by sending either a WRITE_REQ
or a READ_REQ using the following Abeeway primary service.
Abeeway Primary Service (UUID 00008A45-1212-efde-1523-785feabcd123)
Operational mode Characteristic
UUID
Permission
00002741-1212-efde-1523-785feabcd123
WRITE_REQ
READ
The Client application should first discover the Abeeway Primary service (UUID: 00008A45-1212-efde-1523-
785feabcd123). This service supports a writable and notifiable characteristic called Operational mode
Characteristic with UUID: 00002741-1212-efde-1523-785feabcd123.
4.3.7.2 Change the operational mode
The Client application can change the operational mode by sending a write request (WRITE_REQ) containing
the new operational mode value.

Micro Tracker Reference Guide FW 1.7 V1.1
Page 16 of 39
11th october 2018
Restricted distribution
The complete request content is shown below.
Change the operational mode with a Write Request
Bytes 0-3
New operational Mode
Under successful completion, the tracker replies with a write Response (WRITE_RSP) containing the value
0x00. Such a message is displayed below.
Operational mode response from Write Response
Byte 0
Status
0x00: success
Under failure, the tracker replies with an Error Response (ERROR_RSP) shown below.
Operational mode response from Error Response
byte 0
Error code
0x81: Invalid operational mode
4.3.7.3 Read the operational mode
The Client application can read the current operational mode by sending a Read request (READ_REQ).
The Read Response (READ_RSP) associated to this command is shown below.
Read the operational mode value response
Bytes 0-3
Current operational Mode
Refer to the section to convert the values.
4.3.8 Send system commands
The Client application can send system commands to the device.
Before accessing this service, the Client application should discover the Abeeway Primary service (UUID:
UUID 00008A45-1212-efde-1523-785feabcd123).

Micro Tracker Reference Guide FW 1.7 V1.1
Page 17 of 39
11th october 2018
Restricted distribution
Abeeway Primary Service (UUID 00008A45-1212-efde-1523-785feabcd123)
Custom command characteristic
UUID
Permission
0000273D-1212-efde-1523-785feabcd123
READ
WRITE_REQ
WRITE_CMD
4.3.8.1 Clear the bond
To remove a bonding information, (locally stored), a bonded Client application should first inform the tracker
about this operation, which is achieved by writing 0x99 to the custom command characteristic value.
Once done, the central device should remove its bonding information.
4.3.8.2 Reset the tracker
To reset the tracker, the Client application should write 0xFE to the custom command characteristic value
(0000273D-1212-efde-1523-785feabcd123).
4.3.8.3 Powering OFF the tracker
To power off the tracker, the Client application should write 0xFF to the custom command characteristic
value.
4.4 Low battery management
When the battery level goes below 3,2V, the device is automatically move to the off mode (no more payload
sent), and a shutdown payload with the reason “low battery” is sent.
While the battery is not charged, the device stays in this mode, and after any button press the Low battery
melody is played (except if the battery level goes below 2.8V.)
When the battery level is above 3,2V a long button press is needed to restart the tracker (move in its previous
mode)
If the battery level is below 2.8V it can take more than the regular two hours to fully charge it.
4.5 User interface
4.5.1 Button management
The interface from the user to the tracker is performed via a button.
Sequence
Action
Output
Two short presses
Trigger an alert position or start/ end
the SOS mode
Other LED pattern
(see next section)
Any press when battery low
(short or long press)
Go to OFF mode, except if mode
disabled
Buzzer melody
fast LED blinking
One long press when device OFF and
good battery
Wake up
LED pattern
(See next section)
One very long press (5 s) when device
ON.
Go to the OFF mode, except if mode
disabled
Buzzer melody

Micro Tracker Reference Guide FW 1.7 V1.1
Page 18 of 39
11th october 2018
Restricted distribution
Button down when device is ON
Blue LED ON
4.5.2 LED interface
One of the two interfaces between the user and the tracker is done via the LED interface. Several patterns
have been defined for different outputs.
LED blinking patterns
Three fast blinks
Go to the OFF mode (Low battery or user operation)
Three slow blinks
Device starting for the first time
Long fast blink of blue LED
LoRa join operation in progress
Fast blink of blue LED after two button clicks
Device acknowledges the alert position
Slow blink of blue LED after two button clicks
SOS mode. Blinking remains until the mode is left
4.5.3 Buzzer melodies
The second interface between a user and the tracker is done via a buzzer.
Up to nine different melodies have been defined:
Melody
Meaning
Device reset
Device is resetting/ going to bootloader
Major rising scale
Device is starting
Major falling scale
Device is going to OFF mode
Low battery
Low battery detected
SOS stop
SOS mode is left
BLE bond on going
Tracker in not bound. Waiting for a bond
BLE bond failure
Bond process unsuccessful
BLE bond success
Bond process successful
BLE alert
Alert activated from connected device using BLE
Note:
1- A zip file containing the different sounds can be found in the same folder than this document.
4.6 Geolocation strategies
4.6.1 Main operating modes
The following geolocation policies (geoloc_sensor parameter) are used by the operating modes: motion-
tracking, permanent-tracking and start/end tracking. Note that in standby mode, only side operations can
report positions.
➢WIFI only →Only WIFI scans are used for position determination.
➢GPS only →Only the GPS is used for position determination.
➢LP-GPS only→GPS and low power-GPS are used for position determination.
➢Multimode (WIFI + AGPS + GPS) →Alternate WIFI, LP-GPS and GPS technologies on failure, with
timeout. Superseded by WIFI-LPGPS/ WIFI-GPS mode.
➢WIFI-GPS only →WIFI then GPS if WIFI fails in one geolocation cycle.
➢WIFI-LPGPS only →WIFI then Low power-GPS if WIFI fails in one geolocation cycle.
➢WIFI-LPGPS/ WIFI-GPS →WIFI-low power GPS first, then WIFI-GPS if WIFI-low power GPS fails until
timeout, then back to WIFI-low power GPS.
➢BLE beacon scan only →Provide data formatted as a list of “MAC address/RSSI” couple that can be
used to compute a position
Note:

Micro Tracker Reference Guide FW 1.7 V1.1
Page 19 of 39
11th october 2018
Restricted distribution
1- The first position is always a WIFI one whatever the chosen geolocation strategy.
4.6.2 Side operations
The following geolocation policies (geoloc_method parameter) are used for periodic-reporting or on-demand
actions.
➢WIFI only →Only WIFI scans are used for position determination
➢GPS only →Only the GPS is used for position determination
➢LP-GPS only→GPS and LP-GPS are used for position determination
➢WIFI-GPS only →WIFI then GPS if WIFI fails in one geolocation cycle
➢WIFI-LPGPS only →WIFI then low power-GPS if WIFI fails in one geolocation cycle
➢BLE beacon scan only →Provide data formatted as a list of MAC address/RSSI(Receive Signal Strengh
Indication) couple that can be used to compute a position
4.6.3 Geolocation technology description
4.6.3.1 GPS
When doing a cold start, the tracker uses systematically a timeout of 5 minutes instead of the configured
one.
To complete a position, the GPS module expects one of the two following conditions to be achieved.
➢The GPS_convergence timeout (time let to the GPS module to have a more precise position)
➢The gps_ehpe value is below the configured value. EHPE (Estimated Horizontal Position Error) is
provided by the GPS module and is expressed in meter.
Once completed the position is reported via LoRa and the GPS module switches to standby state.
Then, it waits gps_standby_timeout delay before going to the off state (losing all data and ephemeris)
In the case where the GPS module didn’t succeed, a GPS timeout message is sent instead of a GPS position
message.
Note:
1- If a period smaller than gps_timeout is set for ul_period the GPS timeout used will be ul_period
instead of gps_timeout
GPS state diagram

Micro Tracker Reference Guide FW 1.7 V1.1
Page 20 of 39
11th october 2018
Restricted distribution
4.6.3.2 Low power GPS
In this mode, the device sends the data given by the GPS module before the agps_timeout delay expiry and
the position calculation is done in our server.
If the GPS module didn’t succeed in having enough data to provide to the server, a LP-GPS timeout message
is sent instead of a LP-GPS data message.
Note:
1- If a period smaller than agps_timeout is set for ul_period the LP-GPS timeout used will be ul_period
instead of agps_timeout
4.6.3.3 WIFI
Since a WIFI scan is always done within five seconds, there is no timeout parameter.
Once the scan is done, BSSID are sent via LoRa with the related RSSI and the position calculation is done in
our server.
In a multi technology geolocation strategy, a WIFI scan with less than 3 BSSID triggers a technology switch.
Regardless the number of BSSID (including 0) a WIFI position is sent.
In the case where the communication fails with the WIFI module, the device sends either a WIFI failure
message or a WIFI timeout message.
4.6.3.4 BLE
In this mode, the device scans to find up to ble_beacon_count number of BLE beacons before the
ble_beacon_timeout delay expiry.
Once the scan is done, the BLE beacon MAC addresses are sent via LoRa with the related RSSI
In the case where the BLE module fails to detect BLE beacons, the device sends a BLE failure message.
Notes:
1- BLE Beacons must be at least compliant with:
•iBeacon (Apple)