Terminal Composition
The terminal composition can be read by DPV1. A word is transmitted for each terminal containing the terminal number for complex terminals (KL15xx, KL25xx, KL3xxx, KL4xxx, KL5xxx, KL6xxx, KL8xxx), and the length and type information for digital terminals:
Bit | Value | Description |
|---|---|---|
0 | 1bin | Digital terminal has inputs |
1 | 1bin | Digital terminal has outputs |
2-7 | - | reserved |
8-14 | X | Length in bits |
15 | 1bin | Always 1bin (indicates that the terminal is digital) |
Reading the terminal composition
The terminal composition is represented in the DPV1 addressing as follows:
|
Slot number |
Index |
Byte |
Description |
|---|---|---|---|
|
0 |
9 |
0-1 |
Number of the Bus Coupler |
|
2-3 |
Value for terminal 1 | ||
|
... |
... | ||
|
46-47 |
Value for terminal 23 | ||
|
10 |
0-1 |
Value for terminal 24 | |
|
... |
... | ||
|
46-47 |
Value for terminal 47 | ||
|
11 |
0-1 |
Value for terminal 48 | |
|
... |
... |
... | |
|
18 |
46-47 |
Value for terminal 239 | |
|
19 |
0-1 |
Value for terminal 240 | |
|
... |
... | ||
|
30-31 |
Value for terminal 255 |
Checking the terminal composition
The same data can also be accessed by a DPV1 Write. In this case the Bus Coupler compares the value that has been written with the true value, returning a negative DPV1 Write response if the data does not agree. This permits more precise checking of the terminal configuration than is possible by checking the CfgData. The length must match the actual length of table 9. The calculation should include two bytes for each terminal with process data. The Bus Coupler ID in register 0 of table 9 is not taken into account.
Error codes in the write response
|
Error_Code_1 |
Error_Code_2 |
|---|---|
|
0xBE |
Number of terminals |
|
0xBF |
First faulty byte in the written data |