https://devzone.nordicsemi.com/f/nordic-q-a/56477/ble-connection-times-out-on-central-and-peripheral-both-sidesCentral info SDK: 15.3 nRF52840 Peripheral info SDK: 13.1 nRF52832 Connection Param MIN_CONN_INTERVAL MSEC_TO_UNITS 40 MAX_CONN_INTERVAL MSEC_TO_UNITS 52 SLAVE_LATENCY 3 CONN_SUP_TIMEOUT 1500 BLE connection times out on Central and Peripheral, bothen-USTelligent Community 13Thu, 16 Jan 2020 14:44:57 GMThttps://devzone.nordicsemi.com/thread/229441?ContentTypeID=1Thu, 16 Jan 2020 14:44:57 GMT137ad170-7792-4731-bb38-c0d22fbe4515:375b3fe5-2905-45d5-b1fc-3d9477506a9drun_ar<p>The 32kHz source is used to keep track of connection events. It is usually an external crystal or the internal rc. configuration of the accuracy is done in sdk_config.h see NRF_SDH_CLOCK_LF_ACCURACY</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/228953?ContentTypeID=1Tue, 14 Jan 2020 08:34:21 GMT137ad170-7792-4731-bb38-c0d22fbe4515:1853f9c9-6743-4eec-ae8c-50537c05017aSawada<p>sorry.<br />When a problem occurred, the supervision timeout was 4000 milliseconds.<br />What is a 32kHz source?<br />We have verified that neither device has reset.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/228789?ContentTypeID=1Mon, 13 Jan 2020 12:34:41 GMT137ad170-7792-4731-bb38-c0d22fbe4515:58ff2daa-aaf6-4c8f-9706-9202004bfd25run_ar<p>Hi,</p> <p>A supervision timeout of 15000 ms should be more than enough. I would guess you might have issue with the 32kHz source, or that you are testing in an environment with some really bad interference.</p> <p>What HW are you testing on? And what is the usecase for this device, i.e. in what kind of environment is the device located when the link is lost?</p> <p>I assume you are checking to make sure you do not have any unintentional resets on either device?</p><div style="clear:both;"></div>