max number of BLE connections limitation for S132 device

[kirill.neznamov]

Hi.

I am using nrf52832 SoC with s132 device (4.0.2).
Device is acting as peripheral, I have set max BLE connection limit to 1.

ble_cfg.gap_cfg.role_count_cfg.periph_role_count  = 1;
ble_cfg.gap_cfg.role_count_cfg.central_role_count = 0;
ble_cfg.gap_cfg.role_count_cfg.central_sec_count  = 0;
err_code = sd_ble_cfg_set(BLE_GAP_CFG_ROLE_COUNT, &ble_cfg, ram_start);



I would like to know what is specified behavior of S132 stack when somebody tries to connect when 1 connection is already established?
Must stack on peripheral's side to send disconnect packet with specified reason of disconnect in that case?

The issue for my case:
I have device nrf52832 and 2 mobile phones.

1. 1st mobile phone connects to device. -> all is ok
2. 2nd mobile phone tries to connect to device and connect process hangs forever.
3. if 1st mobile drops BLE connect, 2nd phone connected to device.

[kirill.neznamov]

This ticket duplicates the following
https://devzone.nordicsemi.com/f/nordic-q-a/34494/what-will-happen-if-somebody-will-connect-to-peripheral-which-has-already-1-ble-connection-established
So it can be closed.

[Vidar Berg]

Hi, 

The BT stack will not be aware of the second phone since it is not sending connectable advertisement packets as long as it is connected with the first phone (connect requests are sent in response to connectable advertisement packets). In other words, the 52 device will not be visible/available for other devices while connected.  

The second phone tries to scan for connectable advertisement packets from this device, but will not receive any. It would be the same case if the device was out of range. The phone app should probably scan for advertisement packets first to see if it can discover the device before attempting to connect to it.