Different AccessLevel in Type space in relation to Instance space|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
Different AccessLevel in Type space in relation to Instance space
Avatar
Martin Lang
Germany
Member
Members
Forum Posts: 72
Member Since:
06/25/2014
sp_UserOfflineSmall Offline
1
03/18/2020 - 08:02
sp_Permalink sp_Print sp_EditHistory

Assumption:

A companion spec define a VariableNode as following (OPC UA for IO-Link)

The Variable ProcessDataOutput shall be mapped to the cyclically data transferred to the device. It is vendor-specific, if the Variable is writeable.

The related NodeSet2-XML defines this VariableNode with attribute AccessLevel CurrentRead/CurrentWrite.

So below ObjectTypes the AccessLevel is defined for this VariableNode.

But whats about the Instance space if there will never a support to write the VariableNode.

Question:

Is it allowed to change the attribute AccessLevel to CurrentRead in the instance space?

Or must the each time CurrentRead|CurrentWrite and only the UserAccessLevel will be CurrentRead?

This question also relevant for the Method attributes Executeable and UserExecutable.

 

thx & br

Avatar
Randy Armstrong
Admin
Forum Posts: 1438
Member Since:
05/30/2017
sp_UserOfflineSmall Offline
2
03/19/2020 - 00:09
sp_Permalink sp_Print

In general, any permission related attributes have rules defined by the modeller. In this case, the modeller made it clear that write access is optional so you can change the AccessLevel to RO. 

In other cases, you would keep the same AccessLevel but you could do whatever you need with UserAccessLevel.

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