What are the functional restrictions of old releases and firmware versions for the S7-400 CPUs operating in conjunction with the CP443-5 Extended V6.1?
Description This entry gives an overview of the functional restrictions for old releases and firmware versions of the S7-400 CPUs operating in conjunction with the CP443-5 Extended V6.1.
Restrictions for old releases of the S7-400 CPUs Table 01 shows S7-400 CPUs that are no longer supplied and which support or do not support the functions as listed below when operating in conjunction with the CP443-5 Extended V6.1:
No DPV1 functionality
No CiR functionality (DP slave, configurable extension)
No determination of bus topology from the user program
Max. number of external DP segments per station: 4
Number of CPs able to be operated: 8
Multicomputing
CPU
Order number
Release
Number of AG_SEND or AG_RECV calls
that can be operated in parallel
SYNC/FREEZE
CPU412
6ES7412-1XF01-0AB0
6ES7412-1XF02-0AB0
As from 2
As from 2
12/12
12/12
-
+
CPU413
6ES7413-1XG01-0AB0
6ES7413-1XG02-0AB0
As from 2
As from 1
12/12
12/12
-
+
CPU413-2
6ES7413-2XG01-0AB0
6ES7413-2XG02-0AB0
As from 2
As from 1
12/12
12/12
-
+
CPU414-1
6ES7414-1XG01-0AB0
6ES7414-1XG02-0AB0
As from 2
As from 2
12/12
12/12
-
+
CPU414-2
128 KB
6ES7414-2XG01-0AB0
6ES7414-2XG02-0AB0
As from 2
As from 2
12/12
12/12
-
+
CPU414-2
384 KB
6ES7414-2XJ00-0AB0
6ES7414-2XJ01-0AB0
As from 4
As from 2
12/12
12/12
-
+
CPU416-1
6ES7416-1XJ01-0AB0
6ES7416-1XJ02-0AB0
As from 2
As from 1
32/32
32/32
-
+
CPU416-2
0.8 MB
6ES7416-2XK00-0AB0
6ES7416-2XK01-0AB0
As from 4
As from 1
32/32
32/32
-
+
CPU416-2
1.6 MB
6ES7416-2XL00-0AB0
6ES7416-2XL01-0AB0
As from 4
As from 1
32/32
32/32
-
+
Table 01
Restrictions for S7-400 CPUs as from firmware version V3.1
CPU
Order number
6ES7...-0AB0
Firmware
version
Number of
AG_SEND or
AG_RECV calls
that can be operated
in parallel
SYNC/
FREEZE
DPV1
CiR/
HKiR
Enable /
disable
DP slaves
Determine
bus
topology
412
...412-1XF03...
As from V3.1
24/24
+
+
+
+
-
412-2
...412-2XG00...
As from V3.1
24/24
+
+
+
+
-
414-2
...414-2XG03...
As from V3.1
24/24
+
+
+
+
-
412-3
...414-3XJ00...
As from V3.1
24/24
+
+
+
+
-
414-4H
...414-4HJ00...
As from V3.1
24/24
-
+
+
-
-
416-2
...416-2XK02...
As from V3.1
64/64
+
+
+
+
-
416-3
...416-3XL00...
As from V3.1
64/64
+
+
+
+
-
416F-2
...416-2FK02...
As from V4.0
64/64
+
+
+
+
-
417-4
...417-4XL00...
As from V3.1
64/64
+
+
+
+
-
417-4H
...417-4HL00...
...417-4HL01...
As from V2.1
As from V3.1
64/64
64/64
-
-
-
+
+
+
-
-
-
-
Table 02
Which modules can you use when implementing software redundancy?
Description Software Redundancy (SWR) is a software package for configuring fault-tolerant controllers with standard components. The controller part consists of standard CPUs of the S7-300 and S7-400 series. The redundancy link for synchronizing the redundant CPUs is achieved with standard communication mechanisms like CPs or via an MPI interface. Connection to I/O devices is via two redundant PROFIBUS DP segments to the ET-200M stations with redundant IM 153-2 interface modules. You can also implement Software Redundancy on WinAC RTX as from version 2008.
Note
More information is available in the function manual "Software Redundancy for SIMATIC S7" in Entry ID 1137637.
The following table lists modules that support software redundancy. The lowercase letter x is a wildcard character in the order numbers.
Note
The ET 200M stations must always be configured with active bus modules (6ES7195-7HB00-0XA0 or 6ES7195-7HC00-0XA0), even if the "Hot swapping of I/O modules" function is not possible with S7-300 CPUs.
Which organization blocks do you have to load into the CPU to ensure that the CPU does not go into the "STOP" status when a remote I/O fails?
Configuration Notes:
If the CPU recognizes an asynchronous or synchronous error during the cyclical run (e.g. diagnostics alarm of a DP slave or PROFINET I/O device, station failure, etc.), it calls an appropriate organization block (OB). Users thus have the option of responding to this event.
The following OBs have to be loaded in the CPU to ensure that they can be called by the CPU's operating system if an asynchronous or synchronous error occurs.
OB no.
Explanation
OB called
if
Error
category
Call upon
incoming event
Call upon
outgoing event
82
Diagnostics alarm
A diagnostics-compatible module, for which you have enabled the diagnostics alarm, detects an error and when the error is cleared
(e.g. a short circuit in the input module).
Asynchronous error
Yes
Yes
83
Remove/plug alarm1)
A module in the central or expansion devices is removed and plugged in (e.g. an input module is removed).
Asynchronous error
Yes
Yes
85
Program
cycle error
- A start event for an Alarm OB is present, but the OB cannot be executed because it has not been loaded into the CPU
- An error has occurred when accessing the instance DB of a system function block.
- An error has occurred when updating the process image (module missing or defective).
Asynchronous error
Configuration-specific
Configuration-specific
86
Module rack
failure
Failure of a DP slave in a PROFIBUS DP master system or of an IO device in the PROFINET IO system.
Asynchronous error
Yes
Yes
121
Programming
error
A programming error has occurred (e.g. called block is not loaded).
Synchronous error
Yes
No
122
IO access
error
An attempt is made to access a non-existent signal module.
Synchronous error
Yes
No
1) In the S7-300 CPU, there is no remove/plug alarm when removing/plugging in modules that are used on the PROFIBUS DP, like removing a DP slave module (exception: CPU 318-2). Depending on the DP slave used, the complete DP slave fails, which leads to OB86 "Subrack failure" being called, or standard diagnostics are performed, which leads to OB82 "Diagnostics alarm" being called.
In the S7-300 CPU, there is a remove/plug alarm only when removing/plugging in modules that are used on the PROFINET IO (e.g. removing an IO device).
If the above-mentioned organization blocks are not loaded in the CPU, the CPU switches to the "STOP" mode after attempting to call them.
Warning: If you use the error OBs, then error handling should be programmed for reliable and error-free plant operation or at least a message should be generated in case of an error. Please take into account that the CPU might no longer go into "STOP" and thus dangerous plant statuses might remain unnoticed.
Detailed information on programming the error OBs is available in the STEP 7 Online Help or in the manual "System Software for S7-300/400 System and Standard Functions" in Entry ID: 1214574.
Further information and notes: The diagnostics buffer of the CPU contains more information and notes about which organization block the CPU has called.
More detailed information on individual error OBs is also available in the STEP 7 Online Help under the following keywords:
"Diagnostics > Measures in the program for error handling"
"Calling reference data (LAD/FBD/STL, blocks ...) > Language description, block help, system attributes > Help on OBs"
"Error OBs"
"Settings for reporting system errors"
The following entry tells you which organization blocks do you need for error handling in the S7 program of the CPU: 11499205.
How do you find out further technical information about your module?
Description: In the following you will be shown how to access detailed technical data about the module you use. This is done using an S7-300 CPU315 as an example.
First of all, enter the name of the module you use (without its version designation, e.g.: CPU314, SM322, CP343, ET200S, ...) in the search line:
Fig. 01
While you are making your input, a product link window, which is shown in Fig. 2, appears to the left of the search line. The modules which match the keyword appear here. Now look for the module you use on the basis of the order number.
Fig. 02
Notes:
If the list in Fig. 2 does not include the module which you use, this indicates that this module has been phased out for a number of years. In this case, there will be no further technical information available.
Alternatively, you can also enter the start of an order number (e.g. 6es7315) instead of a module name.
Now left-click the module you use in the product link window. The corresponding product information then appears. It is shown in Fig. 3.
Fig. 03
You can find the following information, among others, in the Entries tab:
Downloads
FAQs
Certificates
Manuals and operating instructions
Applications
You can find further information about the module which you use in the Technical Data tab.
Which communication services supported by the CPUs with integrated PROFINET interface and by the WinAC RTX via Industrial Ethernet?
Description The table below gives you an overview of the communication services that are supported by the CPUs with integrated PROFINET interface and by the WinAC RTX (F) via Industrial Ethernet.
The following entries include the manuals for the above-mentioned CPUs, which provide more information on the Technical Data, Communication Services and Quantity Frameworks.
The following entries give you an overview of the communication services that are supported by the S7-300 and S7-400 Industrial Ethernet CPs: Entry IDs 16767769 and 15368142.
Keywords S7 communication, Open communication services, PROFINET IO, TCP, ISO-on-TCP, UDP, IO device, IO controller, PROFINET CBA
Implementation of SIMATIC modules of the product families S7-300, S7-400, ET 200M, ET 200S ET, 200iSP and TDC in environments with high concentrations of corrosive gas
are also approved for implementation in environments with high concentrations of corrosive gas in compliance with ISA–S71.04 severity level G1; G2; G3.
The relevant information is given in the manuals of the product families S7-300, S7-400, ET 200M, ET 200S, ET 200iSP and TDC.
Please refer to the relevant manuals for more information on climatic environmental conditions.
Where can you find images, graphics, symbols and screenshots for SIMATIC industrial automation systems?
Description: The SIMATIC S7 automation system complies with various different regulations and standards. You can read and if necessary, download the currently available certificates and approvals on the Service & Support pages in the Internet at:
In Product Support, you select the desired product group, e.g. S7-300/S7-300F.
There, you select the Entry list tab and in the Entry type drop-down list you select Certificates.
Using the filters you can narrow down the selection to specific certificates, e.g. UL.
Bild 01
Note: If you select a single product (Product View), you select the Entries tab; otherwise the procedure is identical.
Keywords:
Test certificate
Which SIMATIC S7 components and which drives support clock-synchronicity functionality?
Configuration notes: Clock synchronicity is used to establish a direct connection between the equidistant DP cycle, the I/O modules and the user program.
The following SIMATIC components support clock-synchronicity functionality:
S7-300 CPUs
CPU 315 and CPU317 as DP masters from FW 2.5
CPU 319 as DP masters from FW2.4
S7-400 standard and S7-400F CPUs as DP masters from FW 3.1
ET 200M with selected modules
ET 200S with selected modules
Repeaters and diagnostics repeaters
Please note that only the internal DP interfaces on the CPUs can be used for clock-synchronicity communication.
STEP 7 V5.2 or higher is required for configuration purposes.
The drives which support the clock-synchronicity functionality are the entire product group comprising "SIMODRIVE 611U", "SINAMICS" and "MASTERDRIVE MC".
The following are required in order to configure the drives: Drive ES Basic V5.2 or higher, STEP 7 V5.2 or higher and one of the CPUs mentioned above.
You can find a list with the precise designations of the SIMATIC modules, which support clock-synchronicity functionality, in the manual SIMATIC Clock Synchronicity in subsection 2.2.1 of Entry ID 15218045
Keywords: Constant bus cycle time, Compatibility list
Retentivity behavior of S7-400 CPUs and the CPU 318-2 CPUs
Description: The retentivity behavior of the separate variables is important for developers when creating programs. Developers usually have variables in their programs, whose contents are to be retained even during POWER OFF (retentive) and other variables that then have to be reset to a defined value (non-retentive). In SIMATIC STEP 7 developers can therefore configure retentive address areas for data, markers, S7 timers and S7 counters which can they can then use for the retentive variables. In this entry we describe the retentivity behavior of the address areas with SIMATIC S7-400 CPUs and the CPU 318-2 CPUs. The retentivity behavior of the address areas is described for the POWER OFF/ON change of status, the STOP/RUN operating mode and for overall reset.
The behavior in operating mode STOP/RUN and at POWER OFF/ON depends on:
The CPU.
The use of battery, RAM memory card and FLASH memory card.
The parameterization in the HW Configuration.
The "Non-Retain" property set for each separate data block.
Program blocks and data blocks at POWER OFF/ON with/without buffer battery
The following points hold for program blocks and data blocks at POWER OFF/ON:
Without buffer battery:
S7-400 CPUs: If the program and data blocks in the main memory are not buffered by a battery, then the S7-400 CPU is completely reset after POWER OFF/ON. Then the runtime-relevant data blocks and program blocks are reloaded into the main memory from the FLASH memory card (if slotted).
In the case of all data blocks the current values are reloaded from the load memory (FLASH memory card). If there are no current values in these data blocks in the load memory, then the initial values are loaded from the load memory.
CPU 318-2: If the program and data blocks in the main memory are not buffered by a battery, then they are lost after POWER OFF/ON. However, the values in the retentive address areas - as configured in the hardware configuration (see Table 03) - are retained. After POWER OFF/ON the runtime-relevant data blocks and program blocks are reloaded from the FLASH memory card (if slotted) into the main memory, whereby the values for retentive data block elements are taken from the retentive memory.
In the case of non-retentive data blocks the current values are reloaded from the load memory (FLASH memory card). If there are no current values in these data blocks in the load memory, then the initial values are loaded from the load memory.
S7-400 CPUs: and CPU 318-2: Program and data blocks in the internal RAM load memory or on the RAM memory card are lost at POWER OFF/ON without buffer battery.
With buffer battery:
S7-400 CPUs: and CPU 318-2: If you use a battery, the program and data blocks are buffered in the main memory. They are retained after POWER OFF/ON.
In the case of a parameterized warm start or restart after POWER ON there are no changes to the data block contents (restart only with S7-400).
In the case of a parameterized cold start after POWER ON the current values of the data blocks are reloaded from the load memory. If there are no current values in these data blocks in the load memory, then the initial values are loaded from the load memory.
CPU 318-2: If you use a buffer battery, all the data blocks are buffered with CPU 318-2. All the values of the data blocks are retained at POWER OFF/ON.
Differences between overall reset and "POWER OFF/ON without buffer battery and without memory card" with CPU 318-2
In the case of "POWER OFF/ON without buffer battery and without memory card" the retentive areas remain unaffected with CPU 318-2. If the program is reloaded in this case, then it works with the old values from the retentive area. By default these are the first 8 counters, for example. This can lead to dangerous plant statuses if you don't take this into account.
Recommendation:
After a "POWER OFF/ON without buffer battery and without memory card" always do an overall reset.
Data, markers, S7 timers and S7 counters at POWER OFF/ON
The following Table 01 gives an overview of the retentivity behavior with data, markers, S7 timers and S7 counters in the various startup modes at POWER OFF/ON.
Startup mode
POWER OFF/ON
Cold start
All markers, S7 timers and S7 counters are deleted.
The current values of the data blocks are reloaded from the load memory. If there are no current values in these data blocks in the load memory, then the initial values are loaded from the load memory.
Warm start
All retentive markers, S7 timers and S7 counters are retained.
All non-retentive markers, S7 timers and S7 counters are deleted. (In the case of an unbuffered 400-series CPU the retentive markers, S7 timers and S7 counters are also deleted.)
In the case of retentive data blocks ("Non-Retain" disabled) the values are retained.
In the case of non-retentive data blocks ("Non-Retain" enabled) the current values are reloaded from the data blocks in the load memory. If there are no current values in these data blocks in the load memory, then the initial values are loaded from the load memory.
Restart (only S7-400)
All markers, S7 timers and S7 counters are retained.
The values are retained for all data blocks.
It is only possible to restart the CPU in buffered status.
Table 01
Data, markers, timers and counters with the STOP/RUN operating mode
The following Table 02 gives an overview of the retentivity behavior with data, markers, S7 timers and S7 counters in the various startup modes with the STOP/RUN operating mode.
Startup mode
STOP/RUN operating mode
Cold start
All markers, S7 timers and S7 counters are deleted.
The current values of the data blocks are reloaded from the load memory. If there are no current values in these data blocks in the load memory, then the initial values are loaded from the load memory.
Warm start
All retentive markers, S7 timers and S7 counters are retained.
All non-retentive markers, S7 timers and S7 counters are deleted.
In the case of retentive data blocks ("Non-Retain" disabled) the values are retained.
In the case of non-retentive data blocks ("Non-Retain" enabled) the current values are reloaded from the data blocks in the load memory. If there are no current values in these data blocks in the load memory, then the initial values are loaded from the load memory.
Restart (only S7-400)
All markers, S7 timers and S7 counters are retained.
The values are retained for all data blocks.
Table 02
Configuring retentive address areas in SIMATIC STEP 7
The following Table 03 describes how to proceed to configure retentive address areas.
No.
Procedure
1
Open the Hardware Configuration of your S7-400 station (or CPU 318-2). Double-click on the icon of your CPU --> The "Properties - CPU 41x ..." window opens.
Fig. 01
2
Select the "Retentive Memory" tab.
Fig. 02
3
In the "Retentive Memory" tab, in the "Retentivity" field you can configure the retentive address areas for:
Markers
S7 timers
S7 counters
Only CPU 318-2: In the "Areas" field you can also define the retentive areas in data blocks. The "Non-Retain" property of the data blocks is not supported by CPU 318-2.
Warning:
Please make sure that your data blocks defined as retentive are available in the CPU 318-2 and are not too short.
Fig. 03
4
After configuring the desired retentive areas you can quit the CPU Properties dialog via "OK" or make changes in other tabs.
Table 03
Configuring retentivity behavior of data blocks in SIMATIC STEP 7
In S7-400 CPUs all the data blocks are preset to retentive. It is possible to disable retentivity individually for each data block. The following Table 04 describes how to set the retentivity behavior of a data block. Warning:
The CPU 318-2 does not support the data block property "Non-Retain". However, the "Non-Retain" selection field is not disabled in STEP 7.
No.
Procedure
1
Mark the data block for which you wish to change the "Non-Retain" property. In the menu bar you select "Edit > Object Properties..." or press the key combination [Alt] + [Return]. This opens the data block's "Properties..." window.
Fig. 04
2
In the "Properties..." dialog select the "General - Part 2" tab.
Fig. 05
3
When you enable the "Non-Retain" option, the data block is no longer retentive.
Fig. 06
Table 04
Overall reset
The following Table 05 gives an overview of the overall reset procedures.
Overall reset with S7-400 and CPU 318-2
The following elements are deleted in the memory:
User program in the internal load memory (RAM)
User program on the RAM memory card (if slotted)
All markers, S7 timers and S7 counters
The following elements are retained:
Contents of the diagnostics buffer
Contents of the FLASH memory card
Time
Protection level set
Status and value of the elapsed time counter
Procedures after overall reset with slotted RAM memory card or without memory card:
Without FLASH memory card the original MPI interface parameters are retained.
Since the complete user program has been deleted, you must transfer a new program.
Important:
If you wish to communicate with the CPU from your PG/PC after the overall reset, the only option you have for setting up this communication is via the MPI or MPI/DP interface.
Procedures after overall reset with slotted FLASH memory card:
If you have a flash memory card inserted, following the overall reset the CPU copies the user program and the system parameters saved on the flash memory card to the main memory.
In the case of data blocks the current values are reloaded from the data blocks on the FLASH memory card. If there are no current values in these data blocks on the FLASH memory card, then the initial values are loaded from the load memory.
When the FLASH memory card is slotted the MPI parameters from the FLASH memory card are valid after the overall reset.
Table 05
S7-400: Operating Mode Switch at the new CPU 41x (as of FW Version 4.0)
QUESTION:
What are the functions of the Operating Mode Switch of new CPUs
(as of Firmware Version 4.0)?
ANSWER:
New CPUs (Truncated Order No.: 6ES741x-xxx04-0AB0) are
fitted with a toggle switch that has already been successfully in
use with the S7-300 for some time. This toggle switch has three
positions to select the current operating mode. The old key switch
is void.
Old
New
RUN-P
RUN
RUN
RUN + Protection Level 2
STOP
STOP
MRES
MRES
Tab. 1: Comparison of old and new functions of the Operating
Mode Switch
Positions of the Operating Mode Switch
RUN (previously RUN-P)
The CPU processes the application program. In this case access to
the periphery is possible. Programs can be retrieved with the PG
from the CPU (CPU –> PG) as well as transferred into the CPU (PG
–> CPU). Via protection level 2 (CPU configuration via HW
Config) the operating mode can be locked: merely read-only
with blocks (previously RUN).
STOP
The CPU does not process an application program. Access to the
peripherie is not possible. Programs can be retrieved with the PG
from the CPU (CPU –> PG) as well as transferred into the CPU (PG
–> CPU).
MRES (Master Reset)
Position of the switch for the master reset of the CPU.
Note: Cold start is further possible via STEP 7, but
no longer via the operating mode switch.
