<aside> đź’ˇ Applicable to firmware versions: 1.1.0
</aside>
Register | Size (bytes) | Base | Description | Default Value | Range (Min- Max) | Comments |
---|---|---|---|---|---|---|
304 | 2 | 10 | PIN code | 0 | ||
(deactivate d) | ||||||
0 - 9999 | PIN code used with ATPIN command. Value 0 disables the PIN code. | |||||
306 | 1 | 10 | Product mode | |||
0 | 0: PARK | |||||
1: RUN | In PARK mode, the product is not using Radio. In RUN mode, the product will send/receive RF | |||||
uplinks/downlinks. |
Register | Size (bytes) | Base | Description | Default value | Min-Max Value | Comments |
---|---|---|---|---|---|---|
300 | 2 | 10 | Keep alive period | 8640 (24h) | 2 ... 65535 | X 10 seconds |
301 | 2 | 10 | Transmit period of data |
1 |  0 ... 65535 | Number of backups (history logs) to be done before sending a frame (thus defining the sending period). The value 0 is equivalent to disabling the periodic mode. | | 315 | 1 | 10 | Time zone offset | 0 | -12 … 14 | Defines the Time Zone offset from UTC (in hours). Must be defined for Daylight Saving Time management. | | 316 | 1 | 10 | Daylight Saving Time management | 0 | 0 … 1 | Only applicable to European countries. 0: disabled 1: enabled | | 318 | 1 | 10 | Timestamping |  0 |  0 … 1 | LoRaWAN only If enabled, add a time stamp in data frames. 0: disabled 1: enabled | | 319 | 1 | 10 | RTC calibration value | 0 | -100 … 100 | Allows for correcting a possible drift of the clock. In tenths of a second per day. | | 320 | 2 | 10 | History period |  1 |  1 ... 65535 | Number of readings to be performed before saving in the history logs The value 1 is equivalent to 1 backup per reading | | 321 | 2 | 10 | Sampling period | 1800 (1h) | 15 ... 65535 | X 2 seconds | | 322 | 2 | 10 | Alarm repetition period |  0 |  0 ... 65535 | If an alarm is active, this register allows the product to send periodically a reminder.  0: no repetition X sampling period (S321) | | 323 | 1 | 10 | Number of additional (redundant)samples per frame | 0 | 0…23 | Number of samples to be repeated in the next frame | | 324 | 1 | 10 | Sensors activation | 3 | 1: Sensor 1 2: Sensor 2 3: Both sensors | |
Register | Size (bytes) | Base | Description | Default value | Min-Max value | Comments |
---|---|---|---|---|---|---|
330 | 1 | 10 | Alarm type | 0(inactive) | 0: Inactive | |
1: Low threshold | ||||||
2: High threshold | ||||||
3: Both thresholds | ||||||
331 | 2 | 10 | High threshold value | 0 | -550 … 1550 | |
(-55°C to +155°C) | tenth of °C | |||||
332 | 1 | 10 | High threshold hysteresis | 0 | 0…255 | tenth of °C |
333 | 2 | 10 | Low threshold value | 0 | -550 … 1550 | |
(-55°C to +155°C) | tenth of °C | |||||
334 | 1 | 10 | Low threshold hysteresis | 0 | 0… 255 | tenth of °C |
Register | Size (bytes) | Base | Description | Default value | Min-Max value | Comments |
---|---|---|---|---|---|---|
340 | 1 | 10 | Alarm type | 0(inactive) | 0: Inactive | |
1: Low threshold | ||||||
2: High threshold | ||||||
3: Both thresholds | ||||||
341 | 2 | 10 | High threshold value | 0 | -550 … 1550 | |
(-55°C to +155°C) | tenth of °C | |||||
342 | 1 | 10 | High threshold hysteresis | 0 | 0…255 | tenth of °C |
343 | 2 | 10 | Low threshold value | 0 | -550 … 1550 | |
(-55°C to +155°C) | tenth of °C | |||||
344 | 1 | 10 | Low threshold hysteresis | 0 | 0 … 255 | tenth of °C |
Register | Description | Encoding | Details |
---|---|---|---|
201 | Spreading Factor (SF) by default (Read Only) | Decimal | Default: 12 |
Min/max: 7 to 12 | |||
Unit: None | |||
214 | LORA APP-EUI (first part – MSB) | Hexadecimal | Default: 0 |
Key encoded on 16 characters. Each register contains a part of | |||
the key. | |||
Used during the JOIN phase in OTAA mode | |||
E.g.: | |||
APP-EUI = 0018B244 41524632 | |||
• S214 = 0018B244 | |||
• S215 = 41524632 | |||
215 | LORA APP-EUI (second part – MSB) | Hexadecimal | Default: 0 |
Key encoded on 16 characters. Each register contains a part of | |||
the key. | |||
Used during the JOIN phase in OTAA mode | |||
E.g.: | |||
APP-EUI = 0018B244 41524632 | |||
• S214 = 0018B244 | |||
• S215 = 41524632 | |||
216 | LORA APP-KEY (first part – MSB) | Hexadecimal | Default: 0 |
Key encoded on 32-byte characters. Each of the 4 registers contains 8 characters. | |||
Used during the JOIN phase in OTAA mode | |||
E.g.: | |||
APP-KEY = 0018B244 41524632 0018B200 00000912 | |||
• S216 = 0018B244 | |||
• S217= 41524632 | |||
• S218=0018B200 | |||
• S219= 00000912 | |||
217 | LORA APP-KEY (second part – MID MSB) | Hexadecimal | Default: 0 |
Key encoded on 32-byte characters. Each of the 4 registers contains 8 characters. | |||
Used during the JOIN phase in OTAA mode | |||
E.g.: | |||
APP-KEY = 0018B244 41524632 0018B200 00000912 | |||
• S216 = 0018B244 | |||
• S217= 41524632 | |||
• S218=0018B200 | |||
• S219= 00000912 | |||
218 | LORA APP-KEY (third part – MID LSB) | Hexadecimal | Default: 0 |
Key encoded on 32-byte characters. Each of the 4 registers contains 8 characters. | |||
Used during the JOIN phase in OTAA mode | |||
E.g.: | |||
APP-KEY = 0018B244 41524632 0018B200 00000912 | |||
• S216 = 0018B244 | |||
• S217= 41524632 | |||
• S218=0018B200 | |||
• S219= 00000912 | |||
219 | LORA APP-KEY (fourth part – LSB) | Hexadecimal | Default: 0 |
Key encoded on 32-byte characters. Each of the 4 registers contains 8 characters. | |||
Used during the JOIN phase in OTAA mode | |||
E.g.: | |||
APP-KEY = 0018B244 41524632 0018B200 00000912 | |||
• S216 = 0018B244 | |||
• S217= 41524632 | |||
• S218=0018B200 | |||
• S219= 00000912 | |||
220 | LoRaWAN Options | Hexadecimal | Default: 5 |
Bit 0: Activation of the ADR ON(1)/OFF(0) | |||
Bit 1: Reserved | |||
Bit 2: DUTY CYCLE ON(1)/DUTY CYCLE OFF(0) | |||
Bits 3 & 4: Reserved | |||
Bits 5: CLASS C (1)/ CLASS A (0) | |||
Bits 6 to 7: Reserved | |||
CAUTION: | |||
Deactivation of the Duty cycle may result in a violation of the | |||
conditions of use of the frequency band, depending on the use of the device, thus violating the regulations in force. | |||
In the case of disabling the Duty cycle, liability is transferred to | |||
the user. | |||
221 | Mode of activation | Decimal | Default: 1 |
Choice: (see NOTE 1 after the table) | |||
• 0: ABP | |||
• 1: OTAA | |||
222 | LORA NWK_SKEY (first part – MSB) | Hexadecimal | Default: 0 |
The parameter is encoded in 16 bytes. 4 registers contain 4 bytes. | |||
223 | LORA NWK_SKEY(second part - MID MSB) | Hexadecimal | |
224 | LORA NWK_SKEY (third part - MID LSB) | Hexadecimal | |
225 | LORA NWK_SKEY(fourth part – LSB) | Hexadecimal | |
226 | LORA APP_SKEY (first part – MSB) | Hexadecimal | Default: 0 |
Parameter is encoded on 16 bytes, each register with 4 bytes. | |||
227 | LORA APP_SKEY(second part - MID MSB) | Hexadecimal | |
228 | LORA APP_SKEY (third part - MID LSB) | Hexadecimal | |
229 | LORA APP_SKEY(fourth part – LSB) | Hexadecimal | |
259 | Channels Plan (US/AU 915 only) | Decimal | Default: 0 |
Min/max: 0 to 8 | |||
Select the Sub Band to use by the device during the Join phase (the same Sub Band supported by the GW). | |||
0: the device uses all the supported channels: [0-63] in 125 kHz and [64-71] in 500 kHz | |||
1: the device will use only Sub Band n°1. Use the channels [0-7] in 125 kHz and a channel [65] in 500 kHz. | |||
… | |||
8: the device will use only Sub Band n°8. Use the channels [56-63] in 125 kHz and 71 in 500 kHz. | |||
CAUTION: | |||
Using one Sub Band may result in a violation of the conditions of use of the frequency band, depending on the use of the device, thus violating the regulations in force. | |||
In the case of using a value different to “0”, liability is transferred to the user. | |||
280 | NETWORK ID | Hexadecimal | Default: 0 Read only |
281 | DEVICE ADDRESS | Hexadecimal | Default: 0 |
NOTE 1: The “Over The Air Activation” (OTAA) mode uses a JOIN phase before being able to transmit on the network. This mode uses the APP_ EUI (S214 and S215) and APP_KEY (S216 to S219) codes during this phase to create the keys for network communication.
Once this phase is completed, the codes APP_sKEY, NWK_sKEY and DEVICE ADDRESS will be present in the corresponding registers. A new JOIN phase is started every time the device exits Command mode, a reset is performed, or the device is turned on.
Codes:
The “Activation by personalization” (ABP) mode has no JOIN phase; it transmits directly on the network using the codes NWK_sKEY (S222 to S225), APP_sKEY (S226 to S229) and DEVICE ADDRESS (S281) to communicate.
Codes:
Register | Size (bytes) | Base | Description | Default Value | Range (Min- Max) | Comments |
---|---|---|---|---|---|---|
303 | 1 | 10 | LoRaWAN Confirmed mode | |||
0 | ||||||
0-1 | 0: deactivation | |||||
1: activation | ||||||
312 | 4 | 10 | Maximum delay between 2 authentication attempts | |||
43200 (12h) | ||||||
60- | ||||||
2592000 | ||||||
X 1 second | ||||||
Period: 1 minute | ||||||
to 30 days | ||||||
313 | 2 | 10 | Weighting factor for initial authentication attempts | 1 | 1-65535 | |
314 | 1 | 10 | Number of tries for each authentication attempt | 10 (EU) | ||
72 (US/AU) | 1-255 |
Register | Size (bytes) | Base | Description | Default Value | Range (Min- Max) | Comments |
---|---|---|---|---|---|---|
307 | 2 | 10 | Sigfox Downlink period | 1440 (24h) | 0-65535 | X 1 minute |
⇒ Period: 1 min to 45 days | ||||||
317 | 1 | 10 | Sigfox Duty cycle (RC1 only) | 1 | 0-1 | 0: Duty cycle deactivated |
1: Duty cycle activated |
A configuration coherency check is made at the time of the backup. Cases where backups are refused because considered as inconsistent:
Cases refused | Description |
---|---|
(S330 = 3) && (S333 > S331) | CH1 : Low threshold > High threshold |
(S330 = 3) && ((S333 + S334) > (S331 - S332)) | CH1 : (Low threshold + Low hysteresis) > (High threshold - High hysteresis) |
(S324 = 2) && (S330 != 0) | CH1: Sensor not activated and alarm activated |
(S340 = 3) && (S343 > S341) | CH2 : Low threshold > High threshold |
(S340 = 3) && ((S343 + S344) > (S341 - S342)) | CH2 : (Low threshold + Low hysteresis) > (High threshold - High hysteresis) |
(S324 = 1) && (S340 != 0) | CH2: Sensor not activated and alarm activated |
Data with size greater than 1 byte will be transmitted MSB first. In LoRaWAN, frames are sent on port 1.
All frames sent by the product contain a status byte. Its format is identical for all IoT Adeunis products.
Alarm Status | Bit 7 to 5 | Bit 4 | Bit 3 | Bit 2 | Bit 1 | Bit 0 |
---|---|---|---|---|---|---|
Frame Counter | AppFlag2 | AppFlag1 | Timestamp | |||
Low Bat | Config | |||||
No Error | 0x00 to 0x07 | 0 | 0 | 0 | 0 | 0 |
Configuration done | 0x00 to 0x07 | 0 | 0 | 0 | 0 | 1 |
Low bat | 0x00 to 0x07 | 0 | 0 | 0 | 1 | 0 |
Timestamp | 0x00 to 0x07 | 0 | 0 | 1 | 0 | 0 |
AppFlag1 | 0x00 to 0x07 | 0 | 1 | 0 | 0 | 0 |
AppFlag2 | 0x00 to 0x07 | 1 | 0 | 0 | 0 | 0 |
The status byte provides two bits reserved for a specific use of each product (AppFlag1 and AppFlag2). For this product:
This frame is sent following the reception of a frame with code 0x01, or at the start of the product.