Keep Alive; Reply Frame To A Register Value Request In A Downlink Frame; Response Frame Following An Update Of Register(S) Via Downlink - ADEUNIS ARF8276A Guide Utilisateur

LoRaWAN Smart Building MOTION - Guide utilisateur / User guide version V1.0.0

4.1.5 Keep alive

This frame (0x30) is transmitted at the frequency defined by the register 300 only if no periodic data is defined or in alarm mode on a threshold
overflow (S301 = 0).
0 1
Code Status
0x30 Cf Status
0x30 0xA3
Its size is 2 bytes. It contains only the code byte (0x30) and the status byte.

4.1.6 Reply frame to a register value request in a downlink frame

Following reception of a downlink frame with the code 0x40, the frame 0x31 is transmitted (see section 4.2.4). It contains all the values of the
registers requested in the downlink frame 0x40.
0 1
Code Status
0x31 See Statut VALUE 1
In this example: the value 1 in response to CONF ID1 is a 2-byte register, the value 2 in response to CONF ID2 is a 1-byte register and 3 in
response to CONF ID3 is a 2-byte register.
If an error is detected in the request, the returned 0x31 frame will be empty.
Note: the size of the data registers defined by the fields "CONF ID1", "CONF ID2", "CONF ID3", "etc.", is variable depending on the registry
number. Refer to the list of registers (see section 3.4.1) to determine the size of each one and to deduce the total size of the data returned by
the 0x31 frame.

4.1.7 Response frame following an update of register(s) via downlink

Following reception of a downlink frame with the code 0x41, the frame 0x33 is transmitted (see paragraph 4.2.5 for details). It shows whether
the downlink frame (0x41) has been received and gives information on the support status of the latter.
Note: the data size "CONF ID 1 VALUE", "CONF ID 2 VALUE", "etc." is set to a variable byte number according to the register number. Refer to
the list of registers in paragraph 3.4.1 to determine the size of each register.
0 1
0x33 Status Request
byte status
CAUTION: if the request 0x41 concerns several registers, the device will stop the analysis of the Downlink request at the first error and will send
the Status frame with the reason and the identifier of the register concerned.
Request status:
- 0x01: success => device restart as a result of this request
- 0x02: error - no update
- 0x03: error - coherence
- 0x04: error - invalid register
- 0x05: error - invalid value
- 0x06: error - truncated value
- 0x07: error - unauthorized access
- 0x08: error - device defect
In the event of an error, if a partial reconfiguration has taken place before the error was detected, the device restarts and returns to its last valid
configuration. As a result, you will have to configure the device again with the new data.
Registry ID: Indicates to the user the registry that caused the error (only if "Request Status" is different from 0x01).
2 3 4
PAYLOAD
VALUE 1 VALUE2
2 3-4
Register ID
5 ... 11
VALUE3 VALUE3 X
FR
EN
Page 73 of 86