Maintenance of PCS 7 V5.1 is still assured.

• If a Hotfix or a Service Pack for a problem exist, this Hotfix or Service Pack will be made available.
• If the problem can only be solved with PCS 7 V5.2, a software update is required. The consequences of software updating to the client are similar to those of a Service Pack.
• If the problem has not been identified yet, problem correction will be made within the framework of PCS 7 V5.2. In this case a software update to PCS 7 V5.2 incl. Hotfix or Service Pack will be made available.

New technical features of the Operator Station OS

• Specification of the channel fault in the process control message
  In the process control message the fault arising at a channel will now be displayed with a specification of the fault reason (e.g. open wire). Previously, only the channel fault as such was displayed. This applies to DI, DO, AI, AO, as well as to centralized and distributed I/Os.
   

New technical features of the Engineering System ES

• CPU Robustness
  Additional measures have been implemented to avoid reasons for CPU STOPs. Checking of local data requirements, nesting depth of blocks and number of PBC (programmed block communication) block instances have been improved. Before loading is started the loading memory and the working memory are checked for sufficient capacity.
  In addition, warning limits can be specified to indicate possible reasons for STOPs when exceeded. Warning limits can be specified for local data requirement, memory space and the max. no. of PBC blocks.
   
• Handling of blocks
  If a block type is imported that already exists under the same object name (block no., e.g. FB 61), but with a different symbolic name, a dialog will appear to re-name the block (in line with the copying of blocks with the same object name in the SIMATIC Manager).
   
• Extended diagnostics
  The function "Generate module driver" has been extended and made more open:
  The new driver concept permits the support of PA devices, including the import of data from SIMATIC PDM.
  The new driver blocks enable the exact specification of channel faults in the messages.
  If new Siemens or non-Siemens module types have to be included, the partial knowledge about the driver generator can be supplemented by additional XML files (object and action lists), to ensure that diagnostics is in conformity with PCS 7. The manual "Programming Instructions: Generating Driver Blocks" describes how these files are generated.
  In existing projects the module drivers can continue to be generated according to the existing driver concept (compatibility).
  
  The blocks of the new driver concept (OB_BEGIN, OB_END, OB_DIAG) enable more accurate and more specific diagnostics. To avoid double messages, the previous process control group messages can be suppressed.
   
• Extended plan reference data
  The plan reference data contain a list indicating all OBs used in the program with the required local data space and the configured local data sizes (off-line and on-line). This information makes it easier to introduce any adaptations that may be necessary.
  The specifications in the statistics list of the plan reference data have been extended. Now, all PBC-relevant block instances are listed (also user blocks and called blocks of a multi-instance block). The statistics list shows the number of process objects of a project and the max. possible number of process objects in accordance with the installed license.
   
• Reading back parameters from the CPU
  The function "Read back parameters" has been further improved. A protocol listing the parameters that have been read back is now additionally available.
   
• PCS 7 Block libraries
  The existing driver blocks (PA_DI, PA_DO, PA_AI, PA_AO and PA_TOT) have been converted to symbolic addressing. The blocks process the corresponding PA profiles of a PA field device in accordance with PROFIBUS PA 3.0 class A and B.
  In analogy to the MOD blocks of S7-300/400 SM modules, there are now also driver blocks for PA devices to monitor the modules:

Based on the existing blocks CH_DI, CH_DO, CH_AI and CH_AO of the "PCS 7 Driver Blocks" library, new universal blocks CH_U_DI, CH_U_DO, CH_U_AI and CH_U_AO have been created and expanded for signal processing of a PA field device (PA profile 3.0) or of a HART main/subsidiary variable. With these blocks a function can either be operated with conventional I/Os, or with field devices.
The new block library is installed under a new name, so that the previously installed PCS 7 library can remain on the PC.

• SIMATIC PDM
   
• SIMATIC PDM has been expanded by the configuration for ET 200iS. The HART field devices connected to ET200iS can also be configured with PDM, based on the PNO standard.
  The new driver concept permits the automatic import of data from PDM to the driver blocks.
  SIMATIC PDM V5.1+SP1 will be supplied together with ET200iS for the latter's startup quantities. SIMATIC PDM V5.1 will continue to be available. When the startup quantities have been shipped, SIMATIC PDM V5.1+SP2 will be released.
   
• Usability
  The Engineering System V5.2 has been rounded off by additional usability improvements. This also includes index labels for sub-diagrams in CFC, minimization of the necessity to change between keyboard and mouse, improved navigation and signal follow-up, optionally higher "packing density" of blocks in a diagram.

New technical features in the connection of I/O modules and field devices

• Y-Link
  The Y-Link (order no. 6ES7 197-1LA00-0XA0, consisting of IM 157, Y coupler and RS485 repeater) enables single-channel decentralized I/Os to be connected to a H-type CPU via a redundant PROFIBUS DP.
  DP slaves (DP V0) can be connected behind the Y-Link (with 12 MBaud between DP master and Y-Link and max. 1.5 MBaud between Y-Link and DP slave).
  The evaluation of the diagnostics of the Y-Link (and thus of the indirectly connected DP standard slaves) is supported by driver blocks. A transparent transfer of the DP standard slave diagnostics via the Y-Link is not yet possible.
   
• ET200iS
  As from PCS 7 V5.2, the ET 200iS can be configured for Ex areas (together with SIMATIC PDM). The ET200iS modules listed below are integrated in the configuration with SIMATIC PCS 7 V5.2 (Driver Wizard). See separate Simatic update on the start of shipment of the ET200iS and the modules.

The following modules are supported:

	IM151-2	6ES7 151-2AA00-0AB0
	Digital input 4 x DI Namur	6ES7 131-5RD00-0AB0
	Digital output 2 x DO 25V/25mA DC	6ES7 132-5SB00-0AB0
	Analog input 2 AI, 2DMU	6ES7 134-5RB00-0AB0
	Analog input 2 AI, 4DMU	6ES7 134-5RB50-0AB0
	Analog input 2 AI, RTD	6ES7 134-5SB50-0AB0
	Analog input 2 AI, TC	6ES7 134-5SB00-0AB0
	Analog output 2 AO	6ES7 135-5RB00-0AB0
	Analog input 2 AI Hart, 2DMU	6ES7 134-5TB00-0AB0
	Analog input 2 AI Hart, 4DMU	6ES7 134-5TB50-0AB0
	Analog output 2 AO Hart	6ES7 135-5TB00-0AB0

• ET200X

The ET 200X distribured I/O system can be included as from PCS 7 V5.2.
Configuration in PCS 7 is in analogy to ET200M.

The following modules are supported by PCS7 V5.2:

	DI 8x 24V DC	6ES7 141-1BF30-0XA0
	DO 4x 24V/2A DC	6ES7 142-1BD40-0XA0
	DO 4x 24V/2A DC	6ES7 142-1BD40-0XB0
	AI 2x U (+/-10V)	6ES7 144-1FB31-0XB0
	AI 2x I (+/-20mA, 4-20mA, 4-wire measuring transducer)	6ES7 144-1GB31-0XB0
	AI 2xI (4-20mA, 2-wire measuring transducer)	6ES7 144-1GB41-0XB0
	AI 2x RTD (Pt100)	6ES7 144-1JB31-0XB0
	AO 2x U (+/-10V)	6ES7 145-1FB31-0XB0
	AO 2x I (+/-20mA, 4-20mA)	6ES7 145-1GB31-0XB0
	DI 4/DO 2xP	6ES7 148-1DA00-0XA0
	DO 16xP (connecting module for CPV10 valve cluster)	6ES7 148-1EH01-0XA0
	DO16xP (connecting module for CPV10 valve cluster	6ES7 148-1EH11-0XA0
	Erxpansion module DO 8x 24V/1.2A DC, long design	6ES7 142-1BF30-0XA0
	Power module DO 4x 24V/2A DC	6ES7 148-1CA00-0XB0
	DI 8x 24V DC	6ES7 141-1BF40-0XA0

• ET200M
  With PCS 7 V5.2 the range of modules supported by PCS 7 has been increased by various standard modules.
   
• Diagnostic repeater
  As from PCS 7 V5.2, the diagnostic repeater can be used for cable diagnostics on PROFIBUS-DP (Copper cables, up to 12 MBaud). The diagnostic repeater can be connected to PROFIBUS-DP and displayed and operated via HW-Config.
   
• DP V0 Slaves
  Non-Siemens DP slaves responding like standard slaves acc. to DP V0 can also be configured as from PCS 7 V5.2 and higher. A module driver has to be generated for this purpose. This module driver can be integrated in the new driver concept.

New technical features of the Automation Systems AS

• S7-400-CPUs

The new driver concept is supported by the following CPUs with firmware version 3.0 and higher:

	CPU 414-3	6ES7 414-3XJ00-0AB0
	CPU 414-4H	6ES7 414-4HJ00-0AB0
	CPU 416-2	6ES7 416-2XK02-0AB0
	CPU 416-3	6ES7 416-3XL00-0AB0
	CPU 417-4	6ES7 417-4XL00-0AB0
	CPU 417-4H	6ES7 417-4HL01-0AB0

• Other improvements for S7-400 CPUs V3.0
  The extended connectiondiagnostics (identification of an open connection to the CPU -> display in the proces control message) is now also being supported for standard CPUs.
  CPUs with firmware V3.0 now also support DP V1 communication. Details are available from the following entry:

http://www.ad.siemens.de/simatic-cs under the entry ID 7027576

DPV1 Communication is also possible via CP443-5 Ext (DX03/V4.0 and higher).

CPUs with firmware V3.0 now also support operation of an S7-400 CPU as I-slave. Details are available from the following entry:

http://www.ad.siemens.de/simatic-cs under the entry ID 113652

The Industrial Ethernet CPs have also been innovated with a new firmware:
As of firmware version 2 the initial node identification no longer requires MPI, but is effected directly via Industrial Ethernet.

Use of BATCH flexible
The proven BATCH flexible V4.02 can now also be used with PCS 7 V5.2.

Please speak to your SIMATIC contact at your local Siemens office if you have any further questions.