Search

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

38 result(s) for EngineeringUnits

OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access

3.1.5 EngineeringUnits

EngineeringUnits units of measurement for AnalogItems that represent continuously-variable physical quantities (e.g., length, mass, time, temperature) Note 1 to entry: This standard defines Properties to inform about the unit
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.6.2 Variable NodeClass

ByteString but an array of the DataType Byte . In that case the MaxArrayLength applies. EngineeringUnits O EU Information Only used for DataVariables having a Number DataType (or a subtype ... that may change and define semantic aspects of the parent Node . For example, the EngineeringUnits Property describes the semantic of a DataVariable , whereas the Icon Property does not. In this
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.6.4 DataVariable

Property MaxArrayLength indicates the maximum allowed array length of the value. The Property EngineeringUnits indicates the engineering units of the value. There are no additional Properties defined for DataVariables
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.8.5.1 Overview

DataType and add meta data to fields of the Structured DataType , like providing the EngineeringUnits or EURange . In order to restrict the usage for each field of a Structured DataType
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.8.5.2 DataTypeRefinement Objects

DataType as Number , the DataTypeRefinement restricts this to an Int32 . As meta data, the EngineeringUnits is defined as Kelvin, therefore the AnalogUnitType is used as VariableType . The optional field2
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

7.21 VectorType

vector. The DataType EUInformation is defined in OPC 10000-8 . Note that the Property EngineeringUnits is intentionally not used, as it would have to define the engineering unit
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

7.23 CartesianCoordinatesType

coordinates. The DataType EUInformation is defined in OPC 10000-8 . Note that the Property EngineeringUnits is intentionally not used, as it would have to define the engineering unit
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

7.25 OrientationType

orientation. The DataType EUInformation is defined in OPC 10000-8 . Note that the Property EngineeringUnits is intentionally not used, as it would have to define the engineering unit
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access

5.3.2.2 BaseAnalogType

HasProperty Variable EURange Range PropertyType Optional HasProperty Variable EUNumberRange NumberRange PropertyType Optional HasProperty Variable EngineeringUnits EUInformation PropertyType Optional Conformance Units Data Access BaseAnalogType The following paragraphs describe the Properties ... also EURange shall be provided and populated with the equivalent value for legacy reasons. EngineeringUnits specifies the units for the DataItem 's value (e.g., DEGC, hertz, seconds). The EUInformation type
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access

5.3.2.4 AnalogUnitType

AnalogUnitType This VariableType requires the EngineeringUnits Property . The AnalogUnitType derives from the BaseAnalogType . It is formally defined in Table 4 . Table 4 - AnalogUnitType definition Attribute Value BrowseName AnalogUnitType IsAbstract False ... BaseAnalogType defined in 5.3.2.2 ; i.e. the Properties of that type are inherited. HasProperty Variable EngineeringUnits EUInformation PropertyType Mandatory Conformance Units Data Access AnalogUnitType
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access

5.3.2.5 AnalogUnitRangeType

AnalogUnitRangeType The AnalogUnitRangeType derives from the AnalogItemType and additionally requires the EngineeringUnits Property . It is formally defined in Table 5 . Table 5 - AnalogUnitRangeType definition Attribute Value BrowseName AnalogUnitRangeType IsAbstract False ... Properties of that type are inherited. HasSubtype VariableType AnalogNumberUnitRangeType Defined in 5.3.2.7 HasProperty Variable EngineeringUnits EUInformation PropertyType Mandatory Conformance Units Data Access AnalogUnitRangeType
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access

5.3.4.1 General

HasProperty Variable InstrumentRange Range PropertyType Optional HasProperty Variable EURange Range PropertyType Mandatory HasProperty Variable EngineeringUnits EUInformation PropertyType Mandatory HasProperty Variable Title LocalizedText PropertyType Mandatory HasProperty Variable AxisScaleType AxisScaleEnumeration PropertyType Mandatory ... operation. It is intended for such use as automatically scaling a bar graph display. EngineeringUnits holds the information about the engineering units of the Value of the ArrayItem . For additional
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access

5.3.4.2 YArrayItemType

YArrayItemType The Value of the YArrayItem contains the numerical values for the Y-Axis. Engineering Units and Range for the Value are defined by corresponding Properties inherited from the ArrayItemType ... Int64, Float, Double, ComplexNumberType and DoubleComplexNumberType . The XAxisDefinition Property holds the information about the Engineering Units and Range for the X-Axis. The StatusCode SemanticsChanged bit shall
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access

5.3.4.3 XYArrayItemType

Axis (XVType.x) and the value itself (XVType.value), used for the Y-Axis. Engineering units and range for the Value are defined by corresponding Properties inherited from the ArrayItemType . XAxisDefinition Property ... holds the information about the Engineering Units and Range for the X-Axis. The axisSteps of XAxisDefinition shall be set to NULL because it is not used. The StatusCode SemanticsChanged
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access

5.3.4.6 NDimensionArrayItemType

Int32, Int64, Float, Double, ComplexNumberType and DoubleComplexNumberType. AxisDefinition Property holds the information about the EngineeringUnits and Range for all axis. The StatusCode SemanticsChanged bit shall ... InstrumentRange, EURange, EngineeringUnits, Title or AxisDefinition Properties are changed (see 5.2 for additional information
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access

5.6.4.1 General

General EUInformation contains information about the EngineeringUnits . The intention of the OPC UA standard is not to define a set of units but a way to expose units based
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access

A.3.1.3 Item

properties of the DA Item are assigned to the EURange Property EngineeringUnits : The value of the Engineering Unit property of the DA Item are assigned to the EngineeringUnits Property . InstrumentRange
OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access

A.4.2.3 Variable Nodes

Units (Property ID: 100) : if the node in the OPC UA Server references a EngineeringUnits property node, then the value of the EngineeringUnits property node is assigned the EU Units
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services

10.2 Handling of OPC UA Namespaces

standards body although the namespace of the NodeId reflects something else, for example the EngineeringUnits Property . All NodeIds of Nodes not defined in this document shall not use the standard ... Namespaces used in this document NamespaceURI Namespace Index Example http://opcfoundation.org/UA/ 0 0:EngineeringUnits http://opcfoundation.org/UA/GDS/ 2 2:ApplicationRecordDataType
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.3.2.4 FieldMetaData

correctly describe the Field Value in the DataSetMessages . For example if the Property is EngineeringUnits , the unit of the Field Value shall match the unit of the FieldMetaData . The KeyValuePair
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.12.2 Supported configuration properties

property. Description of the Variable provides additional information. Properties like EURange or EngineeringUnits can be used to provide value ranges and units. The configuration property descriptions are referenced from
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

10.2 Handling of OPC UA Namespaces

standards body although the namespace of the NodeId reflects something else, for example the EngineeringUnits Property . All NodeIds of Nodes not defined in this document shall not use the standard ... Namespaces used in this document NamespaceURI Namespace Index Example http://opcfoundation.org/UA/ 0 0:EngineeringUnits http://opcfoundation.org/UA/Onboarding/ 2 2:Registrar http://opcfoundation.org/UA/GDS/ 3 3:ApplicationRecordDataType
OPC-10000-24 – OPC Unified Architecture - Part 24: Scheduler

10.2 Handling of OPC UA Namespaces

standards body although the namespace of the NodeId reflects something else, for example the EngineeringUnits Property . All NodeIds of Nodes not defined in this document shall not use the standard ... Namespaces used in this document NamespaceURI Namespace Index Example http://opcfoundation.org/UA/ 0 0:EngineeringUnits
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

6.3.7 CustomMetaDataProperties Property

structure of the CustomMetaDataProperties for a SerializationScope excluding the metadata comprising the EUInformation and EngineeringUnits Properties of the AnalogUnitType and AnalogUnitRangeType Variables in the SerializationScope . Figure 10 - CustomMetaDataProperties example ... KeyValuePair elements at the lowest indices contain the semantic Properties (e.g. key="EngineeringUnits", value=EUInformation) for the Value of the represented Variable . Sub- Variables are represented with elements
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

A.4 Energy Measurement Values

SerializationProperty contains the HasProperty ReferenceType . The same applies to the PeMeasurementID , AccuracyDomain , AccuracyClass and EngineeringUnits Properties of the MeasurementValueType Variables (see OPC PE ) The SerializationValue DataType structure contains only fields
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

14.2 Handling of OPC UA namespaces

standards body, although the namespace of the NodeId reflects something else, for example, the EngineeringUnits Property . All NodeIds of Nodes defined outside of this document shall not use the standard ... Namespaces used in this Document NamespaceURI Namespace Index Example http://opcfoundation .org/UA/ 0 0:EngineeringUnits http://opcfoundation .org/UA/FX/Data/ 2 2:FxCommandMask http://opcfoundation .org/UA/FX/AC/ 3 3:AutomationComponentType http://opcfoundation .org/UA/FX/CM
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.2.4 Verifying Assets

process could also be used to verify the values of configuration settings such as EngineeringUnits
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.3.7.4 Using ControlGroups with Connections

ConnectionEndpoint using the ReassignControlCmd . Then, as long as the Connection is established, the EngineeringUnits are locked and cannot be changed
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

10.1 General

defined in this clause. The Value of the LifetimeVariable provides the current value. The EngineeringUnits Property and the relation of the Indication to a classification ObjectType provide the semantic ... range of the Value . Table 143 - Lifetime examples Node CertificateValidity PartsProduced LifetimeVariable 200 553 EngineeringUnits (M) day number of parts StartValue (M) 365 0 WarningValues (O) 10 950 LimitValue
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

10.2 LifetimeVariableType definition

Value of the Variable , provided by the LifetimeVariableType's mandatory 0: EngineeringUnits , derived from the 0: AnalogUnitType . The DataType shall be the same as for the Value of the Variable ... Value of the Variable , provided by the LifetimeVariableType's mandatory 0: EngineeringUnits , derived from the 0: AnalogUnitType . The DataType shall be the same as for the Value of the Variable
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

12.2 Handling of OPC UA namespaces

standards body although the namespace of the NodeId reflects something else, for example the EngineeringUnits Property . All NodeIds of Nodes not defined in this specification shall not use the standard ... Namespaces used in this specification NamespaceURI Namespace Index Example http://opcfoundation.org/UA/ 0 0:EngineeringUnits http://opcfoundation.org/UA/DI/ 1 1:ComponentType http://opcfoundation.org/UA/DI/PackageMetadata/ 2 2:PackageMetadata
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

16.2 Handling of OPC UA Namespaces

standards body although the namespace of the NodeId reflects something else, for example the EngineeringUnits Property . All NodeIds of Nodes not defined in this document shall not use the standard ... Namespaces used in this document NamespaceURI Namespace Index Example http://opcfoundation.org/UA/ 0 0:EngineeringUnits http://opcfoundation.org/UA/DI/ 2 2:DeviceRevision
OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping

8.2 Handling of OPC UA Namespaces

standards body although the namespace of the NodeId reflects something else, for example the EngineeringUnits Property . All NodeIds of Nodes not defined in this document shall not use the standard
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

7.5.1 CalibrationValueType

inheriting the InstanceDeclarations of that Node 0:HasProperty Variable 0:EngineeringUnits 0:EUInformation 0:PropertyType M The CalibrationValueType inherits the Properties of the DataItemType . That does include the optional ... ValuePrecision , defining the precision of the calibration value. The mandatory 0: EngineeringUnits defines the engineering unit of the calibration values. Remark: The quantity of the calibration value is of importance
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

7.5.2 CapacityRangeType

inheriting the InstanceDeclarations of that Node 0:HasProperty Variable 0:EngineeringUnits 0:EUInformation 0:PropertyType M 0:HasProperty Variable Resolution 0:Double 0:PropertyType M The CapacityRangeType inherits the Properties ... optional 0: ValuePrecision , defining the precision of the calibration value. The mandatory 0: EngineeringUnits defines the engineering unit of the calibration values. The Resolution defines the step size
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

9.2 Handling of OPC UA Namespaces

standards body although the namespace of the NodeId reflects something else, for example the EngineeringUnits Property . All NodeIds of Nodes not defined in this document shall not use the standard ... Namespaces used in this document NamespaceURI Namespace Index Example http://opcfoundation.org/UA/ 0 0:EngineeringUnits http://opcfoundation.org/UA/DI/ 2 2:DeviceRevision
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location

10.2 Handling of OPC UA Namespaces

standards body although the namespace of the NodeId reflects something else, for example the EngineeringUnits Property . All NodeIds of Nodes not defined in this document shall not use the standard ... Namespaces used in this document NamespaceURI Namespace Index Example http://opcfoundation.org/UA/ 0 0:EngineeringUnits http://opcfoundation.org/UA/DI/ 2 2:DeviceRevision
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning

12.2 Handling of OPC UA Namespaces

standards body although the namespace of the NodeId reflects something else, for example the EngineeringUnits Property . All NodeIds of Nodes not defined in this document shall not use the standard ... Namespaces used in this document NamespaceURI Namespace Index Example http://opcfoundation.org/UA/ 0 0:EngineeringUnits http://opcfoundation.org/UA/RSL/ 2 2:SpatialLocationType