• State Verified Answer
  • Replies 9 replies
  • Subscribers 62 subscribers
  • Views 9693 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 109828
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Central: multiple connection at the same time

Thierry

Hi,

I'm using S130 with PCA10028 and I would like to connect my central device to multiple peripheral at the same time.

According to my understanding, the only way I have to achieve this goal is to use whitelist. However, once the first device acknowledge my connect, scanning seems to stop and no more connections are done.

Is my understanding correct ? and if yes why ? Where come from this limitation ? (SDK, Bluetooth, hardware...)

Does I have any way to continue connection on other devices without recalling sd_ble_gap_connect again ?

Thanks for your support

Parents
  • 0

    I think you are talking about sd_ble_gap_scan_start. however, I'm talking about sd_ble_gap_connect which can be use in 2 way:

    • Either provide a peer address and it will connect to this specific peer address
    • or you can provide a whitelist and it will connect to the first device found in this list.

    I didn't find in the documentation the exact behavior of this function when we provide a whitelist (maybe I missed something) but I noticed this function will connect to the first device found then stop everything. What I expected when I found this function is to call sd_ble_gap_connect 1 time and receive many BLE_GAP_EVT_CONNECTED events for every devices specified in the whitelist.

    So, I just want to make sure if my understanding is correct and I would like to know if it's a BLE behavior or Nordic behavior ?

Reply
  • 0

    I think you are talking about sd_ble_gap_scan_start. however, I'm talking about sd_ble_gap_connect which can be use in 2 way:

    • Either provide a peer address and it will connect to this specific peer address
    • or you can provide a whitelist and it will connect to the first device found in this list.

    I didn't find in the documentation the exact behavior of this function when we provide a whitelist (maybe I missed something) but I noticed this function will connect to the first device found then stop everything. What I expected when I found this function is to call sd_ble_gap_connect 1 time and receive many BLE_GAP_EVT_CONNECTED events for every devices specified in the whitelist.

    So, I just want to make sure if my understanding is correct and I would like to know if it's a BLE behavior or Nordic behavior ?

Children
No Data
Related