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

BLE_GAP_TIMEOUT_SRC_AUTH_PAYLOAD

Hello.
I have 3 peripherals connected to 1 central.
The BLE_GAP_EVT_TIMEOUT event occurs in Central.
Occurrence timing is random, p_ble_evt->evt.gap_evt.params.timeout.src is 0x03. This shows BLE_GAP_TIMEOUT_SRC_AUTH_PAYLOAD, but I'm not sure why it happens. BLE_GATT_OP_SIGN_WRITE_CMD is not used.
I would like to know what causes this timeout and how to handle it.

Thank you.

Parents
  • Hello,

    BLE_GAP_TIMEOUT_SRC_AUTH_PAYLOAD gets reported to the app if no encrypted data packets have been exchanged within a certain timeframe (8 minutes by default). So I would expect it to take at least 8 minutes before you receive this event on your Central.

    It may be expected for your devices to not exchange any data (or LE PIng) for longer periods of time. In that case, it should be ok to just ignore the BLE_GAP_TIMEOUT_SRC_AUTH_PAYLOAD event and keep the connection alive.

Reply
  • Hello,

    BLE_GAP_TIMEOUT_SRC_AUTH_PAYLOAD gets reported to the app if no encrypted data packets have been exchanged within a certain timeframe (8 minutes by default). So I would expect it to take at least 8 minutes before you receive this event on your Central.

    It may be expected for your devices to not exchange any data (or LE PIng) for longer periods of time. In that case, it should be ok to just ignore the BLE_GAP_TIMEOUT_SRC_AUTH_PAYLOAD event and keep the connection alive.

Children
Related