<?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>Broadcast with custom UUID</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/243/broadcast-with-custom-uuid</link><description>Hi, 
 I am trying to figure out how I can advertise with a custom UUID...
I know I have to start by adding a base address and then build on top of it. However, when I try to advertise I should indicate the length[Length], followed by type [Service Data</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 08 Aug 2013 10:56:57 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/243/broadcast-with-custom-uuid" /><item><title>RE: Broadcast with custom UUID</title><link>https://devzone.nordicsemi.com/thread/1319?ContentTypeID=1</link><pubDate>Thu, 08 Aug 2013 10:56:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8f47bf16-f5d1-47f0-bc11-8e1fa223d4c0</guid><dc:creator>Nuno Lourenco</dc:creator><description>&lt;p&gt;Nice tip, that might work!
Thank you.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Broadcast with custom UUID</title><link>https://devzone.nordicsemi.com/thread/1318?ContentTypeID=1</link><pubDate>Thu, 08 Aug 2013 10:54:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7f0bced6-07f5-471b-a55f-244d2a3c4afe</guid><dc:creator>Ulrich Myhre</dc:creator><description>&lt;p&gt;Yes, the spec is not yet covering this yet. Until it is in you could probably make use of the &amp;quot;Manufacturer specific data&amp;quot; field (See Core Spec V4.0, Vol. 3, Part C, 11.1.4) to advertise your data.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Broadcast with custom UUID</title><link>https://devzone.nordicsemi.com/thread/1317?ContentTypeID=1</link><pubDate>Thu, 08 Aug 2013 06:45:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5d10bbe8-4b7f-45af-9b97-c26643915c7e</guid><dc:creator>Nuno Lourenco</dc:creator><description>&lt;p&gt;Hi Ulrich,&lt;/p&gt;
&lt;p&gt;Thank you for the tip. I think I can now understand how to do it! :)
However, there is a lack in the standard when it comes to this... If you take a look at the Supplement to Bluetooth Core Specification, page 20 (Data types definitions and formats), section 1.11 SERVICE DATA only makes reference to 16 bits UUIDs. And we should not convert them...
I have also taken a look at some other examples online and many people use 16 bits UUIDs that are &amp;quot;still not defined&amp;quot; (eg. 0xFFE0).
Good to know that with this stack we can use the full 128 bits!&lt;/p&gt;
&lt;p&gt;regards&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Broadcast with custom UUID</title><link>https://devzone.nordicsemi.com/thread/1320?ContentTypeID=1</link><pubDate>Thu, 08 Aug 2013 06:25:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2a834033-cafe-47a6-9141-a42a1a7e424a</guid><dc:creator>Ulrich Myhre</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Could this similar question and solution work for you?&lt;/p&gt;
&lt;p&gt;&lt;a target="_blank" href="https://devzone.nordicsemi.com/index.php/i-m-having-trouble-advertising-a-vs-service" rel="nofollow"&gt;https://devzone.nordicsemi.com/index.php/i-m-having-trouble-advertising-a-vs-service&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Just remember the size restrictions! :)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>