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
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
- Page 5 and 6: Table of contents 4.5.2. External o
- Page 7 and 8: Table of contents B. PROFIBUS hardw
- Page 9 and 10: 1. Purpose of PC Control 645-12M In
- Page 11 and 12: Introduction Advantages of decentra
- Page 13 and 14: Introduction VEBES VEBES, the netwo
- Page 15 and 16: 2. Reliability and safety Reliabili
- Page 17 and 18: Reliability / safety 2.4. Safety Ou
- Page 19 and 20: Reliability / safety 2.5. Electroma
- Page 21 and 22: 2.5.5. Protection against external
- Page 23 and 24: 3. Hardware Hardware 3.1. Design 17
- Page 25 and 26: Hardware 3.2.2.1. Uninterrupted swi
- Page 27 and 28: Hardware 3.4.2. Setting the reset t
- Page 29 and 30: Hardware 3.5. Interfaces 3.5.1. V.2
- Page 31 and 32: Hardware 3.6. Memory PC Control 645
- Page 33 and 34: Hardware 3.8.2. How to avoid addres
- Page 35 and 36: Hardware -- Activate the "Memory" o
- Page 37 and 38: Hardware To reserve a memory range
- Page 39 and 40: i n 0 2 4LV o g 0 2 4LV o Sa t da t
- Page 41 and 42: PC Control 645-12M used as PLC 4.1.
- Page 43 and 44: PC Control 645-12M used as PLC -- S
- Page 45 and 46: PC Control 645-12M used as PLC The
- Page 47 and 48: 4.2. Going online with KUBES PC Con
- Page 49 and 50: PC Control 645-12M used as PLC 4.2.
- Page 51 and 52: 4.3. Memory settings PC Control 645
- Page 53 and 54: 4.4. PLC working method PC Control
- Page 55: 4.5.1.1. Short description of local
- Page 59 and 60: PC Control 645-12M used as PLC 4.5.
- Page 61 and 62: 4.5.3.1. Status of PROFIBUS master
- Page 63 and 64: 4.5.3.2. PEaxx.yy: DP slave status
- Page 65 and 66: 4.6. Summary of commands PC Control
- Page 67 and 68: PC Control 645-12M used as PLC 4.6.
- Page 69 and 70: PC Control 645-12M used as PLC 4.6.
- Page 71 and 72: PC Control 645-12M used as PLC 4.6.
- Page 73 and 74: 4.6.4. Shift and rotation commands
- Page 75 and 76: PC Control 645-12M used as PLC 4.6.
- Page 77 and 78: PC Control 645-12M used as PLC 4.6.
- Page 79 and 80: 4.7. Types of operands PC Control 6
- Page 81 and 82: PC Control 645-12M used as PLC 4.8.
- Page 83 and 84: PC Control 645-12M on PROFIBUS 4.9.
- Page 85 and 86: PC Control 645-12M on PROFIBUS PROF
- Page 87 and 88: PC Control 645-12M on PROFIBUS 4.9.
- Page 89 and 90: 4.9.2.3.1. Choosing a station and g
- Page 91 and 92: 4.9.2.4. Service 7: activate/deacti
- Page 93 and 94: 4.9.2.6. Service 6: synchronise DP
- Page 95 and 96: PC Control 645-12M on PROFIBUS 4.9.
- Page 97 and 98: PC Control 645-12M on PROFIBUS ====
- Page 99 and 100: PC Control 645-12M on PROFIBUS ====
- Page 101 and 102: PC Control 645-12M on PROFIBUS ====
- Page 103 and 104: PC Control 645-12M on PROFIBUS ====
- Page 105 and 106: PC Control 645-12M on PROFIBUS ====
Operands<br />
4.5.1.2. Accumulator function test<br />
The built-in accumulator serves buffering remanent operands.<br />
It is possible to test its functions via the user program.<br />
With KUBES running, proceed as follows:<br />
1 Choose two free directly consecutive byte markers (e.g.<br />
BR15.14 and BR15.15).<br />
2 Input a bit pattern into these before the first start;<br />
suggestion: BR15.14=aa, BR15.15=55 (hexadecimal<br />
values)<br />
Call up the "Display address range" in online operation<br />
(command ^F5)<br />
3 Include a program at the beginning of your Organisation<br />
Module with the purpose of checking the bit pattern at<br />
every start. There are various possible reactions to errors.<br />
Program suggestion<br />
; Accumulator function test<br />
; ------------------<br />
ACCU_TST LD BR15.14 ; (remanent byte marker for accu test)<br />
CMPD $55AA ; bit pattern still exist?<br />
JP= START ; yes -> start program<br />
; Error and failure handling<br />
; for example:<br />
; - PLC reset (used in this case)<br />
; - increment one byte marker (for KUBES' dynamic display)<br />
; - have a (decentralised) output flash<br />
; - generate text for terminal display<br />
; - warning message on process visualisation screen<br />
; - message to other station(s) via PROFIBUS<br />
ERROR RESET ; reset PLC if accu discharged<br />
; Start user program<br />
; ----------------------<br />
START NOP<br />
4 - 18