Hi,

yes, check the link and you will get this information:

Update V2.9.4 CPUs

Dependencies with regard to STEP 7, STEP 7 Safety Advanced and upwards compatibility:
Totally Integrated Automation Portal with STEP 7 Professional V17 or higher is required to configure this CPU firmware version.
Configurations with earlier TIA Portal STEP 7 Professional versions are compatible with later releases.
The handling is described detailed in entry109744163

Enhancement of the user experience:

The following behavior has been improved:

• OPC UA Server: Change of the behavior when using multi-dimensional arrays in a UDT:
  As of firmware version V2.9.4, S7-1500 CPUs encode multi-dimensional arrays within structures according to the OPC UA specification V1.04. CPUs with older firmware versions encode the corresponding structures in a different form. If you have been using multi-dimensional arrays within structures for CPUs with older firmware versions and want to upgrade to the latest firmware version, you must update your client programs accordingly.
• The startup behavior of the CPUs has been stabilized.
• Copying data between optimized and non-optimized data blocks has been improved.
• Export of recipes with structures and underlying scalar data types no longer generates the error message 16#8091.
• With S7-1500 CPUs <=1516, it no longer happens very sporadically that a constant of the type LWORD or LREAL is not written correctly in very large instance data blocks (> 32 Kbytes) when the instance is called.
  
  

The following behavior was corrected:

• When starting communication with a PROFINET device, these sporadic error messages no longer occur:
  • Temporary CPU error: Serious firmware exception error (internal system code: 16#00000265 16#1002000D 16#00000000)
    CPU switching to DEFECTIVE mode (system reaction) or
  • Temporary CPU error: Serious firmware exception error (internal system code: 16#00080001 16#1002FFFF 16#00000246)
    CPU switching to DEFECTIVE mode (system reaction)
• When using SFB 143 "DataLogClear" simultaneously with an instruction of the group "File handling" ("FileReadC" or "FileWriteC"), these sporadic error messages no longer occur:
  • Temporary CPU error: Serious firmware exception error (internal system code: 16#00400001 16#1002006F 16#7856D54C)
    CPU switching to DEFECTIVE mode (system reaction) or
  • Temporary CPU error: Serious firmware exception error (internal system code: 16#00400001 16#1002006F 16#00010202)
    CPU switching to DEFECTIVE mode (system reaction)
• Web pages of the CPU created with SIMATIC WinCC Unified "View of Things", no longer show the error message "invalid Tagname xxx" when the symbolic address contains UTF-8 characters, such as Chinese characters and the address element is not bracketed by quotation marks.
• When accessing the web server of the CPU, these sporadic error messages no longer occur:
  • Temporary CPU error: Serious firmware exception error (internal system code: 16#00080001 16#1002007B 16#E0042DB4)
    CPU switching to DEFECTIVE mode (system reaction) or
  • Temporary CPU error: Serious firmware exception error (internal system code: 16#00000038 16#10020000 16#00000000)
    CPU switching to DEFECTIVE mode (system reaction) or
  • Temporary CPU error: Serious firmware exception error (internal system code: 16#00080001 16#1002007B 16#E0042EA4)
    CPU switching to DEFECTIVE mode (system reaction)
• When using very large blocks, sporadic compilation errors when downloading to the CPU and the subsequent error message no longer occur:
  • Temporary CPU error: Serious firmware exception error (internal system code: 16#00400001 16#10020035 16#77D95B54)
    CPU switching to DEFECTIVE mode (system reaction)
• When triggering alarms, sporadic error messages no longer occur:
  • Temporary CPU error: Serious firmware exception error (internal system code: 16#0FFF0000 16#10020000 16#00000000) CPU switching to DEFECTIVE mode (system reaction)
• When using the instruction MC_SetAxisSTW, the error 16#8FFF no longer occurs when the execute bit is set with the falling edge of the MC_Power.Enable.
• When using the technology object TO_CamTrack in special scenarios, faulty switching of cams no longer occurs.
• When using the instructions MC_OffsetRelative or MC_OffsetAbsolute with a negative offset that are being replaced by an MC_OffsetRelative, undesirable motions of the following axis no longer occur.
• After upgrading a project to motion control version 6.0, zero pointer access in the OB MC-Transformation (OB98) no longer occurs when using the user-defined kinematics.
• In case of significant changes to the dynamic values at the TO Kinematics, sporadic error messages no longer occur:
  • Temporary CPU error: Serious firmware exception error (internal system code: 16#00400001 16#10020059 16#00010202)
    CPU switching to DEFECTIVE mode (system reaction)

 

 Regards,

Towome