Eliminated from:
LenzeCam library V01.03.06.00 and higher, included from Engineer HighLevel 2.10 SP2 onwards
Behaviour of the new version?
After a download or after the power has been switched on, the L_CamSyncIn function block correctly synchronises with the master value when oversynchronous engaging of the clutch takes place.
What happens?
The L_CamSyncIn function block does not synchronise with the master speed as expected but indicates an error at the status output bError. Bit 18 in the status code C5609 has been set ('maximum speed C5602 is exceeded').
In this case, C5602 may have been set to far higher values than the maximum speed necessary for actual synchronisation.
When does the problem occur?
For oversynchronous clutch-in (the position difference between the dnTpPos_p and dnOpenPos_p inputs must be smaller than the position difference between the dnOpenPos_p and dnSyncPos_p inputs), the L_CamSyncIn function block calculates the maximum occurring initial speed and compares it with the limit parameterised in C5602. This is done before motion actually starts.
After the power has been switched on or after device initialisation, the scaling routine for code C5602 ('maximum speed') is not called. This is incorrect and causes the function block to calculate internally with a maximum speed of zero. It is only after the code has been re-written and the scaling routine for C5602 has been called that the internal speed limit is set to the correct value.
Possibilities of diagnosis?
Although C5602 has been set to far higher values than the maximum speed needed for actual synchronisation, the function block remains at a standstill after the start command and signals an error via the status output bError. In this case, bit 18 in status code C5609 is set ('maximum speed C5602 is exceeded').
Short-term measures/recommendations?
Write the desired maximum speed in code C5602 after initialisation (e.g. by means of an automated writing procedure by means of the L_DevWriteParDInt) function block.
Evaluation:
The functional restriction occurs in a reproducible manner after device initialisation but only if oversynchronous clutch-in is necessary. The functional restriction is eliminated as a result of code C5602 being re-written.
