<?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>NUS Event Handling and Latency Measurements, (Single Packet Per Connection Interval)</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/35002/nus-event-handling-and-latency-measurements-single-packet-per-connection-interval</link><description>SDK 14.2 / SD132 5.0 / NRF52832 --&amp;gt; NRF52832 
 There is a thread here which discusses &amp;quot;when NUS is ready&amp;quot; : https://devzone.nordicsemi.com/f/nordic-q-a/28208/when-is-nus-ready 
 While BLE_NUS_EVT_RX_DATA is reliable in indicating the system is ready to</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 04 Jun 2018 13:10:30 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/35002/nus-event-handling-and-latency-measurements-single-packet-per-connection-interval" /><item><title>RE: NUS Event Handling and Latency Measurements, (Single Packet Per Connection Interval)</title><link>https://devzone.nordicsemi.com/thread/134576?ContentTypeID=1</link><pubDate>Mon, 04 Jun 2018 13:10:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:603a8834-b057-4478-b329-fb8ae1a86fbb</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Notification packets passed to&amp;nbsp;&lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v5.0.0/group___b_l_e___g_a_t_t_s___f_u_n_c_t_i_o_n_s.html?cp=2_3_1_1_1_2_4_2_4#ga313fe43c2e93267da668572e885945db"&gt;SD_BLE_GATTS_HVX &lt;/a&gt;are queued internally in the softdevice scheduler, which&amp;nbsp;handles the packet transmission and ensure that max. number of packets are sent per connection interval. In other words,&amp;nbsp;you should get max. throughput as long as the application keeps the output buffer full.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Transmission complete is signaled to the application through the&amp;nbsp;&lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v5.0.0/group___b_l_e___g_a_t_t_s___e_n_u_m_e_r_a_t_i_o_n_s.html#ggae537647902af1b05c1e32f12d6b401c7afab96bfa9918017082235f7664919f9d"&gt;BLE_GATTS_EVT_HVN_TX_COMPLETE&lt;/a&gt;&amp;nbsp;event. This&amp;nbsp;event can be combined with a ring buffer, etc if you want to avoid the while loop.&lt;/p&gt;
&lt;p&gt;Also, the number of packets per connection interval depends on the time set aside for each connection, see sdk_config.h::NRF_SDH_BLE_GAP_EVENT_LENGTH. It&amp;#39;s set to 320*1.25 ms in the throughput example.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>