Virtualizing a DCS in PCS7

Virtualizing a DCS in PCS7

Before applying changes to your PCS7 control system, it’s always good practice to simulate on a virtual processor.

While PLCSIM makes the process of simulating changes to the DCS nearly effortless, it’s a bit more complicated to simulate your entire DCS on a VM. This blog will guide you through configuring virtual AS/OS communication in your PCS7 Multiproject.

Getting Started

The first step to getting your virtual DCS configured is to configure your VM’s NICs. If you're not working in a VM, you can follow along on your host machine.

  1. Open your Windows OS’s Network Adapters panel.
  2. Assign static IP addresses to one of your VM’s NICs. 
    1.  Hit the ‘Advanced’ button to assign more than one IP to the NIC.
  3. I threw the range, .4, and .5 at the adapter to mimic the assignments on my multiproject’s physical AS, as well as the changes we’re about to make.

Network Connections Settings Menu

Editing the Multiproject

Next, we’ll make some changes to your Multiproject. Open up a copy of your multiproject in Simatic Manager – you probably don’t want to do this directly on your ES because the hardware and network configurations will change.

  1.  In HW Config, add a new communications processor to the PLC rack you’re going to simulate. This will be the path that the simulated OS will use to browse to the AS.
    1.  Make it easy on yourself and search for the CP card by catalog number. I added the 6GK7 443-1EX30-0XE1, version 3.0.
    2. Drag the CP card to an open slot on your DCS chassis.
  2. Next, assign the CP card to an existing subnet and give it an IP address from the range you created above.
    1. Right click on the PN-IO module under the CP 443-1 and open the Object Properties.
    2. Open the Interface Properties and assign it an IP address and subnet mask. My PN-IO X5 and X5-1 adapters are assigned to and .4 respectively, so this CP card will take the last IP we added (
    3. Make sure to click on the project-wide subnet you want to assign the card to – for me, this was called SYSTEMBUS. Confirm your settings with OK.

Computer properties windows

WinCC Explorer

Next, we’ll make some changes to the OS application in WinCC Explorer.

  1.  In the Project Properties, tick the box to ‘Allow activation on ES’ (right click on the project in the tree > properties > Options).
  2.  In the Computer properties (left click on ‘Computer’ in the tree, right click on the computer listed > Properties), take the following steps:
    1. Replace the given name with your Local Computer Name (on General tab).
    2. On the Startup tab, disable Alarm Logging and Tag Logging.
    3. Confirm with OK.
  3. Optionally, add user credentials.
  4. Delete the server data (right click on Server Data > Delete).

Head back to Simatic Manager and find the WinCC application in your OS project. Double click on the Connections item to open the NetPro project file.

  1. Right click on the CP card in your project’s OS server and select Properties.
    1. On the Options tab, throw in an NDIS IP address – this is just a placeholder so that it doesn’t get flagged as an error later. I used a dummy address of
    2. Confirm it with OK.
  2. Next, select the WinCC Application.
    1. Delete the existing connection.
    2. Create a new TCP connection by right clicking in an empty field > Insert New Connection.
    3. Expand the ‘In the multiproject’ item, and browse to your AS.
    4. Select ‘TCP connection’ as your Type, and ensure the tick box to Display Properties is ticked. Hit Apply to confirm.
    5. Untick the ‘Active connection establishment’ option and confirm with OK.

Simulating the Multiproject

We’re done configuring your multiproject – now it’s time to simulate!

  1. Open PLCSIM, and compile and download to the simulated processor.
    1. After downloading, verify that you can open a chart in Test mode. If you can’t, perform a full download from within CFC editor and you should be able to go online.
  2. Perform a full compile on your OS.
  3. Open WinCC Explorer and activate your runtime. It might take a minute or more, but, you should find that, after it activates, you can move data between the simulated AS and your new simulated OS.
  4. After virtualizing your AS and OS, you can simulate changes to your DCS in a development environment prior to deploying them to your production equipment.

Learn more about DMC's Siemens S7 PLC Programming expertise and contact us today for your next project!


There are currently no comments, be the first to post one.

Post a comment

Name (required)

Email (required)

Enter the code shown above: