<?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 anomaly when using Fast ramp-up</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/92138/esb-anomaly-when-using-fast-ramp-up</link><description>To achieve the maximum transfer rate over ESB, I added the following expression to the ESB initialization function: 
 NRF_RADIO-&amp;gt;MODECNF0 = (NRF_RADIO-&amp;gt;MODECNF0 &amp;amp; ~RADIO_MODECNF0_RU_Msk) | RADIO_MODECNF0_RU_Fast &amp;lt;&amp;lt; RADIO_MODECNF0_RU_Pos; 
 
 This really</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 21 Sep 2022 11:58:15 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/92138/esb-anomaly-when-using-fast-ramp-up" /><item><title>RE: ESB anomaly when using Fast ramp-up</title><link>https://devzone.nordicsemi.com/thread/387282?ContentTypeID=1</link><pubDate>Wed, 21 Sep 2022 11:58:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d7d7730a-5fb4-4bb3-8a9c-21da187bc882</guid><dc:creator>ovrebekk</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;The ESB library hasn&amp;#39;t been tested for use with fast mode, so possibly there is some timing issues that could pop up in this case.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;You have checked that receiving 252 byte ACK payloads work fine without this change?&lt;/p&gt;
&lt;p&gt;You could try to increase the&amp;nbsp;RX_ACK_TIMEOUT_US_2MBPS parameter, but it doesn&amp;#39;t really make logical sense that you would have to increase this when using faster startup.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Possibly the issue is caused by the&amp;nbsp;preparation of the ACK payload taking too much time when you have a long payload and a fast startup, since the MCU has much less time before the radio expects a packet to be ready.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards&lt;br /&gt;Torbjørn&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ESB anomaly when using Fast ramp-up</title><link>https://devzone.nordicsemi.com/thread/387069?ContentTypeID=1</link><pubDate>Tue, 20 Sep 2022 11:52:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:076cedb2-2492-4314-b8cf-67f2460c90bf</guid><dc:creator>Andrej102</dc:creator><description>&lt;p&gt;Clarification: 1700 kbit/s is without reverse packets. Reverse packets will certainly reduce the speed. Here the question is not in getting the maximum speed, but in the abnormal behavior of the ESB protocol with the enabled setting fast ramp-up.&lt;/p&gt;
&lt;p&gt;How to get rid of it? In reality, my ACK packets rarely contain a payload, but when it is present, its length is 252 bytes, and this anomaly prevents me from working.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>