s130-0.5.0 disconnect when central fail to connect another central

[bingo]

there are 3 modules to test(A1,B1,C1)

---

*2. A1 connect with B1(B1 is master, A1 is slave), C1 is power off, B1 as slave attempt to connect C1 with BLE_GAP_ADV_TYPE_ADV_IND(Connectable undirected), get BLE_GAP_EVT_TIMEOUT, src is BLE_GAP_TIMEOUT_SRC_ADVERTISING, connection between A1 and B1 still alive

*3. A1 connect with B1(B1 is master, A1 is slave), C1 is power off, B1 as slave attempt to connect C1 with BLE_GAP_ADV_TYPE_ADV_DIRECT_IND(Connectable directed), get BLE_GAP_EVT_TIMEOUT, src is BLE_GAP_TIMEOUT_SRC_ADVERTISING, but connection between A1 and B1 is terminated

*4. A1 connect with B1(B1 is master, A1 is slave), C1 is power on, B1 as slave can connect C1 with BLE_GAP_ADV_TYPE_ADV_IND or BLE_GAP_ADV_TYPE_ADV_DIRECT_IND, after this, connection between A1 and B1 still alive

after use s130-1.0.0

---

but issue (2.3.4) remained

thanks.

[bingo]

Hi Petter, as you understand, 3 is not expected behaviour. I think connection between A1 and B1 shounld not terminated. Here is the list of connection parameters between A1 and B1: conn_params.min_conn_interval = 10; conn_params.max_conn_interval = 20; conn_params.slave_latency = 0; conn_params.conn_sup_timeout = 100;

I will add issue 1 as a separate question, sorry for the inconvenience.Thank you for your response.