Corrected from:
EtherCAT E94AYCET communication module FV 4.02
Response of the new version?
The 94xx EtherCAT module with a 4.02 firmware starts to the "Operational" state faultlessly with an EtherCAT operation of 2ms and with use of the DC function.
What happens?
When the EtherCAT master (controller) is started, it may happen that the 94xx EtherCAT module V3 &V2 does not change to the OP status.
When does the problem occur?
The problem may occur if the 94xx EtherCAT module is actuated in the DC slave mode (synchronised EtherCAT operating mode) and an EtherCAT bus cycle of 2ms is applied.
Which products are affected?
EtherCAT E94AYCET communication module FV 3.0 in connection with TA CiA 402
Controller 3200C
Panel Controller p500
Diagnostics options?
If the 94xx EtherCAT module does not change to the OP status when it is actuated in DC mode, the module reports the following EtherCAT messages back to the EtherCAT master (controller).
- Error when responding to the Init command failed. State change='SAFEOP to OP'.
- Slave reports error. AL status: 'SAFE OPERATIONAL' (0x14), AL status code: 'Synchronization error' (0x1A).
Short-term measures/recommendations?
None
Evaluation:
The error occurs directly when the controller is switched on or is restarted. It does not cause any undefined system situations, since the 94xx axes do not change to the OP status (setpoint and actual value processing). So far, the restriction has been detected in the context of internal tests of the Lenze controller releases 3.14 and 3.15. No tests were performed for older Lenze controller releases lower than 3.14.
So far, NO feedback with regard to this malfunction has been provided from the field!
