RE: Concurrent actions BLE s130 SDK 11

Ulrich Myhre — Fri, 13 May 2016 07:45:17 GMT

To add to this: Apart from the few things we state that you shall not do, no operations should crash the SoftDevice. Instead, the SoftDevice will return an error code stating that something went wrong. So all operations should be safe, but it is possible to lose performance and efficiency by not being careful.

All the links are also independent, so any write operation on link 1 will never affect what you can call on link 2. But it can affect performance and throughput.

RE: Concurrent actions BLE s130 SDK 11

run_ar — Thu, 12 May 2016 12:47:37 GMT

As soon as a connection is established it's ok to use this link. The scheduler will handle conflicts between the existing connection and scanning. In case a packet is dropped in a connection due to scanning, it will be retransmitted in the next connection event, if the packet is dropped multiple times and you get closer to the connection supervision timeout the priority of the link will be increased to avoid dropping the connection. But it's still a good idea to make sure scan intervals and connection intervals doesn't interfere each other. You can take a look at the scheduler chapter in the Softdevice specification for more details on this.