10 OPC UA DataTypes ToC Previous Next

10.6 ResultValueDataType ToC Previous Next

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 TighteningResultDataType and StepResultDataType and represented as ResultValueType variable. The structure is defined in Table 78.

Table 78 - ResultValueDataType Structure

Name Type Description
ResultValueDataType structure Subtype of the 0:Structure defined in OPC 10000-5.
Value 0:Double    The mandatory Value is the measured value of the given result. The value corresponds to the PhysicalQuantity attribute of JoiningDataVariableType in the following section 9.10.Note: Additional information on whether the Torque or Angle are evaluated as positive or negative is described in the following section D.5.
Name 0:String The optional Name is a user readable name of the given measurement value.
ResultEvaluation ResultEvaluation The optional ResultEvaluation indicates whether the measured value is as per the configured limits and corresponds to a successful result or not. Refer section 10.2 for the pre-defined values.
ValueId 0:Guid The optional ValueId is the system-wide unique Identifier of the given value if it is available in the system.
ValueTag 0:Byte    The optional ValueTag is an associated tag to the given measurement value to classify it based on the tightening domain. Examples: FINAL, YIELD, SNUG, etc. It has the following pre-defined values which shall be used for each instance of this type.   * 0 - UNDEFINED   * 1 - FINAL indicates the final reported measurement value.   * 2 - TORSION indicates the twisting of the tightening 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 as a result 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 transition value between two steps in a multi-step program.   * 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 when a given trace is not beginning at the start of the step.   * 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.Note:   Additional explanations and pictures describing of some of the ValugTag values are provided in Annex C.
TracePointIndex 0:Int32 The optional TracePointIndex is the index to the trace sample array from which corresponds to this specific result.
TracePointTimeOffset 0:Double The optional TracePointTimeOffset is the time offset (in seconds) 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.
ReporterId 0:Guid The optional ReporterId is the system-wide unique identifier of the parameter configured in the Program which is being monitored or sampled.
ViolationType 0:Byte    The optional ViolationType 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.
ViolationConsequence 0:Byte    The optional ViolationConsequence provides information on the consequence occurred due to the violation of the configurable limits. Examples: Step Transition, Abort Tightening 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
SensorId 0:Guid The optional SensorId is the system-wide unique identifier of the sensor which has reported the value.
LowLimit 0:Double The optional LowLimit provides the lower limit of the measured value as per the program.
HighLimit 0:Double The optional HighLimit provides the upper limit of the measured value as per the program.
TargetValue 0:Double The optional TargetValue provides the target value of the specific measurement in the program step.
ResultStep 0:String    The optional ResultStep provides the step number or name of the program step which has generated the result. Note: This is not applicable for StepResultValues in StepResultType or StepResultDataType. This is added for OverallResultValues in TighteningResultType or TighteningResultDataType to get the information of particular step which has reported the specific value.
PhysicalQuantity 0:Byte The optional PhysicalQuantity is to determine the type of the physical quantity associated to a given value(s). Refer section 9.10 for the pre-defined values.
EngineeringUnits 0:EUInformation The optional 0:EngineeringUnits defines the engineering unit of the value.

Its representation in the AddressSpace is defined in Table 79.

Table 79 - ResultValueDataType Definiton

Attribute Value        
BrowseName ResultValueDataType        
IsAbstract False        
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the 0:Structure defined in OPC 10000-5.          

Previous Next