Diagnostic LEDs

A BX Controller has two groups of LEDs for status display:

On the top right of the BX controller there are two green power LEDs. These are provided for diagnostics of the power supply of the BX Controller and of the power contacts.
The DIAG LEDs are located above the navigation switch on the left. They indicate the state of the fieldbus, the PLC and the K-bus.

Diagnostic LEDs 1: — Diagnostic LEDs for the fieldbus, the PLC, the K-bus and the power supply units

POWER LEDs for diagnostics of power supply

Power LEDs	Meaning
Left LED off	BX Controller has no power supply
Right LED off	Power contacts has no power supply

DIAG LEDs

The DIAG LEDs are sub-divided as follows:
- Bus: fieldbus diagnostics
- PLC: PLC diagnostics
- I/O: K-bus diagnostics

The LEDs can be off, green, orange or red.

Diagnostic LEDs 2: — Diagnostic LEDs for the fieldbus, the PLC and the K-bus

After switching on, the BX Controller 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.

LEDs for fieldbus diagnostics

LED Bus	Meaning
off	no fieldbus connected
red illuminated	no fieldbus connected, DeviceNet 24 V missing, DeviceNet communication error - wrong baud rate, incorrect termination
flashes red	communication error, IO timeout - communication to DeviceNet master interrupted
flashes orange	Baud rate search active, no baud rate found
flashing green	communication with master not yet established
green illuminated	DeviceNet communication active

LED for PLC diagnostics

LED PLC	Meaning
off	PLC in stop or no program available
flashes red	The set task time is sometimes exceeded (see also Chapter Deactivating the LED for cycle time exceeding).
red illuminated	The set task time is always exceeded.
orange illuminated	PLC runs without boot project (only lights up during the cycle), when the boot project is generated, the LED flashes orange
green illuminated	Boot project - PLC is running (only lights up during cycle)

LED for K-bus diagnostics

LED I/O	Meaning
off	No data are exchanged via the K-bus
red illuminated	error flashing - error type - display
orange illuminated	Register or KS2000 online access
green illuminated	K-bus OK and running

Error code for K-bus diagnostics

Error code	Error code argument	Description	Remedy
0	-	EMC problems	Check power supply for undervoltage or overvoltage peaks Implement EMC measures If a K-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	Enter factory settings with the KS2000 configuration software
	1	Code buffer overflow	Insert fewer Bus Terminals. The programmed configuration has too many entries in the table
	2	Unknown data type	Software update required for the BX Controller
2	-	reserved	-
3	0	K-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	0	K-bus data error, break behind the BX Controller	Check whether the n+1 Bus Terminal is correctly connected; replace if necessary.
4	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	Replace BX Controller
	1	Internal data error	Perform a hardware reset on the BX Controller (switch off and on again)
	2	DIP switch changed after a software reset	Perform a hardware reset on the BX Controller (switch off and on again)
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. Remedy: increase the cycle time
9	0	Checksum error in Flash program	Transmit program to the BX again
9	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	Start the BX Controller 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 BX Controller again. If the error occurs again, restore the manufacturers setting using the KS2000 configuration software