
Architecture: The ApplicationTemplate in detail
Error handling
94
Lenze · ApplicationTemplate · 1.3 EN - 04/2013
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
2. Activation for one cycle: Via the baseChannelSetErrorQuit method, rising edge FALSE
ÊTRUE. The
method sets the xQuitErrors input to TRUE for one cycle.
If multiple errors occur, they cannot
be acknowledged individually. Further information:
L_EATP_ModuleErrorHandler
( 124)
9.9.4 Acknowledging errors: Response in the machine module
The xErrorQuitActive output on the L_EATP_ModuleErrorHandler block can be used within a module
application to acknowledge errors on an integrated function block.
Defining errors - standard procedure
ErrorHandler.xQuitErrors := TRUE; //error acknowledgement active as long as value =
TRUE
•The SetErrors method is to be
extended by one function block.
•The MAP_EmptyModul_App1 FB is
to be extended by the
corresponding declaration.
•The xSetError[1...4] inputs must be
connected to the module
application.
• Assign the corresponding
parameter to the respective error
input:
• Error number,
•Error text,
•Error priority,
• Acknowledgement response
•More information:
L_EATP_ErrorSet
( 119)
Comentarios a estos manuales