Specific Register Value Request Frame; Frame For Updating The Value Of Specific Registers - ADEUNIS LoRaWAN 863-870 ANALOG PWR Guide Utilisateur

LoRaWAN 863-870 ANALOG PWR - Guide utilisateur / User guide version V2.0.2

4.2.3 Specific register value request frame

This frame (0x40) allows to inform the product via the network that it must send the values of specific registers in a uplink frame (0x31).
0 1
Code
0x40 CONF ID1
Description of the frame:
• Bytes 1 to N : CONF IDX (8bits): index of the register to be sent. The corresponding register is 300 + CONF IDX value. For example, if CONF
ID1 =0x14 (so 20 in decimal), the product will send back the value of register number 320.
The associated uplink frame has the code 0x31 (see paragraph 4.1.5).
0 1
Code
0x31 Status
In this example: CONF ID1 is a 2-byte register, CONF ID2 a 1-byte register and CONF ID3 a 2-byte register.
If an error is detected in the request, the returned 0x31 frame will be empty.
IMPORTANT : The user can specify several CONF IDs in his downlink frame but it is his responsibility to verify that according to the protocol the
size of the data available in a downlink frame will be large enough to contain all the desired data. Otherwise, the application will only send the
first values.

4.2.4 Frame for updating the value of specific registers

This frame (0x41) allows to change the value of requested registers.
0 1
Code
0x41 CONF ID1
Description of the frame :
• Byte 1: CONF ID1 (8bits) : index of the first register to change. The corresponding register is 300 + value of CONF IDX. For example, if
CONF ID1 = 0x14 (hexadecimal, so 20 decimal), the product will change the value of register number 320.
• Byte 2: value to assign to CONF ID1 : in this example, its value has a size of 1 byte
• Byte 3: CONF ID2 (8bits) : indice of the second register to change. The corresponding register is 300 + value of CONF IDX.
• Bytes 4 and 5: value to assign to CONF ID2 : in this example, its value has a size of 2 bytes
• ...
The product does not return any uplink frame following the reception of a downlink frame 0x41. However, the Config bit of the status byte (see
section 4.1.1.2) will be set to 1 in the next scheduled uplink frame (periodic or alarm or keep alive frame) if all was well done.
IMPORTANT: the value 0xFF for a CONF IDX will stop the reading of the downlink frame. Only the bytes preceding this value 0xFF will be taken
into account. This mechanism can be useful when you need to work in fixed downlink frame lengths and you do not want to use all available
bytes.
2 3
CONF ID2 CONF ID3
2 3
VALUE1 VALUE1
2 3
CONF ID1
CONF ID2
value
4 5
PAYLOAD
X X
4 5
PAYLOAD
VALUE2 VALUE3
4 5
PAYLOAD
CONF ID2 CONF ID2
value (MSB) value (LSB)
... n
X CONF IDn
... 11
VALUE3 X
... n
CONF IDn
...
value
Page 75 of 87
FR
EN