CC1352R: OAD very slow in beacon mode with large network

I tried with different Beacon intervals (our default = 6 for both beacon order and superframe order).

Lower values don't give better results but setting BO to 7 with SO = 5 improves the throughput, albeit also slower because of the large beacon interval.

No I'm trying to understand the best way to set all the relevant parameters for the optimum result.

I have OAD_BLOCK_SIZE    128 configured.

Could it help increasing this or will it have a too high chance of bit errors?

Hi Marijn, 

Which version of the SDK are you using? 

Which stack are you using? 

Which example are you using? 

Thanks, 
Elin

Hi Elin,

SDK 3.40 (we're upgrading to SDK4.30 which has the same issue)

15.4 stack

Project is based on DMM sensor 15.4 & BLE but BLE is paused in this scenario.

Hi Marijn, 

Thanks for sharing. 

Okay, so you are able to reproduce the issue using the latest SDK? 

What kind of modifications have you made to the project other than adding OAD? 

Thanks, 
Elin

Hi Elin,

As mentioned earlier, the SDK 4.30 has the same behaviour.

Our own application runs in separate threads and can easily be turned off and do not affect the OAD process.

Has TI done any OAD tests in beacon mode with 20+ devices in the network?

Hi Marijn, 

That's a good question. I'm unsure of how large networks we test, but I'll check with the team and get back to you as soon as I can. 

Thanks, 
Elin

Hi Elin,

And can you share some of the results/settings for those tests?

Hi Marijn, 

Unfortunately, I cannot disclose the full set of tests or the results. But rest assured that if we find any issues during testing, they are reported in bug tickets in our internal system. 

Thanks, 
Elin