Abeeway Micro Tracker Reference Manual
  1. Manuals
  2. Brands
  3. Abeeway Manuals
  4. GPS
  5. Micro Tracker
  6. Reference manual

Abeeway Micro Tracker Reference Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Micro Tracker Reference Guide
Micro Tracker
Firmware V1.7
ABEEWAY SAS
contact@abeeway.com
www.abeeway.com

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Micro Tracker and is the answer not in the manual?

Questions and answers

Related Manuals for Abeeway Micro Tracker

Summary of Contents for Abeeway Micro Tracker

  • Page 1 Micro Tracker Reference Guide Micro Tracker Firmware V1.7 ABEEWAY SAS contact@abeeway.com www.abeeway.com...

  • Page 2: Table Of Contents

    Micro Tracker Reference Guide FW 1.7 V1.1 Table of contents Introduction ................................4 General Description ..........................4 Applications ............................... 4 Features .................................4 Installation ................................5 Getting started ............................5 Fixation................................ 5 Functioning ................................6 Main operating modes ........................... 6 Side operations ............................7 BLE (Bluetooth Low Energy) capabilities ..................
  • Page 3 Micro Tracker Reference Guide FW 1.7 V1.1 Tracking in low power mode (beginning and end of motions only) ........37 Indoor only position ..........................37 Fixed frequency positioning ......................37 Activity tracking ............................. 38 Hardware Specifications ..........................39 Page 3 of 39...

  • Page 4: Introduction

    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.

  • Page 5: Installation

    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.

  • Page 6: Functioning

    Micro Tracker Reference Guide FW 1.7 V1.1 4 Functioning 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.

  • Page 7: Side Operations

    Micro Tracker Reference Guide FW 1.7 V1.1 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...

  • Page 8: Ble (Bluetooth Low Energy) Capabilities

    Micro Tracker Reference Guide FW 1.7 V1.1 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.
  • Page 9 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.
  • Page 10 Micro Tracker Reference Guide FW 1.7 V1.1 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).
  • Page 11 (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...
  • Page 12 Micro Tracker Reference Guide FW 1.7 V1.1 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...
  • Page 13 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.
  • Page 14 Micro Tracker Reference Guide FW 1.7 V1.1 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).
  • Page 15 UUID Permission WRITE_REQ 00002741-1212-efde-1523-785feabcd123 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.
  • Page 16 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). Page 16 of 39 11th october 2018...

  • Page 17: Low Battery Management

    Micro Tracker Reference Guide FW 1.7 V1.1 Abeeway Primary Service (UUID 00008A45-1212-efde-1523-785feabcd123) Custom command characteristic UUID Permission READ 0000273D-1212-efde-1523-785feabcd123 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.

  • Page 18: Geolocation Strategies

    Micro Tracker Reference Guide FW 1.7 V1.1 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.
  • Page 19 Micro Tracker Reference Guide FW 1.7 V1.1 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 ➢...
  • Page 20 Micro Tracker Reference Guide FW 1.7 V1.1 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.
  • Page 21 • Eddystone (Google) • Altbeacon 2- The Abeeway geolocation server does not support the position calculation based on BLE beacons. So, it is up to the application to process them. 4.6.3.5 WIFI/LPGPS or WIFI/GPS Using these strategies, the tracker can use two location technologies in the same cycle if needed A WIFI scan result considered as successful (at least three BSSID) triggers a WIFI position message.
  • Page 22 Micro Tracker Reference Guide FW 1.7 V1.1 Page 22 of 39 11th october 2018 Restricted distribution...
  • Page 23 Micro Tracker Reference Guide FW 1.7 V1.1 ➢ In multimode WIFI/LPGPS WIFI/GPS (geoloc_strategy=9): Page 23 of 39 11th october 2018 Restricted distribution...

  • Page 24: Uplink Messages

    Micro Tracker Reference Guide FW 1.7 V1.1 5 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 by: ➢ A common header ➢...

  • Page 25: Encoded Form

    Micro Tracker Reference Guide FW 1.7 V1.1 5.1.2 Confirmed uplink The device can be configured to request LoRa confirmation for a collection of uplink message types. The parameter confirmed_ul_bitmap is used to select the message types that requires a confirmation. Only message types in the range 0x00 to 0x0F can be selected.

  • Page 26: Heartbeat Messages

    Micro Tracker Reference Guide FW 1.7 V1.1 Battery: Battery voltage expressed in volt. Encoded form using lo= 2.8, hi= 4.2, nbits= 8, nresv= 2. It is given with a step of 5,5mV Temperature: Temperature measured in the device, expressed in degree Celsius. Encoded form using lo= - 44, hi= 85, nbits= 8, nresv= 0.
  • Page 27 Micro Tracker Reference Guide FW 1.7 V1.1 5.5.1 GPS fix payload Common header Data Byte 0-4 Byte 5 Byte 6-8 Byte 9-11 Byte 12 Byte 13-15 Header Latitude Longitude EHPE Encrypted Age: Age of the fix. Encoded form using lo= 0, hi= 2040, nbits= 8, nresv= 0. Expressed in seconds. The step is 8 seconds.
  • Page 28 Micro Tracker Reference Guide FW 1.7 V1.1 v_bat5: encoded voltage at T0 + 2 seconds. v_bat6: encoded voltage at T0 + 2.5 seconds. Notes: 1- Most of time a WIFI timeout occurs due to low battery. 2- v_bat encoding uses lo=2.8, hi=4.2, nbits=8, nresv=2. It is expressed in volt with a step of 5.5mV...

  • Page 29: Energy Status Messages

    ➢ 3: scan already on going ➢ 4: No beacon detected ➢ 5: hardware incompatibility 5.6 Energy Status messages This message should be used for the primary battery life estimation. It is not useful for micro tracker 5.7 Activity status messages Common header Data...

  • Page 30: Configuration Messages

    Micro Tracker Reference Guide FW 1.7 V1.1 5.8 Configuration messages Common header Data Byte 0-4 Byte 5 Byte 6-10 Byte 11-15 Byte 16-20 Byte 21-25 Byte 26-30 Header Tag=2 Parameter 0 Parameter 2 Parameter 2 Parameter 3 Parameter 4 Parameter x: Configuration parameter x, coded on 5 bytes as follow: ➢...

  • Page 31: Downlink Messages

    Micro Tracker Reference Guide FW 1.7 V1.1 6 Downlink messages These messages are sent from the server to the tracker through the LoRa network. They are used to either configure or manage the tracker. Each message contains a header including: ➢...

  • Page 32: Operational Mode Configuration

    Micro Tracker Reference Guide FW 1.7 V1.1 6.2 Operational mode configuration The operating mode can be remotely configured with a downlink LoRa message built as follow: Byte 0 Byte 1 Byte 2 0x02 Mode ACK: Acknowledge token. Refer to the section Acknowledge token.

  • Page 33: Sos Mode Configuration

    Micro Tracker Reference Guide FW 1.7 V1.1 6.5 SOS mode configuration Turn on SOS mode of the tracker: Byte 0 Byte 1 0x04 Turn off SOS mode of the tracker: Byte 0 Byte 1 0x05 See section Side operations to have more information about the SOS mode behavior. In this section it is also described how activate it using double press button 6.6 Parameters configuration...
  • Page 34 Micro Tracker Reference Guide FW 1.7 V1.1 6.6.2 Parameters for side operation modes Parameter Unit Range Description Period of the periodic position report. periodic_pos_period 0x03 second 0, 900 - 604800 A null value (0) disables this reporting. Oneshot geolocation policy used for alert,periodic or on...

  • Page 35: Debug Command

    Micro Tracker Reference Guide FW 1.7 V1.1 Parameter Unit Range Description The number of retries for each confirmed uplink when the confirmed_ul_retry 0x13 none confirmation is not received Note: (1) Refer to the section Strategy used for more details (2) Refer to the section...

  • Page 36: Examples Of Configuration

    Micro Tracker Reference Guide FW 1.7 V1.1 7 Examples of configuration 7.1 Accurate position using GPS mode only Case description: Accurate Motion tracking of an asset. Configuration: ✓ Environment: outdoor only (GPS mode only). ✓ Reporting position period: 5 minutes.

  • Page 37: Tracking In Low Power Mode (Beginning And End Of Motions Only)

    Micro Tracker Reference Guide FW 1.7 V1.1 7.3 Tracking in low power mode (beginning and end of motions only) Case description: Long-battery life time. Tracking an asset to get its final location in an indoor/outdoor environment. Proposed configuration ✓ Operational mode: Start/End tracking.

  • Page 38: Activity Tracking

    Micro Tracker Reference Guide FW 1.7 V1.1 Results Position every 6 hours Every 6 hours the device sends its position twice using WIFI/AGPS method. The number of uplinks is doubled if the device is moving. Position every 30 minutes Every 30 minutes the device sends its position once using Multimode strategy. The number of uplinks is doubled if the device is moving.

  • Page 39: Hardware Specifications

    Micro Tracker Reference Guide FW 1.7 V1.1 8 Hardware Specifications Refer to the related datasheet Page 39 of 39 11th october 2018 Restricted distribution...

Table of Contents