Product Configuration Request Frame; Network Configuration Request Frame; Specific Register Value Request Frame - ADEUNIS Sigfox RC1 ANALOG Guide Utilisateur

sigfox RC1 ANALOG - Guide utilisateur / User guide version V2.0.1
E.g.:
• The product is running in the periodic mode
O S301 = 6 i.e. a periodicity of sending of frames of 60min, every hour or 24 times per day.
O S307 = 4, we wish to perform 4 downlink frames per day
O Result: The value of S301 gives us 24 frames per day that are divided by the value of S307 to obtain the result
of 6. Thus for all 6 Periodic frames the acknowledgment request will be transmitted thus enabling the network to
send a downlink frame.
• The product is running in the event mode
O S300 = 36 i.e. a periodicity of sending of frames of 360min, i.e. Every 6 hours or 4 times per day.
O Result: the acknowledgment request will be transmitted 4 times per day thus enabling the network to send a
downlink frame.
Caution: The configuration of the downlink frames has impacts on consumption and therefore on the life of the
product since it must then open listening windows and no longer be in standby. On the other hand, as the SIGFOX
network limits to 4 the number of downlink frames if the product configuration allows us to do a lot more, there
will be no more response from the network and the acknowledgment that the product is waiting for will not come.
4.2.1

Product configuration request frame

This frame allows to inform the product via the network that it must resend the product configuration uplink frame
(0x10).
0 1
Code
0x01 X
4.2.2

Network configuration request frame

This frame allows to inform the product via the network that it must resend the network configuration uplink frame
(0x20).
0 1
Code
0x02 X
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 regis-
ter 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
2 3
X X
2 3
X X
2 3
CONF ID2 CONF ID3
2 3
VALUE1 VALUE1
4 5
PAYLOAD
X X
4 5
PAYLOAD
X X
4 5
PAYLOAD
X X
4 5
PAYLOAD
VALUE2 VALUE3
6 7
X X
6 7
X X
... 7
X CONF ID7
... 11
VALUE3 X
Page 73 of 86
FR
EN