Siemens PLCSIM Advanced
Overview
Section titled “Overview”Two routes reach a PLCSIM Advanced instance: the native API (recommended, symbolic tag names, no PUT/GET) and S7comm through the Siemens S7 interface. Platform for the native route: Windows only.
The two routes compare like this.
Set up and parameters
Section titled “Set up and parameters”There are two ways to reach a Siemens PLCSIM Advanced instance from CONNECT. Neither needs a coupler process or a shared-memory bridge.
Native API — recommended
Section titled “Native API — recommended”Interface type Siemens PLCSIM Advanced (native API). CONNECT drives the official Siemens simulation API in its own process and attaches to a registered instance by name.
| Parameter | Example |
|---|---|
| Instance name | PLCSimInstance |
| Update cycle | 10 ms |
| Remote address | 192.168.1.80:50000 (optional) |
Signals are addressed by their symbolic tag name (Motor1_Start, "Data_block_1".Speed), and Browse lists the instance’s tags with their direction already derived from the memory area — %I is written by the viewer, %Q, %M and data blocks are read from it. Optional filters narrow a browse to HMI-visible tags, to named data blocks, or by regular expression.
Unlike the S7comm route below, this route needs no absolute addresses and no PUT/GET, and optimized block access can stay enabled. Softbus works, so the instance needs no virtual Ethernet adapter. CONNECT also detects a TIA software download while running and rebuilds its tag bindings instead of reading addresses that have moved.
Which tags are loaded. PLCSIM Advanced keeps its tag list to 500 000 entries, and every array and structure element counts — asking for every data block of a large (safety) project overruns it. CONNECT therefore loads the process image and the markers plus exactly the data blocks it needs: the ones named in Data Block Filter, and the ones your configured signal addresses point at (an address of the form "Data_block_1".Speed names its block; an unquoted DB1.Speed does not and stays unbound). A Browse has no signals to work from, so it lists data block tags only for the blocks you name in the filter.
If the list still exceeds the limit, CONNECT retries that browse with HMI-visible tags only. It reports this as tagListFallback in GET /status and the gateway log, alongside the requested scope and filter. This does not change your Browse HMI-visible tags only setting; the next connection tries the full list again. A signal whose tag was missing during fallback stays unbound with a tag not found issue until you restart the interface.
Requirements: PLCSIM Advanced V4 to V7 must be installed on the machine CONNECT runs on. The instance must already be registered and running; CONNECT attaches to it but never creates or downloads an instance. CONNECT does not ship the Siemens API. It loads the API from your installation, so your own PLCSIM Advanced license applies. This interface is Windows only and is not offered by the Linux build. If PLCSIM Advanced is not installed, the interface reports this in its status and makes no connection attempt.
An instance on another PC. Set Remote address to host[:port] of that PC’s PLCSIM Advanced Runtime Manager (IPv4 address or host name, default port 50000); empty means the instance runs on the CONNECT machine. The remote PC must allow remote connections in its PLCSIM Advanced Control Panel, and PLCSIM Advanced must still be installed on the CONNECT machine, because the API is loaded from there. A malformed address is shown as a configuration error and not retried.
Not supported in this version. SyncPoint lock-step co-simulation and 64-bit integer tags (LInt, LWord) — those are reported as a signal issue rather than truncated silently.
Over S7comm
Section titled “Over S7comm”Interface type Siemens S7, pointed at the instance. Use this when PLCSIM Advanced is not installed on the CONNECT host, or when CONNECT runs on Linux.
In the PLCSIM Advanced instance settings, switch the network adapter from Softbus to PLCSIM Virtual Eth. Adapter, then enable PUT/GET in the simulated CPU’s protection settings. After that the instance is addressed exactly like a real S7-1500 — same IP, rack and slot. Softbus is not supported: only the virtual Ethernet adapter speaks TCP/IP, addresses must be absolute, and the addressed data blocks must have optimized block access disabled.
Create or import signals
Section titled “Create or import signals”- Manually. Native API: enter the symbolic tag name, for example
Motor1_Startor"Data_block_1".Speed. S7comm route: absolute addresses as on Siemens S7. - Browse. Yes, on the native API route. Browse lists the instance’s tags with the direction already derived from the memory area (
%Iis written by the viewer;%Q,%Mand data blocks are read). Arrays, structures, strings and 64-bit integers are not offered. Optional filters narrow it to HMI-visible tags, to named data blocks or by regular expression. A browse lists data block tags only for the blocks named in the filter. The S7comm route browses only a TIA.sdfsymbol table. - File import. No file import on the native API route. The S7comm route offers the Siemens tag table import described on the Siemens S7 page.
- From the model. When the model already has its PLC signals, Addresses → Fill from controller… in the signal-mapping section of the CONNECT panel previews matches by exact name against what Browse finds and then writes the addresses. Addresses → Import address table… takes a CSV or TSV with
name;address[;dataType[;topic]]rows. New signals take direction and type from the same-named model signal; signals that already exist keep their configured type. See Configuring interfaces.
How direction, data types and write access are decided is explained in Common concepts and Configuring interfaces.
See also
Section titled “See also”- Common concepts — text signals, direction, write access, tracking signals
- Configuring interfaces — adding signals, direction and write access
- All supported interfaces
- Troubleshooting — connection and signal problems