<?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 write module</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/43140/queued-write-module</link><description>Hi, 
 I configured nrf_ble_qwr to use 256 byte long buffer in my BLE peripheral. I registered my value handles (2) which I want to support long writes using nrf_ble_qwr_attr_register. I set NRF_BLE_QWR_MAX_ATTR = 2. On connected event I assign connection</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 30 Jan 2019 17:03:56 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/43140/queued-write-module" /><item><title>RE: Queued write module</title><link>https://devzone.nordicsemi.com/thread/168764?ContentTypeID=1</link><pubDate>Wed, 30 Jan 2019 17:03:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3b8ac3a9-4f4e-4571-9f4e-7619a03d210d</guid><dc:creator>gaminn</dc:creator><description>&lt;p&gt;I set wr_auth = 1 when creating my characteristic and now it works.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Queued write module</title><link>https://devzone.nordicsemi.com/thread/168759?ContentTypeID=1</link><pubDate>Wed, 30 Jan 2019 16:23:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0e6f724b-5a53-45c4-bb70-4b2867c61f4e</guid><dc:creator>gaminn</dc:creator><description>&lt;p&gt;I discovered that on execute write command from central I receive BLE_GATTS_EVT_WRITE with&amp;nbsp;p_evt_write-&amp;gt;op ==&amp;nbsp; BLE_GATTS_OP_EXEC_WRITE_REQ_NOW. This is not handled by nrf_ble_qwr. I probably doesn&amp;#39;t understand what is the purpose of nrw_ble_qwr module and if I should use it.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Queued write module</title><link>https://devzone.nordicsemi.com/thread/168714?ContentTypeID=1</link><pubDate>Wed, 30 Jan 2019 13:37:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:93f09242-fd12-416b-a797-b287923555f8</guid><dc:creator>gaminn</dc:creator><description>&lt;p&gt;Unfortunately I can&amp;#39;t modify the central.&lt;/p&gt;
&lt;p&gt;I read documentation but still I&amp;#39;m not able to receive the data. Documentation states that on execute write command from central we receive&amp;nbsp;&lt;a class="el" href="https://www.nordicsemi.com/DocLib/Content/SDK_Doc/nRF5_SDK/v15-2-0/group__nrf__ble__qwr#ggacf965a6f79276f170544a8df9d5485c3a0e1728d711d173ddb09d32673c99fe58"&gt;NRF_BLE_QWR_EVT_AUTH_REQUEST&lt;/a&gt;&amp;nbsp;event in nrf52 peripheral.&amp;nbsp;However I never receive it. I set breakpoint in nrf_ble_qwr.c, function on_rw_authorize_request. It never hits this function.&lt;/p&gt;
&lt;p&gt;I&amp;#39;m migrating nrf51 project that used old SDK to nrf52832 SDK 15. Old project worked&amp;nbsp;regarding queued writes - I passed my buffer to softdevice on BLE_EVT_USER_MEM_REQUEST using&amp;nbsp;sd_ble_user_mem_reply() and then on BLE_GATTS_EVT_WRITE (when p_evt_write-&amp;gt;op == BLE_GATTS_OP_EXEC_WRITE_REQ_NOW) I read received data from the buffer.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Queued write module</title><link>https://devzone.nordicsemi.com/thread/168705?ContentTypeID=1</link><pubDate>Wed, 30 Jan 2019 13:19:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:abcb3072-072c-4a7c-aa99-cca2fae816b3</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;If you have a requirement to use queued write because you cannot control the central, then yes, you can use the queued write module. But the scenario you describe where you just need to split long data in several chunks is not a good use case for queued writes (it is simply overcomplicated, since it is designed for a different and more complex use case), so if you can change the central to avoid it that would probably be the best.&lt;/p&gt;
&lt;p&gt;If you decide to stick with queued writes, you can refer to the q&lt;a href="https://www.nordicsemi.com/DocLib/Content/SDK_Doc/nRF5_SDK/v15-2-0/lib_ble_queued_write"&gt;ueued writes module documentation&lt;/a&gt; in addition to the example.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Queued write module</title><link>https://devzone.nordicsemi.com/thread/168702?ContentTypeID=1</link><pubDate>Wed, 30 Jan 2019 13:11:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:18e6fb81-c653-447c-b436-7075e5a0aee2</guid><dc:creator>gaminn</dc:creator><description>&lt;p&gt;Thanks. I have BLE central that splits long data to several chunks and then writes it to my characteristics using several &amp;quot;prepare write requests&amp;quot; (it sets offset and length of current chunk) and then it executes &amp;quot;execute write request&amp;quot;.&amp;nbsp;Am I going to receive this data using&amp;nbsp;Queued write module or how in SDK 15?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Queued write module</title><link>https://devzone.nordicsemi.com/thread/168695?ContentTypeID=1</link><pubDate>Wed, 30 Jan 2019 12:49:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e34cfa76-bbf0-402f-b1de-a0821447231c</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;The example you refer to, the &lt;a href="https://www.nordicsemi.com/DocLib/Content/SDK_Doc/nRF5_SDK/v15-2-0/ble_sdk_app_queued_writes"&gt;Queued Writes Application&lt;/a&gt;, is probably the best example for seeing the Queued write module in use. However, I did not understand why you want to use the queued writes module?&lt;/p&gt;
&lt;p&gt;Just so there are no misunderstandings I want to emphasize that queued writes only make sense if you want to synchronize writes to multiple characteristics, so that the change take effect simultaneously. If you just want to write to a long characteristic and have to split it over multiple writes, then you should write with offset instead. That is simpler and has less overhead.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>