Terminal bus error – BECKHOFF BK3000 User Manual
Page 19

Basic information
BK3xxx/LC3100
19
Terminal bus error
Error code
Error code
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 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
(terminal n)
- Check programmed configuration for
correctness
- Incorrect table entry / bus coupler
3 pulses
0
Terminal bus command error
- No terminal connected; attach terminals.
- One of the terminals is defective; halve
the number of terminals attached and
check whether the error is still present with
the remaining terminals. Repeat until the
defective terminal is located.
4 pulses
0
n
Terminal bus data error
Break behind terminal n (0:
coupler)0
n
- Check whether the n+1 terminal is
correctly connected; replace if necessary.
– Check whether the end terminal 9010 is
connected.
5 pulses
n
Terminal bus error with register
communication with terminal n
Replace terminal n.
7 pulses
(BK3010,
BK3110, LC3100
only)
n
Analogue terminal inserted
n
th
terminal is an analogue
terminal
Remove n
th
terminal and switch the
coupler off and then on again.
Profibus configuration data errors: BK3000/BK3100
I/O-Err
Remedy
6 pulses
0
n (n>0)
Not enough DP-Cfg data received.
Faulty DP-Cfg data byte.
Check DP configuration.
8 pulses
0
n (n>0)
Not enough User-Prm data received
Faulty User-Prm data byte
Check DP user parameters.
Profibus configuration data errors:
BK3010/BK3110/BK3500
DIA
Remedy
1 pulse
0
n (n>0)
Not enough DP-Cfg data received.
Faulty DP-Cfg data byte.
Check DP configuration.
2 pulses
0
n (n>0)
Not enough User-Prm data received
Faulty User-Prm data byte
Check DP user parameters.