<?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>Multi BLE-Services in the modified Uart Example</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/55165/multi-ble-services-in-the-modified-uart-example</link><description>Hello everybody, 
 
 I&amp;#39;ll try to modify the ble uart example. The target is, to get data from two different nus Services (different characterisitv uuids). They are both initilised and I can subscribe both. Both services are based on the same structure</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 04 Dec 2019 10:57:07 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/55165/multi-ble-services-in-the-modified-uart-example" /><item><title>RE: Multi BLE-Services in the modified Uart Example</title><link>https://devzone.nordicsemi.com/thread/223551?ContentTypeID=1</link><pubDate>Wed, 04 Dec 2019 10:57:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:90482117-5c68-4543-bf61-6747e62af313</guid><dc:creator>marsss</dc:creator><description>&lt;p&gt;Ok thanks a lot &lt;span class="emoticon" data-url="https://devzone.nordicsemi.com/cfs-file/__key/system/emoji/1f642.svg" title="Slight smile"&gt;&amp;#x1f642;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;I will take your tips, try to change my Code and give you a feedback!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Multi BLE-Services in the modified Uart Example</title><link>https://devzone.nordicsemi.com/thread/223499?ContentTypeID=1</link><pubDate>Wed, 04 Dec 2019 08:57:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6998b0c5-5da9-4d99-b89d-fbfe107539d7</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;There are several things that may go wrong here, have you taken a look at:&lt;br /&gt;&lt;a href="https://devzone.nordicsemi.com/nordic/short-range-guides/b/bluetooth-low-energy/posts/ble-characteristics-a-beginners-tutorial"&gt;https://devzone.nordicsemi.com/nordic/short-range-guides/b/bluetooth-low-energy/posts/ble-characteristics-a-beginners-tutorial&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;There are also some useful comments below the tutorial that is useful.&lt;/p&gt;
&lt;p&gt;Typically it should be straight forward enough, make sure that each time you add a service or characteristic,&amp;nbsp;that you have an overview of the handles, since those is needed once you want to send/receive data. This is described in the linked tutorial:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;handle:&lt;/strong&gt;&lt;span&gt;&amp;nbsp;The SoftDevice needs to know what characteristic value we are working on. In applications with two or more characteristics naturally we will need to reference the handle of the specific characteristic value we want to use. Our example only has one characteristic and we will use the handle stored in&amp;nbsp;&lt;/span&gt;&lt;code&gt;p_our_service-&amp;gt;char_handles.value_handle&lt;/code&gt;&lt;span&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;If you are experiencing an assert, then the the application should typically jump to the fault_handler() and you can read out the file name, line number, and error code that is causing the assert by setting a breakpoint there (remember to also define DEBUG). Once you know that, it may be easier to know exactly which line of code is problematic.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>