Are you looking for generic cellular documentation?
Here you can find generic cellular documentation
📢 This document describes the properties and adjustable parameters specific to the LoRaWAN® wireless protocol across all sensors.
IMEI and IMSI
All delivered Sentinum Cellular (NB-IoT and LTE-M1) sensors have an- IMEI
- IMSI (optional, if supplied with SIM card)
- Product number
Configuration options
NFC and downlink commands
Name: psm_on
Description: Power safe mode on or off. Please consult the manufacturer before changing: 0: off 1: on
Default value: 0
Min: 0
Max: 1
read/write: rw
Name: apn
Description: APN, for own SIM cards enter APN here
Default value:
Min:
Max:
read/write: rw
Name: imsi
Description: Specifies the imsi (SIM card number)
Default value:
Min:
Max:
read/write: r
Name: imei
Description: Specifies the imei (module number)
Default value:
Min:
Max:
read/write: r
Name: regm
Description: 0: Automatic network search and registration
1: Semi-manual network registration
2: Manual network registration (reference to mnc)
The mnc must be set correctly for 1 and 2!
Default value: 0
Min: 0
Max: 2
read/write: rw
Name: mnc
Description: Six-digit mobile network code, must be selected appropriately for operator and country
Default value:
Min:
Max:
read/write: rw
Name: rat
Description: 0: NB-IoT only
1: LTE-CAT-M1 only
2: NB-IoT Preference
3: LTE-CAT-M1 Preference
Default value: 0
Min: 0
Max: 53
read/write: rw
Name: tqm
Description: Time stamp q node function:
Packets that have not been sent are placed in a queue and transmitted the next time. A time stamp is also transmitted.
0: off
1: on
Default value: 0
Min: 0
Max: 1
read/write: rw
Name: gnss
Description: Localisation service
0: off
1: on
Default value: 0
Min: 0
Max: 1
read/write: rw
Name: agps
Description: Assisted GPS ephemeris data download when connected
0: off
1: on
Default value: 0
Min: 0
Max: 1
read/write: rw
Name: lper
Description: Time when the localisation service is triggered, in hours
Default value: 168
Min: 1
Max: 336
read/write: rw
Datahub and .json
It is possible to receive the packets from the sensors via the data hub. The sensors send to Sentinum's own backend via protocols such as MQTT-SN, LWM2M or CoAP and are then forwarded via the respective interface. You can choose between MQTT or REST as the interface, for example. You will receive the accesses with your respective delivery and your respective subscription plan. The data is determined via the respective interface in .json format. The meaning of the individual parameters can be found in the payload decoder or in the payload decoder tables of the respective sensors.