User Manual Taiga Tracker - en

User manual
TAIGA TRACKER - ASSET TRACKING DEVICE
DESCRIPTION
Taiga Tracker is designed to track the assets both in open areas
using a navigation receiver, and indoors, using the iBeacon
Bluetooth tag scanner.
In addition to determining the location of the asset, Taiga Tracker

allows you to count the activity of movements, detect impacts.
Energy-efficient data transmission technologies LoRaWAN and Nb-

IoT allows you to provide up to 3 years of battery life. The device
is made in a shock-resistant sealed enclosure, which ensures
operation even in the most severe conditions.
FUNCTIONALITY
• Outdoor geolocation with embedded GPS/GLONASS receiver

• Indoor geolocation with embedded iBeacon scanner
• Motion activity tracking
• Shock detection
• Turn detection
• Temperature measurement
• Battery powered
• Strong waterproof IP-68 enclosure
• Up to 3 years autonomy
• Android/IOS mobile application for device configuration over Bluetooth
APPLICATIONS
• Asset tracking
• Logistics
• Equipment usage activity tracking
• Indoor geolocation
CONNECTIVITY
• LoRaWAN 1.0.3 for TaigaTracker-LW

• Nb-IoT cat. NB2 for TaigaTracker-NB
1
taigaiot.com
User manual
TABLE OF CONTENTS
DESCRIPTION .................................................................................................................................................1
FUNCTIONALITY.............................................................................................................................................1
APPLICATIONS ...............................................................................................................................................1
CONNECTIVITY...............................................................................................................................................1
TABLE OF CONTENTS .....................................................................................................................................2
SPECIFICATIONS ............................................................................................................................................4
DEVICE OPERATION PRINCIPLE .....................................................................................................................5
Device operation behavior .........................................................................................................................5
Geolocation ................................................................................................................................................6
Device modes .............................................................................................................................................6
MOBILE APPLICATION ...................................................................................................................................7
Application description ...............................................................................................................................7
Connecting to device ..................................................................................................................................7
Application features ...................................................................................................................................8
DEVICE CONFIGURATION ..............................................................................................................................9
Geolocation ................................................................................................................................................9
GNSS receiver ...........................................................................................................................................10
iBeacon scanner........................................................................................................................................10
Movement detector .................................................................................................................................11
Motion activity..........................................................................................................................................11
Turn detector ............................................................................................................................................11
Shock detector ..........................................................................................................................................12
Temperature sensor .................................................................................................................................12
Modem *TaigaTracker-NB only ................................................................................................................13
MQTT *TaigaTracker-NB only ...................................................................................................................14
CoAP *TaigaTracker-NB only ....................................................................................................................14
Update server *TaigaTracker-NB only ......................................................................................................14
LoRaWAN *TaigaTracker-LW only ............................................................................................................15
Hibernation ...............................................................................................................................................16
DATA EXCHANGE PROTOCOL ......................................................................................................................17
Uplink packet structure ............................................................................................................................17
GNSS geolocation frame ...........................................................................................................................19
Motion activity frame ...............................................................................................................................20
Shock detection frame..............................................................................................................................20
Bluetooth iBeacon geolocation frame ......................................................................................................21
2
taigaiot.com
User manual
Temperature frame ..................................................................................................................................22

Turn detection frame................................................................................................................................22
Movement detection frame .....................................................................................................................22
CONTACTS ...................................................................................................................................................23
3
taigaiot.com
User manual
SPECIFICATIONS
Enclosure and dimensions
Color Black
Material Glass filled polyamide
Ingress protection rating IP-68
Dimensions 125х75х37 mm
Weight 300 g
Operational conditions
Operational temperature range -40…+85 °С
Humidity 0-100%
Storage temperature range -60 … +100 °C
Power supply
Operational voltage 3.0 V
Battery model 3x CR123 (LiMnO2)
Battery type LiMnO2
Battery lifetime Up to 3 years (depending on settings)
Summary battery capacity 4500 mAh
GNSS geolocation
Antenna type Embedded ceramic
Supported GNSS navigation satellite systems GLONASS/GPS
Number of channels 72
Sensitivity -167 dBm
Cold start time 40 s
Hot start time 3s
Embedded RTC sync with GNSS Yes
Data transmission TaigaTracker-LW TaigaTracker-NB
Communication standard LoRaWAN 1.0.3 class A LTE cat. NB2
Radio frequency range RU864/EU868 B1, B3, B5, B8, B20, B28
Maximum transmit power 16 dBm 23 dBm
Sensitivity -137 dBm -129 dBm
Indoor geolocation
Geolocation method Bluetooth low energy
Scanning period/duration Configurable
Bluetooth beacon format iBeacon
Bluetooth beacon filtration Yes
Additional features
Motion activity tracking Yes, with configurable interval and sensitivity
Start/stop movement detection Yes, with configurable timeout
Shock detection Yes, with configurable sensitivity
Turn detection Yes, with configurable angle threshold
Temperature measurement Yes, with configurable interval
Configuration
Configuration interface With Android/IOS mobile application
Identification
Identification method Embedded NFC tag with device information
4
taigaiot.com
User manual
DEVICE OPERATION PRINCIPLE

Device operation behavior
The basics of device operational principle is presented on structure scheme below
Data generation
regular or event Data transmission
based regular or triggered
Geolocation
FIFO queue LoRaWAN
Movement detector
*for TaigaTracker-LW
Motion activity
Nb-IoT
Turn detector *for TaigaTracker-NB
Shock detector
Temperature sensor
TaigaTracker have several software modules that generate data, module for data transmission and FIFO
queue in between.
The data generation modules can be several types:

• time based - generate data regularly
• event based - generate data when event is detected
• combined - generate data on both, time and events
In addition, data generation software modules is able to trigger immediate geolocation or data
transmission when new data or events is generated by these modules.
Module name Module type Can trigger

Geolocation Time based Data transmission
Movement detector Event based Geolocation, Data transmission
Motion activity Combined Data transmission
Turn detector Event based Geolocation, Data transmission
Shock detector Event based Geolocation, Data transmission
Temperature sensor Combined Data transmission
Embedded queue can store up to 200 records of data and have FIFO operational principle. The oldest data
is transmitting first. If device goes out of network coverage, all measured data will be saved and
transmitted when device goes back to the network.
This architecture allows user to make different flexible asset tracking configurations like:
• Regularly track the asset
• Track asset only when it starts moving and stop moving
• Get location of shock or turn accidents
• Monitor temperature conditions of asset
• Track activity of asset usage
5
taigaiot.com
User manual
Geolocation
TaigaTracker have two methods of resolving position:

• Embedded GNSS receiver, that is used for outdoor geolocation. GNSS can be enabled periodically to
find real geographical position of asset based on radio signals of global navigation satellite systems
GPS and GLONASS.
• Embedded iBeacon scanner, that is used for indoor geolocation. To use iBeacon scanner, the area,
where asset location needs to be tracked should be equipped by iBeacon devices. TaigaTracker
periodically enable iBeacon scanner, find surrounding beacons and generate data frame, that contains
up to 3 visible beacons. For each founded beacon values of Major field, Minor field and RSSI is
recorded. If it is more than 3 beacons is visible in result of scan attempt, TaigaTracker will put in the
frame 3 beacons with best RSSI (actually closest to the device). Based on list of visible beacons,
provided by TaigaTracker and real beacons positions, tracking software can calculate position of the
asset. In addition, Major field filter can be used to prevent device from unwanted iBeacon devices
detection.
If both geolocation methods is enabled in the device settings, iBeacon scanner will be used first. In case if
device can not find any beacon around, it will power on GNSS receiver to find real geographical position.
Device modes
The device possible modes is indicated on picture below
The device is delivered in hibernation mode. It is inactive. Hibernation must be disabled to enable device.
Hibernation mode allows the device to be transported. It is inactivated, emits no messages, and consumes
very little power.
Once activated, device switch between RUN and SLEEP mode based on accelerometer data. These modes
can be used to fine tune the device behavior in the settings. For example, it is possible to disable regular
geolocation in sleep mode.
In SLEEP mode device does not active in Bluetooth for configuration app connection.
6
taigaiot.com
User manual
MOBILE APPLICATION
Application description
A mobile application (iOS or Android) allows configuration of the device via a Bluetooth connection.
Name of the Application: TAIGA IOT
The app can be downloaded from:
• Apple's AppStore – https://apps.apple.com/ru/app/taiga-iot/id1564919917?l=en
• Google's PlayStore - https://play.google.com/store/apps/details?id=com.taiga.confapp
Connecting to device
• Launch the TAIGA IOT Application (make sure that Bluetooth is active)
• Select your device. Please note that it may take 10-15 seconds before your device shows up in the list.
If it doesn’t show update, activate your device by shaking it, as it may be sleeping.
• Enter the password.
Please don’t forget to enable Bluetooth before launching the application
For Android smartphone geolocation need to be enabled as well, otherwise mobile app will
not be able to connect devices. This is Android OS requirement.
The default password (factory settings) for your device is “1111“
7
taigaiot.com
User manual
Application features
The operation of device can be controlled through SETTINGS, STATE, COMMANDS and DEBUG pages of
mobile configuration application.
• Settings: Device configuration

• State: Check the current State of the device
• Commands: Send Commands to device
• Personalization: Check serial number LORAWAN DevEUI, keys, serial number and passwords
• Debug: Check logs and Firmware Update - ONLY ANDROID
8
taigaiot.com
User manual
DEVICE CONFIGURATION
Geolocation
TaigaTracker can launch geolocation process, that assume both iBeacon and GNSS geolocation if enabled
on regular base with predefined period. GNSS receiver and iBeacon scanner can be optionally
enabled/disabled.
If both iBeacon scanner and GNSS receiver is enabled, device use iBeacon scanner first,
then GNSS receiver. If iBeacons scan attempt is successful, GNSS receiver will not be launched.
If both GNSS and iBeacon scanner is disabled, no geolocation will be done, despite the
geolocation settings.
At the end of geolocation process data transmission can be optionally triggered. If this option not enabled,
frame generated in result of geolocation will be saved in queue and transmitted later on regular base or
by another enabled external trigger. External triggers does not impact on regular geolocation, but run
additional geolocation attempt. Regular geolocation could be disabled if devise does not move (SLEEP
mode).
To initiate force geolocation attempt, please use “Run geolocation” command on the COMMANDS
page of mobile application
9
taigaiot.com
User manual
GNSS receiver
The GNSS geolocation is works as indicated on picture below
Looking for position Holding position Generate frame
Looking for position – after power on GNSS receiver it needs a time to resolve position. Time, that is
needed is depends from type of receiver start. For cold start resolving position under clear sky takes
around 40-60 seconds. In worst conditions it can take up to 120 sec. Time for satellite search setting
specify a timeout, after that device will stop attempts to find position and generate empty GNSS
geolocation frame.
Holding position – after position is found, device will leave GNSS receiver in turned on state for satellite
hold time to improve accuracy of position. This is needed because usually, first coordinates, generated by
GNSS receiver after position is found is not quite accurate (error can be up to 100 meters).
Generate frame – after position is found and hold time is elapsed, device will generate GNSS geolocation
frame with founded position and put it in queue.
iBeacon scanner
The iBeacon geolocation is works as described in picture below
Apply filter Generate frame

Looking for beacons
Choose best 3 beacons
Looking for beacons – after power on iBeacon scanner device will look for iBeacon devices radio signals
nearby for time, specified in scanner duration setting.
Apply filter – at the end of the scan, list of visible iBeacons can be filtered by Major field value, provided
in settings. If filtering is not needed, please set this setting to zero
Choose best 3 beacons – since the Bluetooth geolocation frame only contains up 3 beacons, device will
choose from list of visible beacons three with best RSSI values.
10
taigaiot.com
User manual
Generate frame – at the end of filtering and sorting, device will generate frame with best 3 visible beacons
and put it in queue. If less than 3 beacons found, device will generate frame anyway.
If no beacons are visible, or pass the filter, frame will not be generated
Movement detector
Movement detector is work based on embedded accelerometer readings and allow device to switch
between RUN and SLEEP modes. This module is always enabled. Ability to generate start/stop packets can
be enabled/disabled, but the module itself is always working. Sensitivity allows user to define how much
acceleration need to be applied to device to switch it from SLEEP to RUN mode. Stop detection timeout
defines how much time device should not move to switch from RUN to SLEEP mode. Data transmission
and geolocation can be optionally triggered.
If both trigger geolocation and trigger data transmission options is enabled together and
trigger data transmission in geolocation settings enabled as well, data transmission will be
triggered twice. Once after start/stop move, and then after geolocation. This will cause
additional energy consumption.
Motion activity
Device is able to track motion activity of asset with predefined measurement interval and sensitivity.
Activity changing is measured twice per second based on accelerometer data and averaged in
measurement interval. Data transmission can be optionally triggered.
Turn detector
11
taigaiot.com
User manual
Turn detector is work based on embedded accelerometer readings and can detect asset turns in according
with turn angle threshold, defined in settings. After turn is detected, device will ignore another turns, that
could happens in time, defined in turn timeout setting. Data transmission and geolocation can be
optionally triggered. If turn detection functionality is not needed, module can be disabled.
Shock detector
Shock detector is work based on embedded accelerometer readings and can detect asset shocks with
defined in settings sensitivity. Data transmission and geolocation can be optionally triggered. If shock
detection functionality is not needed, module can be disabled.
Temperature sensor
Device is able to provide periodical asset temperature data with period, specified in settings. Data
transmission can be optionally triggered.
If “stop geolocation if no movement” option is enabled, it’s possible that no packets will be
generated during the stop state of device. In this case, periodical temperature measurement
can be used to generate periodical packets once/twice per day to provide heart bit signal to
the tracking platform.
12
taigaiot.com
User manual
Modem *TaigaTracker-NB only
Device will enable modem periodically for regular data transmission with defined in settings regular data
transmission interval. If no one of “trigger data transmission” options in data generation modules is
enabled, all data, that embedded queue contains will be send on regular base. Nb-IoT modem can use
several data transmission methods to the tracking system:
• MQTT protocol
• CoAP protocol
• Non-IP data delivery (NIDD)
Before start using device, please enable LTE bands, that available in your region and specify Access Point
Name for both IP and Non-IP (if used) connectivity methods. To find what bands is available and right APN
names, please contact your telco.
To initiate force join network attempt, please use “Join network” command on the
COMMANDS page of mobile application
13
taigaiot.com
User manual
MQTT *TaigaTracker-NB only
If MQTT protocol is used to transmit device data to the tracking platform please specify in the settings
credentials to access MQTT broker and topic, device should publish data to. Optionally, device can attach
it’s serial number at the end of the provided topic. This is reasonable for some software tracking
platforms.
CoAP *TaigaTracker-NB only
If CoAP protocol is used to transfer device data to the tracking platform please specify in the settings
credentials to access CoAP server and uri path, device should send data to.
Update server *TaigaTracker-NB only
TaigaTracker have over the air firmware and settings update functionality. To get OTA server software,
please contact Taiga IoT company.
14
taigaiot.com
User manual
LoRaWAN *TaigaTracker-LW only
Device can send data regularly through LoRaWAN networks. TaigaTracker-LW support LoRaWAN
specification version 1.0.3 with OTAA join method. Adaptive Data Rate algorithm is disabled. Regional
frequency plan and data transmission.
Avaliable LoRaWAN datarates:

• DR0
• DR1
• DR2
• DR3
• DR4
• DR5
If confirmation option is enabled, device will not remove packets from embedded queue until it receive
packet delivery confirmation from the network. If disabled, device will remove packets from embedded
queue immediately.
Disabled confirmation is reduce load on LoRaWAN network and increase network capacity,
but can cause packet loss. Please disable this setting only if you clearly understand what you
do.
Rejoin interval setting specify interval, device will make attempts to join network. this option is used only
when device still not joined to the network. Once joined, periodical rejoins is disabled.
Device credentials (DevEUI and keys) can be found in the Personalization page of mobile
application (or by scanning the QR code of the device).
To initiate force join network attempt, please use “Join network” command on the
COMMANDS page of mobile application
15
taigaiot.com
User manual
Hibernation
Device have hibernation mode, that can be enabled/disabled through the settings. This mode is needed
for device storage or transportation. In this mode no of software modules is working and device stay in
power saving mode.
16
taigaiot.com
User manual
DATA EXCHANGE PROTOCOL

Uplink packet structure
Each uplink packet in W-protocol should be composed in according with described below structure. One
packet can contain one or more frames. Frames count is variable. All fields with a field width more than
one byte have little-endian byte order.
Uplink packet structure description

Field Field width Description Parameter width Possible values
Packet header
0 – battery power
Type of power 1 LSB bit
Power 1 – external power
1 byte
information Indicates device battery Any positive value from
7 MSB bits
charge 0x00 to 0x64
Serial number presence
0 – serial number field is
bit. Indicates, that
not present
device serial number is 1 LSB bit
1 – serial number field is
present in current
present
packet.
Any positive value from
0x00 to 0x08
Indicates version of W-
Protocol 3 bits 0x01 for protocol
1 byte protocol
information version described in this
document
Payload size presence
0 – payload size field is
bit. Indicate that
not present
payload size field is 1 bit
1 – payload size field is
present in current
present
packet header.
RFU 3 MSB bits
0x00000000 to
Unique device serial 0xFFFFFFFF
(optional, depending on
Serial number 4 bytes 32 bits
serial number presence Serial used in networks,
bit) that have no built in way
to identify device (Nb-
IoT, GPRS, Wi-Fi etc.)
This field is used for
Total length of payload,
connectivity methods
that is sum of all frames,
with flow data transfer
in bytes, excluding
Payload size 2 bytes 16bit like TCP-IP, where
packet header (optional,
several packets can be
depending on payload
transferred as one batch
size presence bit)
of data.
Frame 1
Type of frame 12 LSB bits
0x00 to 0x1000
Frame header 2 bytes
Frame event code. Any positive value from
4 MSB bits
Indicates a reason why 0x00 to 0x10
17
taigaiot.com
User manual
this frame was Depends from Frame

generated type
Frame payload data of current Depends from frame
n bytes
payload frame type
Frame 2
0x00 to 0x1000
4 MSB bits
generated type
n bytes
payload frame type
… Frame n
0x00 to 0x1000
4 MSB bits
generated type
n bytes
payload frame type
Each packet consists from fixed size packet header and one or series of frames. Field “Serial number” used
only in case, when data exchange network protocol has no embedded ability to unique identify end devices
(Wi-Fi, Nb-IoT, LTE, etc..). For network protocols like LoRaWAN with embedded ability to identify device
this fields is not used, that indicated by “serial presence indicator” field.
Examples:
MQTT/CoAP/Non-IP – Serial number field present in packet
LoRaWAN – Serial number field not present in packet
18
taigaiot.com
User manual
GNSS geolocation frame
Field Field width Description Width Possible values

For this type of frame
always == 0x03
0x00 – frame generated
on regular base
Frame 0x01 – frame generated
2 bytes Frame event code.
header because of device mode
Indicates a reason why 4 MSB bits
change
this frame was generated
in result of platform
request
Frame Any positive value from
generation 4 bytes Unixtime (UTC) 32 bits 0x00000000 to
timestamp 0xFFFFFFFF
Device latitude in format
Any value from –
Latitude 4 bytes XX.YYYYY multiplied by 32 bits
9000000 to +9000000
100000
Device longitude in format
Any value from –
longitude 4 bytes XX.YYYYY multiplied by 32 bits
18000000 to +18000000
100000
Altitude 2 bytes Device altitude in meters 16 bits
Ground Speed of device relative to Any positive value from
2 bytes 16 bits
speed the ground in km/h 0x0000 to 0xFFFF
Horizontal dilution of Any positive value from
HDOP 1 byte 8 bits
precision, multiplied by 10 0x00 to 0xFF
Satellites in Amount of satellites used
5 LSB bits
use in navigation solution
0 – device outside
geofence 1
Inside geofence 1 flag 1 bit
1 – device inside
geofence 1
0 – device outside
1 byte geofence 2
Inside geofence 2 flag 1 bit
1 – device inside
geofence 2
0 – if device is not in
movement
Movement Movement flag (based on
1 MSB bit 1 – if device in
status accelerometer data)
movement
19
taigaiot.com
User manual
Motion activity frame

always == 0x05
on regular base
Frame header 2 bytes Frame event code. 0x01 – frame generated
Indicates a reason why 4 MSB bits because of shock
this frame was generated detection
0x02 – stop movement
0x03 – start movement
Measurement Any positive value from
period start 4 bytes Unixtime (UTC) 32 bits 0x00000000 to
Duration of
Measurement Any positive value from
1 byte measurement period in 8 bits
period duration 0 to 255
minutes
Averaged index of
Motion activity Any positive vale from 0
1 byte motion activity in 8 bits
index to 100
measurement interval
Shock detection frame

always == 0x06
Frame Frame event code.
2 bytes
header Indicates a reason why
4 MSB bits 0x01 – shock detected
this frame was
generated
Frame Any positive value from
generation 4 bytes Unixtime (UTC) 32 bits 0x00000000 to
20
taigaiot.com
User manual
Bluetooth iBeacon geolocation frame
This frame lists three visible Wi-Fi access points with strongest RSSI.
For this type of frame always ==
0x09
Frame
2 bytes Frame event code. Indicates a
header 0x00 – frame generated on regular
reason why this frame was 4 MSB bits
base
generated
Frame
generation 4 bytes Unixtime (UTC) 32 bits
0x00000000 to 0xFFFFFFFF
timestamp
Major field of first visible
Major1 2 bytes 16 bits Any value from 0 to 65535
iBeacon
Minor field of first visible
Minor1 2 bytes 16 bits Any value from 0 to 65535
iBeacon
Received signal strength
RSSI1 1 byte 8 bits Any value from -128 to 0
indicator for first visible beacon
Major field of second visible
iBeacon
Minor field of second visible
iBeacon
RSSI2 1 byte indicator for second visible 8 bits Any value from -128 to 0
beacon
Major field of third visible
iBeacon
Minor field of third visible
iBeacon
RSSI3 1 byte indicator for third visible 8 bits Any value from -128 to 0
beacon
RFU 7 LSB bits RFU
Additional
1 byte Movement flag (based on 0 – if device is not in movement
Flags 1 MSB bit
accelerometer data) 1 – if device in movement
21
taigaiot.com
User manual
Temperature frame

0x0F
0x00 – frame generated on regular
Frame header 2 bytes Frame event code.
base
Indicates a reason why this 4 MSB bits
0x01 – frame generated because
frame was generated
alarm
Frame generation Any positive value from
4 bytes Unixtime (UTC) 32 bits
timestamp 0x00000000 to 0xFFFFFFFF
Number of temperature
Sensor number 1 byte 8 bits Any value from 0 to 255
sensor
Temperature in degrees 16 bits
Temperature 2 bytes Celsius * 10 Any value from -32768 to 32768
(example: 25.1 C == 251)
Turn detection frame

0x12
Indicates a reason why 4 MSB bits 0x01 – Turn event detected
Frame
timestamp
Movement detection frame

0x13
Indicates a reason why 4 MSB bits 0x00 – Always zero
Frame
timestamp
0 – if device not in movement
Movement flag 1 byte Movement status 8 bits
1 – if device in movement
22
taigaiot.com
User manual
CONTACTS
Internet of things laboratory LLC
630102, Shevchenko street, building 11, Novosibirsk, Russian Federation
E-mail – info@taigaiot.com
Website – https://taigaiot.com/
23
taigaiot.com

User Manual Taiga Tracker - en

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

User Manual Taiga Tracker - en

Uploaded by

Copyright:

Available Formats

User manual

TAIGA TRACKER - ASSET TRACKING DEVICE

In addition to determining the location of the asset, Taiga Tracker

Energy-efficient data transmission technologies LoRaWAN and Nb-

• Outdoor geolocation with embedded GPS/GLONASS receiver

• LoRaWAN 1.0.3 for TaigaTracker-LW

Temperature frame ..................................................................................................................................22

DEVICE OPERATION PRINCIPLE

The basics of device operational principle is presented on structure scheme below

The data generation modules can be several types:

Module name Module type Can trigger

TaigaTracker have two methods of resolving position:

The device possible modes is indicated on picture below

Please don’t forget to enable Bluetooth before launching the application

The default password (factory settings) for your device is “1111“

• Settings: Device configuration

The GNSS geolocation is works as indicated on picture below

Looking for position Holding position Generate frame

The iBeacon geolocation is works as described in picture below

Apply filter Generate frame

Modem *TaigaTracker-NB only

MQTT *TaigaTracker-NB only

CoAP *TaigaTracker-NB only

Update server *TaigaTracker-NB only

LoRaWAN *TaigaTracker-LW only

Avaliable LoRaWAN datarates:

DATA EXCHANGE PROTOCOL

Uplink packet structure description

this frame was Depends from Frame

GNSS geolocation frame

Field Field width Description Width Possible values

Motion activity frame

Field Field width Description Parameter width Possible values

Shock detection frame

Field Field width Description Parameter width Possible values

Bluetooth iBeacon geolocation frame

Field Field width Description Width Possible values

Turn detection frame

Field Field width Description Width Possible values

Movement detection frame

Field Field width Description Width Possible values

You might also like