Search
18 result(s) for Types
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model7.26 3DOrientationTypeused. The OrientationType , defined in 7.25 , is intended to be subtyped to create Types which represent any multi-dimensional orientations including 3D spaces. The VariableType is formally defined in Table
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model8.2.5 TypesTypes This standard Object Node is the browse entry point for type Nodes . Figure 1 illustrates the structure beneath this Node . Only Organizes References are used to relate Objects ... Types " standard Object . The " Types " Object shall not reference any other NodeClasses . It is formally defined in Table 103 . Table 103 - Types definition Attribute Value BrowseName Types
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions5.1 GeneralCondition model extends the OPC UA base Event model by defining various Event Types based on the BaseEventType . All of the Event Types defined in this document can be further ... extended from domain to Server specific Alarm and Condition Types . Instances of Alarm and Condition Types may be optionally exposed in the AddressSpace in order to allow direct access
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions5.6.1 Generalspecific response options in the ResponseOptionSet and by adding additional functionality to derived Condition Types
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions5.8.24.1 DiscreteAlarmTypeDiscreteAlarmType The DiscreteAlarmType is used to classify Types into Alarm Conditions where the input for the Alarm may take on only a certain number of possible values (e.g. True/False, running/stopped/terminating ... DiscreteAlarmType with sub types defined in this document is illustrated in Figure 22 . It is formally defined in Table 105 . Figure 22 - DiscreteAlarmType Hierarchy Table 105 - DiscreteAlarmType definition Attribute Value
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions5.9.1 Overviewcommon classes used across many industries. Figure 23 informally describes the hierarchy of ConditionClass Types defined in this document. Figure 23 - ConditionClass type hierarchy ConditionClasses are not representations of Object
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions5.9.2 BaseConditionClassTypemore concrete class. Servers should use a more specific ConditionClass , if possible. All ConditionClass Types derive from BaseConditionClassType . It is formally defined in Table 113 . Table 113 - BaseConditionClassType definition Attribute
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditionsapply: All HasCondition References used in a Type shall exist in instances of these Types as well. If the TargetNode in the Type definition is a ConditionType , the same TargetNode
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditionslinked together and with the included ConditionSources using the HasNotifier and the HasEventSource Reference Types . The Server Object shall be the root of this hierarchy. Figure 26 shows such ... used as Event notifier. See 10000-3 for the formal definition of these Reference Types . Figure 26 - Typical HasNotifier Hierarchy
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines4.4.1 OverviewOverview The types defined in this specification are illustrated in Figure 3 . The MyFiniteStateMachineType is a minimal example which illustrates how these Types can be used to describe a StateMachine
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringA.9 Instance mappinginstance tree as specified in the NodeSet files, minus the standard OPC UA Types folder since the equivalent type objects are contained in the AutomationML Libraries. Engineering tools may organize
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices9.2.1 General patternconfigurable Object shall contain a folder called SupportedTypes that references the list of Types available for configuring components using Organizes References . Sub-folders can be used for further structuring ... instance of each Type can be configured. In this case the list of supported Types will shrink with each configured component
-
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial LocationCartesianFrameAngleOrientationType uses it and describes Orientation with Quaternion. Or for representations without orientation only Types which provide a Position (e.g. the CylindricalCoordinatesFrameType or the PolarCoordinatesFrameType ). Figure 25 - Examples of subtypes
-
OPC-30050 – OPC UA for PackML - Common Object Model: PackML4.3.4.1 ConceptsNodeIds . This eliminates the need for manual reconfiguration of systems if a Client uses Types that multiple devices implement. OPC UA also supports the concept of sub typing. This allows ... Figure 7 - The OPC UA Information Model Notation A complete description of the different types of Nodes and References can be found in OPC 10000-3 and the base
-
OPC-30142 – OPC UA for PROFINET Remote IOCondition . In contrast to EventTypes derived from 0:BaseEventType , Alarm and Condition Types offer an Alarm state machine model enabling the implementation of an Alarm timeline
-
OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions6.1 NodeIdsNodeIds The NodeIds of the Types defined in this specification are mandatory and fixed in the provided XML-file. This applies only to the Types themselves
-
OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions19.14 MouldCycleParametersTypeMouldCycleParameters_1 Example1MouldCycle ParametersType M 0:HasComponent Object MouldCycleParameters_2 Example2MouldCycle ParametersType M The Types Example1MouldCycleParametersType and Example2MouldCycleParametersType used in the example are subtypes of the MouldCycleParametersType which is formally
-
OPC-40084-1 – OPC UA interfaces for plastics and rubber machinery - Extrusion - Part 1: General Type Definitionswhole). This ObjectType is abstract, the different components of an extrusion line use derived Types with the necessary specific extensions. Figure 3 - ExtrusionDeviceType Overview Table 1 - ExtrusionDeviceType Definition Attribute Value