show the entry list
ES - SIMATIC Manager -- Working with projects -- Compiling OS and loading OS
What should you watch out for when downloading from the WinCC/PCS 7 Engineering Station to the Operator Station (ES-OS download)?
Why aren't all the block icons updated during OS compilation?
Which settings should you check if OS loading fails with PCS 7 or the OS project cannot be activated?
Problems when mapping data blocks with the same name
How can you clear the following error message during OS compilation: "The number of parameters for the structured DM variables xxx of type yyy does not match the number of operator-controlled connections...".
What is the meaning of the error message "A structure conflict occurred when creating the structured DM variable XXXX of type YYYY..." when compiling the OS?
How do you set the TCP/IP protocol for PLC-OS data transfer?
What is the meaning of the warning in the log file "*** Warning(s) ***: The structure type XXXX has been changed since the last compilation. All associated structured tags (even other S7 programs) will be deleted on the OS." ?
How do you use the template pictures "@PCS7Typicals*.pdl" to create block icons?
What does the compile OS error message "302:3018 - There are process variables whose names are not unique within the project after replacing special characters..." mean?
Which messages may appear in the "Download OS" dialog box?
Why appears the error message "The number of external DM variables in WinCC exceeds the permitted in total number", although the necessary license is available?
With PCS 7, why can't you open the OS project on the OS after it is downloaded from the ES?
Which special characters/separators may not be used in PCS7 V4, V5, and how are they replaced during AS/OS transfer?
What are the requirements for performing an online delta loading of the OS?
Why does the automatic package update of the clients sometimes not work in case of a changes-only download?
What do you do if a text which is configured in the CFC appears different in runtime?
How is a text, which has been configured in the CFC, transferred into the OS during OS compilation, and what do you have to watch out for in particular during configuration?
Which work steps are necessary for a project update of a redundant server couple and the MultiClients in SIMATIC PCS 7 V5.x?
Which work steps are necessary for the update of the OS Runtime data for the migration from PCS 7 V5.x to SIMATIC PCS 7 V6.x?
What do you do in PCS 7 V7.0 if the OS compile process is interrupted because the WinCC project cannot be opened?
Why can WinCC tags have the status "write-protected" and thus cannot be edited, deleted or moved?
What has to be watched out for during the compilation of a modification into the OS-Station after the interface modification of a Function block?
Why can't you transfer the elements of an S7 structure or UDT to WinCC through OS compilation?
Why doesn't OS delta load from the SIMATIC PCS 7 ES work despite Runtime being active on the OS station?
Why do you get a warning to the effect that your OS project is running in demo mode when testing it on your ES?
How can you clear the error message "Download (310:88)"?
How can you correct the error message "OS is currently being loaded from another ES"?
How is server data (server package) generated and loaded?
After reloading the OS project to the server from the ES, how do you clear the undefined error message and the abort?
When compiling the OS project, how can you clear the internal error 15500 in the transfer.log file?
Why does the error message "FileCopyError ....WinCC6.0_Project\GraCS\Default.pdd" occur when making a delta load and what is the "Default.pdd" file for?
Why are texts no longer updated with PCS 7 V6.0 SP3 + SP3 Postfixes after an OS delta compilation and OS delta load?
How do you clear the error message "*** Error(s) ***: Error while requesting messages from the STEP 7 message server...."?
How do you clear the error message "Internal error: transfer of process variables has been aborted. Error number: 15424" when compiling the OS project?
How can you clear the error message "No DM variable can be created for a symbol without a name" during OS compilation?
Why can't you load a project via a network?
What does the compile OS error message "302:3018 - There are process variables whose names are not unique within the project after replacing special characters..." mean?
Part number:

Configuration notes:
The following error message can appear during OS compilation:

"Compile OS (302:3018) - There are process variables whose names are not unique within the project after replacing special characters..."


Fig. 01
 

In the "TRANSFER.log" file on the compilation process, the error text is followed by the names of the process variables which are used more than once.


Fig. 02
 

Note:
If the Make dialog ("Compile and Download Objects") is used to compile/download multiple stations, the compilation process is interrupted with a general error message. However, the separate window with the error message (Fig. 01) doesn't appear. In this case, you will only find the actual error message in the "TRANSFER.log" file for the compilation process (see Fig. 02).

Cause:
During OS compilation, the process objects from the AS programs (SIMATIC Manager) are transferred into the specified OS projects (WinCC project). The names of the process objects must be unique within an AS and within an OS. Two reasons why the names of the process objects lose their uniqueness within the OS are described below.

  • Process objects from a number of AS programs can be transferred (compiled) into the same OS. If multiple AS programs with process objects of the same name are compiled into the same OS, this error message occurs because the process objects no longer have unique names within the OS. On the other hand, identically named process objects from multiple AS programs can be transferred to different OSs.
  • During OS compilation, certain special characters in the name of the configured process objects are replaced by other characters. Situations can arise where different special characters are replaced by the same character. If process objects from one or more AS program(s) are transferred into the same OS and are only distinguished from one another by certain special characters, the special characters which are different in the AS may be replaced by identical characters in the OS. As a result, the name ceases to be unique in the OS. You can obtain information about separators and special characters
    • in the PCS 7 Online Help under "Configuration - Engineering System > Implementing the PCS 7 Configuration > Hierarchy (PH) > Rules for Naming in the PH"
    • in Entry ID 7000709 - Which special characters/separators may not be used in PCS7 V4, V5, and how are they replaced during AS/OS transfer?

The figure below illustrates these two causes of this error taking a plant hierarchy (PH) configuration as an example.


Fig. 03
 

Notes:

  • In this example, only the chart name is used as part of the higher level designation (HID). The name of a block within a chart always forms part of the HID.
  • Charts with the same names cannot be created in the SIMATIC Manager's plant hierarchy if they are assigned to the same AS, even if they have different HIDs (different hierarchy folders).

 Entry ID:26460337   Date:2007-09-21 
I regard this article....as helpfulas not helpful                                 
mySupport
My Documentation Manager 
Newsletter 
CAx-Download-Manager 
Support Request
To this entry
Print
Create PDF 
Send to a friend
QuickLinks
Compatibility tool 
Topics
Help
Online Help
Guided Tour