<?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>How to create your own ble service?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/5055/how-to-create-your-own-ble-service</link><description>I want to graduate from hacking my own data through the heart-rate-service (hrs). None of these seem to fulfill my requirements. Is there a document or template from which I can build my custom service? I really just want to send up a batch of timestamped</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 08 Jan 2015 13:10:40 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/5055/how-to-create-your-own-ble-service" /><item><title>RE: How to create your own ble service?</title><link>https://devzone.nordicsemi.com/thread/17788?ContentTypeID=1</link><pubDate>Thu, 08 Jan 2015 13:10:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bb61f9ba-91ec-4020-97c2-fb2ffc57bd5c</guid><dc:creator>Ulrich Myhre</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Take a look at these previous questions:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/question/161/how-do-i-create-my-own-service-on-the-ble-stack/"&gt;How do I create a service&lt;/a&gt; and &lt;a href="https://devzone.nordicsemi.com/question/639/how-can-i-use-a-vendor-specific-uuid/"&gt;How to use Vendor-specific UUID&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;When creating a non-adopted service, you have to use 128-bit UUID values instead of the 16-bit variants you are used to see. Then you would follow the outline of a normal, simple service like the battery service and pipe the incoming events to your service. To be able to send data, you can either have a notifiable characteristic, have the peer enable notifications, and then start sending data - OR - you can have service that allows data to be written to on the peer side and use write requests/commands or long writes to push your data.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>