TD next - Community

Hi,
I transmit a message with an acknowledgement request.
If the DL message is not received for some raisons, then I observe a residual current consumption bewond the duration of the downlink window.
Is there any way to make sure that the DL process is killed?
Thanks

There is no real "process" to kill: our system is a cooperative multi-threaded with no periodic premption performed by a supervisor triggered by an periodic timer like in desktop or server OSes or other RTOSes.

When you send an uplink frame with downlink request, the firmware will go to sleep mode for 20 s (counted from the end of the first uplink frame), consuming between 1 and 2 µA, then wake up and listen actively for incoming downlink frame for up to 25 s consuming 15 mA. If a frame is received, we have to wait around 2 s before sending back a OOB frame, then go back to sleep without any process running in the background of any kind.