Description You have a WinCC project and no longer know which version of WinCC was used to create the project.
Note
These instructions are valid only for the Windows XP operating system.
Instructions Use Windows Explorer to open the "GraCS" folder of your WinCC project. Sort this folder by date in descending order (Date Modified). Hover with the mouse pointer on the latest PDL file and the tooltip text is displayed. The tooltip text consists of a header, working area and footer. The type and title are displayed in the header. The WinCC version used to save the PDL file is displayed in the working area. The date of the last modification and the size of the file are displayed in the footer. The WinCC version displayed last in the working area should also be the version of WinCC last used to process the project.
Fig. 01
Note
If the picture has been saved with multiple versions, it might happen that not the last version of WinCC used to process the PDL file is displayed in the working area. The reason for this is that the size of the tooltip text is limited depending on the operating system. You can tell this by the fact that the text is truncated in the working area. Then try the procedure with the next PDL file.
Fig. 02
TIP Run the "Convert Pictures" function to ensure that all the pictures are saved with the current version of WinCC. Open the WinCC Explorer, mark the Graphics Designer and right-click to open the pop-up menu. Execute the "Convert Picture" function. This saves all the pictures of the open project with the current version and current date. You should do this before doing long-term archiving of a WinCC project.
How can you prevent operations or value changes being made simultaneously by multiple WinCC clients?
Description When processing critical process values (for controlling pumps, for example) you must make sure that operations and value changes cannot be made simultaneously by multiple clients.
For example, if the picture window for entering setpoint values for a pump is open on one client, then it must be impossible to open that picture window on all other clients.
Instructions
No.
Procedure
1
Create binary tag Create a binary tag named "ReleaseOperation" in the WinCC Explorer.
If you use the "Redundancy" options package, "Tag synchronization" must also be enabled.
Fig. 01
In the "Limits/Reporting" tab you specify the value "1" as start value for the tags.
Fig. 02
2
Configure picture In the Graphics Designer, configure a new picture with the "PumpWindow" picture window and a button to display the picture window.
Fig. 03
3
Parameterize button
Label the button with this text: "Open pump window".
Fig. 04
Dynamize the operator-control enable of the "Button" button in the "Properties" tab ("Button > Miscellaneous > Operator-Control Enable") with the "ReleaseOperation" tag.
Fig. 05
Configure a direct connection to the "Button" button in the "Events" tab ("Button > Mouse > Mouse Action").
Fig. 06
Fig. 07
4
Parameterize picture window In the Object Properties of the "PumpWindow" picture window, select the "Properties" tab and set the value "No" for "Display" ("Picture window > Miscellaneous > Display").
Specify the picture name of the pump picture in the same mask.
Fig. 08
5
Create a new script As long as the "PumpWindow" picture window is displayed the "Button" button must not receive operator-control enable.
For this, in the Object Properties of the "PumpWindow" picture window you select the "Events" tab and dynamize the display ("Picture Window > Property Topics > Miscellaneous > Display > Change").
Fig. 09
Close picture window There are several ways of closing the picture window:
In the Object Properties of the "PumpWindow" picture window, select the "Properties" tab ("Picture window > Miscellaneous") and set the value "Yes" for the "Border", "Title", "Can Be Maximized" and "Can Be Closed" attributes.
In the pump picture you configure a button that will be displayed in the "PumpWindow" picture window. Open the Object Properties dialog of the button, select the "Events" tab ("Button > Mouse > Mouse Action") and create the direct connection below.
Fig. 10
Note:
Instead of the direct connection, a VB script is also possible if multiple decision criteria are required for closing the picture window:
"Parent.Visible = False"
How do you use a monitor with a 1680x1050 pixel resolution with the OS project editor in WinCC?
The directories contain the configuration files and the static sized WinCC pictures for the OS project editor.
2
Configuring the OS project editor
Start the WinCC Explorer and create a new project. Start the OS project editor. The screen layout options available for selection will vary depending on the project used. In the case of single-user station projects, the only option available is the "Standard" layout.
Fig. 01
Apply the required settings and close the project editor again.
3
Creating pictures for the working area
The WinCC pictures for the working area now have a native resolution of 1680x817 pixels. This resolution has also been defined by the OS project editor as a default for new pictures.
If you use larger pictures, scroll bars appear in the working area.
Fig. 02
Note
Should you wish to use another screen resolution which is not available yet, you can create the requisite configuration files yourself. You can use an existing configuration as a template. It can be found in the WinCC installation directory in the folder "...\WinCC\options\pdl\", or use the files which are provided in this project. Also change the static sized WinCC pictures accordingly.
Configuration Notes The following WinCC components must be installed to be able to import a WinCC project into a STEP 7 project:
SIMATIC Device Drivers
Object Manager
AS-OS Engineering
These components are on the WinCC Installation CD (Fig. 01). Furthermore, WinCC and STEP 7 have to be installed on the same computer. By importing the WinCC project into a STEP 7 project you can use the existing compression tool (packer) for archiving the WinCC project.
Fig. 01
Note More information on installing additional components (taking the example of "Smart Tools") in different versions of WinCC is available in Entry ID: 10880206 .
Instructions You have the following options for importing a previously separate WinCC project into your STEP 7 project:
In the SIMATIC Manager you execute the menu command "Options > OS Import...".
Fig. 02
2
Press the button marked to open the selection window shown in Fig. 04.
Fig. 03
3
Select the Projectname.mcp file that you wish to import and press the "Open" button.
Fig. 04
4
Check the project path for the OS to be imported and press the "Import OS" button.
Fig. 05
Note
More information on importing WinCC projects with the SIMATIC Manager is available in the WinCC Information System > Working with WinCC > The Integration of WinCC in SIMATIC Manger > Managing WinCC Projects and Objects with SIMATIC Manager > Importing a WinCC Project with SIMATIC Manager.
2. General procedure for all versions of WinCC
No.
Procedure
1
Insert an Operator Station (OS) into your STEP 7 project.
Fig. 06
2
Change the name of the OS to the one in your WinCC project.
Fig. 07
3
In the Windows Explorer, delete the WinCC project created in the STEP 7 project path, which is generated because of the newly created OS.
Sample project path:
C:\Programs\Siemens\Step7\EXAMPLES\exie\wincproj\'Name of the OS'
4
Now store the existing WinCC project in the STEP 7 project path using the Project Duplicator via the menu item "Save as...". You start the Project Duplicator in the Start menu under "Start > Simatic > WinCC > Tools".
Note
More information on importing WinCC projects with the SIMATIC Manager is available in the WinCC Information System > Working with WinCC > The Integration of WinCC in SIMATIC Manger > Managing WinCC Projects and Objects with SIMATIC Manager > Importing a WinCC Project with SIMATIC Manager.
Creation environment The instructions in this entry were created in the following environment.
Component
Product and version designation
PC operating system
Microsoft Server 2003 SP2
Standard tools
STEP 7 V5.4 SP4
HMI software
WinCC 7.0
Options
---
Controllers
---
How do you activate access protection for a STEP 7 project and set up a user as project editor?
Instructions: STEP 7's access protection permits you to protect projects and libraries with a project password. To set up access protection for a STEP 7 project, you need at least STEP 7 V5.4 and the options package SIMATIC Logon version 1.3 or higher. You can then implement the following functions:
Protect STEP 7 projects and libraries against unauthorized access so that only authorized users can open the protected projects.
Log online activities and logon procedures on the computer so that you can trace accesses and changes at any time.
The access-protected projects can be synchronized in a multiproject.
The table below describes how to proceed to enable access protection and set up a user as project editor for your STEP 7 project.
No.
Procedure:
1
If you wish to add a project editor for your STEP 7 project in the user administration, then you must assign the appropriate user rights to that user beforehand in the user accounts via the Control Panel of the operating system. You must have administrator rights to create or change user rights in the Control Panel.
Fig. 01 shows an example for the user "Login_Test" with restricted access who has been set up in the user accounts via the Control Panel in Windows XP.
Fig. 01
More information on assigning and changing users and user rights is available in our FAQ entitled
"How do you assign standard user and administrator rights in the MS Windows 2000/NT/XP operating systems?"
in Entry ID: 21412424.
2
In the SIMATIC Manager you open the STEP 7 project to be protected and enable the access protection via the menu command "Options > Access Protection > Enable".
Fig. 02
Acknowledge the message displayed with "YES". You can no longer open the project with versions of STEP 7 older than V5.4. However, if you want to edit the project again with an older version of STEP 7, e.g. version V5.3, then you must disable the access protection beforehand.
Fig. 03
3
If the SIMATIC Logon Service is installed, the dialog shown in Fig. 04 opens. Enter your user name, password and the domain with which you also log on to the network when the PC is turned on. You need administrator rights for first-time logon and for setting up the project password.
Fig. 04
Confirm with OK.
4
In the "Enable Access Protection" dialog that opens next, you assign a project password and confirm with OK. The basic functions for access protection are now enabled and the additional menu items are released under "Options > Access Protection".
Fig. 05
5
Now, in order to set up a user a project editor you open the user administration in the SIMATIC Manager via the menu command "Options > Access Protection > Manage...".
Fig. 06
Note:
The SIMATIC Logon Admin Tool opens. If this is the first time you are enabling access protection, the current SIMATIC Logon user is entered automatically in the role of "Project Administrator".
Fig. 07
6
Now, in the role of "Project editor", you mark "Groups and users" and then in "Available groups and users", you click on the local computer - here in this example "AD110374NB" (this computer). Then drag and drop the Windows user (here in this example "Login_Test" as shown in Fig. 08) to the role of "Project editor".
This newly entered user only has the right to edit a project, but not to change the project protection.
Fig. 08
Save your changes under "File > Save" and close the user administration tool.
7
Then enable the change log using the menu command "Options > Change Log > Enable". The access functions are now completely enabled.
Fig. 09
Then close the STEP 7 project in the SIMATIC Manager.
8
To logon as project editor with restricted function rights you open the logon service in the SIMATIC Manager via the menu command "Options > SIMATIC Logon Service..." (explicit logon). The logon is retained when the project is closed.
Fig. 10
Note:
You can also open the access-protected project and enter the project editor in the logon dialog (implicit logon). In this case the project editor is automatically logged off when the project is closed.
9
In the following dialog you enter the data for the project editor who has been set up.
Fig. 11
The new user is displayed in the status line of the SIMATIC Manager at the bottom right.
10
Now, when you open the STEP 7 project to be protected, you can edit the project with the right as project editor, but not with the right to change the access protection. The functions cannot be enabled and are grayed out (Fig. 12).
Fig. 12
You can also open the project to be protected under a user who is not entered in the project administration. In this case, the "Enter Project Password" dialog opens when the project is opened. Here you must enter the correct password for the project, otherwise the project is protected against unauthorized access and does not open.
Fig. 13
After entering the correct password, the project opens and you can edit it. With the correct password, the logged-on SIMATIC Logon user is automatically entered as Project Administrator.
Note:
More information is also available in the STEP 7 Online Help under "Information on access protection".
Note on the integrated WinCC and WinCC flexible projects:
You cannot set up access protection for WinCC and WinCC flexible projects integrated in STEP 7.
Description You can only rename a WinCC project in the SIMATIC Manager or via the project duplicator. You can change the name of the OS directly in the SIMATIC Manager. The relevant changes are made automatically by the system the next time you open the WinCC project from the SIMATIC Manager. In the case of the Project Duplicator, you use the "Save as..." function and specify the new project name as the file name.
Note If you rename your project in the Windows Explorer, you can no longer open it with the WinCC Explorer.
In WinCC, how do you activate and deactivate the global color and global shadow for all objects in a picture?
Description
With the "ChangeGlobalSettings" add-in for WinCC, a new menu entitled "Change Global Properties" is added to the menu bar in the WinCC Graphics Designer.
With the "Change Global Color Scheme" menu command of this menu, you open a dialog with which you can activate and deactivate the "global color scheme" for all objects of the active window.
With the "Change Global Shadow" menu command of this menu, you open a dialog with which you can activate and deactivate the "global shadow" for all objects of the active window.
This add-in is only tested and available for Windows XP and Windows 7.
You can create add-ins for all VBA functions. This simplifies the organization of VBA functions. Creating ".dll" files permits simple saving and project-wide and computer-wide reusability of VBA functions. More information is available in the WinCC Information System under:
Working with WinCC > VBA for automated configuration > AddIns
You can also change the global properties as follows.
Click in the free area of the WinCC picture in the Graphics Designer.
Press "Ctrl+A" on the keyboard.
Right-click a marked picture element and in the Properties dialog that opens, change the "Global Shadow" and "Global Color" properties.
Installation
No.
Procedure
1
Download the "ChangeGlobalSettings.zip" file from this page and unpack the file in a folder of your choice on the hard disk, which does not have any special characters (C:\WinCCAddIns, for example).
2
Close the Graphics Designer and WinCC.
Click the Windows "Start" button and then "Run...".
3
Enter the following command: (<Path> = Storage location of the dll file).
regsvr32 <Path>\ChangeGlobalSettings.dll
(regsvr32 C:\WinCCAddIns\ChangeGlobalSettings.dll, for example)
4
Start WinCC and then open the Graphics Designer.
5
In the menu bar of the Graphics Designer, click on "Tools > Add-In Manager".
6
In the Add-In Manager, under "Available Add-Ins" you mark the entry "Change Global Project Setting" and activate the two check boxes "Loaded/Unloaded" and "Load on Startup". Then close the dialog box with "OK".
Creation environment
Component
Product and version designation
PC operating system
Windows XP Prof. SP3; Windows 7 (Ultimate)
Standard tools
SCADA software
WinCC V7.0 SP2 Upd 4
Necessary options
Controllers
Keywords
Extension, Script
How can you reduce the size of the transaction file (*.LDF) of the database of a WinCC project?
Description The configuration and runtime databases of WinCC grow rapidly if many changes are made over a long period of time. This applies mainly to the transaction file (*.LDF) of the database. You can reduce the size of this file in two ways:
Via settings in the SQL Server Management Studio.
Via a VBS script.
Both ways are described below.
Note Make a backup of your project before proceeding as follows. More information on making backups is available in Entry ID: 38493803
Instructions for "shrinking" in the SQL Server Management Studio
No.
Procedure
1
Open your WinCC project with the WinCC Explorer. WinCC Runtime must not be started.
2
Start the SQL Server Management Studio via "Start > Programs > Microsoft SQL Server 2005 > SQL Server Management Studio". Connect to the SQL server via the "Connect" button.
3
Right-click on "Databases" in the left window. Your database is displayed with CC_... in the left window of the SQL Server Management Studio .
4
Right-click on your database. Select "Properties" in the pop-up menu. In the window that opens, you right-click on "Options". Change the "Recovery Model" setting from "Full" to "Simple". Close this dialog with the "OK" button.
5
Right-click again on your database. Select "Tasks > Shrink > Database" in the pop-up menu. Under "Shrink action", select the setting "Reorganize pages before releasing unused space". Leave the "Maximum free space in files after shrinking" setting at 0%. Click the "OK" button to close the dialog. Now your LDF file has been reduced. Note The "Recovery model" property can remain set to "Simple".
6
Close the SQL Server Management Studio.
Now in the path of your project you see that the LDF file has shrunk. You can restart your WinCC Runtime project.
Instructions for "shrinking" with a VBS script
No.
Procedure
1
Start your WinCC project in the WinCC Explorer.
2
Unpack the attached VBS script on your computer. Start the script and wait until a dialog is displayed with the message "End of Shrink". Close this dialog with the "OK" button.
Note You must have administrator rights on the local computer with the WinCC project in order to execute the script. All the connected databases beginning with the characters "CC_" are then shrunk.
QUESTION:. How can you change the name of a project in the database?
ANSWER:
The responsibility for changes made in the project database always lies in the hands of the user.
In any case you must always create a back-up of the project database (<Project name>.DB) before proceeding as described below:
Start the application "Scview.exe". This application is usually located in the Siemens\Common\sqlany path.
Log into the database under the menu item "TOOLS CONNECT".
ID:
dba
Login:
sql
Server name:
Computer name
Database name
Project name.db
Database file:
Use the browser here to find the relevant database file
If the link to the database is successful, select the "Tables" item in the database explorer.
Now all the tables in the database are displayed. You need the table "MCPTPROJECT".
Open the relevant table using "View data". Now a "DATA", a "STATISTICS" and a "COMMAND" window are opened.
The "Command" window already displays the line "SELECT * FROM "DBA"."MCPTPROJECT".
Terminate this line with a semicolon and enter the following command line:
SELECT * FROM MCPTPROJECT
<EXECUTE>
UPDATE MCPTPROJECT SET PROJECTNAME = '<New name>'
<EXECUTE>
If you are not quite familiar with the SQL database, read the Help file in the database.
The Help file also offers useful information on other operations, changes and procedures.
Setting configuration to "not activated" in the database
QUESTION: How can you set the status of a configuration
to "not activated" outside WinCC?
ANSWER: If you can no longer start up a configuration
in activated status, then this can be put into the inactivated
status by executing the following commands.
IMPORTANT
Generally no responsibility shall be taken for any changes made
directly to the configuration database, as this is the responsibility
of the user. In any case it is recommended to make a back-up of
the configuration database (<configurationname>.DB) before
accessing as follows:
Start the application "ISQL.EXE" using
"Execute" in the task bar.
Under the menu item Command CONNECT the user
must log in to the database:
ID: dba
Login: sql
Database file: here you must enter the database file with full
path name.
If a connection has been set up to the database,
you must enter the following commands in the "Command"
window and run each one using "EXECUTE".
SELECT * FROM MCPTPROJECT
<EXECUTE>
UPDATE MCPTPROJECT SET PROJECTMODE=1
<EXECUTE>
What should you watch out for in particular when using the WinCC Project Duplicator with downtime monitors and process monitors?
Standard procedure According to the standard procedure in WinCC, you use the WinCC project duplicator to make a copy or backup of a WinCC project.
Detailed information on the WinCC project duplicator is available under:
"WinCC Information System > Working with WinCC > Working with Projects > Duplicating and Archiving Projects"
Exception: PI option
If the PI option is used with downtime Monitor V1.0 or Process Monitor Server V1.0, then the WinCC project data is not transferred correctly with the duplicator.
You will probably not be able to start the target project. In this case, proceed as follows:
1. Back up and duplicate the WinCC project data including the DTM/PCM data
No.
Procedure
1
Open the WinCC source project
Open the source project with WinCC Explorer and stop the WinCC Runtime if started.
2
Open the Project Manager
Click on "PI Option" in the navigation tree of the WinCC Explorer.
Right-click to open the pop-up menu " "Administrative Tools"".
In the pop-up menu you select "Open Project Administrative Tools".
The Project Manager dialog opens.
3
Open the wizard for exporting DTM/PCM data
In the Project Manager, select "Tools > Export Project".
Fig. 01
Opening the "Export Project Wizard"
4
Export the DTM/PCM data
Click on "Next" in the "Export Project Wizard".
Enter a name and path and then click on "Next".
Fig. 02
Click again on "Next".
For "What do you want to export?" select either "Configuration Database"
or "Configuration Database and Online Database Set"
or "Configuration Database, Online and Offline Database Set"
Fig. 03
Click on "Next" through to the end,
because you normally do not need to enter anything else
(dependent on the settings of the DTM or PCM).
Click on "Finish".
The PI data is exported.
Acknowledge with "OK".
5
Delete PI project
Delete the PI project in the Project Manager.
Fig. 04
6
Note user authorizations for the PI option
In the User Administrator, note the authorizations for the levels 600-605 for each WinCC user.
Note:
Levels 600-605 are authorization reservations for PI Option DTM/PCM, which will be deleted in the next step.
7
Disable PI Option
Right-click to open the pop-up menu "PI_Option > Administrative Tools".
Select the menu item "Options".
Fig. 05
In the "Options" dialog you select "Disable PI Option".
Fig. 06
Acknowledge with "OK".
8
Transfer the previous configuration
Close the WinCC Explorer and re-open it to make the disabling of PI Options effective in the project.
9
Preparations for project backup
Close the WinCC Explorer again so that the project can be backed up or copied.
10
Copy/backup project with the project duplicator
Open the project duplicator (under "Start > SIMATIC > WinCC > Tools").
Fig. 07
Select the source project and use the menu command "Save as ...".
Enter the target path and target name of the project backup.
Click on "Save".
The project is duplicated without PI Options and can now be copied together with the *.PIB file to a target system to restore it there.
2. Restore the complete runnability of the source project
In section 2, the DTM is re-incorporated so that the project can be re-enabled.
This step is necessary for the project to be able to run again with DTM on the source computer.
No.
Procedure
1
Open the WinCC source project
Open the source project with the WinCC Explorer and stop the WinCC Runtime if started.
2
Enable PI Options
Right-click to open the pop-menu "PI_Option > Administrative Tools" and select the menu item "Options" (see Fig. 05 ( 16 KB ) ).
In "Options" you select "Enable PI Options" (see Fig. 06 ( 6 KB ) ).
Acknowledge with "OK".
3
Transfer the previous configuration
Stop and restart the WinCC Explorer to make the enabling of PI Options effective in the project.
4
Manually re-enter the user authorizations for the PI Options
In the User Administrator, reset the previously noted authorization levels for 600-605 for all users, which are now newly created.
5
Open the wizard for re-importing DTM/PCM data into the source project
In the Project Manager, select "Tools > New Project".
Fig. 08
Opening the "Create Project Wizard".
Click on "Next" in the "Create Project Wizard".
Select "Import an existing project" and then click on "Next".
Fig. 09
6
Re-import the exported PIB file into the source project Part 1
Select <Path and name of PIB file to be imported> and click on "Next".
Fig. 10
7
Re-import the exported PIB file into the source project Part 2
Under "What do you want to import?" you select "Configuration Database"
or "Configuration Database and Online Database Set"
or "Configuration Database, Online and Offline Database Set"
and click on "Next".
Fig. 11
8
Re-import the exported PIB file into the source project Part 3
Select <SQL Server Instance> and click on "Next".
Fig. 12
9
Re-import the exported PIB file into the source project Part 4
Select the <Location of the PI configuration database> and click on "Next".
Fig. 13
10
Re-import the exported PIB file into the source project Part 5
Select the <Location of the PI online database> and click on "Next".
Fig. 14
11
Re-import the exported PIB file into the source project Part 6
Configure the data of the PI Online database set and the database parameters and click on "Next".
Fig. 15
12
Re-import the exported PIB file into the source project Part 7
Define the project type and click on "Next".
Fig. 16
13
Re-import the exported PIB file into the source project Part 8
Define the location for the offline database set and click on "Next".
Fig. 17
Click on "Finish".
The PI data is imported and created.
14
Start the source project
Enable WinCC Runtime.
The PI Options are once again fully available for the source project.
3. Provide the complete runnability of the source project Section 3 is equivalent to Section 2 for the target project.
No.
Procedure
1
Open the WinCC target project
Open the target project with the WinCC Explorer and stop the WinCC Runtime if started.
2
Adapt target project to the new computer
Change the computer name in the project, close the project and then re-open it to make the changes effective.
3
Enable PI Options
Right-click to open the pop-menu "PI_Option > Administrative Tools" and select the menu item "Options" (see Fig. 05 ( 16 KB ) ).
In "Options" you select "Enable PI Options" (see Fig. 06 ( 6 KB ) ).
Acknowledge with "OK".
4
Transfer the previous configuration
Stop and restart the WinCC Explorer to make the enabling of PI Options effective in the project.
5
Manually re-enter the user authorizations for the PI Options
In the User Administrator, set the previously noted authorization levels for 600-605, which are now newly created.
6
Open the wizard for re-importing DTM/PCM data into the target project
In the Project Manager, select "Tools > New Project"
(see Fig. 08 ( 10 KB ) ).
The "Create Project Wizard" opens.
Click on "Next" in the "Create Project Wizard".
Select "Import an existing project" and then click on "Next"
(see Fig. 09 ( 9 KB ) ).
7
Re-import the exported PIB file into the target project Part 1
Select <Path and name of PIB file to be imported> and click on "Next"
(see Fig. 10 ( 8 KB ) ).
8
Re-import the exported PIB file into the target project Part 2
Under "What do you want to import?" you select "Configuration Database"
or "Configuration Database and Online Database Set" and click on "Next"
(see Fig. 11 ( 8 KB ) ).
9
Re-import the exported PIB file into the target project Part 3
Select <Server Instance> and click on "Next"
(see Fig. 12 ( 8 KB ) ).
10
Re-import the exported PIB file into the target project Part 4
Select the <Location of the PI configuration database> and click on "Next"
(see Fig. 13 ( 8 KB ) ).
11
Re-import the exported PIB file into the target project Part 5
Select the <Location of the PI online database> and click on "Next"
(see Fig. 14 ( 9 KB ) ).
12
Re-import the exported PIB file into the target project Part 6
Configure the data of the PI Online database set and the database parameters and click on "Next"
(see Fig. 15 ( 10 KB ) ).
13
Re-import the exported PIB file into the target project Part 7
Define the project type
WARNING! Clear the check mark from "Enable Recovery from Stop to Start"
(= disable this property) and click on "Next"
(see Fig. 16 ( 7 KB ) ).
14
Re-import the exported PIB file into the target project Part 8
Define the location for the offline database and click on "Next"
(see Fig. 17 ( 10 KB ) ).
Click on "Finish".
The PI data is imported and created.
15
Start the target project
Enable WinCC Runtime.
The PI Options are once again fully available for the target project and the project can be run.
What options does the WinCC Project Duplicator provide for creating a redundant server project?
Configuration Notes: The WinCC Project Duplicator provides an option for copying a WinCC project or duplicating it as a redundant server project.
Warning!
When using the PI options "Downtime Monitor" and "Process Monitor", refer to Entry ID: 29034551.
a) Copying a WinCC project using "Save as ..." Using the "Save as..." button of the WinCC Project Duplicator you copy only the configuration data of the WinCC source project "1:1" into a target directory. The Runtime data of the source project is not copied. If not already available, a new empty Runtime database is created in the copied project. If a Runtime database is already available in the target directory, e.g. because the WinCC project already exists on the redundant server, the existing Runtime database will not be replaced by an empty Runtime database. The WinCC source project must not be active in Runtime nor opened in the WinCC Explorer during the copying procedure. The following holds for the target directory:
You need "write access rights".
There must be sufficient memory available.
Note:
It is useful to delete all the "old" project data in the target directory before copying. This prevents project files from being open during the copying procedure. These could not be overwritten by the WinCC Project Duplicator.
In more recent versions of Windows "write access rights" is no longer the default setting on network drive releases. You must manually assign the release for "Write".
Fig. 01
If the "Save as" button of the WinCC Project Duplicator is to be used to generate a redundant server project, after copying you must make the following changes in the WinCC project of the redundant partner server.
No.
Procedure
1
Open the WinCC project in the WinCC Explorer You open the copied WinCC project in the WinCC Explorer.
Note: Since the local computer name and the name of the server in the WinCC computer list do not match immediately after copying, you get an error message: "The configured server is not available. Do you want to open project using the local computer as the server?". Acknowledge the dialog with the "Start server locally" button.
2
Change the computer name Change the computer name in the computer list. For this you use the "Computer Properties" menu.
Fig. 02
You must then close and reopen the WinCC project to make the change of computer name effective. For this you close the project with "File > Close" and open it again with "File > Recent File >".
3
Changing redundancy settings Make the changes with respect to redundancy. For this you open the "Redundancy" editor.
Fig. 03
You enter the name of the partner server in the "Redundant Partner Server" input field. (After copying the project the local computer name is usually given here).
Clear the "Standard Master" check box, because there must never be two "Standard Masters".
Quit the "Redundancy" dialog by clicking on the "OK" button.
4
Activate Runtime
Now you can activate WinCC Runtime on the redundant server computer.
b) Duplicating the WinCC project with "Duplicate" Using the "Duplicate" button of the WinCC Project Duplicator you can copy the configuration and Runtime data of the WinCC source project into a target directory. The copied WinCC project is automatically changed with regard to computer name and redundancy settings.
Depending on the state of the source project either only the configuration data is copied or the configuration and Runtime data.
Project closed The configuration and Runtime data is transferred.
Project open and deactivated Only the configuration data is transferred.
Project in Runtime Only the configuration data is transferred.
Project open and activated Only the configuration data is transferred.
The same requirements hold for the target directory as when copying the project using the "Save as ..." button.
More information:
More information is available in the WinCC Online Help under "WinCC Information System > Working with Projects > Duplicating and archiving projects" and "WinCC Information System > Configurations > Redundant Systems > Working with Redundancy > WinCC Redundancy Project Duplicator".
If your WinCC project is integrated in the SIMATIC Manager, you should use the "PLC > Download" function of the SIMATIC Manager instead of the Project Duplicator.
Why can no OS be inserted in the SIMATIC Manager when using STEP 7 V5.2 and WinCC V5.1?
Description:
When you want to operate WinCC V5.1 and STEP 7 V5.2 together on an PG/PC, the HF 0 to WinCC V5.1 is obligatory. It is - independent of perhaps already installed hotfixes for WinCC V5.1 - installable via Setup.
You can find the hotfix setup in the folder "WinCC-Hotfix"; in the STEP 7 V5.2 CD.
Open the project duplicator on the computer on which the project is located.
2
Select the multi-client project and click "Save As…".
3
Save the project on the multi-client desired in a path of your choice.
4
Remove the network cable of target computer after the copying procedure has been completed.
5
Set the local computer properties of the multi-client. (Adapt the computer name, possible change the startup list, with PCS 7 let the "Split Screen Wizard" and "Alarm Logging Wizard" run).
6
Reboot the computer and making sure to reconnect the network cable beforehand.
Note: Both multi-clients have to be in the same workgroup. They must not be separated by routers or gateways. In addition, their network addresses may only differ in the last digit block.
How can you use other mouse pointers than the ones set by default in WinCC V5.x Runtime?
Description: You can use any mouse pointer of your choice. For example, under "<Drive>:\WINNT.400\Cursors" is a selection of different mouse pointers.
Instructions:
No.
Procedure
1
Open the dialog box via "Start > Run".
2
Enter "regedit".
3
Go to the path: "HKEY_CURRENT_USER\Software\SIEMENS\WinCC\Graphic-Settings\Cursors"
4
Here you can specify the cursor you want to use instead of the default cursor. Enter the path and complete name of the cursor.
Fig. 01
Note: With "ActionCursor" you change the cursor for all objects - except text list and I/O field - on which a direct connection or an action has been configured under "Properties > Event > Mouse".
With "IOFieldActionCursor" you can change the cursor for the I/O fields for which you have configured an action under "Properties > Event > Mouse".
With "IOFieldEditCursor" you change the cursor for the I/O fields in which a value can be entered.
The codes "TextlistActionCursor" and "TextlistEditCursor" have the same significance as the I/O codes but are valid exclusively for text lists.
Important: In general, no warranty can be given for direct changes in the Registry because this is entirely the responsibility of the user. In any event, you are advised to make a backup of the registry before undertaking the actions described here. Furthermore, these settings are computer-specific. This means that when you copy the project to another computer, you must make the settings again there.
Note: Information regarding the dynamization of mouse pointers in WinCC V6.0 can be found in Entry ID: 15222441.
Keywords: Pointer dynamization
How can you dynamize your mouse pointers from SIMATIC WinCC?
Description:
From SIMATIC WinCC V6.0, as in the previous version, you can define your mouse pointers yourself for operator-controllable objects.
These settings are configured in the computer properties.
Open the "Computer properties" dialog by right-clicking the computer. The "Runtime" tab shows the setting options.
You can replace the default mouse pointer displayed in WinCC by your own and configure a new path for the mouse pointers chosen.
Fig. 1: Configuring mouse pointers
Note:
If you are using a previous version to WinCC V6.0, more information is available in Entry ID: 6711995.
How can you use user defined colors from an existing WinCC project in another or a new WinCC project?
When you create "user defined colors" in a WinCC project, in your <Project Folder\GraCS> the file "colors.dat" is generated.
To be able to use these "user defined colors" in another or new project as well, please copy the file "colors.dat" from the original WinCC project and insert it in the desired WinCC project in the folder GraCS.
QUESTION:
How can I modify the color of the RT-
cursor?
ANSWER:
You want to modify the color of the RT-cursor in SIMATIC WinCC as
the cursor is hardly visible on your display.
To activate the cursor open the properties of your PC inside the
WinCC-Project Tab "Graphics-Runtime" and set the check mark at
"Turn on during activation".
Fig. 1: Activation of the cursor
Modification of the color of the RT-cursor.
Click on "Start > Run" and enter "regedit"
Look for the key:
HKEY_CURRENT_USER\SOFTWARE\SIEMENS\WINCC\Graphic-Settings\Cursors
// here only the hyphen at "Graphic-Settings" has to be added
\\
Insert both new values ("right-click > new >
DWORD-Value"):
RTCColorUp ="10000"
RTCColorDown ="10000"
Both values highlight the object in which the cursor is located.
The value "RTCColorUp" saves the color value for the upper and
left side of the object. The value "RTCColorDown" saves the color
value for the lower and right side of the object.
The values used for the standardized colors
in WinCC can be found in the manual for Global Scripts or in the
WinCC-Help under the section 'Value definitions of
attributes'.
Important: Basically, no liability can be assumed for
direct modifications in the registry as this is entirely up
to the user's responsibility. It is highly recommendable to create
a back up of the registry before processing the steps described
above. Moreover, those settings are PC-specific meaning that
they have to be applied again when copying the project to another
PC.
Which criteria apply to the name of a WinCC project?
Instructions: This entry provides tips on the allocation of the WinCC project name:
General information The WinCC information system contains information on the allocation of the project name and on general naming conventions under "Working with WinCC > Working with Projects > Preparation to Create a Project".
Permitted characters The WinCC information system contains information about the characters permitted in the project name under "Working with WinCC > Working with Projects > Appendix > Illegal Characters".
Restrictions in the project name The string "WinCC" or "wincc" should not be used as a WinCC project name.
If the string "WinCC" is used as a project name, errors may occur when a client (without its own project) attempts to access the server project. There is information available on this in Entry ID 24201405.
If the string "wincc" is used as a project name, none of the existing tag logging archives are shown for selection when using SIMATIC BATCH in the "Configure Batch Process Cell > Assign WinCC Tag" dialog. This information is taken from the "readme" for SIMATIC BATCH V7.0.
Subsequent changes to the WinCC project name using the WinCC project duplicator
Before you create the WinCC project, you should give some thought to the name of the project. If you wish to change the name of the WinCC project later on (after creating the project), you can use the WinCC project duplicator to do this. You may not change the name of the project by manually renaming the file structure of the project.
