<?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>Gazell: Possible to send every timeslot?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/27490/gazell-possible-to-send-every-timeslot</link><description>Hi, 
 I am using as settings: 
 timeslot period: 600 us 
 data rate: 2M 
 channel table size: 4 
 timeslots when out of sync: 8 
 timeslots per channel: 2 
 sync lifetime: 10 
 max tx attempts: 2 
 channel selection policy: use current 
 I am</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 09 May 2022 06:13:27 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/27490/gazell-possible-to-send-every-timeslot" /><item><title>RE: Gazell: Possible to send every timeslot?</title><link>https://devzone.nordicsemi.com/thread/366831?ContentTypeID=1</link><pubDate>Mon, 09 May 2022 06:13:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1c38cd61-dd60-49dd-919a-f0725ee8ae07</guid><dc:creator>__karel</dc:creator><description>&lt;p&gt;congratulations on the badge!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Gazell: Possible to send every timeslot?</title><link>https://devzone.nordicsemi.com/thread/108579?ContentTypeID=1</link><pubDate>Thu, 23 Nov 2017 11:47:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4afe77ed-69b7-4d09-b706-e79121d39e6c</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Niels,&lt;/p&gt;
&lt;p&gt;No, it&amp;#39;s not possible. The reason is that we need enough time for listening to ACK.&lt;/p&gt;
&lt;p&gt;Gazel is built in the way that ACK should be used to tell the node if it&amp;#39;s synchronized with the host or not. Also there should be ACK payload if needed also. Packet payload + ACK + ACK payload won&amp;#39;t be able to fit inside a 600us timeslot. This is why we only send packet every other timeslot.&lt;/p&gt;
&lt;p&gt;If you don&amp;#39;t need ACK, I would suggest to use ESB instead. But then you will have also skip channel hopping feature.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>