S7-400H CPU Firmware Update Guide
S7-400H CPU Firmware Update Guide
com)
Industry Online Support
Product Support
Updating firmware in RUN is possible as of this firmware version. An update is only possible from one version to the next, for example, from V6.0.0 to V6.0.1
For information, refer to the respective update description and the Fault-tolerant systems S7-400H system manual under Section 6.4 "Updating the firmware without a memory card" and Section 6.5 "Firmware update in RUN mode".
Difference of the operating system update compared to the remaining S7-400 CPUs
After the actual firmware update, the self-test is started on the fault-tolerant system; this may take several minutes. This time depends on the configuration of the load memory (size of the inserted memory card) and the configuration of the work memory.
Both CPUs must have the same firmware version in an S7-400H. If one CPU of your S7-400H fails, order a new CPU with the same order number. It will be delivered with the latest firmware version. This firmware version may be higher than the firmware version of the CPU being replaced.
In this case, you must downgrade the new CPU to the older firmware version.
S7 memory card
Flash 8 MB (order number 6ES7 952-1KP00-0AA0) or larger
STEP 7 with product version V3.1 or higher
Programming device or PC with external prommer for programming the memory card
Power OFF at the power supply (PS) of the rack in which the CPU is installed.
Insert the prepared operating system update card into the CPU.
Power ON at the power supply of the rack in which the CPU is installed.
The operating system is transferred from the memory card to the internal FLASH EPROM.
During this transfer, all the LEDs on the CPU are lit (INTF, EXTF, FRCE, CRST, RUN, STOP). The operating system update takes about 2 minutes and is completed when the STOP LED on the CPU flashes slowly => memory reset request from the system.
NOTICE:
The self-test is started immediately after the update and can take several minutes, depending on the memory configuration.
Power OFF at the power supply and possible insertion of the memory card intended for the operation.
Power ON at the power supply.
The CPU automatically performs a memory reset and is immediately ready for operation.
Set the time when the operating system update has been successfully completed.
Description of the operating system update in RUN with V6.0
As a general rule, a firmware update in RUN can only be from one firmware version to the next higher firmware version and within fault-tolerant systetms. A downgrade is not possible in RUN. See also the notes in the respective version-specific description.
1. For CPU access protection with password: Select a CPU of the fault-tolerant system in SIMATIC Manager and select the menu command PLC > Access authorization > Setup. Enter the CPU access password.
2. Select one of the two CPUs either via SIMATIC Manager -> Project or HW Config. Do not use the menu command "Accessible nodes" in Simatic Manager.
3. Select the menu command "PLC > Update firmware"
A wizard starts that can automatically update the firmware on both CPUs.
The complete update description and alternative solutions are described in the Fault-tolerant S7-400 H Systems system manual under Section 6.5 "Firmware update in RUN mode".
Downloads
© Siemens AG 2009-2023 - Imprint (https://www.siemens.com/corporate-information) Privacy policy (https://www.siemens.com/privacy-notice) Cookie policy (https://www.siemens.com/cookie-notice) Terms of use (https://www.siemens.com/terms-of-use)
Download V6.0.1 (backup only:)Digital ID (https://www.siemens.com/digital-id) 0.0.0.0
MLFB V6.0.1
CPU 412-5H PN/DP 6ES7 412-5HK06-0AB0 4125hk06_v601.exe (5.2 MB) (/cs/attachments/109474550/4125hk06_v601.exe)
CPU 414-5H PN/DP 6ES7 414-5HM06-0AB0 4145hm06_v601.exe (5.2 MB) (/cs/attachments/109474550/4145hm06_v601.exe)
CPU 416-5H PN/DP 6ES7 416-5HS06-0AB0 4165hs06_v601.exe (5.2 MB) (/cs/attachments/109474550/4165hs06_v601.exe)
CPU 417-5H PN/DP 6ES7 417-5HT06-0AB0 4175ht06_v601.exe (5.2 MB) (/cs/attachments/109474550/4175ht06_v601.exe)
V6.0.2
When the SFC51 was called with SSL W#16#0D91, a synchronization error sometimes occurred if distributed I/O (PROFIBUS or PROFINET) was used; for example W#16#7344: Synchronization error in operating system due to incorrect data.
(Internal ref. AP01442227)
MLFB V6.0.2
CPU 412-5H PN/DP 6ES7 412-5HK06-0AB0 4125hk06_v602.exe (5.2 MB) (/cs/attachments/109474550/4125hk06_v602.exe)
CPU 414-5H PN/DP 6ES7 414-5HM06-0AB0 4145hm06_v602.exe (5.2 MB) (/cs/attachments/109474550/4145hm06_v602.exe)
CPU 416-5H PN/DP 6ES7 416-5HS06-0AB0 4165hs06_v602.exe (5.2 MB) (/cs/attachments/109474550/4165hs06_v602.exe)
CPU 417-5H PN/DP 6ES7 417-5HT06-0AB0 4175ht06_v602.exe (5.2 MB) (/cs/attachments/109474550/4175ht06_v602.exe)
V6.0.3
A performance improvement has been achieved with ISOonTCP connections via the integrated interface
(internal ref. no. 570000)
Additional memory repair mechanisms have been implemented to avoid defects with the identifier 16# 4535 4C45 or 16# 4535 0545.
(internal ref. no. 548108)
The defect with the identifier 16# 4535 24FF 041F occurred in rare cases while loading via CFC
(internal ref. no. 570358)
In the context of T-communication and an aborted connection, the double-sided defect 16# 4550 130e a105 000d occurred in rare cases.
(internal ref. no. 570240)
After disabling and enabling messages in combination with acknowledgment (Alarm8/Alarm8P), it sometimes occurred that the CPU no longer sent messages.
(internal ref. no. 570182)
© Siemens AG 2009-2023 - Imprint (https://www.siemens.com/corporate-information) Privacy policy (https://www.siemens.com/privacy-notice) Cookie policy (https://www.siemens.com/cookie-notice) Terms of use (https://www.siemens.com/terms-of-use)
Note on updating firmware in RUN: Digital ID (https://www.siemens.com/digital-id) 0.0.0.0
The following must be observed when upgrading the firmware from Version V6.0.2 to V6.0.3 in RUN mode. A firmware update in RUN mode may only be carried out if CPU-WinCC station connections have been terminated beforehand. Therefore, before the firmware is installed, stop the
connected WinCC systems or PCS 7 OSs while still in redundant operation (stop Runtime) or terminate the corresponding communication connections. You can re-establish the connection immediately after restart of the CPU with the firmware V6.0.3.If you are unsure of the procedure,
please contact our Customer Support or carry out the firmware update while the CPU is in stop mode.
MLFB V6.0.3
CPU 412-5H PN/DP 6ES7 412-5HK06-0AB0 4125hk06_v603.exe (4.9 MB) (/cs/attachments/109474550/4125hk06_v603.exe)
CPU 414-5H PN/DP 6ES7 414-5HM06-0AB0 4145hm06_v603.exe (4.9 MB) (/cs/attachments/109474550/4145hm06_v603.exe)
CPU 416-5H PN/DP 6ES7 416-5HS06-0AB0 4165hs06_v603.exe (4.9 MB) (/cs/attachments/109474550/4165hs06_v603.exe)
CPU 417-5H PN/DP 6ES7 417-5HT06-0AB0 4175ht06_v603.exe (4.9 MB) (/cs/attachments/109474550/4175ht06_v603.exe)
V6.0.4
After a temporary interruption of the lower sync cable, for example, due to pulling and plugging, sometimes the sync coupling could no longer be established on this cable and possibly the MAINT LED lit up.
(internal ref. no. 738786).
If a station or module was extended or deleted via configuration changes in runtime (CiR) and subsequently a power OFF/ON took place, the CPU was no longer started in RUN.
(internal ref. no. 741006)
The defect with the identifier W#16#4550/0C10 sometimes occurred if multiple field devices were accessed simultaneously with PDM.
(internal ref. no. 902730)
The defect with the identifier W#16#4520/8123 has been corrected, see current
90039870 (/cs/document/90039870/operation-of-switched-i-os-under-profinet?lc=en-ww)
A defect with the identifier W#16#4550/0C0B sometimes occurred when the monitoring time at H-communication connections was very high (> 510 seconds).
(internal ref. no. 972829)
Avoiding station failure in the case of failure of both synchronization lines within a short time under operation with FLASH memory cards.
(internal ref. no. 979442)
Improved performance when using the integrated PN interface for coupling WinCC.
(internal ref. no. 1074895)
MLFB V6.0.4
CPU 412-5H PN/DP 6ES7 412-5HK06-0AB0 4125hk06_v604.exe (5.3 MB) (/cs/attachments/109474550/4125hk06_v604.exe)
CPU 414-5H PN/DP 6ES7 414-5HM06-0AB0 4145hm06_v604.exe (5.3 MB) (/cs/attachments/109474550/4145hm06_v604.exe)
CPU 416-5H PN/DP 6ES7 416-5HS06-0AB0 4165hs06_v604.exe (5.3 MB) (/cs/attachments/109474550/4165hs06_v604.exe)
CPU 417-5H PN/DP 6ES7 417-5HT06-0AB0 4175ht06_v604.exe (5.3 MB) (/cs/attachments/109474550/4175ht06_v604.exe)
V6.0.5
Improvement of the behavior when the maximum number of communications partners are used at the MPI/DP interface in combination with the failure and return of all connections.
(ref. no. 1154731)
In redundant systems, the maximum bracket stack (7) is now consistently available.
(ref. no. 1096875)
System availability has been increased by expansion of the correction mechanisms in case of temporary internal inconsistencies. In redundant systems, an automatic resynchronization may thus be started in some rare cases.
(ref. no. 1194672)
© Siemens AG 2009-2023 - Imprint (https://www.siemens.com/corporate-information) Privacy policy (https://www.siemens.com/privacy-notice) Cookie policy (https://www.siemens.com/cookie-notice) Terms of use (https://www.siemens.com/terms-of-use)
Digital ID (https://www.siemens.com/digital-id)
Optimized handling of synchronization errors between the two CPUs of a0.0.0.0
redundant system also increases system availability.
(ref. no. 1194871)
By expanding the diagnostic functionality in connection with additional PROFIBUS CPs, the switchover time can be further reduced in some cases.
(ref. no. 937190)
Avoidance of a synchronization error in conjunction with calling TCON (FB65) and TDISCON (FB66) blocks in very rapid succession. The blocks are used to establish and terminate connections for open IE communication.
(ref. no. 1115055)
Recommendation: The update to this firmware version should be performed as soon as possible.
NOTE: When using the PROFINET interface in conjunction with time synchronization over this interface (slave to PNIO), the firmware update in RUN sometimes cannot be performed due to an incorrect configuration. In this case, correct the configuration or contact our Customer Support
for further assistance.
Recommendation: Begin the firmware update with the CPU in Rack 1.
MLFB V6.0.5
CPU 412-5H PN/DP 6ES7 412-5HK06-0AB0 4125HK06_V605.exe (5.3 MB) (/cs/attachments/109474550/4125HK06_V605.exe)
CPU 414-5H PN/DP 6ES7 414-5HM06-0AB0 4145HM06_V605.exe (5.3 MB) (/cs/attachments/109474550/4145HM06_V605.exe)
CPU 416-5H PN/DP 6ES7 416-5HS06-0AB0 4165HS06_V605.exe (5.3 MB) (/cs/attachments/109474550/4165HS06_V605.exe)
CPU 417-5H PN/DP 6ES7 417-5HT06-0AB0 4175HT06_V605.exe (5.3 MB) (/cs/attachments/109474550/4175HT06_V605.exe)
V6.0.6
The monitoring of a block simultaneously with an older and a more recent STEP 7 version (STEP 7 V5.x and older than V5) no longer results in a change into the Defective operating state.
(internal ref. no.: 1561762)
If the PROFINET IO diagnostic interrupts were activated at a CP443-1 or CP443-1 Advanced (the CPs can only be used for Ethernet communication with these CPUs) and the system function "RALRM" (SFB54) was called in the diagnostic interrupt (OB 82), the system sometimes
changed to the Defective operating state (with the identifier "Stop cannot be reached" 16#4520 811d 2922 029a).
(internal ref. no.: 1712231)
In rare cases it was possible that the CPU could change to the Defective operating state (with the identifier 16#4535 0544 0414 0000) when open communications blocks (FB 63 "TSEND", FB 64 "TRCV", FB 67 "TUSEND" or FB 68 "TURCV") were called nested with the parameter
RQ =0 and RQ =1
(internal ref.: 1588659)
In rare cases, the CPU changed to the Defective operating state or remained in Stop due to brief voltage drops (few ms).
(internal ref. no.: 1442406)
© Siemens AG 2009-2023 - Imprint (https://www.siemens.com/corporate-information) Privacy policy (https://www.siemens.com/privacy-notice) Cookie policy (https://www.siemens.com/cookie-notice) Terms of use (https://www.siemens.com/terms-of-use)
Digital
In an H-system with higher-level timeIDsynchronization,
(https://www.siemens.com/digital-id)
in very rare cases0.0.0.0
the time of the automation system was set incorrectly for one update cycle immediately after coupling and updating.
(internal ref. no.: 1497557)
Improved behavior of the H-system when calling the system state list for module state information (SSL 16#xC91) with the address 0xFFFF. The address specification is invalid here.
(internal ref. no.: 1625562)
In extremely rare cases, it was possible that the blocks in OB4x (hardware interrupt) and OB82 (diagnostic interrupt) were not processed at a changeover in the H-system.
(internal ref. no.: 1225832).
Improved behavior at redundancy switchovers of the H-system in the case of extremely rare internal defects.
(internal ref. no.: 1719235)
The SNMP data of the H-CPU V6 has been harmonized with the other SIMATIC CPUs. This changes the content of the SNMP variables "ifDescr", "sysDescr" and "sysLocation". These changes particularly improve the interaction with the SINEMA servers.
(internal ref. no.: 1307786, 1388120 and 1388177)
The undesired behavior at SFC49 "LGC_GADR" (Entry ID: 109736598 (/cs/document/109736598/s7-400-cpus-undesired-behavior-with-sfc49-lgc_gadr-?lc=en-ww) ) has been eliminated.
(internal ref. no.: 1641047)
When an output module was pulled in a PROFINET device, it was possible that an access error in the process image (outgoing) was incorrectly generated for this module address immediately after an access error in the process image (incoming).
(internal ref. no.: 1370747)
When reading the device status on a PROFINET subsystem (0x694 and 0x794 system status list) with SFC51 "RDSYSST", the device status sometimes was not displayed correctly if subslots without user data (e.g. a SCALANCE switch) were configured in the PROFINET device
(internal ref. no.: 1340377 and 1336667)
A synchronization error of the H-system in the context of the reading of the system state list (SSL) 16#x694 using the system function "RDSYSST" (SFC51) with the parameters RQ =0 and INDEX =100 has been eliminated.
(internal ref. no.: 1632189)
When reading the system state list (SSL) module state information at PROFINET IO and PROFIBUS DP (SSL-ID W#16#xy96) with the system function RDSYSST (SFC 51), a synchronization error sometimes occurred in the H-system when the function was called with the
parameter RQ =0 on non-redundant modules (one-sided IO devices).
(internal ref. no.: 1653377)
When reading the system state list (SSL) rack/station state information (SSL ID W#16#xy92) at the PROFINET IO and PROFIBUS DP with the system function RDSYSST (SFC 51), the system sometimes changed to the Defective operating state (with the identifier 16#4550 942b
0037 800d) if an invalid DP or master system ID was specified.
(internal ref. no.: 1707674)
MLFB V6.0.6
CPU 412-5H PN/DP 6ES7 412-5HK06-0AB0 4125HK06_V606.exe (5,3 MB) (/cs/attachments/109474550/4125HK06_V606.exe)
CPU 414-5H PN/DP 6ES7 414-5HM06-0AB0 4145HM06_V606.exe (5,3 MB) (/cs/attachments/109474550/4145HM06_V606.exe)
CPU 416-5H PN/DP 6ES7 416-5HS06-0AB0 4165HS06_V606.exe (5,3 MB) (/cs/attachments/109474550/4165HS06_V606.exe)
CPU 417-5H PN/DP 6ES7 417-5HT06-0AB0 4175HT06_V606.exe (5,3 MB) (/cs/attachments/109474550/4175HT06_V606.exe)
V6.0.7
The compatibility when using simulation modules for DP slaves was improved. (Internal ref. 1838617)
An optimization of the processing times when using consistent user data (KND) was introduced. The data from consistent user data is now available more quickly. (Internal ref. 1978874)
The behavior during monitoring of a block with multiple instances (multiple devices or multiple windows) has been improved. The automation system now no longer changes to the "Defect" operating state in very rare cases when exiting monitoring (Internal ref. 1920288)
By using the "Report system errors" function, in rare cases it was possible that correct values were not shown in the status display of the hardware configuration online view. The correct device status is now displayed for an activated system error. (Internal ref. 1780033)
In very rare cases, when the system status list 0x0C75 (status of a switched DP slave in the H system) was read per SFC51 "RDSYSST" and there was simultaneously a change of the redundant partner in "Stop" mode, the CPU switched to the "Defect" operating mode (ID:
4535/0e46/0401) (total failure of the H system). (Internal ref. 1806332)
When there is a bad parameter assignment of an area pointer, the system could switch to "Defect" operating mode (ID: 4535/0512/041f) during subsequent write access. (Internal ref. 2087322)
© Siemens AG 2009-2023 - Imprint (https://www.siemens.com/corporate-information) Privacy policy (https://www.siemens.com/privacy-notice) Cookie policy (https://www.siemens.com/cookie-notice) Terms of use (https://www.siemens.com/terms-of-use)
Digital
When using a fail-safe program ID (https://www.siemens.com/digital-id)
for more than 9 years (without switching0.0.0.0
off the power supply), the CPU could change to the "Defect" operating state. (ID: 4550/9240). (Internal ref. 2215757)
During monitoring of blocks with conditional jump instructions in the monitoring section, a fault could occur in the program execution with a specific command combination (Internal ref. 2109609)
Avoidance of time-of-day overflow in 2036 and 2038. (Internal ref. 2004400)
If a PROFINET network was configured to which no PN devices are connected, a switch to the active IO controller of this empty network in the H system could result in a transition of the CPU to the "Defect" operating state and thus in a failure of the entire H system (ID:
4550/2b0c/a415) (see Entry ID: 109745029 (/cs/ViewDocument.aspx?ArticleID=109745029) ). (Internal ref. 2232376)
After adding modules of a DP station using CiR, it was possible that no module diagnostics were displayed in the hardware configuration online view. (Internal ref. 2289005)
In cases of jump instructions the actual data are no longer displayed when monitoring blocks. Actual data are still displayed for all other types of commands.
The content of the SNMP variables "ifDescr" were adapted. (Internal ref. 2300138).
Note: When using a SIMATIC S7 Memory Card FLASH-EPROM (FEPROM) a CPU with firmware V6.0.7 might not startup in cases a factory reset was executed before or when using the CPU for the first time (“delivery status”).
This behavior can be avoided: Assign an IP address via ES/PG (“Edit Ethernet note”) before.
MLFB V6.0.7
CPU 412-5H PN/DP 6ES7 412-5HK06-0AB0 4125HK06_V607.exe (5,3 MB) (/cs/attachments/109474550/4125HK06_V607.exe)
CPU 414-5H PN/DP 6ES7 414-5HM06-0AB0 4145HM06_V607.exe (5,3 MB) (/cs/attachments/109474550/4145HM06_V607.exe)
CPU 416-5H PN/DP 6ES7 416-5HS06-0AB0 4165HS06_V607.exe (5,3 MB) (/cs/attachments/109474550/4165HS06_V607.exe)
CPU 417-5H PN/DP 6ES7 417-5HT06-0AB0 4175HT06_V607.exe (5,3 MB) (/cs/attachments/109474550/4175HT06_V607.exe)
V6.0.8
In extremely rare cases, a loss of synchronization was possible for T connections that had, in principle, been set up but not established and which are, however, actively terminated, in conjunction with time synchronization in SIMATIC mode.
(Internal ref.: 2369635)
In very rare cases, the CPU no longer started up following a factory reset while using FLASH memory cards.
(Internal ref.: 2519679)
The behavior when monitoring blocks has been improved. A change into Defect operating state with identifier 4550 8F01 no longer occurs.
(Internal ref.: 2560326)
In extremely rare cases, the CPU switched to Defect operating state with identifier 4550/8128 when using consistent user data (KND) > 32 bytes as well as switched I/O, with simultaneous loss of synchronization.
(Internal ref.: 2572334)
The startup behavior with FLASH memory cards has been improved.
(Internal ref.: 2587393)
V6.0.9
Increased robustness for non-standard-compliant messages / message sequences of PROFINET devices (internal ref: 2369963).
Increased tolerance in the event of failing and returning PB/PN devices (internal ref: 3082562).
Increased tolerance in the event of faults on the Profibus DP and PROFINET (internal ref: 3017340, 2783150).
After downloading a faulty configuration and subsequently correcting it, the MAINT LED no longer remains constantly lit (internal ref: 2434632).
Using PDM and writing a data set by controller application at the same time and on the same periphery station may result in a system shut down in very rare cases (internal ref: 2713746).
Increased tolerance for CiR loading and simultaneous station return (internal ref: 3279422).
In extremely rare cases, a call of the TCON could lead to the reserve CPU switching to error-search mode (internal ref: 2916132).
The fault tolerance of MRP communication was further increased (internal ref: 2927068).
Robustness increase belongs to SNMP protocol failures were done. Additionally, it is now possible to deactivate the SNMP protocol, identical workflow as described in SIOS-ID: 109760539 (/cs/ViewDocument.aspx?ArticleID=109760539) (internal ref: 3212316).
In extremely rare cases, a sync loss could occur followed by a system shutdown after a buffered power on and subsequent downloading of very large function blocks (internal ref: 3790197).
Communication via UDP connections has been further optimized. The robustness of a faulty connection setup with TUSEND has been increased (internal ref: 3243985).
Optimized reaction in the very rare case of hardware defects additionally increases system availability (internal ref: 3879447).
By using the "Report system errors" function, in rare cases it was possible that correct values were not shown in the status display of the hardware configuration online view. The correct device status is now displayed for an activated system error (internal ref: 3843887).
In very rare cases, the use of F-systems in conjunction with a programmed master/reserve switchover with the SFC90 could lead to the automation system switching to error-search mode (internal ref: 3955490).
V6.0.10
© Siemens AG 2009-2023 - Imprint (https://www.siemens.com/corporate-information) Privacy policy (https://www.siemens.com/privacy-notice) Cookie policy (https://www.siemens.com/cookie-notice) Terms of use (https://www.siemens.com/terms-of-use)
Digital ID (https://www.siemens.com/digital-id) 0.0.0.0
Download V6.0.10 (recommended for upgrading: 25 March 2022)
Firmware V6.0.10 can be used independently of the STEP 7 or PCS 7 version in use.
Optimization of the processing in the case of very rare hardware defects additionally increases system availability. (Internal ref.: 20485)
The availability of the redundant automation system has been increased by extending the correction mechanisms for temporary internal inconsistencies. The need for debugging has been further reduced. (Internal ref.: 301230/303451)
Reduction of switchover times in a high-availability automation system with configured ISO communication (BSEND/BRECV). (Internal ref.: 20511)
Optimization of the system behavior for a PROFIBUS DP line switchover with a very low transmission rate (configured baud rate e.g. 93.75 Kbps). (Internal ref.: 27148)
The online monitoring of variables in large networks has been improved. (Internal ref.: 27190)
The remote port for passive TCP connections can be specified. Remote port "0" is still rejected. (Internal ref.: 27208)
Increased tolerance when downloading the hardware configuration with IE/PB LINK and DP slaves with more than 188 slots. (Internal ref.: 27214)
Increased resilience in case of an erroneous connection of a "free H-connection" by external devices. This no longer causes the automation system to fail. (Internal ref.: 27243)
Increased tolerance when a PROFIBUS cable is disconnected in a redundant automation system. (Internal ref.: 27252)
Optimization of system redundancy when I/O access errors occur. (Internal ref.: 27274)
In extremely rare cases, "coupling and updating" with high PBK communication could lead to an automatic reboot of the master CPU, and thus to a failure of the automation system. (Internal ref.: 27293)
In very rare cases, after adding an ET 200M output module using H-CiR, there was a brief 1-signal at the outputs of the newly added module. (Internal ref.: 27298)
In the redundant automation system with PROFIBUS or PROFINET process periphery, the behavior has been optimized for the extremely rare case of defective modules or when pulling modules (e.g. ET 200SP HA: pulling a redundant "side-by-side" module). (internal ref.: 27347)
Increased resilience for CiR loading processes. (Internal ref.: 27317)
The automation system remains available after an SSL query (SSL ID=0x19a, MAC address) on a failed device. (Internal ref.: 27346)
Increased tolerance when calling SFC70 with incorrect parameters. (Internal ref.: 66605)
07/2023:
MLFB V6.0.10
4125HK06_V6010.exe (5,3 MB)
CPU 412-5H PN/DP 6ES7 412-5HK06-0AB0 (/cs/attachments/109474550/4125HK06_V6010.exe) (SHA-
256)
4145HM06_V6010.exe (5,3 MB)
CPU 414-5H PN/DP 6ES7 414-5HM06-0AB0 (/cs/attachments/109474550/4145HM06_V6010.exe) (SHA-
256)
4165HS06_V6010.exe (5,3 MB)
CPU 416-5H PN/DP 6ES7 416-5HS06-0AB0 (/cs/attachments/109474550/4165HS06_V6010.exe) (SHA-
256)
4175HT06_V6010.exe (5,3 MB) For further information on SHA-256 see Entry ID 109483101 (/cs/document/109483101/how-do-you-determine-the-sha-256-or-sha-512-checksum-of-a-file-?
CPU 417-5H PN/DP 6ES7 417-5HT06-0AB0 (/cs/attachments/109474550/4175HT06_V6010.exe) (SHA- lc=en-ww) .
256)
Security information
© Siemens AG 2009-2023 - Imprint (https://www.siemens.com/corporate-information) Privacy policy (https://www.siemens.com/privacy-notice) Cookie policy (https://www.siemens.com/cookie-notice) Terms of use (https://www.siemens.com/terms-of-use)
Digital ID (https://www.siemens.com/digital-id) 0.0.0.0
In order to protect technical infrastructures, systems, machines and networks against cyber threats, it is necessary to
implement – and continuously maintain – a holistic, state-of-the-art IT security concept. Siemens’ products and solutions
constitute one element of such a concept. For more information about cyber security, please visit
https://www.siemens.com/cybersecurity#Ouraspiration. (https://www.siemens.com/cybersecurity#Ouraspiration)
Rate entry
You want to discuss in our forum and exchange experiences with other users
Go to the Forum (/forum/ww/en)
Note: Depending on the effort involved, support may be subject to a charge. In this case, please have a Siemens Industry Service Card (https://support.industry.siemens.com/cs/ww/en/sc/4869) ready.
You want to create CAx data for one or more products
Go to the CAx download manager
Note: The feedback always relates to the current entry. Your message will be forwarded to our technical editors working in the Online Support. In a few days, you will receive a response if your feedback requires one.
© Siemens AG 2009-2023 - Imprint (https://www.siemens.com/corporate-information) Privacy policy (https://www.siemens.com/privacy-notice) Cookie policy (https://www.siemens.com/cookie-notice) Terms of use (https://www.siemens.com/terms-of-use)