Lenze PLC Designer ApplicationTemplate (PLC Designer R3-x) - Manual (Page 93)

Lenze · ApplicationTemplate · 1.3 EN - 04/2013
93
Architecture: The ApplicationTemplate in detail
Error handling
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
More information:
L_EATP_ErrorSet ( 119)
L_EATP_ModuleErrorHandler ( 124)
9.9.2 Configuring an error response
The error response types of the error handler define the state of the module's intrinsic application.
If an error occurs, the standard behaviour triggers the configured error response in the other
machine modules.
If a different error response of the machine module is desired, the possibility of programming the
desired error response in the corresponding machine module is provided.
• Further information on the DefaultCoupling (predefined standard response) can be found in the
following section: Default coupling ( 83)
• The error states that can be defined in the module applications (MAP) are divided into the
following error categories:
9.9.3 Acknowledging errors
The acknowledgement of errors deletes all error messages / error causes that have been defined as
requiring acknowledgement from the current error list (Error List).
The acknowledgement of errors can be activated by the following procedures:
1. Permanent activation: Within the module application via the following program command:
Error text Text description of the error. The (English) error text is stored in the table of
attributes.
The error text always is to be used if no higher-level
mechanism for implementation of the error number
in national languages is activated (example: higher-
level visualization).
Detailed
error information
For each error, an additional
attribute (type: DWORD) can be
used, which (in connection with the
error number) can be interpreted.
For a "Drive Error" group error, for instance, the
detailed error information of the corresponding
controller can be used.
Priority Assign priority for errors of the same error response type.
Characteristic Description Further information
Error response (in order of ascending
priority)
Description / acknowledgement behaviour
Information Writes information in the logbook of the controller.
• No acknowledgement required.
Quick stop (fault) Error response in the case of which the machine module involved changes to
the "Stop" status.
• The acknowledgement behaviour is parameterisable.
Warning The machine module/the application remains in the same status.
• The acknowledgement behaviour is parameterisable.
Error Causes the machine module involved to trip a response (for example setting
controller inhibit/pulse inhibit).
• The acknowledgement behaviour is parameterisable.
System fault Fatal error.
Restart of the application required (by mains switching or device reset).
• No acknowledgement possible.