RTOS/CC2640R2F: [BLE5][CC2640R2]Simple central detected disconnection

I suppose so and I believe you will find these resources useful:

Hi Ivan,

Please note that the connection interval also limits what supervision timeout you can use. Can you verify with a sniffer, what parameters are negotiated over air? If the central detect disconnect after 8 seconds, I suppose the supervision timeout is 8s.

As the documentation outlines;

Supervision Time-out: This time-out is the maximum amount of time between two successful connection events. If this time passes without a successful connection event, the device terminates the connection and returns to an unconnected state. This parameter value is represented in units of 10 ms. The supervision time-out value can range from a minimum of 10 (100 ms) to 3200 (32.0 s). The time-out must be larger than the effective connection interval

Effective Connection Interval
The effective connection interval is equal to the amount of time between two connection events, assuming that the slave skips the maximum number of possible events if slave latency is allowed (the effective connection interval is equal to the actual connection interval if slave latency is set to 0).

The slave latency value represents the maximum number of events that can be skipped. This number can range from a minimum value of 0 (meaning that no connection events can be skipped) to a maximum of 499. The maximum value must not make the effective connection interval (see the following formula) greater than 16 s. The interval can be calculated using the following formula:

Effective Connection Interval = (Connection Interval) * (1 + [Slave Latency])
Consider the following example:

Connection Interval: 80 (100 ms)
Slave Latency: 4
Effective Connection Interval: (100 ms) * (1 + 4) = 500 ms
When no data is being sent from the slave to the master, the slave transmits during a connection event once every 500 ms.