K-bus interruption
If the K-bus is interrupted, or suffers from a relatively long malfunction, the coupler enters the K-bus error state. Depending on the setting made for Reaction to K-Bus error in the UserPrmData, the coupler abandons DP data exchange and sets the Stat_Diag bit in the diagnostic data at the next DP start-up (with the consequence that DP data exchange is not carried out), sets the DP inputs to 0, or leaves the DP inputs unchanged.
Byte | Bit | Value | Description |
|---|---|---|---|
10 | 2-3 | 00bin | Reaction to K-bus error: DP data exchange is abandoned (default) |
01bin | Reaction to K-bus error: DP inputs set to 0 | ||
10bin | Reaction to K-bus error: DP inputs remain unchanged |
When the interruption or malfunction on the K-bus has been rectified, the setting of Response to K-bus error in the UserPrmData determines whether the K-bus error state is left manually (by means of a K-bus reset), or automatically:
Byte | Bit | Value | Description |
|---|---|---|---|
7 | 0 | 0bin | Response to K-bus error: manual K-bus reset (default) |
1bin | Response to K-bus error: automatic K-bus reset |
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 (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 |