<?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>Testing LE Ping between two nrf52s</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/20099/testing-le-ping-between-two-nrf52s</link><description>Hi 
 I am trying to test the LE Ping feature between two nrf52s. I am enabling the LE Ping feature from one device via: 
 ble_opt_t opt = {0};

opt.gap_opt.auth_payload_timeout.conn_handle = VaidHandle;
opt.gap_opt.auth_payload_timeout.auth_payload_timeout</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 13 Mar 2017 21:43:44 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/20099/testing-le-ping-between-two-nrf52s" /><item><title>RE: Testing LE Ping between two nrf52s</title><link>https://devzone.nordicsemi.com/thread/78263?ContentTypeID=1</link><pubDate>Mon, 13 Mar 2017 21:43:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c59caab4-8040-4a89-83af-a346d13519a1</guid><dc:creator>Youssif</dc:creator><description>&lt;p&gt;So we found that one way to test this is by configuring the connection interval. Having &lt;code&gt;auth_payload_timeout&lt;/code&gt; set to be lower than (2 x connection interval) on an encrypted connection will trigger &lt;code&gt;BLE_GAP_EVT_TIMEOUT&lt;/code&gt;. The reason for this is that two connection intervals are required for LE Ping, one for request and one for response.&lt;/p&gt;
&lt;p&gt;For example if &lt;code&gt;auth_payload_timeout&lt;/code&gt; is set to 20ms, having the connection interval set to 15ms will ensure that at least 30ms will be needed for ping request and ping response, therefore the device will time out before the response is returned, triggering the &lt;code&gt;BLE_GAP_EVT_TIMEOUT&lt;/code&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Testing LE Ping between two nrf52s</title><link>https://devzone.nordicsemi.com/thread/78262?ContentTypeID=1</link><pubDate>Thu, 02 Mar 2017 15:52:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:14fc25dc-a802-4cc1-8811-4b1727b81653</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Youssif,&lt;/p&gt;
&lt;p&gt;LE Ping is only sent when there is encryption on the link and when there is no encrypted packet exchanged between the peer (only empty packet sent) until timeout is hit.&lt;/p&gt;
&lt;p&gt;You may want to use &lt;a href="https://www.nordicsemi.com/eng/Products/Bluetooth-Smart-Bluetooth-low-energy/nRF-Sniffer/"&gt;a sniffer&lt;/a&gt; to capture on air activity.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>