Hi,
I have a problem with some FMD16 PLC's. We have 15 of them controlling pumps around a site and all of them are a little temperamental when responding to Modbus TCP requests.
We frequently have communication errors that require re-booting the PLC's to get the communication going again only for it to fail at some point in the future, this can be 1 day or 1 month...
We use the web server function also and this works fine so I don't think the issue is with the connection more the PLC.
All the PLC's are connected via wifi aerials and generally respond to a ping in less than 100-250 ms so I'm wondering if this is a latency issue on the modbus protocol??
Can this response time be adjusted??
The TCP master is a SCADA program with polling set to 1000ms for each register / device, with a timeout set to 5000ms. We only read two registers from each PLC.
The SCADA has a re-connect function that upon connection failure tries to re-connect, this is set to 10000ms.
All of the above work fine when the PLC has been power cycled (a online reset does not help get the communication going
) until the comms error returns.
Can I use a set system command on port 4 to set the protocol to modbus without affecting the webserver connections?
The connections are as default 3 server and 3 Modbus connections.
Running out of ideas