Class C confirmed retry settings

comori
Tue, 04 Feb 2025 20:08:19 +0000
The Things Stack v3

Hi All,

Setup:

TTS Cloud Standard

RAK Gateway

RAK End Node

Situation:
I am experimenting with confirmed Class C downlinks, and am trying to understand the available setting for confirmed retries and timeouts.

In this info page it states that

If the Application Server has received the downlink nack message, no action is required, because the Application Server will try to resend the downlink on its own. However, if the Application Server has not received the downlink ack/nack , it can not decide on its own if it should retry the downlink.

Under what condition does the application server receive a downlink nack? Is this based on the Class C timeout setting in the end node Network Layer settings?

i.e., once the timeout is reached, the application server receives a downlink nack to retry?

Furthermore, how many times is this retried? Is this based on the application server setting as.downlinks.confirmation.default-retry-attempts, which defaults to 8?

Thanks in advance!

1 post - 1 participant