L_TS2P_FlyingSawState: Engaging after abort by QSPAppl is no longer possible (corrected from V3.26.0)

Corrected from:
Library L_TS2P_TechModulesSynchronizingCamming (from V3.26.0)
(update via Easy Package Manager)

Response of the new version:
With xQSPApplication = TRUE the running synchronous operation is interrupted. As soon as the request xQSPApplication = FALSE is present and the two inputs xStartFlyingSaw = TRUE and xSyncInInstant = TRUE are present, the FlyingSaw process is started immediately.

What happens?
The TM L_TS2P_FlyingSaw stops and does not synchronise to the material.

When does the behaviour occur?
The input xSyncInInstant = TRUE is set over the entire sequence.
The TM moves synchronously with the material.
Synchronous travel is stopped via xQSPApplication = TRUE.
After the axis reaches standstill, the request xQSPApplication = FALSE is withdrawn. The inputs xStartFlyingSaw = TRUE and xSyncInInstant = TRUE remain set over this sequence.

Which products are affected?
L_TS2P_FlyingSawState from library L_TS2P_TechModulesSynchronizingCamming
 
Short-term measures:
Together with xQSPApplication = TRUE, the inputs xStartFlyingSaw = FALSE and xSyncInInstant = FALSE are to be taken back.

Evaluation / recommendations:
With xQSPApplication = TRUE the running synchronous operation is aborted and not reset as long as the two inputs xStartFlyingSaw = TRUE and xSyncInInstant = TRUE are set. This means that no new synchronisation run can be started. With consideration of the short-term measures, a new synchronisation run can be started.

Automatic Translation

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