Generic NFC and downlink documentation

Are you looking for generic NFC and downlink documentation or wondering how to interpret certain parameters and values for activation?

Here you can find  NFC and downlink documentation

Downlink

Basics of downlinks with Sentinum sensors

Like the payload, the downlink commands are divided into modules. The sensor merely acts as a container that manages and implements the commands. With the help of the downlinks, the sensor can be configured to the specific application. In addition to the configurations, you can also perform downlinks, such as a reset. All commands are protected by minimum and maximum values to prevent incorrect settings.
The structure is hierarchically structured and consists of the following elements:
• Module
• Group
• Property
• Command
A module has several groups, which in turn are made up of several properties.
The following table shows how the structure is generally structured:

Modules and groups of the sensor

Structure of the module key

Example Uplink: 11 11 06 1B E1 92 02 00 00 06 86

Structure of a downlink command

Reset command via downlink

The reset command has to be executed in 2 steps or in 2 downlinks on port 5: First the reset has to be sharpened with the command[TOKEN] 31 11 01 01  and can then be triggered with [TOKEN] 31 11 00.

Downlink example 

First we want to configure our sensor. We decide to put the sensor into a confirmed mode. For this we look at the following downlink (HEX code): 

Next, we want to change the measurement interval to 24 times per day (interval of 60 min). We proceed in this way: 

NFC

Basics

In addition to downlinks, the sensor can also be configured with a smartphone app via NFC. The different configurations of the sensor are called . Pass JSON. The app offers an initial configuration option as soon as the sensor is activated. In addition to the sensor settings, the app also allows the configuration of network parameters, such as APPEUI and APPKEY. Analogous to the downlink, the structure is hierarchically structured.

For the NFC configuration, both the modules (module names) and alias names for the individual properties are important. The following table describes the available modules.

Building one . json object

Each sensor profile is passed as a JSON object. Each object begins with { and ends with }. In one object, other objects can be integrated. 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 that has been formatted:

As in the previous JSON example, the object follows a certain structure. The first key-value pair. If the sensor is disabled (power = off), you can activate the sensor with its basic settings, for example by loading an empty JSON and activating the sensor with the app. The setting of settings is also possible during activation.

To restart the sensor (see restart on a PC) the “REBOOT” command must be written in the “power” field: 

{"power":"REBOOT"}

After a few seconds, the sensor writes the value “ON” in the “power” field and thus indicates the completion of the boot process.

Check the functioning of the sensor

With the help of the “REBOOT” command the functionality of the sensor can be checked. Overwrite the sensor. If the sensor does not overwrite the field after 15 seconds and remains in the {"power":"REBOOT"} state, an error has occurred. This usually indicates an empty battery

Activation, deactivation and app

Activation takes place via an NFC app. A smartphone is required for this. The app can be downloaded from the respective app stores. Simply search for "Sentinum LinQs" and download the app.

You can find instructions for the NFC app here:

https://sentinum.notion.site/LinQs-Anleitungen-b6736b15d07e4452a9f9ea42057391f2?pvs=4

Further information on the NFC APP

Saving values via downlink and NFC

Product and application-specific downlink and NFC commands