![Logo_quer_farbig.png]](https://docs.sentinum.de/hs-fs/hubfs/Logo_quer_farbig.png?height=40&name=Logo_quer_farbig.png){kind=logo}
How do I configure Sentinum sensors via downlink and NFC (provisioning)?
This documentation applies to all sensors in the Sentinum series that feature NFC and downlink capabilities. It serves as generic documentation. Detailed descriptions of the individual fields can be found in the respective linked documentation.
Downlinks
Basics of Downlinks with Sentinum Sensors
All downlinks from the Sentiface and Senticom modules are sent on port 4. All commands from the supervisor module, such as resets, are scheduled on Port 5.
Like the payload, the downlink commands are organized into modules . The sensor merely acts as a container that manages and executes the commands. Using the downlinks, the sensor can be configured for the specific application.
In addition to configurations, executable downlinks, such as a reset, can also be performed. All commands are protected by minimum and maximum values to prevent incorrect settings from being made.
The structure is organized hierarchically and consists of the following elements:
- Module
- Group
- Property
- Command
A module contains several groups, which in turn consist of several properties. The following table shows the general structure.
Sensor Modules and Groups
All downlinks from the Sentiface and Senticom modules are transmitted on port 4. All commands from the supervisor module, such as resets, are scheduled on port 5.
Sentinum guarantees backward compatibility across different subversions. This means that a Sentiface module with the key 0x1121 also accepts downlink commands with the key 0x1111.
Structure of the Module Key
The module key of the SENTIFACE module can be derived from the first two bytes of each uplink.
Uplink example:
11 11 06 1B E1 92 02 00 00 06 86
1111 forms the module key.
The module key explained here applies exclusively to
the SENTIFACE module. For SENTICOM, the module key must always be
0x2111.
Structure of a Downlink Command
The reset command is an exception. It is described in the following section.
In the first data packet (uplink), an alarm variable is often already set, since the value is compared to an internal reference value.
Reset Command via Downlink
The reset command must be executed in two steps, or rather in two
downlinks on port 5. First, the reset must be
armed with
the command
[TOKEN] 31 11 01 01
and can then be triggered with
[TOKEN] 31 11 00
.
| Command HEX | Description |
|---|---|
[TOKEN] 31 11 01 01 |
Armed Reset |
[TOKEN] 31 11 00 |
Reset the Sensor |
NFC
Basics
In addition to downlinks, the sensor can also be configured using a smartphone app via NFC. The various sensor configurations are transmitted as a JSON file.
The app offers an initial configuration option as soon as the sensor is activated. In addition to the sensor's settings, the app also allows you to configure network parameters such as APPEUI and APPKEY.
Similar to the downlink, the structure is organized hierarchically.
For NFC configuration, both the modules (module names) and the alias names for the individual properties are important. The following table describes the available modules.
Structure of a JSON Object
Each sensor profile is passed as a JSON object. Each object
begins with { and ends with }. Additional
objects can be nested within a single object.
In general, objects contain an ordered list of properties,
separated by commas. A property is a
key-value pair consisting of a unique key
(string) and a value (any element).
The key and value are separated by a colon (:)
.
Let's look at the following example:
.png?width=688&height=450&name=Untitled%20(100).png)
As in the previous JSON example, the object follows a specific structure. The first key-value pair.
If the sensor is deactivated (power = off), you can
activate the sensor with its default settings by loading, for
example, an empty JSON file and activating the sensor with the app
. You can also set configurations during
activation.
"power":"OFF" or
'power':"ON" describes a state of the sensor.
The sensor responds with off or on
to a command. off or
on therefore does not constitute a command.
To restart the sensor (similar to restarting
a PC), the command REBOOT must be entered into the
power field:
{"power":"REBOOT"}
After a few seconds, the sensor writes the value ON to the
power field, thereby indicating the
completion of the boot process.
Checking the Sensor's Functionality
Using the command REBOOT, you can
check the sensor's functionality. If the
sensor does not overwrite the field within 15 seconds at the latest and remains in the
state {"power":" REBOOT"}, an error has occurred.
This usually indicates dead batteries or a hardware defect.
Activation, Deactivation, and App
Activation is performed via an NFC app. This requires a smartphone . The app can be downloaded from the respective app stores . Simply search for Sentinum LinQs and download the app.
.png?width=688&height=331&name=Untitled%20(22).png)
Now locate the NFC tag on the sensor. Depending on the type of smartphone, the NFC reader may be located at the top, middle, or bottom of the smartphone.
.png?width=688&height=275&name=Untitled%20(14).png)
You can find the location of the NFC tag on the sensor in the respective user manual or in the Quick Start Guide.
If keys such as
app_eui or app_key
are changed and then a
REBOOT
is performed, the original keys will be restored.
The key power is not assigned to any module group
.
You can find instructions for the NFC app here:
TBD
More information about the NFC app
There are read-only (r), write-only (w), and read & write (rw) keys and values. This allows you to protect certain keys, for example.
If a profile is created or transmitted incorrectly, the previous settings are retained. This can happen, for example, if the JSON was created in an invalid format.
When creating a profile, you can access multiple module groups simultaneously or select individual module groups. The same applies to the properties.
In the latest version of the app, profiles can be created and saved. Additionally, a function for reading sensor data is provided. Furthermore, information such as location can be transmitted to a defined endpoint.
Storing Values via Downlink and NFC
Values stored via NFC are retained even after a reset or battery replacement and are read again from the NFC tag by the sensor.
Values set via downlink can be transferred to the NFC tag using an additional downlink command and stored permanently.
Sensor-Specific NFC and Downlink Configurations
CSQ and Reception
| Value | RSSI dBm | Condition |
|---|---|---|
| 2 | -109 | Marginal |
| 3 | -107 | Marginal |
| 4 | -105 | Marginal |
| 5 | -103 | Marginal |
| 6 | -101 | Marginal |
| 7 | -99 | Marginal |
| 8 | -97 | Marginal |
| 9 | -95 | Marginal |
| 10 | -93 | OK |
| 11 | -91 | OK |
| 12 | -89 | OK |
| 13 | -87 | OK |
| 14 | -85 | OK |
| 15 | -83 | Good |
| 16 | -81 | Good |
| 17 | -79 | Good |
| 18 | -77 | Good |
| 19 | -75 | Good |
| 20 | -73 | Excellent |
| 21 | -71 | Excellent |
| 22 | -69 | Excellent |
| 23 | -67 | Excellent |
| 24 | -65 | Excellent |
| 25 | -63 | Excellent |
| 26 | -61 | Excellent |
| 27 | -59 | Excellent |
| 28 | -57 | Excellent |
| 29 | -55 | Excellent |
| 30 | -53 | Excellent |
