When deep sleep is enabled, code is not allowing LMIC stack to TX an ACK on confirmed downloin messages.
Correct sequence would be:
TX telemetry (uplink)
RX some data (downlink confirmed)
TX ACK for downlink
Maybe RX for some other queued data (downkink)
Going into deep sleep
What happens:
TX telemetry (uplink)
RX some data (downlink confirmed)
Going into deep sleep
So it goes into deep sleep too early. It sould not be based on the fact that a message has been sent, but rather on the fact that LMIC process is complete. Not sure how to do that honestly as LMIC stack is quite obscure to me.
But at least I wanted to point that out if anyone else is pulling hairs like I just did in the recent hours... :)
Hello,
When deep sleep is enabled, code is not allowing LMIC stack to TX an ACK on confirmed downloin messages.
Correct sequence would be:
What happens:
So it goes into deep sleep too early. It sould not be based on the fact that a message has been sent, but rather on the fact that LMIC process is complete. Not sure how to do that honestly as LMIC stack is quite obscure to me.
But at least I wanted to point that out if anyone else is pulling hairs like I just did in the recent hours... :)
Regards,
Yanik