<?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>Some clarity on Gazell packet rates needed</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/52122/some-clarity-on-gazell-packet-rates-needed</link><description>I&amp;#39;m a little confused by the packet rate I&amp;#39;m getting on Gazell. Or rather I&amp;#39;m confused by the low number of &amp;#39;timeouts&amp;#39; I&amp;#39;m seeing - I&amp;#39;d expect to see more, and would like to understand why I&amp;#39;m not. 
 I&amp;#39;m currently using mostly default settings for Device</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 16 Sep 2019 16:45:49 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/52122/some-clarity-on-gazell-packet-rates-needed" /><item><title>RE: Some clarity on Gazell packet rates needed</title><link>https://devzone.nordicsemi.com/thread/209910?ContentTypeID=1</link><pubDate>Mon, 16 Sep 2019 16:45:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c3790f92-ba9e-453b-bc63-b51eed151ae5</guid><dc:creator>Pete W</dc:creator><description>&lt;p&gt;Thanks for the reply Kenneth. I missed the bit in the user guide where it says that the timeslot counter resets to 0 when the Ack is received, and an attempt to send the next new packet is only made when the counter rolls back to 0, which makes sense.&lt;/p&gt;
&lt;p&gt;Regards&lt;/p&gt;
&lt;p&gt;Pete&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Some clarity on Gazell packet rates needed</title><link>https://devzone.nordicsemi.com/thread/209902?ContentTypeID=1</link><pubDate>Mon, 16 Sep 2019 16:09:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:145ede9c-2da1-4f8d-a4d1-ebc11c522db7</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;There is drift between device and host and there is no time information in any of the packets. So the device simply synchronize to the last successful transmit acknowledgement. This successful exchange may have happened at any time with the 600us * 2 &amp;quot;window&amp;quot; (2 is required to ensure that independent of packets size in either direction 1 complete&amp;nbsp;transmit + ack is guaranteed to get through on the channel, even due to drift in clocks between the two peers). So it&amp;nbsp;is not designed to do more than 1 packet in each 1.2ms window in best case.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>