MaxNodesPerRequest limitation|OPC UA Standard|Forum|OPC Foundation

Hi,

We are implementing an  OPCUA stack  on a resource limited system. 

It's possible to limit the number of node id:s in the same ReadRequest using the OperationLimits node specified in Part 5.  To be able to read all the attributes from a node  we have a limitation of 20 node id:s per ReadRequest.

The problem is that our value attribute is very large relative to other attributes (up to 1500 bytes) and there is no way to limit the size of the response. If the client chooses to read 20 value attributes from different nodes we will not be able to handle the worst case. 

Each individual read operation in ReadRequest has a status code. Currently we are planning to use STATUSCODE_BADOUTOFMEMORY for all read operations we cannot handle within a ReadRequest.

Is that a good way to solve the problem?

Can we expect the clients to handle that not all operations were successful?

We have also tried to set the limitation to 1 but the client (UA Expert) cannot not handle this.

/ Mattias