Timeslot-API: how to minimize the effect of BLE

[rgrr2]

Hello,

in our device we use the Timeslot API to share a 802.15.4 based protocol with BLE, softdevice is S140 6.1.1.

Problem: the 802.15.4 protocol misses appr 10% of the slots it is requesting even if BLE is just advertising.  I assume that this is because the Softdevice is doing some internal tasks.

When BLE is switched off, this ratio is around 2.5%, which is not perfect but would be ok.

My goal is to have BLE and 802.15.4 in parallel, unfortunately the 10% slot misses are not acceptable.

So I started to play around with BLE parameters, esp. sd_ble_gap_ppcp_set() and the advertising rate via sd_ble_gap_adv_set_configure().  But actually there is no change in the slot misses, it's always around 10% if BLE is enabled.  No matter if the BLE intervals are reduced or increased.

I'm wondering if I'm missing a point and if there is a way to reduce the number of timeslots the Softdevice is requiring on its own.

Thanks for any suggestion.

Kind regards

Hardy

[Edvin]

There are examples that uses thread and zigbee only, without BLE. In those cases the softdevice is not flashed, and the timeslots are not required. I am not completely sure how it works if you run the BLE+thread/zigbee examples and don't start any BLE activity. I guess that the 802.15.4 stack would still request timeslots, but as the softdevice is not doing anything else, it will always accept them.

Best regards,

Edvin