Corrected from:
L_EATP_ApplicationTemplate V3.16
Response of the new version:
The xLocalError, xLocal Warning, xSlaveError, and xSlaveWarning outputs of the L_EATP_OpModeAccess function block can be TRUE at the same time.
What happens?
At the L_EATP_OpModeAccess function block (see 'BF01_BasicFunction' action in the machine module), there is only the xLocalError output active although both 'Error' and 'Warning' messages are simultaneously set via the L_EATP_ErrorSet function block.
At the L_EATP_OpModeAccess function block, there is only the xSlaveError output active although in the slave machine module both an 'Error' message and a 'Warning' are simultaneously set.
When does this behaviour occur?
The above-described behaviour occurs if locally or in the slave machine module an 'Error' message and a 'Warning' are active at the same time.
Which products are affected?
L_EATP_ApplicationTemplate library V3.14 and higher
Short-term measures:
None
Evaluation/recommendations:
The L_EATP_OpModeAccess function block cannot be used to check if an 'Error' message and a 'Warning' are active at the same time.
