Network-related settings

Available for firmware version 1.5 or later.

Join-retry period

SET

This command is used to set the period (T) of LoRaWAN join request sending from the device, in case it was unable to join the network from the first attempt.

Byte index	Hex value – Meaning
0	10 – The command code.
1	$T, [s] = XX * 5.$ Value 0x00 isn’t applicable. Default value: 0x78 * 5 = 600 sec = 10 minutes.

Example command: 0x10F0 – the server sets join request send period to 20 minutes.

GET

This command is used to get the period (T) of LoRaWAN join request sending from the device, in case it was unable to join the network from the first attempt. Server sends the command code and the response is sent together with the next keep-alive command.

Byte index	Sent request	Received response
0	19 – Command code.	19 – The command code.
1		XX – Network join retry period value. $T, [s] = XX*5$

Example command sent from server: 0x19;

Example command response: 0x19C6 => T = 0xC6*5 = 198*5 = 990s = 16.5 minutes.

This join retry period (T) must comply to LoRaWAN messages duty cycle. Otherwise the join request will be sent on the next attempt. In most of cases, min. acceptable value for T is 240s. Recommended are higher values, for less battery discharge, e.g. 480s.

This join retry period (T) is for the first 15 sent messages. After, the used LoRaWAN stack automatically changes the possibility to send join request to ~20 minutes for 20 network join attempts. If the device is still not joined to the network after these 20 attempts, next join request can be sent after ~3 hours and 15 minutes.

Communication Watch Dog

There is a Watch Dog functionality that forces the device to reset, so it can rejoin the network in case a certain threshold has been reached where no downlinks have been received. There are 2 independent threshold values, one for confirmed mode and one for unconfirmed mode.

When working in confirmed mode if no downlink is received for the period defined by the Watch Dog Period (WDPconfirmed) parameter (see table below), the device resets itself.

When working in unconfirmed mode if no downlink is received for the period defined by the Watch Dog Period (WDPunconfirmed) parameter (see table below), the device resets itself.

The command is described in the table below. The keep-alive in the response is omitted for clarity.

SET

Byte index	Hex value – Meaning
0	1C – The command code.
1	XX – Watch Dog Period (WDP) when confirmed uplinks are used by the device. XX defines how many uplinks should be received without ACK so that the device restarts. On top of that XX uplinks, another 7 minutes should pass before the device restarts. Default value for XX: 0x02. Note that value 0x00 disables the functionality when confirmed uplinks are used.
2	XX – Watch Dog Period (WDP) when unconfirmed uplinks are used by the device. Value is represented in hours. Default value for XX: 0x18. (24 hours) Note that value 0x00 disables the functionality when unconfirmed uplinks are used.

Example command, [Hex]: 1C0300 – Assuming that the Keep-alive period is 5 minutes, the device will wait for 3x5+7 = 22 minutes before resetting if confirmed uplinks are used. If unconfirmed uplinks are used the functionality is disabled (0x00).

GET

Byte index	Sent request	Received response
0	1D – Command code.	1D – The command code.
1		$WDP _{confirmed}$ value.
2		$WDP _{unconfirmed}$ value.

Example command, [Hex]: 1C020C – Assuming that the Keep-alive period is 5 minutes, the device will wait for 2x5+7 = 17 minutes before resetting if confirmed uplinks are used. If unconfirmed uplinks are used it will wait for 0C[HEX]=12[DEC] hours and reset.