Omni-ID Sense IoT User manual

KIT USER GUIDE
LOCATE - POSITION

INTRODUCTION
Congratulations, you are now the proud owner of the SenseIoT LoRa
Technology Evaluation Kit that will help supercharge your IoT projects.
The IoT devices in this kit are called Sense Locate – Position. As well as
harnessing the power of LoRaWAN these intelligent devices include GPS
and an Accelerometer to provide tracking and position accuracy over long
distances.
LoRaWAN is an IoT focussed communications technology that enables
communication with physical gateways which then communicate via a
cellular or IP network to a cloud or locally hosted network server and then to
a subsequent application server.
The Sense Locate – Position is perfect when high volumes of devices with
low communication needs are required. It is very power ecient to ensure a
long life from the built-in battery and very robust for outdoor use.
This kit contains:-
• 5 Sense Locate – Position IoT devices
• An NFC Programmer with charging cable
• A Multitech reader with power cable, plug adapters, network cable,
USB cable and Antenna.
• Memory Stick containing Omni-ID Sense Cong PC software,
electronic version of this user guide and user guides for the
Multitech reader.
• A magnet that can be used to activate the devices and put them
back to sleep.
We hope you enjoy using this kit and ‘testing your Senses’.
The Omni-ID team.
V21220SLP 1

CONTENTS FOR THIS USER GUIDE
1
1.1
1.2
1.3
1.4
1.5
2
2.1
2.1.1
2.1.2
3
3.1
3.1.1
3.2
3.2.1
3.2.2
3.2.3
3.2.4
4
4.1
4.2
4.2.1
5
6
Tag Operation
DBR (Default Beacon Rate)
ABR (Alarm Beacon Rate)
MAB (Motion Alarm Beacon)
GNSS Firmware basic algorithm
Operation Flow Chart
Sense Locate Position, LoRaWAN packets
Device Gateway beacon
LoRa Network Join Request
Sense Locate Position Data Payload
Device’s congurable settings
Conguring Sense Locate Position with Sense Cong PC App
Sleep Tag
Conguring Sense Locate Position with Android App
Settings and default values
Fast Lock
High Accuracy
Advanced
Sense Locate Position Demo Kit
OmniSphere User Guide
Miultitech Gateway Conguration
Conguring IP Address
Data Sheet
Comparrison Guide
3
4
4
5
6
7
8
8
8
11
12
14
16
17
18
19
20
21
22
23
31
32
37
39
V21220SLP 2

1 Tag Operation
Sense Locate Position is a Class A, LoRaWAN Asset tracking device, equipped
with GNSS to provide accurate asset location over LoRaWAN.
LoRaWAN is a secure communication standard that delivers Secure 128 bit
AES end to end encryption.
The device achieves long life by limiting the GNSS module activity to provide
updates only after asset have ceased movement for at least 1minute period.
If an asset has not moved the previous known position is reported avoiding
the GNSS module from having to be switched on to provide an updated
position.
This device will not provide position while moving, if this is required please
contact Omni-ID to discuss this requirement.
Sense Locate Position is designed for tracking and monitoring applications
over LoRaWAN with following built in sensors:
• Accelerometer
• Temperature
• GNSS
Once the device is in a session with a Network Server it transmits Beacons
containing sensor data on congurable beacon rates.
The device beacon rate is dependent on the congurable device settings.
The device has the following beacon states:
• Default Beacon Rate (DBR), congurable
• Alarm Beacon Rate (ABR), congurable
• Motion Alarm Beacon (MAB), The device will beacon when it senses
motion and enters Motion Alarm state, non-congurable.
V21220SLP 3

All beacons regardless of DBR, ABR or MAB contain the following payload
data:
• GNSS Coordinates in the form of Longitude and Latitude, current
updated location or previous location depending on
event triggering the beacon.
• GNSS Lock, indicating if position lock is achieved within
congurable thresholds (DOP, Min and Max lock times), if last known
location is being sent the lock ag is not set.
• Temperature
• Device Battery Voltage
• Alarm Flags.
1.1 DBR (Default Beacon Rate)
The default beacon rate is the frequency at which the tag beacons its
sensor data under normal conditions (not moving and within temperature
threshold).
The tag default beacon rate can be set as a value of 1-255 Hours.
While in DBR state, the device transmits last known GNSS coordinates, it does
not activate the GNSS module to update position for DBR beacon. The GNSS
module is only activated post device movement.
1.2 ABR (Alarm Beacon Rate)
The ABR is the rate at which the device monitors the temperature. If
the temperature detected is outside of the congurable Minimum and
Maximum temperature threshold, it will set the Temperature Alarm Flag and
transmit a single ABR Beacon.
V21220SLP 4

The device carries on sensing the temperature at the ABR and will transmit
an ABR beacon when the temperature returns to within the acceptable
threshold. This beacon resets the Temperature Alarm Flag.
The alarm beacon rate can be set as a value of 0-254 minutes
Setting the value to zero disables the ABR.
ABR payload contains last known GNSS coordinates, it does not activate
the GNSS module for ABR beacon. The GNSS module is only activated post
device movement.
Motion Alarm Beacons are transmitted under the following situations:
• Motion detected: The device transmits a single beacon when it
senses motion, it sends its last known location, sets Motion Alarm
Flag and GNSS Lock/x Flag not set. The device will only send
1 Motion detected triggered beacon while moving.
• Motion Stopped: The Device transmits a single beacon when
it senses that movement has stopped, it sends its last know
location, Motion Alarm Flag is not set and GNSS lock/x ag not set.
• The GNSS module is activated when the device is stationary post
motion for a period greater than 1minute. Once it has achieved a
GNSS x based on user congurable settings the device sends its
current position, Motion Alarm Flag is set and GNSS lock/x ag
set.
If the GNSS module fails to achieve a lock/x within GNSS Max lock time
which is user congurable the device will reattempt after a period of 10
minutes.
GNSS lock/x is attempted a total of four times, if the lock/x is not achieved
after three reattempts the device will beacon the position achieved on nal
V21220SLP 5
1.3 MOTION ALARM BEACON

1.4 GNSS Firmware basic algorithm
Following ow diagram simplies GNSS algorithm based on Tag’s motion
state sensed by Accelerometer Sensor.
Figure 1: MAB basic operation showing GNSS activation process
V21220SLP 6

1.5 Operation Flow Chart
Figure 2: Above ow chart documents the device’s operation
V21220SLP 7

2 Sense Locate Position, LoRaWAN payload
Packets sent over the air from the device to the gateway:
• LoRaWAN Network Join Request
• Device Payload (Either DBR, ABR or MAB beacons)
Packets sent from device to gateway
• Message Acknowledgments used for initiating Network Join
Request
• LoRaWAN control and synchronisation messages, such as ADR
conguration messages from gateway to device.
2.1 Device to Gateway beacon
2.1.1 LoRaWAN Network Join Request
Sense Locate Position is a Class A, LoRaWAN device which uses OTTA (Over
the Air Authentication) procedure to join a LoRaWAN network.
During the join procedure the device transmits a join request and waits for
response from a Network Server to establish a session.
Once the device is in a session with a Network Server it transmits Beacons
containing device sensor data depending on the congurable beacon
schemes.
In order to join Network end device starts the join procedure by transmitting
join request containing,
• DevEUI (Device’s unique ID, 64 bits)
• AppEUI (Application Unique ID, user congurable, 128bits)
• DevNonce (Unique randomly generated number to prevent replay
attack)
V21220SLP 8

An App key needs to be precongured in the Network Server and is used to
validate that the device has permission to communicate with the network.
These values are user congurable and devices can be supplied pre-
congured with alternative values as part of Service Bureau customisation
service.
Once Network Server accepts join request, the device then generates
following session keys based on App Key,
• NwSKey (Network Session Key): To be shared with Network server
• AppSKey (Application Session Key): To be shared with Application
Server, this ensures end to end encryption of pay load data.
Beacons are then received by LoRa gateway and forwarded to
Network Server which will push data to the end application server.
Figure 3: LoRaWAN Network Infrastructure
V21220SLP 9

If more than one Gateway is in communication range with the device, the
network server sends join acceptance message via the gateway which is
closest to end device based on received RSSI vale of a gateway.
Once accepted the tag will stay joined for a period of up to 6months before
reinitiating a Join Request, so long as network service is not interrupted.
The Sense Locate Position is congured to receive acknowledgment from
the Network Server for each beacon transmitted. This acknowledgment is
sent from the gateway and is used to validate that the device is still joined to
the network and that the communication link has not failed.
When a device fails to receive an acknowledgment for the transmitted
beacon, it assumes that the communication between the device and the
network has failed. If device fails to receive acknowledgement for three
consecutive beacons at either ABR, DBR or MAB it will reinitiate the join
request process. While in the re-joining process GNSS module is disabled.
If a device is unable to join a network, it re-attempt a join request at the next
beacon.
Payload acknowledgements are used purely to monitor and determine
devices join status. If a beacon is not acknowledged the device will not
resend the beacon, this is to avoid excessive network trac.
A device will remain connected with a network server after the join process
is completed regardless of whether an alternative Network Server becomes
available with a better communication link.
A network server can use multiple gateways, in this scenario the device
should roam seamlessly between gateways as long as they all push data to
the same network server.
V21220SLP 10

2.1.2 Sense Locate Position Data Payload
The Sense Locate Position payload consists of 11 Bytes (88 bites). The packet
construction is detailed in this section.
Following example demonstrates how the raw payload is parsed into the
various data device variables:
Device to gateway Beacon (Pay Load): D4EB0D033A69F4FF2D1D41
V21220SLP 11
Decimal Value/10=Battery
Voltage
Low battery + 2.2v (GNSS no
longer activated)
Device shut down voltage = 2.1v

3 Device’s congurable settings
The device settings can be congured via NFC. Omni-ID provides both a
PC software that works with ST Microelectronics M24LR Discovery NFC PCB
tool or alternately an android application. The following are the congurable
parameters:
• EUI (App EUI): 16 Hex Characters, default value: 53 70 65 63 74 72 65 31
• Key (App Key): 32 Hex Characters, default value: 44 43 4c 20 47 61 74 65
77 61 79 20 30 30 30 31
• Data Rate: congurable between 0-7 & ADR, default is ADR
o ADR (Automatic Data Rate), at ADR the network server dictates
the Data Rate and automatically adjust bit rate to optimize battery life
and communication distance
o 0 = SF 12/125kH 250 bits/s
o 1 = SF 11/125kH 440 bits/s
o 2 = SF 10/125kH 980 bits/s
o 3 = SF 9/125kH 1,760 bits/s
o 4 = SF 8/125kH 3,125 bits/s
o 5 = SF 7/125kH 5,470 bits/s
o 6 = SF 7/250kH 11 kbits/s
o 7 = SF FSK 50 kbits/s
• DBR (Default Beacon Rate): 1-255 Hours
• ABR (Alarm Beacon Rate): 0-254 Minutes
o Setting ABR value to 0 disables device’s ABR
• Temperature High Threshold: congurable between -20°C to +80°C
• Temperature low Threshold: congurable between -20°C to +80°C
• Accelerometer Threshold: 0-10
• 1 is least sensitive
o 10 is most sensitive
o 0= o
V21220SLP 12

• GNSS Min. Lock Time: 0-10 Minutes (Default 0min)
o Minimum time GNSS chip will remain active to achive GNSS Fix/
lock
o Recommended setting is 0min, non 0 value is benecial in situation
where assets are moving frequently (multiple time in 2h period) as
this will allow full Almanac and Ephemeris data to be received
increasing initial cold lock
time but reducing subsequent hot lock times and optimizing
battery life.
• GNSS Max. Lock Time: 0-10 Minutes (Default 5min)
o Maximum time GPS module remains active while attempting
to get GPS Fix/lock (Look for available satellites, choose suitable
satellites depending on RSSI values and try to get GPS Fix)
• DoP Dilution of Precision: Values can be set between 1.0 to 10 with
increment of 0.1
o Default setting of 5.0 for fast lock achieving an accuracy of
5-10m and DOP 3.0 for high accuracy achieving an accuracy of
1-5m.
o Note that the lower the DOP threshold the higher accuracy on
position will be achieved, however, to achieve the higher accuracy
will take longer time and therefore the GNSS max should be set
accordingly.
o Note there is the tradeo between higher position accuracy, and
battery life reduction due to increased GNSS module up time.
• Sleep Tag: This function can be used to put Tag to sleep and to
awaken Tag from sleep
o Operation can be executed either by utilising Hall Eect chip
(bringing magnet closer to Top side of LED of Device) or by
PC NFC App.
V21220SLP 13

3.1 Conguring Sense Locate Position with Sense
Cong PC App
Supplied Hardware: ST M24LR-NFC Board (USB device for PC)
Supplied Software: Sense Cong PC APP
Figure 4: Conguration of Sense Locate Position using NFC board
NFC Programming Board Tag Placement on Board
V21220SLP 14

Figure 5: Screenshot of Sense Locate Position PC conguration tool
Press“Read MAC Address”.
Press“Read Settings”to read precongured settings. Choose new settings
from right hand column and press“Write Settings”
V21220SLP 15
Congured
Settings
Choose
settings to
congure
• Place the Sense Locate Position
above the NFC PCB as shown
in Figure 4, once in place press
“Connect” .
• Press“Sense Asset GPS”

3.1.1 Sleep Tag
This function can be used to put Tag to sleep and to awaken Tag from sleep
• Select Asleep in Tag status eld and hit Write Data at the bottom of
App page to put Tag to sleep when Tag is not in use to conserve
battery.
• Select Awake in Tag status eld and hit Write Data at the bottom of
App page to awaken the Tag before deployment.
• Alternatively the device can be awaken or put to sleep by placing a
magnet on the device as shown below:
• The LED will illuminate Green when the tag is waking up and will
illuminate to red if going to sleep.
V21220SLP 16

3.2 Conguring Sense Locate Position with Android App
The Sense Locate Position device can be congured with and Android
device equipped with NFC by downloading the Android application“Sense
LoRa”by following link, http://35.160.220.150/wdc/default.aspx
The app provides the user with 4 menu options:
• Fast Lock
o Loads optimal default values for GNSS Fast Lock
o DOP 5.0, GNSS Min0min, GNSS Max 3min.
• High Accuracy
o Loads optimal default values for GNSS high position accuracy
o DOP 3.0, GNSS Min0min, GNSS Max 5min.
• Advanced
• Settings/Default Value
V21220SLP 17
HOMEPAGE CONFIGURATION PAGE

3.2.1 Settings/Default Values
The APP EUI, APP Key and data rate setting can be set via the settings/
Default Values tab in the application.
Please enter values as below,
EUI 16 Hex Value: 5370656374726531
Key 32 HEX Value: 44434C20476174657761792030303031
Toggle “Save provision Settings” switch to right
Save Settings
V21220SLP 18

3.2.2 Fast Lock
For a quick lock that is accurate between 5-10m use the Fast Lock option.
This is ideal for large assets that are easily recognisable, like plant and farm
equipment.
Note: GNSS DOP Value is automatically congured to 5.0
V21220SLP 19