<?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>ESB retransmission delay</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/71688/esb-retransmission-delay</link><description>Hi - I noticed an issue in the esb library as of nRF5 SDK v17.0.2 and am looking for clarification. 
 In the function update_radio_bitrate , the minimum retransmission delay is checked by the following code: 
 
 // Ensure that we do not attempt retransmitting</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 17 Feb 2021 13:07:20 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/71688/esb-retransmission-delay" /><item><title>RE: ESB retransmission delay</title><link>https://devzone.nordicsemi.com/thread/294866?ContentTypeID=1</link><pubDate>Wed, 17 Feb 2021 13:07:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a752e0e7-3f25-4e95-a9f2-186713b65b09</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp;&lt;/p&gt;
[quote user=""]With&amp;nbsp;2 Mbps bit rate, this implies that the minimum delay is (48 + 62 = ) 110 µs. But&amp;nbsp;when the retransmit_delay value is actually used in the &lt;code&gt;on_radio_disabled_tx&lt;/code&gt; function:[/quote][quote user=""]&lt;p&gt;Any value less than 130&amp;nbsp;&lt;span&gt;µ&lt;/span&gt;s&amp;nbsp;would then underflow and give unintended behavior.&lt;/p&gt;
&lt;p&gt;Could you clarify if this reading of the code is correct? And&amp;nbsp;why is 130 subtracted from the retransmit delay when it&amp;#39;s used for the compare interrupt?&lt;/p&gt;[/quote]
&lt;p&gt;You are correct. Anything lower than .retransmit_delay= 130, and the uint16_t will roll over, and it&amp;#39;ll wait for ~65ms before retransmitting.&lt;/p&gt;
&lt;p&gt;The library is implemented to be compatible with the nRF24L-series devices, which use 130 us to ramp up the radio (same when it switches RX-&amp;gt;TX or TX-RX). There should be a check here from our side to validate the local configuration.&amp;nbsp;This is a&amp;nbsp;clear bug from our side! I&amp;#39;ll create an internal report on this matter. Thank you very much for reporting this back to us, and helping us improve our delivery!&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;From the nRF52-series and forward, the radio ramp up time can be configured to be lower; but its kept at a legacy ramp-up time in this specific library to be on-air compatible with nRF51-series and nRF24L-series devices.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;/p&gt;
&lt;p&gt;Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>