show the entry list
Operating System Updates for IM154-8F PN/DP CPU (6ES7154-8FB01-0AB0)
Part number:

DESCRIPTION:
When updating the operating system, always update to the latest version available for the product and its respective article number. The previous versions of the operating system are only intended as backup to allow a downgrade to the original version. Until now this is not known to have been necessary in any case.
The respective latest version of a CPU operating system is valid for all versions of that article number.

Please note:
During the firmware update the actual values will be lost. If you require them, please save these values before starting with the FW update with the function "Copy RAM to ROM...."


The update can either be performed via Micro Memory Card or online:

1. Micro Memory Card:

Requirements for creating an operating system update card:

  • Micro Memory Card with at least 8 MB storage capacity article number 6ES7953-8LP20-0AA0
  • STEP 7 V5.1 SP2 or higher
  • PC with external PROM programmer (6ES7 792-0AA00-0XA0) or FieldPG / PowerPG  for programming the Memory Card

Creating the operating system update card with STEP7:

Recommendation:
Save the "old" firmware on an empty SIMATIC Micro Memory Card, before you update the firmware of your IM154-8F PN/DP CPU interface module. If problems should arise during the update, you can load the old firmware back to your module from the memory card.

  1. Download the desired CPU file
  2. Unpack the file by double-clicking the file name
  3. Delete the Micro Memory Card by executing "File / S7 Memory Card / Delete" in Simatic Manager.
  4. Program the operating system by choosing in Simatic Manager: "Target System/Update Operating System", select the destination directory and start programming by "opening" the CPU_HD.UPD file.
  5. The operating system update card is programmed when the message "The firmware update for the module with order number 6ES7154-8FB01-0AB0 was transferred successfully to the S7 memory card" appears on the screen.

To update the operating system:

  1. Switch OFF the power to the IM154-8F PN/DP CPU and insert the SIMATIC Micro Memory Card with the firmware update.
  2. Switch the power ON again
  3. The IM154-8F PN/DP CPU will automatically identify the SIMATIC Micro Memory Card with the new firmware and start with the firmware update.
  4. During this process all LEDs will be lit.
  5. When the firmware update has been concluded, the STOP LED will blink. This is the request for an overall reset by the IM154-8F PN/DP CPU.
  6. Switch OFF the power to the IM154-8F PN/DP CPU and remove the SIMATIC Micro Memory Card with the firmware update.


2. Online:

Requirements:

  • Online updating of the firmware is possible with STEP 7 V5.4 + SP 4 and higher.
  • The interface module to be updated must be located in a station that can be reached online.
  • The files with the latest firmware version must be available on the file system of your programming device (PG or PC). One folder may only contain the files for one firmware version.

To update the firmware:

  1. Start STEP 7 and switch to HW-Config.
  2. Open the station with the IM154-8F PN/DP CPU to be updated.
  3. Earmark the IM154-8F PN/DP CPU.
  4. Select the menu option Target system > Firmware update.
  5. In the opened menu option Firmware update use the Search button to select the path to the  firmwareupdate files (*.UPD).
  6. When you have selected a file, you will be told in the lower part of the Firmware update dialog field for which module and from which firmware version onwards the file is suitable.
  7. Click the Execute button. STEP 7 will check whether the selected file can be interpreted by the IM154-8F PN/DP CPU and - if the result is positive - load the file to the interface module. If the operating mode of the IM154-8F PN/DP CPU needs to be changed for this purpose you will be asked to perform this action. The IM154-8F PN/DP CPU will then perform the firmware update on its own.
  8. Check with STEP 7 (read CPU diagnostic buffer) whether the IM154-8F PN/DP CPU successfully starts up with the new firmware.

Alternatively you can also trigger the firmware update in SIMATIC Manager:

  • Select the corresponding IM154-8F PN/DP CPU interface module as target CPU and then "Target System/Update Firmware".
  • Select the target CPU via "Accessible Nodes" and then "Target System/Update Firmware".

Both paths will guide you to the above step 5. Now proceed with the other steps. 

Please note:

The following values will be retained when the CPU has been subjected to an overall reset:

  • the parameters of the MPI interface (MPI address and highest MPI address)
  • the IP address of the CPU
  • the sub-network mask
  • the static SNMP parameters

Result

You have equipped your IM154-8F PN/DP CPU interface module online with a new firmware version.

Overview of article numbers and latest versions of the IM154-8F PN/DP CPU:
 Article Number

FW
version

Upgrade with ...
6ES7154-8FB01-0AB0    
 

V3.2.10

Recommended for upgrade:

Update V3.2.10 description

 1548FB01_V3210.EXE ( 6259 KB )

 

V3.2.8

Backup only:

Update V3.2.8  description

 1548FB01_V328.EXE ( 6202 KB )

 

V3.2.7

Backup only:

Update V3.2.7  description

 1548FB01_V327.EXE ( 6191 KB )

 

V3.2.6

Backup only:

Update V3.2.6  description

 1548FB01_V326.EXE ( 6091 KB )

 

V3.2.3

Backup only:

Update V3.2.3  description

 1548FB01_V323.EXE ( 6197 KB )

 

V3.2.1

Backup only:

 1548FB01_V321.EXE ( 6182 KB )

Update V3.2.10 (6ES7154-8FB01-0AB0)

The above CPU version contains no new functions.

Information on STEP7 dependencies and upward compatibility:
To be able to run this CPU your require STEP7 V5.5 or higher.
For the CBA configuration you require iMap V3.0 +SP1 or higher. Configurations with earlier STEP7 and iMap versions are compatible with later releases.
For failsafe applications you require the option package S7 Distributed Safety V5.4 SP4 or higher.

The new firmware version provides the following corrections:

  • In the case of a message buffer dump with a large number of transmission messages that would lead to an abortion of the message dump by the connection partner, e.g. because of lack of memory space, the connections will no longer get hooked up and a Defect with Z1=98C6 will no longer occur.
  • The retentivity backup in the case of power off/on has been stabilized, so that the previously occuring very sporadic Defect with Z1=F00F no longer occurs.
  • With TIA version V11 the loading of blocks which contain an ANY-Pointer with length 0 will no longer lead to Defect of the CPU with Z1=F012.
  • During online monitoring of several blocks with TIA version V12 the previously occuring Defect with Z1=7141 after the third block is now prevented; instead, a negative checkback will be generated.
  • An abortion of the communication connection during Block Status could previously cause the sporadic Defect with Z1=F004. Connection monitoring has now been improved.
  • Rapid successive calls of the SFB 52 (reading of data records) will no longer cause the sporadic Defect with Z1=E801.
  • Repeated loading of the user program on MMC with a simultaneously open topology display will no longer cause the Defect with Z1=F014.
  • Disturbances on the line during job reception from a connection partner will no longer cause the sporadic Defect with Z1=700A.
  • When calling several SFCs13 "Read Standard Diagnostics" the analog I/Os of correctly connected slaves will no longer supply the incorrect diagnosis "Wire Break".
  • During the startup of iDevices with update times set to  > 64 ms, e.g. because of a WLAN line, the login process will no longer sporadically leave some devices out, resulting in a blockage to the plant controller connection.
  • The use of Opera 15.0 or iOS5 with the web server no longer leads to representation errors or a curtailed display of the diagnostic buffer entries. The accessibility with the HTTPS setting has been stabilized.
  • Loading of large F-blocks of > 64KB with TIA version V12 is now possible and no longer leads to a CRC error message.

 
Update V3.2.8 (6ES7154-8FB01-0AB0)

The above CPU version contains no new functions.

Note on STEP7 dependencies and upward compatibility:
To be able to run this CPU your require STEP7 V5.5 or higher.
For CBA configuration you require iMap V3.0 +SP1 or higher.
Configurations with earlier STEP7 and iMap versions can be used with upward compatibility.

For failsafe applications you require the option package S7 Distributed Safety version V5.4 SP4 or higher.

Firmware update V3.2.8 provides the following corrections:

  • COS values of very small numbers (>=0 and <3.8518597E-34) are now output correctly with value 1.
  • AUF DB/DI indirect no longer causes sporadic opening of an incorrect DB.
  • In the case of a block upload or download the CPU will no longer sporadically go to Defect with Z1=F01A.
  • Communication abortions while the communications functions are running will no longer sporadically lead to Defect with Z1=F012.
  • In the case of block calls of the SFCs 82..84 with REQ=0 (RET_VAL=7000), BUSY will not be signaled with TRUE anymore.
  • The accuracy of the square root calculation "SQRT" has been improved.

Update V3.2.7 (6ES7154-8FB01-0AB0)

This firmware version contains the following new features:

  • SFC 109 PROTECT: new mode 12, with which protection level 3 can be activated via user program without password legitimation (even with a password it is now impossible to read/write access the CPU)
  • ET200 motor starters can now be configured as transparent I/Os.

see also Product Information at entry ID 61757603

Note on STEP7 dependencies and upward compatibility:
To be able to run this CPU your require STEP7 V5.5 or higher.
For CBA configuration you require iMap V3.0 +SP1 or higher.
Configurations with earlier STEP7 and iMap versions can be used with upward compatibility.

For failsafe applications you require the option package S7 Distributed Safety version V5.4 SP4 or higher.

Firmware update V3.2.7 provides the following corrections:

  • To prevent loss of retentivity with event ID 16# 4580 resp. event ID 16# 6523, the MMC connection in the case of power off/on has been optimized.
  • If the SFC 23 DEL_DB is used and a DB does not exist, defect Z1=F833 will no longer occur.
  • In the case of synchronization errors that cause a STOP of the CPU, defect Z1=F004 will no longer occur highly sporadically.
  • The abortion of a block transfer will no longer lead to a sporadic defect Z1=4131.
  • Connections of the CPU to a PLC link device will now be cut completely in the case of a connection abortion.
  • If clock flags are used, the three adjacent flag byte addresses are no longer influenced anymore.
  • Uploading of blocks to programming devices has been performance optimized.
  • Specific resources have been increased to ensure that Web-server accesses in the case of storm attacks remain operable.
  • If I-Devices have been configured with sub-module lengths of more than 32 Bytes, OB61 clock pulses will no longer be inaccurate or fail altogether.
  • If programs have been created with SCL, TSEND or TRECV blocks on which send or receive buffer lenghts have been declared as STRING, will no longer cause RET_VAL  807F.
  • Upstream switches that do not support LLDP will no longer cause a defect with Z1=8005 if there are several adjacent modules.
  • After connection breaks with the Open-User communication there will be no more highly sporadic defect with Z1=E801.
  • Multiple bit logical interconnections that concern the same byte will now be executed correctly.
  • The startup characteristics of F modules that have no load voltage upon startup of the CPU, has been improved.
  • If the SFC 12 "D_ACT_DP" is used and a Simocode module is parameterized at the same time when there is a STOP-RUN transition, defect Z1=3303 will no longer occur.
  • Downloading of blocks or projects will no longer cause the cycle time to be constantly increased therafter.

Update V3.2.6 (6ES7154-8FB01-0AB0)

The above new CPU version does not contain any new functions.

Note on STEP7 dependencies and upward compatibility:
To be able to use the new functionalities your require STEP7 V5.5 or higher.
For CBA configuration you require iMap V3.0 +SP1 or higher. Configurations with earlier STEP7 and iMap versions can be used with upward compatibility.
For safety applications you require the option package S7 Distributed Safety V5.4 SP4 or higher.
 
Firmware update V3.2.6 provides the following corrections:

  • Modules that have run for approx. 500 days will no longer get stuck sporadically or show endlessly running timers.
  • Cache errors that cannot be corrected and very sporadically occur during CPU startup will now be entered in the diagnostic buffer with defect identifier Z1= F001 and branched to "Defect" status. During startup the CPU can no longer enter a inconsistent state which is sporadically entered in the diagnostic buffer with event ID 16# 4580 (inconsistent backup buffer content).

Update V3.2.3 (6ES7154-8FB01-0AB0)

Note on STEP7-related dependencies and upwards compatibility:
To be able to use the new functions you require STEP7 V5.5 or higher.
For CBA configuration you require iMap V3.0.1 or higher.

Configurations with older STEP7 and iMap versions can be used with upward compatibility.

Distributed Safety:
For safety applications you require the option package S7 Distributed Safety V5.4 SP4 or higher.

New function:
The above CPU version now enables you to employ the transfer area type "I/O" in a CPU run as I-Device.

The following changes will become effective with firmware update V3.2.3:

  • The retentivity backup for power OFF has been stabilized (concerns highly sporadical loss of retentivity with event ID 16# 4580 "Backup buffer content inconsistent").
  • If a slave has been activated with the SFC12 and subsequently fails, the identifier for an I/O access error will not sporadically remain set anymore if the slave returns during a transition from STOP to STARTUP (e.g. during startup of the CPU).
  • The configuration and use of I/O transfer areas when run as I-Device (direct access from a higher level IO-Controller to the local I/Os of the IM 154-8F PN/DP CPU as I-Device), have been released.
  • No more sporadical loss of actual values after power OFF due to a request for overall reset because of a memory replacement (event ID 16# 6526).

 Entry ID:47354578   Date:2013-12-06 
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 
Topics
Help
Online Help
Guided Tour