All TM V2: In certain cases the wrong state is displayed (Jogging--> STOP)(corrected from V3.22.0)

Corrected from:
The following libraries as of V03.22.00:  
L_TB2P_TechModulesBasic 
L_TF2P_TechModulesFollowingPositioning
L_TS2P_TechModulesSynchronizingCamming
L_TW2P_TechModulesWindingTraversing
                       (Update via EASY Package Manager)

Response of the new version:
The wrong STOP state is no longer displayed during jogging.
What happens?
All technology modules show the STOP state instead of the active JOGGING state.
 
When does the behaviour occur?
If a manual operation is interrupted by a HALT, the technology module changes to the STOP state.
If the xStop input is left at TRUE and a new jogging is requested, e.g. via xJogPos, the axis starts moving.

However, the state of the technology module remains STOP.

This error occurs of course also in all other technology modules.

Which products are affected?
All TM V2 function blocks from the following libraries:
L_TB2P_TechModulesBasic 
L_TF2P_TechModulesFollowingPositioning
L_TS2P_TechModulesSynchronizingCamming
L_TW2P_TechModulesWindingTraversing

Short-term measures:
Resetting the STOP request before requesting another jog.
 
Automatic Translation

URL for linking this AKB article: https://www.lenze.com/en-de/go/akb/202000187/1/
Meta data
Taxonomy: Lib L_CM1P_ControlModules , Lib L_TB1P_TechnologyBasics , Lib L_TB2P_TechModulesBasic , Lib L_TF2P_TechModulesFollowingPositioning , Lib L_TP2P_TechModulesProcessFunctions , Lib L_TS2P_TechModulesSynchronizingCamming , Lib L_TW2P_TechModulesWindingTraversing , FAST Motion Modules V2
AKB-ID: 202000187
Last update: 2023/09/09
Category: Version Informations

Lenze reserves the right to change information on this page at any time. Any liability for the accuracy of the information is excluded.
Contact form