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

GATT CONN TIMEOUT after rejecting connection parameters update

Hi folks,

We got a weird behaviour with our nrf51822(SDK 12.2.0, s130) device. we have built a low power application with following parameters:

  1. MIN_CONN_INTERVAL 200ms
  2. MAX_CONN_INTERVAL 400ms
  3. SLAVE_LATENCY 3
  4. CONN_SUP_TIMEOUT 6s

One of our requirements is to stay at least 10h connected with the master. But during our tests we observed that:

  1. With Android Connect App the device stays very long connected (max. 20h).
  2. With iOS Connect App the device stays only a couple hours connected (max. 4h).
  3. With the Master Control Panel PC the device stays very long connected when we accept the connection parameters. But when we reject the connection parameters update, the device stays only max. 5min connected after the rejecting.

In all the cases we got a GATT CONN TIMEOUT on the master side and on the device side we got a disconnect event. Although we do not do on the device side any explicit disconnection when the connection parameters update failed.

My questions are:

  1. Why we get a GATT CONN TIMEOUT when we reject the connection parameters update... should not the device keep working with the connection parameters set by the master ?
  2. Why the connection time is that short with the iOS Connect App.
  3. We also notice that the GATT CONN TIMEOUT occurs often between on Connect App. How do Android and iOS handle the connection parameters update ?. Do they accept it or they propose/set different parameters. ?

Thx, any help would be appreciated

Cheers,

Etienne

Related