All TM V2: QSPApplication input does not work with active "Internal Control" (corrected from V3.26.0)

Corrected from:

The following libraries from V03.26.00:

L_TB2P_TechModulesBasic

L_TF2P_TechModulesFollowingPositioning

L_TS2P_TechModulesSynchronisingCamming

L_TW2P_TechModulesWindingTraversing

(Update via EASY Package Manager)

Response of the new version:

he xQSPApplication function can be triggered from the application if the visualisation is switched to active via InternalControl = TRUE.

What happens?

The function xQSPApplication from the application does not trigger a QSP.

When does the behaviour occur?

When xInternalCotnrol = TRUE is activated in the visualisation.

Which products are affected?

All TM V2 function modules from the following libraries:

L_TB2P_TechModulesBasic from V03.22.00

L_TF2P_TechModulesFollowingPositioning from V03.22.00

L_TS2P_TechModulesSynchronizingCamming from V03.22.00

L_TW2P_TechModulesWindingTraversing from V03.22.00

Short-term measures / evaluation / recommendations:

In some cases, the visualisation is used to commission technology modules or to test individual functions. In this case, the technology module can be operated via the visualisation from the PLC Designer. The xQspApplication function can be triggered from the visualisation. As soon as the visualisation is deactivated (xInternalControl = FALSE), the xQspApplication function can be triggered from the application.

Automatic Translation

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