Diagnostic LEDs
The Bus Terminal Controllers have status LEDs.
BC9050
LEDs for power supply diagnostics
LED (Power LEDs) | Meaning |
---|---|
Power LED Us off | Bus Coupler has no voltage 24 VDC |
Power LED Up off | No power supply 24 VDC connected at the power contacts |
LEDs for K-Bus diagnostics
LED (K-bus) | Meaning |
---|---|
K-bus RUN | on or flashing - K-bus running |
K-bus ERR | flashing (see error code) |
LEDs for Ethernet diagnosis
LED (Ethernet) | Meaning |
---|---|
LINK/ACT | on - LINK available, flashing - LINK available and communication |
ERROR | flashing - DHCP or BootP active. Waiting for an IP address |
COM | Communication with controller available |
LEDs for PLC diagnostics
LED (Ethernet) | Meaning |
---|---|
PLC | on - PLC running, flashing - cycle time is exceeded, off - cycle time exceeded permanently or PLC stopped |
TC/DC | on - TwinCAT configuration active, off - Default configuration active, flashing TwinCAT configuration faulty |
BC9120
LEDs for power supply diagnostics
LED (Power LEDs) | Meaning |
---|---|
Power LED Us off | Bus Coupler has no voltage 24 VDC |
Power LED Up off | No power supply 24 VDC connected at the power contacts |
LEDs for K-Bus diagnostics
LED (K-bus) | Meaning |
---|---|
K-bus RUN | on or flashing - K-bus running |
K-bus ERR | flashing (see error code) |
LEDs for Ethernet diagnosis
LED (Ethernet) | Meaning |
---|---|
LINK/ACT | on - LINK available, flashing - LINK available and communication |
10/100 Mbaud | on - 100 Mbaud, off - 10 Mbaud |
ERROR | flashing - DHCP or BootP active. Waiting for an IP address |
COM | Communication with controller available |
LEDs for PLC diagnostics
LED (Ethernet) | Meaning |
---|---|
PLC | on - PLC running, flashing - cycle time is exceeded, off - cycle time exceeded permanently or PLC stopped |
TC/DC | on - TwinCAT configuration active, off - Default configuration active, flashing TwinCAT configuration faulty |
Error codes for K-Bus diagnosis
Error | Error | Description | Remedy |
---|---|---|---|
- | flashing continuously | EMC problems |
|
1 | 0 | EEPROM checksum error | Enter factory settings with the KS2000 configuration software |
1 | Code buffer overflow | Insert fewer Bus Terminals. Too many entries in the table for the programmed configuration | |
2 | Unknown data type | Software update required for the Bus Coupler | |
2 | - | Reserve | - |
3 | 0 | K-bus command error |
|
4 | 0 | K-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 KL9010 Bus End Terminal is connected | |
5 | n | K-bus error in register communication with Bus Terminal n | Exchange the nth Bus Terminal |
6 | 0 | Error at initialization | Exchange Bus Coupler |
1 | Internal data error | Perform a hardware reset on the Bus Coupler (switch off and on again) | |
2 | DIP switch changed after a software reset | Perform a hardware reset on the Bus Coupler (switch off and on again) | |
3 | IP address already assigned | Check whether the IP address already exists in the network. | |
7 | 0 | Note: cycle time was exceeded | Warning: the set cycle time was exceeded. This indication (flashing LEDs) can only be cleared by booting the Bus Coupler again. |
9 | 0 | Checksum error in Flash program | Transmit program to the BC again |
1 | Incorrect or faulty library implemented | Remove the faulty library | |
10 | n | Bus Terminal n is not consistent with the configuration that existed when the boot project was created | Check the nth Bus Terminal. The boot project must be deleted if the insertion of an nth Bus Terminal is intentional. |
14 | 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 | 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 KS2000 configuration software |
16 | n | Length of the K-bus data is no longer correct | Start the Bus Coupler again. If the error occurs again, restore the manufacturers setting using the KS2000 configuration software |