Connecting Siemens NX MCD to S7-1200 OPC UA, PLCSIM, SIMIT HIL

Overview: Why Couple NX MCD with a SIMATIC S7-1200

Siemens NX Mechatronics Concept Designer (MCD) is a digital-twin environment inside the NX CAD/CAE platform that lets engineers design, simulate, and validate mechanical behavior, kinematics, sensors, and actuators before any physical hardware exists. Coupling NX MCD to a real SIMATIC S7-1200 controller closes the loop with the actual PLC logic, turning a kinematic model into a true Hardware-in-the-Loop (HIL) commissioning platform.

The S7-1200 family (including the new SIMATIC S7-1200 G2 generation) exposes the control logic in TIA Portal, while NX MCD consumes or produces the I/O signals that drive the virtual machine. Three integration paths are field-proven and documented by Siemens:

• Native OPC UA using the S7-1200's built-in OPC UA server (firmware V14 SP1 and later) and NX MCD's built-in OPC UA client.
• OPC DA using PLCSIM Advanced and a third-party OPC bridge (KEPServerEX or MatrikonOPC) when only a simulation instance of the PLC is available.
• SIMIT + NX MCD co-simulation, the official Siemens virtual-commissioning framework documented in the SIMIT/NX MCD guideline.

The choice depends on whether you have real PLC hardware, the firmware version, license availability for PLCSIM Advanced, and whether the project requires a 21-day trial-only PLCSIM instance or a permanent development environment.

Prerequisites

Communication Architecture Options

When to choose which path

• Use OPC UA Direct when the S7-1200 is real, firmware is V14 SP1+, and you want a clean IP-based connection with no third-party software. NX MCD can subscribe to tags and read/write them in real time.
• Use OPC DA via PLCSIM Advanced when you have no real PLC and a licensed (or trial) PLCSIM Advanced instance is available. This is the path Siemens Community contributors confirm for S7-1500 and is fully applicable to the S7-1200.
• Use SIMIT for production-grade virtual commissioning where you need a SIMIT Unit to expose the S7-1200 to a virtual plant; SIMIT also provides libraries for NX MCD co-simulation as documented in the official Siemens guideline.

Method 1: Direct OPC UA Connection (Recommended)

The S7-1200 OPC UA server has been available since firmware V4.2 (TIA Portal V14 SP1). The S7-1200 G2 extends this with discovery and security profiles described on the SIMATIC S7-1200 G2 product page.

Step-by-step: Enable OPC UA on the S7-1200

1. Open the TIA Portal project containing the S7-1200.
2. Right-click the CPU in the project tree and select Properties > OPC UA > Server.
3. Check Activate OPC UA Server.
4. Set the server port to 4840 (default) or any free TCP port above 1024.
5. Under Security policies, choose at least None for lab use, or Basic128Rsa15 / Basic256Sha256 for production. The S7-1200 G2 supports up to Aes128Sha256RsaOaep.
6. Under User authentication, enable Enable guest authentication only for development; create individual users for production.
7. Compile and download the configuration to the PLC.
8. Verify the server is reachable: from a Windows PowerShell on the same subnet run Test-NetConnection -ComputerName <PLC_IP> -Port 4840. The result should be TcpTestSucceeded : True.

Step-by-step: Connect NX MCD as OPC UA Client

1. In NX MCD, open the Signals node of the mechatronics model.
2. Right-click External Signals and choose New OPC UA Connection.
3. Enter the discovery URL: opc.tcp://<PLC_IP>:4840.
4. Browse the server namespace and select the PLC tags to expose to the kinematic model. Each tag is mapped to a Signal in MCD's signal table.
5. Map signals to NX MCD objects: for example, a boolean "Conveyor_Run" PLC tag drives a MCD Signal Adapter connected to a Rigid Body's velocity source; a real "Axis_Position" (REAL, MD) is published back to the PLC from a MCD Sensor or runtime value.
6. Set the Publishing Interval in NX MCD's connection settings to 50–100 ms for motion control loops; 200 ms is acceptable for visualization-only coupling.
7. Start the simulation. NX MCD reads/writes signals over OPC UA; the S7-1200 logic reacts in real time on its cycle (typically 1–10 ms OB1).

Method 2: PLCSIM Advanced + OPC DA Bridge

This path is widely documented for the S7-1500 and works identically for the S7-1200 once the program is loaded into a PLCSIM Advanced instance. KEPServerEX acts as the OPC DA server that NX MCD subscribes to.

Step-by-step

1. Install PLCSIM Advanced (V3.0+). Launch the management console and start a new instance. Note the instance's IP (e.g., 192.168.1.10) and the S7 communication port 102.
2. From TIA Portal, perform an Online > Extended Download to Target Device; choose PLCSIM Advanced as the target interface.
3. Install KEPServerEX (or MatrikonOPC). Add a channel of type Siemens TCP/IP Ethernet.
4. Add a device, set the IP to the PLCSIM Advanced instance address, and set the rack/slot to 0/1 for S7-1200.
5. Auto-discover tags or manually add them; ensure the OPC DA server is running on the default port 49320.
6. In NX MCD, create an OPC DA Connection, point it to localhost (or the KEPServerEX host), and browse the tags.
7. Run the simulation: TIA Portal's PLCSIM Advanced should be in RUN mode, NX MCD's OPC client should show green "Connected" status, and signal values should change in both directions.

Method 3: SIMIT-Based Virtual Commissioning (Siemens Reference)

Siemens publishes a detailed reference architecture for coupling NX MCD, SIMIT, and a SIMATIC controller. The PDF "Guideline – Virtual Commissioning with SIMIT, NX MCD and S7" (entry ID 109963864 in the Siemens Industry Online Support) describes the full flow:

1. Model the mechatronic system in NX MCD, exposing inputs (e.g., sensors, switches) and outputs (e.g., motor torque, conveyor speed) as MCD signals.
2. In SIMIT, build a virtual plant using SIMIT libraries. SIMIT reads MCD signals over the NX MCD coupling (Shared Memory SHM on a local machine, or TCP via the NX MCD external connection).
3. Add a SIMIT Unit for S7-1200/1500 that exposes the PLC program to the virtual plant via PLCSIM Advanced or a real S7 controller.
4. Download the TIA Portal project to the SIMIT Unit. SIMIT then exchanges I/O with NX MCD, and the controller logic — running in PLCSIM Advanced or on a real S7-1200 — reacts as if it were wired to real sensors and actuators.
5. Use SIMIT's Control Desk for operator override (start/stop, fault injection) without breaking the HIL link.

This is the architecture most academic and industrial virtual-commissioning teams adopt. Reference implementations appear in the IEEE paper "PLC Inverse Kinematics Model-Driven Digital Twin Focused on HIL" (2024), which implements the inverse kinematics in an S7-1200 controlled by TIA Portal and validated through NX MCD.

NX MCD Signal Mapping and Tag Configuration

Tags in the S7-1200 are referenced by data-block and offset. NX MCD does not natively understand S7 symbolic addressing, so the OPC server must expose each tag by its fully qualified name. Typical tag-naming convention in TIA Portal:

DB_Conveyor".Conveyor_Run" : BOOL
DB_Axis".Axis_ActualPosition" : REAL
DB_Axis".Axis_SetpointVelocity" : REAL
DB_Safety".E_Stop_OK" : BOOL

Recommended signal categories in NX MCD:

For motion control, expose the S7-1200's TO (Technology Object) axis data blocks (e.g., DB_Axis_1) so that the axis actual position and actual velocity are visible to NX MCD in real time. Use the MC_Servo and MC_Power blocks; the actual position in the TO data block is updated every position-control cycle (typically 1 ms on the S7-1200, 250 µs on the S7-1200 G2 with the new fast PTO).

KTP700 HMI Integration Considerations

The KTP700 Basic Panel is fully supported on the S7-1200 with TIA Portal V15.1+. When the PLC is being driven by NX MCD, the HMI displays real values because the HMI reads from the same data blocks the OPC UA / OPC DA server is exposing. There is no conflict between HMI polling and NX MCD polling — both are read-only consumers.

• HMI connection: PROFINET to the S7-1200 CPU. Standard update cycle on the KTP700: 100 ms (set in the HMI connection properties).
• Avoid putting NX MCD and the HMI on the same PROFINET interface if you want to isolate the HIL traffic; use a second Ethernet port on the engineering PC.
• For operator override from the HMI (e.g., jog buttons), those write to the same tags that NX MCD reads, so the MCD virtual machine reacts. Be careful: a jog command and a MCD-driven setpoint on the same axis will fight unless prioritized in the PLC logic.

Verification and Commissioning Procedure

1. OPC UA reachability: Test-NetConnection -ComputerName <PLC_IP> -Port 4840 returns True.
2. Tag visibility: Use Siemens' free OPC Scout V10 (in TIA Portal installation media, Siemens\Automation\OPC\OPC_ScoutV10) to browse the S7-1200 server and confirm each tag is listed with the correct data type.
3. NX MCD connection status: In the Signals panel, the OPC UA connection shows a green check and a non-zero publishing rate.
4. Round-trip latency: Toggle a digital output from the PLC, observe the corresponding NX MCD signal; latency on a Gigabit LAN should be < 20 ms. If higher, increase the OPC UA publishing interval or check the PC's CPU load.
5. Motion test: Command the S7-1200 to move an axis using MC_MoveAbsolute and verify in NX MCD that the rigid body position tracks the actual position tag from the TO data block.
6. Fault injection: In SIMIT Control Desk, force a sensor to FALSE and confirm the PLC's safety logic trips as expected.

Troubleshooting Matrix

Field-Commissioning Notes and Best Practices

• S7-1200 vs S7-1200 G2: the G2 doubles the OPC UA throughput and adds discovery, but the configuration flow in TIA Portal V20 is identical. Use the G2 for any new HIL project that needs 250 µs position control.
• License choice: For an evaluation period of 21 days, use OPC UA direct (free) with a real CPU you already own. If you have only simulation, use the PLCSIM Advanced trial and KEPServerEX. After the trial, move to a licensed PLCSIM Advanced, or invest in SIMIT for permanent use.
• Cycle-time budget: The S7-1200 OB1 typically runs 1–10 ms. Do not push more than 100 signals at the 1 ms OPC UA publishing interval; 50 ms is the safe default for plant-scale models.
• Safety: Never connect a live safety circuit to NX MCD signals. Use SIMIT or a hard-wired E-stop that bypasses the HIL loop for real plant commissioning.
• Versioning: Pin the TIA Portal project, NX MCD model, and SIMIT library versions in a single engineering change document. OPC UA namespace is stable across firmware updates, but tag names change when DBs are refactored.