Integrating SIMATIC Comfort Panels into PCS 7 PROFINET MRP Networks Without GSD Faults

A SIMATIC TP1200 Comfort Panel displays a persistent red diagnostic cross ("Device configured, but not available") in PCS 7 Hardware Configurator when configured as a generic GSD/GSDML slave because Comfort Panels operate as autonomous S7 communication clients rather than cyclic PROFINET IO Devices (Application Relations). Unless the panel is explicitly engineered as an IO Device with configured direct keys in TIA Portal, importing its GSD file into HW Config under a CP 443-1 causes the controller to expect cyclic IO submodules that the panel firmware does not host. In PCS 7, the panel should instead communicate via S7 connections over ISO-on-TCP, while participating physically in the MRP ring solely as a Media Redundancy Protocol client.

Root Cause of the 'Device Configured, But Not Available' Fault

Engineers frequently integrate SIMATIC Comfort Panels (such as the TP1200 Comfort 6AV2124-0MC01-0AX0) into existing SIMATIC PCS 7 systems to provide local machine visualization alongside centralized WinCC OS clients. When the plant utilizes a redundant PROFINET ring operating under Media Redundancy Protocol (MRP), engineers often attempt to insert the Comfort Panel directly into the ring topology governed by an Industrial Ethernet communication processor (such as CP 443-1 6GK7443-1EX30-0XE0).

A common point of failure occurs when the engineer exports the panel's GSD/GSDML file from TIA Portal and imports it into the STEP 7 Hardware Catalog in PCS 7, dropping it onto the PROFINET IO system of the CP 443-1. Upon downloading HW Config, the controller marks the panel with a red strike-through icon and reports: Device configured, but not available.

Even though the panel is fully reachable via 'Edit Ethernet Nodes' and CP 443-1 port diagnostics confirms the panel is physically connected as a neighbor, the PROFINET IO Controller cannot establish an Application Relation (AR). This occurs because standard Comfort Panels communicate via acyclic S7 communication (WinCC Comfort runtime querying data blocks), not cyclic IO device polling.

S7 Communication vs Cyclic PROFINET IO Architecture

Understanding the distinction between PROFINET IO cyclic data exchange and WinCC Comfort S7 communication is vital for correct hardware engineering:

Communication ModeEngineering PlatformProtocol / TransportController RolePanel Behavior & StatusCyclic PROFINET IO DeviceHW Config via GSDMLPROFINET RT (Ethertype 0x8892)IO Controller expects cyclic I/O slot dataFails with 'Device not available' unless Direct Keys are configured in TIAAcyclic S7 CommunicationTIA Portal WinCC ComfortS7 Protocol / ISO-on-TCP (Port 102)S7 Server (CPU 417 / CP 443-1 passively answers requests)Operates seamlessly; queries DB tags without requiring GSD in HW ConfigMRP Ring ParticipationTIA Portal & PCS 7 HW ConfigMRP Frames (Ethertype 0x88E3)Ring Master (SCALANCE X or CP 443-1)Functions as MRP Client; forwards ring test frames through onboard switch

If the panel is only intended to display tags, alarms, and trends from the PCS 7 controller, it does not need to be configured as an IO device under the CP 443-1 in PCS 7 HW Config. It only needs an IP address, subnet mask, and S7 connection configured in TIA Portal.

Configuring TP1200 Comfort in a PROFINET MRP Ring

If the TP1200 Comfort Panel is physically wired in series within an MRP ring (utilizing its two onboard RJ45 Ethernet ports P1 and P2):

MRP Role Assignment: The Comfort Panel must be configured as an MRP Client in TIA Portal hardware configuration (PROFINET interface -> Media redundancy -> MRP domain -> Client).
Ring Integrity: The Comfort Panel firmware supports MRP client functionality with standard 200 ms reconfiguration times. However, if the panel is rebooted or powered down, the physical link is briefly broken until the ring master detects the interruption and closes the alternate path.
Alternative Star/Stub Topology: To avoid ring disruptions during panel maintenance, standard practice is to connect the Comfort Panel as a spur node to an external managed switch (e.g., SCALANCE X204-2 6GK5204-2BB10-2AA3) that resides inside the MRP ring, rather than routing the primary ring cable through the operator panel.

Step-by-Step Integration in TIA Portal and PCS 7

To integrate a TP1200 Comfort Panel without GSD communication errors:

Configure S7 Controller in TIA Portal:
- In TIA Portal (V13/V14/V15), add the TP1200 Comfort Panel (6AV2124-0MC01-0AX0).
- In the Network View, add an 'Unspecified S7-400 CPU' (or configure the exact S7-417-4 / CP 443-1 IP address).
- In the HMI Connections tab, create an S7 Connection pointing to the CP 443-1 IP address. Set the Controller parameters: Rack 0, Slot 3 (or the exact rack/slot of the CPU 417-4).
Configure PROFINET Interface on the HMI:
- Set the IP address and Subnet Mask to match the PCS 7 Plant Bus subnet.
- Assign the unique PROFINET Device Name (e.g., hmi-tp1200-area1).
- Under Media Redundancy, set the MRP role to Client if the panel is inserted into the physical fiber/copper ring.
Clean Up PCS 7 Hardware Configuration:
- Open HW Config in SIMATIC Manager.
- If a GSDML object was previously dragged onto the CP 443-1 PROFINET IO system, delete the GSDML device.
- Ensure the CP 443-1 has the PROFINET IO system enabled, with its MRP role set to Manager or Client as required by the ring topology.
- Save and Compile HW Config, then download changes to the S7-400 controller.
Download Runtime to the Panel:
- Download the WinCC Comfort runtime project to the TP1200 Comfort panel via Ethernet using ProSave or TIA Portal.
- The panel immediately initiates S7 communication with the CPU, reading process variables without controller diagnostic alarms.

Verification

To verify seamless panel integration and network health:
1. On the TP1200 Comfort Panel, verify that process tags update dynamically and that no 'Connection disconnected: Connection_1' system alarms appear.
2. Open SIMATIC Manager and inspect the CP 443-1 diagnostic buffer; verify that no 'IO device failure' or 'Application Relation aborted' events are logged.
3. In NCM S7 Diagnostics (Options -> NCM S7 -> Diagnostics), inspect the active S7 connections table; confirm an established S7 connection from the TP1200 IP address to the CPU.
4. Test physical ring redundancy by disconnecting one RJ45 cable from port P1; verify that communication seamlessly switches over within 200 ms without dropping HMI communication.

Limitations and Operational Precautions

Do not configure a Comfort Panel as a cyclic PROFINET IO Device unless the application specifically requires 'Direct Keys' (where panel pushbuttons directly trigger discrete PLC input bytes via cyclic IO images). Configuring an unconfigured IO device generates continuous OB86 (rack/station failure) and OB122 (I/O access error) interrupts in the S7-400 CPU, inflating cycle times and cluttering the diagnostic buffer.

Engineer FAQ

Why did the CP 443-1 report 'Device configured but not available'?

Because HW Config was told the panel is a cyclic PROFINET IO Device via GSDML, but the panel was running standard WinCC Comfort runtime without cyclic IO submodules enabled.

Can a TP1200 Comfort communicate with an S7-400H redundant CPU pair?

Yes, but Comfort Panels do not natively support redundant S7 communication (H-connections). The panel can either communicate via a single CP 443-1, utilize a software script to toggle connection IPs upon failure, or connect through a SIMATIC PN/PN Coupler.

Is it safe to place an HMI panel directly into a high-availability MRP ring?

While supported, it is not recommended in mission-critical sections. If the panel is powered down for maintenance, the ring opens. Connecting the panel to a spur port on an industrial managed switch (such as SCALANCE XC-200) prevents panel maintenance from impacting the plant ring.