I am working on a project where my PLC is quite far from where my supervisor is installed, so to establish communication we are using radios and the Modbus TCP protocol. It is working, but not 100% as we would like.
From time to time, some packets are lost and my templates turn red.
In the binding configurations in the templates, select the Overaly Opt-out option.
Polling based protocols over a slow connection is not recommended, look into something like MQTT which is much better suited for low bandwidth connections.
If you are dead set on modbus, adjust your timeout settings for the device connection on the gateway.
Using Overaly worked here, Ryan, thank you very much!
Is there another place where I can configure this read timeout to fail, other than here in device connections? I don't want to change this timeout here.
Yes... I'm testing other parts of the software here on the workbench and it's overloaded. When I'm in the field with the radio, I'll see how it is there.
It's fine on the Ignition side of things. It's unusual for a Modbus device to support so many concurrent requests... and if you're not currently communicating over the radio you mentioned I wouldn't be surprised if it failed spectacularly when you start.
