https://devzone.nordicsemi.com/f/nordic-q-a/30054/random-disconnect-reason-0x08I use the ble_uart sdk14.2.0 example, I just open the pwm, and then accept the data, I did not deal with the data received from nus, just a connection, a connection error 0x08 random, my configuration of sdk.config just the agreement Stack clock to theen-USTelligent Community 13Tue, 06 Feb 2018 12:59:14 GMThttps://devzone.nordicsemi.com/thread/119938?ContentTypeID=1Tue, 06 Feb 2018 12:59:14 GMT137ad170-7792-4731-bb38-c0d22fbe4515:9da73fa7-2602-4317-946b-e9421acfe9d0Petter Myhre<p>So it works if you use low frequency crystal? And not if you use RC oscillator? If you use RC oscillator, please try to set&nbsp;<span>NRF_SDH_CLOCK_LF_XTAL_ACCURACY&nbsp;to 1.</span></p> <p><span></span></p> <p><span>I&#39;m not sure what kind of timeout you are talking about, could you elaborate?</span></p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/119868?ContentTypeID=1Tue, 06 Feb 2018 07:43:38 GMT137ad170-7792-4731-bb38-c0d22fbe4515:4dd69662-fa96-4180-b47c-302b9b673f0cstrengthstrong<p>#define MIN_CONN_INTERVAL MSEC_TO_UNITS(20, UNIT_1_25_MS)&nbsp;<br />#define MAX_CONN_INTERVAL MSEC_TO_UNITS(75, UNIT_1_25_MS)&nbsp;<br />#define SLAVE_LATENCY 0&nbsp;<br />#define CONN_SUP_TIMEOUT MSEC_TO_UNITS(4000, UNIT_10_MS)&nbsp;</p> <p>#define FIRST_CONN_PARAMS_UPDATE_DELAY APP_TIMER_TICKS(5000)&nbsp;<br />#define NEXT_CONN_PARAMS_UPDATE_DELAY APP_TIMER_TICKS(30000)&nbsp;<br />#define MAX_CONN_PARAMS_UPDATE_COUNT 2&nbsp;</p> <p>#define DEFAULT_ADV_INTERVAL 10<br />#define DEFAULT_ADV_TIMEOUT 0</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/119867?ContentTypeID=1Tue, 06 Feb 2018 07:41:33 GMT137ad170-7792-4731-bb38-c0d22fbe4515:87edf083-508a-42f8-baf2-1d609cd8e174strengthstrong<p>central is android phone and i use nrf52810 , when i use external crystal ,Good effect,Connection 12 hours did not disconnect, but again test, there is a timeout, did not appear after, I do not know why this is. No problem with my timeout parameter, NRF_SDH_CLOCK_LF_XTAL_ACCURACY = 7</p> <div class="client_search_body" id="content_container"> <div class="client_search_container"> <div class="client_search_content"> <div class="client_search_leftside_area"> <div class="client_search_sentence_area"> <div class="client_def_container"> <div class="client_def_bar"> <div class="client_def_list"> <div class="client_def_list_item"> <div class="client_def_list_word_item"> <div class="client_def_list_word_content"></div> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/119351?ContentTypeID=1Wed, 31 Jan 2018 12:11:38 GMT137ad170-7792-4731-bb38-c0d22fbe4515:ee51881d-e0c2-497f-81d3-7a6d747bfa4bPetter Myhre<p>0x08 is BLE_HCI_CONNECTION_TIMEOUT, and this happens because the supervision timeout is hit (no packets from the peer is received in x seconds).</p> <p>Is this a custom board? Have you tried the same code on the nRF52 DK? Does it happen there?</p> <p>What value does NRF_SDH_CLOCK_LF_XTAL_ACCURACY have? Try setting it to 1.</p> <p>What kind of central device are you connecting to?</p><div style="clear:both;"></div>