https://forge.codesys.com/forge/talk/Engineering/thread/3dc9608738/2020-02-27T14:24:11.265000ZRecent posts to EtherCAT_Master - SDO timeout2020-02-27T14:24:11.265000Z2020-02-27T14:24:11.265000Zeschwellingerhttps://forge.codesys.com/u/eschwellinger/https://forge.codesys.comee66fa269b2a6c320839e1249f286121b2ca1872

<div class="markdown_content"><p>Hi,<br/> With 3.5SP14 a change was made to set only the FMMU for the mailbox status bit when going from init to preop. <br/> The normal input and output FMMU are not needed at this point. Some devices do not work with this procedure. The mailbox status flags is always 0 and the working counter is not increased. Only if all FMMUs are set the status bit is transmitted. <br/> In our opinion it is an error in the slave firmware but in the master a workaround is possible and n ow implmented to the 3.5Sp15 release.<br/> BR<br/> Edwin</p></div>

2020-02-27T14:24:10.817000Z2020-02-27T14:24:10.817000Zkurvanovhttps://forge.codesys.com/u/kurvanov/https://forge.codesys.com5a684c9a16b553fea54f4a2af6b4ffff8a955519

<div class="markdown_content"><p>Good morning </p> <p>Thank you for this feedback. <br/> I do not exclude a bug in the slave. Could you give some details about the origin of the bug you suspect in the slave. <br/> Thus, we would also take the opportunity to fix this on the slave side. </p> <p>Thank you for your help</p> <p>Best regards.<br/> Kurvanov</p></div>

2020-02-27T14:24:09.563000Z2020-02-27T14:24:09.563000Zeschwellingerhttps://forge.codesys.com/u/eschwellinger/https://forge.codesys.comde18a5e6f98c6cfdd518848ef8fc8f5ff06c6471

<div class="markdown_content"><p>Hi,<br/> think this wil be solved with the 3.5SP15 version.<br/> This is more or less a bug in the slave which will then be workarounded by a change in the master.<br/> BR<br/> Edwin</p></div>

2020-02-27T14:24:09.096000Z2020-02-27T14:24:09.096000Zkurvanovhttps://forge.codesys.com/u/kurvanov/https://forge.codesys.comb6f621528488c2deb353dfb9217de46d45573bcf

<div class="markdown_content"><p>Dear forum members, </p> <p>I had my raspberry Pi communicating with a Hilscher Netx500 over Ethercat. It worked like a charm for years with several Codesys version up to 3.5.12.30<br/> Today, I updated both Codesys engineering tool to 3.5SP14 and Raspberry firmware to 3.5.14.20</p> <p>Now, when starting the Ethercat communication I got error messages like: </p> <div class="codehilite"><pre><span></span><span class="n">SDO</span> <span class="n">timeout</span> <span class="n">Address</span><span class="p">:</span> <span class="mi">1001</span> <span class="k">Index</span><span class="p">:</span> <span class="mi">16</span><span class="o">#</span><span class="mi">1</span><span class="n">A02</span> <span class="n">SubIndex</span><span class="p">:</span> <span class="mi">0</span> <span class="k">Data</span><span class="p">:</span> <span class="mi">16</span><span class="o">#</span><span class="mi">00</span> <span class="k">Result</span><span class="p">:</span> <span class="mi">16</span><span class="o">#</span><span class="mi">00</span> </pre></div> <p>I assume there is a problem with slave initialisation at bus startup. I also found out a list of Ethercat Standar AL Status code. In this list, error code 16#00 means 'No Error'. <br/> I'm not sure this list apply to the reported error.<br/> Thus, I'm stuck and can't make my device work again. </p> <p>Is there somewhere a parameter to adjust timeout delay ? </p> <p>I'm attaching the full device log</p> <p>Any help on that matter will be greatly appreciated.</p> <p>Best regards.</p> <p><a class="" href="https://forum.codesys.com//download/file.php?id=4679" rel="nofollow">Codesys SDO timeout.zip <span><span>[5.71 KiB]</span></span></a></p></div>