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

ble_event_id 0x1b

hello, Starting nRF 52832 (s 132), leaving idle, after 3 minutes, ble_event_id 0x1b will occur, then BLE communication will be impossible. When ble_event_id is 0x1b, how should we deal with it? (ble_evt_t->header.evt_id)

thank you

Parents
  • Hi,

    The default advertising time is 180 seconds(3 minutes):

    #define APP_ADV_TIMEOUT_IN_SECONDS      180
    

    If you have not connected to a central after 180 seconds, you get the advertising timeout event(BLE_GAP_EVT_TIMEOUT == 0x1B), and the default behavior after that is that the chip goes into sleep mode to save power.

    How to deal with this? Either

    1. Connect with a central within 180 seconds, or
    2. Trigger a wake-up event to exit sleep-mode (e.g. press one of the buttons on the DK) to do another 180 seconds of advertising, or
    3. Do unlimited advertising(no timeout after 180 seconds, see this thread).
Reply
  • Hi,

    The default advertising time is 180 seconds(3 minutes):

    #define APP_ADV_TIMEOUT_IN_SECONDS      180
    

    If you have not connected to a central after 180 seconds, you get the advertising timeout event(BLE_GAP_EVT_TIMEOUT == 0x1B), and the default behavior after that is that the chip goes into sleep mode to save power.

    How to deal with this? Either

    1. Connect with a central within 180 seconds, or
    2. Trigger a wake-up event to exit sleep-mode (e.g. press one of the buttons on the DK) to do another 180 seconds of advertising, or
    3. Do unlimited advertising(no timeout after 180 seconds, see this thread).
Children
No Data
Related