[riot-notifications] [RIOT-OS/RIOT] net/gnrc_lorawan: implement unconfirmed uplink redundancy (#15946)

Akshai M (Augustus Diode) notifications at github.com
Tue Jul 20 14:56:51 CEST 2021


Tested with Chirspstack and it seems to fail. Here are the results.

1. OTAA/ Unconfirimed Messages / Redundancy set to 3.
Result : Node retransmits on different frequencies but occasionally on the same frequency. This seems to against the standard which states 

> Line 681 : The end-device performs  frequency  hopping  as  usual  between  repeated  transmissions,  it does wait after each repetition until the receive windows have expired

2. :heavy_check_mark: Link Check option set /  Redundancy set to 3.
Result : No retries.

<Details>

![no_retries](https://user-images.githubusercontent.com/5170658/126322896-9426b046-e246-4247-a4c7-745f0446a176.png

</Details>

3. :x: ABP Mode ( fake keys) /  Redundancy set to 3/ Unconfirmed uplinks

The device sends uplinks on the same channel

<Details>

![redundancy_ABP](https://user-images.githubusercontent.com/5170658/126326541-b67c94d8-c391-413d-9062-a00b850d0d62.png)

</Details>


4. :x: ABP Mode ( fake keys) /  Redundancy set to 3/ Confirmed uplinks

The device continues to retry uplinks.

<Details>

![unconfirmed_abp](https://user-images.githubusercontent.com/5170658/126327187-9acabda1-11c0-48e5-9591-8efa68e266a1.png)

</Details>




-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/15946#issuecomment-883370407
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20210720/f9f76730/attachment.htm>


More information about the notifications mailing list