<?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>Setting up Bluetooth exchanges message &amp;quot;0x0100&amp;quot; - why?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/33917/setting-up-bluetooth-exchanges-message-0x0100---why</link><description>I am a beginner to Nordic devices and to Bluetooth technology in general. I have set up a Bluetooth connection using the nRF51 Development Kit and an nRF51-Dongle. The dongle works as the master, the DK as the slave. I access the dongle using the software</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 02 May 2018 14:50:56 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/33917/setting-up-bluetooth-exchanges-message-0x0100---why" /><item><title>RE: Setting up Bluetooth exchanges message "0x0100" - why?</title><link>https://devzone.nordicsemi.com/thread/130632?ContentTypeID=1</link><pubDate>Wed, 02 May 2018 14:50:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:218dbabb-4841-457e-b306-1aec38170a80</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/members/miriam"&gt;Miriam&lt;/a&gt;:&amp;nbsp;The ble_app_uart examples uses two characteristics TX and RX to exchange information, data from the central to the peripheral is written to the peripherals RX characteristic. Data from the peripheral is notified from the TX characteristic to the central&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The handle 0x0E corresponds to the UART RX characteristic, the handle 0x0B corresponds to the UART TX characteristic and&amp;nbsp; 0x0C corresponds to the CCCD of the TX characteristic&lt;/p&gt;
&lt;p&gt;Q1: The handle 0x0C corresponds to the CCCD of the UART TX characteristic, i.e. notification is being enabled.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Q2: Yes, from the&amp;nbsp;central side you could not enable notifications, but then the peripheral would not be able to send the data to the central. THe central would then have to &amp;quot;poll&amp;quot; the peripherals TX&amp;nbsp; characteristic by reading it regurarly to see if there is any new data.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Q3: All BLE events passed on from the SoftDevice will go through&amp;nbsp;on_ble_evt(ble_evt_t * p_ble_evt) in main.c&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Q4: Take a look at the Message Sequence Charts for the S130 v2.0.1 SoftDevice, &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s130.api.v2.0.1/s130_msc_overview.html?cp=3_7_2_1_0_1"&gt;here &lt;/a&gt;is the link to the Infocenter page.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>