BECKHOFF BC7300 - Manual (Page 17)

Basic Principles
BC7300 17
The error is encoded in the blinks as follows:
Fast blinking Start of the error code
First slow sequence Error code
Blink code
Second slow sequence Error code argument
Start of the error code Error type Error location
Error code Error
argument Description Remedy
Persistent,
continuous
blinking EMC problems - Check power supply for overvoltage or
undervoltage peaks
- Implement EMC measures
- If a K-Bus error is present, it can be
localised by a restart of the coupler (by
switching it off and then on again)
1 pulse 0
1
2 EEPROM checksum error
Inline code buffer overflow
Unknown data type - Set manufacturer’s setting with the KS2000
- Connect fewer Bus Terminals; too many
entries in the table for the programmed
configuration
- Software update required for the coupler
2 pulses 0
n (n > 0) Programmed configuration
Incorrect table entry / Bus Coupler
Incorrect table comparison (Bus
Terminal n) - Check programmed configuration for
correctness
- Incorrect table entry / Bus Coupler
3 pulses 0 K-Bus command error - No Bus Terminal connected; attach Bus
Terminals.
- 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
n K-Bus data error
Break behind Bus Terminal n (0:
coupler) - Check whether the n+1 Bus Terminal is
correctly connected; replace if necessary.
– Check whether the Bus End Terminal 9010
is connected.
5 pulses n K-Bus error with register
communication with Bus Terminal n
Exchange Bus Terminals
9 pulses 0
n (n>0) Checksum error in program flash
memory
Bus Terminal n is not consistent with
the configuration that existed at boot
image entry Transmit program to the BC7300 again
Check the n
th
Bus Terminal. If a new Bus
Terminal is to be inserted, delete the boot
project (manufacturer's setting)
14 pulses n Bus Terminal n has the wrong format - Start the 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 coupler again, and if the error
occurs again after this, use the KS2000
software to set manufacturer’s settings
16 pulses n Length of the K-Bus data is no longer
correct - Start the coupler again, and if the error
occurs again after this, use the KS2000
software to set manufacturer’s settings
The number of pulses (n) indicates the position of the last Bus Terminal
before the fault. Passive Bus Terminals, such as a power feed terminal, are
not included in the count.
In the case of some errors, rectification does not cause the Bus Coupler to
leave the blink sequence. The Bus Coupler stays in the "Stop" state. The
Bus Coupler can only be re-started either by switching the power supply off
and on again, or by a software reset.
Insertion and removal of Bus Terminals is only permitted when switched