Diagnostic LEDs
The Bus Coupler has two groups of LEDs for the display of status. The "DIAG LEDs" on the left indicate the fieldbus, PLC and K-Bus state. Two green LEDs (Power LEDs) are located in the top right corner of the Bus Coupler. They are used for displaying the supply voltage of the BX Controller and the 24 VDC supply of the power contacts.
LEDs for power supply diagnostics
LED (Power LEDs) |
Meaning |
---|---|
Left LED off |
Bus Coupler has no voltage 24 VDC |
Right LED off |
No power supply 24 VDC connected at the power contacts |
The DIAG LEDs are sub-divided as follows:
- Bus: Fieldbus diagnosis
- PLC: PLC diagnosis
- I/O: K-bus diagnosis
The LEDs can be off, green, orange or red.
After switching on, the Bus Coupler immediately checks the connected configuration. The I/O LED goes out if the start-up was successful. A red I/O LED indicates a Bus Terminal error. The error type is shown in the display. This permits rapid rectification of the error.
LED bus - fieldbus diagnosis
LED |
Meaning |
---|---|
LED off |
no fieldbus connected, Bus Coupler searches for baud rate |
LED red |
error flashing - error type - display |
LED orange |
Bus Coupler has found baud rate, waiting for config and parameter data |
LED green |
Bus communication OK, BX Controller is exchanging data |
LED PLC - PLC diagnosis
LED |
Meaning |
---|---|
LED off |
PLC stop or no program available |
LED red |
Flashing - the set task time is exceeded from time to time |
LED orange |
PLC running without boot project (only during the on cycle), LED flashes orange during creating of the boot project |
LED green |
Boot project - PLC running (only during the on cycle) |
LED I/O - K-Bus diagnosis
LED |
Meaning |
---|---|
LED off |
No data are exchanged via the K-Bus |
LED red |
error flashing - error type - display |
LED orange |
Register or KS2000 online access |
LED green |
K-Bus OK and running |
Error codes for K-Bus diagnosis
Error |
Error |
Description |
Remedy |
---|---|---|---|
0 |
- |
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 BX Controller | |
2 |
- |
Reserve |
- |
3 |
0 |
K-bus command error |
|
4 |
0 |
K-Bus data error, break behind the BX Controller |
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 KL9010 is connected. | |
5 |
n |
K-bus error in register communication with Bus Terminal n |
Exchange the nth bus terminal |
6 |
0 |
Error at initialization |
Replace the BX controller |
1 |
Internal data error |
Hardware reset of the BX controller (switching off and on again) | |
2 |
DIP switch changed after a software reset |
Hardware reset of the BX controller (switching off and on again) | |
3 |
IP address collision |
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 BX Controller again. |
9 |
0 |
Checksum error in Flash program |
Transfer the program to the BX controller 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 BX Controller again, and if the error occurs again then exchange the Bus Terminal. |
15 |
n |
Number of Bus Terminals is no longer correct |
Restart the BX controller. If the error occurs again, reset the BX controller to the delivery state with the configuration software. |
16 |
n |
Length of the K-bus data is no longer correct |