Search
53 result(s) for VariableTypes
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model4.1 OverviewAddressSpace concepts. Clause 6 defines details on the type model for ObjectTypes and VariableTypes . Standard ReferenceTypes , DataTypes and EventTypes are defined in Clauses 7 to 8.61 . The informative Annex
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model4.6.3 Subtypingtype definitions. The subtyping rules are defined in Clause 6 . Subtyping of ObjectTypes and VariableTypes allows: Clients that only know the supertype to handle an instance of the subtype
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model5.6.2 Variable NodeClassused to represent values which may be simple or complex. Variables are defined by VariableTypes , as specified in 5.6.5 . Variables are always defined as Properties or DataVariables of other Nodes
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model5.6.4 DataVariableObject . However, complex DataVariables may expose other DataVariables , and ObjectTypes and complex VariableTypes may also contain DataVariables . Therefore each DataVariable shall be the TargetNode of at least one HasComponent Reference
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model5.6.5 VariableType NodeClassVariableType NodeClass VariableTypes are used to provide type definitions for Variables . VariableTypes are defined using the VariableType NodeClass , as specified in Table 14 . Table 14 - VariableType NodeClass Name Use Data ... ModellingRules defined in 6.4.4 . HasComponent 0..* HasComponent References are used for complex VariableTypes to identify their containing DataVariables . Complex VariableTypes can only be used for DataVariables . The referenced Nodes
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model5.8.1 DataType Modelused to describe the structure of the Value Attribute of Variables and their VariableTypes . Therefore each Variable and VariableType is pointing with its DataType Attribute to a Node ... DataType NodeClass as shown in Figure 17 . Figure 17 - Variables, VariableTypes and their DataTypes In many cases, the NodeId of the DataType Node - the DataTypeId - will be well-known
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Modelhave any encodings and cannot be exchanged on the wire. Variables and VariableTypes use abstract DataTypes to indicate that their Value may be any one of the subtypes
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model5.8.3 DataType NodeClassabstract or not. Abstract DataTypes can be used in the AddressSpace , i.e. Variables and VariableTypes can point with their DataType Attribute to an abstract DataType . However, concrete values can never
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model5.8.6.1 OverviewSubtypeRestriction shall only be used on Variables used as instances, never on InstanceDeclarations or VariableTypes . For Method Arguments , it can be used in combination with the HasArgumentDescription
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model6.1 OverviewOverview In the remainder of Clause 6 the type model of ObjectTypes and VariableTypes is defined regarding subtyping and instantiation
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model6.3.1 Overviewremainder of 6.3 specify subtyping rules for single inheritance on ObjectTypes and VariableTypes
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model6.3.2 AttributesBrowseName and DisplayName values should be overridden. Special rules apply for some Attributes of VariableTypes as defined in 6.2.8 . Optional Attributes , not provided by the parent type, may be added
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model6.4.4.4.3 ExposesItsArrayExposesItsArray The ExposesItsArray ModellingRule exposes a special semantic on VariableTypes having a single- or multidimensional array as the data type. It indicates that each value of the array will also
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Modelused There is no behaviour specified regarding subtypes and instances when changing ObjectTypes and VariableTypes . It is Server -dependent, if those changes are reflected on the subtypes and instances
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space ModelDataVariables , and Methods . This ReferenceType is also used to relate complex Variable s or VariableTypes with their DataVariables . Like all other ReferenceTypes , this ReferenceType does not specify anything about
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model7.15 GeneratesEventthis ReferenceType is to identify the types of Events instances of ObjectTypes or VariableTypes may generate and Methods may generate on each Method call. The SourceNode of References of this
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space ModelA.3 ObjectTypesonly having one value (e.g. a simple heat sensor) can also be modelled as VariableTypes . However, extensibility mechanisms should be considered (e.g. a complex heat sensor subtype could have several
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space ModelA.4.1 GeneralA.4.1 General VariableTypes are only used for DataVariables and should be used when there are several Variables having the same semantic (e.g. set point). It is not necessary to define
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space ModelB.1 Backgroundmarked as <<TypeExtension>>. In addition, the domain model contains ObjectTypes , VariableTypes etc. represented as UML objects (see Figure B.1 ). The OPC Foundation specifies not only
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model5.4 VariableTypesVariableTypes For all VariableTypes specified in NamespaceIndex 0, the Attributes named in Table 6 shall be set as specified in Table 6 . Table 6 - Common VariableType Attributes Attributes Value Value
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model7.1 Generalextended with additional components this standard allows the extension of the standard VariableTypes defined in this document with additional components. This allows the expression of additional information in the type ... Variable anyway. However, it is not allowed to restrict the components of the standard VariableTypes defined in this International Standard. An example of extending VariableTypes would be putting the standard
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model7.2 BaseVariableTypeBaseVariableType The BaseVariableType is the abstract base type for all other VariableTypes . However, only the PropertyType and the BaseDataVariableType directly inherit from this type. There are no References specified
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Modelhaving no more concrete type definition available. This VariableType is the base VariableType for VariableTypes of DataVariables , and all other VariableTypes of DataVariables shall either directly or indirectly inherit from
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model7.28 3DFrameTypereflects the semantic of its DataType , defined in 12.30 . It refines the DataTypes and VariableTypes of the CartesianCoordinates and Orientation to the corresponding 3D types. The VariableType is formally defined
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model8.2.7 VariableTypesVariableTypes This standard Object is the browse entry point for VariableType Nodes . Figure 5 illustrates the structure beneath this Node . Only Organizes References are used to relate Objects and VariableTypes ... VariableTypes " standard Object . The " VariableTypes " Object shall not reference any other NodeClasses . Figure 5 - VariableTypes organization The intent of the " VariableTypes " Object is that
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information ModelThis verb may be used only for affected Nodes that are Variables or VariableTypes . It indicates that the DataType Attribute has changed. Reserved 5:7 Reserved for future use. Shall
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information ModelA.1 Overviewfollowing subclauses describe the design decisions made while modelling the Server Object . General DataTypes , VariableTypes and ObjectTypes such as the EventTypes described in this standard are not taken into account
-
OPC-10000-6 – OPC Unified Architecture - Part 6: MappingsF.15 Examplevalue in the document except for NodeIds that appear in Values of Variables or VariableTypes . <Aliases> <Alias Alias="HasComponent">i=47</Alias
-
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access1 Scopedefines the information model associated with Data Access (DA). It particularly includes additional VariableTypes and complementary descriptions of the NodeClasses and Attributes needed for Data Access, additional Properties , and other
-
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access3.1.2 AnalogItemvalues provided by temperature sensors or pressure sensors. OPC UA defines specific VariableTypes to identify an AnalogItem . Properties describe the possible ranges of AnalogItems
-
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access3.1.3 DiscreteItemnumber of possible values (e.g., OPENING, OPEN, CLOSING, CLOSED) Note 1 to entry: Specific VariableTypes are used to identify DiscreteItems with two states or with multiple states. Properties specify
-
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access3.1.4 ArrayItemNote 1 to entry: Typical examples are the data provided by analyser devices. Specific VariableTypes are used to identify ArrayItem variants
-
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access5.1 GeneralGeneral The DataAccess model extends the variable model by defining VariableTypes . The DataItemType is the base type. ArrayItemType , Base AnalogType and DiscreteItemType are specializations. See Figure 2 . Each of these ... VariableTypes can be further extended to form domain or server specific DataItems . Figure 2 - DataItem VariableType hierarchy
-
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access5.3.2.1 GeneralGeneral The VariableTypes in subclauses 5.3.2.2 to 5.3.2.5 define the characteristics of AnalogItems . The types have identical semantics and Properties but with diverging ModellingRules for individual Properties . The Properties ... only described once - in 5.3.2.2 . The descriptions apply to the Properties for the other VariableTypes as well
-
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Accessthis case the AnalogItemType ). Additional characteristics of DataItem s are defined using Properties . The VariableTypes in 5.2 specify which properties can exist. These Properties have been found to be useful
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & ConditionsHasCondition in a VariableType is a special use case since Variables (and VariableTypes ) are not allowed to be the source of a HasComponent Reference to an Object. Figure 29 provides
-
OPC-10000-10 – OPC Unified Architecture - Part 10: Programs5.2.7 FinalResultDataFinalResultData The FinalResultData ObjectType specifies the VariableTypes that are preserved when the Program has completed its Function . The ObjectType includes a HasComponent for a VariableType of each Variable that comprises
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines4.1 GeneralGeneral This document describes the basic infrastructure to model state machines. It defines ObjectTypes , VariableTypes and ReferenceTypes and explains how they should be used. This document is an integral part
-
OPC-10000-19 – OPC Unified Architecture - Part 19: Dictionary Reference4.1 Generalreference external dictionaries like IEC Common Data Dictionary or ECLASS. It defines ObjectTypes , VariableTypes and a ReferenceType and explains how they should be used. The ObjectTypes are used to represent
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringVariableType mapping All the rules in A.5 for ObjectTypes also apply to VariableTypes with these notable differences: The base AML SUC for OPC UA VariableTypes is BaseVariableType ; VariableTypes have ... this is that the Value of an instance can be any valid DataType . Typically, VariableTypes that derive from BaseVariable type will alter the DataType of Value to be more restrictive
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringopcfoundation.org/UA/" defines the SystemUnitClasses that correspond to their equivalent OPC UA ObjectTypes and VariableTypes
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringopcfoundation.org/UA/DI/" defines the SystemUnitClasses that correspond to their equivalent OPC DI ObjectTypes and VariableTypes
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringdefine the SystemUnitClasses that correspond to their equivalent OPC UA FX ObjectTypes and VariableTypes
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering/UA/Safety/" defines the SystemUnitClasses that correspond to their equivalent OPC UA Safety ObjectTypes and VariableTypes
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices3.3.3.4 VariableTypesVariableTypes For all VariableTypes specified in this document, the Attributes named in Table 10 shall be set as specified in the table. The definitions for the Attributes can be found
-
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics3.3.3.4 VariableTypesVariableTypes For all VariableTypes specified in this document, the Attributes named in Table 10 shall be set as specified in the table. The definitions for the Attributes can be found
-
OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping3.3.1.1 Node definitionsexist if the Node is the target of a HasSubtype Reference . For Variables and VariableTypes , the value of the DataType Attribute is a dependency. For DataType Nodes , any DataTypes referenced
-
OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping3.3.3.4 VariableTypesVariableTypes For all VariableTypes specified in this document, the Attributes named in Table 10 shall be set as specified in the table. The definitions for the Attributes can be found
-
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation3.3.3.4 VariableTypesVariableTypes For all VariableTypes specified in this document, the Attributes named in Table 10 shall be set as specified in the table. The definitions for the Attributes can be found
-
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location3.4.3.4 VariableTypesVariableTypes For all VariableTypes specified in this document, the Attributes named in Table 10 shall be set as specified in the table. The definitions for the Attributes can be found
-
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning3.4.1.1 Node definitionsexist if the Node is the target of a HasSubtype Reference . For Variables and VariableTypes , the value of the DataType Attribute is a dependency. For DataType Nodes , any DataTypes referenced
-
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning3.4.3.4 VariableTypesVariableTypes For all VariableTypes specified in this document, the Attributes named in Table 10 shall be set as specified in the table. The definitions for the Attributes can be found
-
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning4.2.3.3 Companion Specificationsspecification for an industry specific vertical market describes an Information Model by defining ObjectTypes , VariableTypes , DataTypes and ReferenceTypes that represent the concepts used in the vertical market, and potentially also