1. Manuals
  2. Brands
  3. Siemens Manuals
  4. Control Unit
  5. SIMATIC CPU 410
  6. System manual

Siemens SIMATIC CPU 410 System Manual

Process control system, process automation/cpu
Hide thumbs
1
2
Table Of Contents
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
Table of Contents

Advertisement

Quick Links

SIMATIC
PCS 7 process control system
CPU 410 Process Automation/CPU
410 SMART
System Manual
05/2017
A5E31622160-AC
___________________
Preface
___________________
Introduction to the CPU 410
___________________
Configuration of the CPU
410
___________________
PROFIBUS DP
___________________
PROFINET IO
___________________
I/O configuration variants
___________________
System and operating states
of the CPU 410
___________________
Link-up and update
___________________
Special functions of the CPU
410
___________________
Time synchronization and
time stamping
___________________
Plant changes in RUN - CiR
___________________
Plant changes during
redundant operation - H-CiR
___________
Replacement of failed
components during
redundant operation
___________________
Synchronization modules
___________________
System expansion card
___________________
Technical data
___________
Properties and technical
specifications of CPU 410
SMART
___________________
Supplementary information
___________
Characteristic values of
redundant automation
systems
___________
Function and communication
modules that can be used in
a redundant configuration
___________________
Connection examples for
redundant I/Os
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
A
B
C

Advertisement

Table of Contents
loading

Related Manuals for Siemens SIMATIC CPU 410

Summary of Contents for Siemens SIMATIC CPU 410

  • Page 1 ___________________ Preface ___________________ Introduction to the CPU 410 ___________________ Configuration of the CPU ___________________ SIMATIC PROFIBUS DP ___________________ PROFINET IO PCS 7 process control system ___________________ CPU 410 Process Automation/CPU I/O configuration variants 410 SMART ___________________ System and operating states of the CPU 410 ___________________ Link-up and update...
  • Page 2 Note the following: WARNING Siemens products may only be used for the applications described in the catalog and in the relevant technical documentation. If products and components from other manufacturers are used, these must be recommended or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and maintenance are required to ensure that the products operate safely and without any problems.

  • Page 3: Table Of Contents

    Table of contents Preface ..............................17 Preface ............................ 17 Security information ........................ 20 Documentation ........................21 Introduction to the CPU 410 ........................23 Area of application of the CPU 410 in SIMATIC PCS 7 ............23 Possible applications ......................25 The CPU 410 basic system for stand-alone operation ............
  • Page 4 Table of contents Fail-safe operation ......................... 58 Fault-tolerant automation systems (redundancy operation) ..........61 6.3.1 Redundant SIMATIC automation systems ................61 6.3.2 Increase of plant availability, reaction to errors ..............62 Introduction to the I/O link to fault-tolerant system ..............65 Using single-channel switched I/O ..................
  • Page 5 Table of contents Special functions of the CPU 410 ......................133 Security functions of the CPU 410 ..................133 Security levels ........................134 Security event logging......................136 Field Interface Security ......................139 Access-protected blocks ....................... 139 Retentive load memory ......................140 Type update with interface change in RUN ................
  • Page 6 Table of contents 11.8.1 Basic Procedures in STOP Mode ..................172 11.8.1.1 Overview ..........................172 11.8.1.2 Defining CiR Elements ......................174 11.8.1.3 Deleting CiR Elements ......................176 11.8.2 Basic Procedure in RUN Mode .................... 177 11.8.2.1 Overview ..........................177 11.8.2.2 add slaves or modules ......................
  • Page 7 Table of contents 12.9 Removal of components ....................... 211 12.9.1 Change hardware configuration offline ................. 212 12.9.2 Modify and download the user program ................213 12.9.3 Opening the H-CiR wizard ....................214 12.9.4 Modify hardware ........................215 12.9.5 Removal of interface modules ....................216 12.10 Editing CPU parameters .......................
  • Page 8 Table of contents 17.3 Technical specifications of the SEC PO 800 ............... 295 Supplementary information ........................297 18.1 Supplementary information on PROFIBUS DP ..............297 18.2 Supplementary information on diagnostics of the CPU 410 as PROFIBUS DP master ..298 18.3 System status lists for PROFINET IO ..................
  • Page 9 Table of contents 18.15 Other options for connecting redundant I/Os ................ 354 18.16 CPU 410 cycle and reaction times ..................357 18.16.1 Cycle time ..........................357 18.16.2 Calculating the cycle time ..................... 359 18.16.3 Cycle load due to communication ..................362 18.16.4 Response time ........................
  • Page 10 Table of contents C.20 SM 322; DO 8 x AC 230 V/2 A, 6ES7 322–1FF01–0AA0 ............ 410 C.21 SM 322; DO 4 x DC 24 V/10 mA [EEx ib], 6ES7 322–5SD00–0AB0 ........411 C.22 SM 322; DO 4 x DC 15 V/20 mA [EEx ib], 6ES7 322–5RD00–0AB0 ........412 C.23 SM 322;...
  • Page 11 Table of contents Table 6- 5 Interface module for use of single-channel switched I/O configuration at the PROFINET IO interface ........................... 71 Table 6- 6 Signal modules for redundancy ....................84 Table 7- 1 Causes of error leading to redundancy loss ................102 Table 7- 2 Overview of system states of the fault-tolerant system .............
  • Page 12 Table of contents Table 18- 17 Direct access of the CPUs to I/O modules in the expansion unit with remote link, setting 100 m ............................369 Table 18- 18 Example of calculating the response time ................. 370 Table 18- 19 Hardware and interrupt response times;...
  • Page 13 Table of contents Figure 6-19 Fault-tolerant analog output modules in 1-out-of-2 configuration ..........95 Figure 7-1 Synchronizing the subsystems ....................108 Figure 8-1 Meanings of the times relevant for updates ................122 Figure 8-2 Correlation between the minimum I/O retention time and the maximum inhibit time for priority classes >...
  • Page 14 Table of contents Figure 18-24 Example of minimum signal duration of an input signal during the update ....... 346 Figure 18-25 Redundant one-sided and switched I/O ..................354 Figure 18-26 Flow chart for OB 1 ........................356 Figure 18-27 Elements and composition of the cycle time ................358 Figure 18-28 Formula: Influence of communication load ................
  • Page 15 Table of contents Figure C-23 Example of an interconnection with SM 332, AO 8 x 12 Bit ............415 Figure C-24 Example of an interconnection with SM 332; AO 4 x 0/4...20 mA [EEx ib] ....... 416 Figure C-25 Example of an interconnection with SM 422; DO 16 x 120/230 V/2 A ........417 Figure C-26 Example of an interconnection with SM 422;...
  • Page 16 Table of contents CPU 410 Process Automation/CPU 410 SMART System Manual, 05/2017, A5E31622160-AC...

  • Page 17: Preface

    Preface Preface Purpose of this manual The information in this manual enables you to look up operator inputs, function descriptions and technical specifications of the CPU 410-5H Process Automation, CPU 410E Process Automation and CPU 410 SMART. For information on installing and wiring this and other modules in order to set up an Automation System S7-400, Hardware and Installation automation system, refer to Manual Changes compared with the previous version...
  • Page 18 Preface 1.1 Preface Use of the current version of PCS 7 or the engineering tools is only required if the current CPU has new functions compared to the last firmware version and you want to use these functions. The same applies when an old CPU is replaced by a CPU with current firmware: If you do not want to use any properties beyond the scope of the replaced CPU, you can use the CPU with the old article number and old firmware version when configuring in HW Config.
  • Page 19 If you have any questions relating to the products described in this manual, and do not find the answers in this documentation, please contact your Siemens partner at our local offices. You will find information on who to contact at: Contact partners (http://www.siemens.com/automation/partner)

  • Page 20: Security Information

    In order to protect plants, systems, machines and networks against cyber threats, it is necessary to implement – and continuously maintain – a holistic, state-of-the-art industrial security concept. Siemens’ products and solutions only form one element of such a concept. Customer is responsible to prevent unauthorized access to its plants, systems, machines and networks.

  • Page 21: Documentation

    Preface 1.3 Documentation To stay informed about product updates, subscribe to the Siemens Industrial Security RSS Feed under http://www.siemens.com/industrialsecurity. Documentation User documentation The table below provides an overview of the descriptions of the various components and options in the S7-400 automation system.
  • Page 22 0/en) Solution concepts SIMATIC PCS 7 Technical Doc- SIMATIC PCS 7 Process Con- Function mechanisms umentation trol System Configurations of SIMATIC PCS (http://www.automation.siemenh ttps://support.industry.siemens.c om/cs/ww/en/view/59538371s.c om/mcms/industrial-automation- systems- simat- ic/en/handbuchuebersicht/tech- dok-pcs7/Seiten/Default.aspx) Configuring hardware Configuring Hardware and Configuring Hardware and Communication Connections...

  • Page 23: Introduction To The Cpu 410

    F systems. You can find information on this in following manual: SIMATIC Industrial Software S7 F/FH Systems (http://support.automation.siemens.com/WW/view/en/2201072) Why use fault-tolerant automation systems? The purpose of fault-tolerance automation systems is to reduce production downtime caused by faults or by maintenance work.
  • Page 24 Introduction to the CPU 410 2.1 Area of application of the CPU 410 in SIMATIC PCS 7 SIMATIC PCS 7 and CPU 410-5H Process Automation SIMATIC PCS 7 uses selected standard hardware and software components from the TIA building block system for the process control system in the company-wide automation network called Totally Integrated Automation.

  • Page 25: Possible Applications

    Introduction to the CPU 410 2.2 Possible applications Important information on configuration WARNING Open equipment Risk of death or serious injury. S7–400 modules are classified as open equipment, meaning you must install the S7–400 in an enclosure, cabinet, or switch room that can only be accessed by means of a key or tool. Only instructed or authorized personnel are permitted to access these enclosures, cabinets, or switch rooms.

  • Page 26: Figure 2-2 Overview

    Introduction to the CPU 410 2.2 Possible applications Figure 2-2 Overview Additional information The components of the S7–400 standard system are also used in connection with the CPU 410-5H Process Automation. For a detailed description of all hardware components for S7- S7-400 Automation System;...

  • Page 27: The Cpu 410 Basic System For Stand-Alone Operation

    Introduction to the CPU 410 2.3 The CPU 410 basic system for stand-alone operation The CPU 410 basic system for stand-alone operation Definition Stand-alone operation refers to the use of a CPU 410 in a standard SIMATIC-400 station. Note Rack number "0" must be set on the CPU. Hardware of the basic system The basic system consists of the required hardware components of a controller.

  • Page 28: The Basic System For Redundant Operation

    Introduction to the CPU 410 2.4 The basic system for redundant operation Operation You need a system expansion card for operation of a CPU 410. The system expansion card specifies the maximum number of process objects that can be loaded to the CPU and saves the license information in case of a system expansion.
  • Page 29 Introduction to the CPU 410 2.4 The basic system for redundant operation Power supply You require a power supply module from the standard system range of the S7-400 for each of the two subsystems of the S7-400H. To increase availability of the power supply, you can also use two redundant power supplies in each subsystem.

  • Page 30: Rules For H Station Assembly

    Introduction to the CPU 410 2.5 Rules for H station assembly Rules for H station assembly The following rules have to be complied with for a fault-tolerant station, in addition to the rules that generally apply to the arrangement of modules in the S7-400: ●...

  • Page 31: I/O Configuration Variants Of The Fault-Tolerant System

    Introduction to the CPU 410 2.7 I/O configuration variants of the fault-tolerant system I/O configuration variants of the fault-tolerant system I/O configuration variants The following configuration variants are available for the input/output modules: ● In stand-alone operation: one-sided configuration. In the one-sided configuration, there is a single set of the input/output modules (single- channel) that are addressed by the CPU.

  • Page 32: Scaling And Licensing (Scaling Concept)

    Introduction to the CPU 410 2.9 The SIMATIC PCS 7 project You can protect function blocks (FBs) and functions (FCs) against unauthorized access using the S7 Block Privacy application. You can no longer edit protected blocks in STEP 7. Only the interfaces of the blocks are then visible. If you protect blocks with S7 Block Privacy, you may encounter longer download and startup times.
  • Page 33 Introduction to the CPU 410 2.9 The SIMATIC PCS 7 project Expanding the number of POs without replacing the SEC You can expand the number of POs in four steps without replacing the SEC. Step 1: Order the number CPU 410 expansion packs you need using the regular ordering process.
  • Page 34 Introduction to the CPU 410 2.9 The SIMATIC PCS 7 project CPU 410 Process Automation/CPU 410 SMART System Manual, 05/2017, A5E31622160-AC...

  • Page 35: Configuration Of The Cpu 410

    Configuration of the CPU 410 Operator controls and indicators on the CPU 410 Arrangement of the operator controls and indicators on the CPU 410 Figure 3-1 Arrangement of the operator controls and indicators on the CPU 410 CPU 410 Process Automation/CPU 410 SMART System Manual, 05/2017, A5E31622160-AC...

  • Page 36: Table 3- 1 Led Displays On The Cpus

    Configuration of the CPU 410 3.1 Operator controls and indicators on the CPU 410 LED displays The following table gives an overview of the available LED displays. Sections CPU 410 monitoring functions (Page 39) and Status and error displays (Page 41) describe the states and errors/faults indicated by these LEDs. Table 3- 1 LED displays on the CPUs LED display...
  • Page 37 Configuration of the CPU 410 3.1 Operator controls and indicators on the CPU 410 PROFIBUS DP interface You can connect the distributed I/O to the PROFIBUS DP interface. PROFINET IO interface The PROFINET IO interfaces establish the connection to Industrial Ethernet. The PROFINET IO interfaces also serve as the access point for the engineering system.
  • Page 38 Configuration of the CPU 410 3.1 Operator controls and indicators on the CPU 410 Rear of the CPU 410 Setting the rack number Use the switch on the rear panel of the CPU to set the rack number. The switch has two positions: 1 (up) and 0 (down).

  • Page 39: Cpu 410 Monitoring Functions

    Configuration of the CPU 410 3.2 CPU 410 monitoring functions CPU 410 monitoring functions Monitoring functions and error messages The hardware of the CPU and operating system provide monitoring functions to ensure proper operation and defined reactions to errors. Various errors may also trigger a reaction in the user program.
  • Page 40 Configuration of the CPU 410 3.2 CPU 410 monitoring functions Type of error Cause of error Error LED Failure of a rack/station EXTF Power failure in an S7-400 expansion unit • BUSF for PN and DP Failure of a DP/PN segment •...

  • Page 41: Status And Error Displays

    Configuration of the CPU 410 3.3 Status and error displays Status and error displays RUN and STOP LEDs The RUN and STOP LEDs provide information about the CPU's currently active operating state. Table 3- 2 Possible states of the RUN and STOP LEDs Meaning STOP Dark...

  • Page 42: Table 3- 3 Possible States Of The Mstr, Rack0 And Rack1 Leds

    Configuration of the CPU 410 3.3 Status and error displays MSTR, RACK0, and RACK1 LEDs The three LEDs MSTR, RACK0, and RACK1 provide information about the rack number set on the CPU and show which CPU controls the switched I/O. Table 3- 3 Possible states of the MSTR, RACK0 and RACK1 LEDs Meaning...

  • Page 43: Table 3- 6 Possible States Of The Ifm1F And Ifm2F Leds

    Configuration of the CPU 410 3.3 Status and error displays IFM1F and IFM2F LEDs The IFM1F and IFM2F LEDs indicate errors on the first or second synchronization module. Table 3- 6 Possible states of the IFM1F and IFM2F LEDs Meaning IFM1F IFM2F Irrelevant...

  • Page 44: Table 3- 9 Possible States Of The Link1 Ok And Link2 Ok Leds

    Configuration of the CPU 410 3.3 Status and error displays REDF LED System state Basic requirements Dark Redundant (CPUs are redundant) No redundancy error Redundant (CPUs are redundant) There is an I/O redundancy error: Failure of a DP master, or partial or total failure of a •...

  • Page 45: Profibus Dp Interface (X1)

    Configuration of the CPU 410 3.4 PROFIBUS DP interface (X1) PROFIBUS DP interface (X1) Connectable devices The PROFIBUS DP interface can be used to set up a PROFIBUS master system, or to connect PROFIBUS I/O devices. All DP slaves that conform to the standard can be connected to the PROFIBUS DP interface. You can connect the PROFIBUS DP I/O to the PROFIBUS DP interface in redundant or single-channel switched configuration.
  • Page 46 Configuration of the CPU 410 3.5 PROFINET IO interfaces (X5, X8) Connectors The PROFINET interfaces are implemented as Ethernet RJ45 interfaces. Always use RJ45 connectors to hook up devices to a PROFINET interface. Properties of the PROFINET IO interfaces Protocols and communication functions PROFINET IO According to IEC 61784-2 Conformance Class A und B...
  • Page 47 PROFINET IO demands operation at 100 Mbps full-duplex, this would not be a long-term option to address IO devices. Reference ● For details about PROFINET, refer to PROFINET System Description (http://support.automation.siemens.com/WW/view/en/19292127) ● For detailed information about Ethernet networks, network configuration and network components refer to SIMATIC NET Manual: Twisted-Pair and Fiber-Optic Networks (http://support.automation.siemens.com/WW/view/en/8763736).

  • Page 48: Summary Of Parameters For Cpu 410

    Configuration of the CPU 410 3.6 Summary of parameters for CPU 410 Summary of parameters for CPU 410 Default values All parameters are set to factory defaults. These defaults are suitable for a wide range of standard applications and can be used to operate the CPU 410 directly without having to make any additional settings.

  • Page 49: Profibus Dp

    PROFIBUS DP CPU 410 as PROFIBUS DP master Startup of the DP master system You use the following parameters to set startup monitoring of the DP master: ● Ready message from module ● Transfer of parameters to modules This means that the DP slaves must be started up and their parameters assigned by the CPU (as DP master) within the set time.
  • Page 50 PROFIBUS DP 4.2 Diagnostics of the CPU 410 as PROFIBUS DP master BUS1F Meaning Remedy Flashes Station failure Check whether the bus cable is connected to the • • CPU 410 or the bus is interrupted. At least one of the assigned slaves cannot •...

  • Page 51: Profinet Io

    Also observe the following documents: ● Installation guideline ● Assembly guideline ● PROFINET_Guideline_Assembly Additional information on the use of PROFINET IO in automation engineering is available at the following Internet address (http://www.siemens.com/profinet/). CPU 410 Process Automation/CPU 410 SMART System Manual, 05/2017, A5E31622160-AC...

  • Page 52: Profinet Io Systems

    PROFINET IO 5.2 PROFINET IO systems PROFINET IO systems Functions of PROFINET IO The following graphic shows the new functions in PROFINET IO: The graphic shows Examples of connection paths The connection of company You can access devices at the field level from PCs in your company network network and field level Example: •...

  • Page 53: Device Replacement Without Exchangeable Medium / Es

    Further information You will find further information about PROFINET IO in the documents listed below: ● In manual PROFINET system description (http://support.automation.siemens.com/WW/view/en/19292127) ● In Programming Manual Migration from PROFIBUS DP to PROFINET IO (http://support.automation.siemens.com/WW/view/en/19289930) Device replacement without exchangeable medium / ES IO devices having this function can be replaced in a simple manner: ●...
  • Page 54 PROFINET IO 5.3 Device replacement without exchangeable medium / ES Additional information For additional information, refer to the STEP 7 Online Help and to the PROFINET System Description (http://support.automation.siemens.com/WW/view/en/19292127) manual. CPU 410 Process Automation/CPU 410 SMART System Manual, 05/2017, A5E31622160-AC...

  • Page 55: I/O Configuration Variants

    I/O configuration variants Stand-alone operation Overview This section provides information needed for stand-alone operation of the CPU 410. You will learn: ● how stand-alone operation is defined ● when stand-alone operation is required ● what you have to take into account for stand-alone operation ●...

  • Page 56: Table 6- 1 System Modifications During Operation

    I/O configuration variants 6.1 Stand-alone operation Note the different procedures described below for any system change during operation: Table 6- 1 System modifications during operation CPU 410 in stand-alone operation CPU 410 in redundant system state As described in Plant changes in RUN - CiR (Page 155). As described in section Plant changes during redundant operation - H-CiR (Page 197) for redundant operation.
  • Page 57 I/O configuration variants 6.1 Stand-alone operation If you later want to expand the CPU 410 to a fault-tolerant system, proceed as follows: 1. Open a new project and insert a fault-tolerant station. 2. Copy the entire rack from the standard SIMATIC-400 station and insert it twice into the fault-tolerant station.

  • Page 58: Fail-Safe Operation

    The S7 F Systems optional package adds security functions to the CPU 410. The current TÜV certificates are available on the Internet: TÜV certificates (http://support.automation.siemens.com) under "Product Support". Fail-safe I/O modules (F-modules) F-modules have all of the required hardware and software components for safe processing in accordance with the required safety class.

  • Page 59: Figure 6-2 Safety-Related Communication

    I/O configuration variants 6.2 Fail-safe operation Safety-related communication with PROFIsafe profile PROFIsafe was the first communication standard according to the IEC 61508 safety standard that permits both standard and safety-related communication on one bus line. This not only results in an enormous savings potential with regard to cabling and part variety, but also the advantage of retrofit ability.

  • Page 60: Table 6- 2 Measures In Profisafe For Error Avoidance

    Coupling of safety- ✓ ✓ ✓ related messages and standard messages (masquerade) FIFO errors (first-in- ✓ first-out data register for maintaining the sequence) See also S7 F Systems optional package (http://support.automation.siemens.com/WW/view/en/35130252) CPU 410 Process Automation/CPU 410 SMART System Manual, 05/2017, A5E31622160-AC...

  • Page 61: Fault-Tolerant Automation Systems (Redundancy Operation)

    F-systems. You can find information on this in following manual: SIMATIC Industrial Software S7 F/FH Systems (http://support.automation.siemens.com/WW/view/en/2201072) Why fault-tolerant automation systems? The purpose of using fault-tolerant automation systems is to reduce production downtimes, regardless of whether the failures are caused by an error/fault or are due to maintenance work.

  • Page 62: Increase Of Plant Availability, Reaction To Errors

    I/O configuration variants 6.3 Fault-tolerant automation systems (redundancy operation) Single-channel switched I/O In single-channel switched configuration, there is one of each of the input/output modules. In redundant operation, these modules can addressed by both subsystems. The single-channel switched I/O configuration is recommended for system components which tolerate the failure of individual modules.

  • Page 63: Figure 6-4 Example Of Redundancy In A Network Without Error

    I/O configuration variants 6.3 Fault-tolerant automation systems (redundancy operation) No error/fault Figure 6-4 Example of redundancy in a network without error CPU 410 Process Automation/CPU 410 SMART System Manual, 05/2017, A5E31622160-AC...

  • Page 64: Figure 6-5 Example Of Redundancy In A 1-Out-Of-2 System With Error

    I/O configuration variants 6.3 Fault-tolerant automation systems (redundancy operation) With error/fault The following figure shows how a component may fail without impairing the functionality of the overall system. Figure 6-5 Example of redundancy in a 1-out-of-2 system with error CPU 410 Process Automation/CPU 410 SMART System Manual, 05/2017, A5E31622160-AC...

  • Page 65: Introduction To The I/O Link To Fault-Tolerant System

    I/O configuration variants 6.4 Introduction to the I/O link to fault-tolerant system Failure of a redundant node (total failure) The following figure shows that the overall system is no longer operable, because both subunits have failed in a 1-out-of-2 redundancy node (total failure). Figure 6-6 Example of redundancy in a 1-out-of-2 system with total failure Introduction to the I/O link to fault-tolerant system...

  • Page 66: Using Single-Channel Switched I/O

    I/O configuration variants 6.5 Using single-channel switched I/O Note IO redundancy The term IO redundancy is also used for the connection of a redundant I/O to PROFINET IO Addressing If you are using an I/O in a system-redundant configuration, you always use the same address when addressing the I/O.

  • Page 67: Table 6- 3 Interface Modules For Use Of Single-Channel Switched I/O Configuration At The Profibus Dp Interface

    I/O configuration variants 6.5 Using single-channel switched I/O Single-channel switched I/O configuration at the PROFIBUS DP interface The installation with single-channel switched I/O is possible with the ET 200M distributed I/O device with active backplane bus and redundant PROFIBUS DP slave interface and with the ET 200iSP distributed I/O device.

  • Page 68: Table 6- 4 Bus Modules For Hot Swapping

    I/O configuration variants 6.5 Using single-channel switched I/O Bus modules for hot swapping You can use the following bus modules for hot swapping a variety of components: Table 6- 4 Bus modules for hot swapping Bus module Article No. BM PS/IM for load power supply 6ES7195-7HA00-0XA0 and IM 153 BM 2 x 40 for two modules with 40...
  • Page 69 I/O configuration variants 6.5 Using single-channel switched I/O FF Link The FF Link bus link is a gateway between a PROFIBUS DP master system and a FOUNDATION Fieldbus H1 segment and thus enables the integration of FF devices in SIMATIC PCS 7. The two bus systems are uncoupled from each other by the IM 153-2 FF both physically (galvanically) and with respect to protocol and time.

  • Page 70: Figure 6-8 Single-Channel Switched Distributed I/O Configuration At The Profinet Io Interface

    I/O configuration variants 6.5 Using single-channel switched I/O Single-channel switched I/O configuration at the PROFINET IO interface The installation with single-channel switched I/O is possible with the ET 200M and ET 200SP HA distributed I/O devices with active backplane bus and redundant PROFINET IO interface. Figure 6-8 Single-channel switched distributed I/O configuration at the PROFINET IO interface Each subsystem of the S7-400H is connected (over a PROFINET IO interface) to the...
  • Page 71 I/O configuration variants 6.5 Using single-channel switched I/O PROFINET IO interfaces are located on two different IMs, this is known as an R1 configuration The R stands for redundant IMs and thus for two PROFINET IO interfaces. See Chapter Communication services (Page 308). You can use the following interface module for the I/O configuration at the PROFINET IO interface: Table 6- 5...
  • Page 72 You can use the Excel file "s7ftimea.xls" to calculate the monitoring and reaction times. The file is available at the following address: http://support.automation.siemens.com/WW/view/en/22557362 Note Please note that the CPU can only detect a signal change if the signal duration is greater than the specified changeover time.

  • Page 73: Versions Of I/O Connection To The Profinet Io Interface

    I/O configuration variants 6.6 Versions of I/O connection to the PROFINET IO interface Changeover of the active channel during link-up and updating During link-up and updating with master/standby changeover (see Link-up sequence (Page 346)), a changeover between the active and passive channels occurs for all stations of the switched I/O.

  • Page 74: Figure 6-9 System Redundancy

    I/O configuration variants 6.6 Versions of I/O connection to the PROFINET IO interface Configuration The following figure shows various different configurations for connecting IO devices to the fault-tolerant system. Figure 6-9 System redundancy Configura- Properties tion ① Switched I/O at the PROFINET IO Each IO device is connected over one IM with two logic connections (system redundancy) to the two CPUs in the fault-tolerant system.
  • Page 75 I/O configuration variants 6.6 Versions of I/O connection to the PROFINET IO interface Configuration with two IO devices with independent, system-redundant connection This configuration has the following advantage: The complete system can continue operating after a wire break, no matter where the wire break is located. One of the two communication connections of the IO devices is always retained.

  • Page 76: Redundant I/O In An Et 200Sp Ha

    I/O configuration variants 6.6 Versions of I/O connection to the PROFINET IO interface Cabinet concept with switched I/O connected to PROFINET IO The following figure shows the system-redundant connection of nine IO devices via three switches. With this configuration, for example, IO devices can be arranged in multiple cabinets.
  • Page 77 I/O configuration variants 6.6 Versions of I/O connection to the PROFINET IO interface This terminal block connects the respective process signals of the two IO modules to a common process terminal. ● There is less wiring work compared to connecting separate I/O modules, because the interconnection of the process signals is integrated in the system.

  • Page 78: Figure 6-11 S7-400 H-System With Sensors And Actuators On Module Pairs

    I/O configuration variants 6.6 Versions of I/O connection to the PROFINET IO interface Configuration The following figure shows an example for the connection of the sensors or actuators each with two redundantly used input/output modules. Figure 6-11 S7-400 H-system with sensors and actuators on module pairs (redundant signal processing) Response to failure The following applies when a I/O module or a channel of the two I/O modules fails (valid for input/output and mixed modules):...

  • Page 79: Figure 6-12 As 410 With Redundant Module Pairs

    I/O configuration variants 6.6 Versions of I/O connection to the PROFINET IO interface Figure 6-12 AS 410 with redundant module pairs Maintenance and service One of the following functions is possible in each case during operation: ● Firmware update ● Replacing a module CPU 410 Process Automation/CPU 410 SMART System Manual, 05/2017, A5E31622160-AC...

  • Page 80: Connection Of Two-Channel I/O To The Profibus Dp Interface

    I/O configuration variants 6.7 Connection of two-channel I/O to the PROFIBUS DP interface Connection of two-channel I/O to the PROFIBUS DP interface 6.7.1 Connecting redundant I/O Redundant I/O in the switched DP slave To achieve this, the signal modules are installed in pairs in ET 200M distributed I/O devices with active backplane bus.
  • Page 81 I/O configuration variants 6.7 Connection of two-channel I/O to the PROFIBUS DP interface Principle of channel group-specific redundancy Channel errors due to discrepancy cause the passivation of the respective channel. Channel errors due to diagnostic interrupts (OB82) cause the passivation of the channel group affected.
  • Page 82 I/O configuration variants 6.7 Connection of two-channel I/O to the PROFIBUS DP interface The OBs into which you need to link the various blocks are listed in the table below: Block FC 450 "RED_INIT" OB 72 "CPU redundancy error" (only with fault-tolerant systems) •...

  • Page 83: Signal Modules For Redundancy

    I/O configuration variants 6.7 Connection of two-channel I/O to the PROFIBUS DP interface HW configuration and configuring the redundant I/O Follow the steps below to use redundant I/O: 1. Insert all the modules you want to operate redundantly. Please also observe the default rules for configuration detailed below.
  • Page 84 I/O configuration variants 6.7 Connection of two-channel I/O to the PROFIBUS DP interface A complete list of all modules released for SIMATIC PCS 7 V9.0 can be found in the SIMATIC PCS 7 technical documentation, see Technical documentation. Table 6- 6 Signal modules for redundancy Module Article No.
  • Page 85 I/O configuration variants 6.7 Connection of two-channel I/O to the PROFIBUS DP interface Module Article No. Redundant DO dual-channel DO8xDC 24 V/0.5 A 6ES7322-8BF00-0AB0 Definite evaluation of the diagnostics information "P short-circuit" and "wire break" is not possible. Deselect these individu- ally in your configuration.
  • Page 86 I/O configuration variants 6.7 Connection of two-channel I/O to the PROFIBUS DP interface Module Article No. AI 8x16Bit 6ES7 331-7NF00-0AB0 Use in voltage measurement The "wire break" diagnostics function in HW Config must not be enabled when the modules are operated with transmit- •...
  • Page 87 The F ConfigurationPack can be downloaded free of charge from the Internet. You can find it on the Customer Support site at Download of F Configuration Pack (http://support.automation.siemens.com/WW/view/en/15208817) Using digital input modules as redundant I/O The following parameters were set to configure digital input modules for redundant operation: ●...
  • Page 88 Details on combinable ET 200M modules and suitable connecting cables and on the current MTA product range can be found at the following address: Update and expansion of the MTA terminal modules (http://support.automation.siemens.com/WW/view/en/29289048) CPU 410 Process Automation/CPU 410 SMART System Manual, 05/2017, A5E31622160-AC...

  • Page 89: Figure 6-14 Fault-Tolerant Digital Input Module In 1-Out-Of-2 Configuration With One Encoder

    I/O configuration variants 6.7 Connection of two-channel I/O to the PROFIBUS DP interface Using redundant digital input modules with non-redundant encoders With non-redundant encoders, you use digital input modules in a 1-out-of-2 configuration: Figure 6-14 Fault-tolerant digital input module in 1-out-of-2 configuration with one encoder The use of redundant digital input modules increases their availability.

  • Page 90: Figure 6-15 Fault-Tolerant Digital Input Modules In 1-Out-Of-2 Configuration With Two Encoders

    I/O configuration variants 6.7 Connection of two-channel I/O to the PROFIBUS DP interface Using redundant digital input modules with redundant encoders With redundant encoders, you use digital input modules in a 1-out-of-2 configuration: Figure 6-15 Fault-tolerant digital input modules in 1-out-of-2 configuration with two encoders The use of redundant encoders also increases their availability.
  • Page 91 I/O configuration variants 6.7 Connection of two-channel I/O to the PROFIBUS DP interface Using analog input modules as redundant I/O You specified the following parameters when you configured the analog input modules for redundant operation: ● Tolerance window (configured as a percentage of the end value of the measuring range) Two analog values are considered equal if they are within the tolerance window.

  • Page 92: Figure 6-17 Fault-Tolerant Analog Input Modules In 1-Out-Of-2 Configuration With One Encoder

    I/O configuration variants 6.7 Connection of two-channel I/O to the PROFIBUS DP interface Redundant analog input modules with non-redundant encoder With non-redundant encoders, analog input modules are used in a 1-out-of-2 configuration: Figure 6-17 Fault-tolerant analog input modules in 1-out-of-2 configuration with one encoder Remember the following when connecting an encoder to multiple analog input modules: ●...
  • Page 93 I/O configuration variants 6.7 Connection of two-channel I/O to the PROFIBUS DP interface Additional conditions for specific modules AI 8x12 bit 6ES7 331-7K..02-0AB0 ● Use a 50 ohm or 250 ohm resistor to map the current on a voltage: Resistor 50 ohms 250 ohms Current measuring range...

  • Page 94: Figure 6-18 Fault-Tolerant Analog Input Modules In 1-Out-Of-2 Configuration With Two Encoders

    I/O configuration variants 6.7 Connection of two-channel I/O to the PROFIBUS DP interface Redundant analog input modules for direct current measurement The following applies for wiring analog input modules: ● Suitable encoder types: active 4-wire and passive 2-wire transmitters with output ranges +/-20 mA, 0 to 20 mA, and 4 to 20 mA.
  • Page 95 I/O configuration variants 6.7 Connection of two-channel I/O to the PROFIBUS DP interface Redundant analog output modules You implement fault-tolerant control of a final controlling element by wiring two outputs of two analog output modules in parallel (1-out-of-2 configuration) Figure 6-19 Fault-tolerant analog output modules in 1-out-of-2 configuration The following applies to the wiring of analog output modules: ●...
  • Page 96 CPU, the complete passivation process may take approximately 1 minute. See also SIMATIC Process Control System PCS 7 Released Modules (https://support.industry.siemens.com/cs/ww/de/view/109736547/en) S7-400H Systems Redundant I/O (http://support.automation.siemens.com/WW/view/en/9275191) CPU 410 Process Automation/CPU 410 SMART System Manual, 05/2017, A5E31622160-AC...

  • Page 97: Evaluating The Passivation Status

    I/O configuration variants 6.8 Media redundancy 6.7.3 Evaluating the passivation status Procedure First, determine the passivation status by evaluating the status byte in the status/control word "FB_RED_IN.STATUS_CONTROL_W". If you see that one or more modules have been passivated, determine the status of the respective module pairs in MODUL_STATUS_WORD.
  • Page 98 I/O configuration variants 6.8 Media redundancy Configuration The following figure shows examples of the connection of IO devices to the PROFINET IO system: Configura- Properties tion ① Media redundancy Each node is connected to two other nodes in a ring configuration. The IO controller must be configured as an MRP manager in HW Config.
  • Page 99 You can also combine media redundancy under PROFINET IO with other PROFINET IO functions. Additional information For additional information, refer to the STEP 7 Online Help and to Manual PROFINET System Description (http://support.automation.siemens.com/WW/view/en/19292127). CPU 410 Process Automation/CPU 410 SMART System Manual, 05/2017, A5E31622160-AC...
  • Page 100 I/O configuration variants 6.8 Media redundancy CPU 410 Process Automation/CPU 410 SMART System Manual, 05/2017, A5E31622160-AC...

  • Page 101: System And Operating States Of The Cpu 410

    System and operating states of the CPU 410 CPU 410 operating modes 7.1.1 RUN mode Reaction of the CPU If there is no startup problem or error and the CPU was able to switch to RUN, the CPU either executes the user program or remains idle. The I/O can be accessed. ●...

  • Page 102: Stop Mode

    System and operating states of the CPU 410 7.1 CPU 410 operating modes The redundant system state is only supported if the two CPUs have the same version and firmware version. Redundancy will be lost if one of the errors listed in the following table occurs.

  • Page 103: Startup Mode

    System and operating states of the CPU 410 7.1 CPU 410 operating modes Memory reset The memory reset function affects only the selected CPU. To reset both CPUs, you must reset one and then the other. 7.1.3 STARTUP mode Startup types The CPU 410 distinguishes between two startup types: cold restart and warm restart.

  • Page 104: Hold Mode

    System and operating states of the CPU 410 7.1 CPU 410 operating modes The master CPU checks and assigns parameters for the following: ● the switched I/O devices ● the one-sided I/O including CPs and FMs assigned to it Startup of the standby CPU The standby CPU startup routine does not call an OB 100 or OB 102.

  • Page 105: Link-Up And Update Modes

    System and operating states of the CPU 410 7.1 CPU 410 operating modes 7.1.5 LINK-UP and UPDATE modes The master CPU checks and updates the memory content of the standby CPU before the fault-tolerant system assumes redundant system mode. This is implemented in two successive phases: link-up and update.

  • Page 106: Defective State

    System and operating states of the CPU 410 7.1 CPU 410 operating modes 4. If a multiple-bit error occurs on a CPU in redundant operation, that CPU will switch to ERROR-SEARCH operating state. The other CPU becomes master, if necessary, and continues running in solo operation.

  • Page 107: System States Of The Redundant Cpu 410

    System and operating states of the CPU 410 7.2 System states of the redundant CPU 410 System states of the redundant CPU 410 7.2.1 Introduction The S7-400H consists of two redundantly configured subsystems that are synchronized via fiber-optic cables. The two subsystems form a fault-tolerant automation system that operates with a dual- channel (1-out-of-2) structure based on the "active redundancy"...
  • Page 108 You create your program in the same way as for standard S7-400 CPUs. Event-driven synchronization procedure The "event-driven synchronization" procedure patented by Siemens was used for the S7- 400H. Event-driven synchronization means that the master and standby always synchronize their data when an event occurs which may lead to different internal states of the subsystems.

  • Page 109: The System States Of The Fault-Tolerant System

    System and operating states of the CPU 410 7.2 System states of the redundant CPU 410 If the self-test detects an error, the fault-tolerant system tries to eliminate it or to suppress its effects. A description of the self-test is available in Chapter Self-test (Page 114). System operation without STOP To best meet the requirements of the process industry for system operation without STOP, SIMATIC PCS 7 intercepts as many possible STOP causes as possible.

  • Page 110: Displaying And Changing The System State Of A Fault-Tolerant System

    System and operating states of the CPU 410 7.2 System states of the redundant CPU 410 7.2.3 Displaying and changing the system state of a fault-tolerant system Procedure: 1. Select a CPU in SIMATIC Manager. 2. Select the menu command PLC > Diagnostics/Setting >Operating state. Note STOP is only possible with authorization in projects with password protection.

  • Page 111: System Status Change From The Standalone Mode System Status

    System and operating states of the CPU 410 7.2 System states of the redundant CPU 410 Changing to standalone mode (starting only one CPU) 1. In the table, select the CPU you want to start up. 2. Select the Restart button (warm restart). 7.2.5 System status change from the standalone mode system status Requirements:...

  • Page 112: System Diagnostics Of A Fault-Tolerant System

    System and operating states of the CPU 410 7.2 System states of the redundant CPU 410 Changing to STOP system state (stopping the fault-tolerant system) 1. Select the fault-tolerant system in the table. 2. Select the Stop button. Result Both CPUs switch to STOP. Changing to standalone mode (stop of one CPU) 1.
  • Page 113 System and operating states of the CPU 410 7.2 System states of the redundant CPU 410 Result: The operating state of the selected CPU can be identified based on the display of the selected CPU in the "Diagnose hardware" dialog: CPU icon Operating state of the respective CPU Master CPU is in RUN operating state...

  • Page 114: Self-Test

    System and operating states of the CPU 410 7.3 Self-test Self-test Processing the self-test The CPU executes the complete self-test program after an unbuffered POWER ON, e.g., POWER ON after initial insertion of the CPU or POWER ON without backup battery, and in the ERROR-SEARCH operating state.
  • Page 115 System and operating states of the CPU 410 7.3 Self-test RAM/PIQ comparison error If the self-test detects a RAM/PIQ comparison error, the fault-tolerant system exits redundant operating state and the standby CPU switches to ERROR SEARCH operating state (default setting). The cause of the error is written to the diagnostics buffer. The response to a recurring RAM/PIQ comparison error depends on whether the error recurs in the first self-test cycle after troubleshooting or not until later.
  • Page 116 System and operating states of the CPU 410 7.3 Self-test Hardware fault with one-sided OB 121 call, checksum error, 2nd occurrence The response of a CPU 410 to the second occurrence of hardware faults with one-sided OB 121 call and checksum errors is as shown in the following table for the various operating modes of a CPU 410.

  • Page 117: Performing A Memory Reset

    System and operating states of the CPU 410 7.4 Performing a memory reset System Software for S7- For detailed information on SFC 90 "H_CTRL", refer to Manual 300/400, System and Standard Functions Note In a fail-safe system, you are not allowed to disable and then re-enable the cyclic self-tests. Performing a memory reset Memory reset process in the CPU You can perform a memory reset of the CPU from the ES.
  • Page 118 System and operating states of the CPU 410 7.4 Performing a memory reset ● The parameters of the PN interfaces – Name (NameOfStation) – IP address of CPU – Subnet mask – Static SNMP parameters ● The time of day ●...

  • Page 119: Link-Up And Update

    Link-up and update Effects of link-up and updating The link-up and update operations are indicated by the REDF LED on both CPUs. During link-up, the LEDs flash at a frequency of 0.5 Hz, and when updating at a frequency of 2 Hz. Link-up and update have various effects on user program execution and on communication functions.

  • Page 120: Link-Up And Update Via An Es Command

    Link-up and update 8.2 Link-up and update via an ES command Link-up and update via an ES command Which commands you can use on the programming device to initiate a link-up and update operation is determined by the current conditions on the master and standby CPU. The following table shows the possible PG commands for the link-up and update in various circumstances.
  • Page 121 Link-up and update 8.3 Time monitoring The monitoring times are described in detail below. ● Maximum cycle time extension – Cycle time extension: The time during the update in which neither OB 1 nor any other OBs up to priority class 15 are executed. "Normal" cycle time monitoring is disabled within this time span.
  • Page 122 Link-up and update 8.3 Time monitoring Figure 8-1 Meanings of the times relevant for updates Response to time-outs If one of the times monitored exceeds the configured maximum value, the following procedure is started: 1. Cancel update 2. Fault-tolerant system remains in standalone mode, with the previous master CPU in RUN 3.

  • Page 123: Time Response

    Link-up and update 8.3 Time monitoring 8.3.1 Time response Time response during link-up The influence of link-up operations on your plant's control system should be kept to an absolute minimum. The current load on your automation system is therefore a decisive factor in the increase of link-up times.
  • Page 124 Link-up and update 8.3 Time monitoring These times are based on a fault-tolerant system with two communication peers and an average communication load. Your system profile may differ considerably from those scenarios, therefore the following rules must be observed. ● A high communication load can significantly increase cycle time. ●...
  • Page 125 Link-up and update 8.3 Time monitoring Figure 8-2 Correlation between the minimum I/O retention time and the maximum inhibit time for priority classes > 15 Note the following condition: 50 ms + minimum I/O retention time ≤ (maximum inhibit time for priority classes > 15) It follows that a high minimum I/O retention time can determine the maximum inhibit time for priority classes >...
  • Page 126 Link-up and update 8.3 Time monitoring 1. Based on the bus parameters in STEP 7, determine the following for each DP master system: – T for the DP master system – DP changeover time (referred to below as T DP_UM 2.
  • Page 127 Link-up and update 8.3 Time monitoring 10.Determine the share of the maximum inhibit time for I/O classes > 15 that is required by the minimum I/O retention time (T P15_OD = 50 ms + min. I/O retention time [2] P15_OD Note If T >...
  • Page 128 Link-up and update 8.3 Time monitoring 4. Based on the technical specifications of the PN devices used: = 20 ms Device_UM 5. Based on the technological settings of your system: = 1250 ms PTO_1 = 1200 ms PTO_2 = 1000 ms PTO_PN 6.
  • Page 129 Link-up and update 8.3 Time monitoring Remedies if it is not possible to calculate T If no recommendation results from calculating the maximum inhibit time for priority classes > 15, you can remedy this by taking various measures: ● Reduce the cyclic interrupt cycle of the configured cyclic interrupt. ●...

  • Page 130: Performance Values For Link-Up And Update

    Link-up and update 8.3 Time monitoring 8.3.3 Performance values for link-up and update User program share T of the maximum inhibit time for priority classes > 15 P15_AWP The user program share T of the maximum inhibit time for priority classes > 15 can be P15_AWP calculated using the following formula: in ms = 0.7 x size of DBs in work memory in KB + 75...

  • Page 131: Special Features In Link-Up And Update Operations

    Link-up and update 8.4 Special features in link-up and update operations In the worst case, this period is extended by the following amounts: ● Maximum cyclic interrupt used ● Duration of all cyclic interrupt OBs ● Duration of high-priority interrupt OBs executed until the start of interrupt delays Special features in link-up and update operations Requirement for input signals during the update Any process signals read previously are retained and not included in the update.
  • Page 132 Link-up and update 8.4 Special features in link-up and update operations CPU 410 Process Automation/CPU 410 SMART System Manual, 05/2017, A5E31622160-AC...

  • Page 133: Special Functions Of The Cpu 410

    Special functions of the CPU 410 Security functions of the CPU 410 Automation system protection The CPU 410 has a range of functions with which you can protect your automation system. ● Signed firmware: The firmware of the CPU 410 has a signature to detect manipulations on the CPU itself. If firmware with errors in its signature is loaded, the CPU 410 rejects the firmware update.

  • Page 134: Security Levels

    Special functions of the CPU 410 9.2 Security levels Security levels You can define a protection level for your project in order to prevent unauthorized access to the CPU programs. The objective of these protection level settings is to grant a user access to specific programming device functions which are not protected by password, and to allow that user to execute those functions on the CPU.
  • Page 135 Special functions of the CPU 410 9.2 Security levels Setting the protection level with SFC 109 "PROTECT" You can set the following protection levels on your CPU with SFC 109: ● SFC 109 call with MODE=0: Setting the protection level 1. If the password legitimization is locked, the lock is canceled by calling SFC 109 with MODE=0.

  • Page 136: Security Event Logging

    You can store security events as a text file using Simatic Manager -> PLC -> Save Security Events. Parameter description The entries in the saved text file are structured as follows: CEF parameter Key name Meaning Manufacturer Siemens AG Device e.g.: CPU 410-5H Version e.g.: V8.2.0 Event ID Corresponds to Security Event ID (see below) Event...
  • Page 137 Special functions of the CPU 410 9.3 Security event logging CEF parameter Key name Meaning Connection parameters The following parameters are summarized under the term "Connection (optional) parameters": Connection_id, Session ID • Protocol • Application protocol • Connection type • Gateway session ID •...
  • Page 138 Special functions of the CPU 410 9.4 Field Interface Security Security Event Security Event Severity meaning event ID SE_LOGOFF Cancel logon SE_ACCESS_PWD_ENSABLED Password protection was set up SE_ACCESS_PWD_DISABLED Password protection was revoked SE_ACCESS_PWD_CHANGED Password has been changed. SE_ACCESS_DENIED A connection setup from the outside is rejected because Field Interface Security is activated for this interface SE_SOFTWARE_INTEGRITY_CHECK_FAILE An attempt was made to install invalid firmware.

  • Page 139: Field Interface Security

    Special functions of the CPU 410 9.4 Field Interface Security Field Interface Security Activating additional protection at the DP or PNIO interface If want to prevent access to the CPU over the DP or PNIO interface, you can block that access.

  • Page 140: Retentive Load Memory

    Special functions of the CPU 410 9.6 Retentive load memory ● Protected blocks can only be released again for editing if you have the correct key and the corresponding decompilation information included in your package. Make sure that the key is always kept in a safe place. ●...

  • Page 141: Type Update With Interface Change In Run

    Special functions of the CPU 410 9.7 Type update with interface change in RUN Without a backup battery, the following data is not buffered: ● Diagnostic buffer ● Security event buffer ● Date and time ● Process image ● Data blocks that were not backed up to the load memory with CFC ●...

  • Page 142: Resetting The Cpu 410 To Delivery Condition (Reset To Factory Setting)

    Special functions of the CPU 410 9.8 Resetting the CPU 410 to delivery condition (reset to factory setting) Resetting the CPU 410 to delivery condition (reset to factory setting) CPU factory settings A general memory reset is performed when you reset the CPU to its factory settings and the properties of the CPU are set to the following values: Table 9- 2 CPU properties in the factory settings...

  • Page 143: Reset During Operation

    Special functions of the CPU 410 9.9 Reset during operation LED pattern 1 LED pattern 2 Dark Dark STOP Dark Dark Reset during operation CPU operating state The following procedure references the RED or RUN RED operating state. Note If you perform a reset to prevent a malfunction of the CPU, you should read out the diagnostics buffer and the service data before the reset with the menu command "PLC ->...

  • Page 144: Response To Fault Detection

    In the rare instance that a fault occurs that cannot be eliminated by the firmware, the current service data is saved internally for further evaluation by SIEMENS specialists. An automatic reboot is then started. This behavior reduces the downtime of the CPU to a minimum.

  • Page 145: Reading Service Data

    Special functions of the CPU 410 9.11 Reading service data 9.11 Reading service data Application case If you need to contact Customer Support due to a service event, the department may require specific diagnostic information on the CPU status of your system. This information is stored in the diagnostic buffer and in the service data.

  • Page 146: Updating Firmware In Stand-Alone Operation

    Special functions of the CPU 410 9.12 Updating firmware in stand-alone operation 9.12 Updating firmware in stand-alone operation Basic procedure To update the firmware of a CPU, you will receive several files (*.UPD) containing the current firmware. You download these files to the CPU. You can update the firmware in a single work step or you can first download it to the CPU and then activate it at a later time.
  • Page 147 Special functions of the CPU 410 9.12 Updating firmware in stand-alone operation Proceed as follows to activate the loaded firmware at a later time: 1. Open the station containing the CPU you want to update in HW Config. 2. Select the CPU. 3.

  • Page 148: Updating Firmware In Redundant Mode

    Special functions of the CPU 410 9.13 Updating firmware in redundant mode 9.13 Updating firmware in redundant mode Requirement You are operating the CPU 410 in a fault-tolerant system. Both Sync links exist and are working. There are no redundancy losses. The REDF LED is not lit and both CPUs are in redundant mode.
  • Page 149 Special functions of the CPU 410 9.13 Updating firmware in redundant mode Proceed as follows to activate the loaded firmware at a later time: 1. Open the station containing the CPU you want to update in HW Config. 2. Select the CPU. 3.
  • Page 150 Special functions of the CPU 410 9.13 Updating firmware in redundant mode 7. Click "Execute". The CPU in rack 1 is switched to STOP. The new firmware is loaded to and activated in the CPU in rack 1. 8. Click "Continue". The system switches to the CPU with the new firmware.

  • Page 151: Time Synchronization And Time Stamping

    Time synchronization and time stamping Definition of time synchronization Time synchronization refers to the process in which various S7 stations receive or retrieve their local time from a central time source (central time transmitter/time server). Time-of-day synchronization is required when the time sequence of events from different stations is to be evaluated.
  • Page 152 Time synchronization and time stamping CPU 410 as time master If you configure the CPU 410 as the time master, you must specify a synchronization interval. You can select any interval between 1 s and 24 h. Select a synchronization interval of 10 s if the CPU 410 is the time master on the S7-400 backplane bus.
  • Page 153 Time synchronization and time stamping Additional information You can find additional information about time-of-day synchronization and time stamping with SIMATIC PCS 7 in the following manuals: ● High-precision Time Stamping with ET 200SP HA ● High-precision Time Stamping (V9.0) ● Time-of-day Synchronization (V9.0) CPU 410 Process Automation/CPU 410 SMART System Manual, 05/2017, A5E31622160-AC...
  • Page 154 Time synchronization and time stamping CPU 410 Process Automation/CPU 410 SMART System Manual, 05/2017, A5E31622160-AC...

  • Page 155: Plant Changes In Run - Cir

    Plant changes in RUN - CiR 11.1 Motivation for CiR via PROFINET IO There are systems that may not be shut down during operation. This may be the case, for example, due to the complexity of the automated process or the high costs associated with restarting the system.
  • Page 156 Plant changes in RUN - CiR 11.1 Motivation for CiR via PROFINET IO Configuration requirements for PROFINET IO You need to select saving the data on the CPU for all components within the station for which you can choose whether the configuration data is saved on the module itself or on the CPU.

  • Page 157: Permitted Changes Over Profinet Io

    Plant changes in RUN - CiR 11.2 Permitted changes over PROFINET IO 11.2 Permitted changes over PROFINET IO Permitted configuration changes for PROFINET IO The process introduced here supports the following changes to your AS: ● Adding and removing an IO device. The IO device does not need CiR capability for this step.

  • Page 158: Procedure For Profinet Io

    Plant changes in RUN - CiR 11.3 Procedure for PROFINET IO Restriction All changes that are not explicitly permitted above as part of plant changes in RUN, are not permitted during operation and are not explained in more detail here. Recommendations plant changes during operation using CiR ●...

  • Page 159: Add Io Devices Or I/O Modules

    Plant changes in RUN - CiR 11.3 Procedure for PROFINET IO Note IO devices that are to be added or removed do not have to be CiR-capable. Note that the neighborhood relation on the ports may not be change in RUN for non-CiR- capable devices.

  • Page 160: Rebuild Hardware When Adding An Io Device

    Plant changes in RUN - CiR 11.3 Procedure for PROFINET IO Rules for PROFINET IO Within a PROFINET IO subsystem, you must assign an NoS (Name of Station) to an added IO device. You must set the NoS locally on the interface module of the IO device. Recommendation: Prior to local installation, configure the NoS of the interface modules in a separate network.

  • Page 161: Re-Configuring Existing I/O Modules In Io Devices

    Plant changes in RUN - CiR 11.4 Re-configuring I/O modules and ports in IO devices 11.3.5 Re-configuring existing I/O modules in IO devices Procedure The procedure for using previously unused channels is described in the benefits of a previously unused channel. The procedure for re-configuration of previously used channels of I/O modules is described in the sections on re-configuration of a previously used channel or for removing a previously used channel.

  • Page 162: I/O Module Response To Re-Configuration

    Plant changes in RUN - CiR 11.4 Re-configuring I/O modules and ports in IO devices Hardware requirements The I/O modules that can be re-configured in CPU RUN are listed in the info text in the "Hardware catalog" window. 11.4.2 I/O module response to re-configuration Principle The following three responses are possible during re-configuration of input modules: ●...
  • Page 163 Plant changes in RUN - CiR 11.4 Re-configuring I/O modules and ports in IO devices After transmission of the data records, the IO controller marks the I/O modules in the module status data as follows: ● When the transmission was successful, as available. ●...

  • Page 164: Reconfiguration Procedure

    Plant changes in RUN - CiR 11.4 Re-configuring I/O modules and ports in IO devices OB calls in re-configuration Once the CPU has run the tests described in "Behavior of the CPU after download of the configuration in RUN", it starts OB 83 with the event W#16#335A. This means that as of now the input or output data of the I/O modules in question may no longer be correct.
  • Page 165 Plant changes in RUN - CiR 11.4 Re-configuring I/O modules and ports in IO devices Procedure for changing the user program The user program need not be changed as a result of the re-configuration. This is the case, for example, when you change the measuring range for a channel of an analog input module and when you compare the associated analog value with a constant in your program.

  • Page 166: Delete An Already Used Channel

    Plant changes in RUN - CiR 11.5 Motivation for CiR via PROFINET DP 11.4.4.3 Delete an already used channel. Procedure Proceed as follows to remove a channel that has not been used: 1. Change the user program so that the channel to be removed is no longer evaluated, and download it to the CPU.
  • Page 167 Plant changes in RUN - CiR 11.5 Motivation for CiR via PROFINET DP configure the ET 200M with active bus elements and sufficient free space for the planned expansion. You may not integrate the ET 200M as DPV0 slave (with a GSD file). ●...

  • Page 168: Permitted Changes Over Profibus Dp

    Plant changes in RUN - CiR 11.6 Permitted changes over PROFIBUS DP The following OBs must be available in your CPU: ● Hardware interrupt OBs (OB 40 to OB 47) ● Cycle time error OB (OB 80) ● Diagnostic interrupt OB (OB 82) ●...
  • Page 169 Plant changes in RUN - CiR 11.6 Permitted changes over PROFIBUS DP ● Reassignment of parameters of existing modules in DP stations (standard modules and fail-safe signal modules in standard operation) ● Undoing of modifications (undo functionality): added modules, DP slaves and PA slaves (field devices) can be removed again Note If want to add or remove slaves or modules or modify the existing process image partition...

  • Page 170: Cir Objects And Cir Modules For Profinet Dp

    Plant changes in RUN - CiR 11.7 CiR objects and CiR modules for PROFINET DP 11.7 CiR objects and CiR modules for PROFINET DP 11.7.1 Basic Requirements Overview A system modification during RUN via CiR is based on the provisions you have made in your initial configuration for an expansion of your PLC hardware.

  • Page 171: Cir Elements And I/O Address Areas

    Plant changes in RUN - CiR 11.7 CiR objects and CiR modules for PROFINET DP Note When STEP 7 identifies the bus parameters, it takes the configured slaves as well as the CiR elements into account. When it converts CiR elements to real slaves and /or modules in CPU RUN mode, the bus parameter will therefore remain unchanged.

  • Page 172: Procedure For Profibus Dp

    Plant changes in RUN - CiR 11.8 Procedure for PROFIBUS DP I/O Volume for Future Use with CiR Objects and CiR Modules For all DP masters, the following rules apply to future utilization of the I/O bytes: Rule 1 Inputs The total number of physical configured user addresses for inputs and for the input bytes that can be utilized in the future may not exceed the volume of dynamic pro- ject data in the corresponding DP master.
  • Page 173 Plant changes in RUN - CiR 11.8 Procedure for PROFIBUS DP Overview The following basic operating steps are available in STOP state: ● Defining CiR elements ● Deleting CiR elements ● Editing CiR elements ● Downloading the configuration Defining CiR elements You can define CiR objects for previously configured DP and PA master systems and CiR modules for modular DP slaves of type ET 200M / ET 200iSP.

  • Page 174: Defining Cir Elements

    Plant changes in RUN - CiR 11.8 Procedure for PROFIBUS DP 11.8.1.2 Defining CiR Elements Adding CiR elements automatically Note The automatic addition of CiR elements is only possible if a CiR object is not yet present on the selected DP master system. The automatic addition of CiR elements is not available on DP master systems that are downstream of an IM 157.
  • Page 175 Plant changes in RUN - CiR 11.8 Procedure for PROFIBUS DP 3. Using drag-and-drop, move the associated CiR object from the hardware catalog onto the master system. The CiR object then appears in the upper part of the station window as a placeholder slave.

  • Page 176: Deleting Cir Elements

    Plant changes in RUN - CiR 11.8 Procedure for PROFIBUS DP 3. Using drag-and-drop, move the CiR module from the hardware catalog onto the slot directly after the last configured module of the DP slave in the lower part of the station window.

  • Page 177: Basic Procedure In Run Mode

    Plant changes in RUN - CiR 11.8 Procedure for PROFIBUS DP Delete all CiR elements of an existing DP master system as follows: 1. Highlight the icon of the corresponding DP master system in the upper part of the station window.

  • Page 178: Add Slaves Or Modules

    Plant changes in RUN - CiR 11.8 Procedure for PROFIBUS DP Note All plant changes listed below require a CiR object in the DP master system. This also applies for adding and removing slave slots. Back up your current configuration after each download of the station configuration from HW Config (regardless of the CPU mode).

  • Page 179: Reconfigure The Hardware When Adding A Slave

    Plant changes in RUN - CiR 11.8 Procedure for PROFIBUS DP 11.8.2.3 Reconfigure the hardware when adding a slave Procedure 1. Equip the PROFIBUS DP and PROFIBUS PA bus cables with active bus terminals on both ends, so that the cables are correctly terminated during reconfiguration. 2.

  • Page 180: Undo Previous Changes (Undo Function)

    Plant changes in RUN - CiR 11.8 Procedure for PROFIBUS DP 11.8.2.6 Undo previous changes (Undo function): Procedure Undoing changes in RUN involves the following steps: 1. Undo the changes previously made in the user program (if necessary) and then download the user program.

  • Page 181: Using Cir Elements In Run Mode

    Plant changes in RUN - CiR 11.8 Procedure for PROFIBUS DP 11.8.2.8 Using CiR Elements in RUN Mode Introduction This section describes how to expand and then load an existing configuration. Note If you run invalid operations when adding real slaves or modules for configuration, an error message is not output until you load the configuration.
  • Page 182 Plant changes in RUN - CiR 11.8 Procedure for PROFIBUS DP Adding modules in a modular slave of the type ET 200M / ET 200iSP Proceed as follows to add components to an ET 200M / ET 200iSP modular slave: 1.
  • Page 183 Plant changes in RUN - CiR 11.8 Procedure for PROFIBUS DP CPU 410 Process Automation/CPU 410 SMART System Manual, 05/2017, A5E31622160-AC...

  • Page 184: Undoing Previous Changes

    Plant changes in RUN - CiR 11.8 Procedure for PROFIBUS DP Loading the configuration in RUN A modified configuration is loaded in RUN in the following two steps: 1. Check that the current configuration can be loaded ("Station > Check CiR Capability"). 2.

  • Page 185: Reconfigure Existing Modules In Et200M / Et200Isp Stations

    Plant changes in RUN - CiR 11.9 Reconfigure existing modules in ET200M / ET200iSP stations 3. Repeat steps 1 and 2 for the remaining objects you want to remove. 4. Download the modified configuration to your CPU. Note When you delete a slave, STEP 7 updates the guaranteed and the maximum number of slaves as well as the number of input and output bytes of the associated CiR object.

  • Page 186: Module Response During A Reconfiguration

    Plant changes in RUN - CiR 11.9 Reconfigure existing modules in ET200M / ET200iSP stations 11.9.2 Module Response During a Reconfiguration Principle During reconfiguration the input modules can respond in one of the three following ways: ● Channels not affected will continue to return the actual process value. ●...
  • Page 187 Plant changes in RUN - CiR 11.9 Reconfigure existing modules in ET200M / ET200iSP stations Possible fault scenarios during re-configuration The following error scenarios are possible: ● The module receives the parameter data records but cannot evaluate them. ● Serious errors (in particular protocol errors on the DP bus) may cause the DP master to completely suspend the corresponding DP slave, causing all modules of this station to fail.

  • Page 188: Reconfiguration Procedure

    Plant changes in RUN - CiR 11.9 Reconfigure existing modules in ET200M / ET200iSP stations 11.9.4 Reconfiguration Procedure 11.9.4.1 Using a Previously Unused Channel Procedure 1. Change the hardware configuration and download it to the CPU. 2. Save your project. 3.

  • Page 189: Delete An Already Used Channel

    Plant changes in RUN - CiR 11.9 Reconfigure existing modules in ET200M / ET200iSP stations Procedure for changing the user program and the hardware The user program and the hardware must be changed as a result of the re-configuration. This is the case, for example, when you re-configure an input channel from "0 to 20 mA" to "0 to 10 V".

  • Page 190: Notes On Reconfiguration In Run Mode Depending On The I/O

    Plant changes in RUN - CiR 11.10 Notes on Reconfiguration in RUN Mode Depending on the I/O 11.10 Notes on Reconfiguration in RUN Mode Depending on the I/O 11.10.1 Modules in IO devices of the type ET 200SP HA Principle If you are planning plant changes in RUN using CiR, pay attention to the following information even during the planning phase of the ET 200SP HA stations: ●...
  • Page 191 Plant changes in RUN - CiR 11.10 Notes on Reconfiguration in RUN Mode Depending on the I/O Rules for CiR The new DP slave must be assigned a higher station number than all previously configured DP Slaves. Since the total made up of the station number of the added DP slave and the number of slaves that can be added can be at most 125, we recommend that the station number for the added DP slave be selected as follows: Station number of the added DP slave = the highest station number of all previously...
  • Page 192 Plant changes in RUN - CiR 11.10 Notes on Reconfiguration in RUN Mode Depending on the I/O Adding a DP/PA Coupler with Corresponding PA Slaves to an Existing PA Master System Adding a DP/PA coupler with corresponding PA slave system downstream of an existing DP/PA link corresponds with the insertion of multiple PA slaves (Field devices) in an existing PA master system.

  • Page 193: Modules In Et 200M Modular Slaves

    Plant changes in RUN - CiR 11.10 Notes on Reconfiguration in RUN Mode Depending on the I/O Adding a DP/PA Link with PA Master System Adding a DP/PA link and its corresponding PA master system corresponds with the insertion of a new DP slave in an existing DP master system. 11.10.3 Modules in ET 200M Modular Slaves Principle...

  • Page 194: Modules In Et200Isp Modular Slaves

    Plant changes in RUN - CiR 11.11 Effects on the process when re-configuring in RUN Rules for System Modification During Runtime ● You may only add or remove modules immediately after the last existing module. Always avoid gaps between modules. ●...

  • Page 195: Behavior Of The Cpu After Download Of The Configuration In Run

    Plant changes in RUN - CiR 11.11 Effects on the process when re-configuring in RUN Operating system function Effects Time system The timers continue running. The cycles for time-of-day interrupt, cyclic interrupt and time- delay interrupt continue running but the interrupts them- selves are locked.

  • Page 196: Error Displays

    Plant changes in RUN - CiR 11.11 Effects on the process when re-configuring in RUN 11.11.2.2 Error displays LED Displays during Reconfiguration The INTF LED is lit from the start of the consistency check until completion of SDB evaluation. The light will remain on if module parameters are being changed. After the CiR operation, the preset configuration and the actual configuration will differ (the preset configuration is changed after you have downloaded a configuration change to the CPU) and the EXTF LED is lit.

  • Page 197: Plant Changes During Redundant Operation - H-Cir

    Plant changes during redundant operation - H-CiR 12.1 The H-CiR wizard The H-CiR wizard helps you with plant changes during redundant operation. It allows you to download a modified configuration without interrupting operation. Note Using the H-CiR wizard Use the H-CiR wizard for H-CiR operations. This minimizes the risk of inconsistencies and avoids bumps during a plant change.

  • Page 198: Replacing Central Components

    Plant changes during redundant operation - H-CiR 12.2 Replacing central components 12.2 Replacing central components Which central components can be modified? The following changes can be made to the hardware configuration during operation: ● Changing certain CPU parameters ● Re-configuring a module ●...

  • Page 199: Addition Of Interface Modules

    Plant changes during redundant operation - H-CiR 12.3 Addition of interface modules 12.3 Addition of interface modules You can only add the IM 460 and IM 461 interface modules, the external CP 443-5 Extended DP master interface module or the relevant connecting cables when the system is de- energized.
  • Page 200 Plant changes during redundant operation - H-CiR 12.3 Addition of interface modules 9. Switch to CPU with modified configuration. – In SIMATIC Manager, select a CPU of the fault-tolerant system, then select "PLC > Mode" from the menu. – In the "Mode" dialog box, click "Switch to..." –...

  • Page 201: Motivation For H-Cir Via Profinet Io

    Plant changes during redundant operation - H-CiR 12.4 Motivation for H-CiR via PROFINET IO 12.4 Motivation for H-CiR via PROFINET IO When it is possible to perform plant changes in process mode / RUN during redundant operation, this enables a high availability of the plant. The H-CiR procedure relies on already defined and implemented procedures of fault-tolerant systems.

  • Page 202: Permitted Changes Over Profinet Io

    Plant changes during redundant operation - H-CiR 12.5 Permitted changes over PROFINET IO Requirements ● Fault-tolerant system as 1oo2 system ● Redundant PNIO subsystems ● Connection of two switched IO devices with CiR capability that operate simple I/O The following boundary conditions apply: ●...
  • Page 203 Plant changes during redundant operation - H-CiR 12.5 Permitted changes over PROFINET IO Permitted configuration changes for PROFINET IO The process introduced here supports the following changes to your AS: ● Adding and removing IO systems. ● Adding and removing IO controllers. ●...

  • Page 204: Motivation For H-Cir Via Profibus Dp

    Plant changes during redundant operation - H-CiR 12.6 Motivation for H-CiR via PROFIBUS DP 12.6 Motivation for H-CiR via PROFIBUS DP In addition to the options described in Replacement of failed components during redundant operation (Page 223) for replacing failed components in RUN, you can also make plant changes with CPU 410 in redundant mode without interrupting the program that is running.

  • Page 205: Permitted Changes Over Profibus Dp

    More detailed information can be found in the 7, Configuration Manual See also Modifying the System during Operation via CiR (http://support.automation.siemens.com/WW/view/en/14044916) 12.7 Permitted changes over PROFIBUS DP How is hardware modified? If the hardware components concerned can be unplugged or plugging in live, the hardware modification can be carried out in the redundant system state.
  • Page 206 Plant changes during redundant operation - H-CiR 12.7 Permitted changes over PROFIBUS DP Which distributed components can be modified? The following changes can be made to the hardware configuration during operation: ● Adding or removing components of the distributed I/O such as –...

  • Page 207: Adding Components

    Plant changes during redundant operation - H-CiR 12.8 Adding components 12.8 Adding components The same procedure applies for adding components irrespective of whether the distributed I/O is connected over PROFIBUS DP or over PROFINET IO. Starting situation You have ensured that the CPU parameters (for example the monitoring times) are compatible with the planned new program.

  • Page 208: Change Hardware Configuration Offline

    Plant changes during redundant operation - H-CiR 12.8 Adding components Procedure 1. Add the new components to the system. – Insert new central modules in the rack. – Insert new modules in existing modular DP stations – Add new DP stations to existing DP master systems. –...

  • Page 209: Opening The H-Cir Wizard

    Plant changes during redundant operation - H-CiR 12.8 Adding components 12.8.3 Opening the H-CiR wizard The next steps, except for changing and loading the user program, are performed by the H- CiR wizard. Reaction of the I/O to the new master CPU While the previous master CPU is still in STOP, the I/O reacts to the new master CPU as follows: Type of I/O...

  • Page 210: Modify And Download The User Program

    Plant changes during redundant operation - H-CiR 12.8 Adding components Reaction to exceeding the monitoring times When one of the monitored timers exceeds the configured maximum value, the update is aborted and no master switchover is performed. The H system remains in solo mode with the previous master CPU and attempts to later perform the master switchover under certain conditions.

  • Page 211: Use Of Free Channels On An Existing Module

    Plant changes during redundant operation - H-CiR 12.9 Removal of components 12.8.5 Use of free channels on an existing module The use of previously free channels of an I/O module depends mainly on the fact if the module can be configured or not. Non-configurable modules Free channels can be switched and used in the user program at any time in case of non- configurable modules.

  • Page 212: Change Hardware Configuration Offline

    Plant changes during redundant operation - H-CiR 12.9 Removal of components The modules to be removed and their connected sensors and actuators are no longer of any significance to the process being controlled. The fault-tolerant system is operating in the redundant system state.

  • Page 213: Modify And Download The User Program

    Plant changes during redundant operation - H-CiR 12.9 Removal of components 12.9.2 Modify and download the user program Starting situation The fault-tolerant system is operating in redundant system mode. CAUTION The following program modifications are not possible in redundant system mode and result in the system mode Stop (both CPUs in STOP mode): •...

  • Page 214: Opening The H-Cir Wizard

    Plant changes during redundant operation - H-CiR 12.9 Removal of components 12.9.3 Opening the H-CiR wizard The next steps, except for the conversion of the hardware, are performed by the H-CiR wizard. Reaction of the I/O to the new master CPU While the previous master CPU is still in STOP, the I/O reacts to the new master CPU as follows: Type of I/O...

  • Page 215: Modify Hardware

    Plant changes during redundant operation - H-CiR 12.9 Removal of components 12.9.4 Modify hardware Starting situation The fault-tolerant system is operating with the new hardware configuration in the redundant system state. Procedure 1. Disconnect all the sensors and actuators from the components you want to remove. 2.

  • Page 216: Removal Of Interface Modules

    Plant changes during redundant operation - H-CiR 12.9 Removal of components 12.9.5 Removal of interface modules Always switch off the power before you remove the IM460 and IM461 interface modules, external CP 443-5 Extended DP master interface module, and their connecting cables. Always switch off power to an entire subsystem.

  • Page 217: Editing Cpu Parameters

    Plant changes during redundant operation - H-CiR 12.10 Editing CPU parameters 9. Switch to CPU with modified configuration. – In SIMATIC Manager, select a CPU of the fault-tolerant system, then select "PLC > Mode" from the menu. – In the "Mode" dialog box, click "Switch to..." –...
  • Page 218 Plant changes during redundant operation - H-CiR 12.10 Editing CPU parameters Table 12- 1 Modifiable CPU parameters Editable parameter Startup Monitoring time for signaling readiness by modules Monitoring time for transferring parameters to modules Cycle/clock memory Cycle load due to communication Memory Local data for the individual priority classes Time-of-day interrupts (for each time-of-...

  • Page 219: Changing Cpu Parameters Offline

    Plant changes during redundant operation - H-CiR 12.10 Editing CPU parameters 12.10.2 Changing CPU parameters offline Starting situation The fault-tolerant system is operating in redundant system mode. Procedure 1. Edit the relevant CPU properties offline in HW Config. 2. Compile the new hardware configuration, but do not load it into the target system just yet. Result The modified hardware configuration is in the PG/ES.

  • Page 220: Re-Parameterization Of A Module

    Plant changes during redundant operation - H-CiR 12.11 Re-parameterization of a module Reaction to exceeding the monitoring times When one of the monitored timers exceeds the configured maximum value, the update is aborted and no master switchover is performed. The H system remains in solo mode with the previous master CPU and attempts to later perform the master switchover under certain conditions.

  • Page 221: Editing Parameters Offline

    Plant changes during redundant operation - H-CiR 12.11 Re-parameterization of a module 12.11.2 Editing parameters offline Starting situation The fault-tolerant system is operating in redundant system mode. Procedure 1. Edit the module parameters offline in HW Config. 2. Compile the new hardware configuration, but do not load it into the target system just yet. Result The modified hardware configuration is in the PG/ES.
  • Page 222 Plant changes during redundant operation - H-CiR 12.11 Re-parameterization of a module Reaction to exceeding the monitoring times When one of the monitored timers exceeds the configured maximum value, the update is aborted and no master switchover is performed. The H system remains in solo mode with the previous master CPU and attempts to later perform the master switchover under certain conditions.

  • Page 223: Replacement Of Failed Components During Redundant Operation

    Replacement of failed components during redundant operation Note Components in redundant mode Only components with the same product version, the same article number and the same version can be operated redundantly. If a component is no longer available as spare part, you must replace both components so that this condition is met once again.
  • Page 224 Replacement of failed components during redundant operation 13.1 Replacement of central components CAUTION Caution when replacing a CPU If you reuse a CPU that has previously been used at a different location, ensure that the contents backed up in the load memory cannot pose a hazard at the new point of use. Reset the CPU to factory settings if its previous use is unknown.

  • Page 225: Replacement Of A Power Supply Module

    Replacement of failed components during redundant operation 13.1 Replacement of central components CAUTION Wiring synchronization modules crosswise If you wire synchronization modules crosswise, i.e. the IF1 interface of the first CPU with the IF2 interface of the second CPU and vice versa, the two CPUs take over the master role and the system will now function properly.

  • Page 226: Replacement Of An Input/Output Module Or Function Module

    Replacement of failed components during redundant operation 13.1 Replacement of central components Note Redundant power supply If you use a redundant power supply with two PS 407 10A R or PS 405 10A R, two power supply modules are assigned to one fault-tolerant CPU. The associated CPU continues to run if one of the redundant power supply modules fails.

  • Page 227: Replacement Of A Communication Module

    Replacement of failed components during redundant operation 13.1 Replacement of central components To replace signal and function modules of an S7-400, perform the following steps: Step What to do? How does the system react? Disconnect the module from its peripheral power supply, if necessary.

  • Page 228: Replacement Of Synchronization Module Or Fiber-Optic Cable

    Replacement of failed components during redundant operation 13.1 Replacement of central components Starting situation Failure How does the system react? The S7-400H is in redundant system mode and a Both CPUs report the event in the diagnostic • communication module fails. buffer and via appropriate OBs.
  • Page 229 Replacement of failed components during redundant operation 13.1 Replacement of central components Starting situation Failure How does the system react? Failure of a fiber-optic cable or synchronization Master CPU reports the event in the diagnos- • module: tic buffer and through OB 72 or OB 82. The S7-400H is in the redundant system state The standby CPU switches to ERROR- •...
  • Page 230 Replacement of failed components during redundant operation 13.1 Replacement of central components Starting situation Failure How does the system react? Simultaneous failure of both fiber-optic cables Both CPUs report the event in the diagnostic • The S7-400H is in the redundant system state buffer and via OB 72.

  • Page 231: Replacement Of An Im 460 And Im 461 Interface Module

    Replacement of failed components during redundant operation 13.2 Replacement of components of the distributed I/O on PROFINET IO 13.1.6 Replacement of an IM 460 and IM 461 interface module Starting situation Failure How does the system react? The S7-400H is in redundant system mode and The connected expansion unit is turned off.

  • Page 232: Replacement Of Profinet Io Cables

    Replacement of failed components during redundant operation 13.2 Replacement of components of the distributed I/O on PROFINET IO Procedure Proceed as follows to change an IO device: Step What to do? How does the system react? Switch off the power supply to the IO de- OB 86 and OB85 are called, the LED REDF vice.

  • Page 233: Replacement Of Components Of The Distributed I/O On Profibus Dp

    Replacement of failed components during redundant operation 13.3 Replacement of components of the distributed I/O on PROFIBUS DP Replacement procedure Proceed as follows to change PROFINET IO cables: Step What to do? How does the system react? Check the wiring and identify the faulty PROFINET IO cable.

  • Page 234: Replacement Of A Profibus Dp Master

    Replacement of failed components during redundant operation 13.3 Replacement of components of the distributed I/O on PROFIBUS DP Replacement of signal and function modules CAUTION Note the different procedures. Minor injury or damage to equipment is possible. The procedure for replacing and input/output or function module differs for modules of the S7-300 and S7-400.
  • Page 235 Replacement of failed components during redundant operation 13.3 Replacement of components of the distributed I/O on PROFIBUS DP Procedure Proceed as follows to change a PROFIBUS DP master: Step What to do? How does the system react? Turn off the power supply of the central The fault-tolerant system switches to solo rack.

  • Page 236: Replacement Of A Redundant Profibus Dp Interface Module

    Replacement of failed components during redundant operation 13.3 Replacement of components of the distributed I/O on PROFIBUS DP See also The H-CiR wizard (Page 197) 13.3.2 Replacement of a redundant PROFIBUS DP interface module Starting situation Failure How does the system react? The S7-400H is in redundant system mode and a Both CPUs report the event in the diagnostic PROFIBUS DP interface module (IM 153–2, IM...

  • Page 237: Replacement Of Profibus Dp Cables

    Replacement of failed components during redundant operation 13.3 Replacement of components of the distributed I/O on PROFIBUS DP Procedure Proceed as follows to replace a DP slave: Step What to do? How does the system react? Turn off the supply for the DP slave. With one-sided I/O: OB 86 and OB85 are called for access errors during the PA up- date.
  • Page 238 Replacement of failed components during redundant operation 13.3 Replacement of components of the distributed I/O on PROFIBUS DP Replacement procedure Proceed as follows to replace PROFIBUS DP cables: Step What to do? How does the system react? Check the cabling and localize the –...

  • Page 239: Synchronization Modules

    Synchronization modules 14.1 Synchronization modules for the CPU 410. Function of the synchronization modules Synchronization modules are used synchronization link between two redundant CPU 410- 5H. You require two synchronization modules per CPU, connected in pairs by fiber-optic cable. The system supports hot-swapping of synchronization modules, and so allows you to influence the repair response of the fault-tolerant systems and to control the failure of the redundant connection without stopping the plant.
  • Page 240 Synchronization modules 14.1 Synchronization modules for the CPU 410. Mechanical configuration Figure 14-1 Synchronization modules 6ES7 960-1AA08-0XA0 and 6ES7 960-1Ax06-0xA0 CAUTION Risk of injury. The synchronization module is equipped with a laser system and is classified as a "CLASS 1 LASER PRODUCT" according to IEC 60825–1. Avoid direct contact with the laser beam.
  • Page 241 Synchronization modules 14.1 Synchronization modules for the CPU 410. ● Violation of lower limit The sent or received optical performance is low or too low. ● Violation of upper limit The sent or received optical performance is high or too high. ●...
  • Page 242 Synchronization modules 14.1 Synchronization modules for the CPU 410. 5. Repeat steps 1 to 4 for the second synchronization module. 6. Repeat the process for the second fault-tolerant CPU. Connect the IF1 interface of the first CPU with the IF1 interface of the second CPU and the IF2 interface of the first CPU with the IF2 interface of the second CPU.

  • Page 243: Installation Of Fiber-Optic Cables

    ● Damage on sharp edges etc. Permitted bending radius for prefabricated cables The following bending radii must not be undershot when installing the cables (6ES7960– 1AA04–5xA0) prefabricated by SIEMENS. ● During installation: 88 mm (repeated) ● After installation: 59 mm (one-time)
  • Page 244 Synchronization modules 14.2 Installation of fiber-optic cables Local quality assurance Check the points outlined below before you install the fiber-optic cables: ● Does the delivered package contain the correct fiber-optic cables? ● Any visible transport damage to the product? ● Have you organized a suitable intermediate on-site storage for the fiber-optic cables? ●...

  • Page 245: Selecting Fiber-Optic Cables

    Synchronization modules 14.3 Selecting fiber-optic cables Cable pull-in Note the points below when pulling-in fiber-optic cables: ● Always observe the information on pull forces in the data sheet of the corresponding fiber-optic cable. ● Do not reel off any greater lengths when you pull in the cables. ●...
  • Page 246 Synchronization modules 14.3 Selecting fiber-optic cables Cable length up to 10 m The synchronization module 6ES7 960–1AA06–0XA0 can be operated in pairs with fiber- optic cables up to a length of 10 m. Select cables with the following specification for lengths up to 10 m: ●...
  • Page 247 Synchronization modules 14.3 Selecting fiber-optic cables The table below shows the further specifications, based on your application: Table 14- 2 Specification of fiber-optic cables for indoor applications Cabling Components required Specification The entire cabling is routed Patch cables 2 x duplex cables per system within a building Connector type LC–LC No cable junction is required...
  • Page 248 Synchronization modules 14.3 Selecting fiber-optic cables Table 14- 3 Specification of fiber-optic cables for outdoor applications Cabling Components required Specification A cable junction is required Installation cables for outdoor applications Installation cables for • between the indoor and out- outdoor applications 1 cable with 4 cores per fault-tolerant system •...
  • Page 249 Synchronization modules 14.3 Selecting fiber-optic cables Cabling Components required Specification A cable junction is required One distribution/junction box Connector type ST or SC, for example, to match • • between the indoor and out- per branch other components door area Installation and patch cables are see Figure 12-2 connected via the distribution box.
  • Page 250 Synchronization modules 14.3 Selecting fiber-optic cables CPU 410 Process Automation/CPU 410 SMART System Manual, 05/2017, A5E31622160-AC...

  • Page 251: System Expansion Card

    System expansion card 15.1 Variants of the system expansion card Use of the system expansion card The system expansion card (SEC) is inserted in a slot at the back of the CPU. The SEC is used to scale the CPU 410 to correspond the maximum loadable process objects.
  • Page 252 System expansion card 15.1 Variants of the system expansion card Figure 15-1 Increasing number of PO/enabling R1 redundancy You can increase the number of POs in a CPU 410-5H without changing the SEC. PCS 7 process control You can find information on how to increase the number of POs in system, service support and diagnostics (V8.1 or higher) The procedure for increasing the number of PO also applies for transferring the license key...

  • Page 253: Technical Data

    Technical data 16.1 Technical specifications of CPU 410-5H; (6ES7410-5HX08-0AB0) Article number 6ES7410-5HX08-0AB0 General information Product type designation CPU 410-5H Process Automation Hardware product version Firmware version V8.2 Design of PLC basic unit With Conformal Coating (ISA-S71.04 severity level G1; G2; G3) and operating temperature to 70 °C Product function Yes;...
  • Page 254 Technical data 16.1 Technical specifications of CPU 410-5H; (6ES7410-5HX08-0AB0) Article number 6ES7410-5HX08-0AB0 Backup present • Yes; all data with battery • Yes; Program and data of the load memory without battery • Battery Backup battery 370 µA; Valid up to 40°C Backup current, typ.
  • Page 255 Technical data 16.1 Technical specifications of CPU 410-5H; (6ES7410-5HX08-0AB0) Article number 6ES7410-5HX08-0AB0 S7 times 2 048 Number • Data areas and their retentivity retentive data area in total Total working and load memory (with backup battery) Address area I/O address area 16 kbyte;...
  • Page 256 Technical data 16.1 Technical specifications of CPU 410-5H; (6ES7410-5HX08-0AB0) Article number 6ES7410-5HX08-0AB0 via CP • Number of operable FMs and CPs (recommend- 11; Of which max. 10 CP as DP master PROFIBUS and Ethernet CPs • Slots required slots • Time of day Clock Hardware clock (real-time)
  • Page 257 Technical data 16.1 Technical specifications of CPU 410-5H; (6ES7410-5HX08-0AB0) Article number 6ES7410-5HX08-0AB0 Functionality PROFIBUS DP master • PROFIBUS DP slave • DP master Number of connections, max. • 12 Mbit/s Transmission rate, max. • Number of DP slaves, max. • 1 632 Number of slots per interface, max.
  • Page 258 Technical data 16.1 Technical specifications of CPU 410-5H; (6ES7410-5HX08-0AB0) Article number 6ES7410-5HX08-0AB0 Autocrossing System redundancy Redundant subnetworks Change of IP address at runtime, supported Number of connection resources Interface types Number of ports • integrated switch • Media redundancy supported •...
  • Page 259 Technical data 16.1 Technical specifications of CPU 410-5H; (6ES7410-5HX08-0AB0) Article number 6ES7410-5HX08-0AB0 250 µs to 512 ms, minimum value depends on – Updating time the number of configured user data and the con- figured single or redundant mode Address area 8 kbyte;...
  • Page 260 Technical data 16.1 Technical specifications of CPU 410-5H; (6ES7410-5HX08-0AB0) Article number 6ES7410-5HX08-0AB0 – S7 routing – S7 communication – Open IE communication No; however, usable as part of S7 – Shared device – Prioritized startup – Number of connectable IO Devices, max.
  • Page 261 Technical data 16.1 Technical specifications of CPU 410-5H; (6ES7410-5HX08-0AB0) Article number 6ES7410-5HX08-0AB0 Protocols (Ethernet) TCP/IP • Further protocols Yes; via DP/FF Link Foundation Fieldbus • Yes; Via add-on MODBUS • Communication functions PG/OP communication Number of connectable OPs without mes- •...
  • Page 262 Technical data 16.1 Technical specifications of CPU 410-5H; (6ES7410-5HX08-0AB0) Article number 6ES7410-5HX08-0AB0 Alarm 8-blocks 10 000 Number of instances for alarm 8 and S7 • communication blocks, max. 10 000 preset, max. • Process control messages Test commissioning functions Status block Single step Number of breakpoints Status/control...

  • Page 263: Technical Specifications Of Cpu 410E (6Es7410-5Hm08-0Ab0)

    Technical data 16.2 Technical specifications of CPU 410E (6ES7410-5HM08-0AB0) Article number 6ES7410-5HX08-0AB0 Dimensions Width 50 mm Height 290 mm Depth 219 mm Weights Weight, approx. 1.1 kg 16.2 Technical specifications of CPU 410E (6ES7410-5HM08-0AB0) Article number 6ES7410-5HM08-0AB0 General information Product type designation CPU 410E Process Automation Hardware product version Firmware version...
  • Page 264 Technical data 16.2 Technical specifications of CPU 410E (6ES7410-5HM08-0AB0) Article number 6ES7410-5HM08-0AB0 Dependent on the System Expansion Card used expandable • Load memory 48 Mbyte integrated RAM, max. • expandable RAM • Backup present • Yes; all data with battery •...
  • Page 265 Technical data 16.2 Technical specifications of CPU 410E (6ES7410-5HM08-0AB0) Article number 6ES7410-5HM08-0AB0 Counters, timers and their retentivity S7 counter 2 048 Number • Retentivity – adjustable S7 times 2 048 Number • Data areas and their retentivity retentive data area in total Total working and load memory (with backup battery) Address area...
  • Page 266 Technical data 16.2 Technical specifications of CPU 410E (6ES7410-5HM08-0AB0) Article number 6ES7410-5HM08-0AB0 Number of operable FMs and CPs (recommend- CP, LAN • PROFIBUS and Ethernet CPs • Slots required slots • Time of day Clock Hardware clock (real-time) • retentive and synchronizable •...
  • Page 267 Technical data 16.2 Technical specifications of CPU 410E (6ES7410-5HM08-0AB0) Article number 6ES7410-5HM08-0AB0 PROFIBUS DP slave • DP master Number of connections, max. • 12 Mbit/s Transmission rate, max. • Number of DP slaves, max. • 1 632 Number of slots per interface, max. •...
  • Page 268 Technical data 16.2 Technical specifications of CPU 410E (6ES7410-5HM08-0AB0) Article number 6ES7410-5HM08-0AB0 Redundant subnetworks Change of IP address at runtime, supported Number of connection resources Interface types Number of ports • integrated switch • Media redundancy supported • < 200 ms Switchover time on line break, typ.
  • Page 269 Technical data 16.2 Technical specifications of CPU 410E (6ES7410-5HM08-0AB0) Article number 6ES7410-5HM08-0AB0 Address area 1 536 kbyte; Up to 1 500 IOs (channels) – Inputs, max. 1 536 kbyte; Up to 1 500 IOs (channels) – Outputs, max. 1 024 byte –...
  • Page 270 Technical data 16.2 Technical specifications of CPU 410E (6ES7410-5HM08-0AB0) Article number 6ES7410-5HM08-0AB0 – Open IE communication No; however, usable as part of S7 – Shared device – Prioritized startup – Number of connectable IO Devices, max. – Number of connectable IO Devices for RT, max.
  • Page 271 Technical data 16.2 Technical specifications of CPU 410E (6ES7410-5HM08-0AB0) Article number 6ES7410-5HM08-0AB0 Further protocols Yes; via DP/FF Link Foundation Fieldbus • Yes; Via add-on MODBUS • Communication functions PG/OP communication Number of connectable OPs without mes- • sage processing 119; When using Alarm_S/SQ and Alarm_D/DQ Number of connectable OPs with message •...
  • Page 272 Technical data 16.2 Technical specifications of CPU 410E (6ES7410-5HM08-0AB0) Article number 6ES7410-5HM08-0AB0 10 000 Number of instances for alarm 8 and S7 • communication blocks, max. 10 000 preset, max. • Process control messages Test commissioning functions Status block Single step Number of breakpoints Status/control Status/control variable...

  • Page 273: Technical Specifications Of The System Expansion Card

    Technical data 16.3 Technical specifications of the system expansion card Article number 6ES7410-5HM08-0AB0 Dimensions Width 50 mm Height 290 mm Depth 219 mm Weights Weight, approx. 1.1 kg 16.3 Technical specifications of the system expansion card PCS7 System Expansion Card PO 0 Article number 6ES7653-2CH00-0XB0 General information...
  • Page 274 Technical data 16.3 Technical specifications of the system expansion card Article number 6ES7653-2CH00-0XB0 8 192; max. Outputs • Standards, approvals, certificates CE mark CSA approval UL approval cULus FM approval RCM (formerly C-TICK) KC approval EAC (formerly Gost-R) Use in hazardous areas ATEX II 3G Ex nA IIC T4 Gc ATEX •...
  • Page 275 Technical data 16.3 Technical specifications of the system expansion card Article number 6ES7653-2CA00-0XB0 Address area I/O address area Use of 16 KB in the CPU 410-5H Inputs • Use of 16 KB in the CPU 410-5H Outputs • of which distributed 6 kbyte;...
  • Page 276 Technical data 16.3 Technical specifications of the system expansion card PCS7 System Expansion Card PO 500 Article number 6ES7653-2CC00-0XB0 General information Product type designation PCS 7 System Expansion Card PO 500 Hardware product version Firmware version V2.0 Design of PLC basic unit With Conformal Coating (ISA-S71.04 severity level G1;...
  • Page 277 Technical data 16.3 Technical specifications of the system expansion card Article number 6ES7653-2CC00-0XB0 Use in hazardous areas ATEX II 3G Ex nA IIC T4 Gc ATEX • Ambient conditions Ambient temperature during operation 0 °C min. • 70 °C max. •...
  • Page 278 Technical data 16.3 Technical specifications of the system expansion card Article number 6ES7653-2CE00-0XB0 Digital channels 131 072; max. Inputs • 131 072; max. Outputs • Analog channels 8 192; max. Inputs • 8 192; max. Outputs • Standards, approvals, certificates CE mark CSA approval UL approval...
  • Page 279 Technical data 16.3 Technical specifications of the system expansion card Article number 6ES7653-2CF00-0XB0 Memory PCS 7 process objects 1 600; PO for CPU 410-5H; expandable by means of CPU 410 Expansion Pack PO 100 or PO 500 Work memory Use of max. 31.5 MB work memory in the CPU integrated •...
  • Page 280 Technical data 16.3 Technical specifications of the system expansion card Article number 6ES7653-2CF00-0XB0 Height 16 mm Depth 25 mm Weights Weight, approx. 20 g PCS7 System Expansion Card PO 2k+ Article number 6ES7653-2CG00-0XB0 General information Product type designation PCS 7 System Expansion Card PO 2k+ Hardware product version Firmware version V2.0...
  • Page 281 Technical data 16.3 Technical specifications of the system expansion card Article number 6ES7653-2CG00-0XB0 cULus FM approval RCM (formerly C-TICK) KC approval EAC (formerly Gost-R) Use in hazardous areas ATEX II 3G Ex nA IIC T4 Gc ATEX • Ambient conditions Ambient temperature during operation 0 °C min.
  • Page 282 Technical data 16.3 Technical specifications of the system expansion card Article number 6ES7653-2CB00-0XB0 1 536 byte; Up to 1 500 IOs (channels) – PROFINET interface, inputs 1 536 byte; Up to 1 500 IOs (channels) – PROFINET interface, outputs Digital channels 16 384;...

  • Page 283: Properties And Technical Specifications Of Cpu 410 Smart

    Properties and technical specifications of CPU 410 SMART 17.1 CPU 410 SMART CPU 410-5H and CPU 410 SMART Note Except for the special features described in this section, CPU 410 SMART reacts like a CPU 410. While taking this section into consideration, the statements made in this manual about CPU 410 also apply to the CPU 410 SMART.
  • Page 284 If you have nevertheless enabled hardware interrupts on I/O modules with interrupt capability and a hardware interrupt is generated, it is merely entered in the diagnostics buffer and the SFC is not executed. See also AS 410 modular systems (http://support.automation.siemens.com/WW/view/en/77430465/130000) CPU 410 Process Automation/CPU 410 SMART System Manual, 05/2017, A5E31622160-AC...

  • Page 285: Technical Specifications Of The Cpu 410 Smart; (6Es7 410-5Hn08-0Ab0)

    Properties and technical specifications of CPU 410 SMART 17.2 Technical specifications of the CPU 410 SMART; (6ES7 410-5HN08-0AB0) 17.2 Technical specifications of the CPU 410 SMART; (6ES7 410- 5HN08-0AB0) Article number 6ES7410-5HN08-0AB0 General information Product type designation CPU 410 SMART Process Automation Hardware product version Firmware version V8.2...
  • Page 286 Properties and technical specifications of CPU 410 SMART 17.2 Technical specifications of the CPU 410 SMART; (6ES7 410-5HN08-0AB0) Article number 6ES7410-5HN08-0AB0 Yes; Program and data of the load memory without battery • Battery Backup battery 370 µA; Valid up to 40°C Backup current, typ.
  • Page 287 Properties and technical specifications of CPU 410 SMART 17.2 Technical specifications of the CPU 410 SMART; (6ES7 410-5HN08-0AB0) Article number 6ES7410-5HN08-0AB0 Address area I/O address area 16 kbyte Inputs • 16 kbyte Outputs • of which distributed 1 536 byte; Up to 1 500 IOs (channels) –...
  • Page 288 Properties and technical specifications of CPU 410 SMART 17.2 Technical specifications of the CPU 410 SMART; (6ES7 410-5HN08-0AB0) Article number 6ES7410-5HN08-0AB0 Operating hours counter Number • 0 to 15 Number/Number range • SFCs 2, 3 and 4: 0 to 32767 hours SFC 101: 0 to Range of values •...
  • Page 289 Properties and technical specifications of CPU 410 SMART 17.2 Technical specifications of the CPU 410 SMART; (6ES7 410-5HN08-0AB0) Article number 6ES7410-5HN08-0AB0 – Global data communication – S7 basic communication – S7 communication – S7 communication, as client – S7 communication, as server –...
  • Page 290 Properties and technical specifications of CPU 410 SMART 17.2 Technical specifications of the CPU 410 SMART; (6ES7 410-5HN08-0AB0) Article number 6ES7410-5HN08-0AB0 Number of stations in the ring, max. • Functionality PROFINET IO Controller • PROFINET IO Device • PROFINET CBA •...
  • Page 291 Properties and technical specifications of CPU 410 SMART 17.2 Technical specifications of the CPU 410 SMART; (6ES7 410-5HN08-0AB0) Article number 6ES7410-5HN08-0AB0 3. Interface Interface type PROFINET Physics Ethernet RJ45 Isolated automatic detection of transmission rate Yes; Autosensing Autonegotiation Autocrossing System redundancy Redundant subnetworks Number of connection resources Interface types...
  • Page 292 Properties and technical specifications of CPU 410 SMART 17.2 Technical specifications of the CPU 410 SMART; (6ES7 410-5HN08-0AB0) Article number 6ES7410-5HN08-0AB0 – IO Devices changing during operation (partner ports), supported – Device replacement without swap me- dium 250 µs, 500 µs, 1 ms, 2 ms, 4 ms –...
  • Page 293 Properties and technical specifications of CPU 410 SMART 17.2 Technical specifications of the CPU 410 SMART; (6ES7 410-5HN08-0AB0) Article number 6ES7410-5HN08-0AB0 Data record routing S7 routing S7 communication supported • as server • as client • 64 kbyte User data per job, max. •...
  • Page 294 Properties and technical specifications of CPU 410 SMART 17.2 Technical specifications of the CPU 410 SMART; (6ES7 410-5HN08-0AB0) Article number 6ES7410-5HN08-0AB0 Inputs/outputs, memory bits, DBs, distributed Variables • I/Os, timers, counters Number of variables, max. • Diagnostic buffer present • 3 200 Number of entries, max.

  • Page 295: Technical Specifications Of The Sec Po 800

    Properties and technical specifications of CPU 410 SMART 17.3 Technical specifications of the SEC PO 800 17.3 Technical specifications of the SEC PO 800 Core statement Article number 6ES7653-2CM00-0XB0 General information Product type designation PCS 7 System Expansion Card PO 800 Hardware product version Firmware version V2.0...
  • Page 296 Properties and technical specifications of CPU 410 SMART 17.3 Technical specifications of the SEC PO 800 Article number 6ES7653-2CM00-0XB0 Use in hazardous areas ATEX II 3G Ex nA IIC T4 Gc ATEX • Ambient conditions Ambient temperature during operation 0 °C min.

  • Page 297: Supplementary Information

    Supplementary information 18.1 Supplementary information on PROFIBUS DP Monitor/Modify, programming via PROFIBUS You can use the PROFIBUS DP interface to program the CPU or execute the programming device functions Monitor and Modify. Note The "Programming" or "Monitor/Modify" applications prolong the DP cycle if executed via the PROFIBUS DP interface.

  • Page 298: Supplementary Information On Diagnostics Of The Cpu 410 As Profibus Dp Master

    Supplementary information 18.2 Supplementary information on diagnostics of the CPU 410 as PROFIBUS DP master 18.2 Supplementary information on diagnostics of the CPU 410 as PROFIBUS DP master Reading the diagnostics data with STEP 7 Table 18- 1 Reading the diagnostics data with STEP 7 DP master Block or tab in Application...
  • Page 299 Supplementary information 18.2 Supplementary information on diagnostics of the CPU 410 as PROFIBUS DP master Evaluating diagnostics data in the user program The figure below shows how to evaluate the diagnostics data in the user program. Figure 18-1 Diagnostics with CPU 410 CPU 410 Process Automation/CPU 410 SMART System Manual, 05/2017, A5E31622160-AC...
  • Page 300 Supplementary information 18.2 Supplementary information on diagnostics of the CPU 410 as PROFIBUS DP master Event detection The following table shows how the CPU 41xH in DP master mode detects operating state changes on a DP slave or interruptions of the data transfer. Table 18- 2 Event detection of the CPU 41xH as a DP master Event...

  • Page 301: System Status Lists For Profinet Io

    Supplementary information 18.3 System status lists for PROFINET IO 18.3 System status lists for PROFINET IO Introduction The CPU makes certain information available and stores this information in the "System status list". The system status list describes the current status of the automation system. It provides an overview of the configuration, the current parameter assignment, the current statuses and sequences in the CPU, and the assigned modules.

  • Page 302: Configuring With Step 7

    Supplementary information 18.4 Configuring with STEP 7 SSL-ID PROFINET IO PROFIBUS DP Applicability W#16#0D91 Module status information of all modules Parameter adr1 changed in the specified rack/station No, external interface W#16#xy92 Rack/station status information Replacement: SSL-ID Replace this system status list with the W#16#0x94 system status list with ID W#16#xy94 in PROFIBUS DP, as well.

  • Page 303: Configuring Hardware

    Supplementary information 18.4 Configuring with STEP 7 Layout rules ● If there are not enough slots in the central controllers, you can increase the configuration of an H system with expansion units. ● A fault-tolerant station may contain up to 20 expansion units. ●...

  • Page 304: Assigning Parameters To Modules In A Fault-Tolerant Station

    Supplementary information 18.4 Configuring with STEP 7 Specific aspects of the hardware configuration display The redundant DP master system and PN/IO system are displayed by two lines close together to make them easy to identify. 18.4.3 Assigning parameters to modules in a fault-tolerant station Procedure Assign all parameters of the redundant components identically, with the exception of communication addresses.

  • Page 305: Networking Configuration

    If your fault-tolerant system does not link up, check the data memory allocation (HW Config > CPU Properties > H Parameters > Work memory used for all data blocks). See also Service & Support (http://www.siemens.com/automation/service&support) 18.4.5 Networking configuration The fault-tolerant S7 connection is a separate connection type of the "Configure Networks"...

  • Page 306: The Step 7 User Program

    Supplementary information 18.5 The STEP 7 user program When this connection type is configured, the application automatically determines the number of possible subconnections: ● If two independent but identical subnets are available and they are suitable for a fault- tolerant S7 connection, two subconnections are used. In practice, they are usually electrical networks, one network connection in each subnet: ●...
  • Page 307 Supplementary information 18.5 The STEP 7 user program However, we offer you several specific blocks for optimizing your user program, e.g. in order to improve its response to the extension of cycle times due to updates. Specific blocks for S7–400H In addition to the blocks supported both in the S7-400 and S7-400H systems, the S7-400H software provides further blocks which you can use to influence the redundancy functions.

  • Page 308: Programming Device Functions In Step 7

    Supplementary information 18.6 Programming device functions in STEP 7 18.6 Programming device functions in STEP 7 Display in SIMATIC Manager In order to do justice to the special features of a fault-tolerant station, the way in which the system is visualized and edited in SIMATIC Manager differs from that of a S7-400 standard station as follows: ●...
  • Page 309 Supplementary information 18.7 Communication services Communication service Functionality Allocation of S7 connection Via DP resources PN/IE PROFINET IO Data exchange between I/O controllers and I/O devices SNMP Standard protocol for network diagnos- tics and parameter assignment (Simple Network Manage- ment Protocol) Open communication over Data exchange over Industrial Ethernet TCP/IP...

  • Page 310: Pg Communication

    Supplementary information 18.7 Communication services 18.7.2 PG communication Properties Programming device communication is used to exchange data between engineering stations (PG, PC, for example) and SIMATIC modules which are capable of communication. This service is available via PROFIBUS and Industrial Ethernet subnets. Routing between subnets is also supported.

  • Page 311: Munication

    Supplementary information 18.7 Communication services called in the user program using SFBs. These functions are independent of specific networks, allowing you to program S7 communication via PROFINET, Industrial Ethernet, or PROFIBUS. S7 communication services provide the following options: ● During system configuration, you configure the connections used by the S7 communication.

  • Page 312: S7 Routing

    Supplementary information 18.7 Communication services Integration into STEP 7 S7 communication offers communication functions through configured S7 connections. You use STEP 7 to configure the connections. S7 connections with an S7-400 are established when the connection data is downloaded. 18.7.5 S7 routing Properties You can access your S7 stations beyond subnet boundaries using the programming device /...
  • Page 313 Supplementary information 18.7 Communication services S7 routing gateways: PN - DP Gateways between subnets are routed in a SIMATIC station that is equipped with interfaces to the respective subnets. The following figure shows CPU 1 (DP master) acting as router for subnets 1 and 2.
  • Page 314 Supplementary information 18.7 Communication services S7 routing gateways: PROFINET IO - DP - PROFINET IO The following figure shows the access from PROFINET IO to PROFIBUS to PROFINET IO. CPU 1 is the router between subnet 1 and subnet 2; CPU 2 is the router between subnet 2 and subnet 3.
  • Page 315 Reference ● Further information on configuration with STEP 7 can be found in Manual Configuring hardware and communication connections with STEP 7 (http://support.automation.siemens.com/WW/view/en/45531110). ● More basic information is available in Manual Communication with SIMATIC (http://support.automation.siemens.com/WW/view/en/1254686). ● For more information about the TeleService adapter, refer to Manual TS Adapter (http://support.automation.siemens.com/WW/view/en/20983182)

  • Page 316: Data Set Routing

    Supplementary information 18.7 Communication services 18.7.6 Data set routing Routing and data set routing Routing is the transfer of data beyond network boundaries. You can send information from a transmitter to a receiver across several networks. Data set routing is an expansion of S7 routing and is used, for example, in SIMATIC PDM. The data sent through data record routing include the parameter assignments of the participating communication devices and device-specific information (for example, setpoint values, limit values, etc.).

  • Page 317: Snmp Network Protocol

    Supplementary information 18.7 Communication services See also The Process Device Manager For more information on SIMATIC PDM, refer to Manual 18.7.7 SNMP network protocol Properties SNMP (Simple Network Management Protocol) is the standardized protocol for diagnostics of the Ethernet network infrastructure. In the office setting and in automation engineering, devices from many different manufacturers support SNMP on the Ethernet.

  • Page 318: Open Communication Via Industrial Ethernet

    Supplementary information 18.7 Communication services 18.7.8 Open Communication Via Industrial Ethernet Functionality The following services are available for open IE communication: ● Connection-oriented protocols: Prior to data transmission connection-oriented protocols establish a logical connection to the communication partner and close this again, if necessary, after transmission is complete.
  • Page 319 Supplementary information 18.7 Communication services How to use open IE communication You can exchange data with other communication partners via the user program. The following FBs and UDTs are available for this in the "Standard Library" of STEP 7 under "Communication Blocks".
  • Page 320 Supplementary information 18.7 Communication services Job lengths and parameters for the different types of connection Table 18- 7 Job lengths and "local_device_id" parameter Protocol type CPU 410-5H CPU 410-5H with CP 443-1 32 KB ISO on TCP 32 KB 1452 bytes 1472 bytes "local_device_id"...

  • Page 321: Basics And Terminology Of Fault-Tolerant Communication

    Supplementary information 18.8 Basics and terminology of fault-tolerant communication Terminating a communication connection ● Use with TCP and ISO on TCP FB 66 "TDISCON" disconnects the communication connection between the CPU and a communication partner. ● Use with UDP FB 66 "TDISCON" disconnects the local communication access point. This means that the connection between the user program and communication layer of the operating system is terminated.
  • Page 322 Supplementary information 18.8 Basics and terminology of fault-tolerant communication Redundant communication system The availability of the communication system can be increased by duplicating subcomponents, duplicating all bus components, or using a fiber-optic ring. Monitoring and synchronization mechanisms ensure that standby components take over communication if one components fails.
  • Page 323 Supplementary information 18.8 Basics and terminology of fault-tolerant communication Note "Connection" in this manual refers in general to a "configured S7 connection". For other SIMATIC NET NCM S7 for PROFIBUS SIMATIC types of connection, refer to Manuals NET NCM S7 for Industrial Ethernet Fault-tolerant S7 connections The requirement for higher availability with communication components (for example CPs and buses) means that redundant communication connections are necessary between the...
  • Page 324 Supplementary information 18.8 Basics and terminology of fault-tolerant communication Figure 18-7 Example that shows that the number of resulting partial connections depends on the configuration If the active subconnection fails, the already established second subconnection automatically takes over communication. CPU 410 Process Automation/CPU 410 SMART System Manual, 05/2017, A5E31622160-AC...

  • Page 325: Usable Networks

    Supplementary information 18.9 Usable networks Resource requirements for fault-tolerant S7 connections The H-CPU enables the operation of 62 (see Technical specifications) fault-tolerant S7 connections. Each connection needs a connection resource on the CPU; subconnections do not need any additional connection resources. On the CP, on the other hand, each subconnection needs a connection resource.

  • Page 326: Communication Via S7 Connections - One-Sided Mode

    Supplementary information 18.10 Communication via S7 connections Note The START and STOP communication functions act on exactly one CPU or on all CPUs of System the fault-tolerant system. More detailed information is available in Reference Manual Software for S7-300/400 System and Standard Functions Note Downloading the connection configuration during operation If you download a connection configuration during operation, established connections may...
  • Page 327 Supplementary information 18.10 Communication via S7 connections Figure 18-9 Example of linking standard and fault-tolerant systems in a redundant bus system If the plant bus is configured as a duplex fiber-optic ring, the communication of the systems involved is maintained if a break of the two-fiber fiber-optic cable occurs. The systems then communicate as if they were connected to a bus system (linear structure);...

  • Page 328: Communication Via Redundant S7 Connections

    Linking standard and fault-tolerant systems Driver block "S7H4_BSR": You can link a fault-tolerant system to an S7-400 / S7-300 using the "S7H4_BSR" driver block. For more information, contact Siemens by e–mail: function.blocks.industry @siemens.com Alternative: SFB 15 "PUT" and SFB 14 "GET" in the fault-tolerant system: As an alternative, use two SFB 15 "PUT"...

  • Page 329: Communication Via Point-To-Point Cp On The Et 200M

    Supplementary information 18.10 Communication via S7 connections connection redundancy. In the user program, both connections require the implementation of monitoring functions in order to allow the detection of failures and to change over to the standby connection. The following figure shows such a configuration. Figure 18-12 Example of redundancy with fault-tolerant systems and a redundant bus system with redundant standard connections Response to failure...
  • Page 330 Supplementary information 18.10 Communication via S7 connections Configuring connections Redundant connections between the point-to-point CP and the fault-tolerant system are not necessary. Figure 18-13 Example of connecting a fault-tolerant system to a single-channel third-party system via switched PROFIBUS DP Figure 18-14 Example of connecting a fault-tolerant system to a single-channel third-party system via PROFINET IO with system redundancy Response to failure Double errors in the fault-tolerant system (i.e., CPUa1 and IM 153) and a single fault in the...

  • Page 331: Custom Connection To Single-Channel Systems

    Supplementary information 18.10 Communication via S7 connections The point-to-point CP can also be inserted centrally in "Fault-tolerant system a". However, in this configuration even the failure of the CPU, for example, will cause a total failure of communication. 18.10.4 Custom connection to single-channel systems Connection via PC as gateway Fault-tolerant systems and single-channel systems can also be via a gateway (no connection redundancy).

  • Page 332: Communication Via Fault-Tolerant S7 Connections

    Supplementary information 18.11 Communication via fault-tolerant S7 connections 18.11 Communication via fault-tolerant S7 connections Availability of communicating systems Fault-tolerant communication expands the overall SIMATIC system by additional, redundant communication components such as CPs and bus cables. To illustrate the actual availability of communicating systems when using an optical or electrical network, a description is given below of the possibilities for communication redundancy.
  • Page 333 Supplementary information 18.11 Communication via fault-tolerant S7 connections Local connec- Local network con- Used network Remote Remote connec- tion nection protocol network connection tion end point end point PC station PC station with Si- CPU-PN interface CPU 41xH S7 fault with Simatic matic Net CD CP443-1 ( EX 30)

  • Page 334: Communication Between Fault-Tolerant Systems

    Supplementary information 18.11 Communication via fault-tolerant S7 connections You program the fault-tolerant communication with STEP 7 using communication SFBs. These communication blocks can be used to transmit data over subnets (Industrial Ethernet, PROFIBUS). The communication SFBs integrated in the operating system enable an acknowledged data transmission.
  • Page 335 Supplementary information 18.11 Communication via fault-tolerant S7 connections Note The number of connection resources required on the CPs depends on the network used. If you implement a duplex fiber-optic ring (see figure below), two connection resources are required per CP. In contrast, only one connection resource is required per CP if a double electrical network (see figure after next) is used.
  • Page 336 Supplementary information 18.11 Communication via fault-tolerant S7 connections Configuration view = Physical view Figure 18-18 Example of fault-tolerant system with additional CP redundancy Configuration view = Physical view You decide during configuration if the additional CPs are used to increase resources or availability.

  • Page 337: Communication Between Fault-Tolerant Systems And A Fault-Tolerant Cpu

    Supplementary information 18.11 Communication via fault-tolerant S7 connections Fault-tolerant S7 connections Any disruption of subconnections while communication jobs are active over fault-tolerant S7 connections leads to extended delay times. 18.11.2 Communication between fault-tolerant systems and a fault-tolerant CPU Availability Availability can be enhanced by using a redundant plant bus and by using a fault-tolerant CPU in a standard system.

  • Page 338: Communication Between Fault-Tolerant Systems And Pcs

    Supplementary information 18.11 Communication via fault-tolerant S7 connections 18.11.3 Communication between fault-tolerant systems and PCs Availability PCs are not fault-tolerant due to their hardware and software characteristics. The availability of a PC (OS) system and its data management is ensured by means of suitable software such as WinCC Redundancy.
  • Page 339 Supplementary information 18.11 Communication via fault-tolerant S7 connections Figure 18-20 Example of redundancy with fault-tolerant system and redundant bus system Figure 18-21 Example of redundancy with a fault-tolerant system, redundant bus system and redundant connection to the PC. Response to failure Double errors in the fault-tolerant system, e.g., CPUa1 and CPa2, or failure of the PC station result in a total failure of communication between the systems involved;...

  • Page 340: Consistent Data

    Supplementary information 18.12 Consistent data PC/PG as Engineering System (ES) To be able to use a PC as Engineering System, you need to configure it under its name as a PC station in HW Config. The ES is assigned to a CPU and is capable of executing STEP 7 functions on that CPU.

  • Page 341: Consistent Reading And Writing Of Data From And To Dp Standard Slaves/Io Devices

    Supplementary information 18.12 Consistent data Evaluate the entire, currently used part of the receive area RD_i before you activate a new request. SFB 15 When a send operation is initiated (rising edge at REQ), the data to be sent from the send areas SD_i are copied from the user program.
  • Page 342 Supplementary information 18.12 Consistent data For information on SFC 15, refer to the corresponding online help and Manual "System and Standard Functions". Note When a send operation is activated (positive edge at REQ), the data to be transmitted from the send areas SD_i is copied from the user program. You can write new data to these areas after the block call command without corrupting the current send data.

  • Page 343: Link-Up And Update Sequence

    Supplementary information 18.13 Link-up and update sequence 18.13 Link-up and update sequence There are two types of link-up and update operation: ● Within a "normal" link-up and update operation, the fault-tolerant system will change over from solo operation to redundant system state. The two CPUs then process the same program synchronously.
  • Page 344 Supplementary information 18.13 Link-up and update sequence Flow chart of the link-up and update operation The figure below outlines the general sequence of the link-up and update. In the initial situation, the master is in solo operation. In the figure, CPU 0 is assumed to be the master CPU.
  • Page 345 Supplementary information 18.13 Link-up and update sequence Figure 18-23 Update sequence CPU 410 Process Automation/CPU 410 SMART System Manual, 05/2017, A5E31622160-AC...

  • Page 346: Link-Up Sequence

    Supplementary information 18.13 Link-up and update sequence Minimum duration of input signals during update Program execution is stopped for a certain time during the update (the sections below describe this in greater detail). To ensure that the CPU can reliably detect changes to input signals during the update, the following condition must be satisfied: Minimum signal duration >...

  • Page 347: Update Sequence

    Supplementary information 18.13 Link-up and update sequence If 3. is inconsistent, the user program in the load memory in RAM is copied from the master CPU to the standby CPU. Link-up with master/standby changeover In STEP 7 you can select one of the following options: ●...
  • Page 348 Supplementary information 18.13 Link-up and update sequence 3. The execution of OB 1 and of all OBs up to priority class 15 is delayed. In the case of cyclic interrupts, the generation of new OB requests is disabled, so no new cyclic interrupts are stored and as a result no new request errors occur.
  • Page 349 Supplementary information 18.13 Link-up and update sequence 9. Transfer of outputs and of all data block contents modified again. Transfer of timers, counters, bit memories, and inputs. Transfer of the diagnostic buffer. During this data synchronization, the system interrupts the clock pulse for cyclic interrupts, time-delay interrupts and S7 timers.
  • Page 350 Supplementary information 18.13 Link-up and update sequence Communication functions and resulting jobs After it has received one of the jobs specified below, the CPU must in turn generate communication jobs and output them to other modules. These include, for example, jobs for reading or writing parameterization data records from/to distributed I/O modules.

  • Page 351: Switch To Cpu With Modified Configuration

    Supplementary information 18.13 Link-up and update sequence 18.13.3 Switch to CPU with modified configuration Switch to CPU with modified configuration You may have modified the hardware configuration on the standby CPU. The necessary steps are described in Section Replacement of failed components during redundant operation (Page 223).

  • Page 352: Disabling Of Link-Up And Update

    Supplementary information 18.13 Link-up and update sequence 18.13.4 Disabling of link-up and update Link-up and update entails a cycle time extension. This includes a period during which no I/O updates are performed; see Chapter Time monitoring (Page 120). You must pay special attention to this if you are using distributed I/O and a master/standby changeover occurs after the update (thus, when the configuration is modified during operation).

  • Page 353: The User Program

    Supplementary information 18.14 The user program 18.14 The user program The rules of developing and programming the user program for the standard S7-400 system also apply to the S7-400H. In terms of user program execution, the S7-400H behaves in the same manner as a standard system.

  • Page 354: Other Options For Connecting Redundant I/Os

    Supplementary information 18.15 Other options for connecting redundant I/Os 18.15 Other options for connecting redundant I/Os Redundant I/O at user level If you cannot use the redundant I/O supported by the system (Chapter Connection of two- channel I/O to the PROFIBUS DP interface (Page 80)), for example, because the module to be used redundantly is not in the list of supported components, you can also implement the use of redundant I/O at the user level.
  • Page 355 Supplementary information 18.15 Other options for connecting redundant I/Os Hardware configuration and project engineering of the redundant I/O Strategy recommended for use of redundant I/O: 1. Use the I/O as follows: – in a one-sided configuration, one signal module in each subsystem –...
  • Page 356 Supplementary information 18.15 Other options for connecting redundant I/Os Figure 18-26 Flow chart for OB 1 Monitoring times during link-up and update Note If you have made I/O modules redundant and have taken account of this in your program, you may need to add an overhead to the calculated monitoring times so that no bumps occur at output modules (in HW Config ->...

  • Page 357: Cpu 410 Cycle And Reaction Times

    Supplementary information 18.16 CPU 410 cycle and reaction times An overhead is only required if you operate modules from the following table as redundant modules. Table 18- 8 For the monitoring times with redundant I/O Module type Overhead in ms ET200M: Standard output modules ET200M: HART output modules ET200M: F-output modules...
  • Page 358 Supplementary information 18.16 CPU 410 cycle and reaction times Sequence of cyclic program processing The table below shows the various phases in cyclic program execution. Table 18- 9 Cyclic program processing Step Sequence The operating system initiates the scan cycle monitoring time. The CPU copies the values from the process output images to the output modules.

  • Page 359: Calculating The Cycle Time

    Supplementary information 18.16 CPU 410 cycle and reaction times 18.16.2 Calculating the cycle time Extending the cycle time The cycle time of a user program is extended by the factors outlined below: ● Time-based interrupt processing ● Hardware interrupt processing (see also Chapter Interrupt response time (Page 373)) ●...
  • Page 360 Supplementary information 18.16 CPU 410 cycle and reaction times K+ portion in the central controller (from row A in the following table) + portion in the expansion device with local connection (from row B) + portion in the expansion device with remote connection (from row C) + portion via integrated DP interface (from row D1) + portion via external DP interface (from row D2) portion of consistent data via integrated DP interface (from row E1)
  • Page 361 Supplementary information 18.16 CPU 410 cycle and reaction times Extending the cycle time The calculated cycle time of a S7-400H CPU must be multiplied by a CPU-specific factor. The table below lists these factors: Table 18- 12 Extending the cycle time Startup CPU 410-5H stand-alone mode CPU 410-5H redundant...

  • Page 362: Cycle Load Due To Communication

    Supplementary information 18.16 CPU 410 cycle and reaction times 18.16.3 Cycle load due to communication The operating system of the CPU provides the configured percentage of the overall CPU processing capacity to the communication on a continuous basis (time slice technique). If this processing capacity is not required for communication, it is made available to the other processing.
  • Page 363 Supplementary information 18.16 CPU 410 cycle and reaction times This means that a setting of 20% communication load allocates an average of 200 µs to communication and 800 µs to the user program in each time slice. So the CPU requires 10 ms / 800 µs = 13 time slices to execute one cycle.

  • Page 364: Response Time

    Supplementary information 18.16 CPU 410 cycle and reaction times Further effects on the actual cycle time Seen statistically, the extension of cycle times due to communication load leads to more asynchronous events occurring within an OB 1 cycle, for example interrupts. This further extends the OB 1 cycle.
  • Page 365 Supplementary information 18.16 CPU 410 cycle and reaction times ● For relay outputs: typical delay times of 10 ms to 20 ms. The delay of relay outputs depends on the temperature and voltage, among other things. ● For analog inputs: cycle time for analog input ●...
  • Page 366 Supplementary information 18.16 CPU 410 cycle and reaction times Shortest response time The figure below shows the conditions under which the shortest response time is achieved. Figure 18-32 Shortest response time Calculation The (shortest) response time is calculated as follows: ●...
  • Page 367 Supplementary information 18.16 CPU 410 cycle and reaction times Longest response time The figure below shows the conditions under which the longest response time is achieved. Figure 18-33 Longest response time Calculation The (longest) response time is calculated as follows: ●...
  • Page 368 Supplementary information 18.16 CPU 410 cycle and reaction times Processing direct I/O access You can achieve faster response times by directly accessing the I/O in your user program, e.g., with the following instructions: ● L PIB ● T PQW However, note that any I/O access requires a synchronization of the two units and thus extends the cycle time.

  • Page 369: Calculating Cycle And Response Times

    Supplementary information 18.16 CPU 410 cycle and reaction times Table 18- 17 Direct access of the CPUs to I/O modules in the expansion unit with remote link, setting 100 m Access type CPU 410-5H CPU 410-5H stand-alone mode redundant Read byte 11.3 µs 16.6 µs Read word...

  • Page 370: Examples Of Calculating The Cycle And Response Times

    Supplementary information 18.16 CPU 410 cycle and reaction times The result is an approximated actual cycle time. Note down the result. Table 18- 18 Example of calculating the response time Shortest response time Longest response time 3. Next, calculate the delays in the inputs and 3.
  • Page 371 Supplementary information 18.16 CPU 410 cycle and reaction times Calculation of the actual cycle time ● Allowance for communication load (default value: 20%): 18.419 ms * 100 / (100–20) = 23.024 ms. ● There is no interrupt processing. So the actual, cycle time is approx. 23 ms. Calculating the longest response time ●...
  • Page 372 Supplementary information 18.16 CPU 410 cycle and reaction times Calculating the cycle time The theoretical cycle time for the example is derived from the following times: ● As the CPU-specific factor is 1.2, the user program execution time is: approx. 12.0 ms ●...

  • Page 373: Interrupt Response Time

    Supplementary information 18.16 CPU 410 cycle and reaction times ● Case 1: The system sets an output channel of the digital output module after a digital input signal is read in. The result is as follows: Response time = 45 ms + 4.8 ms = 49.8 ms. ●...
  • Page 374 Supplementary information 18.16 CPU 410 cycle and reaction times Increasing the maximum interrupt response time with communication The maximum interrupt response time is extended when the communication functions are active. The additional time is calculated using the following formula: CPU 410-5H t = 100 µs + 1000 µs ×...

  • Page 375: Example Of Calculation Of The Interrupt Response Time

    Supplementary information 18.16 CPU 410 cycle and reaction times 18.16.8 Example of calculation of the interrupt response time Elements of the interrupt response time As a reminder: The hardware interrupt response time is made up of the following: ● Hardware interrupt response time of the CPU ●...

  • Page 376: Reproducibility Of Delay And Watchdog Interrupts

    Supplementary information 18.16 CPU 410 cycle and reaction times 18.16.9 Reproducibility of delay and watchdog interrupts Definition of "reproducibility" Time-delay interrupt: The period that expires between the call of the first operation in the interrupt OB and the programmed time of interrupt. Cyclic interrupt: The fluctuation range of the interval between two successive calls, measured between the respective initial operations of the interrupt OB.

  • Page 377: Runtimes Of The Fcs And Fbs For Redundant I/Os

    Supplementary information 18.17 Runtimes of the FCs and FBs for redundant I/Os 18.17 Runtimes of the FCs and FBs for redundant I/Os Table 18- 21 Runtimes of the blocks for redundant I/Os Block Runtime in stand-alone/single mode Runtime in redundant mode FC 450 RED_INIT 2 ms + 300 µs / configured module pairs Specifications are based...
  • Page 378 Supplementary information 18.17 Runtimes of the FCs and FBs for redundant I/Os Block Runtime in stand-alone/single mode Runtime in redundant mode FB 452 RED_DIAG Called in OB 72: 160 µs Called in OB 72: 360 µs Called in OB 82, 83, 85: Called in OB 82, 83, 85: 250 µs + 5 µs / configured module pairs 430 μs (basic load) + 6 μs / configured mod-...

  • Page 379: Characteristic Values Of Redundant Automation Systems

    You will find an overview of the MTBF of various SIMATIC products in the SIMATIC FAQs in the following entry: Mean Time Between Failures (MTBF) list for SIMATIC Products (http://support.automation.siemens.com/WW/view/en/16818490) Basic concepts The quantitative assessment of redundant automation systems is usually based on their reliability and availability parameters.
  • Page 380 Characteristic values of redundant automation systems A.1 Basic concepts Mean Down Time (MDT) The MDT of a system is determined by the times outlined below: ● Time required to detect an error ● Time required to find the cause of an error ●...
  • Page 381 Characteristic values of redundant automation systems A.1 Basic concepts Figure A-2 MTBF Requirements This analysis assumes the following conditions: ● The failure rate of all components and all calculations is based on an average temperature of 40 °C. ● The system installation and configuration is free of errors. ●...
  • Page 382 Characteristic values of redundant automation systems A.1 Basic concepts ● Corrosion ● Vibration and shock ● Electromagnetic interference ● Electrostatic discharge ● RF interference ● Unexpected sequence of events ● Operating errors The CCF factor defines the ratio between the probability of the occurrence of a CCF and the probability of the occurrence of any other error.

  • Page 383: Comparison Of Mtbf For Selected Configurations

    Characteristic values of redundant automation systems A.2 Comparison of MTBF for selected configurations The availability of a system is expressed as a percentage. It is defined by the mean time between failure (MTBF) and the mean time to repair MTTR (MDT). The availability of a two- channel (1-out-of-2) fault-tolerant system can be calculated using the following formula: Figure A-4 Availability...

  • Page 384: System Configurations With Distributed I/Os

    Characteristic values of redundant automation systems A.2 Comparison of MTBF for selected configurations Fault-tolerant CPU in stand-alone operation Fault-tolerant CPU 410-5H in stand-alone mode Factor Redundant CPUs in different racks Redundant CPU 410-5H in divided rack, CCF = 2% Factor approx.
  • Page 385 Characteristic values of redundant automation systems A.2 Comparison of MTBF for selected configurations Redundant CPUs with single-channel one-sided or switched I/O One-sided distributed I/O Base line Switched distributed I/O, PROFIBUS DP, CCF = 2 % Factor approx. 15 CPU 410 Process Automation/CPU 410 SMART System Manual, 05/2017, A5E31622160-AC...
  • Page 386 Characteristic values of redundant automation systems A.2 Comparison of MTBF for selected configurations Switched distributed I/O, PROFINET, CCF = 2 % Factor approx. 10 The estimate applies if the process allows for any device to fail. Redundant CPUs with redundant I/O The comparison only took account of the I/O modules.
  • Page 387 Characteristic values of redundant automation systems A.2 Comparison of MTBF for selected configurations Redundant I/O MTBF factor See following table Table A-1 MTBF factors of the redundant I/O Module MLFB MTBF factor CCF = 1% Digital input modules, distributed DI 24xDC24V 6ES7 326–1BK02–0AB0 approx.

  • Page 388: Comparison Of System Configurations With Standard And Fault-Tolerant Communication

    Characteristic values of redundant automation systems A.2 Comparison of MTBF for selected configurations A.2.3 Comparison of system configurations with standard and fault-tolerant communication The next section shows a comparison between standard and fault-tolerant communication for a configuration consisting of a fault-tolerant system, a fault-tolerant CPU operating in stand-alone mode, and a single-channel OS.

  • Page 389: Function And Communication Modules That Can Be Used In A Redundant Configuration

    A complete list of all modules released for SIMATIC PCS 7 V8.2 can be found in the SIMATIC PCS 7 technical documentation here: SIMATIC PCS 7 technical documentation (http://www.automation.siemens.com/mcms/industrial-automation-systems- simatic/en/manual-overview/tech-doc-pcs7/Pages/Default.aspx) In redundant configuration you can use the following function modules (FM) and communication processors (CP) with a CPU 410-5H.
  • Page 390 Function and communication modules that can be used in a redundant configuration Module Article No. Release 6ES7 341-1AH02-0AE0 As of product version 1 6ES7 341-1BH02-0AE0 As of firmware V2.0.0 6ES7 341-1CH02-0AE0 Communication processor CP 342-2 6GK7 342-2AH01-0XA0 As of product version 1 (ASI bus interface module) As of firmware V1.10 Communication processor CP 343-2...

  • Page 391: Connection Examples For Redundant I/Os

    Details on combinable ET 200M modules and suitable connection cables as well as the current MTA product range are available at this address: Update and expansion of the MTA terminal modules (http://support.automation.siemens.com/WW/view/en/29289048) Interconnection of output modules Interconnection of digital output modules using external diodes <-> without external diodes...
  • Page 392 Connection examples for redundant I/Os C.2 Interconnection of output modules Information on connecting digital output modules via diodes ● Suitable diodes are diodes with U >=200 V and I_ >= 1 A (e.g., types from the series 1N4003 ... 1N4007). ●...

  • Page 393: 8-Channel Hart Analog Input Mta

    Connection examples for redundant I/Os C.3 8-channel HART analog input MTA 8-channel HART analog input MTA The following figure shows the connection of an encoder to two SM 331; AI 8 x 0/4...20mA HART via an 8-channel HART analog input MTA. Figure C-1 Interconnection example for SM 331, Al 8 x 0/4...20mA HART CPU 410 Process Automation/CPU 410 SMART...

  • Page 394: 8-Channel Hart Analog Output Mta

    Connection examples for redundant I/Os C.4 8-channel HART analog output MTA 8-channel HART analog output MTA The following figure shows the connection of an encoder to two redundant SM 322; AI 8 x 0/4...20mA HART via an 8-channel HART analog output MTA. Figure C-2 Interconnection example for SM 322, Al 8 x 0/4...20mA HART CPU 410 Process Automation/CPU 410 SMART...

  • Page 395: Sm 321; Di 16 X Dc 24 V, 6Es7 321-1Bh02-0Aa0

    Connection examples for redundant I/Os C.5 SM 321; DI 16 x DC 24 V, 6ES7 321–1BH02–0AA0 SM 321; DI 16 x DC 24 V, 6ES7 321–1BH02–0AA0 The diagram below shows the connection of two redundant encoders to two SM 321; DI 16 x DC 24 V.

  • Page 396: Sm 321; Di 32 X Dc 24 V, 6Es7 321-1Bl00-0Aa0

    Connection examples for redundant I/Os C.6 SM 321; DI 32 x DC 24 V, 6ES7 321–1BL00–0AA0 SM 321; DI 32 x DC 24 V, 6ES7 321–1BL00–0AA0 The diagram below shows the connection of two redundant encoder pairs to two redundant SM 321;...

  • Page 397: Sm 321; Di 16 X Ac 120/230V, 6Es7 321-1Fh00-0Aa0

    Connection examples for redundant I/Os C.7 SM 321; DI 16 x AC 120/230V, 6ES7 321–1FH00–0AA0 SM 321; DI 16 x AC 120/230V, 6ES7 321–1FH00–0AA0 The diagram below shows the connection of two redundant encoders to two SM 321; DI 16 x AC 120/230 V.

  • Page 398: Sm 321; Di 8 X Ac 120/230 V, 6Es7 321-1Ff01-0Aa0

    Connection examples for redundant I/Os C.8 SM 321; DI 8 x AC 120/230 V, 6ES7 321–1FF01–0AA0 SM 321; DI 8 x AC 120/230 V, 6ES7 321–1FF01–0AA0 The diagram below shows the connection of two redundant encoders to two SM 321; DI 8 AC 120/230 V.

  • Page 399: Sm 321; Di 16 X Dc 24V, 6Es7 321-7Bh00-0Ab0

    Connection examples for redundant I/Os C.9 SM 321; DI 16 x DC 24V, 6ES7 321–7BH00–0AB0 SM 321; DI 16 x DC 24V, 6ES7 321–7BH00–0AB0 The diagram below shows the connection of two redundant encoder pairs to two SM 321; DI 16 x DC 24V.

  • Page 400: Sm 321; Di 16 X Dc 24V, 6Es7 321-7Bh01-0Ab0

    Connection examples for redundant I/Os C.10 SM 321; DI 16 x DC 24V, 6ES7 321–7BH01–0AB0 C.10 SM 321; DI 16 x DC 24V, 6ES7 321–7BH01–0AB0 The diagram below shows the connection of two redundant encoder pairs to two SM 321; DI 16 x DC 24V.

  • Page 401: Sm 326; Do 10 X Dc 24V/2A, 6Es7 326-2Bf01-0Ab0

    Connection examples for redundant I/Os C.11 SM 326; DO 10 x DC 24V/2A, 6ES7 326–2BF01–0AB0 C.11 SM 326; DO 10 x DC 24V/2A, 6ES7 326–2BF01–0AB0 The diagram below shows the connection of an actuator to two redundant SM 326; DO 10 x DC 24V/2A.

  • Page 402: Sm 326; Di 8 X Namur, 6Es7 326-1Rf00-0Ab0

    Connection examples for redundant I/Os C.12 SM 326; DI 8 x NAMUR, 6ES7 326–1RF00–0AB0 C.12 SM 326; DI 8 x NAMUR, 6ES7 326–1RF00–0AB0 The diagram below shows the connection of two redundant encoders to two redundant SM 326; DI 8 x NAMUR . The encoders are connected to channel 4. Figure C-10 Example of an interconnection with SM 326;...

  • Page 403: Sm 326; Di 24 X Dc 24 V, 6Es7 326-1Bk00-0Ab0

    Connection examples for redundant I/Os C.13 SM 326; DI 24 x DC 24 V, 6ES7 326–1BK00–0AB0 C.13 SM 326; DI 24 x DC 24 V, 6ES7 326–1BK00–0AB0 The diagram below shows the connection of one encoder to two redundant SM 326; DI 24 x DC 24 V.

  • Page 404: Sm 421; Di 32 X Uc 120 V, 6Es7 421-1El00-0Aa0

    Connection examples for redundant I/Os C.14 SM 421; DI 32 x UC 120 V, 6ES7 421–1EL00–0AA0 C.14 SM 421; DI 32 x UC 120 V, 6ES7 421–1EL00–0AA0 The diagram below shows the connection of a redundant encoder to two SM 421; DI 32 x UC 120 V.

  • Page 405: Sm 421; Di 16 X Dc 24 V, 6Es7 421-7Bh01-0Ab0

    Connection examples for redundant I/Os C.15 SM 421; DI 16 x DC 24 V, 6ES7 421–7BH01–0AB0 C.15 SM 421; DI 16 x DC 24 V, 6ES7 421–7BH01–0AB0 The diagram below shows the connection of two redundant encoders pairs to two SM 421;...

  • Page 406: Sm 421; Di 32 X Dc 24 V, 6Es7 421-1Bl00-0Ab0

    Connection examples for redundant I/Os C.16 SM 421; DI 32 x DC 24 V, 6ES7 421–1BL00–0AB0 C.16 SM 421; DI 32 x DC 24 V, 6ES7 421–1BL00–0AB0 The diagram below shows the connection of two redundant encoders to two SM 421; D1 32 x 24 V. The encoders are connected to channel 0. Figure C-14 Example of an interconnection with SM 421;...

  • Page 407: Sm 421; Di 32 X Dc 24 V, 6Es7 421-1Bl01-0Ab0

    Connection examples for redundant I/Os C.17 SM 421; DI 32 x DC 24 V, 6ES7 421–1BL01–0AB0 C.17 SM 421; DI 32 x DC 24 V, 6ES7 421–1BL01–0AB0 The diagram below shows the connection of two redundant encoders to two SM 421; D1 32 x 24 V. The encoders are connected to channel 0. Figure C-15 Example of an interconnection with SM 421;...

  • Page 408: Sm 322; Do 8 X Dc 24 V/2 A, 6Es7 322-1Bf01-0Aa0

    Connection examples for redundant I/Os C.18 SM 322; DO 8 x DC 24 V/2 A, 6ES7 322–1BF01–0AA0 C.18 SM 322; DO 8 x DC 24 V/2 A, 6ES7 322–1BF01–0AA0 The diagram below shows the connection of an actuator to two redundant SM 322; DO 8 x DC 24 V.

  • Page 409: Sm 322; Do 32 X Dc 24 V/0,5 A, 6Es7 322-1Bl00-0Aa0

    Connection examples for redundant I/Os C.19 SM 322; DO 32 x DC 24 V/0,5 A, 6ES7 322–1BL00–0AA0 C.19 SM 322; DO 32 x DC 24 V/0,5 A, 6ES7 322–1BL00–0AA0 The diagram below shows the connection of an actuator to two redundant SM 322; DO 32 x DC 24 V.

  • Page 410: Sm 322; Do 8 X Ac 230 V/2 A, 6Es7 322-1Ff01-0Aa0

    Connection examples for redundant I/Os C.20 SM 322; DO 8 x AC 230 V/2 A, 6ES7 322–1FF01–0AA0 C.20 SM 322; DO 8 x AC 230 V/2 A, 6ES7 322–1FF01–0AA0 The diagram below shows the connection of an actuator to two SM 322; DO 8 x AC 230 V/2 A.

  • Page 411: Sm 322; Do 4 X Dc 24 V/10 Ma [Eex Ib], 6Es7 322-5Sd00-0Ab0

    Connection examples for redundant I/Os C.21 SM 322; DO 4 x DC 24 V/10 mA [EEx ib], 6ES7 322–5SD00–0AB0 C.21 SM 322; DO 4 x DC 24 V/10 mA [EEx ib], 6ES7 322–5SD00–0AB0 The diagram below shows the connection of an actuator to two SM 322; DO 16 x DC 24 V/10 mA [EEx ib].

  • Page 412: Sm 322; Do 4 X Dc 15 V/20 Ma [Eex Ib], 6Es7 322-5Rd00-0Ab0

    Connection examples for redundant I/Os C.22 SM 322; DO 4 x DC 15 V/20 mA [EEx ib], 6ES7 322–5RD00–0AB0 C.22 SM 322; DO 4 x DC 15 V/20 mA [EEx ib], 6ES7 322–5RD00–0AB0 The diagram below shows the connection of an actuator to two SM 322; DO 16 x DC 15 V/20 mA [EEx ib].

  • Page 413: Sm 322; Do 8 X Dc 24 V/0.5 A, 6Es7 322-8Bf00-0Ab0

    Connection examples for redundant I/Os C.23 SM 322; DO 8 x DC 24 V/0.5 A, 6ES7 322–8BF00–0AB0 C.23 SM 322; DO 8 x DC 24 V/0.5 A, 6ES7 322–8BF00–0AB0 The diagram below shows the connection of an actuator to two redundant SM 322;...

  • Page 414: Sm 322; Do 16 X Dc 24 V/0.5 A, 6Es7 322-8Bh01-0Ab0

    Connection examples for redundant I/Os C.24 SM 322; DO 16 x DC 24 V/0.5 A, 6ES7 322–8BH01–0AB0 C.24 SM 322; DO 16 x DC 24 V/0.5 A, 6ES7 322–8BH01–0AB0 The diagram below shows the connection of an actuator to two redundant SM 322; DO 16 x DC 24 V/0.5 A.

  • Page 415: Sm 332; Ao 8 X 12 Bit, 6Es7 332-5Hf00-0Ab0

    Connection examples for redundant I/Os C.25 SM 332; AO 8 x 12 Bit, 6ES7 332–5HF00–0AB0 C.25 SM 332; AO 8 x 12 Bit, 6ES7 332–5HF00–0AB0 The diagram below shows the connection of two actuators to two redundant SM 332; AO 8 x 12 Bit.

  • Page 416: Sm 332; Ao 4 X 0/4

    Connection examples for redundant I/Os C.26 SM 332; AO 4 x 0/4...20 mA [EEx ib], 6ES7 332–5RD00–0AB0 C.26 SM 332; AO 4 x 0/4...20 mA [EEx ib], 6ES7 332–5RD00–0AB0 The diagram below shows the connection of an actuator to two SM 332; AO 4 x 0/4...20 mA [EEx ib].

  • Page 417: Sm 422; Do 16 X Ac 120/230 V/2 A, 6Es7 422-1Fh00-0Aa0

    Connection examples for redundant I/Os C.27 SM 422; DO 16 x AC 120/230 V/2 A, 6ES7 422–1FH00–0AA0 C.27 SM 422; DO 16 x AC 120/230 V/2 A, 6ES7 422–1FH00–0AA0 The diagram below shows the connection of an actuator to two SM 422;...

  • Page 418: Sm 422; Do 32 X Dc 24 V/0.5 A, 6Es7 422-7Bl00-0Ab0

    Connection examples for redundant I/Os C.28 SM 422; DO 32 x DC 24 V/0.5 A, 6ES7 422–7BL00–0AB0 C.28 SM 422; DO 32 x DC 24 V/0.5 A, 6ES7 422–7BL00–0AB0 The diagram below shows the connection of an actuator to two SM 422; DO 32 x 24 V/0.5 A. The actuator is connected to channel 0.

  • Page 419: Sm 331; Ai 4 X 15 Bit [Eex Ib]; 6Es7 331-7Rd00-0Ab0

    Connection examples for redundant I/Os C.29 SM 331; AI 4 x 15 Bit [EEx ib]; 6ES7 331–7RD00–0AB0 C.29 SM 331; AI 4 x 15 Bit [EEx ib]; 6ES7 331–7RD00–0AB0 The diagram below shows the connection of a 2-wire transmitter to two SM 331; AI 4 x 15 Bit [EEx ib].

  • Page 420: Sm 331; Ai 8 X 12 Bit, 6Es7 331-7Kf02-0Ab0

    Connection examples for redundant I/Os C.30 SM 331; AI 8 x 12 Bit, 6ES7 331–7KF02–0AB0 C.30 SM 331; AI 8 x 12 Bit, 6ES7 331–7KF02–0AB0 The diagram below shows the connection of a transmitter to two SM 331; AI 8 x 12 Bit. The transmitter is connected to channel 0.

  • Page 421: Sm 331; Ai 8 X 16 Bit; 6Es7 331-7Nf00-0Ab0

    Connection examples for redundant I/Os C.31 SM 331; AI 8 x 16 Bit; 6ES7 331–7NF00–0AB0 C.31 SM 331; AI 8 x 16 Bit; 6ES7 331–7NF00–0AB0 The figure below shows the connection of a transmitter to two redundant SM 331; AI 8 x 16 Bit.

  • Page 422: Sm 331; Ai 8 X 16 Bit; 6Es7 331-7Nf10-0Ab0

    Connection examples for redundant I/Os C.32 SM 331; AI 8 x 16 Bit; 6ES7 331–7NF10–0AB0 C.32 SM 331; AI 8 x 16 Bit; 6ES7 331–7NF10–0AB0 The figure below shows the connection of a transmitter to two redundant SM 331; AI 8 x 16 Bit.

  • Page 423: Ai 6Xtc 16Bit Iso, 6Es7331-7Pe10-0Ab0

    Connection examples for redundant I/Os C.33 AI 6xTC 16Bit iso, 6ES7331-7PE10-0AB0 C.33 AI 6xTC 16Bit iso, 6ES7331-7PE10-0AB0 The figure below shows the connection of a thermocouple to two redundant SM 331 AI 6xTC 16Bit iso. Figure C-31 Example of an interconnection AI 6xTC 16Bit iso CPU 410 Process Automation/CPU 410 SMART System Manual, 05/2017, A5E31622160-AC...

  • Page 424: Sm331; Ai 8 X 0/4

    Connection examples for redundant I/Os C.34 SM331; AI 8 x 0/4...20mA HART, 6ES7 331-7TF01-0AB0 C.34 SM331; AI 8 x 0/4...20mA HART, 6ES7 331-7TF01-0AB0 The diagram below shows the connection of a 4-wire transmitter to two redundant SM 331; AI 8 x 0/4...20mA HART. Figure C-32 Interconnection example 1 SM 331;...
  • Page 425 Connection examples for redundant I/Os C.34 SM331; AI 8 x 0/4...20mA HART, 6ES7 331-7TF01-0AB0 The diagram below shows the connection of a 2-wire transmitter to two redundant SM 331; AI 8 x 0/4...20mA HART. Figure C-33 Interconnection example 2 SM 331; AI 8 x 0/4...20mA HART CPU 410 Process Automation/CPU 410 SMART System Manual, 05/2017, A5E31622160-AC...

  • Page 426: Sm 332; Ao 4 X 12 Bit; 6Es7 332-5Hd01-0Ab0

    Connection examples for redundant I/Os C.35 SM 332; AO 4 x 12 Bit; 6ES7 332–5HD01–0AB0 C.35 SM 332; AO 4 x 12 Bit; 6ES7 332–5HD01–0AB0 The diagram below shows the connection of an actuator to two SM 332; AO 4 x 12 Bit. The actuator is connected to channel 0. Suitable diodes are, for example, those of the series 1N4003 ...

  • Page 427: Sm332; Ao 8 X 0/4

    Connection examples for redundant I/Os C.36 SM332; AO 8 x 0/4...20mA HART, 6ES7 332-8TF01-0AB0 C.36 SM332; AO 8 x 0/4...20mA HART, 6ES7 332-8TF01-0AB0 The diagram below shows the connection of an actuator to two SM 332; AO 8 x 0/4...20 mA HART.
  • Page 428 Connection examples for redundant I/Os C.36 SM332; AO 8 x 0/4...20mA HART, 6ES7 332-8TF01-0AB0 CPU 410 Process Automation/CPU 410 SMART System Manual, 05/2017, A5E31622160-AC...

  • Page 429: Index

    Index Cold restart, 103 Communication CPU services, 308 Open IE communication, 318 A&D Technical Support, 20 S7 communication, 310 Analog output signals, 95 Communication blocks Applied value, 91 Consistency, 340 Availability Communication functions, 350 Definition, 382 Communication processors, 389 I/O, 65 Communication services of systems, 62 Overview, 308...
  • Page 430 Index Operating system, 361 Process image update, 359 Defining CiR elements, 173, 174 User program, 359 Exact procedure, 174 External diodes, 391 Overview, 173 EXTF, 42 Deleting CiR elements, 173, 173 Overview, 173 Deleting CiR Elements, 176, 176 Precise procedure, 176 SM 321 Factory settings, 142 Example of an interconnection,...
  • Page 431 Index Manual Purpose, 17 I/O, 30 Scope of validity, 17 Switched, 62, 66 Master CPU, 107 I/O redundancy, 78 Master-standby assignment, 107 I/O redundancy errors, 307, 353 Maximum communication delay IE communication, 319 Calculation, 129 Data blocks, 319 Definition, 121 IFM1F, 43 Maximum cycle time extension IFM2F, 43...
  • Page 432 Index System, 109 Reconfiguring, 186, 186 UPDATE, 105 Requirements, 186 Operating system Execution time, 361 configuring, 162, 162, 162, 164, 164, 166, 186, 188, 18 Optional software, 31 8, 189 Organization blocks, 307, 353 a previously used channel, 164, 188 Overview Behavior of the CPU, 162, 186 PROFINET IO functions, 52...
  • Page 433 Index Replacement during operation Simple Network Management Protocol, 317, 317 of distributed I/Os, 233 Single mode, 101 Requirements, 156, 156, 167, 167 Single-bit errors, 116 Response time Single-channel switched I/O, 62, 66 Calculation of the, 366, 367 Failure, 71 Elements, 364 Slot for synchronization modules, 36 Longest, 367 SNMP, 317, 317...
  • Page 434 Index System status list Compatibility, 301 Technical Support, 20 Time information Synchronized, 151 Time monitoring, 120 Time response, 130 Time stamp, 151 Time stamping Functionality, 151 Precision, 151 Requirements, 151 Resolution, 151 Using, 151 Time synchronization, 151 Time-of-day stamping (1 ms), 151 Time-out, 122 Tolerance window, 91 Tools, 31...

This manual is also suitable for:

Simatic 410 smartSimatic pcs 7

Table of Contents