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
PLC error and failure handling 2nd stage 1st alternative Cause Reaction Supply voltage rises back to 24 V DC ± 20% -- "failure" LED will extinguish -- error byte "ERR00.00" will be reset -- the program run will be continued without interruption 2nd alternative Cause Supply voltage continues to fall, c. < 8.5 V Reaction 5 V system voltage will be interrupted => - STOP: the program run will be stopped - RESET: outputs, error byte (ERR00.00) and -- unbuffered markers, timers and counters will be reset - all LEDs off Remedy -- as a precaution, in the user program, to save buffered operands: Processing of the user program should be interrupted until the 2nd stage of the cause has been reached or until a realistic delay period has elapsed. program example for interrupt module no. 17: WAIT 5 ;wait 5 * 10 ms=50 ms L ERR00.00 ;scan error byte CMP 2 ;still undervoltage? JP RETURN ; jump if not RETURN WAIT 5 ;wait for 5*10ms=50ms CMP 2 ;still undervoltage? RESET ; RESET and Stop PLC NOP 4 - 72
PC Control 645-12M used as PLC 4.10.3. Watchdog (program runtime exceeded, failure #3) Cause Indication Reaction Remedy -- runtime of a module > 50...70 ms or -- runtime of the overall program > 2 s -- "failure" LED flashes (if exists) -- KUBES outputs failure message in plain text -- STOP: program run will be stopped -- RESET: outputs and unbuffered markers, timers and counters will be reset -- external outputs (PROFIBUS) off -- change the program architecture to achieve shorter run times -- restart the controller: by hardware: switch supply off and back on again, or by software: KUBES RESET command followed by the RUN command 4 - 73
- 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 ====
- Page 107 and 108: PC Control 645-12M used as PLC 4.10
- Page 109: 4.10.2. Undervoltage (supply, failu
- Page 113 and 114: 4.10.5. Hierarchy error (failure #9
- Page 115 and 116: A. Specifications Specifications A.
- Page 117 and 118: Specifications A.2. Order specifica
- Page 119 and 120: PROFIBUS hardware installation B. P
- Page 121 and 122: PROFIBUS hardware installation B.1.
- Page 123 and 124: PROFIBUS hardware installation B.2.
- Page 125 and 126: PROFIBUS hardware installation B.2.
- Page 127 and 128: PROFIBUS hardware installation Acti
- Page 129 and 130: Index A accumulator 3-9 functional
- Page 131 and 132: Index memory range 3-4 in DOS and W
<strong>PC</strong> <strong>Control</strong> <strong>645</strong>-<strong>12M</strong> used as PLC<br />
4.10.3. Watchdog (program runtime exceeded, failure #3)<br />
Cause<br />
Indication<br />
Reaction<br />
Remedy<br />
-- runtime of a module > 50...70 ms<br />
or<br />
-- runtime of the overall program > 2 s<br />
-- "failure" LED flashes (if exists)<br />
-- KUBES outputs failure message in plain text<br />
-- STOP: program run will be stopped<br />
-- RESET: outputs and unbuffered markers, timers and<br />
counters will be reset<br />
-- external outputs (PROFIBUS) off<br />
-- change the program architecture to achieve shorter run<br />
times<br />
-- restart the controller:<br />
by hardware: switch supply off and back on again,<br />
or<br />
by software: KUBES RESET command followed by the<br />
RUN command<br />
4 - 73