Update

Various improvements and bug fixes

The following behavior has been improved

  • The time synchronization via NTP was improved.
  • If a wrong interface ID is used at the TCON function block, the wrong STATUS "0x80CE"(ERROR_TCON_LOCAL_IP_IS_ANY) is no longer output at the TCON function block but the expected "0x809B"(ERROR_TCON_INVALID_LOCAL_DEVICE_ID).
  • The behavior of the function block "Get_Alarm [FB702]" at reconfiguration of alarms has been improved.
  • The readout of CPU service data has been improved.
  • The reading of recipes (> 512 bytes) with WinCC option SES/LCS has been improved.
  • The behavior in case of user programming errors in connection with arrays has been improved.
  • The behavior when overloading in RUN with many changes of alarm instances has been improved.
  • Serialization from Array of Bool to Array of Byte has been improved.
  • Writing variables to the CPU via the Tag Status and Variable Tables web pages is now always possible after initial authentication and no longer requires re-authentication.
  • The access via View of Things (VoT) to the data types Bool/BBool in multidimensionalArrays via the Web API methods PlcProgram.Read and PlcProgram.Write has been improved.

The following behavior has been fixed

Sporadic error message no longer occurs after setting the REQ input TSEND block of an ISO-on-TCP connection.

  • Temporary CPU error:Fatal firmware exception error
    (internal system code: 16#00000801 16#10028001 16#00008003)
    CPU changes to DEFECTIVE state (system reaction)

**When Graceful Shutdown is activated for a TCP connection of the Open User communication and this connection is closed directly one after the other on the one hand by the communication partner and on the other hand by the CPU, the situation no longer occurs that the CPU continues to reserve the used "connection id" unintentionally after successful termination of the TCP connection. The CPU now releases the "connectionid" as expected, so that it is subsequently available for the establishment of another communication connection.
When accessing the CPU online, the sporadic error messages no longer occur:.

  • Temporary CPU error: Serious firmware exception error (internal system code: 16#00400001 16#10020082 16#783F90A8) CPU changes to DEFECTIVE state (system response) or
  • Temporary CPU error: Fatal firmware exception error (internal system code: 16#00400001 16#1002008216#00010246) CPU changes to DEFECTIVE state (system response)

When there is a high communication load via a CP module operating behind an ET 200SP CPU, the sporadic error message no longer occurs:

  • Temporary CPU error: Serious firmware exception error (internal system code: 16#00100001 16#1002FFFF16#76EB9290) CPU changes to DEFECTIVE state (system response)
    The copying of I/O data to an optimized DB has been optimized.

The web server is now accessible after a hardware configuration download, if "Obtain IP address by other means" was set for the used interface of the CPU and the IP address was configured via the user program.
For non-optimized data blocks the correct bit offset in the absolute address is now returned via method PlcProgram.Browse of the Web API.
If an error occurs in the time synchronization via NTP for S7-1500 R/H CPUs, the sporadic error message in the backup CPU no longer occurs when using GetClockStatus or RD_SYS_T blocks:

  • Temporary CPU error:Fatal firmware exception error
    (internal system code: 16#0FFF0000 16#10020000 16#000000) Temporary CPU error:Fatal firmware exception error
    (internal system code: 16#0FFF0000 16#10020000 16#000000)
    CPU changes to DEFECTIVE state (system reaction)CPU changes to DEFECTIVE state (system reaction)
Version: V2.9.7 Link
Receive Important Update Messages Stay tuned for upcoming Siemens Motor starter SIMATIC ET 200pro updates

Was the content helpful to you?

Advertisement Advertise here?
Udemy IT certification ad