Beckhoff BK3 0 Series, Документация

Страница: 70 / 90

Diagnostics and error handling
BK3xx0 70 Version: 4.3.0
Signaling the K-bus error
A K-bus error is indicated both on the I/O-ERR LED and in the DPV1 status message in the DP diagnostic
data [
}
64] (bytes 11-13).
Byte Bit Description
11 0 too many K-bus command errors
11 1 too many K-bus timeouts
11 2 too many K-bus receive errors
11 3 too many K-bus transmit errors
11 4 K-bus reset error
11 5 general K-bus error
12 0-7 K-bus error code
13 0-7 K-bus error argument
K-bus reset
A K-bus reset can be carried out manually by means of a DPV1 Write:
Slot number Index Byte Value
0 99 0 2
1 1
2 0
3 0
6.3.2 Terminal Diagnostics
If terminal diagnosis has been activated, then each channel of a complex terminals is examined to see
whether bit 6 in the status has changed (exceptions are the KL6001, KL6011 and KL6021, where the
relevant bit is bit 3), and whether the diagnostic bit of each channel of a digital terminal with diagnostics
(KL12x2 or KL22x2) has changed. If that is the case, the existence of new diagnostic data is reported to the
master, and two bytes of diagnostic information starting at byte 16 of each channel for which a diagnosis is
pending are inserted (see
Diagnostic data [ } 64] ).
Terminal diagnosis can be activated in the UserPrmData [
}
35] :
Byte Bit Value Description
7 1 1
bin
Terminal diagnosis is active
Digital terminal diagnosis
By default, the diagnostic bits for the digital terminals that have diagnosis (KL12x2 and KL22x2) are
transmitted cyclically in the process image. These terminals occupy 4 bits each in both the input and output
data. If terminal diagnosis is active, then UserPrmData can be used to specify that only the I/O data for the
digital terminals with diagnosis (KL12x2: 2 bit inputs, KL22x2: 4 bit outputs) is to be included in the cyclic
process image transfer:
Byte Bit Value Description
7 4 1
bin
Diagnostic data of digital terminals not in the cyclic process image
Real-time capacity of the diagnostic data
When making use of terminal diagnosis, it should always be borne in mind that the diagnostic data always
reaches the controller at least one cycle later, and that as a rule access also takes place through different
mechanisms from those used for cyclic process data. This means that process data can already be faulty,