[advertising stop]

RE: [advertising stop]

Sigurd — Wed, 14 Dec 2016 13:22:49 GMT

Q1: i think that the softdevice stops the timer when connection occurs.Correct?

A1: Correct.

Q2: And is there an api function to avoid that the timer will expire?

A2: No.

If you use sd_ble_gap_adv_stop() the timer and advertising is stopped, and you dont get BLE_GAP_TIMEOUT.

RE: [advertising stop]

annapalu — Tue, 13 Dec 2016 14:38:32 GMT

Ok, perfect. i think that the softdevice stops the timer when connection occurs.Correct? And is there an api function to avoid that the timer will expire? Because sometimes i want to stop the advertising not using a state machine ADV_MODE_FAST --> BLE_ADV_MODE_IDLE, but using a advertising_stop() api function(for example when i press the bottom) and in this case i would that the timers don't occurs. Thanks, so much

RE: [advertising stop]

Sigurd — Tue, 13 Dec 2016 14:32:33 GMT

Yes, the timer is stopped. The timer will not expire or timeout, and therfore you dont get the BLE_GAP_TIMOUT.

RE: [advertising stop]

annapalu — Tue, 13 Dec 2016 14:29:39 GMT

Ok, this is clear. But the my idea(maybe is wrong) is that when i set the options, ble_adv_fast_timeout = 30; a timer starts and when expires send a BLE_GAP_TIMEOUT. When the connection occurs, this timers is stopped by softdevice and BLE_GAP_TIMOUT is not getting?

RE: [advertising stop]

Sigurd — Tue, 13 Dec 2016 14:23:24 GMT

If your phone connects to the board, you will not get the BLE_GAP_TIMEOUT. Instead advertising is stopped by the softdevice, and you will get the event BLE_GAP_EVT_CONNECTED telling you that the phone has connected to the board.

RE: [advertising stop]

annapalu — Tue, 13 Dec 2016 14:03:36 GMT

Hi sigurd,

sorry i have another question ( hope the last). If the advertising starts and my board connect to the phone. the BLE_GAP_TIMEOUT doesn't occurs or it occurs and the connection state ignore it. How can i understand this procedure? Thanks.

RE: [advertising stop]

Sigurd — Mon, 12 Dec 2016 16:40:10 GMT

Yes, that is correct.

RE: [advertising stop]

annapalu — Mon, 12 Dec 2016 15:13:00 GMT

Perfect. Now it's all clear. So when the Advertising go in BLE_ADV_MODE_IDLE is the softdevice that worry to stop the advertising? Thanks.

RE: [advertising stop]

Sigurd — Mon, 12 Dec 2016 09:49:54 GMT

Yes, if you have not enabled the ADV_MODE_SLOW, only ADV_MODE_FAST, the advertising will stop when ADV_MODE_FAST timeouts(BLE_GAP_EVT_TIMEOUT). So ADV_MODE_FAST --> BLE_ADV_MODE_IDLE(advertising is stopped). ADV_MODE_SLOW is completely skipped.

RE: [advertising stop]

annapalu — Mon, 12 Dec 2016 09:45:36 GMT

Hi Sigurd,

thank you for the clear answer. I have only a last question. On the gls example, only the BLE_ADV_FAST is enable in the advertising_init(). But when the BLE_GAP_EVT_TIMEOUT occurs, the advertising go in slow mode and advertising stop. This is is possible, if in the advertising_init the slow advertising is not enable?

thanks, Anna

RE: [advertising stop]

Sigurd — Thu, 08 Dec 2016 14:06:27 GMT

Hi,

The function sd_ble_gap_adv_stop() is used to stop the advertising directly from your application code.

In the gls example you can choose to use ADV_MODE_FAST, ADV_MODE_SLOW or to use both. You can enable the different modes in the advertising_init() function with:

options.ble_adv_fast_enabled  = true;
options.ble_adv_slow_enabled =  true;

And you can set the timeout for the different modes with:

options.ble_adv_fast_timeout  = 30;
options.ble_adv_slow_timeout  = 180;

When the timeout happens, you will get the event BLE_GAP_EVT_TIMEOUT. If you are in ADV_MODE_FAST mode, it will switch to ADV_MODE_SLOW, and if you are in ADV_MODE_SLOW it will switch to BLE_ADV_MODE_IDLE and the SoftDevice will stop advertising. The function sd_ble_gap_adv_stop() is not used.

With the limited discoverable mode(BLE_GAP_ADV_FLAGS_LE_ONLY_LIMITED_DISC_MODE) it is not allowed to advertise longer than the timeout period. But if you don't want the advertising to stop, you can switch to general discoverable mode(BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE), and set the timeout to 0 to do unlimited advertising:

advdata.flags                 = BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE;
options.ble_adv_fast_timeout  = 0;