Omni-ID Sense IoT Manuel utilisateur
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 ecient 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 Cong 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 congurable settings
Conguring Sense Locate Position with Sense Cong PC App
Sleep Tag
Conguring 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 Conguration
Conguring 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 congurable beacon rates.
The device beacon rate is dependent on the congurable device settings.
The device has the following beacon states:
• Default Beacon Rate (DBR), congurable
• Alarm Beacon Rate (ABR), congurable
• Motion Alarm Beacon (MAB), The device will beacon when it senses
motion and enters Motion Alarm state, non-congurable.
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
congurable 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 congurable 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 congurable 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 congurable 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 simplies 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
conguration 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 congurable 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 congurable, 128bits)
• DevNonce (Unique randomly generated number to prevent replay
attack)
V21220SLP 8
An App key needs to be precongured in the Network Server and is used to
validate that the device has permission to communicate with the network.
These values are user congurable and devices can be supplied pre-
congured 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
Table des matières
Autres manuels Omni-ID GPS
