Eliminated from:
Library
LenzeCam V01.03.06.00 and higher, included from Engineer HighLevel 2.10 SP2 onwards
Behaviour of the new version?
The
bOpenDone status signal of the
L_CamClutchPos function block now behaves as described in the documentation. However, the
bInTarget status signal has not been corrected.
What happens?
In library versions < V01.03.06.00, the
bOpenDone and
bInTarget status outputs of the
L_CamClutchPos function block indicate TRUE, although the electronic clutch has engaged (status signal bClosed = TRUE).
When does the problem occur?
The problem occurs when the
L_CamClutchPos clutch function block is in the disengaged state (status signal
bClosed = FALSE,
bOpenDone = TRUE,
bInTarget = TRUE) and the input position
dnPosIn_p is at the
dnOpenPosition_p standstill position. If the electronic clutch
L_CamClutchPos is then directly engaged by means of the control input bOpen = TRUE => FALSE, the clutch block changes to the engaged state directly without an engaging phase and without the
bOpenDone and
bInTarget status signals being reset to FALSE.
Possibilities of diagnosis?
The behaviour can be adjusted by means of the following control sequence:
- Disengage electronic clutch L_CamClutchPos with the electrical shaft running (bOpen = FALSE => TRUE)
- Permanently equate the master position dnPosIn_p to the standstill position dnOpenPosition_p
- Close electronic clutch L_CamClutchPos (bOpen = TRUE => FALSE)
The described behaviour occurred when the
bClosed, bOpenDone and
bInTarget status outputs indicated TRUE .
Short-term measures/recommendations?
The
bOpenDone and
bInTarget status signals can be replicated and applied, depending on the output signals.
Evaluation:
The functional restriction only becomes apparent in the case of a certain control sequence, which is rarely used in practice. The behaviour therefore only occurs rarely in the field.
Due to the added element in the function block interconnection, the
bOpenDone and
bInTarget signals can be replicated and applied.
