This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Sleep Immediately after Beacon Advertisement

I'm using the following code to make the beacon sleep:

static void on_ble_evt(ble_evt_t * p_ble_evt)
{
    uint32_t        err_code;
    switch (p_ble_evt->header.evt_id)
    {
        case BLE_GAP_EVT_CONNECTED:
        {
            break;
        }
        case BLE_GAP_EVT_TIMEOUT:
        {
            if (p_ble_evt->evt.gap_evt.params.timeout.src == BLE_GAP_TIMEOUT_SRC_ADVERTISING)
            {
                sd_ble_gap_adv_stop();
                ble_fsm_set_state(Ble_Fsm_State_Idle);
            }
            break;
        }
        default:
        {
            break;
        }
    }
}

Once the state is set to idle, the nrf51 chip goes to sleep and the current draw drops to the order of uA. My only problem here is that the minimum timeout value is 1s and this means that the chip is burning power for 1s. Ideally, I would like the beacon to just advertise once and then go to sleep immediately. What is the best way to do this? Adding a synchronous delay of 5 ms? Any callback that I can use instead?

Parents
  • What do you mean by "sleep"? I assume that nRF5x chip is going to POWER ON SLEEP (wait for event/interrupt) always when nothing is running on MCU so even between adv. events. If you mean POWER OFF state then sure you can do it but no BLE activity can be running during that time, you need to manage wake-up by some external GPIO interrupt line (button or some RTC capable chip if you expect to wake-up periodically).

  • Yes, you will need to do some more debugging and make sure HW is correct (probably trying some basic loop scenarios with special FWs and measure that characteristic) and then check SW (you probably run some busy-loop or similar heavy activity somewhere and it's most probably triggered by your code...) The guide from Nordic I've linked in one previous answer up this thread is answering many details, I have nothing to add to it.

    When it comes to general BLE knowledge I can recommend two sources:

    • original BLE training presentation from BT SIG (it's from 2010 so you need to understand that it covers only 4.0/4.1 but most of new features added in 4.2 and 5.0 are just expanding not changing the basic principles). I use it as quick reference till today.

    (1/2)

Reply
  • Yes, you will need to do some more debugging and make sure HW is correct (probably trying some basic loop scenarios with special FWs and measure that characteristic) and then check SW (you probably run some busy-loop or similar heavy activity somewhere and it's most probably triggered by your code...) The guide from Nordic I've linked in one previous answer up this thread is answering many details, I have nothing to add to it.

    When it comes to general BLE knowledge I can recommend two sources:

    • original BLE training presentation from BT SIG (it's from 2010 so you need to understand that it covers only 4.0/4.1 but most of new features added in 4.2 and 5.0 are just expanding not changing the basic principles). I use it as quick reference till today.

    (1/2)

Children
No Data
Related