I am using OPC UA Server app version 1.12.5 on an X3. My UA client can reach the server but then immediately encounters a ton of errors about nodes missing type definitions. It very quickly hits a stack limit and stops. I recall having the same, or at least very similar, issue with this client trying to connect to an XM22 server on version 14. Once I upgraded to v15, the issue was resolved. I assume this to be an issue with how the server is implemented on the CORE. Is there a solution or an updated UA Server app coming soon?
I have included a log file of the errors.
Best reply by CodeShepherd
We needed some more time to find that the problem for crashing is on client side not on servers. The missing description error did not lead to it but will be fixed in our next release of the server.
The Reason for the error “BadEncodingLimitsExceeded” (“FT-Optix.png”) inside the FT Optix OPC UA client is the variable “ns=2;s=datalayer/retain/chunks”. The client tries to read the value and fails, because of the size of the returned data.
We also teted other clients like e.g. the Prosys OPC UA client can read the value and here you see it’s an array with 122880 elements:
read value in Prosys OPC UA client
The UA-Expert can read, but cannot show the value, because the default setting for the array size is 65536:
read value in UA_Expert OPC UA client
After increasing the max array size to 123000 the UA-Expert is able to show the data too:
read value in UA_Expert OPC UA client 2
And this fits to the OPC UA specification:
OPC UA specification BadEncodingLimitsExceeded
Â
The client must handle such “BadEncodingLimitsExceeded” errors. Please check if you can increase the max array size inside the settings of the FT-Optix UA Client.
