https://forge.codesys.com/forge/talk/Runtime/thread/6904e7ece2/2020-02-27T16:15:56.731000ZRecent posts to Modbus TCP Slave Timing Performance2020-02-27T16:15:56.731000Z2020-02-27T16:15:56.731000Zeschwellingerhttps://forge.codesys.com/u/eschwellinger/https://forge.codesys.com1149da37518aea0e34861292d64e0a1a67c1a433

<div class="markdown_content"><p>Hi,<br/> there is no known change on that,<br/> but even if you switch back or update the libs should give the result both version behave in the same way.</p> <p>How to switch between the versions?</p> <p>Rightclick on the modebus device in the device three - update -&gt; show all version... then either SP14 or SPxx what ever you want.<br/> This switches the library version too.</p> <p>BR<br/> Edwin</p></div>

2020-02-27T16:15:55.914000Z2020-02-27T16:15:55.914000Zcelliotthttps://forge.codesys.com/u/celliott/https://forge.codesys.come05b2b5422a19ed255bea1d24b8a8d2cb26bbfec

<div class="markdown_content"><p>I recently upgraded Codesys from V3.5.14.0 to V3.5.14.20 and the performance of my Modbus TCP Slave devices has degraded where I'm getting around a 5 second poll time, where I was getting around 2 seconds with the previous version.</p> <p>Looking at the Modbus TCP Slave object within the watch window, I noticed now the MB_ERRORCODES cycles through either RESPONSE_SUCCESS, RESPONSE_INVALID_HEADER or UNDEFINED.</p> <p>I'm running the Modbus TCP Slave device with a cyclic trigger and I've tried changing settings such as timeout, trigger time, etc. I've also tried running via a rising edge trigger, but no improvement observed.</p> <p>Also, I'm running Codesys on a Windows 7 64 bit PC and a RP2 single core application where I upgraded both the development environment and RP2 both to V3.5.14.20. The version of the Modbus TCP Slave driver is V3.5.12.0.</p> <p>Any ideas on how I can improve the Modbus TCP Slave polling time, I need short as possible to suit my application?</p></div>