Technical data

Linkage with PLC
182 VIPA GmbH CP486 ⋅ 00/14
6.4.5 Storage of Process Images to Bank 7
The process image can also be directly read out by the user. Following survey shows how bank 7 is
structured. Direct access is very fast:
Address in the
bank (hex)
Byte 0 process image EB 0 -+
.¦
. ¦ 128 byte PAE 0-127
.¦
Byte 127 process image EB 127 -+
Byte 128 process image AB 0 -+
.¦
. ¦ 128 byte PAA 0-127
.¦
Byte 255 process image AB 127 -+
Byte 256 marker Byte 0 -+
.¦
. ¦ 256 byte marker 0-255
.¦
Byte 511 marker Byte 255 -+
Byte 512/513 Timer 0 (high/low) -+
.¦
. ¦ 128 words timer 0-127
.¦
Byte 766/767 timer 127 (high/low) -+
Byte 768/769 counter 0 (high/low) -+
.¦
. ¦ 127 words counter 0-126
.¦
Byte 1020/1021 counter 126 (high/low)-+
Byte 1022 count byte 1) + count byte
Byte 1023 trigger interrupt on CP
Annotation:
All values of this bank are refreshed when the handling module CP L/S is called up (if this is
enabled on the formal operand of the handling module). After every data refreshing in the bank 7
the handling module increments the count byte by 1. CP recognizes by this count byte whether data
are valid and how often they have been refreshed since the last reading. Data are then valid when the
count byte content is involved in the range dual 1...255. iegt. In the case of overflow the count byte
starts again with 1.
The handling module Synchron sets the current counter, address 3FE in bank 7 to 0. By that the CP
recognizes that the data in bank 7 are not valid in the moment.
This bank needs not to be deleted by the CP if 0 is contained in the count byte (address 3FE of
bank).
This bank can only be write accessed by the handling module.
The handling module for refreshing data of bank 7 does not trigger any interrupt.