L_TS2P_FlyingSawState: If the engagement/disengagement process is aborted by Abort, the axle performs a speed jump (corrected from V3.26.0)

Corrected from:
L_TS2P_FlyingSawState from library L_TS2P_TechModulesSynchronizingCamming (as of V3.26.0)
(Update via Easy Package Manager)

Response of the new version:
The rising edge at the xStartFlyingSaw input while the Technology Module is ramping down to standstill via the xAbort function causes the technology module to re-engage with the material.
 
What happens?
The axis is synchronised to the conductance within one cycle. This causes the speed to jump to the value of the speed of the conductance. 

When does the behaviour occur?

The TM is synchronised to the master value. For this purpose, the inputs xStartFlyingSaw = TRUE and xSyncInstant = TRUE are set.

During the synchronisation phase, when the TM has not yet reached synchronous travel, the function xAbort = TRUE is switched.

A short time later in the deceleration phase of the function xAbort, when the drive has not reached standstill, the input xAbort = FALSE is switched and thus the request is cancelled.

As the inputs xStartFlyingSaw = TRUE and xSyncInstant = TRUE are set, the TM changes back to automatic mode. In this case, synchronisation to the master value takes place abruptly.

Which products are affected?
L_TS2P_FlyingSawState from library L_TS2P_TechMoulesSynchronizingCamming

Short-term measures:
With xAbort, the input xStartFlyingSaw = FALSE is also to be switched.
From the style state, xStartFlyingSaw = TRUE can be switched again.

Evaluation / recommendations:
The coupling process is not reset with the function xAbort = TRUE. The synchronisation is reset via xStartFlyingSaw = FALSE. With consideration of the short-term measure, the axis can be synchronised to the master value.


Automatic Translation


URL for linking this AKB article: https://www.lenze.com/en-de/go/akb/202200194/1/
Contact form