<?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>sending data over ble</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/9800/sending-data-over-ble</link><description>Hello, 
 I have developed a simple characteristic to send data over ble using the ble_nus service.
I created a service and added a characteristic to send. Then sending the counter data (eg: 1 to 100 decimal value), one byte per second and I am testing</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 21 Oct 2015 13:31:36 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/9800/sending-data-over-ble" /><item><title>RE: sending data over ble</title><link>https://devzone.nordicsemi.com/thread/36335?ContentTypeID=1</link><pubDate>Wed, 21 Oct 2015 13:31:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3df83b2d-cedd-4e36-b9c7-27a9c0243e2b</guid><dc:creator>Bill Siever</dc:creator><description>&lt;ol&gt;
&lt;li&gt;No. The Bluetooth Specs define the packet structure. 2) No. Again, packet size limitations (and notifications appear to be a single packet).  Again, you can send multiple notification (or indication) packets.  If using this approach, you may be best to use indications since they will confirm receipt.  (Also, it looks like you posted further questions as answers. It would have probably fit better as a comment.  Perhaps a forum moderator can adjust this thread)&lt;/li&gt;
&lt;/ol&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: sending data over ble</title><link>https://devzone.nordicsemi.com/thread/36334?ContentTypeID=1</link><pubDate>Wed, 21 Oct 2015 11:22:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6d22057d-460c-405f-8c95-8f6f9682c55d</guid><dc:creator>sowmya</dc:creator><description>&lt;p&gt;Hello ,&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Is it possible to send more than 20 bytes in single packet?&lt;/li&gt;
&lt;li&gt;Is it not possible to send larger data(more than 20 bytes) in notification characteristic?&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Regards,
Sowmya&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: sending data over ble</title><link>https://devzone.nordicsemi.com/thread/36333?ContentTypeID=1</link><pubDate>Wed, 21 Oct 2015 05:30:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:704deef8-ed13-46e7-9bec-584b5c0eaad5</guid><dc:creator>sowmya</dc:creator><description>&lt;p&gt;Hello Bill, thank you for the information. I made an approach to send data with more than 20 bytes by splitting the long data into 20 bytes each and it is working. For long write I need to use user memory space and I am working on that and get back to you.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: sending data over ble</title><link>https://devzone.nordicsemi.com/thread/36332?ContentTypeID=1</link><pubDate>Tue, 20 Oct 2015 23:42:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a8eb461b-d5a6-4072-aff7-d147e6fb26ed</guid><dc:creator>Bill Siever</dc:creator><description>&lt;p&gt;I believe the notify/indicate messages are actually limited by the BLE specs. A few options: a) send multiple notifications/indications (possible with sequence numbers and offsets in addition to the data) or b) Just use the notification to trigger a read from the central (the notification doesn&amp;#39;t contain data; the read could be a long-read of more than 20 bytes. This seems to be the approach recommended in version 4.1 of the Bluetooth specs).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: sending data over ble</title><link>https://devzone.nordicsemi.com/thread/36330?ContentTypeID=1</link><pubDate>Tue, 20 Oct 2015 13:38:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:109bf69f-7a35-4cee-9278-c507e23a512a</guid><dc:creator>sowmya</dc:creator><description>&lt;p&gt;Yes I searched in forum and I am able to send more than 20 bytes. Now I need to go for long write. I will open one more thread regarding long write. Thank you all.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: sending data over ble</title><link>https://devzone.nordicsemi.com/thread/36328?ContentTypeID=1</link><pubDate>Tue, 20 Oct 2015 11:22:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1e2839d9-cc97-4371-bd0c-02cc5aaecac6</guid><dc:creator>MartinBL</dc:creator><description>&lt;p&gt;There are &lt;a href="https://devzone.nordicsemi.com/questions/scope:all/sort:relevance-desc/page:1/query:20%20bytes/"&gt;several threads&lt;/a&gt; regarding this here on devzone, e.g. &lt;a href="https://devzone.nordicsemi.com/question/155/writing-more-than-20-bytes-at-a-time-to-a-characteristic/"&gt;this&lt;/a&gt; and &lt;a href="https://devzone.nordicsemi.com/question/3860/largest-allowed-setting-for-variable-length-characteristic/"&gt;this&lt;/a&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: sending data over ble</title><link>https://devzone.nordicsemi.com/thread/36331?ContentTypeID=1</link><pubDate>Tue, 20 Oct 2015 08:17:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b4a597c5-886a-4eed-9412-5f2ab7fddd23</guid><dc:creator>sowmya</dc:creator><description>&lt;p&gt;Hi, one more question is, how to send more than 20 bytes of data?
I changed the variable length and also maximum length in GATTS structure but it is not working.
Can anyone guide me?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: sending data over ble</title><link>https://devzone.nordicsemi.com/thread/36329?ContentTypeID=1</link><pubDate>Mon, 19 Oct 2015 13:19:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c095aca3-8243-48bd-8561-fe3b825adb6e</guid><dc:creator>sowmya</dc:creator><description>&lt;p&gt;I configured the CCCD to receive characteristic and it is working. I had used MCP to enable notification.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: sending data over ble</title><link>https://devzone.nordicsemi.com/thread/36327?ContentTypeID=1</link><pubDate>Mon, 19 Oct 2015 13:12:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d888a3a9-9abb-490e-8d41-4ce265ef732b</guid><dc:creator>Bill Siever</dc:creator><description>&lt;p&gt;If the characteristic is properly configured as readable, then you can poll for the data (read it).&lt;/p&gt;
&lt;p&gt;If you want push-style data updates (an update is sent every time there&amp;#39;s new data), the characteristic will need to support either indications or notifications as well as have a client characteristic configuration descriptor (CCCD) to allow the client to opt-in to receive the updates. I&amp;#39;m guessing that you haven&amp;#39;t used the MCP to enable the notifications/indications on the characteristic.&lt;/p&gt;
&lt;p&gt;See the other posts on the CCCD, indications or notifications.  There are also several examples in the SDK.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>