Clarification for index range handling of read/write|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
Clarification for index range handling of read/write
Avatar
Toshihisa Fujii
Member
Members
Forum Posts: 6
Member Since:
02/24/2014
sp_UserOfflineSmall Offline
1
08/31/2016 - 16:50
sp_Permalink sp_Print

Excuse me. I would like to clarify the specification of index range handling.

Current my UA server can support following handling for the array data.

- Read/Write the whole elements of array data type parameter.

- Read/Write only one element  of array data type parameter.

That is, currently no support to access index range (e.g. [5..9], [2..3, 8..10], etc.) of array data type parameter.

Shall the UA server support index range access to pass the certification test? Or is it optional functionality?

If no support of index range access is acceptable from the viewpoint of certification test, which return status code is recommended in case where UA client specify index range? In case of write, BadWriteNotSupported seems to be good. However I have no idea which is recommended in case of read.

Best regards.

Avatar
Guest
Guests
2
09/01/2016 - 06:21
sp_Permalink sp_Print

Hello,

The Standard UA Server requires the "Attribute Read" conformance unit which states "Supports the Read Service to read one or more Attributes of one or more Nodes. This includes support of the IndexRange parameter to read a single element or a range of elements when the Attribute value is an array."

The same profile also contains the "Attribute Write Index" conformance unit which is exclusively for writing via IndexRange, but that conformance unit is OPTIONAL.

So to summarize, reading of index-ranges is required whether it is for the whole range, partial range, or single element; but writing to an index-range is optional behavior.

Your server could return BadWriteNotSupported is consistent with what the CTT expects if a client writes to an index-range when the server does not support the feature.

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