Calling sd_ble_gap_adv_stop() does not emit an on_adv_evt event

RE: Calling sd_ble_gap_adv_stop() does not emit an on_adv_evt event

Petter Myhre — Wed, 07 Dec 2016 08:09:10 GMT

Yes, that is the only time sd_ble_gap_adv_stop() will return NRF_ERROR_INVALID_STATE. You shouldn't get a BLE_GAP_EVT_TIMEOUT event (with timeout source BLE_GAP_TIMEOUT_SRC_ADVERTISING) if you have called sd_ble_gap_adv_stop().

If things are still unclear, or you have more questions please add them separately as new question. This is getting very cluttered.

RE: Calling sd_ble_gap_adv_stop() does not emit an on_adv_evt event

annapalu — Tue, 06 Dec 2016 16:43:39 GMT

Thanks for the answer,

the err_code is = NRF_ERROR_INVALID_STATE. only when an advertising stop occurs when the device is not in advertising? because if it occurs in other case maybe it's important don't ignore it.

the second question is the same, i use a gls example and i see that the advertising stop ( i don't see the board on the phone) when timeout occurs. I use the ble example and callstack is:

ble_stack_init();
softdevice_ble_evt_handler_set(ble_evt_dispatch);
ble_advertising_on_ble_evt(p_ble_evt);

Case : BLE_GAP_EVT_TIMEOUT,

starts the ble_advertising in slow mode and go in Idle mode. My question is, is there a way to stop the timer to avoid that the BLE_GAP_EVT_TIMEOUT arrived after i stop the advertising with command sd_ble_gap_adv_stop();

RE: Calling sd_ble_gap_adv_stop() does not emit an on_adv_evt event

Petter Myhre — Tue, 06 Dec 2016 15:12:19 GMT

If you call sd_ble_gap_adv_stop() when you are not advertising it will return NRF_ERROR_INVALID_STATE. Will something like this work for you:

uint32_t err_code = sd_ble_gap_adv_stop();
if(err_code == NRF_ERROR_INVALID_STATE)
{
    // Do nothing, timeout has occured
}
else
{
    APP_ERROR_CHECK(err_code);
}

It means that instead of examining the advertising module, and make the necessary modifications to it, you can just use the sd_* API directly, like sd_ble_gap_adv_start(), sd_ble_gap_adv_stop() and so on.

I don't understand your second question. If you have further questions I think you should add them separately.

RE: Calling sd_ble_gap_adv_stop() does not emit an on_adv_evt event

annapalu — Tue, 06 Dec 2016 14:48:39 GMT

it's simple to menage adv_stop OR timeout but if i want use both, i have a problem that one i stopped it with sd_ble_ga_adv_stop(), after the timeout expired and try to stop again the advertising and give an error. So two question

What's means " it is easier the sd *API directly "
How when the evt timeout arrived from softdevice the advertising is stopped, i don't see that in the loop Fast_slow_idle the function is called.

RE: Calling sd_ble_gap_adv_stop() does not emit an on_adv_evt event

Petter Myhre — Tue, 06 Dec 2016 14:41:49 GMT

I don't know what is better, I don't know what your application is. If you only want to start one type of advertising and stop it either with sd_ble_gap_adv_stop() or on timeout this is very simple to implement. Have you tried?

RE: Calling sd_ble_gap_adv_stop() does not emit an on_adv_evt event

annapalu — Tue, 06 Dec 2016 14:07:30 GMT

So do you think, that is better use only the command sd_ble_gap_adv_stop? Is there not a method to stopped the timeout to avoid that a new advertising_stop is called? thanks, Anna

RE: Calling sd_ble_gap_adv_stop() does not emit an on_adv_evt event

Petter Myhre — Tue, 06 Dec 2016 13:49:11 GMT

@annapalu Then you will have to modify the Advertising Module. Maybe it is easier to use the sd_* API directly?

RE: Calling sd_ble_gap_adv_stop() does not emit an on_adv_evt event

annapalu — Tue, 06 Dec 2016 13:22:55 GMT

Hi Petter,

if i want use both manually stop advertising and timeout stop advertising, how can i menage it? Because if i stopped manually the advertising, after start the timeout that send a IDLE_EVT_ADV and give an error ( obviously) because it is stopped preciously. thanks, Anna

RE: Calling sd_ble_gap_adv_stop() does not emit an on_adv_evt event

Boaz — Fri, 27 May 2016 13:54:52 GMT

Good answer! Its easy to forget that I can opt to not to use the advertising module at all. Cheers :)

RE: Calling sd_ble_gap_adv_stop() does not emit an on_adv_evt event

Petter Myhre — Thu, 26 May 2016 14:47:23 GMT

The Advertising Module can be used for many typical "Connectable Advertising" scenarios, but if you want other functionality you are free to modify it, or not use it at all.

You can set the advertising data with ble_advdata_set(), and then call sd_ble_gap_adv_start() with the parameters you like. Maybe you want to advertise forever, and always stop it manually with sd_ble_gap_adv_stop()?