Peripheral device: non-connectable advertisement while in a connected state

RE: Peripheral device: non-connectable advertisement while in a connected state

Locky — Wed, 18 Mar 2015 00:19:26 GMT

Cool, glad to help.

RE: Peripheral device: non-connectable advertisement while in a connected state

Pektusin — Tue, 17 Mar 2015 23:07:06 GMT

This is a great news, thanks! I saw a post here mentioning 8 simultaneous connections, so if it is related, then perhaps I could have up to 7 beacons if I needed :-)

Regarding on disconnect trigger, this a good hint! I want to keep the device connectable after it disconnects. In the current implementation my device just resets starting the default connectable advertising over again, but at some point I will want not to reset and keep the state, variables etc.

RE: Peripheral device: non-connectable advertisement while in a connected state

Locky — Tue, 17 Mar 2015 21:44:57 GMT

This is allowed in the S110 stack (at least from v7.0 and later). You simply have to reset the Advertising Data to Non-connectable and start advertising. Its quite simple to set up.

ble_gap_adv_params_t * adv_params

adv_params->type = BLE_GAP_ADV_TYPE_ADV_NONCONN_IND

However just make sure on Disconnect you trigger to set Advertising to Connectable or else you essentially Connect Brick the peripheral