Diagnostics and error handling
BK3xx0
64
Version: 4.3.0
Error code
Error code argu-
ment
Description
Remedy
9 pulses
0
Checksum error in program
flash memory
Set manufacturer's setting with the
KS2000
13 pulses
0
Runtime K-bus command error 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.
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 (bit
length) is no longer correct. n =
bit length after booting
17 pulses
n
Number of Bus Terminals is no
longer correct.
n = number of Bus Terminals
after booting
18 pulses
n
Bus Terminal identifier no
longer correct after reset (n =
Bus Terminal number).
Error location
The number of pulses 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.
6.2
DP diagnostics
6.2.1
DP Diagnostic Data (DiagData)
The DP diagnostic data consists of six bytes of DP standard diagnosis, along with up to 238 bytes of device-
specific diagnostic data. The device-specific diagnostic data for Beckhoff slaves is represented in the DPV1
status message.
When the DP diagnostic data changes, the slave reports this fact to the master, and the master will
automatically fetch the changed diagnostic data. This means that DP diagnostic data is not included in the
DP process data in real-time, but is always sent to the controller a few cycles later.
In TwinCAT the DP diagnostic data is read from the DP Master interface (FC310x, CX1500-M310) using
ADS (see the section describing Slave Diagnosis in the FC310x documentation).
