Frame For Updating The Value Of Specific Registers - ADEUNIS sigfox RC1 Pulse Guide Utilisateur
Masquer les pouces
Voir aussi pour sigfox RC1 Pulse:
- Guide utilisateur (47 pages) ,
- Guide utilisateur (52 pages) ,
- Guide utilisateur (86 pages)
Table des Matières
Publicité
Les langues disponibles
Les langues disponibles
sigfox RC1 Pulse - Guide utilisateur / User guide version V2.0.2
0
Code
0x31
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
frst values.
4.2.5 Frame for updating the value of specific registers
This frame (0x41) allows via the network to change the value of requested registers.
EN
Frame 0x41 :
0
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 = 20, 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) : index 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 and 0x43. 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.
1
2
Status
VALUE1
1
2
CONF ID1
value
3
4
PAYLOAD
VALUE1
VALUE2
3
4
PAYLOAD
CONF ID2
CONF ID2
value (MSB)
5
...
VALUE3
VALUE3
5
...
CONF ID2
...
value (LSB)
11
X
7
CONF IDn value
Page
92
of 104
Publicité
Table des Matières
