-
Notifications
You must be signed in to change notification settings - Fork 3k
Lora: Fix TX_ERROR event if corrupted msg is received for CONFIRMED request #7767
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
Lora: Fix TX_ERROR event if corrupted msg is received for CONFIRMED request #7767
Conversation
…equest When node sends a CONFIRMED message and gateway sends ACK in RX1 window but the message gets corrupted during the transmission (e.g. MIC fails), currently our stack already checks for retransmission after RX1 and if retries attemps are exhausted, TX_ERROR event is sent to application. This is wrong as MAC layer will still attempt reception in RX2 window. This commit fixes the behaviour so that TX_ERROR is not sent until RX2 window has been closed.
@hasnainvirk @AnttiKauppila @kjbracey-arm please review |
This is fix for #7718 |
@cmonr This needs CI. Failure is not related to the PR. |
/morph build |
Build : SUCCESSBuild number : 2838 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 2466 |
Test : SUCCESSBuild number : 2589 |
/morph uvisor-test |
…er_msg_received Lora: Fix TX_ERROR event if corrupted msg is received for CONFIRMED request
Description
When node sends a CONFIRMED message and gateway sends ACK in RX1 window but the
message gets corrupted during the transmission (e.g. MIC fails), currently
our stack already checks for retransmission after RX1 and if retries attemps are
exhausted, TX_ERROR event is sent to application. This is wrong as MAC layer
will still attempt reception in RX2 window.
This commit fixes the behaviour so that TX_ERROR is not sent until RX2 window
has been closed.
Pull request type