https://devzone.nordicsemi.com/f/nordic-q-a/6764/conn_params_error_handler-after-3rd-connectionHi, I&#39;m trying to write my own application based on the ble_lbs example on nrf51822. Recently I&#39;ve discovered a problem with reconnection to the beacon. I can successfully make two cycles of connect and disconnect. When I try to connect for the thirden-USTelligent Community 13Tue, 28 Apr 2015 14:48:59 GMThttps://devzone.nordicsemi.com/thread/23760?ContentTypeID=1Tue, 28 Apr 2015 14:48:59 GMT137ad170-7792-4731-bb38-c0d22fbe4515:a5cce86c-0cbd-4057-a67d-430108949365Konrad Traczyk<p>Ok, thank you very much for your answers. Propably you&#39;re right saying to use the app_timer library.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/23759?ContentTypeID=1Tue, 28 Apr 2015 14:35:17 GMT137ad170-7792-4731-bb38-c0d22fbe4515:87d09cb7-e026-46c1-9f5a-2a03a0acc4e2Wojtek<p>You can do that, but make sure that You dont have function that tries to stop timer that has not been created - this function is connected with other parts of nordic libraries. What I would suggest is to use app_timer library instead of directly using RTC1 - this library is used by many modules and by taking RTC1 You make it useless.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/23758?ContentTypeID=1Tue, 28 Apr 2015 14:04:41 GMT137ad170-7792-4731-bb38-c0d22fbe4515:82d1a4b7-67af-4520-9795-cffec6688b48Konrad Traczyk<p>Does anything bad happen if I comment the entire conn_params_init function? I will have a dedicated android app as central for the beacon, so maybe it should force the connection parameters for the beacon.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/23757?ContentTypeID=1Tue, 28 Apr 2015 13:55:15 GMT137ad170-7792-4731-bb38-c0d22fbe4515:5b32542d-fcc1-4ed7-8115-b7063897d0ccMartinBL<p>Hi. ble_conn_params_init() starts a &quot;one shot&quot; timer using the app_timer library. App_timer uses RTC1 and hence you can&#39;t use RTC1 in your application.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/23756?ContentTypeID=1Tue, 28 Apr 2015 13:26:59 GMT137ad170-7792-4731-bb38-c0d22fbe4515:036f9148-5a60-4da1-a83f-d39be08ed957Konrad Traczyk<p>It didn&#39;t help, but after following the conn_params_negotiation() in debugger, I believe that it uses RTC1 to measure the time, while I use it in my application. Is there any way to change it?</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/23755?ContentTypeID=1Tue, 28 Apr 2015 13:18:39 GMT137ad170-7792-4731-bb38-c0d22fbe4515:f3ae5a19-3446-45ce-a492-27c045a17887Wojtek<p>Try increasing APP_TIMER_MAX_TIMERS and check if it helps.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/23754?ContentTypeID=1Tue, 28 Apr 2015 13:13:51 GMT137ad170-7792-4731-bb38-c0d22fbe4515:47b5c6a2-354c-4e33-9d9f-1f335e16d338Konrad Traczyk<p>It&#39;s called from conn_params_negotiation()</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/23753?ContentTypeID=1Tue, 28 Apr 2015 13:10:55 GMT137ad170-7792-4731-bb38-c0d22fbe4515:14163792-a2f5-4471-811a-e9e1c3d8df58Wojtek<p>You can set breakpoint (trap) in error handler and check call stack - this should help You finding exact line that is setting this error value.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/23752?ContentTypeID=1Tue, 28 Apr 2015 12:55:28 GMT137ad170-7792-4731-bb38-c0d22fbe4515:e738cf60-909c-49b2-988c-b7ce79781ffbKonrad Traczyk<p>Sorry, I totally forgot about it. The err_code&#39;s gets value 0x00000004.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/23751?ContentTypeID=1Tue, 28 Apr 2015 12:51:21 GMT137ad170-7792-4731-bb38-c0d22fbe4515:63126fb2-29c3-460b-9975-6fb62395e7e4Wojtek<p>What error code you get?</p><div style="clear:both;"></div>