<?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>Queued Writes characteristic value longer than 220B</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/4538/queued-writes-characteristic-value-longer-than-220b</link><description>Hello. 
 I neet to write long characteristic value (250B). I use GATTS Queued Writes from example devzone.nordicsemi.com/.../ based on developer.nordicsemi.com/.../a00892.html 
I send data from nRF Master Control Panel (Android 4.4, Nexus 4) and watch</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 21 Nov 2014 11:13:42 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/4538/queued-writes-characteristic-value-longer-than-220b" /><item><title>RE: Queued Writes characteristic value longer than 220B</title><link>https://devzone.nordicsemi.com/thread/16084?ContentTypeID=1</link><pubDate>Fri, 21 Nov 2014 11:13:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f4cca85d-27f1-4b6d-ad1a-1323627aed90</guid><dc:creator>P&amp;#229;l H&amp;#229;land</dc:creator><description>&lt;p&gt;If you have a 250 byte long characteristic value it would be:
ceil(250*23/17)+2 = 341 byte&lt;/p&gt;
&lt;p&gt;Not sure if it is documented anywhere, the structure used for reading back the part values can be located here: &lt;a href="http://developer.nordicsemi.com/nRF51_SDK/doc/7.0.1/s110/html/a01075.html"&gt;developer.nordicsemi.com/.../a01075.html&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Queued Writes characteristic value longer than 220B</title><link>https://devzone.nordicsemi.com/thread/16083?ContentTypeID=1</link><pubDate>Fri, 21 Nov 2014 10:38:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:612f48f9-c358-4c4c-9d66-e1dc6c422269</guid><dc:creator>Piko</dc:creator><description>&lt;p&gt;Hello
Thanks for answer. But my problem isn&amp;#39;t space provided by me. When I receive BLE_EVT_USER_MEM_REQUEST I allocate by sd_ble_user_mem_reply memory block equals to characteristic value = 250B. I even try allocate more = 300. But, with that you write, this means that I need more memory than characteristic value lenght. Is this right? Where I can read about that?
thanks
Piko&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Queued Writes characteristic value longer than 220B</title><link>https://devzone.nordicsemi.com/thread/16082?ContentTypeID=1</link><pubDate>Fri, 21 Nov 2014 10:25:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b3d31ecf-f197-4463-8907-5ef180b0215e</guid><dc:creator>P&amp;#229;l H&amp;#229;land</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;Piko, the best way to determine how much space you should provide when you receive BLE_EVT_USER_MEM_REQUEST is the following calculation.&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;H = handle (2 byte) + offset (2 byte) + length (2 byte) = 6
MTU = 23
DATA = MTU-H = 17

Total Memory = ceil(Char Max Len*MTU/DATA) + 2
&lt;/code&gt;&lt;/pre&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>