This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC2642R: How the BLE stack handles retries in case of unstable communication

Part Number: CC2642R

In case of BLE connection is not stable due to noise/interference, how the BLE stack in peripheral handles the connection?

Let's say the connection is already established and the communication has become unstable. Whether the peripheral or central disconnect the connection before Supervision Timeout? 

If both entities (central and peripheral) waits for Supervision timeout before disconnection, how the BLE stack handles retires? What is the frequency of communication retires? Which BLE stack layer handles it and whether it is configurable?

  • Hi,

    TI's BLE stack follows the BLE specifications.

    When in the connection, if a connection event is missed (packet not received or invalid), the devices wait until the next connection event to retry the transmission. As a result, by modifying the connection interval, you can modify the delay between the retries.
    The devices will try to transmit at each connection event (i.e. retry) until the supervision timeout is expired.

    I hope this will help,

    Regards,