Disconnect after connect parameters update

RE: Disconnect after connect parameters update

Susheel Nuguru — Thu, 01 Jul 2021 11:41:32 GMT

Glad that I could help.

RE: Disconnect after connect parameters update

Gavin — Thu, 01 Jul 2021 01:17:52 GMT

Hmm, i see, thanks Susheel..

RE: Disconnect after connect parameters update

Susheel Nuguru — Wed, 30 Jun 2021 10:52:36 GMT

With such slow connection interval, it is very easy to lose packets (corrupted) packets in a radio noisy environment. Setting the smaller connection interval with make the exchange of packets faster hence giving more time for retires of packets that are lost/corrupted before the supervision timeout expires.

RE: Disconnect after connect parameters update

Gavin — Wed, 30 Jun 2021 10:10:11 GMT

Hi Susheel,

It just received BLE_ADV_EVT_FAST...

But now it is stable after setting a smaller conn interval:

#define MIN_CONN_INTERVAL MSEC_TO_UNITS(7.5, UNIT_1_25_MS)
#define MAX_CONN_INTERVAL MSEC_TO_UNITS(30, UNIT_1_25_MS)

I just confuse why this setting can not work:

#define MIN_CONN_INTERVAL MSEC_TO_UNITS(500, UNIT_1_25_MS)
#define MAX_CONN_INTERVAL MSEC_TO_UNITS(1000, UNIT_1_25_MS)

Thanks.

RE: Disconnect after connect parameters update

Susheel Nuguru — Mon, 28 Jun 2021 11:58:32 GMT

[quote user=""]The ble gateway want to connect the heart rate device, which running the ble_app_hrs example in SDK 17, for test, but it is disconnected after conn parameters update, the reason is 0x8. From the wireshark, the master has send LL_CONNECTION_UPDATE_IND to slave, but the slave no response any more and enters to adv mode.[/quote]

It is not clear what is happening on the peripheral side since the timestamps are visible in your snapshot. Could it that there is a restart on the peripheral side (mostly APP_ERROR_CHECK)? or could it be a super vision timeout?

Could it be that your peripheral has some other logic in handling the BLE_GAP_EVT_CONN_PARAM_UPDATE: event and that logic asserted or caused your peripheral to restart?