Reference EnumStrings or EngineeringUnits multiple times|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
Reference EnumStrings or EngineeringUnits multiple times
Avatar
Martin Lang
Germany
Member
Members
Forum Posts: 72
Member Since:
06/25/2014
sp_UserOfflineSmall Offline
1
06/18/2019 - 06:48
sp_Permalink sp_Print

Hello,

is it permitted to “reuse” property variables like EnumStrings or EngineeringUnits?

Example:

|-> Node A

        |-> EngineeringUnit A

|-> Node B

        |-> EngineeringUnit A

|-> Node C

        |-> EngineeringUnit A

In the example EngineeringUnit A only exist once and will be referenced multiple times.

This example assumes, that the EngineeingUnits are fixed and can not changed durign runtime.

Similar could be done with an EnumStrings property for instance:

|-> Port A / Baudrate (in instance information model)

         |-> EnumString (referenced from the type information model)

|-> Port n / Baudrate (in instance information model)

         |-> EnumString (referenced from the type information model)

In the end only one instance from EnumStrings exist, or must a second instance be created in the instance information model?

 

BR

Martin

Avatar
Randy Armstrong
Admin
Forum Posts: 1579
Member Since:
05/30/2017
sp_UserOfflineSmall Offline
2
06/18/2019 - 07:08
sp_Permalink sp_Print

Yes. It is expected that some servers will optimize representation of common properties/components by linking back to a single node.

Note that this will mean that multiple inverse references will exist from these common nodes.

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