The communication is interrupted for a short period of time when a communication error is reset in case of the EPL master (remedied from V1.05)

Remedied from:
Communication module E94AYCEP Firmware V1.05

Behaviour of the new version
The EPL module checks at first the current bus status before the internal stack reset is executed by the 'error resetting' function. If the node is not in the 'Operational' status, it is started up again by an internal stack reset. If the node is in the 'Operational' status, the active error is only reset internally without executing an internal stack reset.



Which products are affected?
Communication module E94AYCEP Firmware V0.51

What happens?
The EPL master aborts the communication to the connected EPL slaves for a short period of time. The EPL slaves lose their synchronisation with the EPL master and change to the 'Warning locked' status. When the EPL master has been started up again, the communication is continued without problems.

When does the problem occur?
The communication module must be operated as EPL master (CN).
If the Engineer software or keypad is used to reset a communication error of an EPL master while the master is in 'Operational' mode, the module is restarted. As a result, the EPL communication is stopped/interrupted for a short period of time. The EPL master automatically changes back to the 'Operational' mode after the restart.

Possible diagnostics?
The behaviour described before may have occurred when the EPL slaves lose the synchronisation with the EPL master and a monitoring is triggered.

Short-term measures/recommendations?
In order to avoid mismatching application versions in case of an error, set the synchronisation monitoring to 'fault' by means of the EPL master in the EPL slaves under code C13891 or C14891.

Evaluation:
The current firmware version 1.05 of the EPL module checks at first the current bus status before the internal stack reset is executed by the 'error resetting' function. If the node is not in the 'Operational' status, it is started up again by an internal stack reset. If the node is in the 'Operational' status, the active error is only reset internally without executing an internal stack reset.

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