Architecture Overview
The SIMATIC TP1500 Comfort (catalog number 6AV2 124-1QC02-0AX0) is a 15-inch widescreen HMI panel from the SIMATIC Comfort Panel family. Unlike Basic Panels, Comfort Panels ship with two physical PROFINET interfaces (X1 and X3) plus USB host/device, RS-422/485, and optional audio. This dual-port architecture lets a single Comfort Panel terminate S7 connections to two different automation networks that do not share a routing path — for example, a plant-floor S7-1500 cell on 192.168.1.0/24 and an enterprise S7-300/400 line on 10.236.147.0/8 — without requiring an external router.
This document describes the engineering path that has been validated by Siemens Industry Customer Care for connecting two SIMATIC PLCs from different IP subnets to one TP1500 Comfort: PLC_1 (S7-1500) on PROFINET port X1 and PLC_2 (S7-300/400) on PROFINET port X3.
TP1500 Comfort Hardware Interfaces
| Interface | Label | Function | Default Role |
|---|---|---|---|
| PROFINET (LAN) | X1 | 10/100 Mbps RJ45, integrated 2-port switch | Primary HMI / engineering / PLC connection |
| PROFINET (LAN) | X3 | 10/100 Mbps RJ45, separate MAC/IP stack | Secondary network — PLC, HMI-HMI, Smart Server/Client |
| USB Type A | X20 | USB 2.0 host for memory stick / mouse / keyboard | Service |
| USB Type Mini-B | X21 | USB 2.0 device (image export) | Service |
| RS-422/RS-485 | X10 | Serial, MPI / PROFIBUS-capable via adapter | Legacy PLC |
Both X1 and X3 are independent Layer-3 interfaces. They each maintain their own IP address, subnet mask, gateway, and PROFINET device name. There is no built-in routing between them; the panel will not forward IP packets from one interface to the other. This is critical: traffic to a PLC must originate from the interface that shares the PLC's subnet.
Reference Topology
The figure below shows the validated topology referenced by Siemens Asia Pacific Hub support.
IP Subnet Routing Constraints
The TP1500 Comfort uses standard Windows CE / Windows Embedded Compact networking stacks. Each PROFINET port is bound to a virtual adapter. The panel's connection manager (CCAgent / CCEServer) builds the S7-Comm PDU using the local IP that matches the destination subnet.
- Different subnets: Required. X1 and X3 must terminate networks that cannot be aggregated into a single supernet route. The reference case uses 192.168.1.0/24 on X1 and 10.0.0.0/8 on X3.
- Gateway: Configure the gateway only on the interface that must reach an upstream network. If both PLCs are local and reachable on-link, set both gateway fields to 0.0.0.0 to avoid asymmetric routing.
-
PROFINET names: Each interface may carry an independent PROFINET device name (e.g.
hmi-x1andhmi-x3). The PROFINET name is required only when the panel acts as a PROFINET IO device; for pure S7-Comm traffic the IP is what matters. - MTU and VLAN: Default MTU 1500. Comfort Panels do not support VLAN tagging on X1/X3 in firmware ≤ V17 — verify VLAN tagging support against your project firmware release notes before deploying a tagged infrastructure.
Prerequisites
- TP1500 Comfort with image version supporting dual PROFINET interfaces (firmware V14 SP1 or higher; V17/V18/V19/V20/V21 recommended for current security patches).
- TIA Portal V17 or higher installed on the engineering station. WinCC Comfort/Advanced is required for Comfort Panel configuration.
- S7-1500 project (CPU 1511/1513/1515/1516/1517/1518 or ET200SP CPU) configured in the same TIA Portal project.
- S7-300 (CPU 31x PN/DP) or S7-400 (CPU 41x PN/DP) project — STEP 7 V5.x project imported via TIA Portal, or co-located TIA Portal project if the CPU is part of the modern line.
- Two Ethernet patch cables with shielded RJ45 connectors; one per PROFINET segment.
- Physical separation of the two networks. Do not bridge X1 and X3 to the same physical switch unless a managed switch enforces two VLANs that map to the two interfaces.
TIA Portal Project Configuration
Step 1 — Insert the HMI device
Open the TIA Portal project. From the hardware catalog navigate to HMI → SIMATIC Comfort Panels → 1500 → TP1500 Comfort and drag the device onto the project tree. Confirm the catalog order number matches the physical panel (6AV2 124-1QC02-0AX0 for indoor, 6AV2 124-1QC13-0AX0 for Outdoor).
Step 2 — Configure PROFINET interface X1
Open Devices & Networks → TP1500 → PROFINET interface [X1]:
| Parameter | Value (PLC_1 network) |
|---|---|
| Subnet | Click Add new subnet — name suggestion PN/IE_1
|
| IP address | 192.168.1.2 |
| Subnet mask | 255.255.255.0 |
| Router address | 0.0.0.0 (leave empty) |
| PROFINET device name | hmi-x1 |
| Operation mode | PN-IO or S7-Comm only — disable PROFINET IO if not used |
Step 3 — Configure PROFINET interface X3
Open Devices & Networks → TP1500 → PROFINET interface [X3]:
| Parameter | Value (PLC_2 network) |
|---|---|
| Subnet | Add a second subnet — name suggestion PN/IE_2
|
| IP address | 10.236.147.126 |
| Subnet mask | 255.0.0.0 |
| Router address | 0.0.0.0 (leave empty) |
| PROFINET device name | hmi-x3 |
| Operation mode | S7-Comm only (recommended when X1 is used for IO) |
Step 4 — Create the HMI connections
Open Connections in the project tree of the TP1500. Two S7-Comm connections must be created — one for each PLC.
Connection_1 (PLC_1 — S7-1500):
- Communication driver: SIMATIC S7-1500
- PLC station: PLC_1 (S7-1500 CPU)
- Interface on HMI side:
PROFINET [X1] - Interface on PLC side:
PROFINET [X1] - Connection name:
HMI_1_PLC1500
Connection_2 (PLC_2 — S7-300/400):
- Communication driver: SIMATIC S7-300/400
- PLC station: PLC_2 (S7-300/400 CPU)
- Interface on HMI side:
PROFINET [X3] - Interface on PLC side: PROFINET port of the CPU
- Connection name:
HMI_1_PLC300 - Connection resource: An unused S7 connection resource on the S7-300/400 CPU. Slot 0/1 are typically reserved by STEP 7 and the panel; allow at least one resource for the HMI.
For each connection set Mode → Active on the HMI. The S7-Comm connection establishment is initiated from the HMI; the S7-300/400 only answers.
PLC-Side Configuration
S7-1500 (PLC_1)
- In the S7-1500 device configuration, open Properties → Protection & Security.
- Under Connection mechanisms, tick Permit access with PUT/GET from remote partner only if the HMI uses PUT/GET and not the symbolic optimized access.
- Confirm that the PROFINET interface IP matches 192.168.1.1, subnet 255.255.255.0.
- Ensure the S7-1500 CPU has enough free connection resources. S7-1500 supports up to 128 S7-Comm server connections depending on CPU type. The HMI consumes one resource per connection.
S7-300 / S7-400 (PLC_2)
- Open the CPU properties in STEP 7 (TIA Portal or STEP 7 V5.x depending on project origin).
- Navigate to Protection and ensure Permit access with PUT/GET from remote partner (RFC1006) is enabled. Without this, the S7-300/400 will silently drop the HMI's S7-Comm request even when IP and routing are correct.
- Confirm the IP address 10.236.147.125 and subnet mask 255.0.0.0 on the CPU PROFINET interface.
- Open Communication → Connections on the S7-300/400. Confirm at least one S7 connection (ISO-on-TCP / TCP) resource is free. S7-300 supports up to 16; S7-400 CPU 41x PN/DP supports 32 by default. If the project already consumes all slots, the HMI connection cannot be established.
- If a firewall is enabled on the S7-300/400 (rare, but supported on newer S7-300 CPUs with security module), open port 102 (ISO-on-TCP) for the HMI's X3 IP.
HMI-Side Runtime Configuration
- Compile the HMI project. TIA Portal will warn if the connection resource cannot be allocated. Resolve any warnings before downloading.
- Download the project to the TP1500 Comfort via X1 or X3. Siemens recommends using the X1 port for engineering download because the service stack on X3 may be disabled in some configurations.
- After project download, restart the panel. The two connections appear in the Connections runtime view on the Service Desktop.
- If the project was modified after first commissioning, also reset the runtime. From Service Desktop: Start → Settings → OP → Reboot.
Verification and Diagnostics
Network reachability
Open the Service Desktop on the panel (Start → Programs → Service Desktop). Launch Start → Programs → Accessories → Command Prompt and run:
ping 192.168.1.1 :: PLC_1
ping 10.236.147.125 :: PLC_2
ipconfig
- X1 must show 192.168.1.2 / 255.255.255.0
- X3 must show 10.236.147.126 / 255.0.0.0
tracert 10.236.147.125
- First hop must be X3 local subnet (no router needed if on-link)
If ping from one interface fails, verify the cable, the switch VLAN, and the PLC PROFINET interface status LEDs.
S7-Comm diagnostic on the panel
From the Service Desktop:
- Start → Programs → HMI Tools → HMI Diagnose (or Connection Status on older firmware).
- Each connection displays Established / Not established / Fault.
- If a connection shows Fault, expand the detail to view the S7 error code (e.g. 0x00 = no error, 0x01 = connection aborted, 0x05 = resource missing, 0x06 = access error).
PLC-side diagnostic
For the S7-1500: open TIA Portal online → Diagnostics → Connection information. For the S7-300/400: in STEP 7 open PLC → Information → Communication. Look for:
- Connection establishment count
- Active partner IP — must be 192.168.1.2 (X1) or 10.236.147.126 (X3)
- Connection error counter — non-zero indicates authentication or access rejection
Wireshark capture
For deep analysis, mirror the X1 or X3 switch port and capture with Wireshark. Filter on s7comm. Validate the S7 PDU header source TSAP and destination TSAP. The HMI uses TSAP 01.01 by default; the S7-300/400 returns its slot TSAP (e.g. 03.01). If the TSAP differs, the project mismatch is the root cause.
Known Limitations and Workarounds
| Symptom | Root Cause | Workaround |
|---|---|---|
| X3 only pings; S7-Comm not established | Connection on PLC_2 bound to wrong interface slot | Re-bind Connection_2 to PROFINET [X3] in TIA Portal |
| S7-300/400 rejects all S7-Comm requests | PUT/GET disabled on S7-300/400 | Enable access with PUT/GET from remote partner |
| Intermittent S7-300/400 timeout | CPU connection resource exhausted | Free a slot or use connection multiplexing via CP343-1 |
| X1 and X3 same subnet | Layer-2 confusion, duplicate IP detection | Reassign X3 to a different subnet (e.g. 10.x.x.x) |
| Tags from PLC_2 show # in runtime | Variable address typo or DB optimized access denied | Disable optimized access on the DB used by the HMI |
| Service Desktop disabled on X3 | Firmware configuration | Use X1 for engineering access; X3 is data-only |
| Connection breaks after 60 s | Keepalive mismatch | Adjust keepalive interval in connection properties |
Comparison With Other Architectures
| Approach | Pros | Cons |
|---|---|---|
| TP1500 Comfort dual interface (X1+X3) | Single panel, single project, no external router | X3 routing constraints; cannot bridge subnets |
| Two HMI panels, one per network | Simplest network design | Higher hardware cost, duplicate screens |
| SCALANCE XC/XR router between subnets | Flexible routing, multiple VLANS | Adds single point of failure, extra commissioning |
| CP343-1 / CP443-1 on S7-300/400 with routing | Native S7 routing tables | Older S7-300 CPUs lack router capability |
Troubleshooting Matrix
| Check # | Action | Expected Result |
|---|---|---|
| 1 | Verify X1 / X3 LEDs (Link / Activity) | Both green link + activity when PLC traffic active |
| 2 | ping PLC_1 from Service Desktop X1 | < 5 ms reply |
| 3 | ping PLC_2 from Service Desktop X3 | < 5 ms reply |
| 4 | ipconfig /all | X1 = 192.168.1.2/24, X3 = 10.236.147.126/8 |
| 5 | Open HMI Diagnose | Both connections Established |
| 6 | Check PLC_2 protection | PUT/GET = enabled |
| 7 | Free connection resources on S7-300/400 | At least one S7 server resource available |
| 8 | Wireshark capture on PLC_2 segment | S7-Comm TSAP matches HMI project |
Security Considerations
With TIA Portal V18 and Comfort Panel firmware V18 onwards, the panel supports Security Integrated. To harden the dual-network configuration:
- Enable user management on the panel and assign operator/admin roles.
- Disable unused services (SmartServer, SmartClient, Web Server) on the X3 interface if PLC_2 is a critical infrastructure segment.
- Use a managed switch with port security on the X3 segment to prevent accidental bridging from X1.
- Apply firmware updates through Siemens Industry Online Support and verify SHA-256 checksum before download.
Documentation References
- Performance Features of Comfort Panels — TIA Portal V21
- SIMATIC HMI TP1500 Comfort Operating Instructions (6AV2 124-1QC02-0AX0) — Siemens Industry Online Support, entry ID 109749262
- TIA Portal Help Portal — Comfort Panel Communication (S7-Comm, PROFINET IO)
FAQ
Can a TP1500 Comfort connect to two S7 PLCs in different IP subnets at the same time?
Yes. Use PROFINET X1 for one PLC and PROFINET X3 for the other. Configure each interface with an IP and subnet mask that matches its target PLC. X1 and X3 must be in different subnets; assigning the same subnet to both produces ARP conflicts.
Is the X3 port officially documented for S7-Comm?
Siemens supports X3 as a second PROFINET interface that can terminate S7-Comm, PROFINET IO, HMI-HMI, or Smart Client/Server depending on the firmware version. The dual-S7 use case is supported on firmware V14 SP1 and later, with the S7 connection configured in TIA Portal under the X3 interface of the HMI.
Why does my S7-300 reject the HMI connection even though ping works?
On S7-300/400 CPUs, PUT/GET access must be explicitly enabled under Protection → Permit access with PUT/GET from remote partner. Without this, the CPU drops S7-Comm requests with error code 0x81 (resource error) at the security layer even when IP routing is correct.
How many PLC connections can a TP1500 Comfort terminate in total?
Up to 16 simultaneous PLC connections, depending on firmware. The exact limit and PowerTag count are listed in the Comfort Panel Performance Features documentation. For two PLCs on two ports, the panel stays well within budget.
Do I need an external router between the two networks?
No. The TP1500 Comfort hosts two independent Layer-3 interfaces. As long as the HMI service that handles S7-Comm binds to the correct local interface for the destination subnet, the panel reaches each PLC on-link. A router is only required if the HMI must also reach other devices beyond the two PLCs.