It is used to report measurement values of the joining operation. Those are meant to characterize the quality of the process. It is used in JoiningResultDataType and StepResultDataType. The structure is defined in Table 197.
Table 197 – ResultValueDataType Structure
Name |
Type |
Description |
Optional |
ResultValueDataType |
structure |
Subtype of the 0:Structure defined in OPC 10000-5. |
|
MeasuredValue |
0:Double |
It is the measured value of the given result. The value corresponds to the PhysicalQuantity attribute of JoiningDataVariableType in the following section 9.1. |
False |
Name |
0:String |
True |
|
ResultEvaluation |
5:ResultEvaluationEnum |
It indicates whether the measured value is as per the configured limits and corresponds to a successful result or not. |
True |
ValueId |
0:TrimmedString |
It is the identifier of the given value if it is available in the system. |
True |
ValueTag |
0:Int16 |
It is an associated tag to the given measurement value to classify it based on the joining domain. Examples: FINAL, YIELD, SNUG, etc. It has the following pre-defined values which shall be used for each instance of this type.
Note: Additional explanations and pictures describing of some of the ValugTag values are provided in Annex C. |
True |
TracePointIndex |
0:Int32 |
It is the index to the trace sample array from which corresponds to this specific result. |
True |
TracePointTimeOffset |
0:Duration |
It is the time offset to point out the absolute time point in the array of trace samples. This may or may not match with an element in the TraceContent array. If it is not available in the TraceContent array, the value can be visualized in the trace graph via interpolation or some other plotting mechanisms. |
True |
ParameterIdList |
0:TrimmedString[] |
It is an array of parameter identifiers configured in the Program which is being monitored or sampled. Note: In most common cases, it can be a single identifier. |
True |
ViolationType |
0:Byte |
Indicates whether the measured value is above or below the configured limit. It is only relevant if program or step configuration is violated. It has the following pre-defined values which shall be used for each instance of this type.
|
True |
ViolationConsequence |
0:Byte |
It provides information on the consequence occurred due to the violation of the configurable limits. Examples: Step Transition, Abort Joining Operation. Is the consequence repairable or not, etc. It has the following pre-defined values which shall be used for each instance of this type.
|
True |
SensorId |
0:TrimmedString |
It is the system-wide unique identifier of the sensor which has reported the value. |
True |
LowLimit |
0:Double |
It provides the lower limit of the measured value as per the program. |
True |
HighLimit |
0:Double |
It provides the upper limit of the measured value as per the program. |
True |
TargetValue |
0:Double |
It provides the target value of the specific measurement in the program step. |
True |
ResultStep |
0:String |
It provides the step number or name of the program step which has generated the result. Note: This is not applicable for StepResultValues in StepResultDataType. This is added for OverallResultValues in JoiningResultDataType to get the information of the step which has reported the specific value. |
True |
PhysicalQuantity |
0:Byte |
It is to determine the type of the physical quantity associated to a given value(s). Refer section 9.1 for the pre-defined values. |
True |
EngineeringUnits |
0:EUInformation |
It is the engineering unit of the measured value. |
True |
Its representation in the AddressSpace is defined in Table 198.
Table 198 – ResultValueDataType Definition
Attribute |
Value |
||||
BrowseName |
ResultValueDataType |
||||
IsAbstract |
False |
||||
References |
Node Class |
BrowseName |
DataType |
TypeDefinition |
Other |
Subtype of the 0:Structure defined in OPC 10000-5. |
|||||
Conformance Units |
|||||
IJT Result Value Trace Point Index |
|||||
IJT Result Value Trace Point Time Offset |
|||||
IJT Result Value FINAL Tag |