Corrected from:
- Library: L_MC2P_MotionControlCam (FAST Motion) from V03.13.00.52
(contained in the PLC Designer from V03.13.00)
Response of the new version:
Under the described conditions and with the setting SyncMode = mcSlowDown, clutching-in works as described.
Now, the distance for clutching-in is calculated in the FB and the value is no longer accepted at the MasterStartDistance input.
What happens?
Under certain conditions (see below), clutching-in with the setting SyncMode = mcSlowDown does not work correctly.
With the setting SyncMode = mcSlowDown, the distance required for clutching in is supposed to be calculated in the FB. Actually, the value at the MasterStartDistance input is erroneously accepted which, in this case, won't be set to a value unequal zero by the application.
When does this behaviour occur?
- Master axis is in the "Modulo" mode and
- slave axis is parameterised in the "Limited" mode.
Which products are affected?
- Library: L_MC2P_MotionControlCam (FAST Motion)
(contained in the PLC Designer)
Short-term measures:
Provide the MasterStartDistance by calculating it in the application via the FB input:
MC_GearInPos.MasterStartDistance := 2 * ABS ( lrSlaveSyncPositionSet - lrActPosition )
Note:
The MasterSyncPosition and SlaveSyncPosition input parameters must not change while clutching in.
Evaluation/recommendations:
