show the entry list
WinCC -- Operation and maintenance -- Diagnosing errors (evaluating diagnostics files)
How do you use the "SIMATIC Diagnostics Tool" (SDT) to collect diagnostics and system data?
How do you perform comprehensive diagnostics in PCS 7 and WinCC plants?
What do the error messages "Transfer buffer too small", "TagQueue overflow" and "Messages are lost" mean?
Why does the error "S7OPCIAX" occur in the event display?
How can you recognize resource bottlenecks in advance from WinCC and react to them accordingly?
Where can you find a description of the error messages of the Global Script diagnostics window in WinCC RT?
How can I determine the name of an action via the error message "Execute Error in Action @xxx"?
What can be the cause of the WinCC error message "More than 10000 actions in work" (up to V6.2: "More than 5000 actions in work")?
How can you back up the data of the Windows event viewer?
How do you save the diagnostics data of the Windows system monitor (performance monitor) in a file?
How can you define the amount of memory required for the performance indicator log of the Windows system monitor (performance monitor)?
Where can I find explanations of the error messages of the WinCC diagnostics files License.log, WinCC_SStart_xx.log and WinCC_Sys_xx.log ?
How do you evaluate and remedy "OnErrorExecute"-type configuration errors?
How do you write outputs from the "APDiag" diagnostic tool to a file?
How do you use the diagnostic tool "APDiag" to debug C scripts?
How do you determine the function name from the function ID in the case of APDiag-OnErrorExecute messages?
How do you start the "APDiag" script diagnostics tool?
WinCC -- Configuring Tag Logging -- Tag Logging performance
What influence do the archiving parameters have on the system's performance?
Why are the current values not stored in the database with Tag Logging in WinCC V5.x?
Why is a specified percentage hysteresis not suitable for suppressing minor fluctuations in process values in "archive only upon change" mode?
How can you recognize resource bottlenecks in advance from WinCC and react to them accordingly?
Why are the archives different in size and how can you reduce their size?
Why are the current values not stored in the database with Tag Logging in WinCC V4.0x?
Why are values sometimes lost during archiving?
How much hard drive space do measured values of SIMATIC WinCC V6.0 or PCS 7 V6.0 require?
How can you recognize resource bottlenecks in advance from WinCC and react to them accordingly?
Part number:

As from WinCC version V5.0 SP1, there is the System Info Channel available for this. All the necessary information is available in the WinCC Online Help (WinCC Information System) in this path: Communication > System Info.

The CCPerfMon program also continues to be used system internal. However, the functions described below are no longer available to you. For this, a much more convenient and extensive alternative is made available to you via the System Info Channel.

Below is a description of the desired functions for WinCC version V4.x:

If a sequential log is incorrectly calculated or not exported in time, then it might happen that the hard disk becomes full, for example. The consequence is that WinCC or Windows NT becomes inoperable at some time or other. Using the "CCPerfMon.exe" file in the "..\Siemens\WinCC\bin" path, you can recognize the situation in advance and react appropriately.

The program CCPerfmon.exe (only for WinCC V4.x) generates internal tag that are stored in the @CCPerfMon group in the WinCC Tag Management. Using these tags, it is possible, for example, to have the remaining free capacity of the hard disk displayed in a WinCC picture. In this way the user sees how much space is left on the hard disk and can act before the hard disk gets full. This also gives you the option to react over a global action per Script and, for example, store a message or initialize other actions.

All tag names of this group start with @PerfMon@ followed by the meaning of the resource (see Table 1). The text tag named @CCPERFMON@LASTRUN displays the date and time at which the performance data was last determined. There are also internal tags that are monitored by CCPerfMon (see Table 2). The monitoring sequences run every 5 minutes.


  1. It is best to start CCPerfMon by including the program in the computer's startup list. Enter the program with the option "/h" for "hidden". In this case, the CCPerfMon does not appear in the Windows task bar, but can only be seen in the Windows NT Task Manager.

  1. Now configure an image in which you display the tags described below.

Monitored resources and their meanings

Table 1: Monitored Performance Counter etc. (only Windows NT)






CPU idle time in %


Usage of the export file in %


Free main memory


Free space on disk x (x= C..M as available)

Table 2: Monitored WinCC tags




WinCC queue length


WinCC queue length


WinCC queue length

Explanation of the CCPerfMon dialog

You get this dialog when WinCC is in Runtime mode and CCPerfMon is started manually. In this case, CCPerfMon must not be started via the startup list of the computer. It is useful to employ the dialog if you only want to use CCPerfMon now and again. Note, however, that the associated tags are created automatically in any case.

Table 3: Operating and display elements of the dialog

Dialog field / button



Timer Cycle

Output field

Resource acquisition cycle.

Last Run

Output field

Date / time of last acquisition.

Status of Connection to WinCC

Output field

Status of connection from CCPerfMon to WinCC. If "Connected and in Run Time Mode" is not displayed, CCPerfMon is not running correctly.

Clear Statistics


Delete statistical data of CCPerfMon.

Clear Trace Window


Delete the entry in the Trace window.

Trace Level --


Increase Trace (diagnostics) level (more diagnostics outputs).

Trace Level

Output field

Display of the current Trace (diagnostics) level.

Trace Level ++


Reduce Trace (diagnostics) level (less diagnostics outputs). The default value is 10. Increase the value to about 20 for test purposes to have the Trace outputs displayed also in "normal mode".

Trace Window

Output field

Window for diagnostics outputs. The latest information is always at the top.

Only the values of the server are displayed in the CCPerfMon tags. This is why they are stored with "Project-wide Updating". If you change the setting of the tags to "Local Computer Updating", then these tags are updated only on the server, the "0" values remain on the clients. Therefore, the clients cannot overwrite the values.

 Entry ID:954032   Date:2009-09-15 
I regard this helpfulas not helpful                                 
My Documentation Manager 
Support Request
To this entry
Create PDF 
Send to a friend
Compatibility tool 
Online Help
Guided Tour