Beckhoff BC9000 Documentation page 80

Bus terminal controller for ethernet
Table of Contents

Advertisement

Error handling and diagnosis
LEDs for K-bus diagnostics
Error code
Error code argu-
ment
Persistent, contin-
uous flashing
1 pulse
0
1
2
2 pulses
0
n (n > 0)
3 pulses
0
4 pulses
0
n
5 pulses
n
6 pulses
0
1
2
4
8
16
7 pulses
0
(BC9000/BC9100
only)
9 pulses
0
(BC9000/BC9100
1
only)
10 pulses
n
(BC9000/BC9100
only)
14 pulses
n
15 pulses
n
16 pulses
n
LEDs for switch diagnosis (BK9100/BC9100 only)
LED
on
LINK/ACT
Physical connection present
10 / 100 Mbit/
100 Mbit/s
s
80
Description
EMC problems
EEPROM checksum error
Code buffer overflow
Unknown data type
Programmed configuration has an incorrect
table entry
Table comparison (Bus Terminal n)
K-bus command error
K-bus data error, break behind the Bus
Coupler
Break behind Bus Terminal n
K-bus error in register communication with
Bus Terminal n
Error at initialization
Internal data error
DIP switch changed after software reset
from firmware BC9000 BB and BC9100 B0:
from firmware BK9000 BA and BK9100 B0:
IP address already exists in the network
DIP switch incorrect for BootP
Internal data error
Error in IP socket
Note: Cycle time was exceeded
(see Table 1 Register 17 [} 75])
Checksum error in Flash program
Incorrect or faulty library implemented
Bus Terminal n is not consistent with the
configuration that existed when the boot
project was created
nth Bus Terminal has the wrong format
Number of Bus Terminals is no longer cor-
rect
Length of the K-bus data is no longer cor-
rect
Flashes
Communication available
-
Version: 4.0.0
Remedy
• 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)
Enter factory settings with the KS2000 configura-
tion software
Insert fewer Bus Terminals. Too many entries in
the table for the programmed configuration
Software update required for the Bus Coupler
Check programmed configuration for correctness
Incorrect table entry
• 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.
Check whether the n+1 Bus Terminal is correctly
connected; replace if necessary
Check whether the bus end terminal 9010 is con-
nected
Exchange the nth Bus Terminal
Exchange Bus Coupler
Perform a hardware reset on the Bus Coupler
(switch off and on again)
Hardware reset of the Bus Coupler (switch off and
back on again)
Assign another IP address
Set 1-8 to on or off, see BootP [} 75]
Perform a hardware reset on the Bus Coupler
(switch off and on again)
Perform a hardware reset on the Bus Coupler
(switch off and on again)
Warning: the set cycle time was exceeded. This
note (flashing of the LED) can only be reset by re-
booting the BC.
Remedy: increase the cycle time
Transmit program to the BC again
Remove the faulty library
Check the nth Bus Terminal. The boot project must
be deleted if the insertion of an nth Bus Terminal is
intentional.
Start the Bus Coupler again, and if the error occurs
again then exchange the Bus Terminal.
Start the Bus Coupler again. If the error occurs
again, restore the manufacturers setting using the
KS2000 configuration software
Start the Bus Coupler again. If the error occurs
again, restore the manufacturers setting using the
KS2000 configuration software
off
No physical connection present
10 Mbit/s
BC9000 and BC9100

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

Bc9100

Table of Contents