Lenze EtherCAT control technology - Manual (Page 157)

DMS 3.1 EN 01/2011 TD17
L
157
Control technology | EtherCAT communication manual
Diagnostics
System error messages
11.7 System error messages
For system error messages, the following error types are distinguished:
11.7.1 IPC logbook messages
IPC logbook messages are indicated as errors, warnings, or information.
Error type Abbr. Description
Application error CTRL Internal error in the application operating the master.
• E.g. an API function has been called with invalid parameters.
Project error PRJ The XML file of the master does not correspond to the slaves.
• E.g. not all slaves included in the XML file have been detected during
the bus scan.
Configuration error (master) CFG Faulty or insufficient configuration of the master.
• E.g. mailbox command queue too small.
Bus/slave error SLV Error cause by slave
• E.g. "Working Counter Error"
Link layer error LLA Error in the link layer (network driver).
• E.g. the Intel Pro 1000 card could not be found.
• These are mostly internal errors.
Remote API error RAP Error in remote API
(The applications and engineering tools »EtherCAT OPC server«,
»EtherCAT Configurator«, »Engineer« use the remote API.)
• E.g. a connection between slave and master is not possible.
Internal software error ISW Internal master error
• E.g. the master state machine is in an invalid state.

Note!
The WKC error messages (highlighted in blue in the table) are entered into the
logbook when the error is detected for the first time and then cyclically every 5
seconds until 65535 messages have occurred or the error is not active anymore.
In the following table, "[...]" serves as a wildcard for addresses, indexes, message
types, error numbers, etc.
Error type Error text in the IPC logbook Description
CTRL Master state change from [...] to [...] State change of the master from [...] to [...]
CTRL Cyclic command time-out: Time between sending cyclic
commands too high
Time-out of cyclic commands:
The time between the transmission processes is too long.
LLA Retry sending a [...] frame due to [...] Retry to send a data frame
LLA [...] response on [...] Ethernet frame Response to an Ethernet frame
LLA Ethernet cable connected Ethernet cable is connected.
LLA Ethernet cable not connected Ethernet cable is not connected.
PRJ Cyclic command wrong size (too long) The process image seize in the EtherCAT master configuration
(ECAT_MASTER_1.XML) is too large (Example: 35 MB).
PRJ Invalid input offset in cyc cmd, please check InputOffs
PRJ Invalid output offset in cyc cmd, please check OutputOffs
SLV Scan Bus Succeeded, found [...] slaves Bus scan has been completed successfully.
[...] slaves were found.
SLV Scan Bus Error [...], found [...] slaves Bus scan error [...]
[...] slaves were found.
SLV Distributed Clocks status [...] ([...]) Distributed clocks status