show the entry list
Operating System Updates: CPU412-3H / CPU414-4H / CPU414-4H PG / CPU417-4H and CPU412-5H PN/DP, CPU414-5H PN/DP, CPU416-5H PN/DP, CPU417-5H PN/DP
Part number:

 

Latest Firmware V6.0.3 for:

6ES7 412-5HK06-0AB0 Link to Operating System Update
6ES7 414-5HM06-0AB0 Link to Operating System Update
6ES7 416-5HS06-0AB0 Link to Operating System Update
6ES7 417-5HT06-0AB0 Link to Operating System Update 

Latest Firmware V4.5.6 for:

6ES7 412-3HJ14-0AB0 Link to Operating System Update
6ES7 414-4HM14-0AB0 Link to Operating System Update
6ES7 414-4HR14-0AB0 Link to Operating System Update
6ES7 417-4HT14-0AB0 Link to Operating System Update
 

Latest Firmware V4.0.12 for:

6ES7 414-4HJ04-0AB0 Link to Operating System Update
6ES7 417-4HL04-0AB0 Link to Operating System Update



 
DESCRIPTION:

FW Update for Firmware V4.5.x and higher
Updating the firmware is possible in RUN mode starting with this firmware version. An update is only possible from one version to the next, e.g., from V4.5.0 to V4.5.1.
Please refer to the respective update description and the system manual "Fault-tolerant Systems S7-400H" - chapter 6.1 "Updating the Firmware without a Memory Card" and chapter 6.2 "Firmware Update in RUN mode".

FW Update for Firmware up to V4.0.x
Whether an update to a new firmware version can be performed depends on the affected production facility, since an update is only possible, if the facility is turned off.   
An update of the H system to the latest firmware version is only possible while the facility is off.

Parts Replacement
On how to proceed in case of a parts replacement (keeping the previous firmware version) is described here.


Downgrading to an older Firmware Version
In the case of a CPU417-4H (order number 6ES7 417-4HL01-0AB0) with a test date of R, S or T, a downgrade can only be performed down to and including V3.0.0. The test date can be identified by the yellow test sticker on the back of the module. The test date is on the second line below SIEMENS/TESTED and following VP.
If a downgrade is desired and the above restriction applies, please contact your local Siemens office.
 

Should you encounter Problems during the Firmware Update ...
CPUs delivered during a particular delivery period can exhibit problems during the firmware update. 

These CPUs can be identified by one of the following error patterns:

  • All LEDs permanently remain lit, i.e., for longer than the normal update process of up to approx. 4 minutes
  • The LEDs INTF and EXTF blink 

Should you encounter one of the above problems, an error correction is available.


Prerequisites for the Creation of an Operating System Update Card

  • S7 memory card
    Operating system version < V4.5.0: Flash 4 MB (order number 6ES7 952-1KM00-0AA0) or higher
    Operating system version >= V4.5.0: Flash 8 MB (order number 6ES7 952-1KP00-0AA0) or higher
  • STEP 7 V3.1 or higher
  • PG or PC with external prommer for programming the memory card 

Creating the Operating System Update Card with STEP 7

  • Download the desired CPU file
  • Unpack the file by double-clicking on the file name
  • In the SIMATIC Manager, delete the memory card by means of "File / S7 Memory Card / Delete"
  • Program the operating system by selecting "Target System / Update AS Operating System" in the SIMATIC Manager and selecting the target folder; start the programming process by opening the file "CPU_HD.UPD".
    The operating system update card has been programmed once the default mouse pointer reappears.

General procedure for updating the Operating System

  • Power off the power supply (PS) of the rack in which the CPU is inserted
  • Insert the prepared operating system update card into the CPU
  • Power ON the power supply (PS) of the rack in which the CPU is inserted
  • The operating system is transferred from the memory card to the internal FLASH EPROM; during this process, all indicator LEDs on the CPU are lit (INTF, EXTF, FRCE, CRST, RUN, STOP). The operating system update will take approx. 2 minutes; completion is indicated by the STOP LED at the CPU flashing slowly => prompt by the system for overall reset.
    CAUTION:
    Immediately following the update, a self-test is started, which takes a few minutes depending on the memory size. 
  • Power off the power supply (PS) and if necessary insert the memory card intended for operations
  • Power on the power supply (PS); the CPU automatically performs an overall reset and is then immediately operational
  • After a successful operating system update please set the time.

 

Updating the Operating System in RUN mode for V4.5 and higher

The general rule is that if the firmware is updated in RUN mode, the update is only possible from one firmware version to the next higher version. Downgrading in RUN mode is not possible. Please also note the instructions provided in the respective, version-specific description.

To update the firmware of H system CPUs in RUN mode, proceed as follows:

  • Place one of the CPUs in STOP mode using a PG/PC
  • Select this CPU in HW-Config
  • Execute the menu command "Target System > Update Firmware"; the dialog box "Update Firmware" will open; in this box, select the firmware file to be uploaded to the CPU
  • In the SIMATIC Manager or HW-Config, select the menu command "Target System -> Operating Mode -> Switch to" CPU 41xH and select the radio button "with changed Operating System"
  • Perform steps 1 to 3 for the other CPU
  • Switch the system to the redundant operating mode by starting this CPU.

 

Information on Parts Replacement
If the system is to be operated with the previous firmware version, the newly acquired CPU has to be downgraded to the firmware version of the CPU still running. This can either be accomplished via a memory card (as with V4.0.x) or via the online functionality (see manual).
 

Up to Firmware V4.0.x
In an S7-400H system, both CPUs must have the same firmware version. If one CPU of your S7-400H fails, order a new CPU with exactly the same order number. It will be delivered with the latest firmware version.
Further action depends on whether the system must continue to run without interruption or whether it can be stopped briefly. If stopping the system is not permissible, then the newly obtained CPU must be downgraded to the firmware version of the CPU still running. In that case, proceed as follows:

  • Create an operating system update card containing the firmware version of the failed CPU
  • Use this card to transfer the firmware version of the failed CPU to the new CPU
  • Both CPUs now have the original firmware version; your S7-400H can now be switched to the redundant operating mode 

If an overall stop of the system can be tolerated, the existing CPU can be updated to the latest version by stopping the system.

 

Firmware V4.5.x and higher
In an S7-400H system, both CPUs must have the same firmware version. If one CPU of your S7-400H fails, order a new CPU with exactly the same order number. It will be delivered with the latest firmware version, which can be higher than that of the predecessor CPU. In that case, the new CPU must be downgraded to the older firmware version.

Two options are available for downgrading: 

1. Via a memory card as with V4.0.x 
    (see above description)

2. Via the online functionality as follows:

  • Insert the new CPU into your automation system
  • Do not yet connect the fiber-optic cables
  • Select this CPU in HW-Config or the SIMATIC Manager
  • Execute the menu command "Target System > Update Firmware"; the dialog box "Update Firmware" will open; in this box, select the version of the firmware file that corresponds to the predecessor CPU
  • Upload this file to the CPU; the new CPU now has the same firmware version as the previously employed CPU
  • Connect the fiber-optic cables
  • Switch the system to the redundant operating mode by starting this CPU.

 

Difference of this Operating System Update compared to the other S7-400 CPUs

Following the actual firmware update, a self-test will start with the H system. This can take several minutes depending on the size of the load memory (size of the memory card inserted) and the size of the main memory.  

  Overview of order numbers and latest versions of the S7-400-H-CPUs
Order Number

FW Version

Upgrade with ...
6ES7412-3HJ14-0AB0    
 

V4.5.6

16.05.12; Recommended as Update:

V4.5.6 Description

 4123HJ14_V456.exe ( 1452 KB )

 

V4.5.5

06.06.11; Backup only: 

V4.5.5 Description

 4123HJ14_V455.exe ( 1451 KB )

 

V4.5.4

28.01.11; Backup only: 

V4.5.4 Description

 4123HJ14_V454.exe ( 1451 KB )

 

V4.5.3

05.02.10; Backup only: 

V4.5.3 Description

 4123HJ14_V453.exe ( 1421 KB )

 

V4.5.2

19.01.09; Backup only:

V4.5.2 Description

 4123HJ14_V452.EXE ( 1422 KB )

 

V4.5.1

11.04.08; Backup only:

V4.5.1 Description

 4123HJ14_V451.EXE ( 1421 KB )

 

V4.5.0

21.09.07; Backup only:

V4.5.0 Description

 4123HJ14_V450.EXE ( 1419 KB )

     
6ES7412-5HK06-0AB0    
 

V6.0.3

13.09.2013; Recommended as Update:

Update V6.0.3 Description

 4125HK06_V603.exe ( 5051 KB )

 

V6.0.2

12.12.2012; Backup only:

Update V6.0.2 Description

 4125HK06_V602.exe ( 5361 KB )

 

V6.0.1

Backup only:

Update V6.0.1 Description

 4125HK06_V601.exe ( 5361 KB )

     
6ES7414-4HJ00-0AB0    
 

V3.1.5

Recommended as Update:

Update V3.1.5 Description

 4144HJ00_V315.EXE ( 2049 KB )

 

V3.1.4

Backup only:

Update V3.1.4 Description

 4144HJ00_V314.EXE ( 2044 KB )

 

V3.1.3

Backup only:

Update V3.1.3 Description

 4144HJ00_V313.EXE ( 1019 KB )

 

V3.1.1

Backup only:

Update V3.1.1 Description

 4144HJ00_V311.EXE ( 1018 KB )

 

V3.1.0

Backup only:

Update V3.1.0 Description

 4144HJ00_V310.EXE ( 1018 KB )

 

V3.0.1

Backup only:

Update V3.0.1 Description

 F4_4HJ00.exe ( 950 KB )

 

V3.0.0

Backup only:

Update V3.0 Description

 E4_4HJ00.exe ( 939 KB )

 

V2.1.2

Backup only:

Update V2.1.2 Description

  D144HJ00.exe ( 930 KB )

 

V2.1.1

Backup only:

Operating System File V2.1.1

  C144HJ00.exe ( 930 KB )

     
6ES7414-4HJ04-0AB0    
 

V4.0.12

19.04.10; Recommended as Update:

Update V4.0.12 Description

 4144HJ04_V4012.exe ( 1386 KB )

 

V4.0.11

14.11.08; Backup only: 

Update V4.0.11 Description

 4144HJ04_V4011.EXE ( 1385 KB )

 

V4.0.10

22.08.07; Backup only: 

Update V4.0.10 Description

 4144HJ04_V4010.EXE ( 1383 KB )

 

V4.0.9

30.03.07; Backup only:

Update V4.0.9 Description

 4144HJ04_V409.EXE ( 1383 KB )

 

V4.0.8

16.10.06; Backup only:

Update V4.0.8 Description

 4144HJ04_V408.EXE ( 1382 KB )

 

V4.0.7

23.02.06; Backup only:

Update V4.0.7 Description

 4144HJ04_V407.EXE ( 1381 KB )

 

V4.0.6

23.11.05; Backup only:

Update V4.0.6 Description

 4144HJ04_V406.EXE ( 1381 KB )

 

V4.0.5

17.10.05; Backup only:

Update V4.0.5 Description

 4144HJ04_V405.EXE ( 1381 KB )

 

V4.0.4

27.04.05; Backup only:

Update V4.0.4 Description

 4144HJ04_V404.EXE ( 1368 KB )

 

V4.0.3

14.02.05; Backup only:

 4144HJ04_V403.EXE ( 1337 KB )

     
6ES7414-4HM14-0AB0    
 

V4.5.6

16.05.12; Recommended as Update:

V4.5.6 Description

 4144HM14_V456.exe ( 1453 KB )

 

V4.5.5

06.06.11; Backup only: 

V4.5.5 Description

 4144HM14_V455.exe ( 1452 KB )

 

V4.5.4

28.01.11; Backup only:   

V4.5.4 Description

 4144HM14_V454.exe ( 1452 KB )

 

V4.5.3

05.02.10; Backup only: 

V4.5.3 Description

 4144HM14_V453.exe ( 1422 KB )

 

V4.5.2

19.01.09; Backup only:

V4.5.2 Description

 4144HM14_V452.EXE ( 1423 KB )

 

V4.5.1

11.04.08; Backup only:

V4.5.1 Description

 4144HM14_V451.EXE ( 1422 KB )

 

V4.5.0

21.09.07; Backup only:

V4.5.0 Description

 4144HM14_V450.EXE ( 1420 KB )

     
6ES7414-4HR14-0AB0    
 

V4.5.6

16.05.12; Recommended as Update:  

V4.5.6 Description

 4144HR14_V456.exe ( 1454 KB )

 

V4.5.5

06.06.11; Backup only:

V4.5.5 Description

 4144HR14_V455.exe ( 1453 KB )

 

V4.5.4

28.11.11; Backup only: 

V4.5.4 Description

 4144HR14_V454.exe ( 1453 KB )

 

V4.5.3

05.02.10; Backup only: 

V4.5.3 Description

 4144HR14_V453.exe ( 1422 KB )

 

V4.5.2

19.01.09; Backup only:

V4.5.2 Description

 4144HR14_V452.EXE ( 1424 KB )

 

V4.5.1

11.04.08; Backup only:

V4.5.1 Description

 4144HR14_V451.EXE ( 1423 KB )

 

V4.5.0

21.09.07; Backup only:

V4.5.0 Description

 4144HR14_V450.EXE ( 1421 KB )

     
6ES7414-5HM06-0AB0    
 

V6.0.3

13.09.2013; Recommended as Update:

Update V6.0.3 Description

 4145HM06_V603.exe ( 5050 KB )

 

V6.0.2

12.12.2012; Backup only:

Update V6.0.2 Description

 4145HM06_V602.exe ( 5361 KB )

 

V6.0.1

Backup only:

Update V6.0.1 Description

 4145HM06_V601.exe ( 5361 KB )

     
6ES7416-5HS06-0AB0    
 

V6.0.3

13.09.2013; Recommended as Update:

Update V6.0.3 Description

 4165HS06_V603.exe ( 5051 KB )

 

V6.0.2

12.12.2012; Backup only:

Update V6.0.2 Description

 4165HS06_V602.exe ( 5363 KB )

 

V6.0.1

Backup only:

Update V6.0.1 Description

 4165HS06_V601.exe ( 5363 KB )

     
6ES7417-4HL00-0AB0    
   V2.1.5

Recommended as Update:

Update V2.1.5 Description

  4174HL00_V215.EXE ( 1020 KB )

  V2.1.4

Backup only:

Update V2.1.4 Description

  F7_4HL00.exe ( 952 KB )  

  V2.1.3

Backup only:

Update V2.1.3 Description

  E7_4HL00.exe ( 950 KB )  

 

V2.1.2

Backup only:

Update V2.1.2 Description

  D174HL00.exe ( 931 KB )

 

V2.1.1

Backup only:

Update V2.1.1 Description

  C174HL00.exe ( 921 KB )

 

V2.1.0

Backup only:

Update V2.1.0 Description

  B174HL00.exe ( 919 KB )

 

V1.1.0

Backup only:

Operating System File V1.1.0

  A174HL00.exe ( 803 KB )

     
6ES7417-4HL01-0AB0    
 

V3.1.5

Recommended as Update:

Update V3.1.5 Description

4174HL01_V315.EXE ( 2051 KB )

 

V3.1.4

Backup only: 

Update V3.1.4 Description

4174HL01_V314.EXE ( 2048 KB )

 

V3.1.3

Backup only: 

Update V3.1.3 Description

 4174HL01_V313.EXE ( 1020 KB )

 

V3.1.1

Backup only:

Update V3.1.1 Description

 4174HL01_V311.EXE ( 1019 KB )

 

V3.1.0

Backup only:

Update V3.1.0 Description

 4174HL01_V310.EXE ( 1019 KB )

 

V3.0.1

Backup only:

Update V3.0.1 Description

 F7_4HL01.exe ( 952 KB )

 

V3.0.0

Backup only:

Update V3.0 Description

 E7_4HL01.exe ( 940 KB )

 

V2.1.2

Backup only:

Update V2.1.2 Description

  D174HL01.exe ( 931 KB )

 

V2.1.1

Backup only:

Update V2.1.1 Description

  C174HL01.exe ( 921 KB )

     
6ES7417-4HL04-0AB0    
 

V4.0.12

19.04.10; Recommended as Update:

Update V4.0.12 Description

 4174HL04_V4012.exe ( 1386 KB )

 

V4.0.11

14.11.08; Backup only:

Update V4.0.11 Description

 4174HL04_V4011.exe ( 1385 KB )

 

V4.0.10

22.08.07; Backup only:

Update V4.0.10 Description

 4174HL04_V4010.exe ( 1383 KB )

 

V4.0.9

30.03.07; Backup only:

Update V4.0.9 Description

 4174HL04_V409.exe ( 1383 KB )

 

V4.0.8

16.10.06; Backup only:

Update V4.0.8 Description

 4174HL04_V408.exe ( 1382 KB )

 

V4.0.7

23.02.06; Backup only:

Update V4.0.7 Description

 4174HL04_V407.exe ( 1382 KB )

 

V4.0.6

18.11.05; Backup only:

Update V4.0.6 Description

 4174HL04_V406.exe ( 1381 KB )

 

V4.0.5

17.10.05; Backup only:

Update V4.0.5 Description

 4174HL04_V405.EXE ( 1381 KB )

 

V4.0.4

27.04.05; Backup only:

Update V4.0.4 Description

 4174HL04_V404.EXE ( 1368 KB )

 

V4.0.3

14.02.05; Backup only:

 4174HL04_V403.EXE ( 1337 KB )

     
6ES7417-4HT14-0AB0    
 

V4.5.6

16.05.12; Recommended as Update:

V4.5.6 Description

 4174HT14_V456.EXE ( 1454 KB )

 

V4.5.5

06.06.11; Backup only:

V4.5.5 Description

 4174HT14_V455.EXE ( 1452 KB )

 

V4.5.4

28.01.11; Backup only: 

V4.5.4 Description

 4174HT14_V454.EXE ( 1452 KB )

 

V4.5.3

05.02.10; Backup only: 

V4.5.3 Description

 4174HT14_V453.EXE ( 1422 KB )

 

V4.5.2

19.01.09; Backup only:

V4.5.2 Description

 4174HT14_V452.EXE ( 1424 KB )

 

V4.5.1

11.04.08; Backup only:

V4.5.1 Description

 4174HT14_V451.EXE ( 1422 KB )

 

V4.5.0

21.09.07; Backup only:

V4.5.0 Description

 4174HT14_V450.EXE ( 1421 KB )

     
6ES7417-5HT06-0AB0    
 

V6.0.3

13.09.2013; Recommended as Update:

Update V6.0.3 Description

 4175HT06_V603.exe ( 5051 KB )

 

V6.0.2

12.12.2012; Backup only:

Update V6.0.2 Description

 4175HT06_V602.exe ( 5363 KB )

 

V6.0.1

Backup only:

Update V6.0.1 Description

 4175HT06_V601.exe ( 5363 KB )

     

 

 

 

 

Update V2.1.0 (6ES7 417-4HL00-0AB0)

 
Functional Enhancements:
  • Configuration changes in RUN mode
  • Connecting/updating without disconnection
  • Significant improvement of the runtimes with communications functions
  • Operation in a standard station
  • Connection diagnostics (system status list 0x36H)
  • With 6ES7 417-4HL01-0AB00, there is a larger internal memory to avoid communications bottlenecks

Product Information Firmware V 2.1.0
 PI417_4H.pdf ( 64 KB )

 

 

 

Update V2.1.1 (6ES7 417-4HL00-0AB0)
Update V2.1.1 (6ES7 417-4HL01-0AB0)
The following errors were eliminated for CPU 417H:
  • When connecting/updating with memory expansion, it could happen that even before the update trigger, the inputs/outputs had not been updated for several seconds.
  • With one-sided I/O in rack 1 of the H system, the following situation could occur: If there was a fault in an output module, which resulted in I/O area access errors (I/O AAE), then I/O AAE was also issued for slot 1 of station 1 (smallest address).
  • By reading the diagnostics buffer about the communication, in extremely rare cases there could be loss of redundancy (stop of the standby) with the event ID 7323, if many new entries were created at the same time the diagnostics buffer was read.
  • In the case of systems with F components, connecting/updating could cause the CPU A (see below) to be switched to the STOP operating mode by F drivers shortly after the switchover process. The conditions were:
    - CPU A was at least 1 minute in RUN mode
    - With CPU A, the last POWER ON must have occurred at least 5 seconds sooner than that of CPU B
    - CPU A performs an update of CPU B

Product Information Firmware V 2.1.1
 PI41x_4H.pdf ( 103 KB )

 

 

 

 

Update V2.1.2 (6ES7 414-4HJ00-0AB0)
Update V2.1.2 (6ES7 417-4HL00-0AB0)
Update V2.1.2 (6ES7 417-4HL01-0AB0)
The following errors were eliminated for CPU 414H:
  • With firmware versions lower than V2.1.2, calling the SFC87 "C_DIAG" could cause the input I 38.0 to be changed.
  • Contrary to the information in the current Online Help pertaining to system function / function blocks, the following applies when calling SFC51 "RDSYSST" with SZL_ID:=W#16#0112 and INDEX:=W#16#0400: The characteristic ID W#16#0401 is reserved for the operating system. The (new) characteristic ID W#16#0403 indicates that the SFC87 is available on your CPU

Product Information Firmware V 2.1.2
 product information.pdf ( 104 KB )

 

 

 

 

Update V3.0.0 (6ES7 414-4HJ00-0AB0)
Update V3.0.0 (6ES7 417-4HL01-0AB0)
 

New functions available with V3.0 for all S7-400 CPUs. Full DP V1 integration in compliance with PROFIBUS standard IEC 61158 Part 3-6, compatible with existing devices.

Advantages of this functionality:

  • DP V1 slaves can report quickly to the S7-400 by alarm.
  • This improves the distributed diagnostics performance for DP V1 slaves.
  • Extended parameterization options through data record services. This also permits intelligent field devices to be configured.
  • Many features that previously were only possible with S7 slaves will in the future also be open to other DP manufacturers.
  • Alarms in every operating mode, with new alarm OBs such as status alarm, update alarm and manufacturer-specific alarm.

Further Information on the DP V1 Integration
Descriptions and information on switching from PROFIBUS DP to PROFIBUS DPV1 can be found in entry ID 7027576; information on new OBs/SFBs in connection with DPV1 can be found in entry ID 1214574

Functional enhancements available with V3.0 for all CPUs mentioned above:

  • Time synchronization with status also via PROFIBUS DP interface.
  • Runtime improvement for connection-based master-slave communication.
  • Setting the time and time status with new SFC 100.
  • Consistent user data size in the process image.
  • CPU system identification possible via SZL 0x1C.
  • The cyclic self-test has been extended so that sporadic checksum errors are recognized and corrected before they take effect. 

The following errors have been corrected with Operating System V3.0:

  • In the case of S7-400 CPUs, the EXTF LED did not reset in certain circumstances after a failure of the battery backup. This has been corrected.
  • With S7-400 CPUs, a successful operating system update is now entered correctly in the diagnostics buffer.
  • In the 8x mode of the SFC39, only the "Substitute Event" w#16#5380 and no longer the OB start event is entered.
  • In certain cases, when operating flash memory cards in the CPU, it was necessary to perform a power off/on of the CPU after loading the STEP 7 project, because the CPU reported a parameterization error with startup fault. This has been corrected.
  • In the case of error event 6547 "Parameterization Error when assigning Parameters to K Bus Modules", the module number and slot of the DP master are specified in the detailed information of the event, because the master system ID cannot always be determined upon the error detection. It is likewise possible for inserted sub-modules to display the number of the interface module.

 Product informationV30_H.pdf ( 58 KB )

 

 

 

Update V2.1.3 (6ES7 417-4HL00-0AB0)
 

The following errors have been corrected with Operating System V2.1.3:

  • In the case of S7-400 CPUs, the EXTF LED did not reset in certain circumstances after a failure of the battery backup. This has been corrected.
  • With S7-400 CPUs, a successful operating system update is now entered correctly in the diagnostics buffer.
  • Incorrect values in the SZL424 (operating status) immediately after the status transition have been eliminated.
  • In the 8x mode of the SFC39, only the "Substitute Event" w#16#5380 and no longer the OB start event is entered.
  • In certain cases, when operating flash memory cards in the CPU, it was necessary to perform a power off/on of the CPU after loading the STEP 7 project, because the CPU reported a parameterization error with startup fault. This has been corrected.
  • In the case of error event 6547 "Parameterization Error when assigning Parameters to K Bus Modules", the module rack number and slot of the DP master are specified in the detailed information of the event, because the master system ID cannot always be determined upon the error detection. It is likewise possible for inserted sub-modules to display the number of the interface module.
  • The cyclic self-test has been extended so that sporadic checksum errors are recognized and corrected before they take effect.
  • If the geographical address of a connected slave was determined in the H system, both master system IDs from CPU Rack 0 and CPU Rack 1 were provided, which could lead to synchronization errors.
  • If HMI systems are linked, many screen tags are updated and single-sided events (e.g., alarms and communication functions) occurred in a very small time window, the result could be a sporadic loss of synchronization.

Product Information Firmware V 2.1.3 
 Product informationV213_H.pdf ( 81 KB )


Update V2.1.4 (6ES7 417-4HL00-0AB0)
 

The following errors have been corrected with Operating System V2.1.4:

  • In an H system, central expansion units are attached to master and standby. If the voltage supply of the central expansion units breaks down at both the master and standby within approx. 4 ms, a synchronization error might occur after the voltage returns.
  • After numerous connection faults within short periods of time (e.g., several power off cycles), the CPU - in rare cases - entered the DEFECT mode.
  • A large number of monitoring tasks carried out simultaneously (same cycle) by an OS system could - in very rare cases - lead to a loss of synchronization loss in the H system. 
  • In V2.1.3, it was not possible to read out the time remaining of an activated (not yet started) time delay interrupt via SZL 0x222.
  • If a simplex I/O is assigned to rack 0 of an H system, DEFECT mode may occur in rack 1 when loading a configuration to the CPU.
  • The EXTF LED of the CPU remained lit and did not go out after a power off/on cycle or after the return of a DP standard slave (see FAQ 9824085).

Product Information Firmware V 2.1.4 
 A5E130864.pdf ( 72 KB )    

 

 

 

Update V3.0.1 (6ES7 414-4HJ00-0AB0)
Update V3.0.1 (6ES7 417-4HL01-0AB0)
 

The following errors have been corrected with Operating System V3.0.1:

  • In an H system, central expansion units are attached to master and standby. If the voltage supply of the central expansion units breaks down at both the master and standby within approx. 4 ms, a synchronization error might occur after the voltage returns.
  • After numerous connection faults within short periods of time (e.g., several power off cycles), the CPU - in rare cases - entered the DEFECT mode.
  • A large number of monitoring tasks carried out simultaneously (same cycle) by an OS system could - in very rare cases - lead to a loss of synchronization loss in the H system. 
  • In V3.0.0, it was not possible to read out the time remaining of an activated (not yet started) time delay interrupt via SZL 0x222.
  • If a simplex I/O is assigned to rack 0 of an H system, DEFECT mode may occur in rack 1 when loading a configuration to the CPU.
  • The EXTF LED of the CPU remained lit and did not go out after a power off/on cycle or after the return of a DP standard slave (see FAQ 9824085).

Product Information Firmware V 3.0.1 
 A5E73168.pdf ( 80 KB )  

 



Update V3.1.0 (6ES7 414-4HJ00-0AB0)
Update V3.1.0 (6ES7 417-4HL01-0AB0)
 

V3.1.0 contains the following Functional Enhancements:

  1. Configuration in RUN mode (stand-alone operation):
    Configuration in RUN mode (CiR) permits system expansions and rebuilding during the operating phase.
  2. Reparameterization of modules during the operating phase (within the framework of CiR).
  3. Avoidance of stops with the OB88 (processing stop):
    By programming the OB88, special programming errors will no longer cause a mandatory STOP (errors in the allocation of local data, nesting depth too high in the case of synchronous errors and block calls).
  4. Initiation of the topology determination with diagnostics repeater on PROFIBUS DP by means of SFC103.
  5. Operation of redundant I/Os.
  6. Connection of SIMATIC S5 expansion devices:
    Via an IM463-2 interface module, the connection of S5 I/Os for stand-alone operation of the CPU41x-4H is possible.
  7. DP master systems according to DPV1 and DP master systems according to EN 50170 can be employed in the same system. 

The following errors have been corrected in V3.1.0:

  • Under certain circumstances, a defect could occur in the CPU, whereby the diagnostics buffer would not contain a corresponding (defect) entry after a power off/on cycle.
  • When switching off the supply voltage to the last PROFIBUS DP station of a line (with bus terminating resistor), a loss of synchronization with the event ID 43DA could occur.
  • After repeated power off/on cycles, a PROFIBUS DP slave (according to EN 50170) would no longer be correctly accepted.
  • In an H system coupled with an APPLICOM PCI Ethernet module, the following defect could occur: 4550 / b003 / 8752 / 01ae.

Product information A5E00073168-08:
 A5E73168_08.pdf ( 75 KB )  


Error correction in the case of problems with the operating system update
1. Affected CPUs
6ES7 412-1XF03-0AB0 HW Release: 6
6ES7 412-2XG00-0AB0 HW Release: 6
6ES7 414-2XG03-0AB0 HW Release: 6
6ES7 414-3XJ00-0AB0 HW Release: 6
6ES7 414-4HJ00-0AB0 HW Release: 1
6ES7 416-2XK02-0AB0 HW Release: 6
6ES7 416-3XL00-0AB0 HW Release: 6
6ES7 417-4XL00-0AB0 HW Release: 5
6ES7 417-4HL01-0AB0 HW Release: 1

 (The HW release can be read via: STEP 7 / Target System / Module Status Tab: General)

CPUs manufactured in the time frame from June 02 to September 02 are affected, which can be identified by the yellow test sticker on the back of the CPU.
The following identifiers correspond to the above time frame: VPP6, VPP7, VPP8, VPP9  

2. Corrected CPUs

Corrected CPUs (except CPU41x-4H) can be identified by their newer HW release:
6ES7 412-1XF03-0AB0 HW Release: 7
6ES7 412-2XG00-0AB0 HW Release: 7
6ES7 414-2XG03-0AB0 HW Release: 7
6ES7 414-3XJ00-0AB0 HW Release: 7
6ES7 414-4HJ00-0AB0 HW Release: 1 (*)
6ES7 416-2XK02-0AB0 HW Release: 7
6ES7 416-3XL00-0AB0 HW Release: 7
6ES7 417-4XL00-0AB0 HW Release: 6
6ES7 417-4HL01-0AB0 HW Release: 1 (*)

(*) HW release not be incremented after error correction

3. Performing the Error Correction
The error correction is performed similarly to an operating system update. At first, a memory card containing the error correction is created by means of STEP 7. The contents of this memory card is then transferred to the CPU.
In H systems as well, this error correction can only be carried out with the CPU switched off, and should therefore be performed in the context of the operating system update.

Prerequisites for the Creation of a Memory Card for the Error Correction:

  • S7 memory card of the type: Flash with at least 2 MB (also with CPU41x-4H)
  • STEP 7 V3.2 or higher
  • PG or PC with external prommer for programming the memory card   

Creating a Memory Card for the Error Correction:

  1. Download the file: Update_V145.EXE
  2. Unpack the file by double-clicking on the file name 
  3. In the SIMATIC Manager, erase the memory card by means of "File / S7 Memory Card / Delete"
  4. Program the memory card by selecting "Target System / Update Operating System" in the SIMATIC Manager and selecting the target folder; start the programming process by opening the file "CPU_HD.UPD".
  5. The memory card has been programmed once the default mouse pointer reappears. With newer STEP 7 versions, a corresponding message will appear.

Transfer to the CPU: 

Important: The loading process must not be interrupted (e.g., by a power off/on).
The loading process cannot be repeated after an interruption. In such a case, the CPU must be returned to the factory for repair.

  1. Power off the power supply (PS) of the rack in which the CPU is inserted 
  2. Insert the prepared memory card into the CPU 
  3. Permanently hold the key switch of the CPU in the position MRES
  4. Power ON the power supply (PS) of the rack in which the CPU is inserted; after approx. 10 s, the LEDs INTF / FRCE / RUN / STOP will start flashing  
  5. Briefly release the key switch (< 3 s), briefly return to MRES and then release again
  6. The loading process will start:
    LED INTF: Continuously lit - rapid flashing - continuously lit again 
  7. The loading process has been successfully completed once the LED EXTF remains continuously lit (after approx. 15 s) 
    If an error occurred during the loading process, it can be identified as follows:
    - LED FRCE continuously lit => the CPU is not affected by this error 
       (or the error correction has already been performed)
    - Rapid flashing of the LEDs INTF and EXTF => internal error; the module has to be returned for repairs 
    - Slow flashing of the LED INTF => the memory card is not functional
  8. Afterward, perform the operating system update.

 

 

 

Update V3.1.1 (6ES7 414-4HJ00-0AB0)
Update V3.1.1 (6ES7 417-4HL01-0AB0)
 

The following error has been corrected with Operating System V3.1.1:

In stand-alone mode of a H-CPU and also when using simplex I/Os in a H system, the following behavior could occur:
In the case of frequent, in particular cyclic calls of the SFC 51 to read the SZL W#16#4C91 (module status information of a module at an external DP master interface module), it could happen that although the addressed module functions error-free, the error code W#16#8087 is permanently output on the SFC in the RET_VAL parameter. This condition could only be eliminated by an overall reset of the CPU.

Product information A5E00073168-09:
 A5E73168_09.pdf ( 76 KB )

 

 

 

 

Update V3.1.3 (6ES7 414-4HJ00-0AB0)
Update V3.1.3 (6ES7 417-4HL01-0AB0)
 

The following errors have been corrected in V3.1.3:

  • When operating the diagnostics repeater with SFC103, the defect 4550 / B71D could occur.
  • If the communication load is high and several cyclic control & monitoring tasks have to be executed at the same time, a loss of synchronization could occur in very rare cases.

  Product information A5E00073168-10:
 A5E73168_10.pdf ( 80 KB )

 

 

Update V2.1.5 (6ES7 417-4HL00-0AB0)
 

The following errors have been corrected in V2.1.5:

  • Under certain circumstances, a defect could occur in the CPU, whereby the diagnostics buffer would not contain a corresponding (defect) entry after a power off/on cycle.
  • When switching off the supply voltage to the last PROFIBUS DP station of a line (with bus terminating resistor), a loss of synchronization with the event ID 43DA could occur.
  • After repeated power off/on cycles, a PROFIBUS DP slave (according to EN 50170) would no longer be correctly accepted.
  • In an H system coupled with an APPLICOM PCI Ethernet module, the following defect could occur: 4550 / b003 / 8752 / 01ae
  • If the communication load is high and several cyclic HMI tasks have to be executed at the same time, a loss of synchronization could occur in very rare cases.

  Product information A5E000130864_03:
 A5E1130864_03.pdf ( 72 KB )

 

 

 

Update V3.1.4 (6ES7 414-4HJ00-0AB0)
Update V3.1.4 (6ES7 417-4HL01-0AB0)
 

Corrections with Firmware V3.1.4:

  • The display of messages has been improved in the case of a cold restart of WinCC as well as in the case of application program changes.
  • If a large number of DP/DP couplers (IM157) was used in the H system, a synchronization error could occur in the case of a slave failure. This has been corrected.
  • Error correction in the H system for the case of a high communication load when using AG_SEND / AG_RECV
     

  Product Information A5E00073168-11:
 A5E00073168_11.pdf ( 73 KB )

 

 

Update V4.0.4 (6ES7 414-4HJ04-0AB0),
Update V4.0.4 (6ES7 417-4HL04-0AB0)
 

Corrections with Firmware V4.0.4:

1.     A defect with the identifier 4520/819D/xxxx/4576 could occur in the redundant mode, if the following conditions are present:

  • Operation of modules with a consistency over the entire area of more than 32 bytes at an external DP master (e.g., CP443-5 Ext)
  • Allocation of this module to a sub-process image that is also allocated to an OB  

2.     In the case of external DP masters (CP443-5 Ext) and a low PROFIBUS load, an internal system error could occur during startup when connecting/updating.

3.     A defect could occur in the case of a high communication load via AG_SEND / AG_RCV

 

Product Information A5E00299673-03:
 A5E00299673_03.pdf ( 46 KB )

 

 

Update V4.0.5 (6ES7 414-4HJ04-0AB0),
Update V4.0.5 (6ES7 417-4HL04-0AB0)
 

Corrections with Firmware V4.0.5:

  • When using switched I/Os, the switched I/Os might no longer be included as member of PROFIBUS DP after a power off/on at the station.
  • Defect 4535 0040 0000 0000 could sporadically occur.
  • Defect 4550 9240 0000 0001 could occur.
  • Defect 4535 1224 0000 0000 occurred when the block SFC17 "ALARM_SQ", SFC18 "ALARM_S", SFC107 "ALARM_DQ" or SFC108 "ALARM_D" was used and an associated value (parameter SD) with BOOL or an odd number of BYTE or CHAR had been added.
  • Defect 4533 0001 could occur when blocks were reloaded repeatedly.
  • When the standby CPU was in stand-alone mode and transitioned into the redundant mode after service data (not the diagnostics buffer) had been read, defect 4535 0040 0000 0000 could occur.
  • Defect 4520 819D 001D 4567 could occur when a minimum cycle time was set in the CPU parameters and the synchronization link was interrupted.
  • A loss of synchronization 43DA 0000 0000 0000 could occur when an HMI system - such as WinCC - caused a high communication load.
  • Starting with firmware V4.0.5, a topology determination can be triggered via the CP 443-5 Extended DX04 (from V6.1) with an SFC 103 "DP_TOPOL".

   

Product Information A5E00299673-04:
 A5E00299673_04.pdf ( 24 KB )

 

 

Update V4.0.6 (6ES7 414-4HJ04-0AB0),
Update V4.0.6 (6ES7 417-4HL04-0AB0)
 

Correction with Firmware V4.0.6:

When overloading blocks, a redundancy loss with the diagnostics buffer entry 7344 F0A5 0CAF 9724 could occur, if a connection was established at the same time. This is the case, for example, if the CPU attempts to establish configured connections to missing partners.
 

   

Product Information A5E00299673-05:
 A5E00299673_05.pdf ( 53 KB )

 

 

   

Update V4.0.7 (6ES7 414-4HJ04-0AB0),
Update V4.0.7 (6ES7 417-4HL04-0AB0)
 

Corrections with Firmware V4.0.7:

  • If a system data block had a length of exactly 10,000 bytes, problems could occur during loading; e.g., modules were not parameterized afterward.  
  • A large number of operator control & monitoring tasks could lead to a sporadic loss of redundancy.   
  • If the system function SFC 21 "FILL" had a parameter source length of 256 bytes or a multiple of it (e.g., 256 bytes, 128 Word, 256 DWord), the function was not executed.

   

Product Information A5E00299673-06:
 A5E00299673_06.pdf ( 37 KB )

 

 

 

Update V4.0.8 (6ES7 414-4HJ04-0AB0),
Update V4.0.8 (6ES7 417-4HL04-0AB0)
 

Corrections with Firmware V4.0.8:

  • When overloading blocks for S7 communication or block-related messages followed by compressing, the compressing procedure was sometimes blocked when calling these blocks with double-assigned R_ID or EV_ID. In this situation, certain PG functions such as loading blocks, monitoring blocks led to an abort of the PG function with an error message such as (D240) "The Coordination Rules have been violated" or to a corresponding diagnostics buffer entry.
    In fault tolerant systems this prevented the link-up procedure of the reserve CPU.
  • If a nonexistent block was being monitored in the SCL editor in debug mode, the defect 4550 B5A0 0201 D2D9 could occur. 
  • If an SFC without parameter supply was called in the SCL editor, the defect 4520 817A 40XX 00B8 could occur.
  • If an instance data block contains more than 254 structure elements (e.g., an array [1..255] of BOOL) followed by an instance for a block for the S7 communication or block-related messages (e.g., of the type SFB 35), this instance was not recognized by the CPU and STATUS 12 was output when calling the block.
  • A high communication load could cause synchronization losses with the event ID 0x7343.
  • When loading instances for blocks for the S7 communication or block-related messages, a synchronization loss with the event ID 0x7301 could occur in rare cases.
  • If a communication job <Write Tag> was called with several tag addresses (e.g., SFB 15 PUT, write tag with HMI device, SIMATIC Net software SAPI-S7) and a tag address points to a nonexistent data block, incorrect values were written to the subsequent tags of this job.
  • When operating single-sided DP slaves, which are assigned to a sub-process image, different TPA numbers in the OB85 start information could be displayed in the case of I/O access errors. This could lead to a RAM comparison error.

 

Product Information A5E00299673-07:
 A5E00299673_07.pdf ( 43 KB )

 

 

 

Update V4.0.9 (6ES7 414-4HJ04-0AB0),
Update V4.0.9 (6ES7 417-4HL04-0AB0)
 

Correction with Firmware V4.0.9:

Power on/off of both subsystems of the H system with simultaneously activated process control messages could cause the standby CPU to no longer connect.

   

Product Information A5E00299673:
 A5E00299673_08.pdf ( 43 KB )

 

 

 

Update V4.0.10 (6ES7 414-4HJ04-0AB0),
Update V4.0.10 (6ES7 417-4HL04-0AB0)
 

Corrections with FirmwareV4.0.10:

  • When accessing (via SFC 14 / SFC15 or process image) a PROFIBUS DP slave with consistency over the entire range and data length > 32 bytes, a synchronization error in the operating system with the event ID 16# 7344, (Z2): 40ea , (Z3): 06da could occur, if the slave failed due to incorrect data. 
  • When updating the sub-process image via the SFC26, it was possible to complete the function without RET_VAL error message despite a slave failure.

 

Product Information A5E00299673:
 A5E00299673_09.pdf ( 43 KB )

 

 

 

V4.5.0 (6ES7 412-3HJ14-0AB0),
V4.5.0 (6ES7 414-4HM14-0AB0)
V4.5.0 (6ES7 414-4HR14-0AB0)
V4.5.0 (6ES7 417-4HT14-0AB0)
 

Delivery Start of the new S7-400-H CPUs

For further Information, see entry ID 25912888

   

Product Information A5E01368340:
 A5E01368340_01.pdf ( 45 KB )

 

 

V4.5.1 (6ES7 412-3HJ14-0AB0),
V4.5.1 (6ES7 414-4HM14-0AB0)
V4.5.1 (6ES7 414-4HR14-0AB0)
V4.5.1 (6ES7 417-4HT14-0AB0)
 

Corrections with Firmware V4.5.1:

  • During forcing, the defect with the event ID #4550 8F37 sometimes occurred. See also 28662081
     
  • If the failsafe application operates with the last 32 data blocks from the CPU-type-specific number range, the connecting/updating sequence was aborted.
     
  • When switching off a switched slave with more than 32 bytes of consistent user data, which is connected via the CP443-5 , the relevant input values were not always deleted in the process image.

Updating the Firmware in RUN Mode:
The firmware can be updated in RUN mode if your application only uses data blocks in the following number ranges: 

CPU412-3H: 1 - 4063
CPU414-4H: 1 - 4063
CPU417-4H: 1- 8159
CPU414-4H PG: 1- 8159

Otherwise, perform the firmware update in STOP mode. 

Important Information concerning the STEP 7 Version employed:

  • From STEP 7 V5.4 SP3: (PCS7 V7.0 SP1) In HW-Config, perform "Target System -> Update Firmware".
     
  • From STEP 7 V5.3 SP2 up to and including STEP 7 V5.4 SP2 (PCS7 V6.1 SP1+SP2 and V7.0): Before updating the firmware, set the desired CPU to STOP with the SIMATIC Manager "Target System -> Operating Mode". Afterward, the firmware can be updated in HW-Config.  
    Warning:
    With these STEP 7 versions, if you first start with HW-Config "Target System -> Update Firmware", both CPUs will enter into the STOP mode.  

   

Product Information A5E01368340:
 A5E01368340_02.pdf ( 48 KB )

 

Product Information A5E01407763:
 A5E01407763_02.pdf ( 43 KB )

 

 

 

Update V4.0.11 (6ES7 414-4HJ04-0AB0),
Update V4.0.11 (6ES7 417-4HL04-0AB0)
 

Corrections with FirmwareV4.0.11:

  • If the failsafe application operates with the last 32 data blocks from the CPU-type-specific number range, the connecting/updating sequence was aborted.
     
  • When using register-indirect addressing with AR1 or AR2 address registers on data areas (DB) or instance data areas (DI), the H system failed with the event ID 16# 4520 811d 8xxx or 16# 4520 811d cxxx or 16# 4520 811d exxx, if:
    • the data block DB or DI was not present or no data block was open, and
    • the sum of the address of "Pointer Value in the Address Register + Pointer P#" exceeded 2097151.0
       
  • In rare cases, a termination of S7 connections or fault-tolerant S7 connections due to a protocol error caused the H system to fail with the event ID 16#4550 AD03 9A04 0210.

 

Product Information A5E00299673:
 A5E00299673_10.pdf ( 43 KB )

 

 

V4.5.2 (6ES7 412-3HJ14-0AB0),
V4.5.2 (6ES7 414-4HM14-0AB0)
V4.5.2 (6ES7 414-4HR14-0AB0)
V4.5.2 (6ES7 417-4HT14-0AB0)
 

V4.5.2 contains the following corrections:

  • Monitoring tags with the H CPUs V4.5 sometimes led to a H system failure. See also 32619422
     
  • The pulling of the AO HART module (332-8TF01) in redundant mode was not recognized correctly.
     
  • Inserting a module into a switched DP station, which is only accessible single-sided, was not recognized correctly.
     
  • In rare cases, a termination of S7 connections or fault-tolerant S7 connections due to a protocol error caused the H system to fail with the event ID 16#4550 AD03 9A04 0210. 
     

Updating the firmware in RUN mode:

The firmware V4.5.1 can be updated to V4.5.2 in RUN mode.

Caution!

After a firmware update in RUN mode from V4.5.1 to V4.5.2 and a subsequent loading of communication instances (data blocks for the communication and messaging functions) with PCS7 delta-loading, a single-sided CPU defect with the identifier 4535:1242 can sporadically occur.

Recommendation for affected users

The behavior can be avoided as follows:

  • After updating the firmware in RUN mode to V4.5.2, immediately continue to update to V4.5.3. On the basis of V4.5.2, do not perform a delta-loading/reloading of blocks. 
  • Do not use the firmware update in RUN mode to update to V4.5.2.
  • If the firmware still has to be undated in RUN mode to V4.5.2:
    First completely perform the "Firmware Update in RUN Mode" without any interruption; both CPUs will be in the redundant operating mode with firmware V4.5.2.
    Afterward:
    1. Place the master CPU in STOP mode (the master CPU can be identified by the lit LED MSTR)
    2. Perform an overall reset on this CPU
    3. Place this CPU in RUN mode; it will be connected and updated
    4. Both CPUs are now in the redundant operating mode
     
  • If the firmware has already been updated in RUN mode to V4.5.2:
    1. Place one of the CPUs in STOP mode
    2. Perform an overall reset on this CPU
    3. Place this CPU in RUN mode; it will be connected and updated
    4. Both CPUs are now in the redundant operating mode
    5. Perform steps 1 to 3 for the other CPU
    6. Both CPUs are now in the redundant operating mode 
     

Affected CPUs:
CPU 412-3H: 6ES7 412-3HJ14-0AB0
CPU 414-4H: 6ES7 414-4HM14-0AB0
CPU 414-4H: 6ES7 414-4HR14-0AB0
CPU 417-4H: 6ES7 417-4HT14-0AB0

  Product Information A5E01368340:
 A5E01368340_03.pdf ( 45 KB )

 

Product Information A5E01407763:
 A5E01407763_03.pdf ( 36 KB )

 

 

 
Update V3.1.5 (6ES7 414-4HJ00-0AB0)
Update V3.1.5 (6ES7 417-4HL01-0AB0)
 

Corrections with Firmware V3.1.5:

  • If a subsystem is powered off while in the redundant operating mode and a memory compression is active at the same time, the remaining subsystem might become inoperable in rare cases. 
  • With this version, it is possible to force bit memory addresses in ranges greater than 8191. 

 

Product Information A5E00073168-12:
 A5E00073168_12.pdf ( 72 KB )

 

 

 
V4.5.3 (6ES7 412-3HJ14-0AB0),
V4.5.3 (6ES7 414-4HM14-0AB0)
V4.5.3 (6ES7 414-4HR14-0AB0)
V4.5.3 (6ES7 417-4HT14-0AB0)
 

V4.5.3 contains the following corrections:

  • After a firmware update in RUN mode from V4.5.1 to V4.5.2 and a subsequent loading of communication instances (data blocks for the communication and messaging functions) with PCS7 delta-loading, a single-sided CPU defect with the identifier 4535:1242 can sporadically occur.
    See also: 40240573
    (internal ref. AP00905594)
     
  • When using the same event ID for the archive function SFB37 "Send Archive Data" and a messaging block, e.g., ALARM8P, an updating of the messages by an OS could lead to a defect with the event ID 16# 4535 1224.
    (internal ref. AP00902830)
     
  • After a parameter change to a DO module via "System Change during Operation", which is:
    - located in a distributed, switched configuration and
    - connected to the integrated DP interface of the CPU,
    the outputs were no longer activated.
    (internal ref. AP00898006)
  • When monitoring I/O direct access commands (e.g., L PIB), the H system would fail in rare cases with the event ID 16# 4520 F89D C450 811D.
    (internal ref. AP00832024)
  • If the diagnostics buffer of a single-sidedly configured slave was opened from HW-Config, this would cause a synchronization error.
    (internal ref. AP00788952)
  • In the case of a status or controlling of a DB with a number larger than the permitted value range of the CPU, a defect or failure of the H system could occur.
    (internal ref. AP00868740)
  • If the supply voltage is turned on at one side of a switched off Y-link, a synchronization error could occur in rare cases.
    (internal ref. AP00874701)

Product Information A5E01368340-05 

A5E01368340-05.pdf ( 61 KB )

 

Product Information A5E01407763-05

A5E01407763-05.pdf ( 51 KB )

 
Information on updating the firmware in RUN mode:

The firmware V4.5.2 can be updated to V4.5.3 in RUN mode. 

Affected CPUs:
CPU 412-3H:         6ES7 412-3HJ14-0AB0
CPU 414-4H:         6ES7 414-4HM14-0AB0
CPU 414-4H PG:   6ES7 414-4HR14-0AB0
CPU 417-4H:         6ES7 417-4HT14-0AB0

 

 

 

 
V4.0.12 (6ES7 414-4HJ04-0AB0)
V4.0.12 (6ES7 417-4HL04-0AB0)
 

V4.0.12 contains the following corrections:

  • When using the same event ID for the archive function SFB37 "Send Archive Data" and a messaging block, e.g., ALARM8P, an updating of the messages by an OS could lead to a defect with the event ID 16# 4535 1224.
    (internal ref. AP00929781)
     
  • After a parameter change to a DO module via "System Change during Operation", which is:
    - located in a distributed, switched configuration and
    - connected to the integrated DP interface of the CPU,
    the outputs were no longer activated.
    (internal ref. AP00929913)
     
  • In the case of a status or controlling of a DB with a number larger than the permitted value range of the CPU, a defect or failure of the H system could occur.
    (internal ref. AP00929791) 
     
  • If the supply voltage is turned on at one side of a switched off Y-link, a synchronization error could occur in rare cases.
    (internal ref. AP00929919)
     
  • Improved self-diagnostics in the case of memory errors.
    (internal ref. AP00945862)
     
  • If the OB84 was called in rapid succession with the event 16#3583 "Accumulation of detected and corrected Memory Errors", the H system could fail.
    (internal ref. AP00924992)

 

Product Information A5E00299673_11.pdf

A5E00299673_11.pdf ( 53 KB )

 

 

 

 
V4.5.4 (6ES7 412-3HJ14-0AB0),
V4.5.4 (6ES7 414-4HM14-0AB0)
V4.5.4 (6ES7 414-4HR14-0AB0)
V4.5.4 (6ES7 417-4HT14-0AB0)
 

V4.5.4 contains the following corrections:

  • After opening the hardware configuration and transitioning into the online view, a synchronization error could occur, if a one-sided PROFIBUS DP master operating a one-sided line was inserted in a slot gap between two external PROFIBUS DP masters (e.g., CP443-5), which operate switched PROFIBUS DP lines.
    (internal ref. AP00964902)
      
  • If a slave with modules with an odd number of bytes was configured at the integrated DP interface, the H system might not enter into the redundant operating mode after a power off/on cycle of the H system.
    (internal ref. AP00993094)
      
  • Modification of certain slaves (e.g., CP 341) by modifying the system while in operation via CiR was not possible.
    (internal ref. AP00789692)
     
  • For a DPV1 slave with the parameter DPV1_Enable=0 set in the GSD file, a DPV1_Request was erroneously sent.
    (internal ref. AP00972147)
     
  • Contact problems at the memory module could not clearly be assigned to the correct CPU, which caused the H system to fail with the event ID 16#4521 F8BF.
    (internal ref. AP00793186) 
     
  • The output Q of the SFB 5 "TOF" went to zero while the timer was running and being started at the start input IN with a new time period PT.
    (internal ref. AP00979279)
     
  • Sporadic differences within the contents of certain memory areas - that previously led to a failure of the CPU with the event ID 16# 4550 8f37 or to a RAM/PAA comparison error with the event ID 16# 7322 - are now detected, eliminated and reported as CPU hardware fault via OB 84 (OB84_EV_CLASS B#16#35, OB84_FLT_ID B#16#83, "Accumulation of detected and corrected Memory Errors").
    (internal ref. AP01098300) 

 

 

Product Information A5E01368340-07

A5E01368340-07.pdf ( 93 KB )

 

Product Information A5E01407763-06

A5E01407763-06.pdf ( 91 KB )

 
Information on updating the firmware in RUN mode:

The firmware V4.5.3 can be updated to V4.5.4 in RUN mode.

 

 

 
V4.5.5 (6ES7 412-3HJ14-0AB0),
V4.5.5 (6ES7 414-4HM14-0AB0)
V4.5.5 (6ES7 414-4HR14-0AB0)
V4.5.5 (6ES7 417-4HT14-0AB0)
 

V4.5.5 contains the following correction:

  • In rare cases, inconsistencies within the internal data structures could occur resulting in a CPU defect with the following event ID: 4550:AD90:1A02 or 4550:AA02:0B02 or 4550:AE90:0A01 or 4535:2824:0407. 
    (internal ref. AP01177664)

 

Product Information A5E01368340-08

A5E01368340-08.pdf ( 101 KB )

 

Product Information A5E01407763-07

A5E01407763-07.pdf ( 98 KB )

 
Updating the firmware in RUN mode:

The firmware V4.5.4 can be updated to V4.5.5 in RUN mode

During the FW update in RUN mode:

  • the outputs will not be updated for approx. 1.5 seconds.
  • there will be a pause in the data transmission of approx. 1.5 seconds in the case of one-sided communication via CP443-1 and UDP protocol.

 

 

 
V4.5.6 (6ES7 412-3HJ14-0AB0),
V4.5.6 (6ES7 414-4HM14-0AB0)
V4.5.6 (6ES7 414-4HR14-0AB0)
V4.5.6 (6ES7 417-4HT14-0AB0)
 

V4.5.6 contains the following corrections:

  • Following a switchover with a changed configuration (H-CiR), a data block created with the aid of the SFC 22 (CREAT_DB) might in rare cases result in the creation of faulty data, if a switchover with changed operating system (operating system update in RUN mode) was performed previously.     
    (internal ref. AP01348864)
     
  • The defect with the event ID 16#4550 A804 was corrected. 
    (internal ref. AP01338820)
     
  • The simultaneous use of AR_SEND and SFBs for the message creation (SFB 131-136) could result in no messages being sent to the OS. 
    (internal ref. AP01250633 )
     
  • As a result of the STOP of the master CPU with V4.5.4 and V4.5.5, the one-sided communication via the CP443-1 and the UDP protocol could experience a pause of approx. 1.5 seconds in the data transmission.
    (internal ref. AP01312555)
     
  • The system response to bit errors in the module memory (memory card) concerning the event IDs 16#4531 FxBF 0006 and 16#4521 FxBF was improved. In particular, affected CPUs operated as stand-alone now remain in the RUN mode.
    (internal ref. AP01281804)
     
  • After removing and inserting a synchronization module, the module status might be displayed incorrectly by the STEP 7 HW-Config online view and the SZL information function (SFC51 Index 0x591).  
    (internal ref. AP01298063) 

 

Product Information A5E01368340-09

A5E01368340-09.pdf ( 94 KB )

 

Product Information A5E01407763-08

A5E01407763-08.pdf ( 91 KB )

 
Updating the firmware in RUN mode:

The firmware V4.5.5 can be updated to V4.5.6 in RUN mode.

During the FW update in RUN mode:

  • the outputs will not be updated for approx. 1.5 seconds.
  • there will be a pause in the data transmission of approx. 1.5 seconds in the case of one-sided communication via CP443-1 and UDP protocol.

 

 

 
V6.0.1 (6ES7 412-5HK06-0AB0)
V6.0.1 (6ES7 414-5HM06-0AB0)
V6.0.1 (6ES7 416-5HS06-0AB0)
V6.0.1 (6ES7 417-5HT06-0AB0)
 

Delivery release of the new S7-400-H-CPUs

for more informationen please see entry ID 59903098

 

 

 

 
V6.0.2 (6ES7 412-5HK06-0AB0)
V6.0.2 (6ES7 414-5HM06-0AB0)
V6.0.2 (6ES7 416-5HS06-0AB0)
V6.0.2 (6ES7 417-5HT06-0AB0)
 

Version 6.0.2 contains the following correction:

Calling the SFC51 with SZL W#16#0D91 could lead to a synchronization error if distributed I/Os (PROFIBUS or PROFINET) are used; e.g. W#16#7344: Synchronization error in the operating system due to incorrect data.
(internal ref. AP01442227)

 

Product Information A5E03732039_02

A5E03732039_02.pdf ( 99 KB )

 

Product Information A5E03854325_01

A5E03854325_01.pdf ( 136 KB )

 
Updating the firmware in RUN mode:

When you update the firmware in run mode from V6.0.1 to V6.0.2 the indications and archives on the connected WinCC stations may possibly not be updated anymore.

For this reason please bear in mind that a FW update in run should only be executed if the connection between CPU and WinCC station has been separated beforehand. While the system is in redundant mode and before uploading the firmware stop the connected WinCC systems or the PCS 7 OSs (stop the runtime), or separate the corresponding communication connection.

You can restore the connections immediately after the restart of the CPU with firmware V6.0.2.

If you are uncertain about the procedure please contact our Customer Support, or carry out the FW update in stop mode of the CPU.

 

 

 

 
V6.0.3 (6ES7 412-5HK06-0AB0)
V6.0.3 (6ES7 414-5HM06-0AB0)
V6.0.3 (6ES7 416-5HS06-0AB0)
V6.0.3 (6ES7 417-5HT06-0AB0)
 

Version 6.0.3 contains the following corrections:

  • The performance of the ISOonTCP connections via the integrated interface has been enhanced (internal ref 570000)
  • Additional memory repair mechanisms have been implemented to avoid the Defects with identifier 16# 4535 4C45 or 16# 4535 0545 (internal ref 548108)
  • In rare cases the Defect with identifier 16# 4535 24FF 041F could occur when loading via CFC (internal ref 570358)
  • In conjunction with T-communication and connection abortion a two-sided Defect 16# 4550 130e a105 000d could occur in rare cases. (internal ref 570240)
  • After blocking and releasing of messages in combination with acknowledgement (Alarm8/Alarm8P) the CPU could possible cease to dispatch messages. (internal ref 570182)

 

Product Information A5E03732039_03

A5E03732039_03.pdf ( 37 KB )

 

Product Information A5E03854325_01

A5E03854325_01.pdf ( 136 KB )

 
Updating the firmware in RUN mode:

When you update the firmware in run mode from V6.0.2 to V6.0.3 please be sure to observe the following:

A FW update in run should only be executed if the connection between CPU and WinCC station has been separated beforehand. While the system is in redundant mode and before uploading the firmware stop the connected WinCC systems or the PCS 7 OSs (stop the runtime), or separate the corresponding communication connection. You can restore the connections immediately after the restart of the CPU with firmware V6.0.3. If you are uncertain about the procedure please contact our Customer Support, or carry out the FW update in stop mode of the CPU.

 

 

 

 

 Entry ID:6741018   Date:2013-12-18 
I regard this article....as helpfulas not helpful                                 
mySupport
My Documentation Manager 
Newsletter 
CAx-Download-Manager 
Support Request
To this entry
Print
Create PDF 
Send to a friend
QuickLinks
Compatibility tool 
Help
Online Help
Guided Tour