Dynamic multiprotocol support - how does it work with concurrent connection/scan or multiple connections?

[marmio]

Hey,

I have a few questions about dynamic multiprotocol BLE/Thread support.

1. Multiple BLE connections. If I have one connection and connection event length is set for 10% of connection interval Thread/BLE time ratio will be 90% to 10%. What with multiple connections? Does it sum up, with two it will be 80% to 20% and so on?

2. Concurrent scan and connection. Let's say I have a BLE connection with Thread /BLE ratio 90% to 10%. How does it work with additional scan? If want to scan with, let's say, scan interval of 50 ms and scan window of 25 ms, only scan takes 50% of time. Does it also sum with 10% for connection and in summary, it will be 60% for BLE and 40 for Thread? If yes, what are the safe proportions for that case?

Thanks in advance.

[MartinBL]

Hi,

Short answer: everything sums up. The radio is only able to do one task at a time. Hence, it is not possible to service two links in one "radio slot", or scan while at the same time servicing a link, etc. More details and recommendations about concurrent Thread/BLE link timings can be found here:

• BLE Scheduling 
• Thread Multiprotocol support

Best regards

Martin