Adding IPC PX-39A PRO to TIA Portal V17: WinCC Unified Setup

Problem Overview

When adding a SIMATIC IPC PX-39A PRO as an HMI / PC station in TIA Portal V17, the device does not appear in the hardware catalog even after installing the latest V17 Hardware Support Packages (HSPs) and the 08/2024 catalog update. The standard "Add new device" workflow that engineers expect from a Siemens Panel PC integration is blocked, and the missing SKU shows up as "no compatible device found" in the catalog search.

The IPC PX-39A PRO is a current-generation Panel PC, documented under Siemens Support entry ID 109815541. Native catalog entries for this device do not appear in TIA Portal V17; they are introduced in TIA Portal V18 starting at Update 4 and in TIA Portal V19 starting at Update 2. Two practical paths resolve the field issue: (a) run the V17 project on the IPC PX-39A PRO using a generic PC Runtime configuration, or (b) upgrade the engineering tool to V18 Update 4 or V19 Update 2 and load the device natively.

SIMATIC IPC PX-39A PRO Hardware Profile

The SIMATIC IPC PX-39A PRO is an all-around industrial Panel PC designed for protected operator control and high-availability visualization. According to the Siemens product entry SIMATIC IPC PX-39A PRO (109815541), the PRO variant is built on the base Panel PC PX-39A platform and adds PRO-class industrial functionality for harsher environments (extended temperature, shock/vibration, 24/7 operation). The PROFIBUS product finder entry SIMATIC IPC PX-39A PRO summarizes the device as a "all-around IPC protected Panel PC" with maximum industrial functionality.

Key functional characteristics relevant to a WinCC Unified Runtime project:

• Multi-touch operator panel with capacitive glass front (15", 19", 22", or 24" diagonal, depending on configuration)
• Windows 10 IoT Enterprise LTSC 2021 (or Windows Server 2019) preinstalled on selected SKUs
• Intel Core i-class CPU (i3 / i5 / i7 SKU depending on order code)
• Onboard PROFINET (2-port switch) and optional PROFIBUS DP master/slave interfaces for fieldbus integration
• Pre-installed or supported WinCC Unified Runtime; version depends on shipment state and firmware bundle
• PRO-class chassis: dust- and splash-protected front (IP65 typical), fanless cooling on select models

TIA Portal Version Compatibility Matrix

Root Cause: Why the IPC PX-39A PRO Is Missing from V17

Three independent reasons prevent the IPC PX-39A PRO from appearing in the V17 hardware catalog:

1. Catalog cutoff. The IPC PX-39A PRO was added to the TIA Portal catalog in V18 Update 4. V17 and its associated HSPs do not include this device description because the SKU was finalized after V17's final update.
2. HSP coverage. HSPs for V17 only add devices that were known when V17 was current. Late-cycle hardware (such as the PX-39A PRO) is not back-ported to V17 via HSP; instead, it appears in the next major version (V18) and may be back-ported there.
3. WinCC Advanced vs. WinCC Unified. The 08/2024 update tested by the field engineer was applied to a configuration using WinCC Advanced. The IPC PX-39A PRO is a WinCC Unified target. The WinCC Advanced runtime does not match the Unified Runtime that the IPC expects, so the device still does not appear under the Advanced catalog path even after a more recent catalog patch is installed.

None of these reasons indicate a defective installation. The V17 catalog is functioning as designed; the device simply post-dates the V17 cutoff. The 08/2024 catalog update adds new devices for the WinCC Advanced runtime branch but does not bring forward PC station SKUs from V18 / V19 catalogs.

Solution Path A — Configure WinCC Unified Runtime with a Generic PC System

For WinCC Unified PC Runtime, the IPC hardware model does not need to be present in the catalog. The PC Runtime runs as a Windows service on the IPC and exposes its own interface set (PROFINET, PROFIBUS, OPC UA, web) regardless of the host PC SKU. Configure the project with a generic PC System and the WinCC Unified Runtime HMI subtype, then load the compiled project to the IPC.

Prerequisites

• TIA Portal V17 with the latest V17 updates installed (V17 + Update 5 minimum recommended)
• WinCC Unified option licensed for V17 engineering (TIA Portal Unified option, or bundle license)
• WinCC Unified Runtime V17 installed on the target IPC PX-39A PRO (matching the engineering version)
• Ethernet network reachability between engineering PC and the IPC (ping test, same subnet or routed)
• Siemens firewall rules opened: TCP/UDP 102 (PROFINET), TCP 443 (web/HMI), TCP 2308 (RPC), TCP 4840 (OPC UA)

Step-by-step

1. Open the TIA Portal V17 project.
2. Double-click Add new device in the project tree.
3. Select PC Systems → SIMATIC PC → WinCC Unified PC RT. Do not browse for "IPC PX-39A PRO" — that entry does not exist in V17.
4. Confirm the new PC station appears in the project tree with the HMI_RT sub-node.
5. Open HMI_RT and configure screens, tags, alarms, and connections identically to a Unified Comfort Panel project.
6. In the PC station's Device configuration, add the PROFINET and/or PROFIBUS interfaces required by the fieldbus topology. These interface nodes are available without referencing the IPC hardware catalog.
7. Compile the project: Project tree → right-click PC station → Compile → Software (rebuild all).
8. In Online → Accessible devices, browse for the IPC by IP and select the PC station as the target.
9. Download the project. The V17 runtime on the IPC accepts the V17-compiled configuration because the runtime version matches the engineering version.

PC System vs. IPC Station — Why the difference matters

The PC System placeholder exists exactly because WinCC Unified PC Runtime is host-agnostic. It encapsulates the runtime service contract (screens, tags, alarms, logging, scripting, OPC UA server, web server) without binding to any specific Panel PC SKU. The IPC PX-39A PRO is a Windows-based PC with the runtime installed; from the runtime's perspective it is interchangeable with any other x86 IPC running the same Unified PC RT version. The catalog name is informational, not functional.

Solution Path B — Upgrade TIA Portal to V18 Update 4 or V19 Update 2

Upgrade the engineering tool if you require the IPC PX-39A PRO as a named device in the catalog (for example, because your engineering standard mandates explicit hardware references, or because future migrations rely on device-specific diagnostic buffers and firmware metadata).

Recommended target versions

• V18 Update 4 — minimal upgrade for native catalog support of the PX-39A PRO. Preserves V17 project compatibility (V18 opens V17 projects and offers upgrade on next save).
• V19 Update 2 — current long-term supported version with broader catalog coverage, additional Unified Runtime features, and improved OPC UA server diagnostics.

Upgrade procedure

1. Install TIA Portal V18 (or V19) on a separate engineering station, or upgrade the existing one in place.
2. Apply the latest update (V18 Update 4 or V19 Update 2 or higher).
3. Open the existing V17 project. TIA Portal prompts to upgrade; confirm.
4. Open the hardware catalog and navigate to PC Systems → SIMATIC IPC → IPC PX-39A PRO. The device is now listed with its native article number.
5. Drag the IPC PX-39A PRO into the project as a replacement for the generic WinCC Unified PC RT station. TIA Portal maps compatible interfaces automatically; review the PROFINET / PROFIBUS port assignments.
6. Compile and download. The runtime on the IPC must be V18 or V19 to match the upgraded project; if the IPC ships with V17 runtime only, install the newer runtime package from the Siemens support download portal.
7. Transfer a V18 or V19 license to the IPC via the Automation License Manager.

Installing Hardware Support Packages (HSP) for New Devices

HSPs extend the hardware catalog of an installed TIA Portal version without requiring a major version upgrade. They are particularly useful for adding new I/O modules, drives, or third-party devices. They are not, however, a back-port channel for PC station SKUs: PC station catalog entries are added at major version cutoff points, and V17 has no published HSP for the IPC PX-39A PRO.

HSP installation procedure

1. Download the HSP ZIP from the Siemens support portal (TIA Portal → Downloads → Hardware Support Packages).
2. Open TIA Portal V17.
3. Select Options → Support Packages.
4. In the Support Packages dialog, click Install… and browse to the downloaded .zip.
5. Wait for the catalog import to complete. Restart TIA Portal if prompted.
6. Verify installation: Options → Support Packages → Installed support packages tab lists the new package.

HSPs added in step 4 do not retroactively add the IPC PX-39A PRO to V17 because no V17 HSP for this SKU has been published. The same procedure, however, does work for adding the SKU to V18 if a back-port HSP is published there.

WinCC Unified Runtime Configuration Details

Whether you use the generic PC System placeholder or the native catalog entry, the WinCC Unified Runtime configuration follows the same rules. The following parameters are common commissioning targets:

Runtime firewall rules on the IPC

The Unified Runtime opens several TCP/UDP ports. Open them on the Windows Firewall of the IPC before commissioning:

• TCP/UDP 102 — PROFINET IO / S7 communication
• TCP 443 — Unified web server (HTTPS)
• TCP 2308 — TIA Portal project download (RPC)
• TCP 4840 — OPC UA server endpoint
• UDP 34964 — PROFINET discovery (DCP)

Loading the Runtime and Licensing on the Target IPC

The runtime on the IPC must match the engineering version that produced the compiled project. Mismatched versions cause load failures with diagnostics like "HMI load failed: Runtime version mismatch" or "Configuration incompatible with installed runtime version".

1. On the engineering PC, open the project in TIA Portal V17 (or V18 Update 4 / V19 Update 2).
2. Select the PC station in the project tree.
3. Right-click and choose Compile → Software (rebuild all). Resolve any compile errors.
4. From the menu, choose Online → Extended download to device….
5. In the Target device address field, enter the IPC's IP address. Confirm the PG/PC interface is set to the correct Ethernet adapter.
6. Click Search and select the IPC from the list of accessible nodes.
7. Confirm the runtime version shown in the target device dialog matches the engineering version. If not, install the matching runtime on the IPC first.
8. Click Load. Accept the certificate prompt if HTTPS is enabled.
9. Once the load completes, the Unified Runtime on the IPC starts in run mode automatically.

Licensing the Unified Runtime

The WinCC Unified Runtime on the IPC requires a license key transferred via the Automation License Manager. Common license types:

• WinCC Unified PC RT V17 (16 / 64 / 256 / 2k / 4k / 8k / 16k / 32k tags) — tag-count tiered licenses for V17 runtime.
• WinCC Unified PC RT V18 (16 / 64 / … tags) — V18-equivalent license.
• WinCC Unified PC RT V19 (16 / 64 / … tags) — V19-equivalent license.

A V18 or V19 license does not activate a V17 runtime, and vice versa. The license must match the runtime version. Trial licenses (21 days) are available for testing through the Siemens online software delivery portal.

Verification & Commissioning Checklist

Troubleshooting Matrix

FAQ