Sending IBeacon and connectable advertising in parallel

RE: Sending IBeacon and connectable advertising in parallel

Vidar Berg — Thu, 18 Oct 2018 13:02:44 GMT

Hi Christian,

Yes, based on the API documentation this should work, but have not verified it myself.

Best regards,

Vidar

RE: Sending IBeacon and connectable advertising in parallel

Christian Waldmann — Thu, 18 Oct 2018 12:57:21 GMT

Hi Vidar

Using your answer, the following should work:

init IBeacon advertising with short timeout
start IBeacon advertising
-> wait for event BLE_GAP_EVT_ADV_SET_TERMINATED

init connectable advertising with short timeout
start connectable advertising
-> wait for event BLE_GAP_EVT_ADV_SET_TERMINATED

init IBeacon advertising with short timeout
start IBeacon advertising
-> wait for event BLE_GAP_EVT_ADV_SET_TERMINATED

init connectable advertising with short timeout
start connectable advertising
-> wait for event BLE_GAP_EVT_ADV_SET_TERMINATED

and so on....

Can you confirm this

Happy coding
Christian

RE: Sending IBeacon and connectable advertising in parallel

Vidar Berg — Thu, 18 Oct 2018 11:46:37 GMT

Hi,

Number of advertisement sets is currently limited to one, hence the NO_MEM error when you try to add a new set with sd_ble_gap_adv_set_configure. The terminated event will be triggered on advertisment timeout if you have enabled it, see duration/max_adv_evts in ble_gap_adv_params_t.

It is possible to update the advertisment payload on the fly. The limitation is that you have to use the same adv. parameters for both modes (ble_gap_adv_params_t). We introduced a new API in the advertisment module in SDK 15.2.0 that does exactly this, see ble_advertising.c->ble_advertising_advdata_update().

Alternatively, you can use the terminated event to switch "modes". This approach would allow you to use different advertisement intervals for the ibeacon and the connectable packets.

The init->start->stop sequence will also work.

Vidar