Which products are affected?
ESP-SPAC-CAM1 – Software Package Cam V1.4 (
LenzeCamControl1V0104.lib library)
What happens?
The clutch does not engage at the correct position in the clock pulse. This means that the input of the clutch function (
L_CamClutchXAxis.dnSetPosition_p) and the output of the clutch function (
L_CamClutchXAxis.dnPosOut_p) indicate different values although the state 'engaged' is signalled via status signal
L_CamClutchXAxis.bOpen = FALSE.
When does the problem occur?
The problem occurs with the following control sequence:
- The clutch is opened directly or at the stop position selected (control signals bClose = FALSE or bOpenInstant = TRUE)
- The input position dnSetPosition_p continues to move and reverses in the same clock pulse.
- The input position dnSetPosition_p passes the current clutch position dnPosOut_p and moves on without exceeding/falling below the clock-pulse limit.
- The input value stops.
- The clutch re-engages via bOpenInstant = FALSE and a positive edge at bClose. The clutch engages directly so that a constant misalingment between the input position dnSetPosition_p and output position dnPosOut_p occurs.
The direction of rotation of the master value is not important.
Possible diagnostics?
The problem can be reproduced by using the control sequence descirbed above. The problem also occurs in the CAM template since the function block
L_CamClutchXAxis is used here, too.
Short-term measures/recommendations?
A reversing of the master value can be avoided by limiting the direction of rotation in the master signal input. This can be done be using e.g. the function block
L_CamLimitVelocity.
Evaluation:
The problem occurs if the master value (e. g. when using a handwheel function) reverses frequently and the clutch should engage and disengage in this operating mode. Usually, the production machines use master signals with a constant velocity. Thus the problem described does not occur.
