Set Up a PCS 7 Multi-Station Simulation with SIMIT Virtual Controllers

Use a networked SIMIT Virtual Controller setup with the test OS server and clients, rather than relying on local OS simulation to represent a multi-station system. Siemens documents VC creation, station import and complete downloads in SIMIT V10.2. However, that manual explicitly limits this coupling to STEP 7 V5.5 or earlier. Establish the exact installed component compatibility before applying the procedure to a newer PCS 7 system; the unspecified installation cannot be declared supported from the baseline alone.

Use a Networked Simulation Architecture

A multi-station test needs the controller simulation, process model and actual OS server/client relationships. SIMIT V10.2 documents an architecture with a SIMIT PC, optional separate VC hosts and PCS 7 engineering, server and client stations. A VC host must be reachable from both the SIMIT PC and the OS server.

This differs from SIMATIC Manager's local Start OS Simulation feature. The PCS 7 V9.0 SP1 OS manual states that local OS simulation does not communicate between the project's operator stations. Starting several local simulations is therefore not a documented replacement for a connected multi-station test. SIMIT manual, p. 119; OS manual, chapter 20.1

Resolve Version Applicability First

Record the installed PCS 7, STEP 7, CFC, SIMIT and VC releases separately. The opened SIMIT V10.2 manual explicitly limits this VC coupling to STEP 7 V5.5 or earlier. Do not silently extend its import procedure to a later STEP 7 release because the product still uses the PCS 7 name.

The requested installation's versions were not supplied. Consequently, the procedure below is a documented V10.2 baseline, not a confirmed end-to-end setup for the unknown system. A newer applicable compatibility statement and its import workflow are needed where the stated limit is exceeded.

Prepare the Isolated Test Network

As a project-specific preparation, preserve the engineering project and define the AS, OS server and clients included in the test. Map the plant-bus, terminal-bus and simulation-network addresses before enabling any VC.

Siemens documents that imported VCs retain configured controller addresses and connections. Prevent conflicts with real controllers by isolating the test network and coordinating address changes. Check unique addresses and avoid overlapping subnet arrangements. Do not connect the imported simulation to a live plant merely to see whether an OS client finds it.

Documented V10.2 VC Creation and Import

After the compatibility and isolation checks:

Open the SIMIT project.
In the project tree, use the Couplings shortcut menu and choose New coupling.
Select Virtual controller.
In the import dialog, select the STEP 7/PCS 7 project or the supported HWCNExport file, select symbol-import mode and choose the required stations.
Select Import. A VC is created for each selected station and initially assigned to My Computer in the distribution editor.
Configure the host's network settings for the imported VC addresses, following the approved test-network plan. If using another host, distribute the VCs and adapt that host's addressing.
Create and connect the process model needed for the test, then start simulation.

The manual requires a complete station download to the running VC after creation and again after controller-configuration changes. Target the simulated controller explicitly. Importing a station does not itself establish a running, fully downloaded AS application. SIMIT manual, pp. 134–138

Verify the Server and Client Paths Separately

First confirm that the VC runs and that controlled model signals reach the intended AS logic. Then verify communication from the actual test OS server to that simulated AS using the engineered connection configuration.

Finally, open the relevant pictures on each test client and check changing values, alarm presentation and approved operator-command feedback. Separate failures at the model-to-VC, VC-to-server and server-to-client boundaries; a VC RUN indication does not prove all three paths.

Server redundancy, client failover and application-specific integrations require their own acceptance scenarios. No particular topology or failover result was supplied for the requested system.

Verification

Retain a test record showing the exact versions, isolated address plan, imported stations and download targets. Demonstrate at least one controlled input change through the model, AS logic, server and each intended client, and one approved command/feedback path.

Compare actual observations with the intended test scope. Do not describe the setup as a successful multi-station simulation until the server/client paths have been observed; controller simulation alone is a narrower result.

Limitations and Operational Precautions

The historical manual A5E32889040-AB was identified in the question, but its contents were not independently opened and are not relied on here. The verified baseline is the newer V10.2 manual, with its explicit STEP 7 limit.

Use existing licensed and compatible components; a missing VC license can leave simulation stopped. Preserve the simulation project before configuration changes, and reassess snapshots after model or program changes. No live-plant connectivity, performance estimate or lab-tested result is claimed.

Engineer FAQ

Can local OS simulation prove a multi-client system works?
No. The cited OS manual excludes communication between the project's operator stations in that mode.

Can the V10.2 import instructions be assumed valid for a later STEP 7 installation?
No. The manual states a V5.5 limit for the coupling; establish applicable compatibility evidence first.

Technical References

Siemens — SIMIT Simulation Platform V10.2 Operating Manual, March 2020, A5E44876249-AB — network architecture and compatibility, pp. 119–120; VC creation/import and station-download requirement, pp. 134–138.
Siemens — PCS 7 Operator Station V9.0 SP1, chapter 20.1 — local OS-simulation communication limitation.

PCS 7 multi-station simulation

Set Up a PCS 7 Multi-Station Simulation with SIMIT Virtual Controllers