Ignition Gateway OPC error, caused by Groov Epic running codesys

David_HargisToday is the anniversary of the day you joined our community!

1m

We have an Ignition Gateway that lost its OPC Connections to 3 separate Opto-22 Groov Epic R2 Controllers, all running the CodeSys platform. The following was the log error message on the gateway. The OPC interfaces are used to bring the CodeSys program tags into Ignition. As far as we know, there was nothing weird about the network setup. There are about 100 devices on the static IP network. Most of the “Traffic” is ethernet/IP data between the 3 Groov Epic controllers and the 85 VSD/starters (Eaton Power Equipment). The network has been fine for a few months with no issues. We did have some phoenix contact wireless access equipment that was technically plugged in but not configured on the same subnet. That equipment may have caused the blip, but I am unsure what caused this, and am curious if this is an Opto-22 issue or an Ignition issue. We had to restart the Ignition server and re-compile/re-download the codesys programs into each controller to resolve the issue. All of the drives faulted out on field bus error so the Ethernet/IP data definitely dropped out. None of the controllers faulted but the ethernet/IP connections did. Everything looks good now after restart/re-download. Was it just a blip or is there some type of code or gateway configuration fix we could try? Has anyone else had issues with OPC tag connections dropping out on the Ignition gateway with the following messages?

We are running Version: 8.1.32 (b2023091211)

UascClientMessageHandler 30Aug2024 10:01:34 [remote=/172.168.1.200:4840] Exception caught: An existing connection was forcibly closed by the remote host
UascClientAcknowledgeHandler 30Aug2024 09:56:26 [remote=/172.168.1.200:4840] Exception caught: UaException: status=Bad_TcpMessageTypeInvalid, message=unknown message type: 262245
UascClientAcknowledgeHandler 30Aug2024 09:56:26 [remote=/172.168.1.200:4840] Exception caught: UaException: status=Bad_TcpMessageTypeInvalid, message=unknown message type: 262245
…drivers.TCPDriver[AugustaCP2].TCPConnect 30Aug2024 09:20:25 Error connecting to 172.168.1.202:4840. connection timed out: /172.168.1.202:4840
…drivers.TCPDriver[AugustaGH].TCPConnecti 30Aug2024 09:20:25 Error connecting to 172.168.1.201:4840. connection timed out: /172.168.1.201:4840
…drivers.TCPDriver[AugustaCP1].TCPConnect 30Aug2024 09:20:25 Error connecting to 172.168.1.200:4840. connection timed out: /172.168.1.200:4840
DatasourceAuditProfile 30Aug2024 09:19:58 Error verifying audit log table.
Gateway 30Aug2024 09:13:20 ERROR(200): Unable to parse message.
Gateway 30Aug2024 09:13:09 ERROR(200): Unable to parse message.
UascClientMessageHandler 30Aug2024 09:12:15 [remote=/172.168.1.201:4840] Exception caught: An existing connection was forcibly closed by the remote host
UascClientMessageHandler 30Aug2024 09:10:56 [remote=/172.168.1.201:4840] Exception caught: An existing connection was forcibly closed by the remote host
UascClientMessageHandler 30Aug2024 09:10:07 [remote=/172.168.1.201:4840] Exception caught: An existing connection was forcibly closed by the remote host
UascClientMessageHandler 30Aug2024 09:09:37 [remote=/172.168.1.202:4840] Exception caught: An existing connection was forcibly closed by the remote host
UascClientMessageHandler 30Aug2024 09:08:11 [remote=/172.168.1.200:4840] Exception caught: An existing connection was forcibly closed by the remote host
UascClientMessageHandler 30Aug2024 09:07:21 [remote=/172.168.1.202:4840] Exception caught: UaException: status=Bad_TcpMessageTypeInvalid, message=unknown message type: 262245
UascClientMessageHandler 30Aug2024 09:07:21 [remote=/172.168.1.202:4840] Exception caught: UaException: status=Bad_TcpMessageTypeInvalid, message=unknown message type: 262245
UascClientMessageHandler 30Aug2024 09:07:15 [remote=/172.168.1.202:4840] Exception caught: An existing connection was forcibly closed by the remote host
Gateway 30Aug2024 09:04:39 ERROR(200): Unable to parse message.
UascClientMessageHandler 30Aug2024 09:02:44 [remote=/172.168.1.200:4840] Exception caught: An existing connection was forcibly closed by the remote host
UascClientMessageHandler 30Aug2024 09:01:34

This may best handled by our PSG team. The error looks like the connection from Ignition was closed by the EPIC. Our team would need all the internal logs, including what firmware version you are running currently… You may submit a support ticket by calling or emailing:
Phone: 951-695-3080
Email: support@opto22.com

2 Likes