Signal Mapping and OPC UA / PLCSIM Advanced Integration Notes

Practical detail on how NX MCD actually exchanges signals with a PLC, gathered from an open-access engineering case study and community forum threads — supplementing the official Siemens "External Signal Configuration" documentation with real integration notes.

Why OPC UA is in the loop at all

A 2024 open-access case study ("Design of a material sorting digital twin system based on NX MCD," Manufacturing Review) states plainly: the model created in NX MCD cannot exchange data directly with a physical or virtual PLC over Ethernet — the PLC and MCD model must communicate through an OPC UA server. This is a useful mental model for newcomers who expect a native/direct link: OPC UA is not merely one connection option among several, it is the mandatory bridge for anything other than the PLCSIM Advanced direct-connection path introduced in NX 12.

Source: https://mfr.edp-open.org/articles/mfreview/full_html/2024/01/mfreview240009/mfreview240009.html

Naming-based auto-matching

The same case study describes the practical signal-mapping workflow: "the signal mapping phase adopts an intelligent matching mechanism, and the system automatically establishes two-way associations when the MCD model parameters and PLC variable names have naming consistency." In other words — if you name your MCD signals identically to your PLC tag names, NX MCD's signal mapping tool will auto-suggest/auto-bind the pairs, saving significant manual mapping effort on projects with dozens of signals. This is a strong argument for establishing a shared naming convention between the mechanical/MCD modeler and the PLC programmer before virtual commissioning starts, rather than reconciling divergent names after the fact.

Direct PLCSIM Advanced connection (NX 12+) removes the Signal Server

Community forum discussion (Siemens PLM/DISW community, thread "NX MCD," td-p/433191) notes that starting with NX 12.0, MCD gained a direct connection type to S7-PLCSIM Advanced that does not require a separate Signal Server at all. Prior to NX 12, the typical topology required a standalone Signal Server component to broker between MCD and the simulated/real PLC; the direct-connect path collapses that into a simpler configuration. For anyone following older tutorials or blog posts that reference "Signal Server" setup steps, this is the version cutoff to be aware of — content predating NX 12 assumes a topology that later versions no longer require.

Source: https://community.plm.automation.siemens.com/t5/NX-Design-Forum/NX-MCD/td-p/433191 (topic and NX 12 detail captured from search index; full thread body was behind an access wall at fetch time).

Known data type gap: double signals get truncated to int

See the companion file virtual-commissioning-pitfalls.md for details — worth repeating here since it is specifically a signal-mapping issue: Boolean tags map correctly, but double-precision PLC tags are reported to be forced/converted to int when read into NX MCD, which breaks anything depending on fractional values (continuous positions, analog process values) coming back across the OPC UA link. If your commissioning model behaves correctly for on/off logic but shows staircase-quantized motion or values, check whether an intended double/real PLC tag is actually landing in MCD as an integer.

Manual OPC UA setup checklist (from practitioner-oriented writeups)

Consolidated from community/search-indexed guidance on connecting NX MCD to a PLC via OPC UA:

1. Enable/activate the OPC UA server in the PLC's device properties (TIA Portal), including the correct OPC UA license/operating-system type for the runtime.
2. Ensure PUT/GET communication access is allowed for remote objects (a commonly-missed CPU property checkbox in TIA Portal that silently blocks external reads/writes).
3. In NX MCD's External Signals Configuration, choose the OPC UA interface and add the server using its endpoint URL (vs. choosing the PLCSIM Advanced interface directly, which is the simpler NX 12+ path described above).
4. Complete signal mapping by connecting PLC tags to MCD signal objects — watch for the naming-based auto-match behavior described above, and manually verify any signal that didn't auto-bind.

These steps are aggregated from multiple community/search sources rather than a single authoritative document; treat as a practical checklist to validate against your specific NX version's official documentation, not a verbatim procedure.