Search
43 result(s) for View
-
OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts2.1.46 ViewView specific subset of the AddressSpace that is of interest to the Client
-
OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts5.3.4.3 AddressSpace ViewsAddressSpace Views A View is a subset of the AddressSpace . Views are used to restrict the Node s that the Server makes visible to the Client , thus restricting the size ... AddressSpace for the Service requests submitted by the Client . The default View is the entire AddressSpace . Servers may optionally define other Views . Views hide some of the Node
-
OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts6.6 View Service SetView Service Set Views are publicly defined, Server -created subsets of the AddressSpace . The entire AddressSpace is the default View , and therefore, the View Services are capable of operating ... versions of this specification may also define Services to create Client defined Views . The View Service Set allows Clients to discover Node s in a View by browsing. Browsing allows
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model5.4 View NodeClassView NodeClass Underlying systems are often large and Clients often have an interest in only a specific subset of the data. They do not need, or want, to be burdened ... have no interest. To address this problem, this standard defines the concept of a View . Each View defines a subset of the Nodes in the AddressSpace . The entire AddressSpace
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space ModelObjects , the Organizes ReferenceType . The SourceNode of such a Reference should always be a View or an Object of the ObjectType FolderType ; the TargetNode can be of any NodeClass . Organizes
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model7.17 HasEventSourcesource in a Server . The SourceNode of this ReferenceType shall be an Object or View that is a source of Event Subscriptions . A source of Event Subscriptions is an Object ... View that has its "SubscribeToEvents" bit set within the EventNotifier Attribute . The SourceNode may also be an ObjectType when referencing an InstanceDeclaration where an instance of the ObjectType
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model9.32.3 ViewsViews A ModelChangeEvent is always generated in the context of a View, including the default View where the whole AddressSpace is considered. Therefore the only Notifiers which report the ModelChangeEvents ... View Nodes and the Server Object representing the default View . Each action generating a ModelChangeEvent may lead to several Events since it may affect different Views . If, for example
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model9.33.3 ViewsViews SemanticChangeEvents are handled in the context of a View the same way as ModelChangeEvents . This is defined
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space ModelA.5 Viewsspecial class of Clients , for example maintenance Clients , engineering Clients , etc. The View only provides the information needed for the purpose of the Client and hides unnecessary information
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space ModelC.2.2 Simple notationDisplayName of the Method . The font shall not be set to italic. View Trapezium including text representing the string-part of the DisplayName of the View . The font shall
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Servicesmodify and delete Nodes in the AddressSpace . Figure 4 - NodeManagement Service Set The View Service Set , illustrated in Figure 5 , defines Services that allow Clients to browse through the AddressSpace ... allows Clients to get a subset of data from the AddressSpace or the View . Figure 5 - View Service Set The Attribute Service Set is illustrated in Figure 6 . It defines
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services5.8.5.1 DescriptionReferences deleted by an invocation of this Service are contained in a View , then the ViewVersion Property is updated if this Property is supported. Table 31 defines the parameters
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services5.9.1 OverviewOverview Clients use the browse Services of the View Service Set to navigate through the AddressSpace or through a View which is a subset of the AddressSpace . A View
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services5.9.2.1 Descriptionspecified Node. The browse can be further limited by the use of a View . This Browse Service also supports a primitive filtering capability. In some cases it may take longer
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services5.9.2.2 ParametersName Type Description Request requestHeader RequestHeader Common request parameters (see 7.32 for RequestHeader definition). View ViewDescription Description of the View to browse (see 7.44 for ViewDescription definition). An empty ViewDescription ... value causes all References of the nodesToBrowse to be returned. Use of any other View causes only the References of the nodesToBrowse that are defined for that View
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services7.7.3 FilterOperatorOperands Description InView 13 1 TRUE if the target Node is contained in the View defined by operand[0]. The following restrictions apply to the operands: [0]: Any operand that ... resolves to a NodeId that identifies a View Node. If operand[0] does not resolve to a NodeId that identifies a View Node, this operation shall always be False. OfType
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services7.24.1 OverviewDataTypeAttributes Defines the Attributes for the DataType NodeClass . ViewAttributes Defines the Attributes for the View NodeClass . GenericAttributes Defines an id and value list for passing in any number of Attribute
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services7.24.9 ViewAttributes parameterparameter. Table 158 - ViewAttributes Name Type Description ViewAttributes structure Defines the Attributes for the View NodeClass. specifiedAttributes UInt32 A bit mask that indicates which fields contain valid values. A field
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services7.44 ViewDescriptiondefined in Table 194 . Table 194 - ViewDescription Name Type Description ViewDescription structure Specifies a View. viewId NodeId NodeId of the View to Query . A null value indicates the entire AddressSpace ... this parameter shall be null. viewVersion UInt32 The version number for the View desired. When Nodes are added to or removed from a View , the value of a View
-
OPC-10000-4 – OPC Unified Architecture - Part 4: ServicesB.1.3 Example 2filter to select all SystemEvents (including derived types) that are contained in the Area1 View or the Area2 View would result in a logic tree as shown in Figure
-
OPC-10000-4 – OPC Unified Architecture - Part 4: ServicesB.2.2 Querying ViewsB.2.2 Querying Views A View is a subset of the AddressSpace available in the Server . See OPC 10000-5 for a description of the organization of Views in the AddressSpace ... existing View , a Query may be used to return a subset of data from the View . When an application issues a Query against a View , only data defined
-
OPC-10000-4 – OPC Unified Architecture - Part 4: ServicesB.2.3 QueryFirstName Type Description Request requestHeader RequestHeader Common request parameters (see 7.32 for RequestHeader definition). View ViewDescription Specifies a View and temporal context to a Server (see 7.44 for ViewDescription definition
-
OPC-10000-4 – OPC Unified Architecture - Part 4: ServicesB.3.2 Used type modelBrowseName , NodeId , and Value are shown. The Nodes that are included in a View (View1) are enclosed in the coloured box. Two Area nodes are included for grouping
-
OPC-10000-4 – OPC Unified Architecture - Part 4: ServicesB.3.11 Example 8illustration of a request in which the AddressSpace is restricted by a Server defined View . This request is the same as in the second example which illustrates receiving a list ... note that all of the parameters and the ContentFilter are the same, only the View description would be specified as "View1". Example 8: Get PersonType.LastName, AnimalType.Name where
-
OPC-10000-4 – OPC Unified Architecture - Part 4: ServicesB.3.12 Example 9illustration for a request in which the AddressSpace is restricted by a Server defined View . This request is similar to the second example except that some of the requested nodes ... path. It is important to note that the ContentFilter is the same, only the View description would be specified as "View1". Example 9: Get PersonType.LastName, AnimalType.Name where
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model6.4.31 BaseModelChangeEventTypeSourceNode Property for Events of this type shall be the Node of the View that gives the context of the changes. If the whole AddressSpace is the context, the SourceNode ... Events of this type shall be the String part of the BrowseName of the View ; for the whole AddressSpace it shall be "Server
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model6.4.33 SemanticChangeEventTypeSourceNode Property for Events of this type shall be the Node of the View that gives the context of the changes. If the whole AddressSpace is the context, the SourceNode ... Events of this type shall be the String part of the BrowseName of the View , for the whole AddressSpace it shall be "Server". The additional Property defined
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model8.2.4 ObjectsReferences are used to relate Objects to the " Objects " standard Object . A View Node can be used as entry point into a subset of the AddressSpace containing Objects ... Variables and thus the " Objects " Object can also reference View Nodes using Organizes References . The intent of the " Objects " Object is that all Objects and Variables
-
OPC-10000-6 – OPC Unified Architecture - Part 6: MappingsF.7 UAInstanceUAMethod Defines a Method Node as described in OPC 10000-3 . UAView Defines a View Node as described in OPC 10000-3 . Table F.7 - UAInstance Element Type Description
-
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access7.1 Generalcomplete set of services. The services needed for the purpose of DataAccess are: The View service set and Query service set to detect DataItems , and their Properties . The Attribute service
-
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access3.1.4 HistoricalNodeHistoricalNode Object , Variable , Property or View in the AddressSpace where a Client can access historical data or Events Note 1 to entry: A HistoricalNode is a term used in this ... document to represent any Object , Variable, Property or View in the AddressSpace for which a Client can read and/or update historical data or Events . The terms " HistoricalNodes's history
-
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access3.1.6 HistoricalEventNodeHistoricalEventNode Object or View in the AddressSpace for which a Client can access historical Events Note 1 to entry: " HistoricalEventNode's history" or "history of a HistoricalEventNode
-
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical AccessChanges in AddressSpace over time Clients use the browse Services of the View Service Set to navigate through the AddressSpace to discover the HistoricalNodes and their characteristics. These Services provide
-
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Accessreference type shall be a HistoricalEventNode. The Target node shall be any Object or View that has the EventNotifier Attribute set to TRUE. Table 9 - HasCurrentEvent ReferenceType Attributes Value BrowseName
-
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical AccessEvents generated by the Server . Each HistoricalEventNode is represented by an Object or View with a specific set of Attributes. The HistoricalEventFilter Property specifies the fields available in the history ... every Object or View in the AddressSpace can be a HistoricalEventNode . To qualify as HistoricalEventNode , a Node must contain historical Events . To see if historical Events are available, a Client
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model13.1 Overviewissue Method Calls and also resolve Node information. Resolving Node information may require using View Services ( Browse , TranslateBrowsePathsToNodeIds ) and Attribute Services ( Read ). The details related to an application's configuration
-
OPC-30001 – OPC UA Client Function Blocks for IEC 61131-37.23 UA_Browsehandle. E ViewDescription UAViewDescription Optional: Shall be an empty parameter if NOT browsing a View . B BrowseDescription UABrowseDescription Starting Node and other information for navigation. See UABrowseDescription Hint: This parameter
-
OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices4.2.1 Generalrepresent AddressSpace components. The classes are Object , Variable , Method , ObjectType, DataType, ReferenceType and View . Each NodeClass has a defined set of Attributes . This specification defines Nodes
-
OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model4.2.1 Generalrepresent AddressSpace components. The classes are Object , Variable , Method , ObjectType, DataType, ReferenceType and View . Each NodeClass has a defined set of Attributes . This specification makes use of three essential
-
OPC-30040 – OPC UA for AutomationML - Xxx: OPC UA Information Model for AutomationML4.2.1 Generalrepresent AddressSpace components. The classes are Object , Variable , Method , ObjectType, DataType, ReferenceType and View . Each NodeClass has a defined set of Attributes . This specification makes use of three essential
-
OPC-30110 – OPC UA for POWERLINK - POWERLINK: OPC Unified Architecture4.2.1 Generalrepresent AddressSpace components. The classes are Object , Variable , Method , ObjectType, DataType, ReferenceType and View . Each NodeClass has a defined set of Attributes . This specification makes use of three essential
-
OPC-30130 – OPC UA for Control & Communication System Profile(for Machine)4.2.1 Generalrepresent AddressSpace components. The classes are Object , Variable , Method , ObjectType, DataType, ReferenceType and View . Each NodeClass has a defined set of Attributes . This specification defines Nodes
-
OPC-40502 – OPC UA for Computerized Numerical Control (CNC) Systems - for CNC Systems: OPC UA Information Model4.2.1 Generalrepresent AddressSpace components. The classes are Object , Variable , Method , ObjectType, VariableType, DataType, ReferenceType and View . Each NodeClass has a defined set of Attributes . This specification makes use of three essential