L_TS2P_CrossCutterState: CrossCutter no longer starts after canceling a limiter command (fixed from V3.20.0)

Corrected from:
Library: L_TS2P_TechModulesSynchronizingCamming as of V03.20.00.60
                    (Update via Easy Package Manager)
Response of the new version:
After the limiter request (SSS1, SS2 etc.), the technology module can switch back to cutting mode via the xSyncIn = TRUE function.
 
What happens?
The CrossCutter stops despite xSyncIn = TRUE.
The status information of the technology module (state eTMState = CUTTING) indicates that the axis is running.
 
When does the behaviour occur?
After the CrossCutter is synchronized a stop is requested by the limiter (SSS1, SS2 etc.).
After the axis has been ramped down, the limiter request is canceled again.
Then it should be synchronized again with xSyncIn = TRUE.
 
Which products are affected?
Function Block L_TS2P_CrossCutterState from Library L_TS2P_TechModulesSynchronizingCamming
 
Short-term measures:
Cancel the synchronization with xAbort = True or xResetError = True and order xSyncIn = TRUE renewed at the technology module.
 
Evaluation / Recommendations:
The technology module can be switched back to automatic mode by taking the short-term measure into account.
 
Auromatic Translation

URL for linking this AKB article: https://www.lenze.com/en-de/go/akb/201900366/1/
Kontaktformular