When you switch on the SIMATIC IPC277D, it might happen from time to time that no picture is shown when the Windows operating system starts. The backlight is enabled but the screen remains black.
Windows Embedded Standard 7
You can correct this behavior by installing the graphics driver version V1_18_0_3398.
The driver is available from Siemens Technical Support. Use a Support Request to request this specifying your device type or article number:
With the Windows Embedded Standard 7 operating system the Enhanced Write Filter (EWF) must be disabled during the installation. (Detailed information on the topic of EWF is available in Entry ID: 50867677.)
Description The license is displayed correctly in the Automation License Manager, but not taken by the corresponding Runtime software. When you start WinAC RTX and/or WinCC flexible Runtime or WinCC Runtime Advanced, you get this message: "No valid license key can be found". This behavior can occur when a CF card from a third-party manufacturer is being used in the SIMATIC IPCs. Some of these CF cards are recognized as removable media. However, a license can only be used if it is on a hard disk medium. A license can only be transported on a removable medium (also USB stick or floppy disk) but not used.
Instructions This behavior does not occur if you use a SIMATIC CF card that is designed for the SIMATIC IPC. SIMATIC CF cards are always recognized as hard disk media in the SIMATIC IPCs.
An overview of the released storage media is given in Entry ID: 21847868.
How can you improve the boot behavior of SIMATIC IPCs and the SIMATIC Field PG M3?
Description Now and again, booting can take a long time with the SIMATIC IPCs and the SIMATIC Field PG M3. A black screen is displayed during this time. The long boot time does not affect the devices, computing functions or applications in any way.
The behavior described occurs with the hardware and operating systems listed below. Hardware
SIMATIC HMI IPC677C
SIMATIC Field PG M3
Windows XP, 32-bit
Windows Server 2003 R2, 32-bit
Windows Embedded Standard 2009, 32-bit
A defective Windows DLL (Dynamic Link Library) causes new subcodes to be generated constantly in the registry during operation. This behavior causes the registry to grow constantly which in turn prolongs the boot procedure and produces the black screen.
Remedy This behavior is cleared by installing the Intel Management Engine V18.104.22.1687.
You can request the Intel Management Engine V22.214.171.1247 software from Siemens Industry Online Support using a Support Request.
Note With the "Windows Embedded Standard 2009 32-bit" operating system the Enhanced Write Filter (EWF) must be disabled during the installation (see also Entry ID: 40108744).
Instructions Proceed as follows to install the Intel Management Engine.
A new version of the "UNS.exe" file is installed when you install the new Intel Management Engine software.
You can tell whether you already have the latest version installed on your computer from the "UNS.exe" file in the directory
"C:\Program Files\Intel\Intel(R) Management Engine Components\UNS\".
If the UNS.exe file is available in version V126.96.36.1996, then you already have the latest version and do not need an update.
Once you have procured the Intel Management Engine V188.8.131.527 from Siemens Industry Technical Support, unpack the file in a separate directory on your SIMATIC IPC or SIMATIC Field PG M3.
In the "IntelME-Fix" subdirectory you start the batch file "start_repair.bat" with a double-click.
Two DOS windows open during the updating.
Then the computer restarts.
Log on to the computer again. The update is then made automatically. For this a DOS window opens again.
When the update has been completed, the DOS window closes automatically.
You are then using the latest version of the software.
When the computer restarts, the operating system might indicate that new hardware has been found. You can ignore this message. When you install the new Intel Management Engine, the message closes automatically.
Why does the DIAGMONITOR 4.0 software need so much memory after a long period of operation?
Description When you switch on the SIMATIC IPC, it does not start or switches off immediately. If devices/components or plug-in cards with their own power supply are connected to the SIMATIC IPC interfaces, this can lead to so-called regenerative feedback into the SIMATIC IPC. Regenerative feedback can under certain circumstances damage the SIMATIC IPC or the internal computer components.
The component responsible for the regenerative feedback has to be determined by a voltmeter. If you are qualified accordingly, you can determine the component responsible for the regenerative feedback by measuring the voltage at the output connector of the PC power supply unit. You must note the following points to be able to detect a counter voltage in the measuring process:
The SIMATIC IPC must be switched off and the mains connector must be connected.
All the components of the plant that are connected to your SIMATIC IPC must be switched on and active.
If you determine that there are several components that might be the cause of the regenerative feedback, then connect only the component to be checked in each case separately to the SIMATIC IPC.
Possible causes for the regenerative feedback:
PCI-104 modules with additional external power supply (e.g. metrology modules, frame grabber card with camera connected).
External power supply on the 5V supply via a USB interface not in compliance with the USB specification.
Possible culprit components
USB I/Os with their own power supply:
KVM switch with USB and PS/2 interface to the SIMATIC IPC.
KVM switch with USB interface to the Panel.
USB hard disks.
Optical drives with USB connection.
As far as possible, operate components without external power supply or use components that do not have an external power supply.
Generally, regenerative feedback is not permitted for any SIMATIC IPC and must be prevented in all cases by the operator.
Why is the UPS not recognized via USB interface when a Panel PC 477-HMI or -HMI/RTX is operating with a SITOP DC UPS module?
With the pre-loaded software SIMATIC HMI WinCC Flexible 2008 WinXPe this behaviour is caused by the fact that WinCC Flexible uses a USB driver for the USB interconnection (loading of projects via USB-USB-connection).
The SITOP DC UPS software must be installed and the SITOP DC UPS must be connected with the PC (see Entry ID 42822724 or https://www.siemens.com/sitop). In the following table you find a description how to activate the SITOP DC UPS driver.
Open the dialog "Run" in Windows via "Start > Run as..." and enter "devmgmt.msc". By clicking OK the device manager is opened and the driver "USB Bulk Transfer" is displayed.
Click on driver "USB Bulk Transfer" with the right mouse button and select "Properties" in the context menu.
Click on "Update Driver" in register "Driver".
Select option "No, not this time" and click "Next".
Select in the following dialog:
"Install from a list or specific location (Advanced)"
and click "Next".
Choose the directory where you find the SITOP driver and click "Next".
After successful updating the following message appears:
Completing the Hardware Update Wizard
The wizard has finished installing the software for:
SITOP DC-USV 15
Acknowledge the message with "Finish".
In the device manager the component "USB Serial Port" appears. Choose "No, not this time" and click "Next" for the installation of this component by the hardware wizzard..
In the following dialog choose:
"Install from a list or specific location (Advanced)"
and click "Next".
Choose the directory where you find the SITOP driver and click "Next".
After successful installation the following message appears:
Completing the Found New Hardware Wizard
The wizard has finished installing the software for:
SITOP DC-USV 15
Click "Finish" for finishing the installation.
After updating the USB driver and installation of the SITOP DC UPS Com-Port the device manager appears as follows:
Close the device manager.
If the USB-USB driver is needed again, it can be re-installed with the WinCC flexible CD included.
How can you avoid unnecessary "degraded" messages in SIMATIC PCs with RAID1 configuration?
Description In a SIMATIC PC, if a RAID1 hard disk system is reported to be "degraded", this means that a hard disk has failed in the RAID1 array. However, this does not mean that data has been lost. The PC continues to run automatically with the second, intact hard disk (RAID1 functionality). However, now there is no longer hard disk redundancy. The PC can be operated to the next suitable maintenance date.
Cause These are possible causes for "degraded" messages:
A hard disk is defective (hardware error, typical cause for this message).
This message can appear as part of the RAID1 driver's "Bad Block Recovery Handling", even though the hard disk is not defective (rare exception).
"Bad Blocks", also known as "UCRC Failures" (Unrecoverable CRC Failures), can occur when the PC suffers a "hard" switch-off, for example though an abrupt power failure during a write-to-disk procedure. If a "Bad Block" is detected during a read-from-disk procedure, the block concerned is read by the other hard disk of the RAID1 array and the "Bad Block" is corrected. This procedure is called "Bad Block Recovery".
Under certain circumstances, the Storage Manager cannot run the "Bad Block Recovery" procedure properly. This leads to the RAID1 array being reported as "degraded". Just as with a mechanical hardware error, in this case you must also replace the hard drive concerned.
Note The procedure for replacing the hard drive of a RAID1 array is given in the operating instructions of the device concerned.
Products affected The following SIMATIC PCs with RAID1 configuration
Rack PC IL 43
Rack PC 547B
Rack PC 847B
Box PC 627B
Box PC 827B
Panel PC 677B
PCs for PCS 7
IL 43 PCS 7 V6.1 + SP1 bundles
(delivery period: November 2005 to May 2008)
IL 43 PCS 7 V7.0 bundles
(delivery period: January 2007 to May 2008)
RACK 547B PCS 7 V7.0 + SP1
(delivery since October 2007)
RACK 547B PCS 7 V6.1 + SP2
(delivery since January 2008)
in the following operating systems:
Windows 2000, Windows Server 2000
Windows XP, Vista and Windows Server 2003
To ensure correct "Bad Block Handling" and avoid unnecessary "degraded" messages, you must update the RAID driver (Intel Matrix Storage Manager).
Use driver V184.108.40.2062 for Windows 2000 and Windows Server 2000.
Use driver V220.127.116.111 for Windows XP, Vista and Windows Server 2003.
Installation notes Close all applications before installation, because you need to restart.
The SIMATIC IPC DiagMonitor with order number "6ES7648-6CA04-2YX0" is available for evaluating the diagnostics data with SIMATIC IPCs of the C generation.
If the SIMATIC IPC DiagMonitor is installed on the SIMATIC IPC, the a sample WinCC flexible project is installed during the Setup routine.
The sample project is located in the installation path. If the default path is used for the installation, the "DMV4OPCWinCCFlex2008.zip" file is in the following path: "C:\Program Files\Siemens\DiagnosticsManagement\OPC Samples".
Furthermore, a text file is also stored in this path. This text file describes how you can parameterize the DiagMonitor in conjunction with the sample project.
The text file is "readmeWinCCflexible.txt".
1. Requirements and function Specific hardware and software requirements must be met for evaluating the PC diagnostics data.
1.1 Hardware requirements
SIMATIC Microbox 427B, Panel PC 477B
SIMATIC Box PC 627B, SIMATIC Panel PC 677B
SIMATIC Box PC 827B
SIMATIC Panel PC 577B
SIMATIC Rack PC 847B
1.2 Software requirements
SIMATIC PC DiagBase SIMATIC PC DiagBase is freeware that accesses the PC's hardware and provides data like the temperature of the CPU or mainboard in a Windows application. SIMATIC PC DiagBase is the successor to the previous PC diagnostics software "SOM". SIMATIC PC DiagBase is available for downloading in Entry ID 29316343.
PC DiagBridge (PCDiagBridge.exe) The freeware PC DiagBridge is an ActiveX application that provides a programming interface. You can install the software on the SIMATIC Industrial PCs listed above. The diagnostics data is provided via a COM interface. You can download the software at the end of this entry under Download.
WinCCTrigger.ocx The "WinCCTrigger.ocx" is an ActiveX control needed to call the WinCC flexible script cyclically every 2 seconds. The ActiveX control is included in the Download and must be registered on both the configuration PC and the SIMATIC PC.
WinCC flexible Runtime WinCC flexible Runtime must be installed in order to be able to start the WinCC flexible project. WinCC flexible Runtime is subject to license.
BIOS version The hardware diagnostics data depends on the BIOS version, because the "DiagBase API" accesses the BIOS. A BIOS update might be required to be able to evaluate the diagnostics data completely. The "Readme" file of the PC DiagBase gives you the BIOS version required.
1.3 Compatibility The following table shows the compatibility between PCDiag and PCDiagBase.
In the "PCDiagBridge" script, you need the relevant object designation in line 19 for "CreateObject".
Set PCDiag = CreateObject(PCDiag.cPCDiag)
1.4 Function Both software components, PC DiagBase and PC DiagBridge, must be installed on the PC system in order to be able read out the diagnostics data. PC DiagBridge (PCDiagBridge.exe) cannot run without PC DiagBase. In principle, from the user side, WinCC flexible cannot access DLLs (Dynamic Link Library), which is why you need the PC DiagBridge (PCDiagBridge.exe) software. This software serves as a bridge between the system information and WinCC flexible. The ActiveX control "WinCC.Trigger.ocx" starts the "PCDiag Bridge" script cyclically. Data exchange is via the script with PC DiagBridge (PCDiagBridge.exe) and writes the data directly to the internal tag of WinCC flexible. Communication via the script is bidirectional. The PC DiagBridge (PCDiagBridge.exe) software component handles the complete data exchange with the other software and hardware components.
Fig. 01- Technologieschema
In addition to the information from SIMATIC PC DiagBase, PC DiagBridge also provides information on the status of any SITOP UPS connected and any WinAC RTX installed.
Detailed information on PC DiagBridge is available in the associated "Readme" file.
It is only possible to provide data in PC DiagBridge if SIMATIC PC DiagBase is installed on the system.
2. Configuration in WinCC flexible and OCX registration
Download the sample project
Download the file "WinCC_flexible_Projects_PC_Diagnostic.zip" under Download at the end of this entry.
Note: The download contains sample projects for PC 427B, PC 627B and PC 847B.
Open the sample project
Unpack the compressed files.
Open the relevant project for the system concerned.
The three sample projects differ in the configuration only through the different hardware of the PC systems concerned.
Register OCX Trigger You must register the ActiveX control "WinCCTrigger.ocx" on the configuration PC and on the SIMATIC PC.
Copy the "WinCCTrigger.ocx" file (contained in the Download) into the folder "C:\Windows\system32" or "C:\WINNT\system32" (in the Windows installations directory) on your hard disk.
In the Windows Start menu you click on "Run..." and enter the command line "regsvr32 WinCCTrigger.ocx".
Fig. 02 - Ausführen
You get the following message after successful registration:
Fig. 03 - Registrierungs-Meldung
OCX Trigger is an ActiveX control that is needed to call the current data cyclically. ActiveX control is stored on the "Template" picture of WinCC flexible. Only pictures that use this picture template are updated cyclically.
Download and install PC DiagBase
Download the free software SIMATIC PC DiagBase from Entry ID 29316343.
Unpack the compressed ZIP file.
Install SIMATIC PC DiagBase on your SIMATIC PC by clicking on "Setup.exe".
2.1 Content of pictures in the WinCC flexible sample project
OCX Trigger is stored on the template. Once the ActiveX control (OCX Trigger) has been enabled successfully, a stroke of lightning is displayed in a box. The OCX Trigger calls the PCDiagBase script cyclically every 2 seconds.
Fig. 04 - Vorlage
In the Start picture you call the diagnostics picture via the "PC Diagnostic" button. In addition you can have system messages displayed and change the language.
"PC Diagnostic" picture
The sample project contains a diagnostics picture with the following contents (depending on the sample project used):
Fig. 06 - Diagnosebild
If one or more temperature measurements are available for the system used, these are displayed as IO fields and as a bar chart. The dashed yellow line in the bar chart shows the lower limit value and the red dashed line the upper limit value.
The static and dynamic (S.M.A.R.T.) tags are displayed.
If fans are in the system, the speeds are displayed as IO fields with the associated limit values. In addition, each fan is shown with a status display.
Voltage monitoring With SIMATIC PCs the status of the CMOS backup battery is monitored and the number of operating hours displayed. If the CMOS voltage is correct, this is indicated by "OK" in a green box.
Monitoring of SITOP UPS If a SITOP UPS is connected, the LEDs on the front of the UPS light to indicate this.
Monitoring and controlling the WinAC RTX When using a WinAC RTX on the system, the status of the WinAC LEDs can be displayed. You use the "Run" and "Stop" buttons to put the WinAC into the respective modes.
2.2 Content of scripts in the WinCC flexible sample project
This script is called cyclically by the OCX Trigger stored on the picture template. With each trigger the script fetches the current values of PC DiagBridge.
Celsius2Fahrenheit The script converts the temperatures from °C to °F. The temperatures are displayed in degrees Celsius by default. This script must be called in the PC DiagBridge script in order to have the temperatures displayed in degrees Fahrenheit. This script must be called in lines 37, 38 and 39 (see example).
SmartTags("VarPCDiag\LocalPCActTemperature")(i) = Celsius2Fahrenheit(PCDiag.TemperatureCurrent(CLng(i)))
2.3 Notes on integrating the sample project in an existing project You should note the following when integrating the sample WinCC flexible project into an existing project:
The OCX Trigger must be stored on the template so that the diagnostics data can be called cyclically.
The PC DiagBridge script must be copied into the project.
The relevant tags must be copied or created.
3. Verification of the sample project
Create WinCC flexible Runtime
Create the WinCC flexible Runtime by clicking on "Generate" icon in the toolbar.
Fig. 07 - Projekt generieren
Start WinCC flexible Runtime Loader (SIMATIC PC)
Start the "WinCC flexible Runtime Loader" on your SIMATIC PC.
Instructions: By default, WinCC provides the "SYSTEM INFO" channel to display system information. Using the "SYSTEM INFO" channel, you can create tags in the WinCC Tag Management, in which the system enters diagnostics information at runtime. For example, you can create tags that contain the following information at runtime:
Main memory load
Hard disk load
You can use these tags in other WinCC components (e.g. Graphics Designer, Tag Logging, Global Script).
There might be the requirement to display and edit system information that is not provided by the "SYSTEM INFO" channel, for example:
Display of the status of a RAID hard disk system
Display of the temperature of CPU and mainboard
Display of operating or error status of available fans
Display of operating or error status of any available UPS (uninterruptible power supply)
Display of operating or error status of any available PLC software (WinAC RTX)
When using the SIMATIC Industrial PCs listed below, you can display and edit the information described above simply in WinCC Runtime:
SIMATIC IPC DiagBase The "SIMATIC IPC DiagBase" software accesses the hardware of the computer and display the information in a separate Windows application (status of hard disks and fans, temperature of CPU and mainboard). The "SIMATIC IPC DiagBase" software replaces the "SOM" diagnostics software in SIMATIC IPCs.
Until all devices are supplied with it ex works, the software is available for downloading in Entry ID: 29316343 . This entry also contains information on the SIMATIC IPCs that can be implemented.
PCDiagBridge The "PCDiagBridge" software (also called "PCDiag") can be used with one of the above-mentioned SIMATIC Industrial PCs and the "SIMATIC IPC DiagBase" software. It is an ActiveX application that provides a programming interface. You can use this programming interface in WinCC Global Script VBS to access the information of "SIMATIC IPC DiagBase". You can write this information to internal WinCC tags and then use it directly in WinCC pictures, Alarm and Tag Logging.
The "PCDiagBridge" software is available for downloading free of charge in Entry ID: 42674746 . This entry also contains information on the SIMATIC IPCs that can be implemented.
SIMATIC PCDiagBase V1.0
SIMATIC PCDiagBase V1.1
SIMATIC PCDiagBase V1.2
SIMATIC PCDiagBase V18.104.22.168
SIMATIC IPC DiagBase V22.214.171.124
In addition to the information from "SIMATIC IPC DiagBase", "PCDiagBridge" also provides information on the status of any SITOP UPS connected and any WinAC RTX installed.
Detailed information on PCDiagBridge is available in the associated "Readme" file.
SITOP UPS USB driver (FTD2XX.SYS)
If the information of a connected SITOP UPS is to be read out with "PCDiagBridge", the USB driver for the SITOP UPS must be installed.
This entry provides a project in WinCC V7.0, which demonstrates how to use PCDiagBridge and the "SYSTEM INFO" channel.
Configuring the "SYSTEM INFO" channel (for displaying CPU, main memory and hard disk loads)
Below we describe the steps to be taken in the sample project to display the information of the "SYSTEM INFO" channel.
Create "System Info" channel
In the WinCC Explorer, right-click the "Tag Management" item. A pop-up menu opens. Select the "Add new driver..." item. The "Add new driver" window opens. Select the ""System Info.chn" file and then the "Open" button.
Create tags in the Tag Management Create the tags for system diagnostics in the "System Info.chn" channel. The figure below shows the tags created in the "System Info" channel.
In the "Tag properties" dialog, under "Address", you can select the hardware property (resource) you require to display the tag.
In this example we use the "SYSINFO_MEM_UsedPercent" tag to display the main memory used. This tag has the "Available main memory" function and the "Free mem in %" format as address parameters. Linear scaling is used with this tag to convert the "available main memory" value into the "main memory used" value.
Use tags in the picture Create a new picture in the Graphics Designer to display the CPU, main memory and hard disk utilization at Runtime. In this sample project we use the picture name "PCDiagSysInfo.pdl". This picture is used as the Start picture of WinCC Runtime.
The "PCDiagSysInfo.pdl" picture contains the following information:
General project information
Project name (Name)
The project name is displayed as "static text". The "Text" property of the text field is dynamized with VBScript.
The VBS instruction "item.Text = HMIRuntime.ActivateProject.Name" is used to display the project name.
Project path (Path):
The project path is displayed as "static text". The "Text" property of the text field is dynamized with VBScript.
The VBS instruction "item.Text = HMIRuntime.ActivateProject.Path" is used to display the project path.
The DataSourceName is displayed as "static text". The "Text" property of the text field is linked directly to the WinCC system tag "@DatasourceNameRT".
The percentage value of the CPU load is displayed directly in the picture by the "SYSINFO_CPU_UtilizationTotal" tag. The display is made:
in an IO field
in a bar graph
in the WinCC OnlineTrendControl
If the "WinAC RTX" is also running on the computer, a CPU load of 100% is displayed. The reason for this behavior is the "RtxServer.exe" utility. However, it only seems to load the system so much. This behavior is intended so that the CPU is always loaded and not clocked down by power-saving functions of the operating system.
Main memory load
The percentage value of the memory load is displayed directly in the picture by the "SYSINFO_MEM_UsedPercent" tag. The display is made:
in an IO field
in a bar graph
in the WinCC OnlineTrendControl
Hard disk memory load
The percentage value of the memory load of the available hard disk partitions is displayed directly in the picture by the "SYSINFO_DISK_C_FreePercent" tag. The display is made:
in an IO field
in a pie chart (similar to the function in Windows Explorer) where the ellipse is more blue or magenta according to the hard disk space available.
When the hard disk is full, the ellipse is completely blue.
When the hard disk is empty, the ellipse is completely magenta.
Dynamization is done with the dynamic dialog.
Button for selecting the "PCDiagBase.pdl" picture
This button is used to select the "PCDiagBase.pdl" picture at runtime. The PCDiagBase picture contains diagnostics information that is read out by PCDiagBridge. The background color of the button is dynamized according to the error status. If there are no errors in the diagnostics information of PCDiagBridge, then the background color of the button is gray, otherwise red.
Tag Logging CPU, main memory and hard disk are archived in Tag Logging. The size of the Tag Logging archive (Tag Logging FAST and SLOW) is set as follows:
Max. size of 1 segment: 100 MB
Max. duration of 1 segment: 1 day
Max. size of all segments: 700 MB
Max. duration of all segments: 1 week
Configure Alarm Logging The tags of the SYSTEM INFO channel do not trigger any messages or alarms in this project. However, you can monitor the tags of the SYSTEM INFO channel yourself via script or using the "Analog Alarm" function of Alarm Logging.
Configuring PCDiagBridge (for displaying temperature, fan error status, hard disks, UPS)
Below we describe the configuration steps to be taken in the sample project to display the information of PCDiagBridge.
Create tags in Tag Management PCDiagBridge provides an object and methods for reading out hardware information. In this step, you must create the WinCC tags to which the PCDiagBridge information is to be written later. The tag names are the same as the PCDiagBridge methods for reading the information. For the sake of clarity, a separate tag group entitled "PCDiag" is used and the prefix "PCDIAG" is given to the tag names. The following figures show the tags for the different types of PCDiagBridge information as hard copy of the Tag Management.
Tags for temperature monitoring:
Tags for fan monitoring:
Tags for hard disk monitoring:
Tags for voltage monitoring:
Tags for UPS monitoring:
Note: The "PCDIAG_UPS_ExitWinCC" tag is not provided by PCDiagBridge, but serves as a trigger to call a script if the power fails. This script first closes WinCC and then shuts down the whole system.
Assign values to tags with VBScript Create a cyclic action in WinCC Global Script VBS to read hardware information with PCDiagBridge. The following figure shows an excerpt from the script.
If you are using a version of "PCDiagBridge" that is older than V1.1.1, then you must replace the line:
Set PCDiag = CreateObject("PCDiagBridge.cPCDiag") (line 33 in the Text file)
with the line:
Set PCDiag = CreateObject("PCDiag.cPCDiag")
Display tags in the picture The information read with PCDiagBridge is displayed in the picture "PCDiagBase.pdl".
Temperature monitoring: If one or more temperature measurements are available in the system, these are displayed with the associated limit values as IO fields and as a bar chart.
Fan monitoring: If one or more fans are available in the system, the speeds are displayed with the associated limit values as IO fields. In addition, each fan is shown with a status display. The different statuses of a fan are defined in the "PCDiagBase_Fan_ICON.pdl" picture.
Tags for hard disk monitoring: The static hard disk data (Model, Device Name) and the dynamic data (S.M.A.R.T. information) is displayed. The S.M.A.R.T. information is displayed as text via dynamic dialog.
Note: The dynamic dialog has the advantage that in the Graphics Designer, you can simply configure change of language for the different display texts.
Tags for voltage monitoring: In all SIMATIC IPCs, only the voltage of the CMOS backup battery is monitored. If the voltage is OK, a little green box is displayed, otherwise a little red box. In the "PCDiagBase_STATUS_ICON.pdl" picture, the different colors used for dynamization are defined. The different colors are stored as EMF files and are used in WinCC status displays.
Tags for UPS monitoring: If a SITOP UPS is in the system, the LEDs on the front of the SITOP UPS are shown in the picture. A detailed description of the meaning of the separate displays is available in the operating instructions for the "SITOP DC UPS Module".
In the UPS area, there is an additional option check box marked "Shutdown". WinCC is terminated and the computer shut down if the following conditions are fulfilled:
The "Shutdown" check box is checked.
The load status of the UPS backup battery is less than 85%.
The UPS is in backup mode.
The "Shutdown" function is triggered by a cyclic C action.
The action is triggered by the tags "PCDIAG_UPSStateBuffering" and "PCDIAG_UPSStateBufferOK".
WinCC Alarm Control The WinCC Alarm Control is used to display alarm, warning and operating messages.
If a particular hardware device fails, it is also displayed in the picture with a square red background.
The tags "DiskAlarm", "TempAlarm", "FanAlarm", "VoltageAlarm" and "UPSState" are used to display a fault. These tags are bit coded. This means that if a bit is set, there is violation of the upper or lower limit value of a hardware device. The bit position corresponds to the number of the device.
Tag Logging The tags of PCDiagBridge are not archived in Tag Logging.
Configure Alarm Logging The figure below shows the configuration of the Alarm Logging.
Max. size of 1 segment: 50 MB
Max. duration of 1 segment: 1 week
Max. size of all segments: 500 MB
Max. duration of all segments: 1 year
Version: This entry has been tested with the following versions.
Product and version designation
PC operating system
Microsoft Windows XP Professional SP2
SIMATIC PC DiagBase V1.2
SIMATIC PC DiagBase V126.96.36.199
SIMATIC WinCC V7.0
Why does the display on the Panel PC 677 or the monitor on the Box PC 627 sometimes go monochrome (black, pink, blue ...)?
Description In rare cases it might happen that the monitor connected to the Box PC 627 or the display of the Panel PC 677 goes monochrome during operation (pink, green, black, gray, white ...). The plant display is then no longer visible. But the PC continues to be fully functional and the current PC application continues to run. After a restart the display is fully restored on the display or monitor.
You can clear the behavior described above by installing the graphics driver newly adapted by Siemens (product version PV 14.18, driver version: 188.8.131.5221).
More information about the Intel 915GM display driver is available in Entry ID: 51339179.
Note To ensure full functionality of the PC it is absolutely necessary to install the new driver version V184.108.40.20621. This driver has been adapted for the Box PC 627 and the Panel PC 677 and is not identical with the original Intel graphics driver! You must therefore use the driver from the Siemens "Documentation & Drivers CD 04/2006" or from the Siemens download area.
Prink screen, Display, Graphics driver
What do you need to watch out for when restoring a Vista image with the Image Creator V2.0?
Description: After restoring a hard disk image with Windows Vista operating system, Windows can no longer be started. The following message is displayed instead:
In the Master Boot Record (MBR) of the hard disk a "Disk-Signature" is entered. The Windows Vista boot configuration is saved in the file \Boot\BCD (Boot Configuration Data). The partitions of the computer are referenced in the BCD via the "Disk Signature". If the BCD and the MBR are not identical, this behavior occurs. Therefore Windows Vista cannot boot and the message from Fig. 01 appears.
The operating system has to be repaired with the recovery DVD that came with it. Proceed as follows to repair:
Place the recovery DVD in the CD-ROM\DVD.
Restart the computer.
You do this via the key combination "Ctrl + Alt + DEL".
Open the boot menu via the key "Esc" or "F12" and select the CD-ROM\DVD drive.
Press any key if the following request appears on your screen: "Press any key to boot from CD or DVD"
The following message now appears:
Now select "Repair and restart".
Remove the DVD from the CD-ROM\DVD drive.
Restart the computer.
After you restart the computer, Vista is started and the following message appears:
Restart the computer by selecting the "Restart Now" button.
The repair has now been successfully completed.
To prevent the message mentioned above in Fig.01, you have to adapt the BCD data before creating a GHOST image. Open the command console via START -> Run and the command "cmd" with administrator rights. Now enter the three following commands:
You must then check the result:
The following values and entries are important here:
Windows Boot Manager -> device = "boot"
Windows Boot Loader -> device = "boot"
Windows Boot Loader -> osdevice = "boot"
Explanation of terms:
Disk Signature is used by Windows 2000 and Windows XP to clearly identify hard drives that have a classic partition table.
Why are no limit values set for the SOM application when the operating system language is changed?
Description: The behavior described above for the SOM application occurs when not only the language for the menus and dialog fields, but also the settings for the programs that do not support Unicode are changed to Japanese.
The cause of this behavior lies in the fact that the SOM application (Savecard On Motherboard) does not work on a UNICODE basis. Strings that have written in the Registry might be wrongly interpreted after switching the Windows operating system XP Pro MUI (Multilanguage).
After switching the language to Japanese you must uninstall the SOM, restart the PC and then reinstall the SOM. Then restart again and the SOM will work with the correct limit values.
Cursor positioning with SIMATIC Panel PC 670 / 870 with touch screen
QUESTION: On a SIMATIC Panel PC 670 / 870 with
touch screen, why under certain circumstances does the cursor
appear at the edge of the screen on the opposite side when
ANSWER: This behavior occurs with the operating system
Windows NT 4.0 SP5 and SP6 and only whenthe
touch screen has been calibrated with a 5-point calibration. This
behavior does not occur with a 2-point calibration.
A patch has been developed that sets the
error-free 2-point calibration as the default type of
Copy the self-extracting 5Point_Patch.exe file
into a directory.
Open the 5Point_Patch.exe file.
Call the SETUP.EXE file.
Reboot the computer.
Now the 2-point calibration is set as the
default type of calibration.
QUESTION: Simultaneous pressing of the multiple
function keys on the SIMATIC Panel PC 670 and Panel PC 870 is not
permissible. How can I prevent any possible mistakes?
ANSWER: You can prevent any above-mentioned operating
errors by using the software tool KeyTools. KeyTools has two
WinCC hotkey function (only required for
WinCC): KeyTools rotates the key codes of the function
keys F13 - F20 and S1 - S16 on a SIMATIC Panel PC 670 and Panel PC
870 with touchscreen front on which the application WinCC is being
operated. KeyTools is only needed for Windows NT 4.0, Windows 2000
and Windows XP, because in Windows 98SE the key code rotates
Security features (needed for all SIMATIC Panel PCs with
KeyTools installs a counter-locking mechanism for the function
keys F1 - F20 and S1 - S16. If you press several function keys at
the same time, then only the function of the first key pressed is
activated. All the other function keys are ignored.
Please refer to Entry ID: 17159836 for detailed descriptions
of the functions, notes on installation and the software
Failure of the functions of various components after installing the real-time kernel on the Panel PC under Windows NT 4.0 SP6a
Why, after installing the real-time kernel RTX doesn't the
communication with the communications processor CP 5613 work and
why don't the keyboard and mouse no longer function on my Panel PC
670/ 870 under Windows NT 4.0 SP6a?
ANSWER: The BIOS distributes the interrupts between
IRQ 5, IRQ 9, IRQ 11 etc. If the resources of the CP 5613 MPI and
the USB stack fall on same IRQ, then there is an interrupt
Under Windows NT you have to configure your PC / PG so that the CP
5613 does not use the IRQ number jointly with another
Windows NT device.
Install the CP 5613 in the following order:
For Panel PC 670:
Install the card in the back slot (1). PC_670 ( 266 KB )
For Panel PC 870:
Install the card in slot 2. PC_870 ( 270 KB )
In the BIOS set the entry for "Advanced" > " Reset
Configuration data" to "[Yes]".
Install WinLC RTX.
Then you can run all the other hardware and software
Warning: Do not install the CP5613 software
from the SIMATIC NET CD after you have installed the WinLC RTX
More installation instructions are available in the manual
"Windows Logic Controller (WinLC RTX)" (Entry ID: 7216121),
section 2.6 "Special instructions for installing the CP 5613
Description: If an image that has been created on a Panel PC 670 V1 (6AV76...) is subsequently installed on a Panel PC 670 V2 (6AV77...), the following message appears when the PC starts up:
It was not possible to read from the standard data carrier selected. Check the Start path and the data carrier hardware. Read the Windows NT documentation for information on the hardware hard disk configuration.
The boot procedure is then aborted. The reason for the system behavior is that the Panel PC 670 V2 is not image-compatible with the Panel PC 670 V1. An image that has been created on a Panel PC 670 V1 cannot be installed on a Panel PC 670 V2.