Lenze E84AYCET EtherCAT MCI module - Manual (Page 94)

12 Error messages
12.2 Possible causes and remedies
94
Lenze · E84AYCET communication module (EtherCAT) · Communication Manual · DMS 5.0 EN · 05/2013 · TD17
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Internal error [0x01bc6011]
Internal error [0x01bc6100]
Internal error [0x01bc6101]
Invalid parameter set [0x01bc641f]
Error: Lenze setting loaded [0x01bc6420]
Invalid module configuration [0x01bc6430]
Response (Lenze setting printed in bold) Setting: not possible
None System fault : Fault Trouble Quick stop by trouble Warning locked Warning Information
Cause Remedy
Communication module is defective. Send communication module with error description to
Lenze.
Response (Lenze setting printed in bold) Setting: not possible
None System fault : Fault Trouble Quick stop by trouble Warning locked Warning Information
Cause Remedy
Communication module is defective. Send communication module with error description to
Lenze.
Response (Lenze setting printed in bold) Setting: not possible
None System fault : Fault Trouble Quick stop by trouble Warning locked Warning Information
Cause Remedy
Communication module is defective. Send communication module with error description to
Lenze.
Response (Lenze setting printed in bold) Setting: not possible
None System fault : Fault Trouble Quick stop by trouble Warning locked Warning Information
Cause Remedy
No active parameter set could be loaded. Repeat download of the application (including module).
Response (Lenze setting printed in bold) Setting: not possible
None System fault : Fault Trouble Quick stop by trouble Warning locked Warning Information
Cause Remedy
Access via standard device to parameter set within the
memory module was not successful.
Repeat download of the application (including module).
Response (Lenze setting printed in bold) Setting: not possible
: None System fault Fault Trouble Quick stop by trouble Warning locked Warning Information
Cause Remedy
• Faulty module configuration.
• Incorrect sync settings.
Check and correct module configuration/sync settings.