<?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>Notify Enable problem</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/56120/notify-enable-problem</link><description>Hi, 
 I want to directly enable notify without discovering the service handle, but it didn&amp;#39;t work(return NRF_ERROR_BUSY). Because it takes time to discover the service, and I need to communicate as soon as possible after connecting</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 03 Jan 2020 05:52:09 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/56120/notify-enable-problem" /><item><title>RE: Notify Enable problem</title><link>https://devzone.nordicsemi.com/thread/227330?ContentTypeID=1</link><pubDate>Fri, 03 Jan 2020 05:52:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c5a76231-9d1b-4360-8862-1e544a66184a</guid><dc:creator>Yinbun Ye</dc:creator><description>&lt;p&gt;thx Vidor&amp;nbsp;Berg, thx for your reply&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Notify Enable problem</title><link>https://devzone.nordicsemi.com/thread/227234?ContentTypeID=1</link><pubDate>Thu, 02 Jan 2020 13:00:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e1f27a9c-6d8c-4b98-ad1d-00f1d80ae40f</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;NRF_ERROR_BUSY indicates that another write request procedure is ongoing and that you need to wait for it to complete first (completion signaled through &lt;a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v7.0.1/group___b_l_e___g_a_t_t_c___e_n_u_m_e_r_a_t_i_o_n_s.html#ggafd9b8b42eeb832d688e33f4561f97efca6a70fe83b91997c8d3cd47b6cd98a91a"&gt;BLE_GATTC_EVT_WRITE_RSP&lt;/a&gt;). So I think it&amp;#39;s timing related and not that you&amp;#39;re using a hardcoded attribute handle.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Optional: with SDK 16 you can use the&amp;nbsp;&lt;a title="BLE GATT Queue" href="https://infocenter.nordicsemi.com/topic/sdk_nrf5_v16.0.0/lib_ble_gatt_queue.html?cp=7_1_3_2_10"&gt;BLE GATT Queue&lt;/a&gt;&amp;nbsp;module to enqueue the write request.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;API reference:&amp;nbsp;&lt;a title="sd_ble_gattc_write" href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v7.0.1/group___b_l_e___g_a_t_t_c___f_u_n_c_t_i_o_n_s.html?cp=4_5_2_1_2_2_2_11#ga90298b8dcd8bbe7bbe69d362d1133378"&gt;sd_ble_gattc_write&lt;/a&gt;&amp;nbsp;and the&amp;nbsp;MSC:&amp;nbsp;&lt;a title="GATTC Characteristic or Descriptor Value Write" href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v7.0.1/group___b_l_e___g_a_t_t_c___v_a_l_u_e___w_r_i_t_e___m_s_c.html?cp=4_5_2_1_2_2_3_6"&gt;GATTC Characteristic or Descriptor Value Write&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>