<?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 reduce ble_nus_string_send cost?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/26689/how-to-reduce-ble_nus_string_send-cost</link><description>today simple test ble_nus_string_send time-consuming function, but found that the implementation of a ble_nus_string_send and wait for the success of transmission time-consuming about 11~13ms is a normal value? (ATT_MTU = 247, LL payload size = 31,event</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 09 Nov 2017 14:40:53 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/26689/how-to-reduce-ble_nus_string_send-cost" /><item><title>RE: how to reduce ble_nus_string_send cost?</title><link>https://devzone.nordicsemi.com/thread/104972?ContentTypeID=1</link><pubDate>Thu, 09 Nov 2017 14:40:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d8334cbc-e965-4851-8f39-120c8354d52c</guid><dc:creator>Stayhungry</dc:creator><description>&lt;p&gt;Thank you very much.
Your answer is very useful&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: how to reduce ble_nus_string_send cost?</title><link>https://devzone.nordicsemi.com/thread/104971?ContentTypeID=1</link><pubDate>Thu, 09 Nov 2017 14:35:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2643fff9-bedc-4457-bf53-0e6a68acba4a</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Yes, you should set the TX_QUEUE_SIZE to 6 or higher.&lt;/p&gt;
&lt;p&gt;When you enable connection event extension, it&amp;#39;s not very important which event length you set (but you still need to set the queue size big enough). The softdevice will try to send as much as possible until the buffer is empty or when the connection event is finish.&lt;/p&gt;
&lt;p&gt;Most important, you need to get the connection interval to as low as possible, 7.5ms is the lowest.&lt;/p&gt;
&lt;p&gt;I would suggest you to have a look at our ble_app_att_mtu_throughput in the SDK.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: how to reduce ble_nus_string_send cost?</title><link>https://devzone.nordicsemi.com/thread/104970?ContentTypeID=1</link><pubDate>Thu, 09 Nov 2017 10:15:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:466b617a-79f5-47a0-952e-ac42c370fb84</guid><dc:creator>Stayhungry</dc:creator><description>&lt;p&gt;Thanks,Hung Bui.&lt;/p&gt;
&lt;p&gt;I do not know my understanding right, in the ble_gatts.h file BLE_GATTS_HVN_TX_QUEUE_SIZE_DUFAULT this macro definition, if I want to send 6 LL packet in a conneviton event, as long as this is set to 6, and then continue to call sd_ble_gatts_hvx until NRF_ERROR_RESOURCES return, and then Waiting for BLE_GATTS_EVT_HVN_TX_COMPLETE on it, if set to 1, can only send one LL packet.&lt;/p&gt;
&lt;p&gt;Another question, if I understand correctly, when I enable the Connetion event extendsion, does this macro definition make sense?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: how to reduce ble_nus_string_send cost?</title><link>https://devzone.nordicsemi.com/thread/104969?ContentTypeID=1</link><pubDate>Wed, 08 Nov 2017 14:23:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4200d280-7f48-46fd-9eb2-ac976a090858</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Have  look here:
&lt;a href="https://devzone.nordicsemi.com/question/176156/nrf52840-ble-transfer-using-nus-service/"&gt;devzone.nordicsemi.com/.../&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>