L_TF2P_TablePosisioning: Abort in standby triggers error 20401 NoValidDeceleration_Halt (corrected from V3.29.0)

Corrected from:
Library L_TF2P_TechModulesFollowingPositioning (from V3.29.0).
(Update via Easy Package Manager)

Response of the new version:
The technology module L_TF2P_TablePositioningBase changes to the STOP state and reports xAbortDone = TRUE.
 
What happens?
The technology module L_TF2P_TablePos switches to error 20401 (NoValidDeceleration_Halt).

When does the behaviour occur?
The technology module switches to the error state specified above when an invalid profile sequence is selected. After the xResetError, it switches to the STANDBY state.
With xAbort = TRUE, the technology module switches back to the error state. 

Which products are affected?
L_TF2P_TablePositioningBase from library 
L_TF2P_TechModulesFollowingPositioning 

Short-term measures:
The function scCtrlBasicMotion.xHalt can be used instead of xAbort.

Evaluation / recommendations:
In principle, it is not necessary to apply the xAbort function from the STANDBY state, since the axis is already at standstill. In normal operation, when a profile linkage is being moved, the profile can be aborted via xAbort, xQSPApplication and via scCtrlBasicMotion.xHalt and the axis can be brought to standstill.


Automatic Translation

URL for linking this AKB article: https://www.lenze.com/en-de/go/akb/202200370/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: 202200370
Last update: 2023/09/10
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