Connecting to peripheral (Central role) prevents correct advertising/connectibility (Peripheral role)

RE: Connecting to peripheral (Central role) prevents correct advertising/connectibility (Peripheral role)

Petter Myhre — Fri, 03 Jun 2016 11:53:00 GMT

Thank you for the feedback, I will forward it.

RE: Connecting to peripheral (Central role) prevents correct advertising/connectibility (Peripheral role)

puz_md — Fri, 03 Jun 2016 11:39:43 GMT

Too bad, this will make my implementation quite ugly and complicated. But thanks for the feedback.

In this case, I want to suggest a new feature for future SoftDevices: Someting like sd_ble_gap_scan_with_optional_low_priority_connect() where you may attach a whitelist to the scan command and scheduler priority remains at the scan level.

RE: Connecting to peripheral (Central role) prevents correct advertising/connectibility (Peripheral role)

Petter Myhre — Fri, 03 Jun 2016 11:30:27 GMT

I believe this a expected behavior. The exact scenario is not described in Chapter 16 in the S132 SDS v2.0, but it says

The inititator is scheduled asynchronously to any other role (and any other timing-activity)and assigned higher priority to ensure faster connection setup.

On your related question the answer is unfortunately no.