| Persistent, continuous blinking |
|
EMC problems |
- Check power supply for overvoltage or under voltage peaks
- Implement EMC measures
- If a EtherCAT Bus error is present, it can be localized by a restart of the coupler (by switching it off and then on again)
|
| 1 |
0 |
EEPROM checksum error
|
Set manufacturer’s setting with the configuration software |
| 1 |
Code buffer overflow |
Insert fewer Bus Terminals. The programmed configuration has too many entries in the table Software update required for the Bus Coupler |
| 2 |
Unknown data type |
Software update required for the Bus Coupler
|
| 2 Pulses |
0
|
Programmed configuration has an incorrect table entry |
Check programmed configuration for correctness |
|
n (n > 0) |
Table comparison (Bus Terminal n) |
Incorrect table entry |
| 3 Pulses |
0 |
EtherCAT Bus command error |
- No Bus Terminal inserted
- One of the Bus Terminals is defective; halve the number of Bus Terminals attached and check whether the error is still present with the remaining Bus Terminals. Repeat until the defective Bus Terminal is located.
|
| 4 Pulses |
0 |
EtherCAT Bus data error, break behind the Bus Coupler |
Check whether the n+1 Bus Terminal is correctly connected; replace if necessary. |
| n |
Break behind Bus Terminal n |
Check whether the Bus End Terminal is connected. |
| 5 Pulses |
n |
EtherCAT Bus error in register communication with Bus Terminal n |
Exchange the nth Bus Terminal |
| 14 Pulses |
n |
nth Bus Terminal has the wrong format |
Start the Bus Coupler again, and if the error occurs again then exchange the Bus Terminal |
| 15 Pulses |
n |
Number of Bus Terminals is no longer correct |
Start the Bus Coupler again. If the error occurs again, restore the manufacturers setting using the configuration software |
| 16 Pulses |
n |
Length of the EtherCAT Bus data is no longer correct |
Start the Bus Coupler again. If the error occurs again, restore the manufacturers setting using the configuration software |