10.3 ResultValueDataType
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 212.
| 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 | It is a user readable name of the given measurement value. | 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. < 0 – application specific extensions. 0 – UNDEFINED 1 – FINAL indicates the final reported measurement value. 2 – TORSION indicates the twisting of the joining system when applying the tightening torque. When a bolt is tightened, it is subjected to tensile stress as preload is introduced but also to torsion stress because of thread friction. 3 – SNUG or SEATING is the reported point where screw head touches the surface and all parts have mated. 4 – YIELD is the yield point is the reported point on a stress-strain curve that indicates the limit of elastic behaviour and the beginning of plastic behaviour. 5 – EXIT indicates a value sampled when the decision for the step transition is made. 6 – TRACE_START is the point that represents the offset from the start of the step to the FIRST reported trace value when a given trace is not beginning at the start of the step. 7 – TRACE_END is the point that represents the offset from the start of the step to the LAST reported trace value. 8 – MAX represents the maximum value of the given measurement. 9 – MIN represents the minimum value of the given measurement. 10 – TOOL_ANGLE_MOVEMENT represents the angle that handheld tool has moved until reaching the FINAL point, as registered by the internal GYRO. 11 – AVERAGE is the average value. 12 – EXIT_TRIGGER indicates that this value triggered the step transition. 13 – FIRST 14 – RUNDOWN 15 – PREVAILING 16 – SELFTAP 17 – SHUTOFF 18 – RESIDUAL 19 – RESCINDING 20 – PULSE_COUNT 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 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. 0 – UNDEFINED 1 – ABOVE_LIMIT indicates that the measured value is above the configured limit. 2 – BELOW_LIMIT indicates that the measured value is below the configured limit. 3 – NOT_DECIDABLE indicates that the decision is not possible or applicable. | 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. 0 – UNDEFINED 1 – ABORT 2 – NORMAL_STEP_TRANSITION 3 – REPAIR_STEP_TRANSITION 4 – WARNING | 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 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 measured value. | True |
Its representation in the AddressSpace is defined in Table 213.
| 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 | |||||
| IJT Engineering Units |