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

disconnect due to connection time out after enableing all notification

hi,

i am doing a project where i am using central and client model.

i am using nrf52840 as central device and thingy 52 as peripheral device and i am using sdk 14.2.0 and thingy firmware ver. is 2.1.0 

problem is that after i enable all the notifications the thingy 52 only maintains connection for few seconds and then disconnects. and on uart terminal i am seeing the disconnection reason is 0x08 i believe it is connection time out.

i dont know about timeout reason.

please help me out

Parents
  • 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?

     

  • 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.

  • 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?

Reply
  • 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?

Children