Which products are affected?
Template Positioner as of V3.4
What happens?
The current set velocity, which is output via g_nSetVelocity_v, does not always match with the internally used set velocity if the controller is inhibited. The variable keeps the value of the parameter cycle which has been saved last before the controller has been inhibited.
When does the problem occur?
The problem occurs if the controller is inhibited by a velocity setpoint unequal zero while the template is in the 'Positioning' state.
Possible diagnostics?
The controller is inhibited out of the 'Positioning' (g_byOperationState =Positioning) state and while the axis is rotating. In addition, the control variable g_bPositioningEnable has not been reset to FALSE before. As a result, the variable g_DCTRL_bCInh_b =TRUE signals that the controller is inhibited and g_nSetVelocity indicates a value unequal zero which corresponds to the last setpoint of the profile generator before the controller has been inhibited.
Short-term measures/recommendations?
Since the g_nSetVelocity_v signal may not be correct if the controller is inhibited an evaluation of the signal does not make sense.
In case of an inhibited controller the g_nSetVelocity_v signal is wrong if g_nSetVelocity_v is unequal zero in the cycle in which the controller is inhibited.
Evaluation:
The behaviour can be retraced and thus diagnosed quickly.
The evaluation or further processing of this set velocity leads to a wrong result if the controller is inhibited. Its use depends on the application.
