MaxNodesPerRequest limitation|OPC UA Standard|Forum|OPC Foundation

Avatar
Search
Forum Scope


Match



Forum Options



Minimum search word length is 3 characters - maximum search word length is 84 characters
Lost password?
sp_Feed sp_PrintTopic sp_TopicIcon
MaxNodesPerRequest limitation
Avatar
Mattias Bornhager
Member
Members
Forum Posts: 3
Member Since:
11/13/2017
sp_UserOfflineSmall Offline
1
11/15/2017 - 04:18
sp_Permalink sp_Print

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

Forum Timezone: America/Phoenix
Most Users Ever Online: 510
Currently Online:
Guest(s) 16
Currently Browsing this Page:
1 Guest(s)
Top Posters:
Forum Stats:
Groups: 2
Forums: 10
Topics: 1341
Posts: 4545