Corrected from:
Library: L_TS2P_TechModulesSynchronizingCamming V3.24.0
(update via Easy Package Manager)
Response of the new version:
The slave axis remains above the lower driving range limit lrLowerLimit (case A) and initiates the synchronisation process in good time (case B) even if the parameters scPar.lrSyncJerk and scPar.lrJerk have unequal values.
What happens?
Case A
The slave axis exceeds the lower travel range limit lrLowerLimit.
or
Case B
The slave axis starts the synchronisation process too late and must subsequently become faster than the master value to catch up with the synchronous position.
When does the behaviour occur?
The parameters scPar.lrSyncJerk and scPar.lrJerk are different:
Case A: scPar.lrSyncJerk > scPar.lrJerk
Case B: scPar.lrSyncJerk < scPar.lrJerk
Which products are affected?
TM FlyingSaw (L_TS2P_FlyingSawState from library L_TS2P_TechModulesSynchronizingCamming)
Short-term measures:
The parameters scPar.lrSyncJerk and scPar.lrJerk must be the same.
scPar.lrSyncJerk = scPar.lrJerk
Evaluation / recommendations:
It is recommended to set the jerks for all functions (Jogging, MoveAbs, MoveToParkPos etc.) to the same value.
Automatic Translation
