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 4.10.4. Checksum in user program (failure #8) During program generation, a checksum (CS) is generated over the entire user program memory according to a certain algorithm. Cause Reaction Notificatoin Remedy When starting the controller, the monitor re-calculates the checksum and compares it to the stored value. If the result is inequal, the monitor recognises a failure. -- the controller will not start -- error byte "ERR00.00" will be set to 8 -- find and remove the cause of the failure -- use the Transmit command of the KUBES PLC menu to tansmit the project again to the controller 4 - 74
4.10.5. Hierarchy error (failure #9) PC Control 645-12M used as PLC Program calls and other module calls must not exceed certain hierarchy limits (see chapter "3. Software modules" of programming manual E 417 GB). During programming, the controller reports a hierarchy error when it receives a program. At this stage, this is only a warning that there could be an error. Only at start-up does the controller check whether there really is a hierarchy error. If there is not, the error indication disappears again. Cause Reaction Indication Remedy When switching the controller on or after the KUBES start command, the monitor program checks whether there is a hierarchy error (a module calls up the module by which itself was called up or the nesting depth exceeds 5 levels) -- the controller will not start -- "failure" LED flashes (if exists) -- error byte "ERR00.00" will be set to 9 -- find and remove the cause of the error -- use the Transmit command of the KUBES PLC menu to tansmit the project again to the controller 4 - 75
- 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 and 110: 4.10.2. Undervoltage (supply, failu
- Page 111: PC Control 645-12M used as PLC 4.10
- 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
4.10.5. Hierarchy error (failure #9)<br />
<strong>PC</strong> <strong>Control</strong> <strong>645</strong>-<strong>12M</strong> used as PLC<br />
Program calls and other module calls must not exceed certain<br />
hierarchy limits (see chapter "3. Software modules" of<br />
programming manual E 417 GB).<br />
During programming, the controller reports a hierarchy error<br />
when it receives a program. At this stage, this is only a<br />
warning that there could be an error. Only at start-up does<br />
the controller check whether there really is a hierarchy error.<br />
If there is not, the error indication disappears again.<br />
Cause<br />
Reaction<br />
Indication<br />
Remedy<br />
When switching the controller on or after the KUBES start<br />
command, the monitor program checks whether there is a<br />
hierarchy error (a module calls up the module by which itself<br />
was called up or the nesting depth exceeds 5 levels)<br />
-- the controller will not start<br />
-- "failure" LED flashes (if exists)<br />
-- error byte "ERR00.00" will be set to 9<br />
-- find and remove the cause of the error<br />
-- use the Transmit command of the KUBES PLC menu to<br />
tansmit the project again to the controller<br />
4 - 75