Indicating advertisement with a timer

RE: Indicating advertisement with a timer

ps_anu — Thu, 28 Feb 2019 09:13:05 GMT

how to set the flag insid the connected /disconnected event ,how to start advertise using timer

RE: Indicating advertisement with a timer

erltot — Fri, 26 May 2017 14:12:40 GMT

Hi, great!

I'll try it and let you know.

RE: Indicating advertisement with a timer

Hung Bui — Wed, 24 May 2017 11:45:50 GMT

Hi Erltot,

It was a bug in app_timer in SDK v12. It seems to be fixed in SDK v13. Could you try to test using SDK v13 ?

RE: Indicating advertisement with a timer

Hung Bui — Tue, 23 May 2017 08:53:09 GMT

Hi Erltot,

Just an update, it's most likely a but with the app timer. We are still investigating it. It must be an issue of starting and stopping the app timer inside an interrupt handler. There are some is a quick workaround to only start/stop a flag (variable) inside the Connected / Disconnected event and then in your main loop in main() you actually start/stop the timer accordingly to the flag. Using app scheduler with the app timer should also fix the issue.

I will keep you updated when we find the root cause.

RE: Indicating advertisement with a timer

erltot — Tue, 23 May 2017 08:27:42 GMT

Great! Yes, that was a minor mistake when building the simplified version. The flag is cleared in the actual appliaction. Awesome, I look forward to it. If you see something else that is funny please let me know, I am still learning :)

RE: Indicating advertisement with a timer

Hung Bui — Fri, 19 May 2017 16:17:56 GMT

Hi Erltot,

I had a look at your code , seems that you don't clear ble_connected when you receive DISCONNECTED event ?

However, I did see the issue as you described. The timer didn't start right away after disconnection but delayed a little bit. I will do more investigation and get back to you.

RE: Indicating advertisement with a timer

erltot — Fri, 19 May 2017 12:21:15 GMT

Try this: https://ufile.io/exupu

RE: Indicating advertisement with a timer

Hung Bui — Fri, 19 May 2017 11:09:16 GMT

Could you please try to create a small simplified version of your application that can reproduce the issue and update here so that I can test here ?

RE: Indicating advertisement with a timer

erltot — Fri, 19 May 2017 10:29:02 GMT

Exact same effect occur upon disconnect when I start the timer from

static void on_ble_evt(ble_evt_t * p_ble_evt)

switch (p_ble_evt->header.evt_id)

  case BLE_GAP_EVT_DISCONNECTED:

Could there be some constraints of simulateous timers running that I have missed?

Edit: Formatting the code is a pain, I hope you understand

RE: Indicating advertisement with a timer

Hung Bui — Thu, 18 May 2017 13:40:11 GMT

I would suggest to start your m_advertisement_indicator timer outside of BLE_ADV_EVT_FAST. Try to start it when you start advertising in main.c and when you disconnect. I don't think softdevice would block it. It can delay it for a few ms but not blocking it and have the "rubberband effect"

RE: Indicating advertisement with a timer

erltot — Thu, 18 May 2017 08:02:12 GMT

I use repeated mode, which i call once before the big while

err_code = app_timer_create(&m_advertisement_indicator, APP_TIMER_MODE_REPEATED, advertisement_indicator);

APP_ERROR_CHECK(err_code);

I start the timer for the first time in on_adv_evt switch shown above, and I stop it in the p_ble_evt switc in the BLE_GAP_EVT_CONNECTED case:

err_code = app_timer_stop(m_advertisement_indicator);

APP_ERROR_CHECK(err_code);

Sorry, I can't attach the full code

I added a print to RTT in the advertisement_indicator event and noticed it seems to be a rubberband effekt going on, after a while the timer starts but the prints all came simultanously.. Could it be the soft device blocking the event from running, and when it finally runs it executes several times?

RE: Indicating advertisement with a timer

Hung Bui — Tue, 16 May 2017 14:43:32 GMT

Seems like app_timer_start() called but the timer is not really started ? Have you set the timer with APP_TIMER_MODE_SINGLE_SHOT mode ? Please attach your full code.

RE: Indicating advertisement with a timer

erltot — Tue, 16 May 2017 12:44:38 GMT

In the breakpoint I get in ble_advertising_start() is BLE_ADV_MODE_DIRECTED as you suggested.

I tried adding both (not at the same time)

case BLE_ADV_MODE_DIRECTED:

case BLE_ADV_EVT_DIRECTED:

just above the other case in my on_adv_evt, it didn't do much...

When I checked the ble_adv_evt in the event when I disconnect it shows BLE_ADV_EVT_FAST.. I don't understand why does the other parts under the case for BLE_ADV_EVT_FAST get executed and not the timer?

RE: Indicating advertisement with a timer

Hung Bui — Mon, 15 May 2017 14:18:40 GMT

@Erltot: Please add a break point inside ble_advertising_start() and check which advertising mode is entered after the device disconnect. on_disconnected() will be called after the connection is Disconnected.

RE: Indicating advertisement with a timer

Hung Bui — Fri, 12 May 2017 10:56:58 GMT

Hi Erltot,

Which example and SDK are you testing on ?

Note that when we disconnected from the central, we may start with ADV_MODE_DIRECTED instead of BLE_ADV_MODE_FAST. That's why you may not receive the timeout from the timer.