FORUM CTRLX AUTOMATION
ctrlX World Partner Apps for ctrlX AUTOMATION
07-11-2024 02:09 PM
Hello ,
When trying to connect to a OPC-UA server with the ctrlC OPC UA Client the connection fails and several errors are shown.
When using the UA-Expert tool, the connection is OK and variables are available. Also other OPC Clients are able to connect to the OPC Server.
The clocks of the OPC Server and the ctrlX OPC Client are within 3 minutes from each other and we will try to synchronize them to be sure this is not the cause of the problem.
Anonymous authentication and no security is used:
During several connection attempts, the following errors /messages are shown:
The following app versions are installed:
Connection with UA Expert is OK:
What could we do to solve this problem?
07-12-2024 02:41 PM
Most properly is it a network and/or configuration problem (only).
Check the configuration in the Data Layer node “opcuaclient”.
The standard port for OPC UA communication is 4840. By using another ones make sure, that the port forwarding to the server is OK (as well for routers between, firewalls etc.).
Also, the server must accept/trust the client’s certificate. Check this, but often it is done automatically.
@everyone: Feel free to add your ideas and comments, please!
07-15-2024 08:54 AM
The problem is not in the connection or the network. As Mike said, it is working from other (non-Bosch) clients inside the same network. We know the communication parameters, and they are properly set in the opcuaclient configuration.
One of the error messages even shows that the connection is OK, because it tells that there is a problem with the CONNECTED server.
We need an explanation why the Datalayer errors like DL_INVALID_ADDRESS are shown. It looks to me that the problem occurs when the OPC client app is trying to browse through the connected server to add all variables to the datalayer. Maybe it has something to do with the identification of the variables on the server? This server uses numerical id's.
07-23-2024 05:15 PM
INFO The topic is in clarification internally; the result will be posted here again, when finished.