Frequent disconnection with reason 8

RE: Frequent disconnection with reason 8

Mikah S. — Fri, 03 Jan 2025 06:36:30 GMT

I resolved the issue by increasing the supervision timeout.

RE: Frequent disconnection with reason 8

Simonr — Fri, 25 Oct 2024 07:50:25 GMT

Hmm, okay. Can you try sniffing the connection to see what's happening over the air to see what sends the BAS notification disabled function. You can use a dedicated BLE sniffer or the nRF Sniffer for Wireshark and a separate nRF52 DK to run the firmware.

Best regards,
Simon

RE: Frequent disconnection with reason 8

Mikah S. — Fri, 25 Oct 2024 02:18:40 GMT

I can't find anywhere in the code were the notifications would be disabled and the bas notifications shouldn't ever be disabled.

RE: Frequent disconnection with reason 8

Simonr — Wed, 23 Oct 2024 12:42:11 GMT

Ok, if the notifications get disabled that could point to the two devices stop having any meaningful data communication, and thus a timeout occurs because there is no data transferred for the connection timeout. The standard here is 4 seconds if I'm not mistaken. Is there a reason you can see for the notifications being disabled?

Best regards,

Simon

RE: Frequent disconnection with reason 8

Mikah S. — Wed, 23 Oct 2024 01:39:11 GMT

I do have an nRF52840 DK but have been unable to reproduce the issue with the DK. The 32.768 kHz clock has a 12pF capacitor on both XL1 and XL2 lines (I was unable to get 12.5pF capacitors). My application is a Bluetooth keyboard with customizable keys. The connection parameters are not any different than the peripheral_hids_keyboard example in the sdk. I am using the v2.6.1 sdk. I don't know if this is meaningful but before each disconnect the following log message is displayed: bas: blvl_ccc_cfg_changed: BAS Notifications disabled. The board is always acting as a peripheral, and any programming/customizing of keys is done over usb.

RE: Frequent disconnection with reason 8

Simonr — Mon, 21 Oct 2024 13:44:41 GMT

Do you by chance have an nRF52840 DK to try and reproduce this on? Or is it only reproducible on the board you have. How have you loaded the 32.768 kHz, disconnect reason 8 should be a connection timeout if I'm not mistaken, and could indeed point to a drifting LF clock or HF clock source. Although the disconnect intervals of up to 10 minutes seems like a bit much.

Can you share some details on what your application is doing exactly, what connection parameters are you operating with, and what is the central you're connecting to when seeing these disconnects? Are your boards both central and peripheral here, or just one of the roles? What SDK are you using for development?

Best regards,

Simon