I'm trying to connect a to a OPC UA server with CODESYS.
I have trided to use the Data Source Manager with no luck, to a spesific OPC UA Server.
Using the Data Source Manager to other OPC UA complient servers works fine.
All the OPC UA servers that i have tried to connect to works with UA Expert.
The only difference between the servers are that the one that I'm having problems with use namespace index 2 on all browse paths and the other servers use namespace index 4 on the last browsepath.
I have tried using the "OPC UA Client Example", and this works with all servers, no problem at all connecting to the server I am having problem with.
I have used the Device Reader and it says that my device does not support OPC UA Client. But this is weird sice it does work.
There is a new extension called "CODESYS OPC UA Client SL" but it is lacking documentation. What is this, and can it fix my issues?
Thanks in advance.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The namespaceindex only refers to these entries in the attached image (which can be different for each server). So if the servers were identical outside of the nameSpaceIndex, I do not think that would cause a problem. Are there any other differences? I know IdentifierType guid is not yet supported.
Regarding Device Reader, if it works in demo mode then it should be supported on your device. When I run it on my Control Win, I get a "No" in the "License Active/Count" column next to CODESYS OPC UA Client. CODESYS OPC UA Client SL is not a seperate extension, it is a license for activating the feature outside the demo time-limit. It is valid for datasources OPC UA Client and alse the OPC UA Client Example Project.
Hi,
I'm trying to connect a to a OPC UA server with CODESYS.
I have trided to use the Data Source Manager with no luck, to a spesific OPC UA Server.
Using the Data Source Manager to other OPC UA complient servers works fine.
All the OPC UA servers that i have tried to connect to works with UA Expert.
The only difference between the servers are that the one that I'm having problems with use namespace index 2 on all browse paths and the other servers use namespace index 4 on the last browsepath.
I have tried using the "OPC UA Client Example", and this works with all servers, no problem at all connecting to the server I am having problem with.
I have used the Device Reader and it says that my device does not support OPC UA Client. But this is weird sice it does work.
There is a new extension called "CODESYS OPC UA Client SL" but it is lacking documentation. What is this, and can it fix my issues?
Thanks in advance.
The namespaceindex only refers to these entries in the attached image (which can be different for each server). So if the servers were identical outside of the nameSpaceIndex, I do not think that would cause a problem. Are there any other differences? I know IdentifierType guid is not yet supported.
Regarding Device Reader, if it works in demo mode then it should be supported on your device. When I run it on my Control Win, I get a "No" in the "License Active/Count" column next to CODESYS OPC UA Client. CODESYS OPC UA Client SL is not a seperate extension, it is a license for activating the feature outside the demo time-limit. It is valid for datasources OPC UA Client and alse the OPC UA Client Example Project.