PCS7 MaintenanceStation en-US en-US
PCS7 MaintenanceStation en-US en-US
Preface 2
Using the Maintenance
Station 3
SIMATIC
Additional documentation 4
Process Control System PCS 7
Maintenance Station V9.1 Configuring the
maintenance stations 5
Operator control and
Function Manual
monitoring 6
Integration of options 7
02/2021
A5E49490703-AA
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
indicates that minor personal injury can result if proper precautions are not taken.
NOTICE
indicates that property damage can result if proper precautions are not taken.
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 Security information.............................................................................................................................. 9
2 Preface ................................................................................................................................................. 11
3 Using the Maintenance Station ........................................................................................................... 15
3.1 Application, version and configuration ............................................................................... 15
3.2 Objects with diagnostic capability ...................................................................................... 20
3.3 "PC stations" area ............................................................................................................... 21
3.4 "Network objects" area ....................................................................................................... 23
3.5 "AS/System" area................................................................................................................ 24
3.6 "Field devices" area ............................................................................................................ 26
3.7 "User objects" area ............................................................................................................. 29
3.8 MS single station system .................................................................................................... 30
3.9 MS multiple station system ................................................................................................ 32
3.10 MS in plant configuration with multiple OS single-station systems ...................................... 34
3.11 SIMATIC PDM MS................................................................................................................ 36
3.12 PAM Station ....................................................................................................................... 39
4 Additional documentation................................................................................................................... 43
5 Configuring the maintenance stations ................................................................................................ 45
5.1 MS single station system overview ..................................................................................... 45
5.2 MS multiple station system overview.................................................................................. 46
5.2.1 MS Server overview ........................................................................................................... 46
5.2.2 Redundant MS server overview .......................................................................................... 47
5.2.3 MS client or OS/MS client overview .................................................................................... 47
5.3 Overview SIMATIC PDM MS ................................................................................................ 48
5.4 Overview SIMATIC PAM Station........................................................................................... 49
5.5 General settings in the multiproject/project ........................................................................ 50
5.6 Configuring the PC station for MS single station system ...................................................... 51
5.7 Configuring of PC stations for MS multiple station system ................................................... 53
5.7.1 How to configure a PC station for an engineering station .................................................... 53
5.7.2 How to configure a PC station for an MS server ................................................................... 54
5.7.3 How to configure a PC station for the redundant partner..................................................... 55
5.7.4 How to configure a PC station for an MS or OS/MS client ..................................................... 56
5.8 Creating a project for SIMATIC PDM MS............................................................................... 58
5.8.1 Sample project as a project basis ........................................................................................ 58
5.8.2 How to use the sample project ........................................................................................... 58
6.4.6.2 Message correction for objects with SNMP functionality ................................................... 174
6.4.6.3 PC station reset ................................................................................................................ 175
6.4.6.4 AS system reset................................................................................................................ 176
6.4.6.5 Field device reset ............................................................................................................. 176
6.4.6.6 User area reset................................................................................................................. 177
6.4.6.7 Initializing PC objects / Network objects ............................................................................ 178
6.4.6.8 Update PDM devices ........................................................................................................ 179
6.4.7 Filtered manual parameter data export............................................................................. 179
6.4.7.1 Calling the function "Filtered manual parameter data export"............................................ 179
6.4.7.2 Filter settings for the filtered manual parameter data export ............................................. 180
6.4.7.3 Filtered manual parameter data export of EDD/FDI-based devices ..................................... 184
6.4.7.4 How to start the filtered manual parameter data export .................................................... 186
6.4.7.5 How to terminate the filtered manual parameter data export ............................................ 187
6.4.7.6 How to start time-controlled synchronization ................................................................... 188
6.4.7.7 How to stop time-controlled synchronization.................................................................... 189
6.4.8 Filtered cyclic parameter data export ................................................................................ 189
6.4.8.1 Calling the function "Filtered cyclic parameter data export"............................................... 189
6.4.8.2 Filter settings for the filtered cyclic parameter data export ................................................ 190
6.4.8.3 Filtered cyclic parameter data export of EDD/FDI-based devices......................................... 193
6.4.8.4 How to start filtered cyclic parameter data export ............................................................. 195
6.4.8.5 How to terminate the filtered cyclic parameter data export ............................................... 197
6.4.9 Manually filtered complete export via OPC........................................................................ 197
6.4.9.1 Variables for OPC access................................................................................................... 197
6.4.9.2 How to launch the manually filtered complete export (OPC).............................................. 201
6.4.10 Filtered manual parameter data export via OPC access...................................................... 202
6.4.10.1 Tags for OPC access.......................................................................................................... 202
6.4.10.2 How to start the filtered manual parameter data export (OPC) .......................................... 209
6.4.10.3 How to end the filtered manual parameter data export (OPC) ........................................... 210
6.4.10.4 How to start time-controlled synchronization (OPC).......................................................... 210
6.4.10.5 How to stop time-controlled synchronization (OPC) .......................................................... 211
6.4.10.6 How to start the parameter data export for a selected device (OPC) .................................. 211
6.5 Area overview screens ..................................................................................................... 213
6.6 Display of the objects ....................................................................................................... 215
6.7 Block icon ........................................................................................................................ 216
6.8 Block icon for redundant objects ...................................................................................... 219
6.9 Maintenance status and maintenance group display ......................................................... 221
6.10 Maintenance status of redundant objects ......................................................................... 225
6.11 Faceplate ......................................................................................................................... 226
6.11.1 Faceplate display.............................................................................................................. 226
6.11.2 Screen window title and header ....................................................................................... 227
6.11.2.1 Displays and operator controls ......................................................................................... 227
6.11.2.2 Display elements and operator controls for the parameter data export and the filtered
complete export .............................................................................................................. 232
6.11.2.3 How to lock and unlock messages .................................................................................... 234
6.11.2.4 How to depassivate modules or channels ......................................................................... 236
6.11.2.5 How to open websites via maintenance links.................................................................... 236
6.11.2.6 How to open the online view of HW Config....................................................................... 237
6.11.2.7 How to open the configuration interface of SIMATIC PDM ................................................. 238
6.11.2.8 How to call up the Web interface of a network object ....................................................... 239
• PUD Manager
The "PUD Manager" an innovative tool to access documentation, comes with PCS 7 USB flash
drive.
Some of the highlights:
– Customize the documentation set according to your needs.
– Efficient search engine to access your information.
For more information on PUD Manager, refer Process Control System PCS 7; PUD Manager
V2.1 Online Help.
• Technical Information and Solutions
For important technical information and solutions, refer to SIMATIC PCS 7 Overview (https://
support.industry.siemens.com/cs/ww/en/view/63481413).
• PCS 7 System Documentation
System documentation includes documents that cover several products, such as
configuration manuals and Getting Started manuals. This documentation serves as a
guideline for the overall system and explains the interaction between the individual
hardware and software components.
• PCS 7 Product Documentation
Product documentation contains information about specific hardware and software
components. The individual documents provide detailed information on the specific
component.
Full versions of the documentation are available from the "Technical Documentation SIMATIC
PCS 7" website:
PCS 7 Technical documentation (http://www.siemens.com/pcs7-documentation).
You can find additional information in the product overview Process Control System PCS 7; PCS
7 Documentation; section "Options for accessing the documentation".
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 language package (MUI) 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.
Application
Maintenance Station focuses on "Plant Asset Management" and enables preventive and
predictive diagnostics and maintenance of the plant.
In parallel with process control, the Maintenance Station makes available consistent
maintenance information and functions for the system components (assets).
While the plant operator receives all process-relevant information and can intervene selectively
in the process via the operator system (OS), the maintenance engineer inspects the automation
system hardware and processes the associated diagnostic messages and maintenance demands
via the Maintenance Station.
The basis for a Maintenance Station is always an OS that provides this maintenance
functionality.
The OS that has maintenance functionality and the mode in which the Maintenance Station that
is operated is determined in the plant hierarchy of the SIMATIC Manager.
You can find basic information on engineering, configuration and process control in the
following documentation:
• Process Control System PCS 7 Engineering System
• Process Control System PCS 7 Operator Station
• Online help for WinCC
Variants
The Maintenance Station can be used in the following variants:
• SIMATIC PCS 7 Maintenance Station Basic (integrated in the PCS 7 project)
– Is referred to as MS Basic in the document
• SIMATIC PCS 7 Maintenance Station Standard (integrated in the PCS 7 project)
– Is referred to as MS Standard in the document
• SIMATIC Plant Device Management Maintenance Station (stand-alone project)
– Referred to as PDM MS in the document
• SIMATIC Plant Asset Management Station
– Referred to as PAM Station in the document
Note
If you are running a Maintenance Station in the plant, the sign-of-life monitoring with "Lifebeat
Monitoring" must be disabled.
Configuration
The MS Basic and MS Standard of the maintenance station can be configured as MS single-
station system or as MS multiple-station system.
You can find more information on this in the sections "MS single station system (Page 30)" and
"MS multiple station system (Page 32)".
PDM MS can only be configured as an MS single-station system.
You can find additional information about this in the section "SIMATIC PDM MS (Page 36)".
PAM Station can be operated as an MS single-station or MS multiple-station system.
You can find additional information about this in the section "PAM Station (Page 39)".
Note
This function is available for the Maintenance Station in the MS Standard and MS Basic version.
What is monitored?
What is monitored?
What is monitored?
What is monitored?
Plant configuration
The MS single-station system has the following functionalities:
• Operator station (OS)
• Engineering station (ES)
• Maintenance Station (MS)
• SIMATIC PDM
The complete operator control and monitoring functionality for a PCS 7 project (plant/unit) is
located in one station. The OS areas and the "Diagnostics" area of the MS are displayed in the
overview area of the process control.
The "Diagnostics" area visualizes the diagnostics state via diagnostics screens, providing the
required operator control and monitoring functions.
The MS single-station system on the plant bus can be used in parallel with additional single-
station or multiple-station systems.
Plant configuration
The figure below shows an example plant configuration.
6LQJOHVWDWLRQV\VWHP
(QJLQHHULQJVWDWLRQ
2SHUDWRUVWDWLRQ
0DLQWHQDQFH6WDWLRQ
6,0$7,&3'0
3ODQWEXV
$6 $6
Rule
The maintenance station is disabled during configuration.
Plant configuration
The MS server:
• Is configured either on a separate PC station or on a PC station together with the OS server
• Can be configured redundantly
• Processes the process control messages which are visualized on the OS/MS client and/or MS
client
• Can monitor network objects via the OPC server at the plant bus if there is a connection to the
plant bus
The MS client can be configured as follows:
• MS client on a PC station
The MS client visualizes the diagnostic status in the diagnostic area using diagnostic screens
and provides the required operator control and monitoring functions.
• MS client and OS client on a PC station (OS/MS client)
The OS/MS client has the same functionality as an MS client on a PC station and the same
functionality as an OS client.
In addition to the diagnostic area, the overview visualizes the technological areas for process
control.
• MS client on the engineering station
The MS client on the engineering station has the same functionality as an MS client on a PC
station.
In addition, the online view of the hardware configuration editor can be opened.
The MS client that is operated on the engineering station is disabled during configuration.
Plant configuration
The figure below shows an example plant configuration.
7HUPLQDOEXV
26VHUYHU 26VHUYHU 06VHUYHU
3ODQWEXV
(QJLQHHULQJ 0DLQWHQDQFH
,QGXVWULDO(WKHUQHWWHUPLQDOEXV VWDWLRQ VWDWLRQ
26VLQJOHVWDWLRQV\VWHPV
0D[LPXP3&VWDWLRQV
,QGXVWULDO(WKHUQHWSODQWEXV
Configuration:
• 1 redundant OS single-station system (single-station system + single-station system standby)
• Optional: Up to 10 non-redundant OS single-station systems (as reference OS from the OS
single-station system)
• MS as separate PC station
The MS server obtains the data from the AS over the redundant OS single-station system.
If the redundant OS single-station system is disabled, the AS data is no longer displayed.
Note
Messages generated locally on a reference OS are not displayed in the diagnostics pictures.
Affected are e.g. messages for self diagnostics.
If the reference OS is unavailable via the terminal bus, it is visualized on the MS server, however.
For the diagnostic information to be displayed on the OS single-station systems, a Web server
must be configured on the MS server.
The OS single-station system can access the MS server with Web browser control.
You have two options for accessing the MS server from the OS single-station system:
• Option 1
Create a user picture on the OS single-station system in the "Graphics Designer".
Insert a "WinCC WebBrowser Control" in the user picture.
In the process control, you can access the MS via the "WinCC WebBrowser Control" in the user
picture.
• Option 2
Launch the Web Client function via Internet Explorer.
Additional information
Process Control System PCS 7; PC Configuration manual
System configuration
The SIMATIC PDM MS is a station comprises of an IPC Microbox 427x with a pre-installed
operating system and the software solution with a virtualized AS as a single-station system. It is
designed for stand-alone purpose and is independent of the automation solution used.
In terms of representation and function, the SIMATIC PDM MS is structured in the same way as
the SIMATIC PCS 7 Maintenance Station. All the operating and monitoring functions are
performed locally on this PC station.
In the Diagnostics area, the SIMATIC PDM MS visualizes the diagnostic status via diagnostic
screens and provides the necessary operating and monitoring functions.
The diagnostic states of the field devices are determined by the SIMATIC PDM and transmitted to
the virtual AS system for processing using the SIMIT Virtual Controller (VC) installed on the
computer. Messages associated to the field devices are generated by the application in the VC
and the states of the field devices are saved. This information is visualized in the Operating
Process on the SIMATIC PDM MS.
Plant configuration
The figure below shows an example plant configuration.
6,0$7,&3'006
,QGXVWULDO(WKHUQHWSODQWEXV
PROFIBUS DP PROFIBUS DP
PROFIBUS PA PROFIBUS PA
+$57PXOWLSOH[HU
0DQXIDFWXUHU[ :LUHOHVV+$57
Rule
PDM MS is disabled during creation or change of the project structure.
System configuration
PAM Station is designed for stand-alone use and is independent of the automation solution
used. PAM Station consists of a combination of an IPC 647 and an AS410 station which is
connected to the central system bus.
PAM station is similar to MS Standard in terms of functionality and representation in process
control. All operating and monitoring functions can be performed locally on this PC station or on
the clients if PAM Station is configured as a multi-user system. PAM Station visualizes the
diagnostic status in the diagnostics area via diagnostic screens and provides the necessary
operator control and monitoring functions.
The diagnostic states of field devices are determined by SIMATIC PDM. In addition, diagnostic
states can be transferred from the package unit using data block communication. The
combination of this information is then used to generate the corresponding maintenance
messages on the PAM station. In the following, an AS system to be monitored with lower-level
field devices is referred to as a package unit.
Plant configuration
The figure below shows an example plant configuration.
6,0$7,&3$06WDWLRQ
,QGXVWULDO(WKHUQHWSODQWEXV
SIMATIC PAM AS
PROFIBUS DP PROFIBUS DP
PROFIBUS PA PROFIBUS PA
+$57PXOWLSOH[HU
0DQXIDFWXUHU[ :LUHOHVV+$57
(1) The IP protocol must be used for all automation systems. When connected to high-availability
automation systems, the IP protocol must be additionally enabled or else the ISO-on-TCP
protocol is used The PAM station is operated on a non-redundant system bus.
Rule
The process control of the PAM station is disabled during the creation or modification of the
project structure.
The configuration limits of the PAM station is designed for a maximum of 100 non-redundant or
50 redundant AS/PLC stations with up to 200 PDM objects each. The product package includes
a licensing for up to 1000 maintenance objects. Appropriate licenses must be purchased if this
limit is exceeded.
Documentation Purpose
Online help: The documentation supports you during configuration
Help on PCS 7, Configuration - with the SIMATIC Process Control System PCS 7 on an
Engineering System engineering station.
Manual:
Process Control System PCS 7
Engineering System
Online help: The documentation supports you during configuration
Help on PCS 7, Configuration - with the SIMATIC PCS 7 Process Control System on an
Operator Station operator station.
Manual:
Process Control System PCS 7
Operator Station
Manual: This documentation supports you when setting up cen‐
SIMATIC Logon, tral access authorization administration with SIMATIC
SIMATIC Electronic Signature Logon.
Online help and manual: This documentation describes the functions and block I/
Process Control System PCS 7 Os of diagnostic blocks.
PCS 7 Basic Library
Online help and manual: This documentation describes the functions, block I/Os,
Process Control System PCS 7 and input/output fields of the associated faceplates.
PCS 7 Advanced Process Library
Online help: The documentation supports you in configuring the op‐
WinCC Information System erator stations and in operating the operator stations in
the process control.
Manual: This documentation offers support during installation,
Process Control System PCS 7 commissioning of the software, configuration of net‐
SIMATIC PDM works and field devices, commissioning and using run‐
time functions.
Manual: This documentation describes the configuration, instal‐
SIMATIC NET lation and commissioning of an IE/PB Link PN IO.
S7 CPs for Industrial Ethernet (part BL1)
Manual The document offers information on the latest grading
Process Control System PCS 7 of licenses for the different components of the process
Licenses and Quantity Structures control system and the plant size you can achieve with
them.
The section "Calculating the asset tags (hardware com‐
ponents) for the maintenance station" of the document
offers information about the diagnostics-capable ob‐
jects within a PCS 7 project that are counted as asset tags.
Documentation Purpose
Manual The document provides information about hardware
Process Control System PCS 7 and software requirements and about the configuration
PC Configuration options of a PC station.
Manual The "Maintenance Station" section of the documents
Process Control System PCS 7 provides information on migrating a Maintenance Sta‐
Software update with utilization of new func‐ tion.
tions
Manual
Process Control System PCS 7
Software update without utilization of new
functions
What? MS MS
Basic Standard
General settings in the multiproject/project (Page 50) X X
Configuring the PC station for MS single station system (Page 51)
Configuring the monitoring of industrial PCs and network objects (Page 84)
Creation of the diagnostics structure (Page 91)
Advanced diagnostics settings (Page 96) -
Configuring the user diagnostics (Page 121)
Setting up SIMATIC PDM (Page 129) X
Overview of complete export (Page 130)
Overview of individual export (Page 131)
Engineering for maintenance (Page 132) -
Creating/updating the diagnostic screens (Page 135) X
Compile and download (Page 137)
Integration by the Alarm Control Center (Page 311) -
What? MS MS
Basic Standard
General settings in the multiproject/project (Page 50) X X
How to configure a PC station for an engineering station (Page 53)
How to configure a PC station for an MS server (Page 54)
Configuring the monitoring of industrial PCs and network objects (Page 84)
Creation of the diagnostics structure (Page 91)
Advanced diagnostics settings (Page 96) -
Configuring the user diagnostics (Page 121)
Setting up SIMATIC PDM (Page 129) X
Overview of complete export (Page 130)
Overview of individual export (Page 131)
Engineering for maintenance (Page 132) -
Creating/updating the diagnostic screens (Page 135) X
Compile and download (Page 137)
Integration by the Alarm Control Center (Page 311) -
What? MS MS
Basic Standard
General settings in the multiproject/project (Page 50) X X
How to configure a PC station for an engineering station (Page 53)
How to configure a PC station for an MS server (Page 54)
How to configure a PC station for the redundant partner (Page 55)
Configuring the monitoring of industrial PCs and network objects (Page 84)
Creation of the diagnostics structure (Page 91)
Advanced diagnostics settings (Page 96) -
Configuring the user diagnostics (Page 121)
Setting up SIMATIC PDM (Page 129) X
Overview of complete export (Page 130)
Overview of individual export (Page 131) X
Engineering for maintenance (Page 132) -
Creating/updating the diagnostic screens (Page 135) X
Compile and download (Page 137)
Integration by the Alarm Control Center (Page 311) -
What? MS MS
Basic Standard
How to configure a PC station for an MS or OS/MS client (Page 56) X X
Assigning the server data and downloading of a client (Page 138)
Note
There is only one MS server within a multiproject/project.
Additional information
For more information about this, refer to the Process Control System PCS 7 Engineering System
manual and the Process Control System PCS 7; Operator Station manual.
Introduction
If you are already using an existing ES/OS single station system in the multiproject/project you
do not need to execute the following steps.
Requirement
The multiproject/project has been created.
Procedure
1. In the component view of the SIMATIC Manager, select the project into which you want to
insert the MS single station system.
2. Select the menu command Insert > Station > SIMATIC PC station.
A new SIMATIC PC station is inserted in the selected project.
3. Select the SIMATIC PC station, and then select Edit > Object Properties.
4. Enter the name for the PC station in the "Name:" text box.
5. Enter the Windows computer name in the "Computer name" input box.
6. Click "OK".
7. Select the SIMATIC PC station in the component view of the SIMATIC Manager.
8. In the detailed view, open HW Config by double-clicking the "Configuration" object.
The hardware configuration of the SIMATIC PC station opens.
9. If the hardware catalog is not visible, select the menu command View > Catalog.
The hardware catalog opens.
10.Under "SIMATIC PC Station > HMI" in the hardware catalog, select the WinCC application and
drag it into the configuration table.
11.If you want to monitor PC stations and/or network objects, under "SIMATIC PC Station > User
application > OPC server" in the hardware catalog select the OPC server and drag it into the
configuration table.
12.If you want to use SIMATIC PDM, under "SIMATIC PC Station > PDM" in the hardware catalog,
select the PDM application and drag it into the configuration table.
13.Insert any additional objects, for example, network adapters.
For Ethernet connections, it is recommended to use the IE General interface.
14.If you want to monitor the CP 1623 / CP 1613 communications processor as a network object,
use the "Properties..." button to activate "IP protocol is used" in the object properties of the
CP in the "Interface" area of the "General" tab.
15.Select the menu command Save and Compile Station and close HW Config.
16.In the component view of the SIMATIC Manager, select the "[OS(*)]" object below the
SIMATIC PC station in the "WinCC Appl." hierarchy folder.
* is a number assigned by the system.
Introduction
If you have already configured an Engineering Station (ES) in the multiproject/project and are
using SIMATIC PDM, you only have to execute the steps as of step 12.
Requirement
The multiproject/project has been created.
Procedure
1. In the component view of the SIMATIC Manager, select the multiproject/project into which
you want to insert the ES.
2. Select the menu command Insert > Station > SIMATIC PC station.
A new SIMATIC PC station is inserted in the selected multiproject/project.
3. Select the SIMATIC PC station, and then select Edit > Object Properties.
4. Enter the name for the PC station in the "Name:" text box.
5. Enter the Windows name of the ES in the "Computer Name" input box.
6. Click "OK".
7. Select the SIMATIC PC station in the component view of the SIMATIC Manager.
8. In the detailed view, open HW Config by double-clicking the "Configuration" object.
The hardware configuration of the SIMATIC PC station opens.
9. If the hardware catalog is not visible, select the menu command View > Catalog.
The hardware catalog opens.
10.Under "SIMATIC PC Station > HMI" in the hardware catalog, select the WinCC application and
drag it into the configuration table.
11.Insert any additional objects, for example, network adapters.
For Ethernet connections, it is recommended to use the IE General interface.
12.If you want to monitor the CP 1623 / CP 1613 communications processor as a network object,
use the "Properties..." button to activate "IP protocol is used" in the object properties of the
CP in the "Interface" area of the "General" tab.
13.If you are using SIMATIC PDM, under "SIMATIC PC Station > PDM" in the hardware catalog,
select the PDM application and drag it into the configuration table.
14.Select the menu command Save and Compile Station and close HW Config.
15.Download the component configurator.
Introduction
If you are already using an existing OS server as MS server in the multiproject/project, you do not
need to execute the following steps.
Requirement
The multiproject/project has been created.
Procedure
1. In the component view of the SIMATIC Manager, select the multiproject/project into which
you want to insert the MS server.
2. Select the menu command Insert > Station > SIMATIC PC station.
A new SIMATIC PC station is inserted in the selected multiproject/project.
3. Select the SIMATIC PC station, and then select Edit > Object Properties.
4. Enter the name for the PC station in the "Name:" text box.
5. Enter the Windows name of the computer in the "Computer Name" input box.
6. Click "OK".
7. Select the SIMATIC PC station in the component view of the SIMATIC Manager.
8. In the detailed view, open HW Config by double-clicking the "Configuration" object.
The hardware configuration of the SIMATIC PC station opens.
9. If the hardware catalog is not visible, select the menu command View > Catalog.
The hardware catalog opens.
10.Under "SIMATIC PC Station > HMI" in the hardware catalog, select the WinCC application and
drag it into the configuration table.
11.If you want to monitor PC stations and/or network objects, under "SIMATIC PC Station > User
application > OPC server" in the hardware catalog select the OPC server and drag it into the
configuration table.
12.Insert any additional objects, for example, network adapters.
For Ethernet connections, it is recommended to use the IE General interface.
13.If you want to monitor the CP 1623 / CP 1613 communications processor as a network object,
use the "Properties..." button to activate "IP protocol is used" in the object properties of the
CP in the "Interface" area of the "General" tab.
14.Select the menu command Save and Compile Station and close HW Config.
15.In the component view of the SIMATIC Manager, select the "[OS(*)]" object below the
SIMATIC PC station in the "WinCC Appl." hierarchy folder of the MS server.
* is a number assigned by the system.
16.Select the menu command Edit > Object Properties.
The "Properties – OS [name of OS]" dialog box opens.
17.In the entry field "Name:", enter a name for the PCS 7 OS project of the MS server.
18.Select the "Target OS and Standby OS" tab.
– Enter the path to the target OS computer in the "Path to target OS computer" input box.
– Enter a symbolic computer name in the "Symbolic computer name" input box.
– Select the following from the drop-down list box in the "Standby OS" area:
If you not configure the MS server redundantly, select ">none>".
If you configure the MS server redundantly, select the redundant partner. You can only
select the partner if it has been configured.
19.Click "OK".
Introduction
If you are already using the redundant partner of an OS server in the multiproject/project, you
do not need to execute the following steps.
Requirement
The multiproject/project has been created.
Procedure
1. In the component view of the SIMATIC Manager, select the multiproject/project into which
you want to insert the redundant partner.
2. Select the menu command Insert > Station > SIMATIC PC station.
A new SIMATIC PC station is inserted in the selected multiproject/project.
3. Select the SIMATIC PC station, and then select Edit > Object Properties.
4. Enter the name for the PC station in the "Name:" text box.
5. Enter the Windows name of the computer in the "Computer Name" input box.
6. Click "OK".
7. Select the SIMATIC PC station in the component view of the SIMATIC Manager.
8. In the detailed view, open HW Config by double-clicking the "Configuration" object.
The hardware configuration of the SIMATIC PC station opens.
9. If the hardware catalog is not visible, select the menu command View > Catalog.
The hardware catalog opens.
10.Under "SIMATIC PC Station > HMI" in the hardware catalog, select the WinCC application
(stby) and drag it into the configuration table:
11.Insert any additional objects, for example, network adapters.
For Ethernet connections, it is recommended to use the IE General interface.
12.If you want to monitor the CP 1623 / CP 1613 communications processor as a network object,
use the "Properties..." button to activate "IP protocol is used" in the object properties of the
CP in the "Interface" area of the "General" tab.
13.Select the menu command Save and Compile Station and close HW Config.
14.In the component view of the SIMATIC Manager, select the "[OS(*)_StBy]" object below the
SIMATIC PC station in the "WinCC Appl." hierarchy folder (Stby.).
* is a number assigned by the system.
15.Select the menu command Edit > Object Properties.
The "Properties – Standby OS: [name of OS]" dialog box opens.
16.Select the "Target OS and Master OS" tab and enter the path to the target OS computer.
17.Click "OK".
Introduction
You can operate the MS Client or OS/MS Client on the Engineering Station or a separate PC.
Requirement
The multiproject/project has been created.
Procedure
1. In the component view of the SIMATIC Manager, select the multiproject/project into which
you want to insert the MS client.
2. Select the menu command Insert > Station > SIMATIC PC station.
A new SIMATIC PC station is inserted in the selected multiproject/project.
3. Select the SIMATIC PC station, and then select Edit > Object Properties.
4. Enter the name for the PC station in the "Name:" text box.
5. Enter the name in the "Computer name" input field.
– If you are running the MS client on a separate PC station, enter the Windows computer
name of the target computer.
– If you are operating the MS client as MS client on the engineering station, enter the
Windows computer name of the engineering station.
6. Click "OK".
7. Select the SIMATIC PC station in the component view of the SIMATIC Manager.
8. In the detailed view, open HW Config by double-clicking the "Configuration" object.
The hardware configuration of the SIMATIC PC station opens.
9. If the hardware catalog is not visible, select the menu command View > Catalog.
The hardware catalog opens.
10.Under "SIMATIC PC Station > HMI" in the hardware catalog, select the WinCC application
client and drag it into the configuration table.
11.Insert any additional object.
12.Select the menu command Save and Compile Station and close HW Config.
13.In the component view of the SIMATIC Manager, select the "[OSC]" object underneath the MS
client's SIMATIC PC station.
14.Select the menu command Edit > Object Properties.
The "Properties – Client OS: [name of OS]" dialog box opens.
15.In the entry field "Name:", enter a name for the PCS 7 OS project of the MS client.
16.Click "OK".
Introduction
The PDM MS is connected directly to the plant bus through which the automation stations
communicate.
Multiple SIMATIC PDM MS stations can be used in an automation plant. Each station can process
selected field devices of the project based on the task.
The easiest way to integrate the SIMATIC PDM MS into an existing automation system is to create
a project using the supplied sample project with the name "PDMMS_Example".
The station import function can be used to directly transfer communication and device
information from the SIMATIC PCS 7 project to the project of SIMATIC PDM MS.
Additional information
You can find information on using the example project in the following section "How to use the
sample project (Page 58)".
Requirements
• The A1 image with the operating system is installed in the IPC 427.
• The software for the SIMATIC PDM MS was installed via the frame setup of the SIMATIC PCS
7 software media package.
• The SIMIT virtual controller for SIMATIC PDM MS was installed via the setup under the
Additional_Products from the SIMATIC PCS 7.
• The licenses are transferred and are installed on the IPC 427.
• The WiBu dongle for the SIMIT VC is plugged into the IPC 427.
• The SIMATIC PDM device description library has been imported (in case if it was not included
in the image).
• The Ethernet interface of the IPC 427 used for the system bus is configured with a free address
according to the address band on the system bus of the SIMATIC PCS 7 project.
• For the virtual controller that you will use later as a CPU, another free IP address of the system
bus must be entered in the properties of the network card for the Internet protocols (TCP /
IPv4) under advanced settings as an additional IP.
• The terminal bus Ethernet interface (if required) is either configured for a different address
band or set to "Obtain an IP address automatically" in the IP settings.
Procedure
1. Open the SIMATIC Manager.
2. Select the menu command File > Open... .
– Select the Sample projects tab.
– Select the sample project "PDMMS_Example".
– Click "OK".
3. Select the menu command File > Save as... .
Assign the name and location for the project.
4. Select the menu command Options > SIMATIC PDM > Settings... .
– Select the "General" tab.
Enter the path for "Asset export" files.
– Select the "Communication" tab.
If HART auxiliary variables are cyclically transmitted in at least one remote I/O station,
do not enable the SHC mode.
– Select the "Load" tab.
If this function is managed by the automation system, or the "Synchronization field device
parameters" function is used on a SIMATIC PCS 7 Maintenance Station, do not enable the
"Configuration Flag Reset" function.
– Select the "Maintenance Station" tab.
Assign the current project.
Select the "Transfer Maintenance Alarm to Maintenance Station" check box.
– Select the "Change Log" tab.
If you want to save the changes, enable the function.
– Once you update all the settings, close the dialog box by clicking "OK".
5. Select the menu command Options> SIMATIC PDM > Roles management... .
Administer the function rights.
For information on roles management, refer "Roles management" section.
6. Select the SIMATIC PC station and select the menu command Edit > Object Properties... .
– Enter the name of the PC station in the "Name" text box.
– Enter the Windows machine name in the "Computer name" text box.
– Click "OK".
7. Select the PC station and select the menu command Edit > Open Object.
– Configure the selected IP address for the connection to the plant bus in IE General.
– Compile and download the station.
– Close the HW Config.
8. Open the PCS 7 OS project.
– Navigate to OS > Computer and select "PDM_MS_PC"
– Open the properties
– Click "Use Local Computer Name"
– Click "OK" and close the PCS 7 OS project.
9. Select the AS station.
10.Select the menu command Edit > Object Properties... .
– Open the properties of PN-IO-X5 of the CPU and configure the IP address of the virtual
controller.
– Compile the station.
– Close the HW Config.
11.Select the menu command View > Process Device Network View.
12.Navigate to Networks and select the menu command Insert > SIMATIC PDM >
Communication network.
13.Select the "ETHERNET interface".
14.Select the menu command Edit > Object Properties... .
– Select the "Communication" tab.
– Select the option "Use network adapter"
– In the "Network adapter" combo box select the ethernet interface used for the system bus.
15.Select the "PROFINET network" communication network.
16.Select the menu command Edit > Object Properties... .
– Select the "Communication" tab.
– Enter the subnet ID of the plant bus.
You can find the subnet ID in HW Config in the properties of the interface for the plant bus
of each AS station or directly in the properties of the plant bus in NetPro.
– Click "OK" to close the dialog box.
Note
Make sure that the project is a STEP7 or PCS 7 project with PDM. Otherwise, manual
engineering in the "Process Device Network View" is necessary.
Note
When you import a device, ensure that the name of the device is unique.
Note
Process Device Network imports from PCS 7 are possible only via the "Import from HWC
station" function.
29.Verify whether the key switch of the virtual controller is set to "Run" or switch it to the "RUN"
position via the SIMATIC Manager menu command PLC > Diagnostics/Settings > Operating
Mode... .
30.Select the OS project.
31.Start the wizard for compiling the OS with the menu command Edit > Compile.
32.Open the PCS 7 OS project.
33.Start the OS project editor.
34.Start the OS process control.
Result
SIMATIC PDM MS is ready for operation.
Additional information
You can find the description of how to operate the process control in the section "Operator
control and monitoring (Page 147)".
Introduction
Access protection via "SIMATIC Logon Role Management" controls access to device
management, parameter assignment and field device diagnostics.
The following roles have been created for SIMATIC PDM in SIMATIC Logon Role Management by
the system:
• PDM command interface
• Service technician
The roles created by the system can be assigned Windows user groups/users of the local
computer or the domain.
You can add new roles. Assign "Groups and users" and "Function rights" to the roles you have
added.
The function rights are specified by the system. They cannot be deleted, edited or amended.
Additional information
You can find information about SIMATIC Logon Role Management in the manual SIMATIC,
SIMATIC Logon.
You can find information about configuring a role in the section below "How to configure a 'role'".
Requirements
• Groups and users are created in Windows
• Groups and users are members of the "TIA Engineer" group
• At least one user account has administrator rights
Procedure
1. In the SIMATIC Manager, select the menu command Options > SIMATIC PDM > Role
management... .
2. Select the "Roles" folder.
3. Select the "New role" menu command.
4. Enter a name in the "Role name:" text box.
5. Click "OK".
6. Open the folder with the newly created role.
7. Select the "Groups and users" folders associated with the role.
8. Select the "Edit" menu command.
9. Assign "Groups and users" to the role.
10.Click "OK".
11.Select the "Function rights" folders associated with the role.
Result
An additional role has been created.
Introduction
The PAM station is connected directly to the plant bus through which the automation stations
communicate.
Several PAM stations can be used in an automation system. Each station can process selected
units / package units of the project according to the task.
The easiest way to integrate the PAM station into an existing automation system is to create a
project using the supplied example project with the name "PAM_Example".
Using the station import function, communication and device information can be transferred
directly from the automation project to the project of the PAM station.
The example project is available in English. If you need more languages, add them via the
language settings.
You can find information on the language settings in the manual SIMATIC Process Control System
PCS 7 Engineering System .
Note
An extension of the S7-400 hardware configuration of the PAM station is not supported.
Additional information
You can find information on using the example project in the following section "How to use the
sample project (Page 65)".
Requirements
• The PAM Station software is installed on the IPC.
• The licenses are transferred.
• The SIMATIC PDM device description library has been imported.
• The Ethernet interface used for the system bus is configured with an available address within
the address range on the system bus of the automation project.
• The terminal bus Ethernet interface (if desired) is either configured for a different address
range or it is set to "Obtain an IP address automatically" in the IP settings.
• The PAM station is connected to the system bus.
• The intended user accounts have been created under <Control Panel > User Accounts > User
Accounts > Manage.
• The project administrator is a member of the local user group "Logon_Administrator" under
<Computer Management > System > Local Users and Groups > Groups/
Logon_Administrator>.
• All intended users are members of the local user group "Siemens TIA Engineer" listed under
<Computer Management > System > Local Users and Groups > Groups/Siemens TIA
Engineer>.
• You have access (local disk or network) to the automation project via the Windows Explorer
of PAM station.
• The IP protocol or ISOon TCP protocol is activated in the AS/PLC stations of the automation
project.
• The PG/PC interface is set to "PC internal".
Procedure
1. Open SIMATIC Manager.
2. Select the menu command File > Open... .
– Select the Sample project tab.
– Select the sample project.
– Click "OK".
Note
The example project is created in English. The warning regarding Windows language settings
during installation of a Chinese computer can be ignored.
5. Select the menu command Options > SIMATIC PDM > Roles management... .
Administer the function rights.
You can find information on roles management in the "Roles management" section.
6. Select the PC station.
7. Select the menu command Edit > Open Object.
– Configure the selected IP address for the connection to the plant bus in IE General.
– Compile and download the station
8. Select the SIMATIC 400 station.
9. Select the menu command Edit > Open Object.
– Configure the selected IP address of interface "PN-IO-X5" for the connection to the plant.
– Compile and download the station
10.Select the menu command View > Process Device Network View.
11.Select the "ETHERNET network" communication network
12.Select the menu command Edit > Object properties... .
– Select the "Communication" tab.
– Enter the subnet ID of the plant bus.
You can find the subnet ID in HW Config in the properties of the interface for the plant bus
of each AS station or directly in the properties of the plant bus in NetPro.
13.Select the "ETHERNET network" communication network.
14.Select the menu command Edit > SIMATIC PDM > Import from HWC station.
– Select the user project.
– Select the AS stations.
The AS stations can be selected individually.
– To import the field devices from the automation project, click the "Import" button.
Note
You cannot import your configuration, create it manually in the SIMATIC PDM process device
network view.
18.Select the menu command Options > Plant hierarchy > Advanced diagnostics settings... .
If desired, configure the advanced diagnostic settings.
You can find details on the diagnostic settings under Advanced diagnostics settings
(Page 96).
19.Select the Options > Plant hierarchy > Create/update diagnostics screens menu
command.
Note
In this step, unspecified connections are automatically created in NetPro. These may not be
changed or deleted manually.
Result
The PAM station is ready for operation.
Additional information
You can find the description of operating in process control in the section "Starting the process
control (Page 147)".
Requirements
• The PAM Station software is installed on the IPC.
• The licenses are transferred.
• The SIMATIC PDM device description library has been imported.
• The Ethernet interface used for the system bus is configured with an available address within
the address range on the system bus of the automation project.
• The terminal bus Ethernet interface (if desired) is either configured for a different address
range or it is set to "Obtain an IP address automatically" in the IP settings.
• The PAM station is connected to the system bus.
• The intended user accounts have been created under <Control Panel> User Accounts and
Family Safety > Manage User Accounts > Manage Accounts>.
• The project administrator is a member of the local user group "Logon_Administrator" under
<Computer Management > System > Local Users and Groups > Groups/
Logon_Administrator>.
• All intended users are members of the local user group "Siemens TIA Engineer" under
<Computer Management > System > Local Users and Groups > Groups/Siemens TIA
Engineer>
• You have access (local disk or network) to the automation project via the Windows Explorer
of PAM station.
• The IP protocol or ISOon TCP protocol is activated in the AS/PLC stations of the automation
project.
Procedure
1. Open SIMATIC Manager.
2. Select the menu command File > New...
– Assign the name and storage location for the project.
– Use "Project" as the project type to create an individual project.
3. Select the project node and select the menu command Insert > Station > SIMATIC PC
Station.
4. Select the SIMATIC PC station and select the menu command Edit > Object Properties... .
– Enter the name for the PC station in the "Name" text box.
– Enter the Windows computer name in the "Computer name" text box.
– Click "OK".
5. Select the SIMATIC PC station
6. Select the menu command Edit > Open Object.
7. Select the "WinCC application" in the hardware catalog under "SIMATIC PC station > HMI" and
drag it into the configuration table: If the hardware catalog is not visible, select the menu
command View > Catalog.
8. Select the "PDM application" in the hardware catalog under "SIMATIC PC station > PDM" and
drag it into the configuration table:
9. Select the network card "IE General" in the hardware catalog under "SIMATIC PC station > CP
Industrial Ethernet".
Configure the selected IP address for the connection to the plant bus in IE General.
10.Select the menu command Station > Save and compile and Station > Close.
11.Select the project node and select the menu command Insert > Station > SIMATIC 400
Station.
12.Select the SIMATIC 400 station and select the menu command Edit > Object Properties....
– Enter the name of the SIMATIC 400 station in the "Name:" text box.
– Click "OK".
13.Select the SIMATIC 400 station.
14.Select the menu command Edit > Open Object.
15.Select the central rack used in the hardware catalog under "SIMATIC 400 > Rack-400" and
insert it into the configuration using drag-and-drop.
16.Select the power supply used in the hardware catalog under "SIMATIC 400 > PS-400 >
Standard PS-400" and insert it into the central rack using drag-and-drop.
17.Select the CPU used in the hardware catalog under "SIMATIC 400 > CPU-400 > CPU 400-H >
CPU 410-5H" and insert it into the central rack using drag-and-drop. Configure the "PN-IO-X5"
interface with the IP address for connection to the plant bus.
Note
An extension of the S7-400 hardware configuration of the PAM station is not supported.
18.Select the menu command Station > Save and Compile and Station > Close.
19.Select the menu command Options > Configure Network.
20.Select the CPU in the SIMATIC 400 station.
21.Select the menu command Insert > New Connection... .
– Select the WinCC application in the SIMATIC PC station.
– Select the connection type "S7 connection".
– Click "OK".
22.Select the menu command Network > Save and Compile... and Network > Close.
23.In the SIMATIC Manager, select the menu command Options > SIMATIC PDM > Settings... .
– Select the "General" tab.
Enter the path for "Asset export files".
– Select the "Communication" tab.
If HART auxiliary variables are cyclically transmitted in at least one remote I/O station,
do not enable SHC mode.
– Select the "Download" tab.
When this function is managed by the automation system, or the "Synchronization field
device parameters" function is used on a SIMATIC PCS 7 Maintenance Station, do not
enable the "Configuration Flag Reset" function.
– Select the "Maintenance Station" tab.
Assign the current project.
– Select the "Change log" tab.
If you want to save the changes, enable the function.
24.Select the menu command Options > SIMATIC PDM > Roles management... .
Administer the function rights.
You can find information on roles management in the "Roles management" section.
25.Select the menu command View > Process Device Network View.
26.Select the menu command Insert > SIMATIC PDM > 2 networks.
27.Select the "Networks" node
28.Select the menu command Insert > SIMATIC PDM > 4 Communication networks.
Assign the device type "ETHERNET network" and close the dialog by clicking "OK".
29.Select the "ETHERNET network" communication network
30.Select the menu command Edit > Object properties... .
– Select the "Communication" tab.
– Enter the subnet ID of the plant bus.
You can find the subnet ID in HW Config in the properties of the interface for the plant bus
of each AS station or directly in the properties of the plant bus in NetPro.
31.Select the "ETHERNET network" communication network
32.Select the menu command Edit > SIMATIC PDM > Import from HWC station.
– Select the user project.
– Select the AS stations.
The AS stations can be selected individually.
– To import the field devices from the SIMATIC PCS 7 project, click on the "Import" button.
Note
You cannot import your configuration, create it manually in the SIMATIC PDM process device
network view.
Note
When the same station is imported again, the station is not overwritten in the process device
network view. Instead, it is added to the existing stations.
37.Select the Options > Plant hierarchy > Create/update diagnostics screens menu
command.
Note
In this step, unspecified connections are automatically created in NetPro. These may not be
changed or deleted manually.
Additional information
You can find the description of operating in process control in the section"Operator control and
monitoring (Page 147)".
Introduction
Access protection via "SIMATIC Logon Role Management" controls access to device
management, parameter assignment and field device diagnostics.
The following roles have been created for SIMATIC PDM in SIMATIC Logon Role Management by
the system:
• PDM command interface
• Service technician
The roles created by the system can be assigned Windows user groups/users of the local
computer or the domain.
You can add new roles. Assign "Groups and users" and "Function rights" to the roles you have
added.
The function rights are specified by the system. They cannot be deleted, edited or amended.
Additional information
You can find information about SIMATIC Logon Role Management in the manual SIMATIC,
SIMATIC Logon.
You can find information about configuring a role in the section below "How to configure a 'role'".
Requirements
• Groups and users are created in Windows
• Groups and users are members of the "TIA Engineer" group
• At least one user account has administrator rights
Procedure
1. In the SIMATIC Manager, select the menu command Options > SIMATIC PDM > Roles
management... .
2. Select the "Roles" folder.
3. Select the "New role" menu command.
4. Enter a name in the "Role name:" text box.
5. Click "OK".
6. Open the folder with the newly created role.
7. Select the "Groups and users" folders associated with the role.
Result
An additional role has been created.
Introduction
You can use the PAM station to retrieve diagnostic information about AS/PLC stations, remote IO
stations and field devices from the package units and display and monitor them in the process
control.
To do this, you configure a corresponding data block in the package unit for each device to be
monitored. This addition to the configuration is optional and does not change your user
program.
You use these data blocks to provide device-specific status, text, and diagnostic information for
further processing. The devices are divided into the classes AS stations, field devices and remote
IO stations.
This information is read and processed by the PAM station. There is no write access to the
package unit.
The following information can be transmitted:
• Status and maintenance information for displaying and reporting the maintenance status on
the PAM station.
• Detailed diagnostic information, for display in "External diagnostics" view for field devices
(Page 277).
• Status information
• Analog values for monitoring with the "PAM_IF" block and for display in the "Monitoring" view
for analog values (Page 283). You can find information on the configuration under:How to
configure analog value monitoring (Page 79).
A corresponding function module is available for each type for simple data supply of the data
modules. Configuration can easily be performed in the CFC graphical editor using these function
blocks:
• "FB_DB_CPU" for "DB_PAM_CPU"
• "FB_DB_ IM" for "DB_PAM_IM"
• "FB_DB_ CD" for "DB_PAM_CD"
You can find a template for the data and function blocks:
• In the PCS 7 Basic Library as of V9.0 SP2 in the folder "PAMMS > Blocks"
• On PCS 7 USB flash drive as archived library "PAM_Templates.zip" in the folder "Additional
Products > SIMATIC_PAM_STATION".
Note
The data blocks can be used in automation projects for the AS stations of the SIMATIC 4xx, 3xx
and 15xx series, provided that they support the GET functionality.
You can dynamically supply the individual parameters of the data modules with actual values
from your user program.
When entering static information (e.g. for the "LID" parameter), ensure you enter the "actual
value" in the LAD/STL/FBD editor under "View > Data view".
PAM station
• In the ”Process Device Network View”, add CPU, networks, Remote I/O stations, modules,
field devices including addresses, slot numbers (Manually or via import).
• In the ”Plant View” update the Diagnostic Screens.
• Under ”Advanced Diagnostic Settings” (Plant Hierarchy), assign the data block numbers.
• Compile and Download the ”Charts” folder (PAM-AS).
• Compile PAM-OS.
Note
Visualisation of a Package Unit (CPU, I/O station, modules, devices) similar to a PCS 7 Automation
System.
Details
The following sections provide an overview of the structure of the data blocks required for
configuration.
Parameter description
SM_NOKx Status signal modules Connect the group error of the signal
modules here. This information is
passed on in the PAM station to the
module PAM_SM, where it triggers a
corresponding message.
DB_PAM_CPU block
The DB_PAM_CPU block can be installed for the AS/PLC stations. You install a block for each CPU
in a redundant system.
DB_PAM_CD block
The DB_PAM_CD block can be installed in the package unit for each field device.
DB_PAM_IM block
The DB_PAM_IM block can be installed in the package unit for each Remote IO Station . The
information to the RIO modules is also forwarded to the SIMATIC PAM station via it.
Additional information
You can find more information on the block in the PCS 7 Basic Library Online Help.
Introduction
There are two versions for configuring the analog value monitoring in the PAM station:
• By configuring the data connections in the "Advanced Diagnostic Settings".
• By directly installing the monitoring block in a CFC.
Requirements
The project has been created.
You can find information on this in the sections:Sample project as a project basis
(Page 65)andHow to create a project without using the sample project (Page 68).
Procedure
Note
Depending on the input parameter PVx_PU_LK (x: 0,1,2), the analog value is taken from the data
block of the package unit or via the connected input parameter PVx (x: 0,1,2).
You can find more information on the block in the PCS 7 Basic Library Online Help.
Note
This configuration is also applied to the "Advanced Diagnostic Settings > PAM Data Connections"
in the "Generate/update diagnostic screens" dialog.
Note
Depending on the input parameter PVx_PU_LK (x: 0,1,2), the analog value is taken from the data
parameter of the package unit or via the connected input parameter PVx (x: 0,1,2).
You can find more information on the block in the PCS 7 Basic Library Online Help.
Additional information
You can find additional information about the views in the sections ""Monitoring" view for analog
values (Page 283)" and ""PAM data connection" tab (Page 115)".
Introduction
Note
This configuration can be used for the maintenance station in the PDM MS and PAM Station
versions for field devices connected to PROFIBUS DP or PA.
A service bridge can be used to reach field devices that are either connected directly to a
PROFINET network or can only be reached via a PROFINET network. For more information, refer
to entry ID 109747975 in the Industry Online Support.
The IE/PB link is used if it is not possible to communicate with the field devices connected to the
PROFIBUS via an AS station.
The IE/PB Link PN IO link module connects the two network types, Industrial Ethernet and
PROFIBUS.
If you have already planned for an IE/PB Link PN IO link module in the system and configured it
for this purpose, you can continue directly in the section "Procedure 3".
Requirement
The project has been created.
Step 2 - Configure IE/PB Link PN IO link module in the SIMATIC 300 station
1. Select the SIMATIC 300 station in the component view of the SIMATIC Manager.
2. In the detailed view, open HW Config by double-clicking the "Hardware" object.
The hardware configuration of the SIMATIC 300 station opens.
3. If the hardware catalog is not visible, select the menu command View > Catalog.
4. Select the device type Gateway – IE/PB Link PN IO in the hardware catalog under "SIMATIC
300".
Note
The IE/PB Link PN IO link module is a special configuration object.
No other objects, such as profile rails or modules, can be placed in the S7-300 station apart
from this object.
Step 3 - Configure IE/PB Link PN IO link module in the process device network view
1. Configure an Ethernet network in the process device network view.
2. Assign parameters for the Ethernet network with the S7 subnet ID.
3. Configure the IE/PB Link PN IO Link module in this Ethernet network.
4. Assign parameters for the IE/PB Link PN IO link module using the following data:
– With the S7 subnet ID
– With the corresponding IP address
– With the corresponding DP master address
5. Repeat the procedure for any other IE/PB Link PN IO link modules.
Additional information
For additional information on this topic, refer to the SIMATIC NET; S7-CPs for Industrial Ethernet
and PCS 7 Process Control System; SIMATIC PDM manuals.
5.11.1 Requirements
Introduction
The following general settings are required for correct display in process control:
• In the Internet Explorer, the "Display intranet sites in Compatibility View" option must be
disabled in the "Compatibility View Settings".
• The "Language for web content" option must be enabled in the Windows Control Panel under
"Time, Language and Region > Language > Advanced Settings".
The programs or services listed in the following table must be available and configured to
monitor industrial PCs and network objects.
• SNMP service
– SNMP is the Simple Network Management Protocol that is used to manage networks.
– The SNMP service must be configured.
You can find more information about this in the manual Process Control System PCS 7;
PCS 7 PC Configuration.
A network connection must be available to the objects with SNMP functionality to be
included in the diagnostics.
• Diagnostics Monitor
– Diagnostics Monitor is a diagnostics tool that provides the diagnostic data required from
SIEMENS industrial PCs.
– Diagnostics Monitor is called in the header of the faceplate in process control.
– Diagnostics Monitor must be installed and configured.
You can find more information about this in the manual Process Control System PCS 7;
PCS 7 PC Configuration.
– Additional settings
Start the Web server
Start the Management Explorer.
Select Options > Web server.
Authorize Diagnostics Monitor Web server in the Windows firewall
Open the firewall.
Create a new exception/rule for the "MiniWebService.exe" program.
This file is accessed via the Windows Start menu, submenu ...\Siemens\Automation
\DiagnosticManagement\WebServer_DM\Bin.
Note
The systems that are monitored by the MS should be reachable via ping.
Introduction
If an SNMP-compatible object is configured in the OPC server, a device profile and a community
have to be assigned to this SNMP-compatible object.
Overview
The following table shows the assignment of the community to the device profile.
Note
If not explicitly mentioned, "xy" stands for the latest version of the device profile.
Note
"No SNMP" as device profile has the following effects on the diagnostic screens:
• No block icon is created for a network object.
• The block icon for a PC station is created for an industrial PC.
5.11.3 How to assign objects with SNMP functionality to the OPC server
Naming rules
Aspects to be taken into account when naming objects with SNMP functionality:
• Do not use spaces or special characters in module names.
• For IPCs, assign module names that correspond to the computer name of the IPC in the
SIMATIC Manager.
• For all other modules, assign module names that are different from the existing computer
names of PC stations in the project.
• If you use two separate Ethernet networks in your configuration, make sure that both the
names and the IP addresses of the modules are unique across the network.
Requirements
• The HW configuration for the PC objects and network objects is completed.
• The OPC server has been inserted.
You will find more information on this subject in the following sections:
– Configuring the PC station for MS single station system (Page 51)
– How to configure a PC station for an MS server (Page 54)
Procedure
1. Select the OPC server in HW Config, and then select the menu command Edit > Object
Properties....
The "Properties – OPC server" dialog box opens.
2. Open the "SNMP" tab.
3. Enter at least 1000 ms in the "Cycle time" input box.
You can obtain additional information with the "Help" button.
4. Click "Edit plant configuration".
The "Edit plant configuration" dialog box opens.
5. Click "Import".
All objects configured in your project with an IP address are imported.
Note
When you import a CP 1623 / CP 1628, the IP address of the HW Config is imported. If
appropriate, this TCP/IP address is to be replaced by the IP address of the Miniport adapter.
– Timeout:
Enter a value of 9000 ms or higher, depending on the number of objects to be monitored.
You can obtain additional information with the "Help" button.
– SNMP optimization
Activate the check box.
– Comment:
You can enter a comment in this field. This comment is visualized in the faceplate of the
process control system.
8. Click "OK".
The "Edit nodes" dialog box closes and you return to the "Edit plant configuration" dialog box.
9. Click the "Add" button if you want to insert IPCs or other objects with SNMP functionality.
The "Add node" dialog box opens.
10.Enter all required data.
Proceed as described in item 7.
11.Click "OK".
The "Add node" dialog box closes and you return to the "Edit plant configuration" dialog box.
12.Insert additional nodes as required.
13.Click "OK".
The configuration is complete.
14.Compile and download the hardware configuration.
Additional information on this is available in the Process Control System PCS 7;
Engineering System manual.
5.11.4 How to insert the OPC server into the redundant partner
Requirement
The OPC server is configured in the MS server.
You can find additional information on this in the section "How to assign objects with SNMP
functionality to the OPC server (Page 87)".
Procedure
1. In SIMATIC Manager, open the component view.
2. Select the SIMATIC PC station of the MS server.
3. In the detailed view, open HW Config by double-clicking the "Configuration" object.
The hardware configuration of the SIMATIC PC station opens.
4. Select the OPC server.
5. Select Edit > Copy from the menu.
6. Select the SIMATIC PC station of the redundant partner.
7. In the detailed view, open HW Config by double-clicking the "Configuration" object.
The hardware configuration of the SIMATIC PC station opens.
8. Select the position for the OPC server.
9. Select the Edit > Paste command.
10.Select the Station > Save and Compile command.
Introduction
Data tags, alarm tags and alarm texts for all objects with SNMP functionality are generated in the
PCS 7 OS project with tag export.
Requirements
• The diagnostic structure has been created.
• The maintenance station has been compiled.
Procedure
1. Select the OPC server in HW Config, and then select Edit > Object Properties... .
The "Properties – OPC server" dialog box opens.
2. Open the "SNMP" tab.
3. In the "Tag export" group, select the check box
– "Export complete plant configuration" upon initial tag export
– "Export changes only" upon all subsequent tag exports
Note
Field devices are displayed in different areas:
• If you use the PCS 7 Basic Library >= V8.1 in your project, all field devices are displayed in the
field device area.
• If you use the PCS 7 Basic Library < V8.1 in your project, all field devices are displayed in the
AS/System area.
Additional information
You can find additional information about this in the "Relationship between the diagnostic
structure and variant (Page 94)" section.
Procedure
1. Open the plant view in the SIMATIC Manager.
2. Select the object in the tree view:
– If you are using a multiproject, select the object "[name of the project] MP".
– If you are using a single project, select the object "[name of the project]".
3. Select the menu command Options > Plant Hierarchy > Settings... .
4. If you have selected a multiproject, the "Plant Hierarchy - Settings" dialog box opens.
Select the project whose settings you wish to use as a template for the plant hierarchy.
– Click "OK".
The "Customize Plant Hierarchy" dialog box opens.
– Proceed to step 6.
5. If you have selected an individual project or a project within a multiproject, the "Plant
Hierarchy - Settings" dialog box opens.
6. Define the settings for the relevant levels.
Remember that the settings of the plant hierarchy within the multiproject/project are to be
uniform.
7. Activate the "Derive picture hierarchy from the plant hierarchy" check box.
If you do not wish to derive the diagnostic screens from the plant hierarchy for your plant
areas, deactivate the "Picture Tree" check box in the dialog for compiling the OS.
Configure the plant hierarchy for the diagnostic screens in the PCS 7 OS project in the Picture
Tree editor.
8. Enable the "Derive diagnostic screens from the plant hierarchy" check box.
9. Specify the version.
Enable the appropriate option button:
– "Maintenance Station Standard (license required)" option button
– "Maintenance Station Basic (overview screens only)" option button
– "Maintenance Station PDM (no AS diagnostics)" option button
– "SIMATIC PAM Station (subject to licensing)" check box.
10.When creating/updating the diagnostic screens, specify whether the names of the created
hierarchy folders should be derived from the name or the commentary for the hardware
components. Enable the appropriate option button:
– "Derive PH names from the names of the hardware components" option button
– "Derive PH names from the comments of the hardware components" option button
Since there are no restrictions on the characters that can be used for the comment texts,
you can use any type of name.
11.Click "OK".
The "Define Maintenance Station" dialog box opens and all OSs available in the multiproject/
project are shown.
12.Select the OS you want to define as Maintenance Station.
13.Click "OK".
Note
Whenever a user changes the resolution of the runtime in OS project editor, a new overview.pdl
will be created. The old picture will be renamed as Overview_save(x).pdl.
Result
In a multiproject, the "Diagnostics" hierarchy folder is inserted in all the projects within the
multiproject.
• The standard diagnostic structure with the hierarchy folders "AS Objects", "Field Devices",
"Network Objects", and "PC Stations" is automatically created in the project with the MS
server. The structure for the user diagnostics must be created manually.
• In the other projects of the multiproject, only the "AS Objects" and "Field Devices" hierarchy
folders are created automatically within the diagnostics structure.
Note
The "Field devices" area is only created if you use the PCS 7 Basic Library >=V8.1 in the AS.
If you use the PCS 7 Basic Library <=V8.1 in the AS, all field devices are assigned to the "AS system"
area.
Introduction
The diagnostic structure is created differently depending on the variant of the Maintenance
Station.
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Introduction
In process control, links to freely configurable web pages can be called in the overview screen
and the header area of the faceplates; these web pages are used to support the diagnostic
measures.
10 link objects are automatically created by the system.
Automatically created link objects are:
Maintenance link1 to Maintenance link10.
The properties are managed in one language.
A link object has the properties "Name:" and "URL:".
The name of the target address is entered in the "Name:" entry field.
The target address is entered in the "URL:" entry field.
You can change the properties of link objects.
You can restore the diagnostic settings for all lists in the tab using the "Set Default Settings"
button.
Rule
• Maintenance links are always valid for the entire multiproject/project.
• The number of link objects is limited to 10.
Display of the link objects, if this is configured:
– In the overview screen, link object 1 to 10
– In the header of the faceplate link, object 1 to 3
• The automatically generated link objects can be renamed.
• The name of the link object contains a maximum of 24 characters.
Requirement
The Maintenance Station has been created.
Procedure
1. Open the plant view in the SIMATIC Manager.
2. Select the object in the tree view:
– If you are using a multiproject, select the object "[name of the project] MP".
– If you are using a single project, select the object "[name of the project]".
3. Select the menu command Options > Plant Hierarchy > Advanced Diagnostics Settings... .
The "Advanced Diagnostics Settings" dialog box opens.
4. Select the "Functions for maintenance" tab
5. In the "Maintenance links" area, select the maintenance link whose existing properties you
want to change.
6. Click "Properties...".
The "Properties maintenance link" dialog box opens.
7. Enter the desired name for the link object in the "Name:" entry field.
8. Enter the target address in the "URL:" entry field.
9. Click "OK".
The "Properties maintenance link" dialog box closes.
10.Click "OK".
The "Advanced Diagnostics Settings" dialog box closes.
Result
After OS compilation and subsequent download, the modified text is displayed in the process
control.
Additional information
You can find additional information on the overview screen in the section "Calling web pages via
maintenance links (Page 158).
You can find additional information on the faceplate in the section "Screen window title and
header (Page 227).
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Introduction
Maintenance targets can be selected for storage of individual export files in the process control.
The selection is made in the "Maintenance" view of the faceplate.
A target object is created automatically by the system.
Automatically created target object:
The name is Default target. The path is project directory ...\wincproj\<os-name>.
A target object has the properties "Name:" and "Path:".
The name of the target path is entered in the "Name:" entry field.
The target path for the individual export file is entered in the "Path:" entry field.
You can add, change and/or delete target objects.
You can restore the diagnostic settings for all lists in the tab using the "Set Default Settings"
button.
Target directory
The target directory can be configured as a local or network directory.
Note
We recommend that you configure the target directory as a network target directory for a plant
configuration with an MS server and a standby MS server. This will ensure that the export file is
always stored in the same "location", regardless of which MS server is the master at the time the
export is initiated.
Rules
• Maintenance targets are always valid for the entire multiproject/project.
• The name of the target object has a length of not more than 24 characters.
Requirement
The Maintenance Station has been created.
Procedure
The following section describes how to configure, change and delete a target object.
To open the "Advanced Diagnostics Settings" dialog, follow the steps below.
1. Open the plant view in the SIMATIC Manager.
2. Select the object in the tree view:
– If you are using a multiproject, select the object "[name of the project] MP".
– If you are using a single project, select the object "[name of the project]".
3. Select the menu command Options > Plant Hierarchy > Advanced Diagnostics Settings... .
The "Advanced Diagnostics Settings" dialog box opens.
4. Select the "Functions for maintenance" tab
Result
After OS compilation and subsequent download, the modified text is displayed in the process
control.
Additional information
You can find additional information on selecting maintenance targets in the section
""Maintenance" view (Page 246)".
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Introduction
An action to be performed can be assigned to a requested maintenance action in the process
control. The assignment is made in the "Maintenance" view of the faceplate.
Seven action objects are created automatically by the system.
Automatically created action objects are:
• Disassembly
• Device swap
• Calibration
• Zero adjustment
• Cleaning
• Service
• Other
Texts for the automatically created maintenance actions are available in multiple languages.
You can find information on this in the Process Control System PCS 7; Operator Station
configuration manual, section "Setting languages".
An action object has the properties "Name:" and "Name for user:".
The name of the maintenance action is entered in the "Name:" entry field.
The name that a maintenance engineer can select from the drop-down list is entered in the
"Name for user:" entry field.
You can add, change and/or delete action objects.
The number of action objects is not limited.
You can restore the diagnostic settings for all lists in the tab using the "Set Default Settings"
button.
Rules
• Maintenance actions are always valid for the entire multiproject/project.
• The name of an action object contains a maximum of 24 characters.
• The name of the action object is managed in one language.
• The text in the "Name for user:" field is managed in multiple languages.
You can find information on this in the section "Configuring multilingual texts (Page 105)".
Requirements
The Maintenance Station has been created.
Procedure
The following section describes how to configure, change and delete an action object.
To open the "Advanced Diagnostics Settings" dialog, follow the steps below.
1. Open the plant view in the SIMATIC Manager.
2. Select the object in the tree view:
– If you are using a multiproject, select the object "[name of the project] MP".
– If you are using a single project, select the object "[name of the project]".
3. Select the menu command Options > Plant Hierarchy > Advanced Diagnostics Settings... .
The "Advanced Diagnostics Settings" dialog box opens.
4. Select the "Functions for maintenance" tab
5. Click "OK".
The "Add maintenance actions" dialog box closes.
6. Click "OK".
The "Advanced Diagnostics Settings" dialog box closes.
Result
After OS compilation and subsequent download, the modified text is displayed in the process
control.
Additional information
You can find additional information on multilingual configuration of maintenance actions in the
section "Configuring multilingual texts (Page 105)".
You can find additional information on languages in the Process Control System PCS 7; Operator
Station configuration manual, section "Setting languages".
You can find additional information on assigning a maintenance action in the section
""Maintenance" view (Page 246)".
Note
This function is available if you configured the Maintenance Station in the MS Standard version.
Introduction
Since PCS 7 V8.2, user-specific maintenance information texts can be configured in the process
control for displaying detailed diagnostic information in the faceplate.
Sixteen information objects are created automatically by the system.
Automatically created information objects are:
• External service request, no additional information
• Service interval reached
• Different operating state
• Different performance parameters
• Auxiliary energy problem
• Auxiliary material problem
• Mechanical problem
• Electrical problem
• Pneumatic problem
• Calibration request
• Measuring circuit check
• Process-related event
• Cleaning request
• Emptying request
• Wear reserve undershot
• Degree of pollution high
Texts for the automatically created maintenance information are available in multiple
languages.
You can find information on this in the Process Control System PCS 7; Operator Station
configuration manual, section "Setting languages"
An information object has the properties "Name:" and "Name for user:".
The name of the maintenance information is entered in the "Name:" entry field.
The name that is displayed in the faceplate is entered in the "Name for user:" entry field.
You can change the properties of information objects.
You can restore the diagnostic settings for all lists in the tab using the "Set Default Settings"
button.
Rule
• Maintenance information is always valid for the entire multiproject/project.
• The number of maintenance information objects is limited to 16.
• The name of the information object is managed in one language and cannot be changed.
• Maintenance information created by the system can be adapted on a user-specific basis.
• The text in the "Name for user:" field is managed in multiple languages.
You can find information on this in the section "Configuring multilingual texts (Page 105)".
• The following applies to a project created in PCS 7 versions before V8.2.
The maintenance information in the faceplate pre-assigned by the system is only displayed
if the "Advanced Diagnostics Settings" dialog has been opened and confirmed with "OK".
Requirement
The Maintenance Station has been created.
Procedure
1. Open the plant view in the SIMATIC Manager.
2. Select the object in the tree view:
– If you are using a multiproject, select the object "[name of the project] MP".
– If you are using a single project, select the object "[name of the project]".
3. Select the menu command Options > Plant hierarchy > Advanced diagnostics settings... .
The "Advanced Diagnostics Settings" dialog box opens.
4. Select the "Functions for maintenance" tab
5. In the "Maintenance information" group, select the information object whose properties you
want to change.
6. Click "Properties...".
The "Properties maintenance information" dialog box opens.
The previous entries are displayed in the input dialog.
7. Enter the desired text.
8. Click "OK".
The "Advanced Diagnostics Settings" dialog box opens.
– If the change does not affect the other languages, click "No".
– If the change affects the other languages, click "Yes".
The "Advanced Diagnostics Settings" dialog box closes.
9. Click "OK".
The "Properties maintenance information" dialog box closes.
10.Click "OK".
The "Advanced Diagnostics Settings" dialog box closes.
Result
After OS compilation and subsequent download, the modified text is displayed in the process
control.
Additional information
You can find additional information on multilingual configuration of maintenance information
in the section "Configuring multilingual texts (Page 105)".
You can find additional information on languages in the Process Control System PCS 7; Operator
Station configuration manual, section "Setting languages".
You can find additional information on configuring in the section "How to configure the display
of the maintenance information in MS Standard (Page 118)".
You can find additional information on displaying maintenance information in the section
""External diagnostics" view for field devices (Page 277)".
Introduction
Default texts for maintenance actions and maintenance information are available for the
languages installed in the project.
Languages that might typically be installed in the project are:
• German (Germany)
• English (United States)
• French (France)
• Italian (Italy)
• Spanish (Spain, international sorting)
• Chinese (simplified, China)
• Japanese (Japan)
You can display the languages installed in the project.
Select the menu command Options > Language for Display Devices... in SIMATIC Manager.
Requirements
The Maintenance Station has been created.
The desired languages have been installed in each project.
Procedure
1. Select the menu command Options > Language for display devices.
2. Select the desired language as the default language.
3. Click "OK".
4. Select the menu command Options > Plant Hierarchy > Advanced Diagnostics Settings....
5. Select the appropriate text.
6. Click "Properties".
7. Enter the desired text in the "Name for user:" field.
8. Click "OK".
9. To change the text in the selected language only, click "No".
10.Click "OK".
11.Repeat steps 5 to 10 for all texts you want to change in the selected language.
12.Click "OK".
13.Repeat steps 1 to 12 for all texts and languages you want to change.
Result
After OS compilation and subsequent download, the modified text is displayed in the process
control.
Additional information
You can find additional information on languages in the Process Control System PCS 7; Operator
Station configuration manual, section "Setting languages".
Note
The function is available if you configured the maintenance station in the MS Standard
or PDM MS versions.
Introduction
You specify the scope for creating/updating diagnostics screens in the "Automatic positioning of
the block icons in the areas" area of the "Other settings" dialog.
Automatic positioning can be selected for one of the following diagnostic areas.
• AS/system
• Field devices
• User objects
• Network objects
• PC stations
The selection applies to the selected diagnostic area including all subordinate levels.
The system offers the following options:
• Check box cleared
This is the default setting.
When you create/update a screen, all PCS 7 block icons are arranged automatically, starting
in the top left corner.
Screens in which a rack structure (for example, ET 200 central rack) is displayed are
exceptions to this. In this case, the block icons for objects are arranged in the order of their
slots.
After you update/create the diagnostics screens, move the block icons to meet your
requirements. Block icons that have been moved remain in their position after the screen is
updated. New block icons are added in the top left corner of the screen.
Note that adding new block icons may cause icons to overlap.
Block icons to be deleted are removed from the screen. Their position in the screen remains
unoccupied.
• Check box selected
The block icons for the selected diagnostic area are repositioned automatically.
All block icons are repositioned.
Requirement
The Maintenance Station has been created.
Procedure
1. Open the plant view in the SIMATIC Manager.
2. Select the object in the tree view:
– If you are using a multiproject, select the object "[name of the project] MP".
– If you are using a single project, select the object "[name of the project]".
3. Select the menu command Options > Plant Hierarchy > Advanced Diagnostics Settings....
The "Advanced Diagnostics Settings" dialog box opens.
4. Select the "Other settings" tab.
5. Select the desired diagnostic area.
6. Click "OK".
These settings are saved retentively.
Result
When the "Create/update diagnostic screens" function is executed, the block icons for the
selected diagnostic area are repositioned automatically.
After OS compilation and subsequent download, the changes are applied in the process control.
Additional information
You can find additional information in the section "Creating/updating the diagnostic screens
(Page 135)"
5.13.2.2 Directory of the filtered total export and the log files of the parameter export
functions
Introduction
In the "Directory of the filtered total export and the log files of the parameter export functions"
area of the "Other settings" dialog, you specify the user-specific storage location for the files of
the (filtered) total export.
The user-specific target directory can be configured as an absolute or relative path.
In a redundant system, the total export file is saved on the MS server and on the redundant
partner when using an absolute path.
Requirement
The Maintenance Station has been created.
Procedure
1. Open the plant view in the SIMATIC Manager.
2. Select the object in the tree view:
– If you are using a multiproject, select the object "[name of the project] MP".
– If you are using a single project, select the object "[name of the project]".
3. Select the menu command Options > Plant Hierarchy > Advanced Diagnostics Settings....
The "Advanced Diagnostics Settings" dialog box opens.
4. Select the "Other settings" tab.
5. Specify the storage location for the files of the filtered total export and the log files of the
parameter export .
Note
• Additional Export Path stores both Filtered complete Export and log files of Parameter
Data Export.
• The existing export files are not deleted with the addition of new files.
6. Click "OK".
These settings are saved retentively.
Result
After OS compilation and subsequent download, the setting is applied in the process control and
saved in the "@ExportPath" tag.
Files of the (filtered) total export are additionally stored at the specified storage location.
Note
If the user removes the storage path in Advanced Diagnostic Settings, @ExportPath Tag will be
removed from internal tag list.
Note
The function is available if you configured the maintenance station in the MS Standard
or PDM MS versions.
Introduction
In the "Navigation information in the screen" area of the "Other settings" dialog, you specify
whether and at which location the path will be displayed within the plant hierarchy in the
diagnostic screen in the process control.
The path can be displayed at the following positions in the diagnostic screen:
• Top left
• Top center
• Top right
• Bottom left
• Bottom center
• Bottom right
The overview screen of the diagnostic screens is not affected by these settings.
Requirement
The Maintenance Station has been created.
Procedure
1. Open the plant view in the SIMATIC Manager.
2. Select the object in the tree view:
– If you are using a multiproject, select the object "[name of the project] MP".
– If you are using a single project, select the object "[name of the project]".
3. Select the menu command Options > Plant Hierarchy > Advanced Diagnostics Settings....
The "Advanced Diagnostics Settings" dialog box opens.
4. Select the "Other settings" tab.
5. Select the "Display" check box.
6. Select the position for the display of the path in the diagnostics screen.
7. If you want to have the block icons repositioned, select the "Re-position block icons" check
box.
8. Click "OK".
These settings are saved retentively.
Result
When the "Create/update diagnostic screens" function is run, the associated path will be
displayed in the diagnostic screens at the selected position.
After OS compilation and subsequent download, the changes are applied in the process control.
Note
If block icons and path information overlap in the diagnostic screens, use the "Re-position block
icons" option.
Note
The function is available if you configured the maintenance station in the MS Standard
or PDM MS versions.
Introduction
The hierarchy and objects of the PC station and network objects areas are displayed in the tab.
You can make structural and block icon changes for custom process control visualization.
The tab has a similar structure to the Explorer with a tree and list view.
The tree view shows the folder structure. This is the basis for the hierarchy of the diagnostic
screens.
The individual objects are displayed in the list view. This is the basis for the block icons for the
diagnostic screens.
Operator input
Tree view area (hierarchy)
Create subfolders in the tree view to create a hierarchy. You can drag-and-drop individual objects
to the subfolders. You can select multiple components.
A combination of PC stations and network objects is possible.
You can add, delete and rename subfolders.
• Assign a unique name or change the name when you add a subfolder.
This name is then used when you create diagnostic screens.
• If you delete a folder, you delete all the subfolders that it contains.
All objects assigned to these folders are assigned to the higher-level folder when the original
folder is deleted.
The overview folder for PC stations and network objects cannot be deleted or renamed.
• You can also create empty subfolder.
Empty subfolders are taken into consideration under the following conditions when creating
the diagnostic screens:
– At least one lower-level object has been assigned to the empty hierarchy folder.
– The empty subfolder is not created as the lowest hierarchy folder.
• "Create diagnostic screens" creates a group display in the higher-level screen for each
available subfolder.
List view area (objects)
The following information is displayed in the individual columns of the list view:
• Name of the object
– Derived from the PC station name and OPC server configuration
– Cannot be modified in the editor
• Block icon
– Type of block icon to be used when creating the diagnostic screen
– Cannot be modified in the editor
Result
Closing the editor with the "OK" button saves all configuration changes in the background.
There is no direct derivation of the plant hierarchy.
The following actions are then performed during the creation/update of diagnostic screens:
• The structure and diagnostic screens in the plant hierarchy are created or deleted.
• The block icons required for OR operations for group display information in the diagnostic
hierarchy are added automatically.
Note
This function is available if you configured the maintenance station in the PAM Station version.
Introduction
In process control, user-specific maintenance information texts can be displayed in the faceplate
to provide detailed diagnostics information.
It is possible to display up to 16 information texts per device class. The following classes are
available:
• AS stations
• Remote IO stations (modular stations)
• Field devices (non-modular devices)
The following information texts are available by default:
• External service request, no additional information
• Service interval reached
Rule
• Maintenance information is always valid for the entire project.
• The number of maintenance information items per type is limited to 16.
• The name of the information object is managed in one language and cannot be changed.
• Maintenance information created by the system can be adapted on a user-specific basis.
• The text in the "Name for user:" field is managed in multiple languages.
You can find information on this in the section "Configuring multilingual texts (Page 105)".
Requirement
The PAM station has been created.
Procedure
1. Open the plant view in the SIMATIC Manager.
2. In the tree view, select the object "[Name of the project]".
3. Select the menu command Options > Plant Hierarchy > Advanced Diagnostics Settings... .
The "Advanced Diagnostics Settings" dialog box opens.
4. Select the tab "PAM information text".
5. In the corresponding "Maintenance information" group, select the information object from
which you want to change the previous properties.
6. Click "Properties...".
The "Properties maintenance information" dialog box opens.
The previous entries are displayed in the input dialog.
7. Enter the desired text.
8. Click "OK".
The "Advanced Diagnostics Settings" dialog box opens.
– If the change does not affect the other languages, click "No".
– If the change affects the other languages, click "Yes".
The "Advanced Diagnostics Settings" dialog box closes.
9. Click "OK".
The "Properties maintenance information" dialog box closes.
10.Click "OK".
The "Advanced Diagnostics Settings" dialog box closes.
Result
The changed text is displayed in the process control after the OS compiling.
Additional information
You can find additional information on multilingual configuration of maintenance information
in the section "Configuring multilingual texts (Page 105)".
You can find additional information on languages in the Process Control System PCS 7; Operator
Station configuration manual, section "Setting languages".
You can find additional information on configuring in the section "How to configure the display
of the maintenance information in PAM Station (Page 119)".
You can find additional information on displaying maintenance information in the section
""External diagnostics" view for field devices (Page 277)".
Note
This function is available if you configured the maintenance station in the PAM Station version.
Introduction
In the area "Advanced diagnostic settings" in the "PAM other settings" dialog, you define the
scope of the PDM objects for the PAM station.
The hierarchy and objects of the PC station and network objects areas are displayed in the tab.
You can make structural and block icon changes for custom process control visualization.
The tab has a similar structure to the Explorer with a tree and list view.
The tree view shows the folder structure. This is the basis for the hierarchy of the diagnostic
screens.
The individual objects are displayed in the list view. This is the basis for the block icons for the
diagnostic screens.
Operator input
Selection and filter area
• Select the check box "Hide signal modules" to hide the signal modules in the tree view.
• You can filter the list view by entering text in the "Filter" box. The filter searches only in the
"Device name" box. You can also filter for parts of words, control characters are not required
in the entry.
Tree view area (hierarchy)
• In the tree view, the configuration of the SIMATIC PDM process device network view is
displayed at package unit (DSGW) level.
• Depending on the selection, the corresponding devices are displayed in the "List view" area.
If the top node "Networks" is selected in the tree view, all configured devices are displayed.
• If the package unit is selected, you can assign the DB numbers for the devices of an entire
package unit via the shortcut menu "Assign DB numbers". The number band starts with the
entry in the "Start value for DB numbers:" box for the first device and then increments
automatically.
• When the "Networks" node is selected, you can assign the DB numbers for all configured
package units via the "Assign DB Numbers" shortcut menu. The "Start value for DB numbers:"
is the start value for each package unit.
Result
Closing the editor with the "OK" button saves all configuration changes in the background.
There is no direct derivation of the plant hierarchy.
The following actions are then performed during the creation/update of diagnostic screens:
• The charts for the diagnostic screens and analog value processing are created or deleted.
• The structure and diagnostic screens in the plant hierarchy are created or deleted.
Note
This function is available if you configured the Maintenance Station in the MS Standard version.
Introduction
This section describes the configuration steps for displaying the maintenance information in the
process control.
Requirements
• The maintenance information has been created.
You can find information on this in the section "Configuring maintenance information
(Page 103)".
• Channel blocks of the Advanced Process Library are applied (in PCS 7 V8.2 or higher).
Procedure
1. Activate the "Bit 10" at the channel block of the input "Feature".
2. Interconnect the "MS_Ext" input on the channel block with the signals of the external
maintenance state of the user program.
You can use the "MSTOu" converter block for this.
3. Interconnect the "Text_Ref" input on the channel block with the signals you use for displaying
the external diagnostic information.
You can use the "BO_W" converter block for this.
The individual bits of the "Text_Ref" input activate the state display in the faceplate in the
"External diagnostics" view in process mode.
Note
Maintenance demanded and maintenance required
Only the external maintenance states "Maintenance demanded" (corresponds to significance 6)
and "Maintenance required" (corresponds to significance 5) are taken into account in the
diagnostics block.
These maintenance statuses trigger the messages "Maintenance demanded (external)" and
"Maintenance required (external)" in the process control.
Note
Multiple channel blocks for HART modules
When HART modules and auxiliary variables are used, you use multiple channel blocks for the
same channel of the module.
The above-mentioned procedure must be performed for each channel block.
Result
After AS and OS compilation and subsequent download, the maintenance information is
displayed in the process control.
Additional information
You can find additional information on displaying maintenance information in the section
""External diagnostics" view for field devices (Page 277)".
5.14.2 How to configure the display of the maintenance information in PAM Station
Note
This function is available if you configured the maintenance station in the PAM Station version.
Introduction
This section describes the configuration steps for displaying the maintenance information in the
process control.
Requirements
• The maintenance information has been created.
You can find information on this in the section ""PAM information text" tab (Page 112)".
• Data blocks are created in the package unit and configured accordingly.
Procedure
• Write the "DD" parameter of the corresponding data block bit-by-bit in the package unit.
Result
Depending on the value set in the "DD" parameter, the maintenance information is marked in the
"External Diagnostics" view for field devices.
Additional information
You can find additional information on displaying maintenance information in the section
""External diagnostics" view for field devices (Page 277)".
5.15.1 Overview
Note
The user diagnostics is available for the maintenance station in the MS Standard and PAM Station
variants.
Introduction
Passive or indirect objects without self-diagnostics (for example, pumps, motors, control loops)
can be monitored with the help of the user diagnostics. A "user" area is created within the
diagnostic structure for this purpose.
You can perform the following tasks in the "user" area:
• Creating individual diagnostic structures
• Creating project-specific diagnostics rules
• Configuring condition monitoring functions
Introduction
You create the user diagnostic structure in the project with the AS and the project with the
Maintenance Station. If the AS and the Maintenance Station are in different projects of a
multiproject, configure the CFCs in the project with the AS for the user diagnostic area and, in
the project with the Maintenance Station, configure the OS pictures for the user diagnostic area.
The user diagnostic area must be created in both projects.
Requirement
The diagnostic structure has been created.
Procedure
1. Open the plant view in the SIMATIC Manager.
2. In the plant hierarchy, select a project for which you wish to create a user diagnostic structure.
3. In the tree view, select the diagnostic hierarchy folder directly below which the "AS objects"
hierarchy folder is located.
4. Select the menu command Insert > Technological Objects > Hierarchy Folder.
Note
There may only be one hierarchy folder created for the user diagnostic structure under the
"Diagnostics" hierarchy folder.
8. If you have not created the user diagnostic structure in the project of the MS server, you must
update the plant hierarchy.
You can find additional information about this in the section "How to update the user
diagnostic structure (Page 126)".
Introduction
The "AssetM" block is used to monitor user-specific sections of the plant. This block is integrated
into a CFC. Multiple blocks can be integrated into a CFC.
Note
The procedure detailed here also applies to the AS system and field devices areas.
Requirement
The user diagnostic structure has been created.
Procedure
1. In the tree view, select the hierarchy folder in which you are creating a CFC.
2. Select the menu command Insert > Technological Objects > CFC.
A new CFC is created.
3. Select the CFC in the detail view.
5. Mark the CFC in the detail view and select the menu command Edit > Open Object.
6. Select the "AssetM" block from the PCS 7 Advanced Process Library.
7. Drag-and-drop the block into the CFC.
8. Interconnect the signals, which are to be displayed via the PCS 7 Maintenance Station, using
the "AssetM" block.
You will find additional information on the "AssetM" block in the Online Help for the block.
9. Execute steps 1 to 7 if you want to create additional CFCs.
Additional information
Additional information on this is available in the Process Control System PCS 7;
Engineering System manual.
5.15.4 Assigning parameters for the "AssetM" block using SIMATIC PDM
Overview
After the "AssetM" block has been placed in the CFC chart, interconnect the parameters that are
to be used.
To display information in the faceplate from SIMATIC PDM for the monitored object during
process control, a SIMATIC PDM object must be created for each "AssetM" block in the process
device plant view.
This SIMATIC PDM object saves the rating plate (identification data) and the diagnostic texts. The
"AssetMon" device is assigned to the SIMATIC PDM object.
The PLT ID is a connection parameter between a SIMATIC PDM object (EDD/FDI parameter data)
and the faceplates in the Maintenance Station.
The PLT-ID is linked to the SIMATIC PDM object.
Procedure
The PDM object is created in SIMATIC Manager as follows:
1. Select View > Process Device Plant View in SIMATIC Manager.
2. Select a project in SIMATIC PDM in which you want to insert the SIMATIC PDM object.
3. Select File > New object.
Note
The PLT ID cannot be changed or deleted.
Additional information
You can find additional information on the "AssetM" block in the manual Process Control
System PCS 7; Advanced Process Library.
You will find information on operating states in the sections ""Diagnostics" view for user objects
(Page 278)" and ""Monitoring" view for user objects (Page 280)".
5.15.5 Assigning parameters for the "AssetM" block without using SIMATIC PDM
Overview
After the "AssetM" block has been placed in the CFC chart, interconnect the parameters that are
to be used.
To display information on the monitored object in the faceplate during process control, assign
parameters for the text to be displayed at the block.
Note
A "0" must be entered as the value for the PLT_ID parameter at the "AssetM" block.
The following table shows at which block parameter you configure the text for display in the
corresponding view.
Additional information
You can find additional information on the "AssetM" block in the manual Process Control
System PCS 7; Advanced Process Library.
You will find more information on operating states in the sections ""Diagnostics" view for user
objects (Page 278)" and ""Monitoring" view for user objects (Page 280)".
Introduction
The following steps are only required if you have created a user diagnostic structure in a location
other than the MS server project.
You have to update the plant hierarchy in the multiproject.
Procedure
1. In the "plant hierarchy", select the project for which you have created a user diagnostic
structure.
2. In the shortcut menu, select the menu command Plant Hierarchy > Update in
Multiproject.
The "Plant Hierarchy - Update in Multiproject" dialog box opens.
3. Click "OK".
The "Plant Hierarchy - Update in Multiproject (target projects)" dialog box opens.
4. Enable the check box for the MS server's current project.
5. Click "OK".
6. Perform steps 1 to 6 for all the projects in a multiproject for which you have created a user
diagnostic structure.
Result
The user diagnostic hierarchy of the other projects is added to the plant hierarchy in the project
of the MS server.
Introduction
You create the user diagnostic screens in the hierarchy folders of the user-specific diagnostic
structure in the project. In an MS single station system, this is the MS project. In an MS multiple
station system, it is the MS server project.
You can create one user diagnostic screen per hierarchy folder.
Requirements
• The user diagnostic structure has been created.
• The CFCs for the user diagnostic structure have been created.
• A multiproject update is performed for multiprojects.
Procedure
1. Open the plant view in the SIMATIC Manager.
2. In the tree view, select the hierarchy folder for which you want to create the user diagnostic
screen.
3. Select the menu command Insert > Technological Objects > Picture.
4. Enter a short, unique name and confirm with the Enter key.
The name is applied.
5. Click "OK".
6. Select the picture in the detail view.
7. Select the menu command Edit > Object properties... .
8. Select the "Block icons" tab.
9. Select the "Derive the block icons from the plant hierarchy" check box.
10.Repeat steps 2 through 9 for all hierarchy folders into which you wish to insert user diagnostic
screens.
5.15.8 How to create the group display hierarchy for the user diagnostics
Introduction
You will need to refer to the information in this section if you have added a user-specific
diagnostic structure to the diagnostic structure.
Requirement
The PCS 7 OS project is opened:
• In an MS single station system, this is the PCS 7 OS project of the MS.
• In an MS multiple station system, it is the PCS 7 OS project of the MS server.
Procedure
1. In the WinCC Explorer tree view select the "Project Editor".
2. Open the shortcut menu and select the menu command Open.
The "OS Project Editor" dialog box opens.
3. Select the "Message display" tab.
4. Enable the "Create/Update Group Displays" check box in the "Group display hierarchy" group.
5. Click "OK".
The group displays for the hierarchy calculation are automatically inserted into the screens
when the hierarchy is saved, the OS is compiled or the OS is downloaded.
Overview
If you have configured devices with SIMATIC PDM, the following requirements must be met on
the engineering station for visualization in the process control.
• Installation
The SIMATIC Process Device Manager (SIMATIC PDM) add-on package (requires a license) is
installed.
• In the Windows Control Panel
– The Microsoft Internet Information Server (IIS) with ASP.NET support is installed.
– The rule in the firewall is enabled.
– The SIMATIC PDM users are added to the Logon_Administrator Windows group.
• In the Windows Start menu
– The SIMATIC PDM Web server is configured.
• In SIMATIC Manager:
– A PDM application is inserted in the PC station of the engineering station.
– In the SIMATIC PDM "Settings..."
The path to the maintenance project is entered on the "Maintenance Station" tab.
For multi-user engineering with several engineering stations, the path must be entered
for each engineering station.
– In the SIMATIC PDM "Role management..."
All Windows users who use SIMATIC PDM Web are assigned the "Service user" role.
Note
You can configure more than one ES within a PCS 7 project. In this case the "master" ES may
contain the "PDM application".
Additional information
You can find information about this in the following documents:
• Online Help for SIMATIC PDM
• Manual Process Control System PCS 7; Help for SIMATIC PDM
Overview
Note
You use this function during process control when the maintenance station is used in the MS
Standard, PDM MS, or PAM Station versions.
Identification data from all diagnostics-capable objects (such as field devices, PCs, AS objects,
network objects) can be exported.
With a complete export, the data from all the objects with diagnostic functionality are exported
to the export file "@XML_Export.sml".
The complete export file is stored in the default target directory on the MS in the "AssetExport"
folder of the OS project directory.
The complete export file is stored on both partners in a redundant system.
The complete export file can also be stored in a configured target directory (e.g., for reuse of the
data in external systems).
You can find information on this in the section "Directory of the filtered total export and the log
files of the parameter export functions (Page 108)".
In the process control, the system allows you to display the data of the last complete export in
filtered form and to export this data.
Additional information
You can find additional information about displaying and exporting the data in process control
in the section "Functions in the overview screen (Page 158)".
Overview
Note
You use this function when the maintenance station is used in the MS Standard, PDM MS, or PAM
Station versions.
Data of a diagnostics-capable object (such as field devices, PCs, AS objects, network objects) can
be exported.
With a single export, the data of a diagnostics-capable object are written to an export file.
The file name is automatically generated by the system.
The individual export file is stored in the default target directory on the MS in the "AssetExport
\Out" folder in the OS project directory.
The individual export file is stored in the standard target directory on the connected OS server
(current preferred server) in a redundant system.
The individual export file can also be stored in a configured target directory (e.g. for reuse of the
data in external systems).
You can find information on this in the section "Configuring maintenance targets for individual
export (Page 98)".
Note
Individual Export is available only in English Language irrespective of the Runtime Language.
Additional information
You can find additional information about displaying and exporting the data in the process
control in the section ""Maintenance" view (Page 246)".
Note
This function is available for the Maintenance Station in the MS Standard version.
Introduction
You must make interconnections on the blocks in the CFC for the release request.
We recommend that the configuration steps be taken into consideration when the typicals are
created.
Requirements
• The CFC typicals have been created.
• The PCS 7 Advanced Process Library V8.2 or higher is used.
Procedure
1. Open the CFC typical.
2. Interconnect the output parameter MS_Req of the channel block with a free input parameter
ExtMsg of the technological block.
3. Change the message class of the utilized external message on the technological block to the
message class not requiring acknowledgment "Request for operator input - General".
4. Adapt the event text as desired.
You can connect the release request signals of multiple channel blocks to the technological block
with an OR operation.
Result
The release request "Sequence for maintenance (Page 303)" can be used.
After AS and OS compilation and subsequent download, the changes are applied in the process
control.
Compile and download the OS in which the technological block will be displayed.
Additional information
You can find additional information on maintenance in the section "Overview of maintenance
(Page 301)" and in the manual Process Control System PCS 7; Advanced Process Library.
Note
This function is available for the Maintenance Station in the MS Standard version.
Introduction
You must make interconnections on the blocks in the CFC chart for the maintenance release.
We recommend that the configuration steps be taken into consideration when the typicals are
created.
Requirement
• The CFC typicals have been created.
• The PCS 7 Advanced Process Library is used.
Procedure
1. Open the CFC typical.
2. Interconnect the output parameter MS_Release of the technological block with the input
parameter MS_Release of the channel block.
You can interconnect the maintenance release of a technological block to multiple channel
blocks.
3. Interconnect the output parameter OosAct of the channel block with the input parameter
OosLi of the technological block.
You can connect the "In maintenance" information (OosAct) of multiple channel blocks to the
technological block with an OR operation.
4. Use the feature bit "Reaction to the out of service mode" to define the desired behavior of the
technological block.
Note
Multiple channel blocks for HART modules
When HART modules and auxiliary variables are used, you use multiple channel blocks for the
same channel of the module.
The above-mentioned procedure must be performed for each channel block.
Result
The maintenance release "Sequence for maintenance (Page 303)" can be used.
After AS and OS compilation and subsequent download, the changes are applied in the process
control.
Compile and download the OS in which the technological block will be displayed.
Additional information
You can find additional information on maintenance in the section "Overview of maintenance
(Page 301)" and in the manual Process Control System PCS 7; Advanced Process Library.
Introduction
The diagnostic screens in the diagnostics area with their block icons are created or updated with
this function.
The "@@maintenancetypicals.pdl" file contains all the templates for block icons which are used
to display the diagnostic information.
If you execute the "Create/update diagnostic screens", PCS 7 automatically uses block icons from
this file. This file is installed as standard during the installation of PCS 7.
You can customize block icons to your specific requirements.
Note
If you want to customize the standard block icons included in the @@maintenancetypicals.pdl
file, do not change this file. All changes in this file are overwritten by an update.
Always create a new file. The name of the file starts with the fixed name component
"@maintenancetypicals". You can specify the rest of the file name yourself. Insert the required
block icons there and customize them.
The process is exactly the same as for adapting the standard block icons.
You can find additional information about this in the section "Example: Creating object
templates" in the WinCC Information System online help.
You can find additional information on positioning block icons in the section "Automatic
positioning of block icons in the areas (Page 106)".
Requirements
The configuration must have the following status:
• The settings relating to the diagnostic structure have been made.
You can find information on this in the section "How to make the settings in the plant
hierarchy (Page 92)".
• The "Language for display devices" is set as the default language in the SIMATIC Manager.
Texts displayed during process control are generated in this language.
• When you use SIMATIC PDM, the maintenance project is configured in the settings for the
SIMATIC PDM project.
Procedure
1. Open the SIMATIC Manager and activate the plant view.
2. Select the required hierarchy folder in the tree view.
– If you want to create diagnostics screens for the multiproject/project, select the
multiproject/project.
– If you wish to create diagnostic screens for certain hierarchy folders, select the required
hierarchy folder in the maintenance station.
3. Select the Options > Plant Hierarchy > Create/Update Diagnostics Screens menu
command.
4. If you have already compiled the AS charts, no other dialog box is opened, and the diagnostic
screens are created/updated directly.
Proceed to step 6.
5. If you haven't compiled the AS charts yet, the "Create module drivers" dialog box is opened
one after another for every CPU for which this function has not been executed yet.
Click "OK" in all dialog boxes to create the required diagnostic blocks.
Note
If you click "Cancel" in this dialog box, no module drivers are created for this CPU, and the
diagnostic screens are not updated!
6. The "Create/update diagnostic screens" dialog box opens after the completion of the
generation process.
Click "Yes".
The function log is displayed in the "WordPad" editor. If error messages appear, rectify the
errors and run the function again.
7. Close the "WordPad" editor.
Result
The diagnostic screens are created or updated.
After OS compilation and subsequent download, the diagnostic screens are displayed in the
process control.
Requirements
• The configuration and parameter assignment of the devices (for example, field devices, PCs,
AS objects, network objects) has been completed.
• The "Create/update diagnostics screens" function has been executed.
• The project is open in SIMATIC Manager.
Additional information
You can find information about the function "Compile and Download Objects" in the "Compiling
and Downloading" section of the Process Control System PCS 7; Engineering System manual.
Server data
Before an MS or OS/MS client is downloaded, it must be assigned the relevant OS server. This
loads the server data to the MS or MS/OS client project.
Downloading
The MS client or OS/MS client is downloaded in exactly the same way as an OS client. The MS
client in the engineering station does not have to be downloaded.
Additional information
Additional information is available in the manual Process Control System PCS 7; Operator Station
in the sections "Downloading the server data" and "How to compile and download several
operator stations".
You change the version in the SIMATIC Manager in the plant hierarchy settings. You can find
additional information about this in the section "How to make the settings in the plant hierarchy
(Page 92)"
If you change the version of the maintenance station, you must observe the following:
• MS Standard to MS Basic
– The diagnostic structure below the AS objects, the diagnostic structure of the field devices
and the user diagnostic structure including the contained pictures are deleted.
• MS Basic to MS Standard
– The diagnostic structure of the AS objects is regenerated.
– The diagnostic structure of the field devices is created.
– The diagnostics structure for user objects is created when they are customized.
• MS Standard to PDM MS
– The diagnostic structure of the AS objects including the contained pictures is deleted.
– The diagnostic structure of the field devices is regenerated.
• PDM MS to MS Standard
– The diagnostic structure of the field devices including the contained screens is
regenerated.
– The diagnostic structure of the AS objects is generated.
• MS Basic to PDM MS
– The diagnostic structure of the AS objects including the contained pictures is deleted.
– The diagnostic structure of the field devices is created.
• PDM MS to MS Basic
– The diagnostic structure of the field devices and the user diagnostic structure including
the accompanying screens are deleted.
– The diagnostic structure of the AS objects is generated.
• Changing the version to PAM Station
– There is no option for changing one of the other versions to PAM Station.
– In this case, disable the function "Derive diagnostic screens from the plant hierarchy".
– Enable the function again with the required value.
After changes, you may have to perform the following tasks:
• Creating/updating the diagnostic screens (Page 135)
• Compile and download (Page 137)
• Assigning the server data and downloading of a client (Page 138)
Changes in the hardware configuration of the engineering system affect the displays in the
diagnostic screens.
After changes, perform the following tasks:
• Creating/updating the diagnostic screens (Page 135)
• Compile and download (Page 137)
Note
This function is available for the Maintenance Station in the MS Standard and MS Basic version.
Perform the following tasks if a subproject with an AS is added after creating the diagnostics
structure:
• Enable diagnostics derivation in the plant hierarchy settings of the newly added subproject.
Confirm the following information.
Exit the dialog with "OK".
• Creating/updating the diagnostic screens (Page 135)
• Compile and download (Page 137)
Note
This function is available for the Maintenance Station in the MS Standard and MS Basic version.
Perform the following tasks if an OS server is added after creating the diagnostic structure in the
multiproject/project:
• Assign server data of the OS server to the MS server
You can find more information on this topic in the Process Control
System PCS 7; Operator Station manual in the section "How to load server data".
• Load MS server
You can find additional information about this in the "Compile and download (Page 137)"
section.
Note
This function is available for the Maintenance Station in the MS Standard and MS Basic version.
If an OS server is defined at a later point in time as MS server in a plant in operation, you need
to perform not only the configuration tasks described for the MS server but also a download for
the OS client, which assumes the role of the OS/MS client.
For additional information on downloading, refer to the section "Assigning the server data and
downloading of a client (Page 138)".
Note
This function is available for the Maintenance Station in the MS Standard and MS Basic version.
Perform the steps in the table if you subsequently use another OS as MS server in an operating
plant.
This assigns MS functionality to another OS.
The steps in the table apply to the example configuration. The example configuration consists of
a redundant OS server (original MS) and a redundant MS server (new MS).
Note
This function is available for the Maintenance Station in the MS Standard and MS Basic version.
If you change the storage location of a subproject with the "Save As" function, you must stop the
SIMATIC PDM Asset Service before performing the "Save As" operation.
When the "Save As" operation is finished, you must restart SIMATIC PDM Asset Service.
Introduction
During deletion of the diagnostic structure, the following is deleted:
• Diagnostics hierarchy folder with all subfolders
• Target objects
• Action objects
• Link objects
Requirement
• The diagnostic structure and/or user diagnostic structure has been created.
Note
If you have manually changed diagnostic screens, make sure that you make a backup copy
before deleting, because all changes will be lost after deleting and recreating the diagnostic
structure.
Procedure
1. Open the plant view in the SIMATIC Manager.
2. Select the object in the tree view:
– If you are using a multiproject, select the object "[name of the project] MP".
– If you are using a single project, select the object "[name of the project]".
3. Select the menu command Options > Plant Hierarchy > Settings... .
The "Plant Hierarchy - Settings" dialog box opens.
4. Proceed as follows if you have selected a multiproject:
– Click "OK".
The "Plant Hierarchy - Settings" dialog box opens.
– Proceed to step 6.
5. If you have selected an individual project or a project within a multiproject, the "Plant
Hierarchy - Settings" dialog box opens.
6. Disable the "Derive diagnostic screens from the plant hierarchy" check box.
7. Click "OK".
Note
The complete diagnostic structure and all the diagnostic screens are deleted, including the
user diagnostic structure.
The charts with the diagnostic blocks and the charts of the user diagnostics are not deleted
during this process; they remain in the chart folders for the S7 programs.
PDM MS
Before activating process control, check the setting for the PCS 7 OS project type in WinCC
Explorer. A single station project must be set as the project type.
Activate process control in WinCC Explorer using the "Activate" button.
User administration
Creation of users and assignment of user rights for operator control and monitoring in pictures,
faceplates, alarm lists and for operation of the system functions is the same as in PCS 7 OS.
You can find additional information on this topic in the Process Control System PCS 7;
Operator Station manual and the WinCC Information System online help.
NOTICE
User right "Higher order process controlling"
When the user right "Higher order process controlling" is used, the operating system can be
accessed in certain scenarios.
Example: Web interface of a network component with integrated firmware loader.
OS simulation
You can only use the OS simulation function in the MS Standard or MS Basic version.
OS simulation for a PCS7 Maintenance Station in MS Standard and MS Basic is possible only to
a limited extent (for example, no identification or diagnostics data).
Additional information
You can find additional information on this in the manual Process Control System
PCS 7, OS Process Control.
This section only describes the displays and buttons that are specific to the Maintenance Station.
In addition to the display, an AS process control message without area information is generated.
The message is triggered as soon as at least one highest priority message in the "Diagnostics"
area is pending.
As soon as all highest priority messages in the "Diagnostics" area have gone out, the message
without area information is assigned the status "outgoing".
For more information on configuration of the message priority see the manual Process Control
System PCS 7; Operator Station.
The following table shows an example of the assignment of the displays to their area and
describes the possible states that each display can have.
Note
If no maintenance group display is created for an area in the overview screen of the "Diagnostics"
area, the corresponding display is also not shown.
The area key is used to open the overview screen for the diagnostics area.
Navigation through the picture hierarchy is similar to navigation through the picture hierarchy
of the OS areas.
The number in the priority column indicates the priority of the display. The lowest number has
the highest priority.
Note that unacknowledged messages have a higher priority than acknowledged messages.
(1) At least one message is locked. "Lock messages" can be performed for objects of the AS/
System areas, user objects and field devices.
This section only describes the buttons that are specific to the Maintenance Station.
Locking/unlocking messages
If a picture is open within an AS in the AS/System and Field devices area, messages can be
locked or unlocked for the objects shown in this picture and their subordinate components.
If a screen is open below the overview screen in the User objects area, messages can be locked
or unlocked for the objects shown in this screen and their lower-level components.
This function is not available in the PC stations and Network objects areas and also, it is not
available if the Diagnostics Overview screen is selected in the working area.
You can find additional information on enabling/disabling messages in the section: "How to lock
and unlock messages (Page 234)".
Note
The lock/unlock message icons are not available in the AS/System and Field devices top level
area. To view these icons, go into the different levels of the heirarchy.
Additional information
You can find additional information in the following sections:
• Overview screen (Page 155)
• Area overview screens (Page 213)
• Block icon (Page 216)
• Faceplate (Page 226)
Introduction
The browser with the "Diagnosis" preselected opens when an operator selects the button while
working with the workfield from the Diagnostics section of the work box.
Only diagnosis area is enabled and selected, whereas all other areas are disabled and de-selected
(opposite if you use it in one of the technological area). Only the buttons for selection of ASSET-
states are offered.
In the new diagnostic area, the browser will show exactly the same columns like in the normal
mode: BlockName, Type, State, and Area.
Overview
The "PCS 7 measuring point browser" window displays all the relevant maintenance state of
devices.
You can see the description of each status in the section: "Maintenance status and maintenance
group display (Page 221)".
"Selection of states"
This area displays maintenance state of devices. All state icons are shown in their respective
status group frames. The group name is displayed in the tooltip when the mouse pointer is
hovered in the area between the state icon and the group frame. You can select/ deselect one or
more states from any status group by clicking the icon. The status information of the selected
states is displayed in the status area.
The following states are displayed in this area:
• Selection of areas
This area displays the top folders of the plant hierarchy. You can select/deselect one or more
areas.
Note
In the Diagnostic Mode, it is not possilbe to select a particular area.
• Status area
This area shows the list of blocks with their corresponding "Type", "State", and "Area"
depending on the "Selection of states" and "Selection of areas".
Note
In measuring point browser for the diagnostic area, loop in alarm works only through Loop
in alarm button.
Introduction
The maintenance engineer gets an overview of the plant status of the entire plant in the
overview screen.
You can use the buttons to launch various functions. The functions are described in the following
sections.
A maintenance group display is shown in each area if there is at least one lower-level picture for
this area. The areas are shown in color as shown below:
• PC stations (on a yellow background)
• Network objects (on a green background)
• AS/system (cyan background)
• Field devices (cyan background)
• User objects (on a light blue background)
Note
The "Field devices" area is only created for PCS 7 Maintenance Station if you use the PCS 7 Basic
Library >=V8.1 in the AS.
If you use the PCS 7 Basic Library <=V8.1 in the AS, all field devices are assigned to the "AS system"
area.
The following figure shows an example of the overview screen for the diagnostics area:
(1) At least one message is locked. Messages can only be locked for objects of the AS/System
areas, user objects and field devices.
6.4.1 Overview
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Introduction
Up to 10 Web pages that are used to provide support for diagnostics measures can be called. The
buttons are displayed when the calls are configured.
The first 3 buttons are also displayed in the header of the faceplate.
Requirements
• The maintenance target (web address) has been configured.
• The maintenance target can be accessed via the network.
Procedure
1. Click the button.
Result
The web page is displayed in a screen window.
Additional information
You can find information on configuring in the section "Configuring maintenance links
(Page 96)".
Introduction
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
The complete export is used to export the electronic rating plate and the object status of all the
objects with diagnostic functionality (for example, field devices, PCs, and network objects).
This file forms the basis for the filtered complete export.
Procedure
1. Click the button.
Result
The complete export is executed.
The information is saved to the file "@XML_Export.sml".
Additional information
You can find information on configuring in the section "Overview of complete export
(Page 130)".
Note
Avoid parallel access to the filtered manual complete export.
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Introduction
The system allows you to display the data of the last complete export filtered and to export this
data.
A complete export is performed automatically when this function is used.
Various filter criteria are available for filtering data.
• Filter data
Procedure
1. Click the button.
Result
The view of the faceplate for the manually filtered complete export is displayed.
Additional information
You can find additional information on filtering in the section "How to filter and save the data of
the complete export" below.
Introduction
The faceplate includes various filter settings for the export.
The export can be started.
When you open the faceplate, you get an overview of the last executed or started export. The
settings remain in effect even after you have executed a complete download/changes-only
download of the OM/MS server.
Once an export has started, you cannot change any filter settings.
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Display
The following figure shows an example of the faceplate for the manually filtered complete
export.
Operator control
• Operator control
Note
For every successful or an unsuccessful export, a status message is received.
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Note
The manually filtered complete export and remote access via OPC use the same variable
structure.
They are therefore dependent on one another and can influence one another.
Export file
One export file is created for every manually filtered complete export.
The export file is saved to the MS server project.
An additional storage location can be specified in the ""Other settings" tab (Page 106)" tab under
"Advanced diagnostic settings".
The name of the export file is structured as follows: "LogFilteredExportManually_YYYY-MM-
DD_HH-MM-SS-SSS.XML".
The most recent export file is also stored with the following name for display in the faceplate:
"CurrentFilteredExportManually.XML".
The export file contains the following information:
• Overall status of the manually filtered complete export
• Start time, end time and duration of execution
• Information on manually filtered complete exports with errors or that were not performed
The storage location contains the three most recent export files. Older export files are deleted
from the system.
If an export file cannot be deleted due to access conflicts, an error message is generated in the
process control. The system attempts to delete the export file during the next export.
If an export file cannot be written with the defined name due to access conflicts, an error
message is generated in the process control. The file name is suffixed with "(<x>)", where x is a
natural number beginning with "1".
Reaction of the manually filtered complete export when the SIMATIC PDM ASSET service is stopped
• The SIMATIC PDM ASSET service is stopped due to archiving
The project states are regularly archived on the engineering station in many plants.
The SIMATIC PDM ASSET service must be stopped and locked to prevent it restarting for the
duration of archiving.
No jobs can be accepted during this time. The Maintenance Station call is rejected.
In this case, a manually filtered complete export that is to be started or is already running is
paused for the duration of archiving.
The system checks every 10 minutes whether it is possible to resume the manually filtered
complete export. The check is repeated 20x.
Each check is entered in the log with a time specification.
In this phase, the status in the "...State" variable remains 0xFFFF.
If the start is successful, the manually filtered complete export continues.
If the start fails after the maximum number of retries, the filtered manual complete export is
canceled with a message in the message system.
• The SIMATIC PDM ASSET service is not running for other reasons
In this case, the Maintenance Station attempts to start the SIMATIC PDM ASSET service.
If the start is successful, the manually filtered complete export starts or continues.
If the start fails, the manually filtered complete export is canceled with a message in the
message system.
Additional information
For additional information, please refer to the following sections.
6.4.4.4 How to filter and save the data of the manually filtered complete export
Requirement
• The faceplate for the manually filtered complete export is open. The view for the manually
filtered complete export is displayed.
• The manually filtered complete export is not being performed at this time.
• The cyclically filtered complete export may have started.
• Processing of the cyclically filtered complete export is not being performed at this time.
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Procedure
1. Select the filter criteria you require.
– Select the desired filter criteria check boxes in the following groups:
- Maintenance status
- Maintenance job
- Priority
- Maintenance status
- Device management
If multiple filter criteria are selected, they are ORed.
Exception: An exception to this is the "Loop check: On previous day" check box, which is
only taken into consideration when the "Loop check" check box is selected.
– You can enable all filter criteria with the "Select all" button.
Click "Deselect all" to clear all filter criteria selected.
– In the "Type information" group, you can select an area from the drop-down lists and enter
the text you are looking for in the input boxes.
You can use the characters "*" and "?" as wildcards.
Link the fields.
2. Click the "Start" button.
The view expands to include the operator panel.
3. Click "OK".
A picture window with the result will appear.
Note
If it is detected when starting an export that another filtered complete export is already
running, the new export to be launched is canceled.
Additional information
You can find additional information on the name and storage location in the section "Overview
of complete export (Page 130)".
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Note
Avoid parallel access to the manually filtered complete export.
Introduction
The system allows you to export the data of the last complete export cyclically filtered.
You open the faceplate for filtered complete export using the button in the overview screen.
You can use the cyclically filtered complete export irrespective of the manually filtered complete
export.
Three independent cyclically filtered complete exports are available.
Procedure
1. Click the button.
2. In the faceplate, select one of the views for the cyclically filtered complete export.
You can find information on the selection of the views in the section "Display elements and
operator controls for the parameter data export and the filtered complete export (Page 232)".
Result
The view of the faceplate for the selected cyclically filtered complete export is displayed.
Additional information
For additional information, please refer to the following sections.
The function description in the following sections applies to each of the three cyclically filtered
complete exports.
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Introduction
The faceplate includes various filter settings for the export.
The export can be started or terminated.
When you open the faceplate, you get an overview of the last executed or started export. The
settings remain in effect even after you have executed a complete download/changes-only
download of the OM/MS server.
Once an export has started, you cannot change any filter settings. You can only terminate the
export operation.
Overview
The following figure shows an example of the faceplate for the cyclically filtered complete export:
Display
• Next start
Date and time of the next cyclically filtered complete export start
Operator control
• Operator control
Note
For every successful or an unsuccessful export, a status message is received.
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Export file
One export file is created for every cyclically filtered complete export.
The export file is saved to the MS server project.
An additional storage location is specified under "Advanced diagnostic settings" in the "Other
settings" tab (Page 106).
The name of the export file is structured as follows: "LogFilteredExportCyclic <n>_YYYY-MM-
DD_HH-MM-SS-SSS.XML" (n=1 to 3).
The most recent export file is also stored with the following name for display in the faceplate:
"CurrentFilteredExportCyclic<n>.XML".
The export file contains the following information:
• Overall status of the cyclically filtered complete export
• Start time, end time and duration of execution
• Information on cyclically filtered complete exports with errors or exports that were not
performed
The storage location contains the three most recent export files. Older export files are deleted
from the system.
If an export file cannot be deleted due to access conflicts, an error message is generated in the
process control. The system attempts to delete the export file during the next export.
If an export file cannot be written with the defined name due to access conflicts, an error
message is generated in the process control. The file name is suffixed with "(<x>)", where x is a
natural number beginning with "1".
Reaction of the cyclically filtered complete export when the SIMATIC PDM ASSET service is stopped
• The SIMATIC PDM ASSET service is stopped due to archiving
The project states are regularly archived on the engineering station in many plants.
The SIMATIC PDM ASSET service must be stopped and locked to prevent it restarting for the
duration of archiving.
No jobs are accepted during this time. The call to the Maintenance Station is rejected.
In this case, a cyclically filtered complete export that is to be started or is already running is
paused for the duration of archiving.
The system checks every 10 minutes whether it is possible to resume the cyclically filtered
complete export. The check is repeated 20x.
Each check is entered in the log with a time specification.
In this phase, the status in the "...State" variable remains 0xFFFF.
If the start is successful, the cyclically filtered complete export continues.
If the start fails after the maximum number of retries, the cyclically filtered complete export
is canceled with a message in the message system.
• The SIMATIC PDM ASSET service is not running for other reasons
In this case, the Maintenance Station attempts to start the SIMATIC PDM ASSET service.
If the start is successful, the cyclically filtered complete export is started or continues.
If the start fails, the cyclically filtered complete export is canceled with a message in the
message system.
Additional information
For additional information, please refer to the following sections.
Requirements
• The faceplate for the filtered complete export is open.
• The cyclically filtered complete export to be selected is not started.
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Procedure
1. Select the required cycle in the header of the faceplate with the "Cycle" button.
2. Select the filter criteria you require.
– Select the required filter criteria check boxes in the following groups:
- Maintenance status
- Maintenance job
- Priority
- Maintenance status
- Device management
If multiple filter criteria are selected, they are ORed.
Exception: An exception to this is the "Loop check: On previous day" check box, which is
only taken into consideration when the "Loop check" check box is selected.
– You can enable all filter criteria with the "Select all" button.
Click "Deselect all" to clear all filter criteria selected.
– In the "Type information" group, you can select an area from the drop-down lists and enter
the text you are looking for in the input boxes.
You can use the characters "*" and "?" as wildcards.
Link the fields.
3. Enter the cycle in hours in the "Cyclic execution" text box.
4. Enter the date and time for the first export in the "Start" text box.
5. Click the "Start" button.
The view expands to include the operator panel.
6. Click "OK".
Result
The next start time is calculated from the specified start and cycle time.
An operator message is triggered.
An export file is created after each cycle.
The status display in the header of the faceplate shows the current status.
Note
If it is detected when starting an export that another filtered complete export is already running,
the new export to be launched is canceled.
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Requirement
The faceplate for the cyclic filtered complete export is open.
Procedure
1. Select the started cycle in the header of the faceplate with the "Cycle" button.
2. Click "Exit".
The view expands to include the operator panel.
3. Click "OK".
Result
The cyclically filtered complete export for the selected cycle is terminated.
An operator message is triggered.
Introduction
The "Message correction" function deletes messages of SNMP-compatible objects in the
configuration data of the Maintenance Station (server data) for which the relationship with the
project has been deleted, for example, if you have removed PC hardware from the system.
The "Message correction" function is available if your plant is not operated via a
PCS 7 Web client.
Procedure
1. Click the button.
Result
Relevant messages are deleted.
Note
This function is available if you configured the Maintenance Station in the MS Standard version.
Introduction
The "PC station reset" function resets the saved error states in the following views:
• "Diagnostics" for PC objects
• "Connection representation" for client objects
• "Connection representation" for server objects
All saved error states of the objects in the "PC stations" area are reset.
Procedure
1. Click the button.
Result
Error states are reset.
An operator message is triggered.
Additional information
You can find information on the individual views at:
• "Diagnostics" view for PC objects (Page 252)
• "Connection display" view for client objects (Page 253)
• "Connection display" view for server objects (Page 255)
Note
This function is available if you configured the Maintenance Station in the MS Standard version.
Introduction
The "AS system reset" function resets the saved error states in the following views:
• "Performance" for AS objects
• "OBX..." for AS objects
• "Connection load display" for CPU connections
All saved error states of the objects in the "AS system" area are reset.
Procedure
1. Click the button.
Result
Error states are reset.
An operator message is triggered.
Additional information
You can find information on the individual views at:
• "Performance" view for AS objects (Page 260)
• "OBx..." view for AS objects (Page 262)
• "Parameters" view for AS objects (Page 264)
Note
This function is available if you configured the Maintenance Station in the MS Standard version.
Introduction
The "Field device reset" function resets the saved error states in the following view:
• "Diagnostics" for AS objects
All saved error states of the objects in the "Field devices" area are reset.
Procedure
1. Click the button.
Result
Error states are reset.
An operator message is triggered.
Additional information
Information on the view is available at:
• "Diagnostics" view for AS objects (Page 257).
Note
This function is available if you configured the maintenance station in the MS Standard version.
Introduction
The "User area reset" function resets the saved error states in the following views:
• "Diagnostics" for user objects
• "Monitoring" for user objects
All saved error states of the object in the "User objects" area are reset.
Procedure
1. Click the button.
Result
Error states are reset.
An operator message is triggered.
Additional information
You can find information on the individual views at:
• "Diagnostics" view for user objects (Page 278)
• "Monitoring" view for user objects (Page 280)
Introduction
The "Initializing PC objects / Network objects" function can be used to manually initiate the status
generation for PC objects and network objects.
Procedure
1. Click the button.
Result
The status generation for objects is updated for the PC objects and network objects areas.
An operator message is triggered.
Introduction
The "Update PDM devices" function can be used to improve the conformity of the displays to the
diagnostic status in the maintenance stations and SIMATIC PDM. If you use field devices in
SIMATIC PDM in case of PDM MS or PAM Station, the determined diagnostic status will not be
updated until the cycle time is reached. This function makes it easier to establish a conforming
state for the entire project. The button is operable only when PDM is installed and is locked when
a refresh is running.
Note
All the SIMATIC PDM objects based on an EDD/FDI integration will be updated. However, it will
take a very long time and can impose a strong load on the performance.
Procedure
1. Click the button.
Result
The status generation of all the PDM objects is updated.
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Note
Avoid parallel access to filtered manual parameter data export.
Introduction
The filtered manual parameter data export enable a manual parameter data export from field
devices via SIMATIC PDM.
You open the faceplate for parameter data export using the button in the overview screen. The
view for the filtered manual parameter data export is displayed.
Pre-requisite
SIMATIC PDM V8.2 or later must be installed on Engineering System for the button to be
operable.
Procedure
1. Click the button.
Result
The view of the faceplate for the filtered manual parameter data export is opened.
Additional information
For additional information, refer to the following sections:
6.4.7.2 Filter settings for the filtered manual parameter data export
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Introduction
The faceplate includes various filter settings for the export.
The export can be started or terminated.
When you open the faceplate, you get an overview of the last executed or started export. The
settings remain in effect even after you have executed a complete download/changes-only
download of the OM/MS server. Data export can be done in the following methods:
• Offline - Parameter data (project): It reads parameter data from the project and exports it.
• Online - Parameter data (field device, complete): It reads all the parameters data from the
field device and updates it in the project and exports it.
• Online - Parameter data (filed device, selected): It reads only a set of parameters data from
the field device and updates it in the project and exports it. The parameters that are relevant
for each used device type can be selected via SIMATIC Manager menu “Extended Parameter
Selection”. The selected parameter details are read back from the field device and an export
file with all the device parameter details gets generated.
Synchronization field device --> project: It exports all the modified parameters data that triggers
Config Change and are updated in the project from the field device on set intervals.
Once an export has started, you cannot change any filter settings. You can only terminate the
export operation.
Time-controlled synchronization can be enabled or disabled irrespective of the other export
settings.
Display
The following figure shows an example of the faceplate for the filtered manual parameter data
export:
Operator control
• Operator control
• Display
Preview value:
The preview value specifies how many devices match the currently set filter.
While the preview value is being determined or if it could not be determined, for example,
because the ASSET service is currently unavailable, "***" is displayed as preview value.
Note
For every successful or an unsuccessful export, a status message is received.
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Note
The filtered manual parameter data export and remote access via OPC to use the same variable
structure.
They are therefore dependent on one another and can influence one another.
Note
When exporting online parameter data, the device parameter assignment may not be open
elsewhere. Otherwise, only an export of online parameter data is performed.
This is relevant for the following export types:
• Export of the "online parameter data (field device)"
• Time-controlled synchronization (field device --> project)
• Online parameter data export for a selected device
Refer to the export file to find out whether online or offline parameter data was exported.
Reaction of the parameter data export when SIMATIC PDM ASSET service is stopped
• SIMATIC PDM ASSET Service is stopped due to archiving
The project states are regularly archived on the engineering station in many plants.
The SIMATIC PDM ASSET service must be stopped and locked against restarting for the
duration of archiving.
No export jobs can be accepted during this time. The call to the Maintenance Station is
rejected.
In this case, a parameter data export that is to be started or is already running is paused for
the duration of archiving.
There is a check every 10 minutes to determine whether it is possible to resume the
parameter data export. The check is repeated 20x.
Each check is entered in the log with a time specification.
In this phase, the status in the "...State" variable remains 0xFFFF.
If the start is successful, the parameter data export continues.
If the start fails after the maximum retries, the parameter data export is canceled with a
message in the message system.
• SIMATIC PDM ASSET Service is not running for other reasons
In this case, the Maintenance Station attempts to start the SIMATIC PDM ASSET service.
If the start is successful, the parameter data export is started or continued.
If the start fails, the parameter data export is canceled with a message in the message system.
Export file
The parameter data is stored in an individual export file for each created device.
The export format and the content of these export files conform to the export format of SIMATIC
PDM.
To specify the storage location, select the menu command Options > SIMATIC PDM >
Settings... in SIMATIC Manager and then go to the "General" tab, "Path for 'Asset export' files".
The name of the export file is structured as follows: "<Devicename>_
$YYYYMMDD_HHMMSS.XML".
When name conflicts occur during the export, the file name is extended by "_1".
Log file
For each export job, a log file is created in which the successful or unsuccessful export of the
parameter data of the devices is documented.
The storage location of the log file is specified using the WinCC variable
@AssetControl.ExportPath. The log file is also saved in the project of the MS server.
The name of the log file has the following structure: "LogPDMExportManually_YYYY-MM-
DD_HH-MM-SS-SSS.XML".
In addition, the most recent log file is stored with the following name for display in the faceplate:
"CurrentPDMExportManually.XML".
Additional information
For additional information, refer to the following sections:
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Requirements
• The faceplate for the parameter data export is open. The view for the filtered manual
parameter data export is displayed.
• The filtered manual cyclic parameter data export is not being performed at this time.
• The filtered cyclic parameter data export may have started.
• The processing of the filtered cyclic parameter data export is not being performed at this time.
Procedure
1. Select which parameter data will be exported.
– If you want to export parameter data stored in the project, select the "Offline parameter
data (project)" check box.
– If you want to export all the parameter data stored in the field device, select the "Online
parameter data (field device, complete)" check box.
– If you want to export only a set of parameters data stored in the field device, select the
"Online parameter data (field device, selected)" check box. The parameters that are
relevant for each used device type can be selected via SIMATIC Manager menu “Extended
Parameter Selection”. The selected parameter details are read back from the field device
and an export file with all the device parameter details gets generated.
2. If you want to export all the modified parameters data that triggers Config Change and are
updated in the project from the field device on set intervals, select the "Synchronization field
device --> project: check box.
3. Select the filter criteria you require.
When several check boxes are selected, the filter criteria are linked with "Or".
Exception: An exception to this is the "Loop check: On previous day" check box, which is only
taken into consideration when the "Loop check" check box is selected.
4. Click the "Start" button.
The view is expanded to include the operator panel.
5. Click "OK".
Result
An export file is created for each individual device.
An operator message is triggered.
The values displayed in the "Export jobs for SIMATIC PDM" area are updated.
The status display in the header of the faceplate shows the current status.
A log file is created for the export job.
Note
If it is detected when starting an export that another parameter data export is already running,
the new parameter data export to be launched is canceled.
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Requirements
• The faceplate for the parameter data export is open.
• The view for the filtered manual parameter data export is displayed.
Procedure
1. Click "Exit".
The view is expanded to include the operator panel.
2. Click "OK".
Result
The parameter data export is terminated.
An operator message is triggered.
The values displayed in the "Export jobs for SIMATIC PDM" area are updated.
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Requirements
• The faceplate for the parameter data export is open.
• The view for the filtered manual parameter data export is displayed.
• The "Time-controlled synchronization field device --> project" check box is selected.
Procedure
1. Enter the time of the start.
2. Select the "Time-controlled synchronization field device --> project" check box.
Result
An operator message is triggered.
The synchronization is performed at the specified time.
A check is made at the specified time as to whether there is a difference in the parameter data
between the device and project or if a device has independently signaled a configuration
change. For these devices, all the parameter data is first read from the devices and saved in the
project.
The parameter data saved in the project is then exported to the specified destination.
The selected filter criteria are not taken into consideration for the device selection.
The values displayed in the "Export jobs to SIMATIC PDM" area are not updated.
A log file is not created on the Maintenance Station.
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Requirements
• The faceplate for the parameter data export is open.
• The view for the filtered manual parameter data export is displayed.
Procedure
1. Clear the "Time-controlled synchronization field device --> project" check box.
Result
Time-controlled synchronization was disabled.
An operator message is triggered.
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Note
Avoid parallel access to the filtered parameter data export.
Introduction
The filtered cyclic parameter data export enables cyclic parameter data export from field devices
via SIMATIC PDM.
You open the faceplate for parameter data export using the button in the overview screen.
You can use the filtered cyclic parameter data export independent of the filtered manual
parameter data export.
Three independent filtered cyclic parameter data exports are available.
Requirement
Using SIMATIC PDM
Procedure
1. Click the button.
2. In the faceplate, select one of the views for the filtered cyclic parameter data export.
Result
The view of the faceplate for the selected filtered cyclic parameter data export is displayed.
Additional information
For additional information, refer to the following sections:
The function description in the following sections applies to each of the three filtered cyclic
parameter data exports.
6.4.8.2 Filter settings for the filtered cyclic parameter data export
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Introduction
The faceplate includes various filter settings for the export.
Display
The following figure shows an example of the faceplate for the cyclic parameter data export.
• In the Maintenance status, Maintenance job, Priority, Maintenance status and Device
management areas
Selected filter criteria
• In the Export settings area
Selected type of export
Operator control
Clicking the button displays the operator panel for terminating the None
export operation.
• Operator control
• Display
Preview value:
Specifies how many devices match the currently set filter
Note
For every successful or an unsuccessful export, a status message is received.
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Note
While exporting either of the "Online parameter data", the device parameter assignment may
not be open elsewhere. Otherwise, only an export of offline parameter data is performed.
Refer to the export file to find out whether online or offline parameter data was exported.
Export file
The parameter data is stored in an individual export file for each created device.
The export format and the content of these export files conform to the export format of SIMATIC
PDM.
To specify the storage location, select the menu command Options > SIMATIC PDM >
Settings... in SIMATIC Manager and then go to the "General" tab, "Path for 'Asset export' files".
Depending on the selected cycle, an additional "Cycle<n>" subdirectory is automatically created
as the storage location, where <n> represents the number of the selected cycle.
The name of the export file is formed as follows: "<Device name>_
$YYYYMMDD_HHMMSS.XML".
When name conflicts occur during the export, the file name is extended by "_1".
Log file
For each export job, a log file is created in which the successful or unsuccessful export of the
parameter data of the devices is documented.
The storage location of the log file is specified using the WinCC variable
@AssetControlCyclic.ExportPath. The log file is also saved in the project of the MS server.
Depending on the selected cycle, an additional "Cycle<n>" subdirectory is automatically created
as the storage location, where <n> represents the number of the selected cycle.
The name of the log file has the following structure: "LogPDMExportCyclic<n>_YYYY-MM-
DD_HH-MM-SS-SSS.XML".
In addition, the most recent log file is stored with the following name for display in the faceplate:
"CurrentPDMExportCyclic<n>.XML".
The log file contains the following information:
• Overall status of the parameter data export
• Start time, end time and duration of the execution
• Information on parameter data exports with errors or that were not performed
The storage location contains the three most recent log files. Older log files are deleted from the
system.
When a log file cannot be deleted due to access conflicts, an error message is generated in the
process control.
When a log file cannot be written with the defined name due to access conflicts, an error
message is generated in the process control. The file name is suffixed with "(<x>)", where x is a
natural number beginning with "1".
Additional information
For additional information, refer to the following sections:
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Requirements
• The faceplate for the parameter data export is open.
• The filtered cyclic parameter data export to be selected is not started.
Procedure
1. Select the desired cycle in the header of the faceplate with the "Cycle" button.
2. Select which parameter data will be exported.
– If you want to export parameter data stored in the project, select the "Offline parameter
data (project)" check box.
– If you want to export all the parameters data stored in the field device, select the "Online
parameter data (field device, complete)" check box.
– If you want to export a set of parameters data stored in the field device, select the "Online
parameter data (field device, selected)" check box.
3. Select the filter criteria you require.
When several check boxes are selected, the filter criteria are linked with "Or".
Exception: An exception to this is the "Loop check: On previous day" check box, which is only
taken into consideration when the "Loop check" check box is selected.
4. Enter the cycle in hours in the "Cyclic execution" text box.
5. Enter the date and time for the first start of cyclic processing in the "Start" text box.
6. Click the "Start" button.
The view is expanded to include the operator panel.
7. Click "OK".
Result
The next start time is calculated from the specified start and cycle time.
An operator message is triggered.
An export file is created for each individual device.
If the filtered cyclic parameter data export has been started, the display values are updated in the
"Export jobs to SIMATIC PDM" area and a log file is created.
The status display in the header of the faceplate shows the current status.
Note
If it is detected when starting an export that another parameter data export is already running,
the new parameter data export to be launched is canceled.
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Requirement
The faceplate for the parameter data export is open.
Procedure
1. Select the desired started cycle in the header of the faceplate with the "Cycle" button.
2. Click "Exit".
The view is expanded to include the operator panel.
3. Click "OK".
Result
The parameter data export for the selected cycle is terminated.
An operator message is triggered.
The values displayed in the "Export jobs for SIMATIC PDM" area are updated.
Introduction
The manually filtered complete export can also be run via OPC access.
The information for the manually filtered complete export is stored in a structure variable.
This variable structure can be directly accessed by another computer via the OPC DA interface.
You can find information on establishing an OPC connection in the WinCC Information System
online help.
The "Access via OPC" column explains how the variables are to be used.
(1)
@AssetInfoExportControl.MSFilter
The following tables show the permitted values for bits 0 to 31.
If multiple bits are set, the states are ORed.
Exception: An exception to this is bit 24 "Loop check: On previous day", which is only taken into
consideration when bit 21 "Loop check" is set.
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Maintenance state
Good - - - - - - - - - - - - - - - 1
Passivated - - - - - - - - - - - - - - 1 -
Out of service - - - - - - - - - - - - - 1 - -
Simulation - - - - - - - - - - - - 1 - - -
Local operator con‐ - - - - - - - - - - - 1 - - - -
trol
Maintenance re‐ - - - - - - - - - - 1 - - - - -
quired
Maintenance de‐ - - - - - - - - - 1 - - - - - -
manded
Maintenance alarm - - - - - - - - 1 - - - - - - -
Device status un‐ - - - - - - - 1 - - - - - - - -
known/untested
Configuration - - - - - - 1 - - - - - - - - -
change
Maintenance job
Maintenance re‐ - - - - - 1 - - - - - - - - - -
quired requested
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Maintenance de‐ - - - - 1 - - - - - - - - - - -
mand requested
Maintenance - - - 1 - - - - - - - - - - - -
alarm requested
Maintenance status
Completed - - 1 - - - - - - - - - - - - -
Canceled - 1 - - - - - - - - - - - - - -
In maintenance 1 - - - - - - - - - - - - - - -
...
Bit 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
...
Maintenance not - - - - - - - - - - - - - - - 1
started
Planned mainte‐ - - - - - - - - - - - - - - 1 -
nance
Release request - - - - - - - - - - - 1 - - - -
Priority
Important object - - - - - - - - - - - - - 1 - -
Safety-related ob‐ - - - - - - - - - - - - 1 - - -
ject
Maintenance state
Locked messages - - - - - - 1 - - - - - - - - -
Device management
Loop check - - - - - - - - - - 1 - - - - -
Loop check: - - - - - - - 1 - - - - - - - -
On the previous
day
Write protection - - - - - - - - - 1 - - - - - -
Group 1 - - - - - - - - 1 - - - - - - -
Group 2 - - - - - 1 - - - - - - - - - -
Group 3 - - - - 1 - - - - - - - - - - -
@AssetInfoExportControl.TypInfo
The table shows the permitted values.
Value Explanation
Initial value
"<Text filter key=""Type"" Filter=""SI‐ You can specify any text filter using keywords.
MATIC RACK PC"" /> The basic structure is shown in the "Value" column.
<TextFilterCombination>AND</Text‐ The following keywords are available:
FilterCombination>
• TagFunktion
<Text filter key=""HwVersion"" Fil‐
ter=""V3.5"" />" • TagLocation
• Address
• Description
• Message
• Type
• Manufacturer
• OrderNumber
• SerialNumber
• InstallationDate
• HwVersion
• SwVersion
• HWComment
@AssetInfoExportControl.Start
The table shows the permitted values.
Value Explanation
0 Initial value
1 "Start" command via faceplate
The command is reset after execution of the manually filtered complete export.
2 "Start" command via OPC
The command is reset after execution of the manually filtered complete export.
@AssetInfoExportControl.State
The table shows the permitted values.
Value Explanation
0x0 Initial value
0xFFFF Manually filtered complete export underway
0x01 Manually filtered complete export complete
All information data has been determined.
0x02 Manually filtered complete export complete
The manually filtered complete export has been terminated by the operator.
Value Explanation
0x03 Manually filtered complete export complete
No information data has been determined.
0x04 Processing complete
No device status corresponded to the filter criteria.
0x05 Processing complete
Cyclically filtered complete exports running in parallel prevented start.
@AssetInfoExportControl.DateStarted
The table shows the permitted values.
Value Explanation
Date&T Start time of the export for the export file
ime
@AssetInfoExportControl.DateFinished
The table shows the permitted values.
Value Explanation
Date&T End time of the export for the export file
ime
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Note
The filtered manual complete export and remote access via OPC use the same variable structure.
They are therefore dependent on one another and can influence one another.
Procedure
1. Write the @AssetInfoExportControl.MSFilter and/or @AssetInfoExportControl.TypeInfo
variable in accordance with the required filter criteria.
2. Write a value of "2" to the start variable @AssetInfoExportControl.Start.
Result
An export file with the result is created.
Note
If it is detected when starting an export that another filtered complete export is already running,
the new export to be launched is canceled.
Introduction
The filtered manual parameter data export can also be performed with OPC access.
The information for the parameter data export is stored in a structure variable.
This variable structure can be directly accessed by another computer via the OPC DA interface.
You can find information on establishing an OPC connection in the WinCC Information System
online help.
The "Access via OPC" column explains how the variables are to be used.
(1)
@AssetControl.ActionType
The table shows the permitted values.
Value Explanation
0x01 Export of the offline parameter data (project)
0x02 Export of the online parameter data (field device, complete)
0x03 Export of the online parameter data (field device, selected)
@AssetControl.MSFilter
The following tables show the permitted values for bits 0 to 31.
If multiple bits are set, the statuses are ORed
Exception: An exception to this is bit 24 "Loop check: On previous day", which is only taken into
consideration when bit 21 "Loop check" is set.
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Maintenance state
Good - - - - - - - - - - - - - - - 1
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Passivated - - - - - - - - - - - - - - 1 -
Out of service - - - - - - - - - - - - - 1 - -
Simulation - - - - - - - - - - - - 1 - - -
Local operator con‐ - - - - - - - - - - - 1 - - - -
trol
Maintenance re‐ - - - - - - - - - - 1 - - - - -
quired
Maintenance de‐ - - - - - - - - - 1 - - - - - -
manded
Maintenance alarm - - - - - - - - 1 - - - - - - -
Device status un‐ - - - - - - - 1 - - - - - - - -
known/untested
Configuration - - - - - - 1 - - - - - - - - -
change
Maintenance job
Mainten. required - - - - - 1 - - - - - - - - - -
requested
Maintenance de‐ - - - - 1 - - - - - - - - - - -
mand requested
Maintenance - - - 1 - - - - - - - - - - - -
alarm requested
Maintenance status
Completed - - 1 - - - - - - - - - - - - -
Canceled - 1 - - - - - - - - - - - - - -
In maintenance 1 - - - - - - - - - - - - - - -
...
Bit 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
...
Maintenance not - - - - - - - - - - - - - - - 1
started
Planned mainte‐ - - - - - - - - - - - - - - 1 -
nance
Release request - - - - - - - - - - - 1 - - - -
Priority
Important object - - - - - - - - - - - - - 1 - -
Safety-related ob‐ - - - - - - - - - - - - 1 - - -
ject
Device management
Loop check - - - - - - - - - - 1 - - - - -
Loop check: - - - - - - - 1 - - - - - - - -
On the previous
day
Write protection - - - - - - - - - 1 - - - - - -
Bit 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
Group 1 - - - - - - - - 1 - - - - - - -
Group 2 - - - - - 1 - - - - - - - - - -
Group 3 - - - - 1 - - - - - - - - - - -
@AssetControl.Start
The table shows the permitted values.
Value Explanation
0 Initial value
1 "Start" command
The command is reset after completion of the offline/online export job (ActionType).
@AssetControl.MSFilterPreview
The structure of the @AssetControl.MSFilterPreview variable corresponds to that of the
@AssetControl.MSFilter variable.
@AssetControl.StartPreview
The table shows the permitted values.
Value Explanation
0 Initial value
1 "StartPreview" command
The preview value is determined.
@AssetControl.ExportStarted
The table shows the permitted values.
Value Explanation
Date&T Start time of the export for the log file
ime
@AssetControl.ExportFinished
The table shows the permitted values.
Value Explanation
Date&T End time of the export for the log file
ime
@AssetControl.CyclicTrigger
The table shows the permitted values.
Value Explanation
0 "Time-controlled synchronization field device --> project" not enabled
1 "Time-controlled synchronization field device --> project" enabled
Command for enabling the time-controlled synchronization for field device -> project
@AssetControl.CyclicTriggerRun
The table shows the permitted values.
Value Explanation
0 "Time-controlled synchronization field device --> project" not enabled
Command for disabling the time-controlled synchronization for field device -> project
1 "Time-controlled synchronization field device --> project" enabled
@AssetControl.CyclicTriggerStartTime
The table shows the permitted values.
Value Explanation
0 to 23 Start time of the time-controlled synchronization
@AssetControl.CyclicTriggerStart
The table shows the permitted values.
Value Explanation
0 Initial value
1 Start of the execution of the devices in the "Configuration change" state
@AssetControl.State
The table shows the permitted values.
Value Explanation
0x0 Initial value
0xFFFF Offline/online export job is running
0x01 Export completed
All offline/online export jobs have been completed.
0x02 Export completed
The offline/online export job was terminated by the operator.
0x03 Export completed
Not all offline/online export jobs have been completed.
Value Explanation
0x04 Processing completed
No device status corresponded to the filter criteria.
0x05 Processing completed
Export executed in parallel prevented the start
Refer to the log file for your export job to find out which export jobs were executed successfully
and which were not.
@AssetControl.Cancel
The following table shows the permitted values.
Value Explanation
0 Initial value
1 "Exit" command
@AssetControl.DeviceCount
The following table shows the permitted values.
Value Explanation
0 Initial value
0 ... Total number of offline/online export jobs according to filter criteria
@AssetControl.DeviceCountPreview
The following table shows the permitted values.
Value Explanation
0 Initial value
0 ... Total number of offline/online export jobs according to filter criteria for the preview value
@AssetControl.DeviceCountOK
The following table shows the permitted values.
Value Explanation
0 Initial value
0 ... Number of successful offline/online export jobs
@AssetControl.DeviceCountFailed
The following table shows the permitted values.
Value Explanation
0 Initial value
0 ... Number of unsuccessful offline/online export jobs
@AssetControl.TagExportStart
The following table shows the permitted values.
Value Explanation
0x0 Initial value
0x01 "Start online export job" command (field device, complete)
The command is reset after executing the export job (TagExportName).
0x02 "Start offline export job" command (project)
The command is reset after executing the export job (TagExportName).
0x03 "Start online export job" command (field device, selected)
The command is reset after executing the export job (TagExportName).
@AssetControl.TagExportState
The following table shows the permitted values.
Value Explanation
0x0 Initial value
0xFFFF Export job is running
0x01 Export has ended.
Export job has been completed.
0x03 Export has ended.
Export job has not been completed.
0x04 Processing has ended.
No match found for TagExportName.
@AssetControl.TagExportName
The variable is "empty" in the initial state.
Specify the tag name of the device to be exported. You can find this name in the Component List
Editor.
@AssetControl.ExportPath
The variable is "empty" in the initial state. The log file for your export job is only stored in the
"AssetExport" directory in the OS project of the MS server.
Specify the path for AssetExport files that you have specified in the settings for SIMATIC PDM. The
log file for your export job is stored in the specified path and in the "AssetExport" directory in the
OS project of the MS server.
6.4.10.2 How to start the filtered manual parameter data export (OPC)
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Note
The filtered manual parameter data export and remote access via OPC to use the same variable
structure.
They are therefore dependent on one another and can influence one another.
Procedure
1. Select which parameter data will be exported.
– If you are exporting offline parameter data, write the @AssetControl.ActionType variable
with the value 0x01.
– If you are exporting online parameter data, write the @AssetControl.ActionType variable
with the value 0x02.
2. Write the @AssetControl.MSFilter variable according to the desired filter criteria.
3. Write the @AssetControl.ExportPath variable.
4. Set the start variable @AssetControl.Start.
Result
An export file is created for each individual device.
The values of the @AssetControl.DeviceCount, @AssetControl.DeviceCountOK, and
@AssetControl.DeviceCountFailed variables contain the current execution status.
The values displayed in the "Export jobs for SIMATIC PDM" area are updated.
A log file is created for each export job.
Note
If it is detected when starting an export that another parameter data export is already running,
the new parameter data export to be launched is canceled.
6.4.10.3 How to end the filtered manual parameter data export (OPC)
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Procedure
1. Set the @AssetControl.Cancel variable.
Result
The parameter data export is terminated.
The @AssetControl.Start variable is automatically set to "0".
The values of the @AssetControl.DeviceCount, @AssetControl.DeviceCountOK, and
@AssetControl.DeviceCountFailed variables are updated.
Note
The @AssetControl.Start variable is automatically set to "0" after completion of the export job.
In this case, it is not necessary to terminate the offline/online parameter data export.
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Requirement
Time-controlled synchronization is disabled.
Procedure
1. Enter the time of the start in the @AssetControl.CyclicTriggerStartTime variable.
2. Set the @AssetControl.CyclicTrigger variable to "1".
Note
When the value of the @AssetControl.CyclicTrigger variable changes from "0" to "1", a modified
start time takes effect.
Result
The synchronization is performed at the specified time.
A check is made at the specified time as to whether there is a difference in the parameter data
between the device and project or if a device has independently signaled a configuration
change. For these devices, all the parameter data is first read from the devices and saved in the
project.
The parameter data saved in the project is then exported to the specified destination.
The selected filter criteria are not taken into consideration for the device selection.
Time-controlled synchronization has no effect on the variables @AssetControl.DeviceCount,
@AssetControl.DeviceCountOK or @AssetControl.DeviceCountFailed.
A log file is not created on the Maintenance Station.
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Procedure
1. Set the @AssetControl.CyclicTriggerRun variable to "0".
Result
Time-controlled synchronization was terminated.
6.4.10.6 How to start the parameter data export for a selected device (OPC)
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Procedure
1. Write the @AssetControl.TagExportName variable with the variable name of the device to be
exported.
2. Write the @AssetControl.ExportPath variable.
3. Select which parameter data will be exported.
– If you are exporting online parameter data, write the @AssetControl.ActionType variable
with the value 0x01.
– If you are exporting offline parameter data, write the @AssetControl.ActionType variable
with the value 0x02.
Result
An export file is created for the device to be exported.
If the online parameter data export cannot be executed, the offline parameter data are
automatically exported.
The export via variable name has no effects on the @AssetControl.DeviceCount,
@AssetControl.DeviceCountOK and @AssetControl.DeviceCountFailed variables.
The values of the @AssetControl.DeviceCount, @AssetControl.DeviceCountOK, and
@AssetControl.DeviceCountFailed variables contain the current execution status.
A log file is not created.
The @AssetControl.Start variable is automatically set to "0x0" after completion of the export job.
Note
It is not necessary to terminate the online parameter data export.
Note
The "Field devices" area is only created for PCS 7 Maintenance Station if you use the PCS 7 Basic
Library >=V8.1 in the AS.
If you use the PCS 7 Basic Library <=V8.1 in the AS, all field devices are assigned to the "AS system"
area.
Introduction
The objects to be monitored are displayed in the diagnostic screens as block icons in the process
control.
To get more information about an object, you can call the corresponding faceplate with a mouse
click.
Block icon
The block icons supported by the system which can be displayed in the diagnostic screens are
contained in the file "@@maintenancetypicals.pdl".
The file is located in the project directory under " ... \wincproj\<os-name>\GraCS".
You can find a description of block icons in the section "Block icon (Page 216)" and in the section
"Block icon for redundant objects (Page 219)".
Faceplate
Faceplates display all information on an object with diagnostic capability in process mode. This
includes information that can be obtained by the object itself or from the project data. When
information is unavailable, the corresponding field is empty.
The faceplate is made up of the title of the screen window, the header and the different views.
You can change the view.
The number of views in the faceplates depends on the type of object. The "Identity", "Messages",
"Note" and "Maintenance" views are always available for selection in the faceplates. Intelligent
objects, for example objects described by an EDD/FDI device description and integrated in
SIMATIC PDM, have additional views depending on the object.
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
You can find additional information about this in the section "Faceplate display (Page 226)" and
in the section "Faceplate redundant objects (Page 243)".
The label matches the local ID (LID) from the identification data of the device.
You can find information about the LID in the section "Origin of the identification data
(Page 294)".
– The following figure shows an example of the label of a device classified as important:
The setting is made in the SIMATIC PDM object properties of the device.
– The following figure shows an example of the label of a device in a safety-related
application:
The setting is made in the SIMATIC PDM object properties of the device.
• Bitmap
The figure below shows an ET 200:
A bit map displaying the device icon is entered automatically in the "DeviceIcon" property,
provided the bit map is available in HW Config.
• Maintenance group display of the custom object
The following figure shows the maintenance group display as AS process control fault.
You open the associated faceplate with the maintenance group display.
The following states are displayed depending on the maintenance status of the object.
You can find information on the display in the section "Maintenance status and maintenance
group display (Page 221)".
You can use the diagnostic icon to open the associated faceplate.
You can find information about the display in the section "Maintenance status and
maintenance group display (Page 221)".
The redundancy status is displayed for redundant objects.
You can find information on this in the section "Maintenance status of redundant objects
(Page 225)".
• Active memo
The following figure shows the display if a note is active.
You can find information on this in the section ""Note" view (Page 250)".
• Maintenance group display of the lower-level hierarchy
The following figure shows the display of the maintenance group display as AS process
control fault.
Various states are displayed in the maintenance group display, depending on the
maintenance group displays of the objects of the lower-level hierarchy.
You can find information on this in the section "Maintenance status and maintenance group
display (Page 221)".
If you click on the maintenance group display in the process control, the lower-level process
picture in the hierarchy is displayed.
&+ &+
&+ &+
&+ &+
Display Explanation
No display Channel not available
Channel not used/disabled
"Good" channel state
"Bad" channel state
Note
The use of the character ":" in the symbolic name of a channel or in the comment of the module
is not permitted.
Introduction
Note
This function is available for the Maintenance Station in the MS Standard and MS Basic version.
Block icons
The following table shows the possible types of display:
Additional information
You can find additional information in the sections "Block icon (Page 216)" and "Maintenance
status of redundant objects (Page 225)".
Introduction
The diagnostics icon represents the maintenance status of the object.
The maintenance group display represents the message status of the object and the lower-level
objects.
Note
If the maintenance state is "Unchecked/unknown" in the faceplate, all other dynamic displays are
irrelevant.
The number in the priority column indicates the priority of the display. The lowest number has
the highest priority.
Note that unacknowledged messages have a higher priority than acknowledged messages.
Bit Explanation
0 to 7 Display of the maintenance state
8 to 15 Display of the maintenance state of the redundant partner
16 "1"= Redundant partner available
17 "0" = Primary partner is master
"1" = Redundant partner is master
18 SIMATIC PDM maintenance state worse than device status
19 to 20 Coding of cycle time for the cyclic update
Bit 19=0, Bit 20=0: 1 day
Bit 19=1, Bit 20=0: 12 hours
Bit 19=0, Bit 20=1: 1 hour
Bit 19=1, Bit 20=1: 10 minutes
21 "1" = Device is selected as "Selection for exports" in the maintenance view
Selection user group 1, if Bit 0 and Bit 1 are not set in the variable *.MS2
22 "1" = SIMATIC PDM has detected a status change
23 "1" = block takes part in the cyclical updating of SIMATIC PDM
24 to 27 OS operation
28 to 31 SIMATIC PDM maintenance state
Bit Explanation
0 "1" = Device is selected as "Selection for exports" in the maintenance view
Selection user group 2, if Bit 21 is set in the variable "MS"
1 "1" = Device is selected as "Selection for exports" in the maintenance view
Selection user group 3, if Bit 21 is set in the variable "MS"
2 to 27 Reserved
28 "1" = "Config Change" mode. This object will be set to visible until it is reset.
30 "1" = "Out of service" mode
31 "1" = "Passive" mode
Note
The "Out of service" and "Passive" operating modes are available for the maintenance station in
the PAM Station version.
Introduction
Note
This function is available for the Maintenance Station in the MS Standard and MS Basic version.
In the faceplate header and in the block icon, the maintenance status of both objects is displayed
in one diagnostics icon for the redundant pair.
The maintenance status for this diagnostics icon is formed from the maintenance states of the
object A and B.
Additional information
You can find information on the displays in the section "Maintenance status and maintenance
group display (Page 221)".
6.11 Faceplate
Introduction
Starting from a block icon in a diagnostics screen, the maintenance engineer can open the
corresponding faceplate while the process is in operation; this faceplate provides him with
access to more detailed information and facilitates operator control of the block.
Introduction
The control bar always has the same structure. The appropriate displays and buttons are shown
based on the object type and configuration.
Note
These display elements and operator controls are available for the maintenance station in the
MS Standard or PDM MS versions.
Display
The following table provides an overview:
(8) Lock messages, • AS/System Locks or unlocks all messages for the object
unlock messag‐ You can find additional information about this in
• Field devices
es the section "How to lock and unlock messages
• User objects
(Page 234)".
(9) Acknowledge • PC stations Acknowledging the message on the object
messages • Network objects
• AS/System
• Field devices
• User objects
(10) Depassivation • Field devices: Displayed if a module or a channel is passivated
Redundant I/O modules You can find additional information about this in
the section "How to depassivate modules or
channels (Page 236)".
(13) Link object 1 to • PC stations Calling up configured Web pages
link object 3 You can find more information on this in the sec‐
• Network objects
tions "Configuring maintenance links (Page 96)"
• AS/System
and "How to open websites via maintenance
• Field devices links (Page 236)".
• User objects
(14) Diagnostics • PC stations: Calling up the IPC "Diagnostics Monitor"
monitor SIEMENS IPCs You can find additional information about this in
the section "How to call the IPC "Diagnostics
Monitor" (Page 240)".
Additional information
You can find additional information in the section "Display elements and operator controls for
the parameter data export".
6.11.2.2 Display elements and operator controls for the parameter data export and the
filtered complete export
Introduction
Note
These display elements and operator controls are available for the maintenance station in the
MS Standard or PDM MS versions.
The following figure shows an example of the display elements and operator controls:
Display
(18) "Manual complete export" You can find additional information in the following
view sections:
• Manually filtered complete export (Page 160)
Status displays
Additional information
You can find information on other display elements and operator controls in the header in the
section "Displays and operator controls (Page 227)".
Introduction
Messages are enabled or disabled for objects from the AS/System areas, field devices and user
objects.
Messages can be locked or unlocked in the button set or in the faceplate.
Locked messages are indicated by an X:
• In the group display in the overview area
You can find additional information about this in the section "Overview area (Page 149)".
• In the maintenance group displays in the overview screen, area overview screen, block icon,
and faceplate
You can find additional information about this in the section "Maintenance status and
maintenance group display (Page 221)".
Note
Any change in the operator authorization level must be implemented in the project of each
operator station in an MS multiple-station system.
Additional information
For more information on this, refer to the Process Control System PCS 7; Operator Station
manual.
Introduction
Note
This function is available for the Maintenance Station in the MS Standard version.
The passivation button is displayed in the faceplate in order to ensure that the discrepancy of a
redundant module or its failed channels can be detected by the maintenance engineer.
As long as the discrepancy time is active, maintenance required and a message are displayed in
the message system in the faceplate of the module.
If, moreover, a long-term discrepancy is detected, the module/channel is passivated. This results
in a loss of redundancy. The module or the channel is indicated as "Faulty" in the block icon. The
maintenance demanded, the button for depassivation and a message in the message system are
displayed in the faceplate.
If the cause of the discrepancy has been corrected, the depassivation can be carried out with the
button in the faceplate.
Procedure
1. Click the "Depassivation" button.
2. Click the "Execute" button.
Result
The depassivation is executed. The button is hidden.
Introduction
Up to 3 Web pages which are used to provide support for diagnostics measures can be called. The
buttons are displayed when the calls are configured.
Requirements
• The Maintenance Station is available in the MS Standard version.
• The maintenance target (web address) has been configured.
• The maintenance target can be accessed via the network.
Procedure
1. Click the button.
Result
The web page is displayed in a screen window.
Introduction
The "Call Hardware Project" button is used to call the online view of the hardware configuration
(HW Config).
Note
This function is available for the maintenance station in the MS Standard and PAM Station
versions.
The hardware project can be called if the MS client is operated on the ES.
Requirement
The object is part of the hardware configuration.
Procedure
1. Click the "Call Hardware Project" button.
Note
Do not proceed until the online view of the hardware configuration (HW Config) is completely
open, because HW Config online may otherwise be put in the background and can no longer
be reached if key combinations are locked. In this case, press the button once again.
Result
The online view of the hardware configuration (HW Config) opens.
Introduction
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
You use the "Call SIMATIC PDM" button to open the configuration interface for the device shown
in the faceplate.
Requirements
• The SIMATIC PDM Server is installed and set up.
• The object can be programmed with SIMATIC PDM.
Procedure
1. Click the "Call SIMATIC PDM" button.
2. Enter your logon data in the input boxes of the logon dialog box.
Result
The configuration interface for the object displayed in the faceplate is opened.
Additional information
You can find information about the opened display in the manual Process Control System PCS 7;
Help on SIMATIC PDM.
Introduction
Use the "Call configuration data" button to open the Web interface for the object.
First, an attempt is made to establish a secure connection (HTTPS) to the device. If the secure
connection is successfully established, the "Call configuration data" button is displayed for
operator selection.
If the secure connection cannot be established, an attempt is made to establish a non-secure
connection (HTTP). If the non-secure connection is successfully established, the "Call
configuration data" button is displayed for operator selection.
If no connection can be established, the "Call configuration data" button is not available for
selection.
Note
This function is available for the maintenance station in the MS Standard version, optionally also
in the PDM MS and PAM Station.
Requirements
• The network objects must be accessible via the network.
• The "Trusted sites" security setting is in effect.
For additional information on this topic, refer to the SIMATIC NET; "Industrial Ethernet OSM/
ESM Network Management" Manual.
• The network object device profile corresponds to the OSM or SCALANCE device profile.
Procedure
1. Click the "Call configuration data" button.
Result
The Web interface of the object opens.
Introduction
Note
This function is available for the Maintenance Station in the MS Standard version. Optionally also
in PDM MS and PAM Station.
You can open the "Diagnostics monitor" Web page of the object with the "Diagnostics monitor"
button.
First, an attempt is made to establish a secure connection (HTTPS) to the device. If the secure
connection is successfully established, the "Diagnostics monitor" button is displayed for
selection.
If no connection can be established, the "Diagnostics monitor" button is not available for
selection.
Requirements
• The Diagnostics Monitor diagnostic tool is installed and configured.
• The web server is started and enabled in the Windows firewall.
• The PC stations can be accessed via the network.
Procedure
1. Click the "Diagnostics monitor" button.
Result
The diagnostic tool is called.
6.11.3 Views
Available
This view is displayed at all the objects.
This view is not available in the faceplate for the redundant server pair.
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Overview
This view displays the configuration data or device data in the information box. The composition
of the identification data depends on the object selected.
The structure of the view is identical for all faceplates; only the origin of the identification data is
different.
The following figure shows an example of the view:
Display
• Maintenance state
You can find more information on the maintenance status in the sections "Maintenance
status and maintenance group display (Page 221)" and "Maintenance status of redundant
objects (Page 225)".
• Identification data
The identification data represents the electronic rating plate of a device. The identification
data is refreshed manually in the faceplate using the operator control.
There is an automatic update following the change in status from "Maintenance alarm" to
another maintenance status. The exception to this is the status "unknown/unchecked".
You can find information about the sources of the identification data in the section "Origin of
the identification data (Page 294)".
Note
Not every object provides all identification data.
If certain identification fields in the "Identity" view are empty even though the time stamp in
the "Last update" field has been updated, these data are not provided by the object. The
causes may be as follows:
• No data are stored in the object.
• The object does not recognize the data.
If, however, no time stamp is displayed in the "Last update" field, either the identification data
have not been updated or there are no online data available for this object.
• Comment
The comment is read from HW Config.
• Last update
The timestamp of the last update of the identification data is displayed.
• Operating mode
The current operating mode is displayed and can be changed.
Note
The selection of the operating mode is available on the PAM station.
• State
The following table shows the icon representation for the origin of the data:
Display Meaning
Device data
The data source is the device.
Project data
The data source is the project.
No data were read from the device.
No icon No information on the data source
Operator control
Additional information
You can find information on displaying redundant objects in the faceplate in the section
"Faceplate redundant objects (Page 243)".
Introduction
Note
This function is available for the Maintenance Station in the MS Standard version.
The custom maintenance status is displayed in the faceplate for the object and for the partner
in the relevant diagnostics icon.
The redundancy state is displayed in the faceplate for the redundancy object.
Display in a faceplate
The redundancy state is displayed in the header in one diagnostic icon.
The following figure shows an example of the "Identity" view for a redundantly connected
remote IO station:
• In this view, if the object is redundant, one diagnostics icon is displayed for the active object
and one for the passive object. The respective diagnostic icon displays the custom
maintenance state.
• An orange square is displayed between a diagnostic icons. The square marks the active
object. The active object is the object that exercises the role of the master
• When the faceplate is opened, the information box always shows the data of the active
object.
• By clicking on a diagnostics icon, the diagnostics icon is given a colored border and the
corresponding data is displayed in the information box.
• Refreshing data with the "Refresh" button only affects the active object. This may have the
result that only project data is displayed for the passive object.
• If the passive object was active and the data was refreshed with the "Refresh" button, device
data is also displayed for the passive object.
• If the passive object is selected in the faceplate, when the "Refresh" button is clicked, the
diagnostics icon of the active object is given a colored border and the data of the active object
is displayed in the information box.
Note
When the faceplate for a redundant signal module opens, the data of the selected signal module
is always displayed. It is not possible to switch between the redundant objects. To display the
data for the redundant signal module, open the faceplate for the respective signal module.
Additional information
You can find information on the redundancy state in the section "Maintenance status of
redundant objects (Page 225)".
Available
This view is displayed at all the objects.
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Overview
This view contains all messages that are present for an object.
The following messages are displayed:
• Diagnostic/error messages
• Operating messages after selection of the long-term archive list in the toolbar
The following figure shows an example of the view:
Display
Messages
• Currently pending messages, independent of acknowledgment status
• Unacknowledged messages went out
• In addition to the filter for the "Origin", only messages that belong to the "Diagnostics" area
are displayed.
Operator control
Operation takes place the same way as operation on an operator station.
You can find additional information on this in the manual Process Control System PCS
7, OS Process Control.
The following button is also displayed for switching between the "Journal" view and the
"Operator message" view if the short-term archive list is selected.
Available
This view is displayed at all the objects.
This view is not available in the faceplate for the redundant server pair.
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Overview
This view allows the maintenance engineer to demand and manage a maintenance job for the
specific object. The maintenance state of the demanded maintenance measure is displayed in
the diagnostic screens in the maintenance group display. The maintenance state, the
maintenance job and the state of the maintenance job are displayed in the header of the
faceplate.
In this view you can execute a single export, consisting of identification data, the maintenance
status and the maintenance information of the respective object.
The following figure shows an example of the view for an input and output module:
Display
Note
The Advanced Process Library is required in order to display the maintenance release.
This function is available for the Maintenance Station in the MS Standard version.
Display Meaning
Release granted for all objects/channels involved
Display Meaning
Channel/object deactivated in hardware configuration
Interconnected/used and release by the operator in the plant area not granted
Interconnected/used and release by the operator in the plant area granted
Operator control
• Demand
• Request
"Requested action" You select an action from the drop-down box.
area An action, for example, can be "Disassembly".
You can find information on configuring an action in the
section "Configuring maintenance actions (Page 100)".
"Time requested" The time of the request of the maintenance job is specified in
area the input box. The time is entered in the following format:
YYYY.MM.DD - hh:mm.
"Maintenance sta‐ By selecting an option button, the maintenance job is given
tus" area a processing state.
• In maintenance
• Release request This function is available for the Maintenance Station in
the MS Standard version.
• Planned mainte‐
nance Note: Available only for field devices.
• Completed
• Cancel
"Passivate" check box Available for PC and IPC objects
The PC object is passivated by clicking on the check box.
You can find information on passivation in the section "Pas‐
sivating PC objects (Page 307)".
"Memo" area The maintenance engineer can enter a note for the service
job in the memo field or change a saved note.
The text is applied to the individual export file.
Do not enter more than 255 characters, since a maximum of
255 characters can be use for commenting the operation
message.
In order for the note text to be saved as a comment for the
operator message and permanently displayed in the memo
field, one of the following operator actions is required in
addition to entering the note text:
• Change the type of maintenance job in the maintenance
job area
• Switch between the service types "In maintenance" and
"Planned maintenance" (bilateral) in the Maintenance
status area
The note text is deleted when you complete or cancel the
maintenance job.
"Targets" area • Check boxes
Additional information
You can find information on single export in the section "Overview of individual export
(Page 131)".
Available
This view is displayed at all the objects.
This view is not available in the faceplate for the redundant server pair.
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Overview
You can leave temporary messages for other maintenance engineers in this view.
The following figure shows an example of the "Notes" view.
Operator control
Note
A full compilation of the MS (that is the MS for single-station systems and the MS server for
multiple-station systems) and subsequent download of the MS server deletes the contents of
the memo view.
Available
This view is displayed for the IPC objects from the PC objects area.
Note
This view is available for the Maintenance Station in the MS Standard version. Optionally also for
PDM MS and PAM Station.
Overview
Up to 18 binary states of an IPC are displayed in this view.
Example view for an object IPC with the profile V1.3
Note
The redundancy loss of channel A/B is only indicated in the case of a redundant connection to
the terminal bus with Softnet IE/RNA in combination with the IPC Profile 1.5.
Display
• Status of the objects
The following table shows the icon representation of the statuses:
Display Meaning
No detail information pending or available
Pending fault
There was a fault for a time
No icon No state
Operator control
With Profile V1.4 and higher, the stored states are reset "Process controlling" for the
when you click the button. diagnostics area
Available
This view is displayed at all the OS clients, MS clients and OS/MS clients from the area of the PC
objects.
Note
This view is available for the Maintenance Station in the MS Standard version.
Overview
This view shows all servers, the server data of which are downloaded to the client.
Servers are OS servers, MS servers and OS/MS servers.
The following figure shows an example of the view:
Display
• The symbolic computer name of all servers
• The computer name of all servers
• The computer name of the redundant partner
• Configured and currently connected preferred servers
• Current connection
• State
The following table shows the icon representation of the statuses:
Display Meaning
Configured preferred servers
Operator control
Clicking the button resets the selection for server con‐ "Process controlling" for the
nections that have failed in the meantime. diagnostics area
Available
This view is displayed at all the OS servers, MS servers and OS/MS servers from the area of the
PC objects.
Note
This view is available for the Maintenance Station in the MS Standard version.
Overview
This view displays all clients connected to the server.
Display
• The computer name of all clients assigned to the server
• The computer name of the redundant partner
• Configured and currently connected preferred servers
• Current connection
• State
The following table shows the icon representation of the statuses:
Display Meaning
Configured preferred servers
Operator control
Clicking the button resets the selection for client "Process controlling" for the di‐
connections that have failed in the meantime. agnostics area
Available
The following views are shown for devices of the type Switch, Drive and EnergyMeter from the
field devices area.
Note
This view is available for the Maintenance Station in the MS Standard version.
Overview
Information on Switch, Drive and EnergyMeter type devices is displayed in these views.
• The following figure shows an example of the view for Switch:
• The following figure shows an example of the view for Drive in accordance with the NAMUR
standard:
The fault display in this view is derived solely from the quality information made available
through the process picture.
Display
• Statuses for the device
The following table shows the icon representation of the statuses:
Display Meaning
No detail information pending or available
Problem exists
There was a fault for a time
There is a warning
There was a warning for a time
No icon No state
Operator control
Clicking the button resets the saved states. "Process controlling" for the
diagnostics area
Available
This view is displayed for the AS station in the AS/system area for CPU types that support the
SFC78 and have the following firmware versions:
• Standard CPU 41x >= firmware version V5.0
• H-CPU 4xx >= firmware version V4.5
Note
This view is available for the maintenance station in the MS Standard and PAM Station (PAM
AS410) versions.
Overview
This view graphically displays the overall situation of the CPU utilization. All values in the bar
chart are given as percentages. The reference value is the assigned maximum cycle monitoring
time of the CPU.
All of the displays of the overall situation are mean values. because displaying actual values of
the most recent cycle in each instance would result in a widely fluctuating reduction ratio display
in the screen refreshing cycle.
The following figure shows an example of the view:
Display
• Total runtime
The values in the bar diagram are specified in %, relative to the set maximum cycle monitoring
time.
Its numeric magnitude is displayed under the bar.
– Mean value
Mean value of the actual value in % (TOTALPER block parameter)
– Actual value
Mean value of all net run times in % OB3x/OB8x + OB1 (TOTALCUR block parameter)
– Max. value
Formed from the net run times in % of all the OB3x/OB8x + OB1 net run times from the
most recent cycle (TOTALMAX block parameter)
– Min. value
Formed from the net run times in % of all the OB3x/OB8x + OB1 net run times from the
most recent cycle (TOTALMIN block parameter)
• Horizontal bar diagrams for OB3x
The values refer to the respective OB cycle time.
The graphic display of the OB3x times is expanded by an indicator that signals buffered and
lost start events.
– Net value
– Gross value
– Start event lost
• Horizontal bar diagrams for OB8x and OB1
The values refer to the configured maximum cycle monitoring time.
– Net value
• Scan rate:
Display of the scan rate for all cyclical OBs of the user program
Operator control
Clicking the button resets the values. "Process controlling" for the
diagnostics area
NOTICE
Utilization limit
When the CPU gets close to full capacity, the user programs will become sluggish. If this starts
to affect process mode, the user program will need to be reconfigured.
You can find additional information about this in the section ""Parameters" view for AS objects
(Page 264)".
Available
This view is displayed for the AS station in the AS/system area for CPU types that support the
SFC78 and have the following firmware versions:
• Standard CPU 41x >= firmware version V5.0
• H-CPU 4xx >= firmware version V4.5
Note
This view is available for the maintenance station in the MS Standard and PAM Station versions.
Overview
This view displays the utilization of the OBs in a CPU with diagnostics functionality.
The following figure shows an example of the "OB3x" view .
Display
• The utilization of the OB3x organization blocks is shown in the "OB3x" view:
– The absolute gross and net value, and the average value over a number of cycles of the OB
3x, related to the configured maximum cycle monitoring time of the OB in each case.
– The minimum and maximum values reached since the last reset of the OBs
• The utilization level of the OB8x organization blocks is shown in the "OB8x/OB1" view:
– The absolute net value and the average value over a number of cycles of the OB8x and
OB1, related to the configured maximum cycle monitoring time of the OB in each case.
– The minimum and maximum values reached since the last reset of the OBs.
Operator control
Available
This view is displayed for the AS station in the AS/system area for CPU types that have the
following firmware versions:
• Standard CPU 41x >= firmware version V5.0
• H-CPU 4xx >= firmware version V4.5
Note
This view is available for the maintenance station in the MS Standard and PAM Station versions.
Overview
In this view, parameters can be assigned for the overload behavior.
The default cycle monitoring time for the CPU is 6 s.
Failure to process all the OBs within this time will result in a cycle overload.
To prevent the CPU from switching to "Stop" mode, you can parameterize an "Emergency mode".
• The following figure shows an example of the "Parameter" view of the CPU with SFC78.
• The following figure shows an example of the "Parameter" view of the CPU without SFC78.
Emergency mode
"Emergency mode" automatically reduces the speed of the configured cyclic tasks. The user
programs then run more slowly.
"Emergency mode" should not be used on a continuous basis. The "Emergency mode" is signaled
as a maintenance alarm with maximum priority setting.
Display/Operation
Available
This view is displayed for the AS station in the AS/System area for the following CPU types:
• H-CPU 4xx >= firmware V6
Note
This view is available for the maintenance station in the MS Standard and PAM Station versions.
Overview
This view shows the 5 most heavily loaded connections of the CPU.
The connection types are displayed according to the maximum value of the load from the top
down.
The following figure shows an example of the view:
Note
The displayed actual values correspond to the values that are displayed on the "Connection
statistics" tab in the "Module status" dialog of the CPU.
Display
• Possible connection types:
The connection type corresponds to the configuration in NetPro.
– Invalid connection type
– S7 connection
– S7 connection (fault-tolerant)
– T connection (TCP native)
– T connection (UDP)
– T connection (ISO-on-TCP)
– Routed connection
– PG connection
– OP connection
– OMS connection
– Free connection
– Free connection (TCP)
– System connection
– RPC7 connection
– Connection for basic communication
• Partner / identification
Shows the partner ID from NetPro
• Load
Shows the utilization of the connection as a percentage
• Actual value
• Maximum value
Operator control
Available
This view is displayed for all the CPUs and CPs in the central rack and expansion rack.
Note
This view is available for the maintenance station in the MS Standard and PAM Station versions.
Note
Access from the faceplate on the Maintenance Station is not possible if the diagnostic buffer on
the Engineering Station is already open.
Display
• Sequential number
• Time
Time when the event occurred
• Short text
Brief information about the event
• Error code
Error code for the event
• Detailed description
Detailed information on the event
• Last update
Time stamp of the last update of the data
Operator control
Available
This view is displayed for all the CPUs.
Note
This view is available for the maintenance station in the MS Standard and PAM Station versions.
Overview
This view displays the LEDs of the CPU.
The following figure shows an example of the display for a redundant CPU:
The following figure shows an example of the view of the CPU of the package unit for a SIMATIC
PAM station:
Display
• Frequency
The following table shows an example of the frequency at which the state flashes:
Display Meaning
0.5 The LED flashes at a frequency of 0.5 Hz.
• State
The following table shows the icon representation of the statuses:
Display Meaning
"Active" state
"Active" state
Operator control
Available
This view is displayed at all the objects from the field devices area.
Note
This view is available for the maintenance station in the MS Standard, PDM MS and PAM Station
versions.
Overview
This view displays data of devices which are integrated through an EDD/FDI device description.
The data are read in SIMATIC PDM and transferred to the Maintenance Station.
When you open the view you get an overview of the most recently selected options.
The settings remain in effect even after you have executed a complete download/changes-only
download of the OM/MS server.
Note
If you have executed the reading back of the operable and observable parameters in the AS, the
settings of the complete download are retained during complete download of the AS.
Display
• Communication via SIMATIC PDM
Displays the state of the communication connection between SIMATIC PDM and the device
the last time communication was established
Display Meaning
Communication with SIMATIC PDM established
Communication with SIMATIC PDM not established
• Write protection
Shows the time stamp for when the "Project-specific write protection" parameter was set in
SIMATIC PDM for this device
Display Meaning
Write protection is set
No icon Write protection is not set
Time stamp for write protection
• Loop check
Shows the time stamp for when the "Device tested" parameter was set in SIMATIC PDM for
this device
Display Meaning
Loop check was performed
No icon Loop check was not performed
Time stamp of the last "Loop check".
• Device state
Indicates the possible state of the relevant device (standard diagnostics based on the PA
Profile of the "PROFIBUS & PROFINET International" organization)
Display Meaning
The state "Good" is indicated by a green symbol before the cor‐
responding text.
The individual error states are indicated by a red symbol before
the corresponding text.
No icon No state pending
• Detailed diagnostics:
Shows the time stamp of the last reading of the diagnostics data in SIMATIC PDM
Display Meaning
Time stamp of the last update of the data
The content of the text box is read and displayed for the current state from the EDD/FDI device
description of the device supplied by the manufacturer.
The information displayed in the text field shows messages of the respective field device. The
texts are manufacturer-specific.
The texts are only displayed in the language configured in SIMATIC PDM or in the default
language specified by the manufacturer.
The language change in process control has no effect.
Operator control
Additional information
You can find information on the displayed error texts for updating the diagnostics data in the
section "Error texts for field devices/user objects (Page 291)".
You can find information on the loop check function and project-specific write protection in the
SIMATIC PDM manual.
Available
This view is displayed at all the objects from the field devices area.
Note
This view is available for the maintenance station in the MS Standard, PDM MS and PAM Station
versions.
Overview
This view displays the device parameters of field devices in the project which are integrated
through an EDD/FDI device description.
The following figure shows an example of the view:
Additional information
You can find information on error texts in the section "Error texts for field devices/user objects
(Page 291)".
Available
This view is displayed for objects from the field devices area.
Note
This view is available for the maintenance station in the MS Standard and PAM Station versions.
Overview
External diagnostics information on the object is displayed in this view.
The following figure shows an example of the view:
Display
• State
The following table shows the icon representation of the statuses:
Display Meaning
No detailed information pending or available
• Display text
You configure the texts in the "Advanced Diagnostic Settings".
Additional information
You can find information on configuring the texts for MS Standard in the section "Configuring
maintenance information (Page 103)".
You can find information on configuring maintenance information for MS Standard in the
section "How to configure the display of the maintenance information in MS Standard
(Page 118)".
You can find information on configuring maintenance information in the SIMATIC PAM station
in the section ""PAM information text" tab (Page 112)".
Available
This view is displayed for objects from the user objects area, such as the AssetM block.
Note
This view is available for the maintenance station in the MS Standard and PAM Station versions.
Overview
In this view, information on the user object are displayed.
The following figure shows an example of the view:
Display
• State
The following table shows the icon representation of the statuses:
Display Meaning
No external detail information pending or available
Detail information pending
Detail information existed for a time
No icon No state pending
• Display text
– With SIMATIC PDM
The texts are configured by the user in the SIMATIC PDM object of the "AssetM" block in the
EDD/FDI device description.
You can find additional information in the section "Assigning parameters for the "AssetM"
block using SIMATIC PDM (Page 124)".
– Without SIMATIC PDM
The texts are configured at the block.
You can find additional information in the section "Assigning parameters for the "AssetM"
block without using SIMATIC PDM (Page 125)".
Operator control
Clicking the button resets the saved states. "Process controlling" for the
diagnostics area
Additional information
You can find information on error texts in the section "Error texts for field devices/user objects
(Page 291)".
Available
This view is displayed for all objects from the user objects area.
Note
This view is available for the standard version of the maintenance station.
If a designation for at least one process value is entered in the EDD/FDI device description or at
the parameter "PVx.Value", the view can be selected.
Overview
PCS 7 offers the option of setting up, in a user diagnostics structure, monitoring functions for
objects that are not automatically integrated in the diagnostic screens of the Maintenance
Station. These objects include, for example:
• Values defined by rules or calculations
• Objects that do not support diagnostics (e.g., field devices not recognized in PCS 7)
• Technical areas
• Groups of components
You can show the following monitoring functions in a diagnostics screen:
• Operating hours meter
• Service interval
• Calibration interval
The following figure shows an example of the view:
Display
• Area and Labeling
The following table shows the different configuration variants:
• Signal status
The number in the priority column indicates the priority of the display. The lowest number
has the highest priority.
The following table shows the relationship between display and priority:
2 Bad, process-related
4 Uncertain, device-related
5 Uncertain, process-related
6 Maintenance demanded
None 7 Good
None - Input not connected
• Actual value
The value is read from the "AssetM" block.
• Remaining value
The difference between the actual value and the next limit value is formed in the "AssetM"
block.
• Units of measure
The unit of measurement is configured in the "AssetM" block.
• Alarm limits
The alarm limits are configured in the "AssetM" block.
Operator control
Additional information
You can find information on error texts in the section "Error texts for field devices/user objects
(Page 291)".
Available
This view is displayed for all objects with analog value processing in the field devices area of the
PAM station.
Note
This view is available for the maintenance station in the PAM Station variant.
If a value is entered for at least one process value at the parameter "PVx_Name" (x = 0..2) of the
"PAM_IF" block, the view can be selected.
Overview
In this view, you can display the following monitoring functions, for example:
• Operating hours meter
• Service interval
• Calibration interval
The following figure shows an example of the view:
Display
• Area and Labeling
The following table shows the different configuration variants:
Display Meaning
Display of the view for analog value If a value is entered for at least one process value at the pa‐
monitoring rameter "PVx_Name" (x = 0..2) of the "PAM_IF" block, the view
can be selected.
Label for the process value e.g. PV1 The text is configured by the user at the PVx_Name (x = 0..2)
parameter of the "PAM_IF" block. The corresponding area in
the view is displayed.
• Signal status
The number in the priority column indicates the priority of the display. The lowest number
has the highest priority.
The following table shows the relationship between display and priority:
2 Bad, process-related
4 Uncertain, device-related
5 Uncertain, process-related
6 Maintenance demanded
None 7 Good
None - Input not connected
• Actual value
The value is read from the "PAM_IF" block or transferred from the data block for the object in
the package unit.
• Remaining value
The difference between the actual value and the next limit is formed in "PAM_IF" block or in
"PAM_XX" block.
• Units of measure
The unit of measurement is configured in the "PAM_IF" block or transferred from the package
unit.
• Alarm limits
The alarm limits are configured in the "PAM_IF" block.
• Bar graph for the process value
Colored display of the actual value when limits are reached.
Operator control
Additional information
You can find additional information in the following sections:
""PAM data connection" tab (Page 115)"
"How to configure analog value monitoring (Page 79)"
Available
This view is displayed for the network objects of the Switches group (PN_Main_Family = 13) on
PROFINET in the Field Devices area.
Note
The view is available for the Maintenance Station in the MS Standard version.
Overview
Information on the port monitoring of network objects is displayed in this view.
The following figure shows an example of the view:
Display
Status display of ports
The following table shows the icon representation of the states:
Display Meaning
Port monitoring enabled/good status
Maintenance demanded pending
Maintenance demanded was pending for a time
Port monitoring disabled or unknown
Operator control
Clicking the button resets the saved maintenance "Process controls" for the di‐
states. agnostics area
Available
This view is displayed for the compact field unit from the field devices area.
Note
This view is available for the Maintenance Station in the MS Standard version.
Overview
This view displays the maintenance states of the individual CFU channels.
The eight binary input/output channels are displayed on the left half of the screen.
The right half of the screen shows the eight channels for connecting the field devices.
The following figure shows an example of the view:
Display
Status display of channels
The following table shows the icon representation of the states:
Display Meaning
Maintenance required pending
Unknown/untested
"Good" state
Display Meaning
Maintenance status was pending and has not yet
been reset
No icon Channel not in use.
Operator control
Clicking the button resets the saved maintenance "Process controls" for the di‐
states. agnostics area
Available
This view is available in the AS station CPU function block and package units. It is also available
for monitored package units of a PAM Station.
Note
This function is available for the Maintenance Station in the MS Standard, PDM MS and PAM
Station versions.
Overview
This view displays the detailed view of memory, process objects and time in the information box.
The following figure shows an example of the view:
Display
• Work Memory (Code)
It displays the total and used work memory in bytes. It is used by the AS system for Code.
• Work Memory (Data)
It displays the total and used work memory in bytes.
• Load Memory
It displays the total and used load memory in bytes.
• Process Object
It displays the allocated and available process object in the AS system.
Note
Process Objects are available only for 410 CPUs.
• Timestamps
It displays the current timestamp of the last update..
• Status
It displays the synchronization status. It determines whether the transmitted time is
synchronized or not.
A time is considered to be out of sync when:
– the synchronization signal has failed (e.g. DCF77 signal is missing or no time
synchronization telegram is received).
– the current time master is other than quartz clock (doesn not support external time
synchronization).
Status Description
Green Time synchronization completed
Grey Time synchronization not available
Available
This view is available in the AS station CPU function block. It is also available at all redundant 400
CPUs.
Note
This function is valid only if the AS is used as an H-System in SIMATIC Manager.
Note
This function is available for the Maintenance Station in the MS Standard.
Overview
This view shows the last 10 measured times of cycle time extension and lock time. In addition,
the average of the measured times is displayed.
The following figure shows an example of the view:
Display
• Cycle time extension
It shows the measured time of max. scan cylce time extension the system took for the
switchover during a HCiR download.
• Disabling time for prority classes > 15 for cyclic interrupt OB3x
It shows the measured time of max. lock time the system took for the switchover during a
HCiR download.
Note
If the suggested measures are not successful or an error code is output that is not further
specified in the table, contact Technical Support.
The following table shows the assignment of the identification data displayed on the MS to the
origin.
Note
ID data of PC stations without PCS 7 installation are not transferred to the maintenance station.
Where does the identification data for a network object come from?
In the case of the faceplate for network objects, the identification data is read from the device
via an SNMP connection.
The device must be configured in the SNMP OPC Server of the maintenance station for this.
This data is prepared for display on the maintenance station with the "Export tags for WinCC"
function.
The following table shows the assignment of the identification data displayed on the MS to the
origin.
6.12.5 Identification data for devices that are integrated using a device description
(EDD/FDI)
From where does the identification data for the EDD/FDI device description come?
The identification data is provided via SIMATIC PDM for the faceplate of devices that are
integrated through an EDD/FDI device description.
The data are provided if the EDD/FDI device description is created in conformance with the
specifications of the PROFIBUS & PROFINET International organization, the Hart Communication
Foundation, or the Fieldbus Foundation.
The information is largely based on the tag names used in the EDD/FDI device description. These
tag names can be optionally displayed in the configuration interface of PDM. The display is
activated in the settings of SIMATIC PDM.
The following table shows the assignment of the identification data displayed on the MS to the
origin.
1)
Article number = also order number or MLFB
Where does the identification data for objects in the user area come from?
The display of the identification data depends on its source:
• With SIMATIC PDM
From the EDD/FDI device description
• Without SIMATIC PDM
At the block in the CFC chart
The following table shows the assignment of the identification data displayed on the MS to the
origin.
Introduction
The operators of the Maintenance Station and the Operator Station can be different individuals
and can work in physically separate locations.
As a result, the information flow between the Maintenance Station and Operator Station is not
guaranteed.
Maintenance takes place in agreement with the plant operator.
Communication is supported by means of icons and messages.
This enables a coordinated maintenance sequence.
The maintenance sequence is documented and can be tracked.
Maintenance is initiated and edited in the faceplate in the "Maintenance" view
Note
This function is available for the maintenance station in the MS Standard, PDM MS and PAM
Station versions. The release request and maintenance release are available in the MS Standard
version.
Status diagram
The possible status transitions are explained in the diagram below.
1RUPDOVWDWXV
0DLQWHQDQFH
0DLQWHQDQFHDODUP 0DLQWHQDQFHUHTXLUHG GHPDQGHG
3ODQQHGPDLQWHQDQFH
5HOHDVHUHTXHVW
&DQFHO ,QPDLQWHQDQFH
*RRG
&RPSOHWHG
Additional information
You can find additional information on the release for maintenance and on configuring the
technological blocks in the online help Process Control System PCS 7; Advanced Process Library.
Introduction
Note
This function is available for the maintenance station in the MS Standard, PDM MS and PAM
Station versions. The release request and maintenance release are available in the MS Standard
version.
Requirements
• The technological block has been interconnected in the CFC.
You can find information on interconnecting in the section "Engineering for maintenance
(Page 132)".
• "Manual" or "On" mode is active for the technological block.
• The operator has the operator authorization "system operation".
Step 1 Result
Maintenance engineer requests Maintenance job requested
maintenance job
1. Open the diagnostic faceplate. In the header of the faceplate and in the block icon, the "Main‐
tenance alarm requested" status is displayed in the mainte‐
2. Select the "Maintenance" view.
nance group display.
3. Enter a text in the "Memo" area if re‐
quired.
4. In the "Maintenance job" area, se‐
lect, for example, the "Alarm" option In addition, the maintenance job status "Maintenance engi‐
button. neer has not yet created a maintenance job" is displayed in the
faceplate header.
5. Click "On" in the operator panel for
activating the maintenance job.
Step 2 Result
Maintenance engineer schedules Maintenance job scheduled
maintenance job
1. Open the diagnostic faceplate. In the block header, the display for the status of the mainte‐
nance job changes from "Maintenance engineer has not yet
2. Select the "Maintenance" view.
created a maintenance job" to the status "Planned mainte‐
3. Enter a text in the "Memo" area if re‐ nance".
quired.
4. Select the "Planned maintenance"
option button in the "Maintenance
status" area. An operator message is triggered.
5. Click "On" in the operator panel. The text entered in the "Memo" area is displayed:
• In the Memo area of the "Maintenance" view of the face‐
plate
• As a comment for the message in the operator input list of
the faceplate and message system
Step 3 Result
Maintenance engineer requests Maintenance release requested
maintenance release
1. Open the diagnostic faceplate. In the block header, the display for the status of the mainte‐
nance job changes from "Planned maintenance" to the status
2. Select the "Maintenance" view.
"Release request".
3. Enter a text in the "Memo" area if re‐
quired.
4. Select the "Release request" option
An operator message is triggered.
button in the "Maintenance status"
The text entered in the "Memo" area is displayed:
area.
• In the Memo area of the "Maintenance" view of the face‐
5. Click "On" in the operator panel.
plate
• As a comment for the message in the operator input list of
the faceplate and message system
The following is displayed on the technological faceplate:
• Display of the release request (operator prompt)
• Message of "Request for operator input - General" class
Step 5 Result
Maintenance engineer puts the ob‐ Maintenance of the object can be performed
ject into "Maintenance status"
1. Open the diagnostic faceplate. In the block header, the display for the status of the mainte‐
nance job changes from "Release request" to the status "In
2. Select the "Maintenance" view.
maintenance".
3. Enter a text in the "Memo" area if re‐
quired.
4. Select the "In maintenance" option
button in the "Maintenance status" An operator message is triggered.
area. The text entered in the "Memo" area is displayed:
5. Click "On" in the operator panel. • In the Memo area of the "Maintenance" view of the face‐
plate
• As a comment for the message in the operator input list of
the faceplate and message system
Depending on the configuration of the technological block,
the following is displayed on the technological faceplate:
• Display of the maintenance demand and release
• "Out of service" mode and the "Maintenance demanded
and maintenance release" icon
Maintenance can be performed.
Step 1 Result
Maintenance engineer completes Maintenance complete
maintenance
1. Open the diagnostic faceplate. In the block header, the display for the status of the mainte‐
nance job changes from "In maintenance" to the status
2. Select the "Maintenance" view.
"Good".
3. Enter a text in the "Memo" area if re‐
The text in the Memo area is deleted in the "Maintenance"
quired.
view of the faceplate.
4. Select the "Completed" option but‐ An operator message is triggered.
ton in the "Maintenance status" area.
The entered text in the "Memo" area is displayed as a comment
5. Click "On" in the operator panel. for the message in the operator input list of the faceplate and
message system.
The "Maintenance demanded and Maintenance release" icon
is hidden in the technological faceplate.
Step 2 Result
Plant operator ends the release for Release for maintenance is ended by the plant operator
maintenance
1. Open the technological faceplate. An operator message is triggered.
2. Select the "Parameter" view. The technological block is set to "Manual" mode.
3. Disable the "Release for mainte‐
nance".
4. Click "No" in the operator panel.
Introduction
With the "Passivate" function, a PC object is temporarily excluded from the monitoring during
process control.
Overview
A PC object is passivated by the following operator actions:
• Operator actions in the faceplate in the "Maintenance" view
The operator actions are stored retentively and are retained even if there is a complete
download to the OS station.
You can find additional information on this in the section ""Maintenance" view (Page 246)".
• Disabling/enabling process control
If the process control of a monitored OS station is deactivated, its PC object is automatically
set to passivated.
As soon as this OS station is restarted, the passivation is canceled again.
Available
This function is available on all IPC/PC stations.
Display
If a PC object is passivated, "Passivated" is displayed as the maintenance state in the block icon
and faceplate.
No group alarm is displayed in the maintenance group display of the PC object.
Messages
If a PC object is passivated by an operator input in the faceplate, an operator message is
generated.
All messages pending for this PC object are acknowledged automatically when the PC object is
passivated.
As long as the PC object is passivated, no new messages are generated for this PC object.
Any pending events are signaled when the PC object is depassivated.
Introduction
Note
This function is available for the Maintenance Station in the MS Standard and MS Basic version.
The "Flutter suppression" function for channel blocks of the PCS 7 Advanced Process Library is
used to delay the outgoing of a message by a configured period.
Flutter occurs when the status of fault messages changes from "Outgoing" back to "Incoming"
within the delay time.
The flutter suppression affects diagnostics events in OB82 and OB83.
There is only one flutter message per module. The delay times and fault messages are channel-
specific.
The fault messages are extended by at least the delay time.
Requirement
• The CFC typicals have been created.
• The PCS 7 Advanced Process Library is used.
Procedure
1. Open the CFC typical.
2. Configure the flutter time at the channel block with the "FlutTmIn" parameter.
3. Activate the flutter suppression at the channel block with the "FlutEN = 1" parameter.
Note
Multiple channel blocks for HART modules
When HART modules and auxiliary variables are used, you use multiple channel blocks for the
same channel of the module.
The above-mentioned procedure must be performed for each channel block.
Result
The flutter suppression is activated.
After AS compilation and subsequent download, the changes are applied for process control.
Additional information
You can find additional information on maintenance in the section "Displays and operator
controls (Page 227)" and in the manual Process Control System PCS 7; Advanced Process Library.
Introduction
The basic settings of the MS are subjected to a consistency check during the process control.
If an inconsistency is detected by the system, a message is displayed in the process control.
The following paragraphs describe how the inconsistency is displayed and which steps you can
take to eliminate it.
Display
The message is displayed in the message list of the OS/MS and in the faceplate of the affected PC
station.
The message text is "Inconsistency found in maintenance settings".
Note
Status displays can display incorrect states as a result of the inconsistency.
Elimination procedure
1. Click the button "Repair" in the Diagnostics settings area.
Database entries and startup list are corrected.
You can find the "Repair" button in the Plant Hierarchy settings of the SIMATIC Manager.
The "Repair" button is only operable when the "Migrate (Page 140)" button is not operable.
2. Download all operating systems.
Corrections to the database entries are transferred to the target systems.
You can load a change for the OS server.
Result
• Consistency has been created
The message has been sent and will not be triggered again.
• Consistency has not been created
The message is still pending.
Contact Technical Support.
In addition to the description of the problem, also transfer the log files from the path(1)
"...\SIEMENS\WinCC\diagnostics" of the affected PC station.
(1)
Depending on the operating system
D
C Depassivation, 236
CFC Device profiles, 86
Creating, 123 Diagnostic screens
Changes in the project generating, 135
Add OS server, 141 updating, 135
Adding an AS subproject, 141 Diagnostic structure, 91, 94
Changes in HW Config, 140 deleting, 145
Changes in the software, 144 generating, 92
updating, 92
Maintenance information
Configuring, 103, 112, 118, 119
H Maintenance job, 301
Display, 221
Hardware project
Maintenance links
Calling, 237
Configuring, 96
HART modules, 129
Maintenance required, 301
Maintenance state
Display of objects, 221
I Messages, 150
Identification data Structure of the variable for the maintenance
AS objects, 296 status, 223
Devices with EDD/FDI device description, 297 Maintenance Station
IPCs, 294 Application, 15
Network objects, 295 Compiling, 137
Objects in the user area, 300 Configuration, 19
PCs, 294 Downloading, 137
IE/PB Link PN IO PCS 7 Web client, 19
Using, 81 Variants, 15
Inconsistency Maintenance Station Basic
Diagnostics settings, 310 Application, 15
Individual export Maintenance Station Standard
Executing, 246 Application, 15
Export file, 131 Maintenance status
Overview, 131 Display for redundant objects, 225
Target directory, 98, 131 Maintenance targets
Initializing Configuring, 98
PC objects / Network objects, 178 Manually filtered complete export
Filter settings, 161
Function, 160
L OPC/start, 201
Starting, 165
Lifebeat monitoring
Message correction, 174
Sign-of-life monitoring, 16
Messages
Locking
Deleting, 174
Messages, 152
Locking/unlocking, 152, 234
Log of the diagnostic screens
Maintenance state, 150
Display, 136
Without area information, 150
Migrating
Diagnostics settings, 140
M Miniport adapter, 84
Maintenance Module
Plant-specific, 118, 119 Depassivation, 236
Sequence, 303 MS Basic
Status diagram, 302 (See Maintenance Station Basic), 15
User-specific, 103, 112 MS Client
Maintenance actions configuring, 56
Configuring, 100 Installation on the ES, 32
Maintenance demanded, 301 MS multiple station system
Maintenance group display Configure MS server, 46, 47
Display, 221 Configure redundant MS server, 47
Maintenance Station, 32
SIMATIC Logon
Roles management, 62, 72
SIMATIC PAM Station V
Analog value monitoring, 79
Variant, 94
Application, 15
Variants
Configuring, 49
Maintenance Station Basic, 15
Project, (Creating)
Maintenance Station Standard, 15
Sample project, (Overview), (use)
SIMATIC PDM Maintenance Station, 15
SIMATIC PDM, 129
Version, 91
Calling, 238
Specifying, 92
Roles management, 63, 73
View
SIMATIC PDM MS
CFU diagnostics, 287
(See PDM Maintenance Station), 15
Connection load display for CPU connections, 266
Compiling, 137
Connection representation for client objects, 253
Downloading, 137
Connection representation for server objects, 255
Header, 233
Diagnostics for AS objects, 257
Sample project, (use)
Diagnostics for field devices, 272
SNMP service, 84
Diagnostics for network objects, 285
SNMP variable
Diagnostics for PC objects, 252
exporting, 89
Diagnostics for user objects, 278
State of the areas
External diagnostics, 277
Overview area, 149
Identity, 241
Status diagram
LED display for CPUs, 270
Maintenance, 302
Maintenance, 246
Structure of the variable
Messages, 245
For the maintenance state, 223
Monitoring for user objects, 280, 283
System configuration
Note, 250
SIMATIC PAM Station, 39
OBx for AS objects, 262
Parameters for AS objects, 264
Parameters for field devices, 276
U PERFDSGW, 288
Unlocking Performance for AS objects, 260
Messages, 152 Status of the CPU, 269
User diagnostic screens
Configure group display hierarchy, 127
Creating, 126 W
User diagnostic structure
Web page
Configuring AssetM, 124
Calling, 96, 239
Configuring PAM_IF, 79
Web pages
Creating, 122
"Overview" button, 158
Creating a CFC, 123
Faceplate, 236
Overview, 121
Working area, 153
Updating in the multiproject, 126
User diagnostics structure
Configuring AssetM, 125
User interface
Button area, 152
Layout, 148
Overview area, 149
Working area, 153
User-specific blocks, 128