<?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>UART service center</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/100249/uart-service-center</link><description>Hi nordic, 
 Our product have used nordic UART service to transmit data. 
 In ble_nus.c file, we have opened the BLE_UUID_NUS_RX_CHARACTERISTIC notify funciton to send data, so what should I do to recieve this characteristic data in the nus_c in central</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 05 Jun 2023 19:41:09 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/100249/uart-service-center" /><item><title>RE: UART service center</title><link>https://devzone.nordicsemi.com/thread/429415?ContentTypeID=1</link><pubDate>Mon, 05 Jun 2023 19:41:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3fd49f98-5607-4492-8ace-464d31734486</guid><dc:creator>Hieu</dc:creator><description>&lt;p&gt;This is tricky. The &amp;quot;example code&amp;quot; for this is already there in the same file, ble_nus_c.c. You simply have to replicate exactly what is done to the TX Characteristic.&lt;/p&gt;
&lt;p&gt;Here are the functions you will want to refer to:&lt;/p&gt;
&lt;p&gt;Enabling notification:&amp;nbsp;ble_nus_c_tx_notif_enable()&lt;br /&gt;This is a &amp;quot;public&amp;quot; function which is called from outside the module. You should see the RX Characteristic&amp;#39;s CCCD being written.&lt;/p&gt;
&lt;p&gt;Handle the data:&amp;nbsp;ble_nus_c_on_ble_evt()&lt;br /&gt;This is where the SoftDevice push raw BLE events to the application&amp;#39;s modules, including ble_nus_c.c. You should look into how&amp;nbsp;BLE_GATTC_EVT_HVX is handled from here to the point where ble_nus_c.c generate a&amp;nbsp;BLE_NUS_C_EVT_NUS_TX_EVT and call the&amp;nbsp;ble_nus_c_t&amp;#39;s handler.&lt;/p&gt;
&lt;p&gt;Asides from this, I think perhaps your difficulties lies with not fully understanding some concepts. Here are some things that I think most people will encounter for the first time around this stage. Please make sure they understand what they are.&lt;/p&gt;
&lt;p&gt;- CCCD&lt;br /&gt;- Attribute&lt;br /&gt;- Attribute Handle&lt;br /&gt;- The fact that Services, Characteristics, and Descriptors are just attributes&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s start with this. Please look into what I listed above and let me know how it goes.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UART service center</title><link>https://devzone.nordicsemi.com/thread/428869?ContentTypeID=1</link><pubDate>Fri, 02 Jun 2023 01:13:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8ef12dca-b609-449c-8556-67af553d5784</guid><dc:creator>Taylor</dc:creator><description>&lt;p&gt;In my opinion, on_hvx() returned the data and data length which have been enabled the charactertic notify. But the example just enabled the&amp;nbsp;BLE_UUID_NUS_TX_CHARACTERISTIC&amp;#39;s notify,so when the peripheral tansmit data from&amp;nbsp; the&amp;nbsp;BLE_UUID_NUS_RX_CHARACTERISTIC, we can not handle this.&lt;/p&gt;
&lt;p&gt;In addition to this,the peripheral will disconnect automatically while tansmit data from&amp;nbsp;&lt;span&gt;BLE_UUID_NUS_RX_CHARACTERISTIC.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;So I have no idea how wo enable the&amp;nbsp;BLE_UUID_NUS_RX_CHARACTERISTIC&amp;#39;s notify and handle the data.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UART service center</title><link>https://devzone.nordicsemi.com/thread/428777?ContentTypeID=1</link><pubDate>Thu, 01 Jun 2023 13:47:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a32524ba-79c6-4b35-880b-5b87eba01297</guid><dc:creator>Hieu</dc:creator><description>&lt;p&gt;Could you please go into details what you are confused about on_hvx()? Or are you completely confused what it is and is looking for some starting points?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UART service center</title><link>https://devzone.nordicsemi.com/thread/428665?ContentTypeID=1</link><pubDate>Thu, 01 Jun 2023 09:42:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c25cb7d5-a2b6-4483-ad04-d22c45ea6a5c</guid><dc:creator>Taylor</dc:creator><description>&lt;p&gt;Thanks for your reply.&lt;/p&gt;
&lt;p&gt;I am so comfused of&amp;nbsp;&lt;span&gt;on_hvx(), could you tell me how to solve my problem?&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UART service center</title><link>https://devzone.nordicsemi.com/thread/428285?ContentTypeID=1</link><pubDate>Tue, 30 May 2023 21:41:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:858e0d29-68e3-4571-b1ee-b8bbf1feb3bb</guid><dc:creator>Hieu</dc:creator><description>&lt;p&gt;Hi Taylor,&lt;/p&gt;
&lt;p&gt;Please look into how&amp;nbsp;on_hvx() is implemented and used in ble_nus_c.c.&lt;/p&gt;
&lt;p&gt;Hieu&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>