Lenze EtherCAT Controller-based Automation - Manual (Page 193)

Lenze · Controller-based Automation · EtherCAT® Communication Manual · DMS 6.4 EN · 04/2014 · TD17
193
12 Diagnostics
12.6 System error messages
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
5733 ...: ecatSetTargetState - EtherCAT master could not be set to
"target state". The master is busy (timeout)
Time-out during status change ’Request’
5740 ...: Error 0x... when reading out the bus scan status Internal error: Internal bus scan failed.
5743 ...: Error 0x... during restart of the bus scan Internal error: Internal bus scan failed.
6200 ... (...): Configuration mismatch. VendorID check failed (0x... /
0x...)
Configured and current bus structure do not match. At the
indicated position, a slave with the following vendor ID is
expected (expected/current).
6201 ... (...): Configuration mismatch. ProductCode check failed (0x... /
0x...)
Configured and current bus structure do not match. At the
indicated position, a slave with the following vendor product
code is expected (expected/current).
6202 ... (...): Configuration mismatch. Revision check failed (0x... / 0x...) Configured and current bus structure do not match. At the
indicated position, a slave with the following revision is
expected (expected/current).
6203 ... (...): Configuration mismatch. VendorID check failed (0x... /
missing...)
Configured and current bus structure do not match. At the
indicated position, a slave with the following vendor ID is
expected (currently, there is no slave available here).
6204 ...: Configuration mismatch. Too many slaves after ’... (...)’ on the
bus. Identification 0x... / 0x... / 0x...)
Configured and current bus structure do not match. More slaves
than configured are connected to the bus. For the first odd slave,
vendor ID, product code and revision are indicated.
6212 ...: All slaves ’Operational’ again Information: Slaves reset from "Operational" state to a lower
state were set to "Operational" again (e.g. by means of
L_ETC_SetSlaveState())
6213 ...: Cyclical command WKC error (repeated ... times) One or several slaves do not process the commands of the cyclic
frames. Possible causes may e.g. be that slaves are no longer
available or were reset from the "Operational" status to a lower
status. Only the 1st, 10th, 100th, 1000th, 10000th, etc. error is
logged.
6214 ...: Frame response error (repeated ... times) Master did not receive transmitted EtherCAT frame with the
next bus cycle task call. Causes may be wiring errors, contact
problems, and an excessive cycle time load of the EtherCAT task.
6215 ...: Not all slaves ’Operational’ (repeated ... times) The master is in the "Operational" status and one or several
slaves are reset to a lower status. Only the 1st, 10th, 100th,
1000th, 10000th, etc. error is logged.
6216 ... (...): Emergency message overflow. Further emergency
messages are blocked
A slave repeatedly sends the same emergency message. After
receipt of five messages, this error message appears and further
emergency messages from the slave are no longer logged until
the status of the slave changes from "Init" to "Pre-Operational".
6220 ...: New configuration loaded Information: New IEC application with EtherCAT master was
loaded.
6221 ...: New configuration loaded. No slaves defined Information: New IEC application with EtherCAT master was
loaded. There are no slaves defined.
6222 ...: Master start failed. Configuration error Internal error: Master was not configured correctly.
6230 ...: Master start failed The master cannot be started. General message (no ’Bus
mismatch’, DC/DCM, cable problem). Observe previous
messages in the logbook!
6231 ...: Master start failed. Bus mismatch The master does not start due to a ’Bus mismatch’:
Configured and current bus structure do not match. Which slave
is not correct is logged shortly before this message.
6232 ...: Master start failed. EtherCAT cable not connected The master cannot be started because the Ethernet cable is not
connected (no link-up).
6233 ...: Master start failed. DC/DCM configuration Internal error: The master cannot be started because of a faulty
DC/DCM configuration.
6234 ...: Master start failed. Slaves cannot be set to Pre-Operational. The master cannot be started because of a slave error. Observe
previous messages (slave error) in the logbook!
6240 ...: Status change ’Operational’ failed (0x...) The master cannot be set to "Operational". General message,
none of the following errors. Observe previous messages in the
logbook!
6241 ...: Status change ’Operational’ failed. Master is not initialised Internal error: The master cannot be started because of a faulty
DC/DCM configuration.
6242 ...: Status change ’Operational’ failed. EtherCAT cable not
connected
The master cannot be set to "Operational" because the Ethernet
cable is not connected (no link-up).
6243 ...: Status change ’Operational’ failed. DCM is not in-sync The master cannot be set to "Operational" because the Ethernet
cable is not connected (no link-up).
6244 ...: Status change ’Operational’ failed. Times for bus cycle task
and DC are not identical
Internal error: The DC cycle time and the cycle time of the
EtherCAT bus cycle task are not identical.
Error no. Message text in the Lenze Controller logbook Description