Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deep sleep blocking ACK for confirmed downlinks #36

Open
kickouille opened this issue Jan 26, 2021 · 0 comments
Open

Deep sleep blocking ACK for confirmed downlinks #36

kickouille opened this issue Jan 26, 2021 · 0 comments

Comments

@kickouille
Copy link

Hello,

When deep sleep is enabled, code is not allowing LMIC stack to TX an ACK on confirmed downloin messages.

Correct sequence would be:

  1. TX telemetry (uplink)
  2. RX some data (downlink confirmed)
  3. TX ACK for downlink
  4. Maybe RX for some other queued data (downkink)
  5. Going into deep sleep

What happens:

  1. TX telemetry (uplink)
  2. RX some data (downlink confirmed)
  3. 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... :)

Regards,

Yanik

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant