Hello,
I am noticing something curious when I attempt beacon mode for my nRF52 (sdk 12.1). Attached is an image of ubertooth packets that correctly show my ADV_NONCONN_IND packets, but then immediately it detects ADV_IND packets coming from the same device which are open to scan requests and scan responses. I followed the Power profiling tutorial to setup beacon mode, and I am curious why those ADV_IND packets are slipping in. I would like to save that battery power not responding to scan requests. Has anyone else seen this before?
BTW, here is how I set up my beacon mode advertising:
sd_ble_gap_adv_stop();
... init data
advertising_init(advdatabuf, ADVDATABUF_SIZE, APP_BCN_ADV_INTERVAL, APP_BCN_ADV_TIMEOUT_IN_SECONDS);
memset(&m_adv_params, 0, sizeof(m_adv_params));
m_adv_params.type = BLE_GAP_ADV_TYPE_ADV_NONCONN_IND;
m_adv_params.p_peer_addr = NULL;
m_adv_params.fp = BLE_GAP_ADV_FP_FILTER_BOTH;
m_adv_params.interval = APP_BCN_ADV_INTERVAL;
m_adv_params.timeout = APP_BCN_ADV_TIMEOUT_IN_SECONDS;
NRF_LOG_INFO("Beacon triggered\r\n");
err_code = sd_ble_gap_adv_start(&m_adv_params);
APP_ERROR_CHECK(err_code);
Thank you! Josh
