C135 PCS 7 (PCS7)
6C
6 Cielo Ciencia y Tecnología
·Publicada en C135 PCS 7 (PCS7)

How to Properly Create, Configure, and Download a New WinCC OS Client in SIMATIC PCS 7

How to Properly Create, Configure, and Download a New WinCC OS Client in SIMATIC PCS 7

To successfully create and deploy a new WinCC OS Client in a SIMATIC PCS 7 Multiproject—avoiding file copy failures and computer name mismatch errors—engineers must follow a structured 9-step configuration workflow. The process requires inserting a new SIMATIC PC Station in SIMATIC Manager, assigning the exact physical Windows computer name, adding a 'WinCC Client' application in HW Config, compiling NetPro, generating and assigning updated Server Data packages (.pck), defining the target UNC network path, and setting Windows user groups (SIMATIC HMI) and folder share permissions with Full Control before executing the target download.

Table of Contents

Architectural Role of the OS Client in SIMATIC PCS 7

In SIMATIC PCS 7 distributed control systems, Operator Station Clients (OS Clients) act as operator visualization terminals that connect to one or more WinCC OS Servers:
* No Direct AS Communication: OS Clients do not communicate directly with automation stations (PLCs); all tag, alarm, and recipe data is requested from the central OS Servers across the Terminal Bus.
* Server Data Packages (.pck): The OS Client's project contains no internal process tags; it imports compiled server data packages representing the data namespace of each connected OS Server pair.
* Compact Footprint: Because process data and archives reside on servers, an OS Client project is lightweight (typically 200–400 MB), containing only local screen navigation files, user profiles, and project configuration headers.

Common Engineering Traps: Name Mismatches and File Copy Aborts

When commissioning a new OS Client, engineers frequently encounter two failure modes during download:

1. 'Error in changing the computer name in the client station'

  • Occurs when the Engineering Station successfully copies files across the network share, but fails to mount the target database via remote SQL/DCOM calls to update the internal project computer name.
  • Root Cause: The Windows user account lacks administrative privileges, the logged-in user does not belong to the local SIMATIC HMI group on the client, or CCCleaner.exe was not run to release locked background processes.

2. 'The files could not be copied or could only be copied partially'

  • Occurs during the initial file transfer phase.
  • Root Cause: The target destination folder on the client is not shared with Full Control permissions, Windows Defender Firewall blocks SMB port 445, or simple file sharing is enabled.

The 9-Step Standard Engineering Workflow for OS Clients

Follow this comprehensive procedure to add an OS Client to a PCS 7 Multiproject:

Step 1: Insert New SIMATIC PC Station

In SIMATIC Manager, right-click the Multiproject -> Insert New Object -> SIMATIC PC Station.

Step 2: Set Exact Computer Name

Right-click the PC Station -> Object Properties. In the Name and Computer name fields, enter the exact physical Windows computer name of the target client workstation (case-insensitive, max 15 alphanumeric characters).

Step 3: Configure Hardware in HW Config

  1. Open HW Config for the PC Station.
  2. From the catalog, insert a WinCC Client application into the virtual PC rack (Slot 1).
  3. Insert an IE General network interface card (Slot 2) and configure its Terminal Bus IP address.
  4. Save and compile HW Config.

Step 4: Compile NetPro Connections

Open NetPro, execute Network -> Save and Compile, and close NetPro.

Step 5: Prepare Target Client File System

  1. On the physical OS Client workstation, create a dedicated project directory:
    D:\WinCC_Projects
  2. Right-click the folder -> Properties -> Sharing -> Advanced Sharing:
    * Share the folder as WinCC_Projects.
    * Permissions: Grant Full Control to Everyone and the local SIMATIC HMI group.
  3. Security tab (NTFS): Grant Full Control to SIMATIC HMI, Administrators, and SYSTEM.

Configuring Server Data Assignment and Target Paths

Step 6: Generate Server Data on OS Servers

In SIMATIC Manager, right-click each Master OS Server -> Server Data -> Generate.

Step 7: Assign Server Data to the OS Client

  1. In SIMATIC Manager, expand the OS Client object and open the WinCC project.
  2. In the WinCC Explorer navigation tree, right-click Server Data -> Implicit Update (or select Assign).
  3. Select the generated server packages (.pck) for all plant OS Server pairs and click OK.
  4. Configure the OS Project Editor to apply standard screen layouts and horn settings. Close WinCC.

Step 8: Set Target Download Path in SIMATIC Manager

  1. In SIMATIC Manager, right-click the OS Client -> Object Properties -> Target OS and Standby OS.
  2. Set the Target OS path to the network UNC share:
    \<OS_Client_Computer_Name>\WinCC_Projects\<Client_Project_Name>.mcp

Step 9: Execute Target Download

  1. Right-click the OS Client -> PLC -> Download.
  2. Select Entire OS.
  3. SIMATIC Manager transfers project files, initializes the local database, updates the target computer name, and completes with 100% success.

OS Client Commissioning and Troubleshooting Reference Matrix

The following table outlines common OS Client download failures and verified resolutions:

Error Message / SymptomUnderlying DefectDiagnostic CheckpointCorrective Action'Error changing computer name'SQL/DCOM permission deniedWinCC_Sys_01.log on clientRun CCCleaner.exe; add user to SIMATIC HMI'Files could not be copied'Share rights or firewall blockingWindows Explorer \Client\ShareShare folder with Full Control to SIMATIC HMI'Server data package missing'Server packages ungeneratedWinCC Server Data editorRight-click OS Server -> Generate Server DataClient opens blank white screensIncomplete OS Project Editor runGraphics Designer GraCSRun OS Project Editor with standard layoutTags show yellow exclamation marksSimatic Shell unconfiguredSimatic Shell propertiesSelect Terminal Bus adapter in Simatic Shell

Disciplined execution of this 9-step workflow ensures rapid, error-free client deployment.

Verification

To verify that the new OS Client is operational:
1. Verify that the SIMATIC Manager download dialog completes with: 'Download completed successfully'.
2. On the OS Client workstation, launch WinCC Explorer; verify that the project title bar displays the local computer name.
3. Activate WinCC Runtime.
4. Verify that process pictures from all assigned OS Servers are accessible via the area navigation buttons.
5. Confirm that real-time process values update dynamically and that incoming alarms populate the alarm banner.

Limitations and Operational Precautions

  • Never copy-paste an existing OS Client station inside SIMATIC Manager without immediately updating its computer name and clearing legacy server package references.
  • OS Client computer names must not exceed 15 characters, must not start with a number, and must not contain underscores or special characters.
  • Ensure all participating workstations have identical Windows user credentials and time synchronization.
  • Always validate final license quantities, WinCC RT Client licenses, and MLFBs against the applicable Siemens catalog and authorized distributor quotation.

Engineer FAQ

Do OS Clients require an AS RT Process Object (PO) license?

No. Process Objects are hosted and licensed exclusively on the OS Servers. OS Clients only require a WinCC RT Client software license (e.g., 6AV6381-2BD07-4AX0).

Can I create a Referenced Client instead of a Standard Client?

Yes. A Referenced Client points directly to a master client's shared network project file, eliminating the need to download project files to individual client machines.

Why does CCCleaner need to be executed on the client before download?

If WinCC was previously opened on the client, residual processes (CCProjectMgr.exe, CCClientRT.exe) retain file locks on database templates; CCCleaner safely terminates them.

Technical References

Related Articles

Related Tags

  • OS Client Configuration
  • WinCC Client Download
  • Server Data Packages
  • SIMATIC HMI Group
  • Target OS Path
6 respuestas