Annex – BECKHOFF BK4000 User Manual
Page 24

Annex
24
BK4000
Annex
Example: combination of a process image
in the bus coupler
An example explains the affiliations of the input and output channels to the
process image. Our example setup should consist of the following bus
terminal modules:
In this configuration, the
Position
Function module on the busbar
bus coupler creates the
POS00
Bus coupler
allocation list that
POS01
Digital inputs, 2 channels
follows below
POS02
Digital inputs, 2 channels
POS03
Digital inputs, 2 channels
POS04
Digital inputs, 2 channels
POS05
Digital inputs, 2 channels
POS06
Digital inputs, 2 channels
POS07
Digital outputs, 2 channels
POS08
Digital outputs, 2 channels
POS09
Digital outputs, 2 channels
POS10
Analog inputs, 2 channels
POS11
Analog outputs, 2 channels
POS12
Analog outputs, 2 channels
POS13
Analog inputs, 2 channels
POS14
Infeed terminal
POS15
Digital inputs, 2 channels
POS16
Digital inputs, 2 channels
POS17
Digital inputs, 2 channels
POS18
Digital outputs, 2 channels
POS19
Digital outputs, 2 channels
POS20
Analog outputs, 2 channels
POS21
End terminal
By default, InterBus, DeviceNet and Profibus couplers only map signal
channels of 16-bits width. The CONTROL/STATUS BYTE is not available.
That is to say, an analog input terminal with 2 channels, for example, ap-
pears in the process image with 2 x 16 bits. The figures showing the byte
addresses and the affiliations differ correspondingly when CON-
TROL/STATUS is activated.
Part for byte-oriented data,
analog outputs
relative
byte address
Bit position
Process image in
the controller
Position in the
block
0, 1
none
A0, A1
POS11
2, 3
none
A2, A3
POS11
4, 5
none
A4, A5
POS12
6, 7,
none
A6, A7
POS12
8, 9
none
A8, A9
POS20
10, 11
none
A10, A11
POS20