Simens simatic s7 400 cpu

Description

Preface, Contents 1 SIMATIC Structure of a CPU 41x Memory Concept and Startup Scenarios 2 Automation System S7-400 CPU Specifications Cycle and Reaction Times of the S7-400 3 Technical Specifications Reference Manual This manual is part of the documentation package with the order number 6ES7398-8AA03-8BA0 Edition 12/2002 A5E00165965-01 Index 4

Safety Guidelines This manual contains notices intended to ensure personal safety, as well as to protect the products and connected equipment against damage. These notices are highlighted by the symbols shown below and graded according to severity by the following texts: ! ! ! Danger indicates that death, severe personal injury or substantial property damage will result if proper precautions are not taken. Warning indicates that death, severe personal injury or substantial property damage can result if proper precautions are not taken. Caution indicates that minor personal injury can result if proper precautions are not taken. Caution indicates that property damage can result if proper precautions are not taken. Notice draws your attention to particularly important information on the product, handling the product, or to a particular part of the documentation. Qualified Personnel Only qualified personnel should be allowed to install and work on this equipment. Qualified persons are defined as persons who are authorized to commission, to ground and to tag circuits, equipment, and systems in accordance with established safety practices and standards. Correct Usage Note the following: ! Warning This device and its components may only be used for the applications described in the catalog or the technical description, and only in connection with devices or components from other manufacturers which have been approved or recommended by Siemens. This product can only function correctly and safely if it is transported, stored, set up, and installed correctly, and operated and maintained as recommended. Trademarks SIMATIC, SIMATIC HMI and SIMATIC NET are registered trademarks of SIEMENS AG. Third parties using for their own purposes any other names in this document which refer to trademarks might infringe upon the rights of the trademark owners. Copyright W Siemens AG 2002 All rights reserved Disclaim of Liability The reproduction, transmission or use of this document or its contents is not permitted without express written authority. Offenders will be liable for damages. All rights, including rights created by patent grant or registration of a utility model or design, are reserved. We have checked the contents of this manual for agreement with the hardware and software described. Since deviations cannot be precluded entirely, we cannot guarantee full agreement. However, the data in this manual are reviewed regularly and any necessary corrections included in subsequent editions. Suggestions for improvement are welcomed. Siemens AG Bereich Automation and Drives Geschaeftsgebiet Industrial Automation Systems Postfach 4848, D- 90327 Nuernberg Index-2 Siemens Aktiengesellschaft  Siemens AG 2002 Technical data subject to change. Automation System S7-400 A5E00165965-01 A5E000165965-01

Preface Purpose of the Manual The manual contains reference information on operator actions, descriptions of functions and technical specifications of the central processing units, power supply modules and interface modules of the S7-400. How to configure, assemble and wire these modules (and other) in an S7-400 system is described in the installation manuals for each system. Required Basic Knowledge You will need general knowledge of automation to understand this manual. Target Group This manual is aimed at people with the required qualifications to commission, operate and maintain the products described. Scope of this Manual The manual applies to the S7-400 automation system. Changes Since the Previous Version This manual describes S7 CPUs with firmware version 3.1. Certification The SIMATIC S7-400 product range has the following certificates: • Underwriters Laboratories, Inc.: UL 508 (Industrial Control Equipment) • Canadian Standards Association: CSA C22.2 Number 142, tested (Process Control Equipment) • Factory Mutual Research: Approval Standard Class Number 3611. You can find details on the certificates and approvals in section 1.1, Standards and Certificates, of the “Module Specifications” reference manual. Automation System S7-400 CPU Specifications A5E00165965-01 iii

Preface CE Labeling The SIMATIC S7-400 product range complies with the requirements and protection objectives of the following EU directives: • EC low voltage directive 73/23/EEC • EC electromagnetic compatibility directive 89/336/EEC C-Tick Mark The SIMATIC S7-400 product range complies with the requirements of the AS/NZS 2064 standard (Australia and New Zealand). Standards The SIMATIC S7-400 product range complies with the requirements and criteria of the IEC 61131-2. Place of this Documentation in the Information Environment This manual is part of the documentation package for S7-400, M7-400. System S7-400/M7-400 Documentation Package • • • • S7-400, M7-400 Programmable Controller; Hardware and Installation S7-400, M7-400 Programmable Controllers; Module Specifications Automation System S7-400; CPU Data S7-400 Instruction List Navigating The manual offers the following access aids to make it easy for you to find specific information quickly: • At the start of the manual you will find a complete table of contents and a list of the diagrams and tables that appear in the manual. • An overview of the contents of each section is provided in the left column on each page of each chapter. • You will find a glossary in the appendix at the end of the manual. The glossary contains definitions of the main technical terms used in the manual. • At the end of the manual you will find a comprehensive index which gives you rapid access to the information you need. iv Automation System S7-400 CPU Specifications A5E00165965-01

Preface Note In order to program and commission an S7-400 you require STEP 7 V52 as well as the following manuals or manual packages: Manual/ Manual Package Standard Software for S7 and M7 Chapter Overview • Installing and starting up STEP 7 on a programming device / PC • Working with STEP 7 with the following contents: STEP 7 Basic Information Managing projects and files Configuring and assigning parameters to the S7-400 configuration Assigning symbolic names for user programs Creating and testing a user program in STL/LAD Creating data blocks Configuring the communication between two or more CPUs Loading, storing and deleting user programs in the CPU / programming device Monitoring and controlling user programs Monitoring and controlling the CPU • Guide for efficiently implementing the programming task with the programming device / PC and STEP 7 • How the CPUs work (for example, memory concept, access to inputs and outputs, addressing, blocks, data management) • • • • • Description of STEP 7 data management Using data types of STEP 7 Using linear and structured programming Using block call instructions Using the debug and diagnostic functions of the CPUs in the user program (for example, error OBs, status word) STEP 7 Reference Information • Basic procedure for working with STL, LAD, or FBD (for example, structure of Statement List (STL) for S7-300 and S7-400 • • • • • • Ladder Logic (LAD) for S7-300 and S7-400 Function Block Diagram (FBD) for S7-300 and S7-400 STL, LAD, or FBD, number formats, syntax) Description of all instructions in STEP 7 (with program examples) Description of the various addressing methods in STEP 7 (with examples) Description of all functions integrated in the CPUs Description of the internal registers in the CPU Description of all system functions integrated in the CPUs Description of all organization blocks integrated in the CPUs System and Standard Functions Manual PG 7xx • Description of the programming device hardware • Connecting a programming device to various devices • Starting up a programming device Automation System S7-400 CPU Specifications A5E00165965-01 v

Preface Recycling and Disposal The S7-400 is low in contaminants and can therefore be recycled. To recycle and dispose of your old device in an environment-friendly manner, please contact a disposal company certified for disposal of electronic waste. Further Support If you have any technical questions, please get in touch with your Siemens representative or agent responsible. http://www.siemens.com/automation/partner Training Centers We offer a number of courses to help you become familiar with the SIMATIC S7 programmable logic controller. Please contact your regional training center or our central training center in D 90327 Nuremberg, Germany for details: Phone: Internet: vi +49 (911) 895-3200. http://www.sitrain.com Automation System S7-400 CPU Specifications A5E00165965-01

Preface Service & Support in the Internet In addition to our documentation, we also offer you the benefit of all our knowledge on the Internet. http://www.siemens.com/automation/service&support There you will find: • A newsletter with all the latest information on your products • Knowledge Manager to locate the documentation you require • A forum in which users and specialists throughout the world exchange their experiences • Your local contact person for Automation & Drives using our contact database • Information about our on-site service, repairs, spare parts and much more is available under the heading “Service”. viii Automation System S7-400 CPU Specifications A5E00165965-01

Structure of a CPU 41x Controls and Indicators of the CPU 417-4 Module designation, version, abbreviated order number and firmware version LEDs INTF, EXTF, BUS1F, BUS2F, FRCE, RUN, STOP LEDs IFM1F, IFM2F V3.0.0 BUS1F BUS2F IFM1F IFM2F Slot for the memory card Mode selector Under cover MPI/PROFIBUS DP interface PROFIBUS DP interface Under cover Module slot for interface module 1 Module slot for interface module 2 Incoming supply of external backup voltage Under the metal lid on the left-hand side Interface for memory expansion Figure 1-4 Layout of the Controls and Indicators of the CPU 417-4 LEDs Table 1-1 gives you an overview of the LEDs on the individual CPUs. Section 1.2 describes the states and errors indicated by these LEDs. Automation System S7-400 CPU Specifications A5E00165965-01 1-5

Structure of a CPU 41x Table 1-1 LED LEDs of the CPUs Color Meaning In CPU 412-1 412-2 414-2 416-2 414-3 416-3 417-4 INTF red Internal fault x x x x EXTF red External fault x x x x FRCE yellow Active force request x x x x RUN green RUN mode x x x x STOP yellow STOP mode x x x x BUS1F red Bus fault at MPI/PROFIBUS DP interface 1 x x x x BUS2F red Bus fault at PROFIBUS DP interface 2 – x x x IFM1F red Error at interface submodule 1 – – x x IFM2F red Error at interface submodule 2 – – – x Mode Selector You can use the mode selector to select the current operating mode of the CPU. The mode selector is a key switch with four switching positions. You can use different protection levels and limit any program changes or startup options (STOP to RUN transition) to a certain group of people. Section 1.4 describes the functions of the mode selector and the protection levels of the CPUs. Slot for Memory Cards You can insert a memory card in this slot. There are two types of memory card: • RAM cards You can expand the load memory of a CPU with the RAM card. • FLASH cards You can use the FLASH card to store your user program and your data so that they are failproof (even without a backup battery). You can either program the FLASH card on the programming device or in the CPU. The FLASH card also expands the load memory of the CPU. You can find a detailed description of the memory cards in Chapter 1.5. 1-6 Automation System S7-400 CPU Specifications A5E00165965-01

Structure of a CPU 41x Slot for Interface Modules You can insert one interface module (IF module) for each CPUs 41x-3 and 41x-4 in this slot. Interface for Memory Expansion CPU 417-4 also features interfaces for memory expansion. These make it possible to expand the working memory. (See “S7-400, M7-400 Programmable Controllers, Hardware and Installation” ) MPI/DP interface You can connect the following devices to the MPI of the CPU, for example: • Programming devices • Operation and monitoring devices • Additional S7-400 or S7-300 controllers (see Section 1.6). Use the bus connector with an angular outgoing cable (see the Installation manual, Chapter 7) You can also configure the MPI interface as a DP master and use it as a PROFIBUS DP interface with up to 32 DP slaves. PROFIBUS DP interface You can connect the distributed I/O, programming devices/OPs and additional DP master stations to the PROFIBUS DP interface. Automation System S7-400 CPU Specifications A5E00165965-01 1-7

Structure of a CPU 41x Incoming Supply of External Backup Voltage at the “EXT.-BATT.” Socket You can use one or two backup batteries – depending on the module type – in the power supply modules of the S7-400 to do the following: • Provide backup power for the user program you have stored in RAM. • Maintain memory bits, times, counts and system data as well as data in variable data blocks. • Provide backup power for the internal clock. You can achieve the same backup power by connecting a voltage between 5 V and 15 V DC to the “EXT.-BATT.” socket of the CPU. The “EXT.-BATT.” input has the following features: • Reverse polarity protection • A short-circuit current limit of 20 mA You need a cable with a 2.5 mm ∅ jack to connect power to the “EXT.-BATT” socket, as shown in the following illustration. Note the polarity of the jack. Positive pole Negative pole 2.5 mm jack ∅ Note You will require the external incoming supply at the “EXT.-BATT.” socket if you replace a power supply module and want to provide a backup supply for the user program stored in RAM and the data mentioned above while the module is being replaced. 1-8 Automation System S7-400 CPU Specifications A5E00165965-01

Structure of a CPU 41x 1.2 Monitoring Functions of the CPU Monitoring and Error Messages The CPU hardware and the operating system have monitoring functions that ensure that the system functions correctly and that there is a defined response in the event of an error. A number of errors will also produce a response from the user program. The following table gives you an overview of possible errors, their causes and the responses of the CPU. Type of Fault/Error Cause of Fault Response of the Operating System Error LED Clock pulse failure Monitoring of the failure of the processor clock pulse System standstill Disabling of the digital outputs by issuing the “OD” (Output Disable) signal – Access error Module failure (SM, FM, CP) ”EXTF” LED lights up until the fault is acknowledged. In SMs: • OB 122 call • Entry in the diagnostic buffer • In the case of input modules: Entry of null for the date in the accumulator or the process image In the case of other modules: • OB 122 call EXTF Clock synchronous interrupt Timing error Start a program synchronized to the DP clock • • • • • The runtime of the user program (OB1 and all the interrupts and error OBs) exceeds the specified maximum cycle time. OB request error Overrun of the start information buffer Time error interrupt Re-enter RUN following CiR Call OB 61 to OB 64 – ”INTF” LED lights up until the fault is acknowledged. OB 80 call If the OB is not loaded: The CPU goes into STOP mode. Power supply module error (not power failure) In the central or distributed I/O rack: • At least one backup battery in the power supply module is empty. • The backup voltage is missing. • The 24 V supply to the power supply module has failed. OB 81 call If the OB is not loaded: The CPU continues to run. Diagnostic Interrupt An I/O module with interrupt capability reports a diagnostic interrupt. OB 82 call If the OB is not loaded: The CPU goes into STOP mode. Remove/insert interrupt Removal or insertion of an SM and insertion of an incorrect module type. The LED EXTF will not light up if the only inserted SM is removed from the CPU in STOP during default configuration. The LED lights up briefly when the SM is inserted again. INTF OB 83 call If the OB is not loaded: The CPU goes into STOP mode. Automation System S7-400 CPU Specifications A5E00165965-01 EXTF EXTF EXTF 1-9

Structure of a CPU 41x Type of Fault/Error Cause of Fault • Priority class error • • • • • Failure of a rack/station Communication error • • • • Priority class is called, but the corresponding OB is not available. In the case of an SFB call: The instance DB is missing or defective. OB 85 call If the OB is not loaded: The CPU goes into STOP mode. Error during the updating of the process image Error LED INTF EXTF Power failure in an expansion rack Failure of a DP line Failure of a coupling line: missing or defective IM, interrupted line) OB 86 call If the OB is not loaded: The CPU goes into STOP mode. Status information cannot be entered in DB Incorrect frame identifier Frame length error Error in the structure of the global data message DB access error OB 87 call If the OB is not loaded: The CPU goes into STOP mode. • • Nesting depth exceeded for Cancel processing Response of the Operating System synchronous errors • Too many nested block calls (B EXTF INTF Call OB 88 If the OB is not loaded: The CPU goes into STOP mode. INTF stack) • Error allocating local data Programming error Error in the machine code or in the user program: • BCD conversion error • Range length error • Range error • Alignment error • Write error • Timer number error • Counter number error • Block number error • Block not loaded Loss of clock Error in the compiled user program (e.g. impermissible OP code or jump over the end of the block) CPU goes into STOP mode. Reboot or memory reset required. Clock was lost either because an OB 61 to 64 was not start due to higher priorities or because additional asynchronous bus loads suppressed the bus clock. MC7 code error OB 121 call If the OB is not loaded: The CPU goes into STOP mode. Call OB 61..64 at the next pulse. INTF INTF INTF EXTF There are also test and information functions available in each CPU that you can call up with STEP 7. 1-10 Automation System S7-400 CPU Specifications A5E00165965-01

Structure of a CPU 41x 1.3 Status and Error LEDs Status LEDs The two RUN and STOP LEDs on the front panel of a CPU informs you of the currently active CPU operating status. LED RUN Meaning STOP H D CPU is in RUN state. D H CPU is in STOP state. The user program is not processed. Restart and warm restart/reboot is possible. If the STOP status was triggered by an error, the error indication (INTF or EXTF) is also set. CPU has the status DEFECT. The INTF, EXTF and FRCE LEDs also flash. B B 2 Hz 2 Hz B H HALT status has been triggered by a test function. H A warm restart/reboot/restart has been triggered. It can take a minute or longer to execute the warm restart/reboot/restart depending on the length of the OB called. If the CPU still does not go into RUN, there might be an error in the system configuration. B Memory reset is requested by the CPU. 0.5 Hz B 2 Hz x 0.5 Hz x B Memory reset is running. 2 Hz D = LED is dark; H = LED lights up; B = LED flashes with the specified frequency; x = LED status is irrelevant Automation System S7-400 CPU Specifications A5E00165965-01 1-11

Structure of a CPU 41x Error Displays and Points to Note, All CPUs The three LEDs INTF, EXTF and FRCE on the front panel of a CPU inform you about the errors and points to note during the execution of the user program. LED Meaning INTF EXTF FRCE H x x An internal has been detected (program or configuration error) or the CPU is performing a CiR. x H x An external error has been detected (in other words, the cause of the error cannot be traced back to the CPU module). x x H A force request is active. H = LED lights up; x = LED status is irrelevant The LEDs BUSF1 and BUSF2 indicate errors in connection with the MPI/DP interface and the PROFIBUS DP interface. LED Meaning BUS1F BUS2F H x An error has been detected at the MPI/DP interface. x H An error has been detected at the PROFIBUS DP interface. B x DP master: DP slave: x B DP master: DP slave: One or more slaves at PROFIBUS DP interface 1 are not replying. not addressed by the DP master One or more slaves at PROFIBUS DP interface 2 are not replying. not addressed by the DP master H = LED lights up; B = LED flashes; x = LED status is irrelevant 1-12 Automation System S7-400 CPU Specifications A5E00165965-01

Structure of a CPU 41x Error LEDs and Points to Note, CPU 41x-3 and 41x-4 The CPUs 41x-3 and 41x-4 continue to have the LED IFM1F and LEDs IFM1F and IFM2F. These indicate errors in connection with the first and second module interfaces. LED Meaning IFM1F IFM2F H x An error has been detected at module interface 1. x H An error has been detected at module interface 2. B x DP master: x B DP master: One or more slaves on the PROFIBUS DP interface module inserted in module slot 1 are not responding DP slave: not addressed by the DP master One or more slaves on the PROFIBUS DP interface module inserted in module slot 2 are not responding DP slave: not addressed by the DP master H = LED lights up; B = LED flashes; x = LED status is irrelevant Diagnostic buffer You can read out the exact cause of an error in STEP 7 (PLC –> Module Information) from the diagnostic buffer. Automation System S7-400 CPU Specifications A5E00165965-01 1-13

Structure of a CPU 41x 1.4 Mode Selector Function of the Mode Selector Using the mode selector, you can put the CPU in RUN/RUN-P or STOP mode or reset the memory of the CPU. STEP 7 offers further options for changing the mode. Positions The mode selector switch is designed as a keyswitch. Figure 1-5 illustrates the possible positions of the mode selector. RUN-P RUN STOP MRES Figure 1-5 Positions of the Mode Selector Table 1-2 explains the positions of the mode selector. In the event of a fault or if there are startup problems, the CPU will go into or remain in STOP mode irrespective of the position of the mode selector. 1-14 Automation System S7-400 CPU Specifications A5E00165965-01

Structure of a CPU 41x Table 1-2 Positions of the Mode Selector Explanation Position RUN-P If there is no startup problem or error and the CPU can go into RUN, the CPU processes the user program or is idle. It is possible to access the I/O. The key cannot be removed in this position. Programs can: • Be read out with the programming device from the CPU (CPU programming device) • Be transferred to the CPU (programming device CPU). RUN If there is no startup problem or error and the CPU can go into RUN, the CPU processes the user program or runs in idle. It is possible to access the I/O. The key can be removed in this position to ensure that the mode cannot be changed without authorization. The programming device can read the programs in the CPU (CPU –> PG). The program in the CPU cannot be changed when the switch is in the RUN position (see STEP 7)! The protection level can be bypassed using a password set in the STEP 7 / Hardware Configuration (STEP 7 V4.02 and above). In other words, if you use this password, the program can also be changed when the switch is in the RUN position. STOP The CPU does not process the user program. The digital signal modules are disabled. The key can be removed in this position to ensure that the operating mode cannot be changed without authorization. Programs can: • Be read out with the programming device from the CPU (CPU programming device) • Be transferred to the CPU (programming device CPU). MRES (Master Reset) Momentary-contact position of the key switch for the master reset of the CPU and for cold restart (see the following pages). Protection Levels A protection level can be defined in the CPUs of the S7-400 that can be used to protect the programs in the CPU from unauthorized access. You can determine with the protection level which programming device functions a user can execute on the CPU in question without particular authorization (password). You can execute all the programming device functions using a password. Setting the Protection Levels You can set the protection levels (1 to 3) for a CPU under STEP 7/Configuring Hardware. You can remove the protection level set under STEP 7/Configuring Hardware using a manual reset with the mode selector. You can also set protection levels 1 and 2 using the mode selector. Table 1-3 lists the protection levels of a CPU of the S7-400. Automation System S7-400 CPU Specifications A5E00165965-01 1-15

Structure of a CPU 41x Table 1-3 Protection Levels of a S7-400 CPU Function Protection Level 1 Switch Position • All programming device functions are permitted RUN-P/STOP (default setting). 2 • It is permissible to load objects from the CPU into RUN programming device. In other words, only read programming device functions are permitted. • Functions for process control, process monitoring and process communication are permitted. 3 • All information functions are permitted. • Functions for process control, process monitoring – and process communication are permitted. • All information functions are permitted. If different protection levels are set with the mode selector and with STEP 7, the higher protection level applies (3 before 2, 2 before 1). Operating Sequence for Memory Reset Case A: You want to download a complete, new user program to the CPU. 1. Turn the switch to the STOP position. Result: The STOP LED lights up. 2. Turn the switch to the MRES setting and keep it at this setting. Result: The STOP LED is dark for a second, light for a second, dark for a second and then remains on. 3. Turn the switch back to the STOP setting, then to the MRES setting again within the next 3 seconds and back to STOP. Result: The STOP LED flashes for at least 3 seconds at 2 Hz (memory reset is executed) and then lights up permanently Case B: When the STOP LED flashes slowly at 0.5 Hz, the CPU is requesting a memory reset (system memory reset request, after a memory card has been removed or inserted, for example). Turn the switch to MRES and back to the STOP position. Result:The STOP LED flashes for at least 3 seconds at 2 Hz (reset is being executed) and then remains lit. You can find the complete description of what happens during a memory reset in the: S7-400, M7-400 Programmable Controllers Installation Manual, Chapter 6. Cold Restart The user program is started again following a cold restart. All the data, including the retentive data, are deleted. 1-16 Automation System S7-400 CPU Specifications A5E00165965-01

Structure of a CPU 41x Restart Following a restart, the user program resumes at the position at which it was interrupted. If the restart after power-on function (automatic restart) is to work, the S7-400 must have a battery backup. Reboot (Warm Restart) The user program is started again following a warm restart. The retentive data and the contents of the data blocks are kept. Operating Sequence at Warm Restart/Reboot/Restart 1. Turn the switch to the STOP position. Result: The STOP LED lights up. 2. Turn the switch to the RUN/RUNP setting. Whether the CPU executes a warm restart/reboot or a restart depends on the parameter assignment for the CPU. Operating Sequence at Cold Restart 1. Turn the switch to the STOP position. Result: The STOP LED lights up. 2. Turn the switch to the MRES setting and keep it at this setting. Result: The STOP LED is dark for a second, light for a second, dark for a second and then remains on. 3. Turn the switch to the RUN/RUNP setting. Automation System S7-400 CPU Specifications A5E00165965-01 1-17

Structure of a CPU 41x 1.5 Design and Function of Memory Cards Order Numbers The order numbers for memory cards are listed in the technical specifications in Chapter 4. Configuration The memory card is slightly larger than a credit card and protected by a strong metal casing. It is plugged into a receptacle at the front of the CPU; the end to be inserted is obvious from the design of the memory card. Name of the Memory Card Order number Front elevation Side elevation Type plate Grip Figure 1-6 Structure of the Memory Card Function The memory card and an integrated memory area on the CPU together form the load memory of the CPU. In operation, the load memory contains the complete user program including comments, symbols, special additional information that permits decompiling of the user program, and all the module parameters (see Chapter 2.1). 1-18 Automation System S7-400 CPU Specifications A5E00165965-01

Structure of a CPU 41x What the Memory Card Contains The following data can be stored in the memory card: • User program, that is, blocks (OBs, FBs, FCs, DBs) and system data • Parameters that determine the behavior of the CPU • Parameters that determine the behavior of the I/O modules. • As of STEP 7 V5.1 the Project in Their Entirety in Suitable Memory Cards. Types of Memory Cards for the S7-400 Two types of memory card are used in the S7-400: • RAM cards • Flash cards (FEPROM cards) Note Non-Siemens memory cards cannot be used in the S7-400. What Type of Memory Card Should You Use? Whether you use a RAM card or a Flash card depends on how you intend to use the memory card. Table 1-4 Types of Memory Cards ...Then If you ... want to store the data in RAM and you want to modify your program during RUN or RUN-P mode, use a RAM card want to store your user program permanently on the memory card, even with power removed (without backup or outside the CPU), use a Flash card Automation System S7-400 CPU Specifications A5E00165965-01 1-19

Structure of a CPU 41x RAM Card you use a RAM card, you must plug this into the CPU to load the user program. The user program is loaded with the help of the programming device (PG). You can load the entire user program or the individual parts such as FBs, FCs, OBs, DBs, or SDBs into the load memory in STOP mode or in RUN-P mode. If you remove the RAM card from the CPU, the information stored on it is lost. The RAM card does not have a built-in backup battery. If the power supply has a functioning backup battery or if an external backup voltage is supplied to the CPU via the “EXT. BATT.” socket, the contents of the RAM card are retained after switching off the power supply provided the RAM card remains plugged into the CPU and the CPU remains in the rack. Flash Card If you use a Flash card, there are two ways of loading the user program: • Set the CPU to STOP with the mode selector, plug the Flash card into the CPU, and load the user program with STEP 7 “PLC –> Load User Program to Memory Card”. • Load the user program into the Flash card in offline mode at the programming device or adapter and then insert the Flash card into the CPU. You can only load your complete user program with the Flash card. You can load smaller program sections into the integrated load memory on the CPU using the programming device. In the case of larger program changes, you must always reload the Flash card with the complete user program. The Flash card does not require voltage to store its contents, that is, the information stored on it is retained even when you remove the Flash card from the CPU or if you operate your S7-400 system without backup (without backup battery in the power supply module or “EXT. BATT.” socket of the CPU). Which Memory Card Capacity to Use The capacity of the memory card you use depends on the size of the user program and the additional memory requirement resulting from the use of function modules or communications modules. See the manuals of these modules for details of their memory requirements. To optimally use the working memory (code and data) your CPU, you should expand the load memory of the CPU with a memory card with at least the same capacity as the working memory. 1-20 Automation System S7-400 CPU Specifications A5E00165965-01

Structure of a CPU 41x Changing the Memory Card To change the memory card, follow the steps outlined below: 1. Set the CPU to STOP. 2. Remove the plugged in memory card. Note If you remove the memory card, the CPU requests a memory reset by flashing the STOP indicator every three seconds. This sequence cannot be influenced by error OBs. 3. Insert a “new” memory card. 4. Perform a memory reset on the CPU. Automation System S7-400 CPU Specifications A5E00165965-01 1-21

Structure of a CPU 41x 1.6 Multipoint Interface (MPI) Connectable Devices You can, for example, connect the following nodes to the MPI: • Programming devices (PG/PC) • Operation and monitoring devices (OPs and TDs) • Additional SIMATIC S7 programmable controllers Some connectable devices take a supply of 24 V from the interface. This voltage is available there in non-isolated form. Programming Device/OP-CPU Communication A CPU can maintain several simultaneous online connections during communication with programming devices/OPs. By default, one of these connections is for a programming device and one is for an OP/operation and monitoring unit. For more information about the number of connection resources and the number OPs that can be connected for each CPU, refer to Chapter 4 Technical Specifications. Communication and Interrupt Response Times Notice The interrupt reaction times can be delayed by read and write jobs with a high data volume (approx. 460 byte). CPU-CPU Communication There are two types of CPU-CPU communication: • Data transfer via S7 basic communication • Data transfer via S7 communication You can find additional information on this in the “Programming with STEP 7” manual. Connector Use only the bus connector with an angular outgoing cable for PROFIBUS DP or a programming device cable for connecting devices to the MPI (see Chapter 7 in the Installation Manual). 1-22 Automation System S7-400 CPU Specifications A5E00165965-01

Structure of a CPU 41x Multipoint Interface as DP Interface You can also configure the MPI interface as a DP interface. To do this, you can reconfigure the MPI interface under STEP 7 in SIMATIC Manager. You can use this to set up a DP line with a maximum of 32 slaves. 1.7 PROFIBUS DP Interface Connectable Devices You can connect any PROFIBUS DP slave that complies with the standard to the PROFIBUS DP interface. In this case, the CPU is either a DP master or DP slave connected via the PROFIBUS DP field bus to the passive slave stations or other DP masters. Some connectable devices take a supply of 24 V from the interface. This voltage is available there in non-isolated form. Connector Use only the bus connector for PROFIBUS DP or PROFIBUS cable for connecting devices to the PROFIBUS DP interface (see Chapter 7 in the Installation Manual). Automation System S7-400 CPU Specifications A5E00165965-01 1-23

Structure of a CPU 41x 1.8 Overview of the Parameters for the S7-400 CPUs Default Values All the parameters have default settings at delivery. These defaults, which are suitable for a whole range of standard applications, mean that the S7-400 can be used immediately without the need for further settings. You can find the CPU-specific default values using “Configuring Hardware” in STEP 7. Parameter Blocks The behavior and properties of the CPU are defined using parameters that are stored in system data blocks. The CPUs have a defined default setting. You can change this default setting by modifying the parameters in the hardware configuration. The following list gives you an overview of the configurable system properties available in the CPUs. • General properties (e.g. Name of the CPU) • Startup (e.g. enabling of a restart) • Clock synchronous interrupts • Cycle/clock memory (e.g. cycle monitoring time) • Retentivity (number of memory markers, timers and counters that are maintained) • Memory (e.g.local data) Note: If, for example, you set greater or smaller values than the default values for the process image, the number of diagnostic buffer entries and the maximum number of ALARM-8 blocks (SFB 34 and SFB 35) and blocks for S7 communication, the working memory available for the program code and for data blocks will be reduced or increased by this amount. • Assignment of interrupts (process interrupts, delay interrupts, asynchronous error interrupts) to the priority classes • Time-of-day interrupts (e.g. start, interval duration, priority) • Watchdog interrupts (e.g. priority, interval duration) • Diagnostics/clock (e.g. time synchronization) • Protection levels Note 16 memory bytes and 8 counter numbers are set to retentive in the default settings, in other words, they are not deleted when the CPU is restarted. 1-24 Automation System S7-400 CPU Specifications A5E00165965-01

Structure of a CPU 41x Parameter Assignment Tool You can set the individual CPU parameters using “Configuring Hardware” in STEP 7. Note If you make changes to the existing settings of the following parameters, the operating system carries out initializations like those during cold restart. • Size of the process image of the inputs • Size of the process image of the inputs • Size of the local data • Number of diagnostic buffer inputs • Communication resources These initializations are: – Data blocks are initialized with the load values – Memory bits, times, counts, inputs and outputs are deleted regardless of the retentive settings (0) – DBs generated via SFC are deleted – Permanently configured, base communication connections are established – All the priority classes start from the beginning again Automation System S7-400 CPU Specifications A5E00165965-01 1-25

Structure of a CPU 41x 1.9 Multicomputing Chapter Overview Section Description Page 1.9.1 Peculiarities 1-28 1.9.2 Multicomputing Interrupt 1-29 1.9.3 Configuring and Programming Multicomputing Operation 1-29 What is Multicomputing Operation? Multicomputing operation is the operation of several (max. 4) multicomputing-capable central processing units at the same time in a central rack (central device) of the S7-400. The CPUs involved automatically change their modes synchronously. In other words, they start up together and change to STOP mode together. The user program runs on each CPU irrespective of the user programs in the other CPUs. This makes it possible to execute controller tasks in parallel. When Do You Use Multicomputing? It is advantageous to use multicomputing in the following cases: • If your user program is too large for a single CPU and storage space is becoming scarce, distribute your program over several CPUs. • If a certain part of your system is supposed to be processed quickly, remove the relevant program section from the overall program and have it processed by a separate, “quick” CPU. • If your system consists of several different parts that can be easily separated from one another and can therefore be controlled relatively independently, let CPU1 process system part 1, CPU 2 system part 2 and so on. 1-26 Automation System S7-400 CPU Specifications A5E00165965-01

Structure of a CPU 41x Example The figure below shows a programmable controller that is working in multicomputing mode. Each CPU can access the modules assigned to it (FM, CP, SM). CR P S C P U 1 C P U 3 C P U 4 C P U 2 I I I M M M 1 2 3 Figure 1-7 I M CP, FM, I/O I M I/O I M CP, FM, I/O I M I/O I M CP, FM, I/O I M I/O I M CP, FM, I/O I M I M CP, FM, I/O I M I/O I M CP, FM, I/O I M I/O L i n e I/O I/O EU I M CP, FM, I/O I M I/O I M CP, FM, I/O I M Multicomputing Example The Difference Between Multicomputing Operation and Operation in the Segmented Rack In the segmented CR2 rack (physically segmented; cannot be done by parameter assignment), only one CPU is allowed per segment. However, this is not multicomputing. The CPUs in the segmented rack each make up an independent subsystem and respond as separate processors. There is no shared logical address area. Multicomputing operation is not possible in segmented racks (see also the Installation Manual). Automation System S7-400 CPU Specifications A5E00165965-01 1-27

Structure of a CPU 41x 1.9.1 Peculiarities Slot Rules In multicomputing operation, up to four CPUs can be inserted at the same time in a central controller (CC) in any order. If you use CPUs that can only handle module start addresses that are divisible by 4 (usually CPUs before 10/98), you must keep to this rule for all the configured CPUs when you assign addresses! The rule applies should you also use CPUs that allow the bytewise assignment of module start addresses in single-computing operation. Bus Connection The CPUs are connected to one another via the communication bus (K bus). In other words, if configured appropriately, all the CPUs can be reached by the programming device via an MPI interface. Behavior at Startup and During Operation At startup, the CPUs involved in multicomputing operation automatically check whether they can synchronize with each other. Synchronization is only possible if: • All the configured CPUs (but only those) are inserted and not defective. • Correct configuration data (SDBs) have been created and loaded for all the inserted CPUs. If one of these prerequisites is not met, the event is entered in the diagnostic buffer with ID 0x49A4. You can find explanations of the event IDs in the reference information for standard and system functions. When STOP mode is exited, a comparison of the types of startup (COLD RESTART/REBOOT (WARM RESTART/RESTART) is carried out. If their startup type differs, the CPUs do not go into RUN mode. Assignment of Addresses and Interrupts In multicomputing operation, the individual CPUs can each access the modules that were allocated to them during configuration with STEP 7. The address area of a module is always assigned exclusively to a CPU. Each interrupt-capable module is assigned to a CPU. Interrupts originating from such a module cannot be received by the other CPUs. 1-28 Automation System S7-400 CPU Specifications A5E00165965-01

Structure of a CPU 41x Interrupt Processing The following applies to interrupt processing: • Process interrupts and diagnostic interrupts are only sent to one CPU. • When a module fails or is removed or inserted, the interrupt is processed by the CPU that was assigned to the module at parameter assignment with STEP 7. Exception: A module insertion/removal interrupt that starts from a CP reaches all the CPUs even if the CP was assigned to a CPU at configuration with STEP 7. • In the event of a rack failure, OB 86 is called on each CPU, including CPUs that were not assigned a module in the failed rack. You can find further information on the OB 86 in the reference information on organization blocks. Typical I/O Application Specification The typical I/O application specification of a programmable controller corresponds in multicomputing operation to the typical application specification of the CPU with the most resources. The relevant CPU-specific or DP master-specific typical application specifications cannot be exceeded in the individual CPUs. 1.9.2 Multicomputing Interrupt Using the multicomputing interrupt (OB 60), you can respond synchronously to an event in multicomputing on the corresponding CPUs. In contrast to the process interrupts triggered by signal modules, the multicomputing interrupt can be output only by CPUs. The multicomputing interrupt is triggered by calling SFC 35 “MP_ALM“. You will find more information in the System Software for S7-300/400, System and Standard Functions manual. 1.9.3 Configuring and Programming Multicomputing Operation Please refer to the manual Configuring Hardware and Communication Connections with STEP 7 V5.2 to find out how to configure and program the CPUs and the modules. Automation System S7-400 CPU Specifications A5E00165965-01 1-29

Structure of a CPU 41x 1.10 Modifications to the System During Operation The ability to modify the system during operation using CiR (Configuration in RUN) allows you to make certain changes to the configuration in the RUN mode. Processing is halted for a brief period in order to accomplish this. The upper limit of this time period is set to one second by default but can be changed. During this time, the process inputs retain their most recent value (see the manual, “ Modifications to the System During Operation Using CiR” You can download a free copy of this manual from the Internet address:http://www.siemens.com/automation/service&support You can modify the system during operation using CiR in system segments with distributed I/O. This requires a configuration as shown in the following illustration. To simplify the example, only one DP master system and one PA master system are shown. These restrictions do not apply in actual practice. MPI/DP interface of a CPU 41x or DP interface of a CPU 41x-2 or interface module IF 964-DP or an external DP interface module CP 443-5 ext. PROFIBUS: DP Master System ÉÉÉÉÉÉÉÉÉÉÉ ÉÉÉÉÉÉÉÉÉÉÉ ÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉ ÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉ DP Master IM 157+ DP/PA Coupler Modular DP Slave ET200M, ET200S or ET200iS PA Link SUBNET: PA Master System PA Slave (field device) Compact DP Slave Figure 1-8 1-30 PA Slave (field device) Overview: Architecture enabling modification of a system during operation Automation System S7-400 CPU Specifications A5E00165965-01

Structure of a CPU 41x Hardware Requirements for Modification of a System During Operation The following hardware requirement must be fulfilled during the commissioning phase in order to be able to subsequently modify the system during operation: • An S7-400 standard CPU (CPU 412, CPU 414, CPU 416 or CPU 417), firmware V3.1 or later, or an S7-400-H-CPU (CPU 414-4H or CPU 417-4H) in single mode. firmware V3.1 or later. • If you wish to modify the system during operation on a DP master system with an external DP master (CP 443-5 extended), it must have firmware V5.0 or later. • If you want to add modules for the ET 200M: Use the IM153-2 version MLFB 6ES7 153-2AA03-0XB0 or later or the IM 153-2FO version MLFB 6ES7 153-2BB00-0XB0 or later. You will also need to install the ET 200M with active bus elements and with enough free space for the planned expansion. You may not install the ET 200M as DPV0 slave (using a GSD file). • If you wish to add entire stations: be sure to include the required bus connectors, repeaters, etc. • If you wish to add PA slaves (field devices): use IM157 version 6ES7157-0AA82-0XA00 or later in the corresponding DP/PA Link. • Rack CR2 cannot be used. • The cannot use one or more of the following modules within a station where you wish to modify the system during operation using CiR: CP 441-1, CP 441-2, CP 444. • No multicomputing • No multimaster configuration • No use of I-slaves on DP master systems from where you wish to modify the system during operation using CiR. If you have configured a CPU 41x as a I-slave on one of your interfaces (MPI/DP, DP or interface module IF 964-DP) and one or more additional DP master systems go out from this CPU (via the other interfaces or via an external DP interface module CP 443-5), then the following applies: you can modify the system during operation using CiR on these additional DP master systems (although you cannot reconfigure the I-slave interface). Note You can freely mix components that are cable of system modification during operation and those that are not (except for those listed above). However, you can only make system modifications to CiR-capable components. Automation System S7-400 CPU Specifications A5E00165965-01 1-31

Structure of a CPU 41x Software Requirements for System Modifications During Operation To be able to change a configuration in RUN mode, the user program must fulfill the following requirement: it must

simatic_s7_400 - Siemens

These presentations are classified and categorized, so you will always find everything clearly laid out and in context.
You are watching All you need to know about the Microsoft Band presentation right now. We are staying up to date!