Pcs 7
Pcs 7
Pcs 7
Additional support 2
Ensuring Availability 3
SIMATIC Configuring diagnostics
conditions 4
PCS 7 process control system
Service support and diagnostics Message concept of PCS 7 5
(V8.0)
Failure - What next? 6
Service Manual
Diagnostics in PCS 7 7
Failure, replacement and
return 8
03/2012
A5E02779775-02
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
with a safety alert symbol, indicates that minor personal injury can result if proper precautions are not taken.
CAUTION
without a safety alert symbol, indicates that property damage can result if proper precautions are not taken.
NOTICE
indicates that an unintended result or situation can occur if the relevant information is not taken into account.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will be
used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to property
damage.
Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions. Qualified
personnel are those who, based on their training and experience, are capable of identifying risks and avoiding
potential hazards when working with these products/systems.
Proper use of Siemens products
Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended or
approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be complied with. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of Siemens AG. The remaining trademarks in this publication
may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software described.
Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in
this publication is reviewed regularly and any necessary corrections are included in subsequent editions.
1 Preface.........................................................................................................................................................7
2 Additional support.......................................................................................................................................11
3 Ensuring Availability....................................................................................................................................13
3.1 Introduction..................................................................................................................................13
3.2 Data backup................................................................................................................................14
3.2.1 Options for data backup..............................................................................................................14
3.2.2 Backing up ES project data.........................................................................................................16
3.2.2.1 How to back up parameter settings of the SIMATIC station........................................................16
3.2.2.2 How to archive a project..............................................................................................................17
3.2.2.3 How to retrieve a project..............................................................................................................19
3.2.2.4 How to archive and retrieve a multiproject..................................................................................20
3.2.2.5 How to archive custom libraries...................................................................................................21
3.2.2.6 How to export operator and display texts....................................................................................22
3.2.2.7 How to back up custom functions and actions............................................................................23
3.2.3 Backing up OS project data.........................................................................................................24
3.2.3.1 Backing up configuration data.....................................................................................................24
3.2.4 Backing up batch data.................................................................................................................25
3.2.4.1 Backing up configuration data.....................................................................................................25
3.2.4.2 How to generate a backup...........................................................................................................25
3.2.4.3 How to restore data from a backup.............................................................................................27
3.2.4.4 How to archive batches...............................................................................................................28
3.2.5 Backing up SIMATIC Route Control data....................................................................................29
3.2.5.1 Backing up configuration data.....................................................................................................29
3.2.5.2 How to back up project data from SIMATIC Route Control ........................................................29
3.2.5.3 How to restore data from a backup.............................................................................................30
3.2.6 Creating an image.......................................................................................................................31
3.2.6.1 Backing up data by generating an image file...............................................................................31
3.2.7 Comparing project versions.........................................................................................................32
3.2.7.1 Comparing project versions with VXC.........................................................................................32
3.3 Hardware update.........................................................................................................................32
3.3.1 Hardware updates.......................................................................................................................32
3.3.2 How to make adjustments after a hardware change...................................................................35
3.3.3 Updating the CPU........................................................................................................................35
3.3.3.1 How to perform a firmware update for the CPU (as of V5.0).......................................................36
3.3.3.2 How to perform a firmware update for the H-CPU (as of V4.5)...................................................38
3.3.4 Updating an interface module......................................................................................................39
3.3.4.1 Updating an interface module (IM)..............................................................................................39
3.3.4.2 How to perform a firmware update of an interface module (IM)..................................................40
3.3.5 Updating a CP xxx.......................................................................................................................41
3.3.5.1 Updating a communication processor (CP).................................................................................41
3.3.5.2 How to perform a firmware update of the CP 341.......................................................................42
3.3.5.3 How to perform a firmware update of the CP 443-1....................................................................43
3.3.5.4 How to perform a firmware update of the CP 443-5 Extended....................................................45
3.3.6 Working with GSD files................................................................................................................48
Disclaimer of liability
WARNING
Siemens assumes no liability for inappropriate use of the instructions provided in this
documentation or any consequences that might result for the customer.
● Only trained service employees should be authorized to work on the process control
system.
● Always observe the plant-specific rules and government regulations when making
changes to your system.
● Observe the plant-specific boundary conditions and adjust the work accordingly.
● Always bear in mind that changes in a system can impact other sections of the system.
Note
PCS 7 Readme
The information given in the PCS 7 Readme on the Internet takes precedence over all the
PCS 7 manuals. Please read this PCS 7 Readme carefully; it contains important information
and amendments on PCS 7 for you.
● The PCS 7 Readme on the Process Control System; SIMATIC PCS 7 DVD includes
important notes on PCS 7 and takes precedence over the documentation supplied for
PCS 7.
● Following the installation of PCS 7, you can find documents such as Process Control
System PCS 7; PCS 7 Readme and What's New in PCS 7? via the submenu SIMATIC >
Product Information > <Language>.
As of PCS 7 V8.0, you obtain basic PCS 7 system documentation with the Process Control
System; SIMATIC PCS 7 DVD.
The PCS 7 Internet site www.siemens.com/pcs7-documentation (www.siemens.com/pcs7-
documentation) provides convenient access to the complete PCS 7 documentation. You can
find the following for current PCS 7 versions:
● In the section "Hardware manuals for SIMATIC PCS 7 ..."
– The manuals for components approved for a PCS 7 version
● In the section "Software manuals for SIMATIC PCS 7 ..."
– The complete system documentation
The separate setup program for PCS 7 documentation and the PCS 7 help system for
download. After the installation of the setup program, you will find the documentation at
the following locations on the Engineering Station:
- as online help (CHM file) for the SIMATIC Manager application
- as PDF file in the Windows Start menu with the SIMATIC documentation
– The complete documentation for PCS 7 as a Manual Collection
Required Knowledge
This documentation provides information about working with PCS 7 and is intended for trained
service personnel. The following knowledge is required to understand the documentation:
● Basic knowledge of Microsoft Windows operating systems
● Knowledge of the functions and configurations of SIMATIC PCS 7 (Engineering System,
PCS 7 Operator Station).
Conventions
In this documentation, the names of elements in the software interface are specified in the
language of this documentation. If you have installed a multi-language package for the
operating system, some of the designations will be displayed in the base language of the
operating system after a language switch and will, therefore, differ from the designations used
in the documentation.
Technical support
Technical support for all A&D products can be accessed
● Via the Support Request web form
Technical support (http://www.siemens.en/simatic-tech-doku-portal)
● You can find additional technical support information in the Internet at
http://www.siemens.com/automation/service (http://www.siemens.de/automation/support-
request)
Overview
This section presents measures for ensuring availability of a PCS 7 system.
You can find information on fault-tolerant systems in the Process Control System PCS 7; Fault-
Tolerant Process Control Systems manual.
The information in this section enables you to perform the following tasks:
● Maintain the specified condition of a system.
Examples: Adherence to maintenance intervals, replacement of batteries
● Optimize the system and prevent faults
Examples: perform firmware updates, eliminate known sources of errors
● Minimize downtime caused by faults
Examples: provide backups
Note to reader
This section is split up into several topical fields. The following information is provided for each
topic area:
Content
Introduction
You can back up project data in a variety of ways and for a variety of purposes, for example,
project archiving, image file.
After system failure, you can use a backup to quickly restore the system to its original state.
Note
Make sure that backups are stored in a protected location (in separate rooms, fireproof
cabinets, etc.).
Make sure the backups are readable (particularly when reusable storage media such as
floppy disks are used).
Introduction
You can change parameters (such as controller settings) online in the SIMATIC station using
the PCS 7 OS and the engineering station.
Some situations make it necessary to back up the current data blocks, FBs or parameter
settings from the SIMATIC station. This is the case, for example, when the configuration data
have been restored from a data backup.
You can make use of the following backup options:
● Reading data blocks and FBs from the SIMATIC station
● Reading charts with current parameters from the SIMATIC station
NOTICE
These actions overwrite all settings in the configuration with the current values of the
system. Make sure that the settings for start values, for example, are correctly maintained.
DANGER
If you read back the data from the SIMATIC Station, you must ensure that hazardous
conditions cannot occur following a hot restart of the system or after configuration data
are downloaded.
Introduction
You can use various tools to archive project data.
Below, the PKZip (PKZip Server) program is used for archiving:
You can find the setup for PKZip on the SIMATIC PCS 7-DVD. PKZip is automatically installed
during the PCS 7 system setup.
You can start PKZip from the SIMATIC Manager.
Requirement
● A tool is installed for archiving project data (default: PKZip).
Archiving a project
1. In SIMATIC Manager, select the menu command File > Archive
The "Archive" dialog box opens.
2. Select the "Multiprojects" (or "User Projects") tab.
3. Click "Browse" and select the project you want to archive from the list.
4. Click "OK" to save your settings.
The "Archive - Select Archive" dialog box opens.
5. Make the following settings for the archiving:
– Select the drive and folder for the archive file from the "Save" drop-down list.
– In the "File name" box, enter the file name under which the archive file should be saved.
Recommendation:
Name the archive file of the project in such a way that it allows you to deduce the date
of the archiving from the name. Example: "yearmonthdayprojectname"; 091230name
6. Click "Save" to apply your settings.
The "Archive – Options" dialog box opens.
7. If you want to archive the project on floppy disks, select the size of the diskette.
For additional information about this dialog box, click "Help".
8. Click "OK".
The archiving process begins.
When the "Archive" dialog box closes, archiving is completed.
Write protection
Note
If you copy the project directly to the CD/DVD, all files and directories will be write-protected.
Before using the project again, you need to remove the "Read-only" file attribute for all files
and folders in the project.
Additional information
You can find information on the product version in the PCS 7 Readme on the SIMATIC PCS
7-DVD.
Requirements
● The tool that was used to archive the project is installed (default: PKZip).
● You set up all defaults required for the tool that is used to archive the project (for additional
information, refer to the "How to archive a project (Page 17)" section.
Note
You can find the setup for PKZip on the Process Control System; SIMATC PCS 7 DVD.
PKZip is automatically installed during the PCS 7 system setup.
Procedure
1. In SIMATIC Manager, select the menu command File > Retrieve.
The "Retrieve - Select Archive" dialog box opens.
2. Edit the following settings for the archive file:
– In the "Search in" list:
Enter the drive and folder where the project was archived.
– In the "File name" box:
Enter the name of the file where the project is archived.
3. Click "Open" to save your settings.
The "Select Destination Directory" dialog box opens.
4. Select the destination directory/project directory in the selection list.
5. Click "OK" to apply your settings.
The retrieval is finished when the "Retrieving" dialog box closes.
Introduction
You can store a multiproject in compressed form in an archive file in the same way as individual
projects or libraries. This can be done on a hard disk or on transportable storage media (such
as a ZIP disk).
If individual projects of a multiproject are stored on more than one PC in a network, you must
use the following programs to archive the multiproject:
PKZip
This program is installed automatically together with PCS 7 (STEP 7 add-on package).
Recommendation:
Archive the multiproject on an engineering server.
Archiving a multiproject
1. Select the multiproject in SIMATIC Manager.
2. Select the menu command File > Archive.
The "Archive" dialog box opens.
3. Select the "Multiprojects" tab.
4. Confirm the selected multiproject by clicking "OK" to save your entries.
5. Make the following settings for the archiving:
– In the "Save to" drop-down list:
Select the drive and folder.
– In the "File name" box:
Enter the name of the file in which the data are to be saved.
6. Click "Save" to apply your settings.
The "Archive – Options" dialog box opens.
7. If you want to archive the project on floppy disks, select the size of the diskette.
For additional information about this dialog box, click "Help".
8. Click "OK".
The archiving process begins.
When the "Archive" dialog box closes, archiving is finished.
Retrieving a multiproject
1. In SIMATIC Manager, select the menu command File > Retrieve.
2. In the next dialog box, select the archived multiproject.
3. Click "Open" to save your entries.
The "Select Destination Directory" dialog box opens.
4. Select the destination directory where the archive is to be unzipped. Click "OK".
The multiproject is retrieved.
After the retrieval operation, the "Retrieve" dialog box opens.
5. Click "OK".
The following is displayed in the "Retrieve" dialog box.
– The name of the retrieved project
– A prompt for opening the project
6. Click "Yes" as required to open the project, or click "No" to close the session.
Result
A subdirectory is automatically created in the destination directory you selected. The
subdirectory contains the following:
● By default: The name of the multiproject
● Individually: A unique directory name derived from the name of the multiproject
The following are placed in the subdirectory:
● Multiproject
● Projects contained in the multiproject
● Libraries, including the master data library
Once a multiproject is retrieved, all project directories of the multiproject are located on the
same level below this directory.
Introduction
If you have created a custom project library in PCS 7, we recommend that you archive it.
Perform the steps below for each library to be backed up.
Procedure
1. In SIMATIC Manager, select the menu command File > Archive.
The "Archive" dialog box opens.
2. Open the "Libraries" tab.
3. Click "Browse" and select the library you want to archive from the list.
Introduction
To visualize the process on the operator station you use faceplates, which show the plant
operator the measured values, operating limits, units, and operator texts of the blocks, for
example.
If you have changed operator or display texts in your blocks, we recommend that you back up
the operator and display texts.
Requirement
PCS 7 allows you to store all operator and display texts in every desired language. The only
requirement is that the language is installed in your project:
● The languages available in SIMATIC Manager can be displayed via the menu command
Options > Language for Display Devices.
● The number of languages offered is specified when Windows is installed (system
characteristics).
Procedure
1. Open the project in the SIMATIC Manager.
2. In the component view, select the master data library (or, if not available, the project folder).
3. Select the menu command Options > Manage Multilanguage Texts > Export.
The "Export User Texts" dialog box opens.
Introduction
PCS 7 enables you to create dynamic sequences in your OS project by creating custom
functions and actions. These functions and actions are written in ANSI-C language.
You must back up any project functions, standard functions, local actions, and global actions
that you have created or modified.
Additional information
● Online Help for WinCC Information System
Introduction
The configuration data of the PCS 7 operator station is automatically backed up when a
multiproject is archived. A separate backup is not required.
Backing up OS PC data
The OS configuration data are located on the PCS 7 engineering station. You therefore back
up OS server PCs or OS client PCs with an image. You can find information on this in the
section "Backing Up Data by Generating an Image File (Page 31)".
Additional information
● Manual Process Control System PCS 7; SIMATIC BATCH
Rule
NOTICE
The follow applies when a backup is running:
Operator input cannot be executed on the BATCH client where a backup is being generated.
Procedure
1. In BatchCC, select the menu command Options > Backup.
2. If there are non-archived batches in the project, you must acknowledge the message dialog
for non-archived batches. In this case, click "OK".
The "Save as..." dialog box opens.
3. Enter the name of the backup file ("...".sbb) in the "File Name" input field.
4. Select the storage location for your backup file from the "Save to" input field.
5. Click on the "Save" button.
The backup file is generated.
Import/Export Assistant
Using the IEA, you can export/import the following batch objects to/from a file with the extension
*.sbx:
● Libraries
● Basic recipes
● Formula categories
The export is supported in SIMATIC BATCH V6.1 or higher.
Note
For reasons of performance, you should only export/import one recipe to/from a file when
exporting/importing large recipes.
Note
All referenced objects such as libraries, materials and formula categories are included in the
export.
All formulas that belong to a formula category are included in the export.
Additional information
● SIMATIC BATCH Manual
Introduction
You can restore the data from a backup file and update the Batch process cell in the SIMATIC
BATCH Control Center (BatchCC).
Requirement
No Batch process cell is available in the BatchCC.
Reading a backup
1. In BatchCC, select the menu command Options > Restore.
The "Restore" dialog box opens.
2. Select the storage location for the backup file ("...".sbb).
3. Click "Open".
The backup file is loaded.
Result
In BatchCC, the data from the backup file is entered into the batch database and made
available again to the plant.
Long-term archive
You archive batches in long-term archives in BatchCC. Long-term archives are used for long-
term storage of batch data in accordance with the FDA.
Rules
● Only completed batches can be archived.
● Data from long-term archives cannot be used to restore defective batch data or batch
structures.
Requirement
The archiving technology is preset in BatchCC.
● Technology "Directory":
The archive data is saved to a shared network folder. SIMATIC BATCH does not use any
specific login or password settings for access to this folder.
● Technology "SQL Server":
The archive data is saved to an SQL database. Login and password are mandatory for this
technology; a specification of the domain is not used.
● Technology "FTP Server":
The archive data is saved to an FTP Server. Login and password are mandatory for this
technology; a specification of the domain is only required if the login is assigned to a domain.
For additional information, refer to the SIMATIC BATCH online help.
Additional information
● Manual Process Control System PCS 7; SIMATIC Route Control
Introduction
This section describes the separate backup of partial routes from SIMATIC Route Control to
a file.
Note
You can back up the partial routes with the offline project data from SIMATIC Route Control.
The interface blocks are part of the PCS 7 project and are backed up during the archiving of
the PCS 7 project.
Creating a backup
1. Select the multiproject/project in the SIMATIC Manager.
2. Select the Options > SIMATIC Route Control> Engineering menu command.
The "Route Control Engineering - ..." dialog box opens.
3. Select the menu command Options > Export/Import CSV > CSV Export/Import Wizard ....
The "Wizard: CSV file data exchange (Export/Import)" opens.
4. Check the path in the "Directory" input box.
5. In the "Direction" group, activate the check box "RC project engineering >> CSV file(s)
(Export).
6. Click "Continue".
7. Select all check boxes.
8. Click "Continue".
9. Click "Finish".
The files are exported.
Additional information
● Manual Process Control System PCS 7; SIMATIC Route Control
Introduction
You restore partial routes from SIMATIC Route Control from a backup file.
Importing a backup
1. Select the multiproject/project in the SIMATIC Manager.
2. Select the Options > SIMATIC Route Control> Engineering menu command.
The "Route Control Engineering - ..." dialog box opens.
3. Select the menu command Options > Export/Import CSV > CSV Export/Import Wizard ....
The "Wizard: CSV file data exchange (Export/Import)" opens.
4. The dialog box "Wizard: CSV file data exchange (Export/Import)" opens.
5. Check the default path set in the "Directory" input box.
6. In the "Direction" group, activate the check box "CSV file(s) >> RC project engineering
(Import).
7. Click "Continue".
8. Select all check boxes.
9. Click "Continue".
10.Click "Finish".
The project engineering data are imported.
Additional information
● Manual Process Control System PCS 7; SIMATIC Route Control
Introduction
It is advisable to generate an image file of the installation in order to backup partitions and
hard disk data (e.g. after reinstallation).
Image file
An image file maps all of the data on the backed-up medium (hard disk, logical drives). It is
used to back up data on partitions or hard disks. Many of the software packages that can be
used to generate image files also offer data compression.
Boot partitions are included in the backup. This enables you to save all the PC settings
including the Windows system settings.
All the data of a PC can usually be restored from an image file within a short amount of time
(e.g., 2 GB data takes approx. 10 minutes). In the event of a fault, you can restore the complete
PC installation.
Rules
● You must use the same hardware to restore data.
● Note the following settings of the hard disk for the image file
(you can find additional information on this in the section "Managing the operating system
(Page 91)"):
– Partition size
– Formatting of partition or hard disk (e.g., NTFS, FAT32)
● Authorizations and license keys cannot be included in the backup.
● The image software must be compatible with the current operating system.
Basic procedure
1. Move the authorizations and license keys to another medium (diskette, partition, etc.) before
generating the image.
2. Follow the instructions of the manufacturer of the image software when creating an image.
Additional information
● Documentation relating to the image software used
Overview
Introduction
In this section, a hardware update refers to changing the firmware in SIMATIC modules.
Updating the firmware of a SIMATIC module is referred to as a "firmware update" in the
following.
A firmware update includes the following:
● Function upgrades
● Operating system enhancements
Released modules
You can find the firmware versions for modules released of a particular PCS 7 version in the
"PCS 7 - Released Modules" documentation that corresponds to the version in question.
CPU 416-2
X 7
8 9
416-2XK02-0AB0
V3.0.2
● When a firmware update is delivered you obtain a label showing the current firmware
version which you can paste over the displayed label. After having completed the firmware
update, replace the module label accordingly to identify the valid FW version. This will
ensure uniformity in the plant documentation.
Modules that cannot be updated:
● If only the manufacturer can perform changes to a module, only the product version is
shown on the housing of the module (indicated by a cross; in the following example: product
version 10).
Example:
PS 407 10A
X 11
12 13
407-0KA01-0AA0
Note
The update file may be supplied in an executable, self-extracting file (.exe). When you want
to perform consecutive updates for different module types of module versions, you must unzip
the update files in separate folders for the different CPUs as follows:
● Type of module
● Product version
● Firmware version
Overview
The sections below describe topics related to hardware updates:
● Adjustments after a hardware change (Page 35)
● Updating a SIMATIC S7 CPU (Page 35)
● Updating an interface module IM xxx (Page 39)
● Updating a CP xxx (Page 41)
● Working with GSD files (Page 48)
Basic procedure
A change to the hardware always requires a change to the software. Configure the hardware
changes in HW Config. Compile the changes and then download the data to the CPU. You
can then physically replace, remove or add the modified hardware.
Procedure
1. Open the project (the AS) in HW Config.
2. Drag the object (such as the CPU: Type, Firmware Version x.x) from the hardware catalog
and drop it into the appropriate slot in the AS configuration table.
The following message appears: "Do you want to exchange component ... with
component ...?"
3. After verification, click "Yes" to confirm.
4. Select the menu command Station > Save/Compile.
You can also perform the compiling during the subsequent work.
Preparation
Compare the type and manufacture date of the modules you are using with the information in
the document PCS 7 Released Modules.
If replacement of the CPU is required, contact your Siemens representative.
Note
In a fault-tolerant PCS 7 system, the (S7-400H) CPUs must always have a uniform hardware
version and the same firmware version.
You always need a memory card for a firmware update for older CPUs.
3.3.3.1 How to perform a firmware update for the CPU (as of V5.0)
You are provided with several files (*.UPD) with the latest firmware to update the firmware of
a CPU. Download these files to the CPU. You do not need a memory card for the online update.
However, it is still possible to perform a firmware update with a memory card.
Preparation
Compare the type and manufacture date of the modules you are using with the information in
the document PCS 7 Released Modules.
If replacement of the CPU is required, contact your Siemens representative.
Requirements
● STEP 7 V5.3 or higher is installed on the programming device or PC.
● The update file for the firmware update is available on the programming device/PC.
● The CPU, whose firmware is to be updated, must be accessible online, for example, via
PROFIBUS, MPI or Industrial Ethernet. The files containing the latest version of the
firmware are available in the file system of your programming device or PC. A folder may
only contain the files for one firmware version.
Note
For CPUs with a PROFINET interface, you can update the firmware via Industrial Ethernet
on the PROFINET interface. Updating via Industrial Ethernet is significantly faster than
MPI or DP (depending on the configured baud rate).
You can update the firmware of the other CPUs via Industrial Ethernet, if the CPU is
connected to Industrial Ethernet via a CP.
Procedure in HW Config
To update the firmware of a CPU, proceed as follows:
1. Open the station with the CPU to be updated in HW Config.
2. Select the CPU.
3. Select the menu command PLC > Update Firmware.
4. Select the path to the firmware update files (CPU_HD.UPD) by clicking the "Browse" button
in "Update Firmware" dialog.
Once you have selected a file, information about which modules and which firmware
versions are suited for the file is displayed in the lower fields of "Update Firmware" dialog.
5. Click "Run".
STEP 7 checks whether the selected file can be interpreted by the CPU and loads the file
to the CPU if the result is positive. If the operating state of the CPU must be changed to do
this, you are prompted by dialogs to take action.
Note
Protecting the update process
There a digital signature, which is checked during the update of the CPU to protect the
firmware update. If an error is detected, the old firmware remains active and new firmware is
discarded.
3.3.3.2 How to perform a firmware update for the H-CPU (as of V4.5)
The firmware version can be changed using the online functionality as of firmware version
V4.5.x.
● Firmware update of an H system in RUN
● It is not possible to downgrade in RUN
Downgrading an H-CPU
If a CPU in your S7-400H, fails, order a new CPU with the same number. This comes with the
latest firmware version. This firmware can be higher than the predecessor CPU. In this case,
the new CPU must be set to the older firmware version.
1. Insert the new CPU into your automation system.
Note
Do not connect the fiber-optic cable to the CPU of an H system.
5. Download this file to the CPU. The new CPU now has the same firmware version as the
previously used CPU.
6. Now connect the fiber-optic cable for the CPU of an H system.
Switch the system to the "Redundant" operating mode by starting this CPU.
You can then upgrade both CPUs of the H system to the latest firmware in the "Run" state.
Introduction
The interface modules (IM) ) are the interface to the PROFIBUS DP in PCS 7.
Preparation
● Compare the type and version of the interface modules you are using with the information
in the document PCS 7 Released Modules.
● If replacement of the interface module is required, contact your Siemens representative.
● A firmware update is possible for some interface modules. You will find the procedure in
the section "How to perform a firmware update of an IM (Page 40)" below.
Note
You can perform a firmware update of the interface modules for SIMATIC 400H station with
redundant interface modules during runtime.
Introduction
This section provides a description of the update of the firmware for interface modules
(Interface Module (IM)) via Industrial Ethernet.
Requirements
The following is required to perform the update via Industrial Ethernet:
● STEP 7 V5.3 or higher is installed on the programming device or PC.
● The update file for the firmware update is available on the programming device / PC.
● The CP 443-1 is routing-capable (check in HW Config: Properties of the CP > brief
description "Routing" is listed).
● The files containing the current (new) version of the firmware is available in the file system
of your programming device or PC.
● The IM has been integrated in your PCS 7 project.
Procedure
1. Open SIMATIC Manager.
2. In the component view, select the SIMATIC station in which the IM is located.
3. Double-click the "Hardware" object in the detail window.
HW Config opens.
4. Select the IM whose firmware you want to update.
5. Select the menu command PLC > Update Firmware.
The "Update Firmware" dialog box opens.
6. Make the settings in accordance with the table below.
7. Click "Execute". The firmware is updated.
Setting Action
Location of the In the "Firmware File" group, specify the folder where you placed the file for
firmware file the firmware update. If you want to search, you can use "Browse" to open
Explorer.
Activation of "new" Use the "Activate firmware after download" check box to specify when the
firmware "new" firmware is to be activated as follows:
● Select the "Update firmware after download" check box if the IM is to
perform an automatic RESET after the new firmware was successfully
loaded. The new firmware is active following the restart.
● Clear the "Update firmware after download" check box to prevent the IM
from performing a RESET reset the new firmware was loaded. The "new"
firmware becomes active only after the power supply has been switched
off.
Note
After the firmware update of the IM has been successfully completed, update the identifier of
the firmware version. You can find information on this in the section "Hardware Updates
(Page 32)".
Introduction
In PCS 7, communication modules (CPs) are used to connect a SIMATIC station to bus
systems. By updating the firmware, you can enhance the CP properties without replacing the
hardware.
Overview
The sections below describe procedures for updating firmware:
● CP 341 firmware update (Page 42)
● CP 443-1 firmware update (Page 43)
● CP 443-5 Extended firmware update (Page 45)
Introduction
This section explains how to update the CP 341 firmware.
Preparations
● Compare the type and version of the modules you are using with the information in the
document PCS 7 Released Modules.
● If you need to replace the CP, contact your Siemens representative.
Procedure
1. Open SIMATIC Manager.
2. In the component view, select the SIMATIC station in which the CP 341 is located.
Note
Before deleting the older firmware, the CP checks if the order number of the firmware to be
downloaded is permitted.
Result
The new firmware is installed in the operating system memory of the CP. The progress of the
installation is indicated by a progress bar and a percentage under "Done". Once the firmware
update is complete, the module is ready for immediate operation.
Preparation
● Compare the type and version of the modules you are using with the information in the
document PCS 7 Released Modules.
● If you need to replace the CP, contact your Siemens representative.
Note
If the NCM S7 diagnostics do not start, the connection between the programming device/
PC and the CP 443-1 is faulty. Correct the fault.
5. Note the MAC address setting of the CP 443-1 under "Industrial Ethernet".
NOTICE
Note the following:
● A warning message appears before the download operation begins if an incorrect CP type
has been inadvertently addressed. The firmware can nevertheless be downloaded to an
incorrect CP type if the message is acknowledged.
● With the next steps, all data on your CP are deleted and cannot be recovered!
● Do not cancel a download operation once it is started. The CP may no longer be usable
if you do this and you will have to send it in for repair.
1. In the Siemens SIMATIC programs Start menu, select: STEP 7 > NCM S7 Industrial
Ethernet > Firmware Loader.
The dialog box of the firmware loader opens.
2. Click "Continue".
3. In the "Step 1" dialog box, set the path for the update file:
– Click "Browse".
– Use "Select file" to select the desired file ("<drive>:\TEMP\Cp4435ba.fwl", for example).
– Click on the "Open" button.
4. Click "Continue".
Note
The access point must be set to "S7ONLINE CP xxxx(ISO)".
Note
If a CP does not respond to a load procedure via the configured MAC address, load the CP
again via the imprinted address.
Preparation
● Compare the type and version of the modules you are using with the information in the
document PCS 7 Released Modules.
● If you need to replace the CP, contact your Siemens representative.
Note
Ensure the following for the firmware update of the CP 443-5 Extended:
● If you want to connect devices that operate with PROFIBUS standard DPV1 to your
PCS 7 system after conversion, you might have to replace the hardware (e.g. CP type:
6GK7 443-5DX03-0XE0 with firmware V5.1 or higher).
● This hardware requires special device drivers.
For information on generating the device drivers, refer to the Process Control System
SIMATIC PCS 7; Programming Instructions, Creating Blocks for PCS 7 documentation.
NOTICE
Note the following:
● With the next steps, all data on your CP are deleted and cannot be recovered!
● Do not cancel a download operation once it is started. The CP may no longer be usable
if you do this and you will have to send it in for repair.
1. In the Siemens SIMATIC programs Start menu, select: STEP 7 > NCM S7 > Firmware
Loader.
The dialog box of the firmware loader opens.
2. Click "Continue".
3. In the "Step 1" dialog box, set the path for the update file
– Click the "Browse" button.
– Use "Select file" to select the desired file ("<drive>:\TEMP\Cp4435ex.fwl", for example).
– Click on the "Open" button.
4. Click "Next" to confirm the next three dialog boxes until you reach "Step 4: Perform Load
Operation".
5. Read the information in the dialog box for "Step 4: Perform Load Operation".
In the table below you will find the download operation states that are displayed.
6. Switch off the power supply of the rack.
7. Click "Cancel" to close the dialog box.
8. Reestablish the original PROFIBUS connection.
9. Switch on the power supply for the module.
The CP performs a self-test and is then ready for operation.
Introduction
STEP 7 Version 5 applies a more stringent test to the GSD files (GSD = Device Master
dataFfile). Syntax errors or non-interpretable errors can occur with GSD files from an older
project, however.
Improved help texts are provided for syntax errors and GSD problems starting with STEP 7
Version 5.1 SP2.
If the following measures are not successful, contact the device manufacturer and request a
new GSD file. You can find solutions for some errors in this table:
Troubleshooting
Information
● For additional information on the update of the PCS 7 software, refer to the
– Process Control System PCS 7; Software update without utilization of new functions
– Process Control System PCS 7; Software update with utilization of new functions
● For additional information on updating redundant operator stations at runtime, refer to the
PCS 7 Process Control System; Fault-Tolerant Process Control Systems manual, "Guide
to updating a redundant OS at runtime" section.
A corresponding brief overview is provided in the"Updating the PCS 7 OS in runtime
(Page 50)" section of this documentation.
● Information on installing hot fixes are included in the respective software package with the
hot fix.
Note
Note that you must use the appropriate hardware in order to take advantage of features in
new software versions.
You can find information on the minimum requirements for PC stations in PCS 7 in the manual
PCS 7 Process Control System; PC Configuration and Authorization.
Introduction
You have the option of updating a redundant PCS 7 OS configuration at runtime in order to
adapt the "older" version of your current PCS 7 process control system to a "newer" PCS 7
version.
Updating the PCS 7 OS involves the following tasks:
● Preparatory measures
● Installation of the "new" software
● Commissioning measures required to adapt your existing PCS 7 process control system
Updating the PCS 7 OS during running operation offers the following benefits:
● Operation of the PCS 7 system is not disrupted.
● The AS does not enter STOP mode.
● The automation process can still be operator controlled and monitored.
Requirements
Several requirements must be fulfilled to ensure that the status of a PCS 7 system can be
diagnosed effectively. The most important requirements are:
● Diagnostics are enabled for the components.
● Diagnostic options were activated during configuration
Checking PC components
● You check PC components using software tools of PCS 7 (such as a maintenance station
or PC DiagMonitor) and the operating system.
● The following configuration actions assist you in diagnosing PC components:
Additional information
● Online help PC DiagMon
Introduction
The message system and diagnostic options of PCS 7 help you to assess the system status.
You can find information about the PCS 7 message concept in the following sections:
● PCS 7 message system (Page 54)
● Origin of a message (Page 55)
● Determining the source of a message (Page 56)
● Evaluating and understanding messages (Page 57)
Basic terms
Some basic terms used in the PCS 7 message concept are defined in the following:
Term Definition
Events Events lead to a change in the data status in the automation system.
For example, an event can be the following:
A bit is modified in an automation system by a change to a process value, or after a
specified limit value was reached.
The configuration determines which events trigger a message.
Messages Messages are triggered by events or by a message frame. PCS 7 has the following
message types:
● Operator input messages
● Process messages
● Operating messages
● Process control messages and system messages
Error and In PCS 7, the PCS 7 Operator Station operator control and monitoring system is also
fault used to display errors and faults in the process.
● Error: component (object) status that does not disturb the process (for example,
defective display lamps).
● Fault:component (object) status that interferes with the process (for example, a
defective motor).
Additional information
You can find detailed information about the message system as follows:
● In the WinCC Information System:
Select the Start menu command under the SIEMENS SIMATIC products WinCC
Information System, and look under "System Overview > How WinCC Works >
– Message system of a PCS 7 OS
– Archive system of a PCS 7 OS
– Reports system of a PCS 7 OS
● In the configuration manual PCS 7 Process Control System; Operator Station, in the section
"Settings for the alarm system"
● In the online help for SIMATIC BATCH, you will find the following information under "Batch
Data Management":
– Batch reports
– Archiving batches
● In the SIMATIC Route Control online help, you will find the following information under
"Operator Control and Monitoring":
– Route log
Note
Be aware of the accuracy of the message system.
If events are recorded within one scan cycle, they can appear in the wrong order in the
message list.
Remedy: You can find information about this in the function manual Process Control System
PCS 7; High-precision Time Stamping.
Additional information
You can find detailed information on configuring messages in the following manuals:
● Configuration manual Process Control System PCS 7; Engineering System
● Configuration manual PCS 7 Process Control System; Operator Station
Message path
Messages can originate in different locations in PCS 7 depending on the configuration. Each
message is given a time stamp. The event which causes a time stamp to be assigned to a
message depends on the place where the message has originated. Irrespective of where they
originate, all messages are handled in the same way regarding how they are displayed and
archived on the PCS 7 OS.
2ULJLQRID3URFHVV0HVVDJH
3URFHVVVLJQDOIDXOW\
$6&3
&38
3ODQW%XV
26&3
0HVVDJH
Figure 5-1 The letter "A" in the picture symbolizes an alarm message in PCS 7.
Additional information
You can find information on configuring messages in the following documentation:
● Configuration manual Process Control System PCS 7; Engineering System
● Configuration manual Process Control System PCS 7; Operator Station
For information on configuring messages with enhanced time stamp accuracy, refer to the
PCS 7 Process Control System; 10 ms Time Stamping function manual.
Procedure
1. Enable the message list by clicking
2. "Activate/Deactivate Autoscroll".
3. In the message list, select the message for which you need additional information.
4. Click "Open Infotext".
5. Note the message number and use "Alarm Logging" to determine the source of the
message.
5.5.1 Introduction
Overview
You can find important information for understanding the PCS 7 message concept in the
following sections:
● Message types in message lists and archives (Page 58)
● Target groups of messages (Page 58)
● Message lists in process mode (Page 59)
● Overflow of message buffer (Page 60)
● Message priorities (Page 61)
● Influencing messages (Page 62)
Term Definition
Operator Input Operator Input messages are generated when an operator controls process
messages variables, for example, changes the operating mode of a controller.
● SIMATIC PCS 7 generates operator input messages automatically if you
use faceplates prepared from the libraries.
● If you configure faceplates according to the programming guide Process
Control System PCS 7; Creating Blocks for PCS 7, PCS 7-conforming
operator input messages are also available for your own blocks.
Process messages Process messages signal process events that take place in the automated
process, such as limit value violations and operating messages.
● Process messages are predefined for the blocks and therefore do not
need to be configured. Message texts and message priority can be
modified as needed in the object properties for the CFC blocks. These
modifications can also be made centrally in the process object view or
by means of import/export operations.
● Operating messages are a subgroup of process messages. They signal
process values that can be used to evaluate a process-related
component, such as an operating hours counter.
Process control Process control messages are generated when SIMATIC PCS 7 detects and
messages signals errors in components within its own system. Such errors range from
failure of a component to a wire break message for a connected I/O signal.
Process control messages are generated by the driver blocks in PCS 7 and
do not need to be configured.
System messages
System messages are messages that are triggered by self-diagnostics of a device. System
messages are usually included in the process control messages or process messages
(operating messages).
Target Groups
Message lists
PCS 7 places incoming messages in message lists. The message is available in different alarm
lists, depending on the event source and on the alarm status.
The following messages lists are available by default. You can modify these standard message
lists or create additional message lists.
List Content
Incoming alarm list The incoming alarm list contains the alarms which require acknowledgment,
however, which are still pending acknowledgment or deactivation.
Acknowledged The acknowledged alarm list contains the acknowledged process alarms.
alarm list
Outgoing alarm list The outgoing alarm list contains the alarms flagged as "Outgoing". Those alarms
are no longer active, but are not yet acknowledged.
History list The history list provides a view of the alarm log which contains all alarms, except
the operator log.
Process control list The process control list provides a view of the alarm log, filtered according to
process alarms (and comparable ones).
Example: Rack failure
Process alarms are also displayed in the following lists:
● Incoming alarm list
● Acknowledged alarm list
● Outgoing alarm list
● History list
Operation list The operation list provides a view of the alarm log. The operation list contains the
operator log.
Examples:
● The operator has set the controller setpoint to 5 bar
● The operator has activated the drive
The following figure illustrates the path a message takes through the message lists.
$/$50/2*
,1&20,1*DODUP
,1&20,1*$/$50/,67
$OOXQDFNQRZOHGJHG
DODUPV
$FNQRZOHGJPHQW 287*2,1*DODUP
$&.12:/('*(' 287*2,1*$/$50/,67
$/$50/,67
$FNQRZOHGJHGDFWLYH $ODUPVFOHDUHGEHIRUH
DFNQRZOHGJPHQW 9LHZVRIWKH
DODUPV
DODUPORJ
ILOWHUHGOLVWV
287*2,1*DODUP $FNQRZOHGJPHQW +,6725</,67
352&(66&21
752//,67
2SHUDWLRQ 23(5$7,21/,67
Alarm log
All alarms, operator information and status changes are saved to the alarm log. You can use
the filters to read specific information from the alarm log.
Note
If events that trigger messages change status in very quick succession, this can trigger a
message surge. The overview of the plant status can no longer be sufficiently ensured.
Additional information
You can prevent a message surge by activating the "Messaging Triggered by
Acknowledgment" function. You can find information on configuring in the configuration manual
Process Control System PCS 7; Engineering System.
Rules
● Message priorities can only be specified if you defined the message number range as
"Unique for Entire CPU".
● In PCS 7 OS, the unacknowledged message with the highest priority is always displayed
in the message row above the overview. If multiple messages have the same priority, the
most recent message is displayed here.
● You can filter the list according to priority.
Additional information
You can find information about configuring message priorities in the configuration manual
Process Control System PCS 7; Operator Station.
Options
PCS 7 offers the following options for influencing messages:
● Message suppression
– You can suppress individual block messages with the CFC configuration.
– In process mode, you can suppress individual messages directly in the faceplate using
the "Suppress message" check box.
● Locking and releasing messages for blocks and OS areas
Locking (and releasing) messages for blocks and OS areas is used when the plant operator
wants to lock all messages of an interrupt-capable block or OS area.
● Hiding and displaying messages
You hide individual messages to reduce the number of messages displayed in process
mode. The messages are entered in a history list. The following variations are used to hide
and display messages in PCS 7:
– Manual hiding and showing of messages in process mode
– Automatic hiding and displaying of messages in process mode
Additional information
● Configuration manual Process Control System PCS 7; Operator Station
● Configuration manual Process Control System PCS 7; Engineering System
● Manual Process Control System PCS 7 OS Process Management
Note
If the components you are using do not have diagnostics capability, only secondary faults
are signaled.
– Use diagnostic tools to analyze the fault. You can achieve the following with the
diagnostic tools:
You can find the cause of a fault.
or
You can verify the presumed cause of a fault.
– You can find the following information in the section "Diagnostics for PCS 7" for support:
The diagnostic tools available for PCS 7
Applications for the various diagnostic tools according to subsystem
Note
Make use of skilled experts if you cannot find a solution to your problem based on
available information. For information on this topic, refer to the section "Additional
support (Page 11)" of this documentation.
NOTICE
Note the following information:
● The following actions may only be carried out by qualified personnel and in compliance
with valid statutory provisions and plant-specific rules:
– Changes to the configuration
– Replacement of and changes to components
● Bear in mind that uncharacteristic situations can occur in the plant after activation.
Make sure the activation of components and secondary systems is carefully directed.
Examples of causes
Introduction
Overview
You support the work of service experts by providing them with information:
● Service experts need information about your plant and the faulty system in order to provide
quick support.
For additional information, refer to the "Plant documentation (Page 65)" section below.
● Service experts need information from the diagnostic buffer of the CPU in order to analyze
the cause of a CPU fault.
For additional information, refer to the "How to read the CPU diagnostic buffer (Page 66)"
section below.
● A memory dump facilitates the analysis of the cause of the CPU fault.
For additional information, refer to the "CPU fault - preparing diagnostics (Page 66)" section
below.
● Backing up the diagnostics files facilitates the analysis of an OS fault.
For additional information, refer to the "How to back up the diagnostic data of the PCS 7
OS (Page 68)" section below.
● You can take all measures necessary to enable remote diagnostics via "remote access".
For additional information, refer to the "Remote diagnostics of a PCS 7 system (Page 69)"
section below.
Requirement
The CPU is in STOP mode.
Procedure
1. Select the faulty CPU in the SIMATIC Manager.
2. As of firmware version V4.0:
Select the menu command CPU > Save service data.
Specify the storage location and name. Save the files.
3. Select the menu command PLC > Diagnostics/Settings > Module Information.
The "Module Information - Online" dialog box opens.
4. Select the "Stacks" tab and read out the following system memory:
– Block stack (B stack)
– Interrupt stack (I stack)
5. Provide these data to the service engineers.
Introduction
The following information is important for analyzing a CPU fault:
● Information on the affected CPU
● Information or actions in the event of a fault
Rules
WARNING
Note the following:
● Only trained service employees should be authorized to work on the process control
system.
● Always observe the plant-specific rules and government regulations when making
changes to a system.
● Observe the plant-specific boundary conditions and adjust the work accordingly.
● Always bear in mind that changes in a system can impact other sections of the system.
Note
A constantly updated list of all module information facilitates troubleshooting in the event of
a fault and reduces the time needed for correcting the fault.
● If the STOP LED is lit, read out the diagnostic buffer. For additional information on
procedures, refer to the "How to read the CPU diagnostic buffer (Page 66)" section
Save the diagnostics buffer to a HEX file and to a TXT file!
● These data can be analyzed by trained service engineers. They contain information about
the cause, for example:
– I/O error
– Synchronization error with an H-CPU
● If the possibility exists that a hardware error in the I/O caused the CPU to switch to STOP
mode, save the diagnostic buffer of the relevant module and the associated bus interface
module (for example, CP 443-5).
● Generate a memory dump.
All LEDs are off or are flashing
You recognize the "CPU defective" status by the following LED displays on the front of the
CPU:
● All LEDs are flashing.
● All LEDs are off, even though the power supply is switched on.
For additional support, contact your Siemens representative or Technical Support. Have the
"information in the event of a fault" indicated above ready.
Basic procedure
We recommend that you back up the diagnostic files for analysis of the cause of the OS fault
by experts.
Note
Once the diagnostic files are backed up (not in diagnostic folder), you can delete the
content of the diagnostic folder. In this way, you avoid keeping old information in the new
diagnostic files.
If the same error occurs the next time you start WinCC, make an additional backup to help
the experts. Only a few messages will need to be analyzed in this backup.
(VWDEOLVKLQJDFRQQHFWLRQYLDWKH
ಮ1HWPHHWLQJಯSURJUDP
&XVWRPHU6XSSRUW 3&6WDWLRQLQ
6HUYLFH3HUVRQDO 3&63ODQW
7&3,3RU0RGHP 7&3,3RU0RGHP
Transmission paths
The data can be transmitted along the following routes:
● Telephone line (modem)
● TCP/IP connection (system-internal network connection)
Security requirements
If you wish to perform remote diagnostics in a PCS 7 plant, you need to protect the this plant
against unauthorized access.
Several measures are required to realize a security concept. Optimal protection is only
provided with all security measures as a whole.
For additional information, refer to the whitepaper Safety concept in PCS 7 and WinCC - Base
document.
6.2.7 Interactive operator control and monitoring with the OS Web Option
Interactive operator control and monitoring of a PCS 7 plant using the OS Web Option
Use the OS Web Option for interactive control and monitoring of a PCS 7 plant.
For additional information, refer to the Process Control System PCS 7; OS Web Option manual.
The figure below shows how the OS Web Option (OS Web server, Web client) can be used in
a PCS 7 plant.
:HEFOLHQW
6RIWZDUH
3&6b:HEFOLHQW
,QWUDQHW,QWHUQHW
26FOLHQW:HEVHUYHU
6RIWZDUH
3&6:HE6HUYHU
/LFHQVHV
6HUYHUOLFHQVHV
26FOLHQW 26FOLHQW
7HUPLQDOEXV
3ODQWEXV
$XWRPDWLRQ
6\VWHP$6
Transmission paths
The data can be transmitted along the following routes:
● Telephone line (modem)
● TCP/IP connection (system-internal network connection)
● Internet
Security requirements
If you use the OS Web Option in a PCS 7 plant, you must protect this plant against unauthorized
access.
Several measures are required to realize a security concept. Optimal protection is only
provided with all security measures as a whole.
For additional information, refer to the whitepaper Safety concept in PCS 7 and WinCC - Base
document.
Disclaimer of liability
WARNING
Siemens assumes no responsibility for inappropriate use of the instructions provided in this
documentation or any consequences that might result for the customer.
WARNING
Note the following:
● Only trained service employees should be authorized to work on the process control
system.
● Always observe the plant-specific rules and government regulations when making
changes to your system.
● Observe the plant-specific boundary conditions and adjust the work accordingly.
● Always bear in mind that changes in a system can impact other sections of the system.
Introduction
The message system and diagnostic tools of PCS 7 help you to assess the status of your
system. You can find information about the diagnostic tools In the following sections.
This description illustrates the capabilities of the diagnostic tools so that you can apply them
to your individual requirements.
● You will also find information on the fields of application for diagnostic tools.
● You will learn how to call up a diagnostic tool.
● Since malfunctions can have a variety of causes and because procedures for using the
diagnostic tools are already available in the online help, a detailed description is not
provided here.
Diagnostics
Diagnostics refers to all activities intended to:
● Ascertain the status of a system
● Find errors and faults as early as possible and identify their cause
Diagnostic messages
Diagnostic capabilities are used to analyze the system status and to determine the causes of
faults.
Overview of diagnostic tools
You can find information on using diagnostic tools, grouped according to areas of application,
in the following sections:
● Full Diagnostics Using the Maintenance Station (Page 75)
● Diagnostics for PC user settings (Page 77)
● Diagnostics for PC Components (Page 77)
● Diagnostics for Network Connections (Page 79)
● Diagnostics during Configuration (Page 80)
● Diagnostics for the CPU (Page 81)
● Diagnostics for Modules (Page 81)
● Diagnostics for PROFIBUS DP (Page 82)
● Diagnostics on PROFIBUS PA (Page 83)
● Diagnostics on PROFINET
● Diagnostics on Foundation Fieldbus
● Diagnostics for the OS (Page 84)
● Diagnostics for the BATCH station (Page 85)
● Diagnostics for the Route Control station (Page 86)
● Diagnostics for the time of day (Page 86)
For many components, you will find displays on the front panel indicating the status of the
component and any errors. Analyzing these displays enables you to obtain information without
intervening in the system. The additional product manuals you will need for this analysis can
be found in the section "Diagnostics for Hardware Displays (Page 87)".
Introduction
With PCS 7 V6.1 and higher, a PCS 7 system can be fully diagnosed with the help of the
maintenance station. The maintenance station is an operator station that is specially configured
and assigned parameters for use in diagnostic and maintenance functions.
We particularly recommend the use of a maintenance station in medium and large PCS 7
systems.
Maintenance station
With the maintenance station, PCS 7 enables you to call up information on the states of all
PCS 7 components on diagnostics screens which are hierarchically structured. As part of this
process, the data of a component are analyzed using the available online functions of the
associated tools. You can access ES data from the diagnostics screens (can be controlled via
access protection mechanisms).
Screens for process-control diagnostics can be generated automatically for the entire PCS 7
system and made available on the maintenance station. The top level forms an overview
screen for the entire system.
Diagnostics options
You will find information on the states of individual PCS 7 components with diagnostic capability
on the maintenance station's special diagnostics screens.
Additional information
● You will find a description of how to configure a maintenance station in the configuration
manual PCS 7 Process Control System; Maintenance Station.
● You will find a description of how to use the maintenance station in process mode in the
manual PCS 7 Process Control System; PCS 7 OS Process Control.
● You can find information on the configuration of a PCS 7 system with a Web Diagnostic
Server and Web Diagnostic Client in the manual PCS 7 Process Control System; PCS 7
OS Web Option.
Overview
Overview
Overview
Connections to intelligent field devices SIMATIC PDM (Page 114) In SIMATIC Manager: Options > Set PG/PC
Interface
PC Ethernet modules NCM S7 Industrial Ethernet In the Siemens SIMATIC programs Start menu:
(Page 98) STEP 7 > NCM S7 Industrial Ethernet >
Diagnostics
Status of configured channels and WinCC - Channel Diagnosis In the Siemens SIMATIC programs Start menu:
their connections to the SIMATIC (Page 104) WinCC > Tools > Channel Diagnostics >
station "Channels/Connections" tab
Overview
Overview
Overview
Overview
Overview
Overview
Overview
Overview
Overview
Overview
Overview
Overview
Many components have displays indicating the component status and errors. Analyzing these
displays enables you to obtain information without intervening in the system.
Components You can find information about diagnostic options in the following manuals and
sections:
Power supply module Reference manual SIMATIC;
S7-400 Programmable Controller; Module Specifications
● Backup battery (optional)
● Error messages by means of LED displays
● Operator control and display elements
Central module for Reference manual SIMATIC;
S7-400 S7-400 Programmable Controller; CPU Data
CPU ● Monitoring functions of the CPU
● Status and error displays
● Operating mode switch
CP 441 Manual SIMATIC;
CP 441 Point-to-Point Communication - Installation and Parameter
Assignment
● Diagnostics for CP 441
CP 443-1 Device manual S7 CPs/Part B4;
Description of CP 443-1
● Displays and operating mode switch
CP 443-5 Extended Device manual S7 CPs/Part B4;
Description of CP 443-5 Extended
● Displays and operating mode switch
S7-300 I/O modules Reference manual SIMATIC;
S7-300 Programmable Controller; Module Specifications
● Diagnostic data for the signal modules
Additional information is available in the ET 200M Signal Modules for Process
Automation () manual or in the
ET 200M distributed I/O device HART analog modules () manual.
S7-300 fail-safe signal Manual SIMATIC;
modules Programmable Controller S7-300; Fail-safe Signal Modules
● Diagnostics of F-SM errors
● Properties, front view, connection and block diagram
S7-300 Manual SIMATIC;
ex I/O modules Programmable Controller S7-300, ET 200M s
ex I/O modules
● Digital input module: Properties
● Diagnostics for analog modules
● Module view and block diagram
Components You can find information about diagnostic options in the following manuals and
sections:
ET 200M Manual SIMATIC;
ET 200M Distributed I/O; Commissioning and Diagnostics
● Diagnostics by means of LED display IM 153-1, IM 153-2
● Diagnostics with STEP 7
ET 200iSP Manual SIMATIC;
ET 200iSP Distributed I/O; Commissioning and Diagnostics
● Status and error LEDs on IM 151-2
● Insertion and removal of modules
● Line break of the NAMUR encoder on the digital input module
● Diagnostics with STEP 7
ET 200pro Manual SIMATIC;
ET 200pro Distributed I/O System; Commissioning and diagnostics
● LED display ...
● Insertion and removal of modules
● Diagnostics with STEP 7
ET 200S Manual SIMATIC;
ET 200S Distributed I/O; Commissioning and Diagnostics
● Diagnostics by means of LED displays
● Diagnostic messages for electronic modules
DP/PA Coupler Manual SIMATIC;
Bus couplers DP/PA- Link and Y-Link
Diagnostics by means of LED displays
● LED displays of the IM 157
● LED displays of the DP/PA coupler
● LED displays of the Y coupler
Y-Link Information under DP/PA Coupler
FF Link Manual SIMATIC;
Bus couplers FF- Link
AFD Manual SIMATIC;
(use on fieldbus - SIMATIC NET; PROFIBUS PA
PROFIBUS PA or ● Diagnostics by means of LED displays
FOUNDATION
● Diagnostic messages for electronic modules
Fieldbus)
AFS (use on fieldbus - Manual SIMATIC;
PROFIBUS PA or SIMATIC NET; PROFIBUS PA
FOUNDATION ● Diagnostics by means of LED displays
Fieldbus)
● Diagnostic messages for electronic modules
Components You can find information about diagnostic options in the following manuals and
sections:
Diagnostic repeaters Manual SIMATIC;
Diagnostic Repeater for PROFIBUS DP
● LED diagnostics
Switch for Ethernet Operating Instructions SIMATIC NET;
Industrial Ethernet Switches SCALANCE X-400
● LED
Commissioning manual SIMATIC NET; Industrial Ethernet, SCALANCE X-100
and SCALANCE X-200 Product Line
● SCALANCE X<…> displays (SCALANCE X208 displays, for example)
Manual SIMATIC NET; Industrial Ethernet OSM/ESM
● Display and control elements
Disclaimer of liability
WARNING
Siemens assumes no liability for improper use of the instructions provided in this
documentation and for any consequences that might result for the customer.
WARNING
Note the following:
● All work must be performed by trained service personnel.
● Always observe the plant-specific rules and government regulations when making
changes to your system.
● Observe the plant-specific boundary conditions and adjust the work accordingly.
● Always bear in mind that changes in a system can impact other parts of the system.
Calling
Enter the following in the "Run" dialog of the Start menu: "msinfo32".
Overview
Calling
Called via Computer Management
Overview
Calling
Called via Computer Management > System
Overview
Overview
Calling
Enter the following in the "Run" dialog of the Start menu: "cmd"
You can find additional information on the Windows commands named here by searching the
Microsoft "Help and Support Center".
Overview
Calling
In the Siemens SIMATIC programs Start menu: SIMATIC NET > Settings > Set PC Station
Overview
Calling
Options:
● In the Siemens SIMATIC programs Start menu: SIMATIC NET > Set PG/PC Interface
● SIMATIC Manager via menu command Options > Set PG/PC Interface
Overview
Calling
Call this on the Windows taskbar by clicking the following icon:
Requirement
The components in the configuration list must be entered in the same order as in the component
image you created with HW Config. If the configuration deviates, it cannot be downloaded to
the PC station. You can find additional information on this in the manual PCS 7 Process Control
System; PC Configuration and Authorizations, in the section "Preparing the PC stations".
NOTICE
Making changes to the configuration list when the PC station is running causes the entire PC
communication to be closed and restarted.
In this case, you will receive a corresponding warning message.
Overview
Overview
7.18.2.10 PC DiagMonitor
Overview of DiagMonitor
Overview
7.18.3.1 NetPro
Calling
In SIMATIC Manager or HW Config, select the menu command Options > Configure Network.
Overview
Calling
In the Siemens SIMATIC programs Start menu: STEP 7 > NCM S7 Industrial Ethernet >
Diagnostics
Overview
Calling
Called via the Web user interface or TELNET
Overview
Overview
7.18.3.5 NCM S7
Calling
In the Siemens SIMATIC programs Start menu: STEP 7 > NCM S7 > Diagnostics
Overview
Calling
Select the PROFINET IO system (e.g. in HW Config) and call the following menu command:
Edit > PROFINET IO > Topology.
Overview
7.18.3.7 MBSA
Introduction
The Microsoft Baseline Security Analyzer (MBSA) is a tool for administrators that enables them
to check a Windows network for security vulnerability.
Overview
Overview
Calling
1. Select "My Computer" in the tree view of Windows Explorer.
2. Select the "Simatic Shell" folder.
3. Select the menu command Settings from the shortcut menu.
Overview
Introduction
The WinCC "System Info" channel is used to evaluate system information from server PCs.
This channel does not require hardware because it directly accesses the system information
on the server PC on which it is installed.
Note
Only system information from a single server can be represented or evaluated on a client.
Overview
Configuration
Online help for WinCC Information System, "Communication > System Info > Channel
Configuration > How to Configure the Channel System Info".
Calling
In the Start menu under the SIEMENS SIMATIC products, select the menu command
WinCC.
Overview
Calling
In the Siemens SIMATIC programs Start menu: WinCC > Tools > Channel Diagnosis
Overview
Additional information
Online help for WinCC Information System, "Channel Diagnostics Using Channel Diagnosis"
Calling
Diagnostics on the connection between OS server and an OS client
Only when WinCC is in process mode: in the menu of the WinCC Explorer.
Overview
Overview
Overview
Note
Redundant single-station systems
The redundancy status is displayed in the process control messages.
Overview
For diagnostics in systems with redundant PCs, it is important to always have an overview of
the redundancy status. The redundancy status represents the status of the individual master
and standby computers. You use the redundancy status display for this.
● The status of the redundant server pair and the non-redundant server assigned to the OS
client are displayed on the OS clients.
● The server status is displayed on the OS servers.
Overview
The status of the time master OS server on the plant bus can be displayed in a plant picture.
A BCE network adapter or up to two communication processors (for example, CP 1623) can
be used as the access point for time synchronization.
You can determine the status of the access points in the process mode when the following
internal text tags are configured on a faceplate:
● Network adapter 1 : @TimeSyncDevice1State
● Network adapter 2 : @TimeSyncDevice2State
Overview
The status of the corresponding BATCH application is indicated within those icons by means
of one of the following thumbnails:
Overview
With SIMATIC Route Control, status icons in the Route Control server taskbar indicate the
redundancy status.
Calling
In the Siemens SIMATIC programs Start menu: SIMATIC Manager
Overview
7.18.7.2 HW Config
Calling
In the Siemens SIMATIC programs Start menu: SIMATIC Manager. In the tree view, click on
"SIMATIC Station" and double-click "Hardware" in the selection list.
Overview
Requirements
● The diagnostic repeater must be installed.
● The cable diagnostics must be prepared.
Calling
Select the diagnose repeater in HW Config.
Select menu command PLC > Diagnostics/Setting > Module Information
Additional information:
Help on STEP 7, topic "Diagnostics, hardware diagnostics and troubleshooting"
Overview
Introduction
SIMATIC PDM is a software package for configuration, parameter assignment, commissioning,
and maintenance of field devices (for example, transducers).
Overview
Disclaimer of liability
WARNING
Siemens assumes no liability for improper use of the instructions provided in this
documentation and for any consequences that might result for the customer.
WARNING
Note the following:
● Only trained service employees should be authorized to work on the process control
system.
● Always observe the plant-specific rules and government regulations when making
changes to your system.
● Observe the plant-specific boundary conditions and adjust the work accordingly.
● Always bear in mind that changes in a system can impact other sections of the system.
Overview
The components and tools listed below are not part of PCS 7 and are used for advanced testing
and diagnostics. Below you will find some of the diagnostics applications suitable for PCS 7:
● Amprolyzer (add-on product) (Page 116)
● BANY (add-on product) (Page 117)
● BT 200 bus test device (Page 119)
● SYSTEM Process Control Diagnostics (add-on product) (Page 119)
Introduction
Amprolyzer is a program that allows you to perform simple, thorough diagnostics for
PROFIBUS.
Calling
If you have installed Amprolyzer, call the program with the Start menu Programs >
Amprolyzer.
Overview
Overview
BANY is a Microsoft Windows-based tool used for documentation, diagnostics, recording, and
analysis of your PCS 7 Ethernet, PROFINET and PROFIBUS networks.
The program packages below can be supplied separately or as a bundle:
Program packages Application Program call after installation via the Start
menu:
BANYnet Diagnostic tool for Ethernet Programs > BANYnet.
networks
BANY PROFIBUS Diagnostic tool for Programs > BANY PROFIBUS.
PROFIBUS networks
BANY PNIO Diagnostic tool for Programs > BANY PNIO.
PROFINET networks
Requirements
● The PC to be used for analyzing PROFIBUS with BANY PROFIBUS must be equipped with
a PROFIBUS network adapter (CP 5512).
● If you wish to analyze the terminal bus and plant bus at the same time, the PC must be
equipped with two Ethernet network adapters.
BANYnet
The table below lists the options for diagnosing Ethernet networks using BANYnet:
BANY PROFIBUS
The table below lists the options for diagnosing PROFIBUS networks using BANY PROFIBUS :
BANY PNIO
The table below lists the options for diagnosing PROFINET networks using BANY PNIO :
Overview
Note
The bus test device is not a software program – for this reason, the Call column is omitted.
Introduction
Display of PROFIBUS diagnostic information on the operator station
Online help: SYSTEM DIAGNOSTICS help
Overview
Configuration
The configuration is described in the online help SYSTEM DIAGNOSTICS - Help > section
"PROFIBUS DP/PA DIAGNOSTICS".
Guide to documentation
You can find information on component response and the procedure to be followed in the event
of failure, exchange and return in the following documentation:
E H
Engineering station, 17, 19
Hard disks, 91
Backing up configuration data, 17, 19
Hardware, 32, 87, 109
Ensuring Availability - Preventive Measures, 13
Diagnostics, 109
ESM, 117
Diagnostics for displays, 87
Status, 117
Update, 32
Ethernet diagnostics and statistics functions, 99
Hardware configuration, 95
Event triggering, 102
Preparing the PC station, 95
Event viewer, 91
HART device, 109
Example, 39
Hiding messages, 62
Determining the current firmware version , 39
Hot restart, 50
Export
Redundant interface, 50
SIMATIC BATCH, 26
HW Config, 81, 111
Export
Calling, 111
Operator and display texts, 22
Diagnostics for the CPU, 81
Exporting/importing batch objects, 26
Module Information, 111
F I
Failure characteristics, 50
Icons in the taskbar, 107, 109
Redundant interface, 50
BATCH server, 107
Failure, replacement and return - guide to
Route Control server, 109
documentation, 121
IM, 40
Fault, 109
Firmware update, 40
On the PROFIBUS, 109
Import/Export Assistant, 26
Firmware
Importing
Updating, 36
SIMATIC BATCH, 26
Industrial Ethernet
Switches, 99
Plant documentation, 65
Preparing, 69
Remote diagnostics, 69 S
Preparing remote diagnostics, 69
Set PC station, 94
Printers and devices, 91
Set PC Station
Printers and print jobs, 96
Calling, 94
Process control messages, 106
Set PG/PC Interface, 94
PROFIBUS, 82, 97, 99, 100, 116, 117, 119
Calling, 94
Call analysis, 117
Setting access permissions, 103
Analysis, 117
Shared files, 92
Connections, 99, 100
Sharing, 92
Diagnostics, 82
Drives, 92
Interface diagnostics, 119
Files, 92
PROFIBUS monitor, 116
Folders, 92
PROFIBUS DP, 119
SIMATIC BATCH, 25, 28
Fault, 119
Archiving batches, 28
General, 119
Backing up configuration data, 25
PROFINET, 82, 117
SIMATIC Manager, 109
Call analysis, 117
Authorizations, 109
Analysis, 117
Calling, 109
Diagnostics, 82
Faults on PROFIBUS, 109
Project, 17, 19
HART devices, 109
Archiving, 17
Module Information, 109
Retrieving, 19
Operating mode, 109
PA devices, 109
System error, 109
R Time, 109
Reading, 66 SIMATIC PDM (add-on), 114
CPU diagnostic buffer, 66 SIMATIC Route Control, 29
Redundancy, 106 Backing up project data, 29
Diagnostics of of OS servers, 106 Backing up configuration data, 29
Time master role of the OS server, 106 Simatic Shell, 101
Redundancy state control, 106 Software, 49
Calling, 106 Update, 49
Redundant interface, 50 Updating, 49
Failure characteristics, 50 State, 58
Hot restart, 50 Messages, 58
Redundant OS components, 106 Station Configuration Editor, 95
Requirements, 51 Calling, 95
Diagnostics, 51 Status, 97, 104, 107, 109, 117
Resolution and frequency, 91 DP slaves, 97
Restore, 20 Multi-user operation, 104
Multiproject, 20 OSM/ESM, 117
Restoring, 20, 27 Redundant BATCH servers, 107
Backup, 27 Redundant Route Control servers, 109
Multiproject, 20 Time master role of the OS server, 106
Retrieving, 19 Storage media, 91
Project, 19 Storage space, 102
Router, 99 Supply source, 32
Latest operation system version, 32
Switches
Industrial Ethernet, 99
U
Update, 32, 36, 39, 41, 49
CP 443-x, 41
CPU operating system, 36
Firmware, 36
Hardware, 32
IM 152-1, 39
IM153-1, 39
IM153-2, 39
IM157, 39
Software, 49
Updating, 40
Firmware of an IM via Ethernet, 40
Updating a SIMATIC S7 CPU, 35
Updating the firmware, 36
User, 92
User Administrator, 103