Corrected from:ApplicationTemplate Standard project template from V3.16
Response of the new version:
The P09_Error action is only processed if one of the outputs xLocalError, xLocalWarning, xSlaveError, or xSlaveWarning of the L_EATP_OpModeAccess function block (see BF01_BasicFunction action in the machine module) is TRUE.
The ErrorEntry range in the P09_Error action is processed if the action was not processed in the last PLC cycle (i.e. if no message was pending neither locally nor in a lower-level slave).
The ErrorExit range is processed if the P09_Error action was processed in the last PLC cycle and there is no longer any message pending in the current cycle.
What happens?
The ErrorEntry and the ErrorExit range in the P09_Error action of the machine module are not processed although the P09_Error action is processed or has been processed.
When does this behaviour occur?
The ErrorEntry range in the P09_Error action is processed once when the machine module reports a local error (OpModeAccess.xLocalError=TRUE). The ErrorExit range is processed once when the local error is no longer pending or has been acknowledged.
The P09_Error action is, however, also processed when warnings or errors of slave machine modules are reported. In this case, the ErrorEntry and the ErrorExit range are not processed.
Which products are affected?
PLC Designer from V3.14
ApplicationTemplate Standard project template from V3.14
Short-term measures:
If necessary, program a separate edge evaluation for warnings and errors of slave machine modules in the P09_Error action. Use the xLocalWarning, xSlaveError, and xSlaveWarning outputs of the OpModeAccess block instance called in the BF01_BasicFunction action of the machine module for this.
Evaluation/recommendations:
The ErrorEntry and the ErrorExit range in the P09_Error action of the machine module are only processed in the case of local error messages. An applicative solution is described under 'Short-term measures'.
