<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent posts to Modbus : dis- / re-connect cable: modbus does not re-start </title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/70f789268f/" rel="alternate"/><link href="https://forge.codesys.com/forge/talk/Engineering/thread/70f789268f/feed.atom" rel="self"/><id>https://forge.codesys.com/forge/talk/Engineering/thread/70f789268f/</id><updated>2025-03-18T10:25:30.590000Z</updated><subtitle>Recent posts to Modbus : dis- / re-connect cable: modbus does not re-start </subtitle><entry><title>Modbus : dis- / re-connect cable: modbus does not re-start </title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/70f789268f/?limit=25#44c8" rel="alternate"/><published>2025-03-18T10:25:30.590000Z</published><updated>2025-03-18T10:25:30.590000Z</updated><author><name>fmon</name><uri>https://forge.codesys.com/u/fmon/</uri></author><id>https://forge.codesys.comf0614d8fb381a15cac32939ba071f2921e883ac0</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Problem solved&lt;/p&gt;
&lt;p&gt;The client modbus cycle time was linked to a task at 500ms. Whereas the channel modbus was at 200ms. Certainly problem of packages synchronisation.&lt;/p&gt;
&lt;p&gt;I let the client modbus cycle time to be handled by itself (See attachement) --&amp;gt; "Use the bus cyle time parameters" (traduce from french)&lt;br/&gt;
See attachement&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Modbus : dis- / re-connect cable: modbus does not re-start </title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/70f789268f/?limit=25#8687" rel="alternate"/><published>2025-03-14T17:46:15.443000Z</published><updated>2025-03-14T17:46:15.443000Z</updated><author><name>fmon</name><uri>https://forge.codesys.com/u/fmon/</uri></author><id>https://forge.codesys.com3684c2b3b26c417daed2a8ac1eefb85d05442d78</id><summary type="html"/></entry></feed>