Timeout or "The secure channel has been closed" error while browsing static tags on a CODESYS OPC UA server

Applies To:

groov View running on:

GROOV-AR1, GROOV-AR1-BASE, GROOV-AR1-SNAP
GROOV-AT1, GROOV-AT1-SNAP
GROOV-SVR-WIN, GROOV-SVR-WIN-BASE, GROOV-SVR-WIN-SNAP
GRV-EPIC-PR1

Versions Affected:

GRV-EPIC-PR1: 3.1.0 to current
All other products: R4.3a to current

Symptoms:

While browsing static tags on a CODESYS OPC UA server, including the one in the GRV-EPIC-PR1, groov View reports a timeout or displays the message The secure channel has been closed. After that, any attempt to communicate with that CODESYS server will fail.

If you review the logs, you may see messages like the following:

19:45:32,827 WARN  [qtp1965237677-19] c.o.g.s.d.o.OpcUaStaticTagBrowser - Could not browse OPC UA node. 
com.prosysopc.ua.ServiceException: Bad_SecureChannelClosed (code=0x80860000, description="The secure channel has been closed.")
19:46:32,847 WARN  [PublishTask-com.opto22.groov.server.opcua.OpcUaClientEx@39afdd2] o.o.u.t.t.i.SecureChannelTcp - Connection failed: Bad_CommunicationError (code=0x80050000, description="2147811328, Read timed out")
19:46:32,847 WARN  [PublishTask-com.opto22.groov.server.opcua.OpcUaClientEx@39afdd2] o.o.u.t.t.i.SecureChannelTcp - Bad_CommunicationError: Retrying
19:48:34,113 WARN  [PublishTask-com.opto22.groov.server.opcua.OpcUaClientEx@39afdd2] o.o.u.t.t.i.SecureChannelTcp - Connection failed: Bad_CommunicationError (code=0x80050000, description="2147811328, Read timed out")
19:48:34,113 WARN  [PublishTask-com.opto22.groov.server.opcua.OpcUaClientEx@39afdd2] o.o.u.t.t.i.SecureChannelTcp - Bad_CommunicationError: Retrying
19:48:55,196 WARN  [qtp1965237677-19] c.o.g.s.d.o.OpcUaStaticTagBrowser - Could not connect to OPC UA server. 
19:50:35,307 WARN  [qtp1965237677-37] o.o.u.t.t.i.SecureChannelTcp - Connection failed: Bad_CommunicationError (code=0x80050000, description="2147811328, Read timed out")
19:50:35,307 WARN  [qtp1965237677-37] o.o.u.t.t.i.SecureChannelTcp - Bad_CommunicationError: Retrying
19:51:36,469 WARN  [qtp1965237677-37] c.o.g.s.d.o.OpcUaStaticTagBrowser - Could not connect to OPC UA server. Failed to create secure channel to server: : opc.tcp://codesys1:4840 [http://opcfoundation.org/UA/SecurityPolicy#None,None]

Note that these messages may also indicate that you configured the CODESYS OPC UA device with the wrong address. Double check that your configuration details are correct, and, if possible, try using another OPC UA client to verify the address.

To re-establish communication to the CODESYS OPC UA server, restart the GRV-EPIC-PR1.

Resolution:

Opto 22 has resolved this issue.

Questions?

Contact: Opto 22 Product Support.
Phone: 800-835-6786 or 951-695-3080
Email: support@opto22.com

DISCLAIMER

This Opto 22 Knowledge Base ('OptoKB') article is intended to provide general technical information on a particular subject or subjects and is not an exhaustive treatment of such subjects. Accordingly, the information in this OptoKB article is not intended to constitute application, design, software, or other professional engineering advice or services. Opto 22 may modify the OptoKB articles at any time. Before making any decision or taking any action which might affect your equipment, you should consult a qualified professional.

OPTO 22 DOES NOT WARRANT THE COMPLETENESS, TIMELINESS, OR ACCURACY OF THE DATA CONTAINED IN THIS OPTOKB ARTICLE AND MAY MAKE CHANGES THERETO AT ANY TIME AT ITS SOLE DISCRETION WITHOUT NOTICE. FURTHER, ALL INFORMATION CONVEYED HEREBY IS PROVIDED TO USERS 'AS IS.' IN NO EVENT SHALL OPTO 22 BE LIABLE FOR ANY DAMAGES OF ANY KIND INCLUDING DIRECT, INDIRECT INCIDENTAL, CONSEQUENTIAL, LOSS PROFIT, OR DAMAGE, EVEN IF OPTO 22 HAS BEEN ADVISED ON THE POSSIBILITY OF SUCH DAMAGES.

OPTO 22 DISCLAIMS ALL WARRANTIES WHETHER EXPRESSED OR IMPLIED WITH RESPECT TO THE INFORMATION (INCLUDING HARDWARE, SOFTWARE, AND/OR FIRMWARE) PROVIDED HEREBY, INCLUDING THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTIBILITY, AND NON-INFRINGEMENT. Note that certain jurisdictions do not sanction the exclusion of implied warranties: thus, this disclaimer may not apply to you.