Activity for fmonhttps://forge.codesys.com/u/fmon/activity/2025-03-18T10:27:06.252000ZRecent activity for fmonfmon modified a comment on discussion Engineering 🇬🇧2025-03-18T10:27:06.252000Z2025-03-18T10:27:06.252000Zfmonhttps://forge.codesys.com/u/fmon/profile/https://forge.codesys.com/forge/talk/Engineering/thread/70f789268f/?limit=25#44c8Problem solved The client modbus cycle time was linked to a task at 500ms. Whereas the channel modbus was at 200ms. Certainly problem of packages synchronisation. I let the client modbus cycle time to be handled by itself (See attachement) --> "Use the bus cyle time parameters" (traduce from french) See attachementfmon posted a comment on discussion Engineering 🇬🇧2025-03-18T10:25:34.018000Z2025-03-18T10:25:34.018000Zfmonhttps://forge.codesys.com/u/fmon/profile/https://forge.codesys.com/forge/talk/Engineering/thread/70f789268f/?limit=25#44c8Problem solved The client modbus cycle time was linked to a task at 500ms. Whereas the channel modbus was at 200ms. Certainly problem of packages synchronisation. I let the client modbus cycle time to be handled by itself (See attachement) --> "Use the bus cyle time parameters" (traduce from french) See attachementfmon posted a comment on discussion Codesys V2.3 🇬🇧2025-03-18T10:17:48.765000Z2025-03-18T10:17:48.765000Zfmonhttps://forge.codesys.com/u/fmon/profile/https://forge.codesys.com/forge/talk/CODESYS-V2/thread/e4b047d577/?limit=25#234aProblem solved The client modbus cycle time was linked to a task at 500ms. Whereas the channel modbus was at 200ms. Certainly problem of packages synchronisation. I let the client modbus cycle time to be handled by itself (See attachement) --> "Use the bus cyle time parameters" (traduce from french) See attachementfmon posted a comment on discussion Codesys V2.3 🇬🇧2025-03-17T08:52:52.486000Z2025-03-17T08:52:52.486000Zfmonhttps://forge.codesys.com/u/fmon/profile/https://forge.codesys.com/forge/talk/CODESYS-V2/thread/e4b047d577/?limit=25#c2a2Hello, I am using codesys Modbus TCP client (4.4.0.0) to communicate with a python modbus server (package pyModbusTCP). I first start my python server on the distant machine. After a fresh codesys compilation, a plc connection/transfer and a PLC run, the modbus connection is OK. Every time in this context the connection is created correctly. When I shut down the server, the modbus connection falls, that is normal. When I restart the python server, impossible to recreate the modbus connexion. With...fmon modified a comment on discussion Engineering 🇬🇧2025-03-14T18:16:46.967000Z2025-03-14T18:16:46.967000Zfmonhttps://forge.codesys.com/u/fmon/profile/https://forge.codesys.com/forge/talk/Engineering/thread/70f789268f/?limit=25#8687Hello, I am using codesys Modbus TCP client (4.4.0.0) to communicate with a python modbus server (package pyModbusTCP). I first start my python server on the distant machine. After a fresh codesys compilation, a plc connection/transfer and a PLC run, the modbus connection is OK. Every time in this context the connection is created correctly. When I shut down the server, the modbus connection falls, that is normal. When I restart the python server, impossible to recreate the modbus connexion. With...