PC Control / Profi Control 645-12M Instruction Manual pdf - Kuhnke

PC Control / Profi Control 645-12M Instruction Manual pdf - Kuhnke PC Control / Profi Control 645-12M Instruction Manual pdf - Kuhnke

28.03.2014 Views

Operands 4.5.1.2. Accumulator function test The built-in accumulator serves buffering remanent operands. It is possible to test its functions via the user program. With KUBES running, proceed as follows: 1 Choose two free directly consecutive byte markers (e.g. BR15.14 and BR15.15). 2 Input a bit pattern into these before the first start; suggestion: BR15.14=aa, BR15.15=55 (hexadecimal values) Call up the "Display address range" in online operation (command ^F5) 3 Include a program at the beginning of your Organisation Module with the purpose of checking the bit pattern at every start. There are various possible reactions to errors. Program suggestion ; Accumulator function test ; ------------------ ACCU_TST LD BR15.14 ; (remanent byte marker for accu test) CMPD $55AA ; bit pattern still exist? JP= START ; yes -> start program ; Error and failure handling ; for example: ; - PLC reset (used in this case) ; - increment one byte marker (for KUBES' dynamic display) ; - have a (decentralised) output flash ; - generate text for terminal display ; - warning message on process visualisation screen ; - message to other station(s) via PROFIBUS ERROR RESET ; reset PLC if accu discharged ; Start user program ; ---------------------- START NOP 4 - 18

4.5.2. External operands as process image PC Control 645-12M used as PLC External operands are read as inputs or controlled as outputs via PROFIBUS. There are various sources and destinations: - - decentralised input/output devices (e.g. Profi I/O 690E) - - other programmable logic controllers with a DP slave interface - - positioning controllers, etc. As a gate to PROFIBUS, there is a 7 kbyte RAM memory available to PC Control 645-12M for the external operands (3 kbyte bit-addressable, 4 kbyte byte-addressable). This memory represents the process image of the available external operands. VEBES creates a list of the external operands VEBES (see instruction manual E 315 GB, VEBES) is used for network configuration. This process creates projects for all participating Kuhnke masters which are then programmed / edited with the KUBES functionality. During network configuration with VEBES, the programmer determines the communication partners and the amount of communication objects (external operands). VEBES adds these external operands to the list of operands in the corresponding project and distributes them within the process image memory. During programming, they can then be addressed like local operands. It is also possible to use mnemonics in the symbol table. PROFIBUS updates the process image During operation, PROFIBUS automatically takes care of transmitting data between communication partners and process image as often as possible. As this is done at certain time intervals and controlled by interrupts, up-dating may also occur while a (program) module is being processed. This is why PROFIBUS process image data may be different at the beginning and the end of a module (see chapter "4.9.1. Data consistency by OC_CRIT"). This does not apply to interrupt and timer modules. 4 - 19

4.5.2. External operands as process image<br />

<strong>PC</strong> <strong>Control</strong> <strong>645</strong>-<strong>12M</strong> used as PLC<br />

External operands are read as inputs or controlled as outputs<br />

via PROFIBUS. There are various sources and destinations:<br />

- - decentralised input/output devices (e.g. <strong>Profi</strong> I/O 690E)<br />

- - other programmable logic controllers with a DP slave interface<br />

- - positioning controllers, etc.<br />

As a gate to PROFIBUS, there is a 7 kbyte RAM memory<br />

available to <strong>PC</strong> <strong>Control</strong> <strong>645</strong>-<strong>12M</strong> for the external operands<br />

(3 kbyte bit-addressable, 4 kbyte byte-addressable).<br />

This memory represents the process image of the available<br />

external operands.<br />

VEBES creates a list of the external operands<br />

VEBES (see instruction manual E 315 GB, VEBES) is used<br />

for network configuration. This process creates projects for<br />

all participating <strong>Kuhnke</strong> masters which are then programmed<br />

/ edited with the KUBES functionality. During network<br />

configuration with VEBES, the programmer determines<br />

the communication partners and the amount of communication<br />

objects (external operands). VEBES adds these<br />

external operands to the list of operands in the corresponding<br />

project and distributes them within the process image<br />

memory. During programming, they can then be addressed<br />

like local operands. It is also possible to use mnemonics in<br />

the symbol table.<br />

PROFIBUS updates the process image<br />

During operation, PROFIBUS automatically takes care of<br />

transmitting data between communication partners and<br />

process image as often as possible. As this is done at certain<br />

time intervals and controlled by interrupts, up-dating<br />

may also occur while a (program) module is being processed.<br />

This is why PROFIBUS process image data may be different<br />

at the beginning and the end of a module (see chapter<br />

"4.9.1. Data consistency by OC_CRIT"). This does not apply<br />

to interrupt and timer modules.<br />

4 - 19

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!