disconnect due to connection time out after enableing all notification

RE: disconnect due to connection time out after enableing all notification

Bjørn Kvaale — Fri, 18 May 2018 10:13:09 GMT

What is your current connection interval on the Thingy device (e.g. how often the central asks for updates from the peripheral) & on the multilink_central?

RE: disconnect due to connection time out after enableing all notification

nikunj8086 — Thu, 17 May 2018 06:39:29 GMT

ok, i had increased supervision timeout to 6 seconds and i am still facing same problem.

RE: disconnect due to connection time out after enableing all notification

Bjørn Kvaale — Tue, 15 May 2018 10:41:48 GMT

What is your current connection interval on the Thingy device (e.g. how often the central asks for updates from the peripheral) & on the multilink_central? What happens if you increase the supervision timeout to 6 seconds?

RE: disconnect due to connection time out after enableing all notification

nikunj8086 — Mon, 14 May 2018 09:39:39 GMT

hi,

i am using ble_multilink central example and yes,

#define SUPERVISION_TIMEOUT MSEC_TO_UNITS(4000, UNIT_10_MS)

is there in my code.

but i figured that timeout problem occurs more frequently when i enable Microphone characteristic notification uuid 0x0504 on connected thingy device.

RE: disconnect due to connection time out after enableing all notification

Bjørn Kvaale — Mon, 14 May 2018 09:18:32 GMT

Which central example are you using on sdk 14.2.0? Error Code 0x08 is an BLE_HCI_CONNECTION_TIMEOUT (supervision timeout, i.e. you have not received any packets from the peer in x seconds). Do you have this define in your central example: #define SUPERVISION_TIMEOUT MSEC_TO_UNITS(4000, UNIT_10_MS) , with a 4 second supervision timeout?