AB-Prosoft communication gateways PLX32-EIP-MBTCP-Yokogawa Centum DCS, periodikally Modbus TCP Fail whith error on DCS A3B0

Hello. I am experiencing an intermittent issue with the communication link to the DCS.
The system consists of an Allen-Bradley 1756-L71 PLC with a redundant configuration and a ring topology. There are two ProSoft PLX32-EIP-MBTCP gateways, which exchange data with the Yokogawa CENTUM DCS via Modbus TCP. In the opposite direction, we receive several signals via Modbus, such as heartbeat, reset, etc., as well as one 32-bit REAL analog signal.
Periodically, the communication with the DCS is lost. Yokogawa has a utility that can monitor the status of our gateways from the Modbus side. It indicates that the gateways are 1PC (Unhealthy) due to an internal error A3B0.
When both of our gateways are shown as Unhealthy, they are still accessible. When checked using ModScan32, the gateways continue to provide data. There is also a firewall in the communication path.
Could you please advise which parameters in the ProSoft gateway or PLC should be configured or checked to maintain stable communication with the DCS? This issue does not occur all the time, but recently the DCS has been detecting our gateways as closed/unhealthy, and data exchange stops.
I have already tried loading different backups, including backups from periods when the communication was stable, but this did not resolve the issue.
Could you please advise what parameters or settings we should pay particular attention to?
 
Top