Is it possible keep advertising when ancs connecting?

RE: Is it possible keep advertising when ancs connecting?

awneil — Fri, 03 May 2019 16:04:08 GMT

I had the same question, and came across this, but it's no good for SDK 15 - the advertising has changed significantly.

This one is for SDK 15:

https://devzone.nordicsemi.com/f/nordic-q-a/45644/how-do-i-simply-do-a-non-connectable-advert-on-nrf52-using-sdk-15

RE: Is it possible keep advertising when ancs connecting?

Petter Myhre — Wed, 14 Dec 2016 11:16:37 GMT

This behavior is expected.

RE: Is it possible keep advertising when ancs connecting?

frogofmagic — Tue, 13 Dec 2016 15:21:15 GMT

Yes , and other devices only can see advertising can't connect it.

RE: Is it possible keep advertising when ancs connecting?

Petter Myhre — Tue, 13 Dec 2016 12:47:51 GMT

So you are connected with a iPhone 6, you open LightBlue on that same iPhone 6? Then you only have one connection, and LightBlue is just using that.

RE: Is it possible keep advertising when ancs connecting?

frogofmagic — Tue, 13 Dec 2016 01:28:55 GMT

Hi Petter, I test it again, First time I connected with my iPhone6 and paired. Open Lightblue can see the advertising and also can connect it.( I think this should be normal?) But I tried my iPad air and failed to connect it.

I think iPhone6 still connected to nrf51822 and that's why Lightblue can connect it again.

RE: Is it possible keep advertising when ancs connecting?

Petter Myhre — Mon, 12 Dec 2016 10:59:54 GMT

Looks correct. You should only be able to do non-connectable advertising while you are in a connection, and you shouldn't be able to connect to non-connectable advertising. Are you saying that you are able to connect to it while you are connected to it? Or are you connecting with another device while you are connect to it? Please clarify.

RE: Is it possible keep advertising when ancs connecting?

frogofmagic — Mon, 12 Dec 2016 07:58:28 GMT

OK, after try and error, now it can advertising when ancs connecting... I'm not sure it's right or not, please help me check it~

1. Add another initial.

static void non_connectable_advertising_init(void)
{
    uint32_t             err_code;    
		ble_gap_adv_params_t adv_params;
		
		memset(&adv_params, 0, sizeof(ble_gap_adv_params_t));
		adv_params.type        = BLE_GAP_ADV_TYPE_ADV_NONCONN_IND ;
		adv_params.p_peer_addr = NULL;
		adv_params.fp          = BLE_GAP_ADV_FP_ANY;
		adv_params.interval    = 200 ;
		adv_params.timeout     = 0;
		adv_params.p_whitelist =NULL;
		
		err_code = sd_ble_gap_adv_start(&adv_params);
		APP_ERROR_CHECK(err_code);
		
}

And call this new function when connected.

static void on_ble_evt(ble_evt_t * p_ble_evt)
{
    uint32_t err_code = NRF_SUCCESS;

    switch (p_ble_evt->header.evt_id)
    {
        case BLE_GAP_EVT_CONNECTED:
            NRF_LOG_INFO("Connected.\r\n");
            err_code = bsp_indication_set(BSP_INDICATE_CONNECTED);
            APP_ERROR_CHECK(err_code);
            m_cur_conn_handle = p_ble_evt->evt.gap_evt.conn_handle;
            err_code = app_timer_start(m_sec_req_timer_id, SECURITY_REQUEST_DELAY, NULL);
            APP_ERROR_CHECK(err_code);
				
	        non_connectable_advertising_init();  //<===here.
            break; // BLE_GAP_EVT_CONNECTED

Now, it will keep advertising after connected. But...you can connect it again, I already set to BLE_GAP_ADV_TYPE_ADV_NONCONN_IND . Still don't know why still can connect.