stop Ble advertising

RE: stop Ble advertising

Ole Bauck — Mon, 08 Aug 2016 15:36:33 GMT

sd_app_evt_wait() will allow code in event handlers/interrupt (which includes app_timer) to run. You should add sd_app_evt_wait() in the while loop in main to make the device go to system on sleep mode between events and save power.

RE: stop Ble advertising

ALi — Mon, 08 Aug 2016 11:27:17 GMT

I know that And I use it, but I want to use this functions

sd_ble_gap_disconnect()
sd_ble_gap_adv_stop();
sd_app_evt_wait();

for putting my ble on low power and I use an app timer for scanning pins.

and I want to start advertising every 8 hours for 10 minutes. you think this plan is good and

sd_app_evt_wait();

doesn't stop app timer and wait for that events?

RE: stop Ble advertising

Ole Bauck — Mon, 08 Aug 2016 11:10:13 GMT

You can setup regular tasks using app_timer, take a look at this tutorial.

RE: stop Ble advertising

ALi — Mon, 08 Aug 2016 10:54:45 GMT

thank you so much. but I want to scan IO pin every 20ms, and I want to run only this function not BLE.

RE: stop Ble advertising

ALi — Mon, 08 Aug 2016 10:53:27 GMT

thanks. but how I can put BLE in very low Energy mode and just scanning some IO every 20ms and start BLE after 8 hours for 10 min advertising for send data?

RE: stop Ble advertising

Ole Bauck — Mon, 08 Aug 2016 09:39:13 GMT

You are sure you are not running into an error condition and reset? See this. sd_ble_gap_connect_cancel() is used during connection establishment, you should rather use sd_ble_gap_disconnect(). Also the order is wrong, this is the correct way to do it:

Disconnect
Wait for disconnect event (BLE_GAP_EVT_DISCONNECTED)
Stop advertising (the advertising module will start advertising on disconnect, see ble_advertising_on_ble_evt(..) function. Alternatively you can avoid start advertising).

RE: stop Ble advertising

Martin — Mon, 08 Aug 2016 08:27:27 GMT

the best shot you can take is use the WDT.

Here is an example, which wakesup after 60min

static uint16_t wdt_time = 3600; //3600 s = 60 min = 1 hr

     void wdt_init(void)
    {
    	NRF_WDT->CONFIG = (WDT_CONFIG_HALT_Pause << WDT_CONFIG_HALT_Pos) | ( WDT_CONFIG_SLEEP_Run << WDT_CONFIG_SLEEP_Pos);   //Configure Watchdog. a) Pause watchdog while the CPU is halted by the debugger.  b) Keep the watchdog running while the CPU is sleeping.
    	NRF_WDT->CRV = wdt_time*32768;             //wdt_time in s
    	NRF_WDT->RREN |= WDT_RREN_RR0_Msk;  //Enable reload register 0
    	NRF_WDT->TASKS_START = 1;           //Start the Watchdog timer
    }

So fater all your prozessing all you do is put the peripheral into sleep or system off. After 60 min the watchdog will fire and reset(!!!) the device, meaning you will lose all RAM data.

Hope this helps

Martin