Showing results for 
Search instead for 
Did you mean: 

OPC UA Server Node Attributes

OPC UA Server Node Attributes

Established Member

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.


Community Moderator
Community Moderator

A far as i know there is quite no difference between the OPC UA servers in IndraWorks version 14 and 15.

The actual ctrlX CORE OPC UA server is 1.18 that can be found like other early adopter version in the corresponding area of the collaboration room. See e.g. the FAQ for ctrlX WORKS how to get access.

The latest version of the OPC UA Server app that is available to the me in the collaboration room is 1.12.5. As I have seen with my N.A. contact, 1.18 is visible to you as a Bosch employee, but not to everyone else (or at least just not to me). I would be happy to try 1.18 because as I said, switching from IW 14 to 15 had solved my previous problems with this exact same UA client. The differences were evidently stark enough and I would hope that the latest ctrlX UA server would match closely the IW 15 server. 

All early adopter version can also be visible for not Bosch employees. As mentioned above you need to request access once. See post above.

I have received the appropriate access, downloaded and installed V1.18 of the OPC UA Server app and the problem remains the same. The client cannot import nodes because of missing or incorrect type definitions. There is still something wrong with the ctrlX UA server.

Could you please send me a private message with your contact data, so we can have a direct look to this topic?

After a short session we could see the error. We tried to reproduce with your client but in our cases after some time the connection to a IW14 and also IW15 OPC UA server is working fine.

But your topic should be fixed in the next release version 1.20 coming up end of March.

It currently does not work with my ctrlX UA Server, which means I cannot continue with development. The machine is shipping mid-March, which means it needs to be functional by mid-February. I need a solution in the next couple of weeks, not by the end of March.

We are actually checking your topic to get an earlier solution as a patch for 1.18. We will inform you end of the week.


Which week? I had assumed Week 5.

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 clientread 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 clientread 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 2read value in UA_Expert OPC UA client 2

And this fits to the OPC UA specification:

OPC UA specification BadEncodingLimitsExceededOPC 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.