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
PROFIBUS Operands messages 4.5.3. PROFIBUS messages Apart from updating the PROFIBUS process image, the ALI of PC Control 645-12M has a management functionality for specifc operand ranges that indicate the status of the DP master machine, ALI and the connections to the slaves. These are Status of PROFIBUS master: Slave status messages: Connection status: PFxx.yy PSaxx.yy PEaxx.yy The contents and significance of the operand ranges differ from the operands of the same name in Kuhnke controllers with transfer rates up to 500 kbit/s. If external operands are linked in a program (e.g. inputs of a Profi I/O 690E), it has to be taken special care of their validity. If, for example, the bus connection is interrupted the received value may no longer correspond to the real status of the input. In order to avoid wrong switching operations as a result we urgently recommend to carefully analyse the above-mentioned PROFIBUS messages in the program. For startup and testing, we recommend that you use KUBES' "Display single address" and "Display address range" options to make these messages visible. 4 - 22
4.5.3.1. Status of PROFIBUS master 4.5.3.1.1. PFa00.00: ALI status PC Control 645-12M used as PLC Status Description 0 No reset 1 Resetting 2 Reset successfully completed. Initialising the DP core. 3 ASPC2 reset failure. 7 8 9 DP core initialisation error. Possible cause: VEBES program error. ALI ok. ALI initialised and started the DP core. ALI will change its status only after controller hardware reset or if KUBES sends new PROFIBUS network data and starts the controller. Serious internal error. These failures must not occur during operation. Please contact Kuhnke's Service Dept. 4.5.3.1.2. PFa00.01: ALI error message Error Description 0 OK. 1 Wrong parameter. 2 Impossible. 3 Not enough memory. 4 DP core failure. 128 No mailbox available. 129 Initialisation data error. 131 No slave data record for a defined station. 4 - 23
- 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 and 56: 4.5.1.1. Short description of local
- Page 57 and 58: 4.5.2. External operands as process
- Page 59: PC Control 645-12M used as PLC 4.5.
- 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
4.5.3.1. Status of PROFIBUS master<br />
4.5.3.1.1. PFa00.00: ALI status<br />
<strong>PC</strong> <strong>Control</strong> <strong>645</strong>-<strong>12M</strong> used as PLC<br />
Status<br />
Description<br />
0 No reset<br />
1 Resetting<br />
2 Reset successfully completed. Initialising the DP core.<br />
3 AS<strong>PC</strong>2 reset failure.<br />
7<br />
8<br />
9<br />
DP core initialisation error.<br />
Possible cause: VEBES program error.<br />
ALI ok. ALI initialised and started the DP core. ALI will change its<br />
status only after controller hardware reset or if KUBES sends new<br />
PROFIBUS network data and starts the controller.<br />
Serious internal error. These failures must not occur during<br />
operation. Please contact <strong>Kuhnke</strong>'s Service Dept.<br />
4.5.3.1.2. PFa00.01: ALI error message<br />
Error<br />
Description<br />
0 OK.<br />
1 Wrong parameter.<br />
2 Impossible.<br />
3 Not enough memory.<br />
4 DP core failure.<br />
128<br />
No mailbox available.<br />
129<br />
Initialisation data error.<br />
131<br />
No slave data record for a defined station.<br />
4 - 23