<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Start the timer and disconnect bluetooth connection conflict</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/7805/start-the-timer-and-disconnect-bluetooth-connection-conflict</link><description>Hi, 
 I have a question. 
 
 
 SDK:8.1.0 
 
 
 softdevice:8.0.0 
 
 
 I create two APP_TIMER, as follow: 
 
 
 
 I will start the adc_sample_timer, as follow:
 
 
 After the device advtising, I use my phone connect with this device, at</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 01 Jul 2015 11:43:51 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/7805/start-the-timer-and-disconnect-bluetooth-connection-conflict" /><item><title>RE: Start the timer and disconnect bluetooth connection conflict</title><link>https://devzone.nordicsemi.com/thread/27797?ContentTypeID=1</link><pubDate>Wed, 01 Jul 2015 11:43:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5da048aa-6a4b-47d4-89f0-ae209659df35</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;@zcmm: sd_ble_gap_conn_param_update should not be called after you call sd_ble_gap_disconnect(). But it won&amp;#39;t harm, except for the return code 0x08 that you can ignore.&lt;/p&gt;
&lt;p&gt;When do you start the Disconnect timer ? Note that the connection parameter update may not start immediately after you get connected but when a notification handle is enabled, depend on how you configure the start_on_notify_cccd_handle in conn_params_init().&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Start the timer and disconnect bluetooth connection conflict</title><link>https://devzone.nordicsemi.com/thread/27798?ContentTypeID=1</link><pubDate>Wed, 01 Jul 2015 03:50:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fef8b255-02e0-437c-9035-fa3dae44a96d</guid><dc:creator>zcmm</dc:creator><description>&lt;p&gt;thanks. i&amp;#39;m sure i can&amp;#39;t set the interrupt priority.i find the reasons that sd_ble_gap_conn_param_updata fuc is conflict with sd_ble_gap_disconnect. After use sd_ble_gap_disconnect fuc, the link is still connected,then sd_ble_gap_conn_param_updata fuc is used and the response code is 0x00000008. at the same time,i have other questions.the APP_timer is not accuracy. In the case of the same time both #define DISCONNECT_LEVEL_MEAS_INTERVAL APP_TIMER_TICKS(5000, APP_TIMER_PRESCALER) and #define FIRST_CONN_PARAMS_UPDATE_DELAY APP_TIMER_TICKS(5000, APP_TIMER_PRESCALER) , first of all, first open app_timer_start(m_conn_params_timer_id, timeout_ticks, NULL)（timer1） at conn_params_negotiation fuc, and then open the disconnect timer （timer 2）, but the timer 2 faster than the timer 1. why ？&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Start the timer and disconnect bluetooth connection conflict</title><link>https://devzone.nordicsemi.com/thread/27796?ContentTypeID=1</link><pubDate>Thu, 25 Jun 2015 10:39:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:88ea5ff8-93b6-4302-b027-9328e3ec837c</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;@zcmm: I tried to reproduce the issue here but I haven&amp;#39;t managed to. Attach is an example where I trigger a 1 second timer after I connect. The device got disconected and start advertising again.&lt;/p&gt;
&lt;p&gt;Have you make sure you don&amp;#39;t set the interrupt priority of RTC1 and SWI0 to something higher than APP_IRQ_PRIORITY_LOW ?
Also please check if you have an assert when in Disconnect event. You can add a breakpoint in the app assert handler to find the error code, line number &amp;amp; file name of the code that cause the issue, if any.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/ble_5F00_app_5F00_template-_2D00_-disconnectWithaTimer.zip"&gt;ble_app_template - disconnectWithaTimer.zip&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>