Search

Scope: Core (OPC-10000-*) All specs

22 result(s) for AddressSpace.

OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.44 ViewDescription

viewId NodeId NodeId of the View to Query . A null value indicates the entire AddressSpace. timestamp UtcTime The time date desired. The corresponding version is the one with the closest
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

F.1 Overview

target of any reference that would make them visible in an AddressSpace. The tables defining the DataTypes in the specification have field names starting with a lowercase letter. The first
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

F.7 UAInstance

deleted, the child is deleted as well). This information does not appear in the AddressSpace and is intended for use by design tools. This field shall be specified ... placeholder for use by design tools and does not appear in the AddressSpace. For example, well-known Properties or Objects. Only UAObject and UAVariable Nodes may have DesignToolOnly is TRUE
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

F.16 UANodeSetChanges

root of a document that contains a set of changes to an AddressSpace . It is expected that a single file will contain either a UANodeSet or a UANodeSetChanges element ... structure defined in F.22 is produced when a UANodeSetChanges document is applied to an AddressSpace . The elements of the type are defined in Table F.15 . Table F.15 - UANodeSetChanges Element Type
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.1 General

Condition Types . Instances of Alarm and Condition Types may be optionally exposed in the AddressSpace in order to allow direct access to the state of an Alarm or Condition . Instances ... exposed in the AddressSpace still have a ConditionId ( NodeId ). This NodeId can be the target of references in the AddressSpace even though the target node does not exist
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.5.4 Disable Method

Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, all Servers shall allow Clients to call the Disable Method by specifying ConditionId as the ObjectId ... ConditionType Node . Since Condition instances are not required to be defined in the AddressSpace , the MethodId that is passed in the Call Service shall be the NodeId of the Disable
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.5.5 Enable Method

Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, all Servers shall allow Clients to call the Enable Method by specifying ConditionId as the ObjectId ... disabled Condition. Since Condition instances are not required to be defined in the AddressSpace , the MethodId that is passed in the Call Service shall be the NodeId of the Enable
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.5.6 AddComment Method

Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, all Servers shall also allow Clients to call the AddComment Method by specifying ConditionId ... Condition values of this branch will be sent. Table 17 specifies the AddressSpace representation for the AddComment Method . Table 17 - AddComment Method AddressSpace definition Attribute Value BrowseName AddComment References NodeClass
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.7.3 Acknowledge Method

Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, Servers shall allow Clients to call the Acknowledge Method by specifying ConditionId as the ObjectId ... Condition values of this branch will be reported. Table 36 specifies the AddressSpace representation for the Acknowledge Method . Table 36 - Acknowledge Method AddressSpace definition Attribute Value BrowseName Acknowledge References NodeClass
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.7.4 Confirm Method

Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, Servers shall allow Clients to call the Confirm Method by specifying ConditionId as the ObjectId ... Server specific and may even be event or condition specific. Table 39 specifies the AddressSpace representation for the Confirm Method . Table 39 - Confirm Method AddressSpace definition Attribute Value BrowseName Confirm
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.5 Reset Method

Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, Servers shall allow Clients to call the Reset Method by specifying ConditionId as the ObjectId ... normal and have been acknowledged/confirmed prior to being reset. Table 45 specifies the AddressSpace representation for the Reset Method . Table 45 - Reset Method AddressSpace definition Attribute Value BrowseName Reset References
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.7 Silence Method

Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, Servers shall allow Clients to call the Silence Method by specifying ConditionId as the ObjectId ... currently in an audible state, the command is ignored. Table 50 specifies the AddressSpace representation for the Silence Method . Table 50 - Silence Method AddressSpace definition Attribute Value BrowseName Silence References
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.8 Suppress Method

Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, Servers shall allow Clients to call the Suppress Method by specifying ConditionId as the ObjectId ... Alarm instance, even if it is not currently active. Table 52 specifies the AddressSpace representation for the Suppress Method . Table 52 - Suppress Method AddressSpace definition Attribute Value BrowseName Suppress References
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.10 Unsuppress Method

Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, Servers shall allow Clients to call the Unsuppress Method by specifying ConditionId as the ObjectId ... Alarm instance, even if it is not currently active. Table 57 specifies the AddressSpace representation for the Suppress Method . Table 57 - Unsuppress Method AddressSpace definition Attribute Value BrowseName Unsuppress References
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.12 RemoveFromService Method

Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, Servers shall allow Clients to call the RemoveFromService Method by specifying ConditionId as the ObjectId ... even if it is not currently in the Active State . Table 62 specifies the AddressSpace representation for the RemoveFromService Method . Table 62 - RemoveFromService Method AddressSpace definition Attribute Value BrowseName RemoveFromService
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.14 PlaceInService Method

Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, Servers shall allow Clients to call the PlaceInService Method by specifying ConditionId as the ObjectId ... even if it is not currently in the Active State . Table 67 specifies the AddressSpace representation for the PlaceInService Method . Table 67 - PlaceInService Method AddressSpace definition Attribute Value BrowseName PlaceInService
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.17.2 Unshelve Method

Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, all Servers shall also allow Clients to call the Unshelve Method by specifying ConditionId ... Table 137 for the description of this result code. Table 77 specifies the AddressSpace representation for the Unshelve Method . Table 77 - Unshelve Method AddressSpace definition Attribute Value BrowseName Unshelve References
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.17.4 TimedShelve Method

Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, all Servers shall also allow Clients to call the TimedShelve Method by specifying ConditionId ... duration. This limit may be exposed as the MaxTimeShelved Property . Table 83 specifies the AddressSpace representation for the TimedShelve Method . Table 83 - TimedShelve Method AddressSpace definition Attribute Value BrowseName TimedShelve
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.17.6 OneShotShelve Method

Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, all Servers shall also allow Clients to call the OneShotShelve Method by specifying ConditionId ... this result code. The Alarm is already in OneShotShelved state. Table 88 specifies the AddressSpace representation for the OneShotShelve Method . Table 88 - OneShotShelve Method AddressSpace definition Attribute Value BrowseName OneShotShelve
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

4.1 General

Included is the specification of the representation of historical data and Events in the AddressSpace
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

5.6.2 HistoricalDataNodes Address Space Model

HistoricalDataNodes Address Space Model HistoricalDataNodes are always a part of other Nodes in the AddressSpace. They are never defined by themselves. A simple example of a container for HistoricalDataNodes would ... Folder Object". Figure 3 illustrates the basic AddressSpace Model of DataVariables that includes History. Figure 3 - Historical Variable with Historical Data Configuration and Annotations Each HistoricalDataNode with history shall
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.3 Definition of state machine

always be caused by some server-internal logic that is not exposed in the AddressSpace . Each Transition can have one or more Effects . An Effect occurs if the Transition ... Transition . A Transition is not required to expose any Effects in the AddressSpace. Although this specification only specifies simple concepts for state machines, the provided infrastructure is extensible. If needed