<?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>Delay data received at long ranges</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/66643/delay-data-received-at-long-ranges</link><description>Hello, 
 nRFSD5 v16.0, softdevice v.7.0.1, nRF52840 
 We have an application where we receive data from mobile application whenever it writes to a certain UUID. The data is collected at nRF52 hardware end when BLE_GATTS_EVT_WRITE event is fired. 
 However</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 05 Oct 2020 12:12:18 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/66643/delay-data-received-at-long-ranges" /><item><title>RE: Delay data received at long ranges</title><link>https://devzone.nordicsemi.com/thread/272963?ContentTypeID=1</link><pubDate>Mon, 05 Oct 2020 12:12:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b38503e1-1fbc-4e1e-9c28-c88bfe5d6931</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;There may be several reasons for this. Your connection parameters are probably different when you are connected to an nRF52 and a phone.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;My initial thought is that the packet length may differ between the two connections. If you are sending long packets, it means longer time on air, and a larger risk for noise and faulty CRCs.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Another possibility is that you may have different connection intervals on the phone and the nRF. Remember that it is the central that decides the connection interval, so even if you set the preferred connection interval on the peripheral, the central may choose something completely different.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Is it possible to capture a sniffer trace using the &lt;a href="https://www.nordicsemi.com/Software-and-tools/Development-Tools/nRF-Sniffer-for-Bluetooth-LE" rel="noopener noreferrer" target="_blank"&gt;nRF Sniffer&lt;/a&gt;? Preferably a sniffer trace of both scenarios, phone and nRF52 as the central. If you can sniff the conection while you have the 5 second delay, perhaps it can reveal why it takes so long.&lt;/p&gt;
&lt;p&gt;BR,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>