Advertisment not stopping

RE: Advertisment not stopping

endnode — Thu, 11 Jan 2018 12:42:27 GMT

Firstly if your Nordic device starts advertising right after disconnection then it is written as FEATURE in the firmware. If it is your firmware the you wrote it (or blindly used some library/black-box module, still it's your firmware). Secondly how does button relate to this? Don't mix topics, solve one by one and open new ticket if you have further (unrelated) questions.

RE: Advertisment not stopping

DMS — Thu, 11 Jan 2018 11:47:30 GMT

button event handle is not triggering , have any idea ?

RE: Advertisment not stopping

DMS — Thu, 11 Jan 2018 11:43:49 GMT

if connection is established between device, advertising stops . Soon after disconnecting it starts advertising. I want to stop advertising on some event occurance

RE: Advertisment not stopping

endnode — Thu, 11 Jan 2018 10:18:01 GMT

Once the connection is established, the advertising stops automatically. Even if you disconnect later there is no advertising running so nothing to be stopped. If you start it again then you can stop any time later. What part of this isn't your experience?

RE: Advertisment not stopping

DMS — Thu, 11 Jan 2018 10:14:44 GMT

Without out connecting and disconnecting , i am able to turn off advertising. When connection is established and later disconnected, then if i try to stop advertising i am not able to stop it.

RE: Advertisment not stopping

endnode — Thu, 11 Jan 2018 10:05:16 GMT

If you are using Nordic stack aka Soft Device there is no way it would "automatically" advertise unless you use API to request it. Once the connection is established the advertising stops automatically (that is required by BT SIG specification) meaning if you want to advertise along existing connection you need to start new advertising activity (GAP "slot"). However once connection ends the advertising isn't started unless you call sd_ble_gap_adv_start.

In case you get BLE_GAP_EVT_CONNECTED event then advertising is already stopped. If you try to stop it by AD API call then it will throw error back. So you either don't do it at all or (e.g. if you do this in some distant module - which is illogical but can be;) you need to set some global flag and not do it in case that connection is ongoing or you should be more careful how you assert return codes from that sd_ble_gap_adv_stop function call.