The JoiningDataVariableType is a subtype of the BaseDataVariableType. It is to describe common sematic required for variables in the system. In this version of the specification, it provides information about physical quantity and Engineering Units. It is formally defined in Table 188.
Table 188 – JoiningDataVariableType Definition
|
Attribute |
Value |
||||||
|
BrowseName |
JoiningDataVariableType |
||||||
|
IsAbstract |
False |
||||||
|
ValueRank |
−1 (−1 = Scalar) |
||||||
|
DataType |
BaseDataType |
||||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
Other |
||
|
Subtype of the 0:BaseDataVariableType defined in OPC 10000-5. |
|||||||
|
0:HasComponent |
Variable |
PhysicalQuantity |
0:Byte |
0:MultiStateDiscreteType |
O, RO |
||
|
0:HasProperty |
Variable |
0:EngineeringUnits |
0:EUInformation |
0:PropertyType |
O, RO |
||
|
Conformance Units |
|||||||
|
IJT Engineering Units |
|||||||
|
|
|||||||
The component Variables of the JoiningDataVariableType have additional Attributes defined in Table 189.
Table 189 – JoiningDataVariableType Attribute values for child nodes
|
BrowsePath |
Value Attribute |
|||
|
OTHER TIME TORQUE ANGLE IMPULSE DISTANCE AREA VOLUME FORCE PRESSURE VOLTAGE CURRENT RESISTANCE POWER ENERGY MASS TEMPERATURE FREQUENCY JOLT VIBRATION NUMBER LINEAR_SPEED ANGULAR_SPEED LINEAR_ACCELERATION ANGULAR_ACCELERATION TORQUE_SPEEDTORQUE_ACCELERATION TORQUE_PER_ANGLE_GRADIENT TORQUE_PER_ANGLE_GRADIENT2 |
PhysicalQuantity is to determine the type of the physical quantity associated to a given value(s). It has the following pre-defined values which shall be used for each instance of this type.
- 0 – OTHER
- 1 – TIME
- 2 – TORQUE
- 3 – ANGLE
- 4 – IMPULSE
- 5 – DISTANCE
- 6 – AREA
- 7 – VOLUME
- 8 – FORCE
- 9 – PRESSURE
- 10 – VOLTAGE
- 11 – CURRENT
- 12 – RESISTANCE
- 13 – POWER
- 14 – ENERGY
- 15 – MASS
- 16 – TEMPERATURE
- 17 – FREQUENCY
- 18 – JOLT
- 19 – VIBRATION
- 20 – NUMBER
- 21 – LINEAR_SPEED is the change of distance over time.
- 22 – ANGULAR_SPEED is the change of angle over time.
- 23 – LINEAR_ACCELERATION is the change of DISTANCE_SPEED over time.
- 24 – ANGULAR_ACCELERATION is the change of ANGULAR_SPEED over time.
- 25 – TORQUE_SPEED is the change of torque over time.
- 26 – TORQUE_ACCELERATION is change of TORQUE_SPEED over time.
- 27 – TORQUE_PER_ANGLE_GRADIENT is the change of torque over angle.
- 28 – TORQUE_PER_ANGLE_GRADIENT2 is the change of TORQUE_PER_ANGLE_GRADIENT over angle. Example: It is used for yield and snug detection. It represents change of the slope in a torque over angle graph.
0:EngineeringUnits defines the engineering unit of the values.
Note: The quantity and units of the value is of importance, and it is going to be defined in harmonized way.
Note on Physical Quantity and Engineering Units
JoiningDataVariableType describes a minimal way to provide the PhysicalQuantity and EngineeringUnits properties for a given value.
An application can ensure that those are available by using a corresponding Conformance Unit defined for this use case.
If an application does not provide the EngineeringUnits for a given value, it is assumed to be in International System of Units (SI).
The JoiningSystemResultType is a subtype of 0:BaseVariableType. It is used to expose the information of the 5:ResultDataType in individual sub-variables. The 5:ResultMetaData have the same meaning as defined by the DataType in section 10.1.
It is formally defined in Table 190.
Table 190 – JoiningSystemResultType Definition
|
Attribute |
Value |
||||
|
BrowseName |
JoiningSystemResultType |
||||
|
IsAbstract |
False |
||||
|
ValueRank |
-1 (-1 = Scalar) |
||||
|
DataType |
5:ResultDataType |
||||
|
References |
Node Class |
BrowseName |
DataType |
TypeDefinition |
Other |
|
Subtype of the 5:ResultType defined in OPC 40001-101. |
|||||
|
0:HasStructuredComponent |
Variable |
5:ResultMetaData |
JoiningResultMetaDataType |
0:BaseDataVariableType |
M, RO |
|
Conformance Units |
|||||
|
IJT Result Variable Access |
|||||
|
|
|||||
The components of the JoiningSystemResultType have additional subcomponents which are defined in Table 191.
Table 191 – JoiningSystemResultType Additional Subcomponents
|
Source Path |
Reference |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
Others |
|
5:ResultMetaData |
0:HasStructuredComponent |
Variable |
JoiningTechnology |
0:LocalizedText |
0:BaseDataVariableType |
O |
|
5:ResultMetaData |
0:HasStructuredComponent |
Variable |
SequenceNumber |
0:Int64 |
0:BaseDataVariableType |
O |
|
5:ResultMetaData |
0:HasStructuredComponent |
Variable |
Name |
0:String |
0:BaseDataVariableType |
O |
|
5:ResultMetaData |
0:HasStructuredComponent |
Variable |
Description |
0:LocalizedText |
0:BaseDataVariableType |
O |
|
5:ResultMetaData |
0:HasStructuredComponent |
Variable |
Classification |
0:Byte |
0:BaseDataVariableType |
O |
|
5:ResultMetaData |
0:HasStructuredComponent |
Variable |
OperationMode |
0:Byte |
0:BaseDataVariableType |
O |
|
5:ResultMetaData |
0:HasStructuredComponent |
Variable |
AssemblyType |
0:Byte |
0:BaseDataVariableType |
O |
|
5:ResultMetaData |
0:HasStructuredComponent |
Variable |
AssociatedEntities |
EntityDataType[] |
0:BaseDataVariableType |
O |
|
5:ResultMetaData |
0:HasStructuredComponent |
Variable |
ResultCounters |
ResultCounterDataType[] |
0:BaseDataVariableType |
O |
|
5:ResultMetaData |
0:HasStructuredComponent |
Variable |
InterventionType |
0:Byte |
0:BaseDataVariableType |
O |
|
5:ResultMetaData |
0:HasStructuredComponent |
Variable |
IsGeneratedOffline |
0:Boolean |
0:BaseDataVariableType |
O |
|
5:ResultMetaData |
0:HasStructuredComponent |
Variable |
ExtendedMetaData |
KeyValueDataType[] |
0:BaseDataVariableType |
O |
Refer section 10.1 for the descriptions of the variables.
The JoiningSystemEventContentType is a subtype of 0:BaseVariableType. It is used JoiningSystemEventType and JoiningSystemConditionType.
It is formally defined in Table 192.
Table 192 – JoiningSystemEventContentType Definition
|
Attribute |
Value |
||||
|
BrowseName |
JoiningSystemEventContentType |
||||
|
IsAbstract |
False |
||||
|
ValueRank |
-1 (-1 = Scalar) |
||||
|
DataType |
0:BaseDataType |
||||
|
References |
Node Class |
BrowseName |
DataType |
TypeDefinition |
Other |
|
Subtype of the 0:BaseDataVariableType defined in OPC 10000-5. |
|||||
|
0:HasComponent |
Variable |
JoiningTechnology |
0:LocalizedText |
0:BaseDataVariableType |
O, RO |
|
0:HasComponent |
Variable |
AssociatedEntities |
EntityDataType[] |
0:BaseDataVariableType |
O, RO |
|
0:HasComponent |
Variable |
ReportedValues |
ReportedValueDataType[] |
0:BaseDataVariableType |
O, RO |
|
0:HasComponent |
Variable |
EventText |
0:LocalizedText |
0:BaseDataVariableType |
O, RO |
|
0:HasComponent |
Variable |
EventCode |
0:Int64 |
0:BaseDataVariableType |
O, RO |
|
Conformance Units |
|||||
|
IJT Event Payload |
|||||
|
IJT Event Payload Associated Entities |
|||||
|
IJT Event Payload Reported Values |
|||||
JoiningTechnology is a human readable text to identify the joining technology which has triggered the event. Examples: Tightening, Gluing, Riveting, Flow Drill Fastening, etc.
AssociatedEntities is a list of identifiers of various entities/objects available in the given system. Example: An event maybe associated to Asset, Result, Joint, Error, etc.
EventText is a human readable text related to the context of the event.
EventCode is a system specific event code associated to the given event.
ReportedValues is a list of values associated with the given event payload. Example: If it is an over temperature event, then the ReportedValue can be the measured value along with the corresponding limits.