Hello,

we have a CodeSys RTE v3.5.8 with activated OPC-UA-Server.
Connecting via UAExpert works fine so far and I can browse nodes and values.

When trying to use the Prosys OPC-UA-Java-SDK to read some SPS value, I get the following error:

[2016-05-17 11:58:00,008+0000] [WARN] [vert.x-worker-thread-0] [AddressSpace] – Cannot set the type corresponding to the typeDefinition (ns=3;i=62) of node 4:AVTemp (ns=4;s=|var|CODESYS Control RTE .Application.HMI_Logger.AVTemp) com.prosysopc.ua.client.AddressSpaceException: Cannot determine NodeClass for NodeId: ns=3;i=62 because the value is not good: DataValue(value=(null), statusCode=Bad_NodeIdUnknown (0x80340000) “The node id refers to a node that does not exist in the server address space.”, sourceTimestamp=null, sourcePicoseconds=0, serverTimestamp=05/17/16 11:57:59.9700000 GMT, serverPicoseconds=0)
at com.prosysopc.ua.client.AddressSpace.getNode(Unknown Source)
at com.prosysopc.ua.client.AddressSpace.getType(Unknown Source)
at com.prosysopc.ua.client.AddressSpace.getNode(Unknown Source)

As it turns out, Codesys is publishing nodes with non-existant node type refences (Reference: HasTypeDefinition points to “ns=3;i=62” which does not exist on the server).
It seems UAExpert has no immediate problem with this, as long as one does not try to follow the refernece. In contrast, The SDK seems to allways follow all references, which results in an error/abort state.

So my question would be how I can proceed on this issue: I am in contact with codesys to see if it is a bug on their side. I would also like to know if there is a possibility to ship arround this issue in the SDK as a workaround. (Like an “only check attributes and not references”-mode)

Thank You