IMDTouchKnowledge BaseShop main store

Troubleshooting

Connecting an HMI to an S7-400 across Ethernet and PROFIBUS

HMI and touchscreens Published 6 min read

Short answer

WinCC flexible will never list an Ethernet-to-PROFIBUS connection, because an HMI connection definition binds one driver to one interface on the panel. Your three-segment path works only if the device between the two media converts the S7 protocol, and a Wi-Fi access point and router convert nothing. Add a documented Ethernet-to-PROFIBUS gateway at the router position, or change one segment; with the panel PROFIBUS-only, the gateway is the branch that fits.

On this page
  1. Why WinCC flexible shows no Ethernet-to-PROFIBUS choice
  2. Counting protocol changes on the S7-400, Wi-Fi and PROFIBUS path
  3. What the gateway must do
  4. Configuring the path once the gateway is in place
  5. Prove each segment, then the path
  6. Decisions for each layout
  7. Questions asked

The connection you are missing does not exist as a dropdown entry, and that is not a mistake in your project: an HMI connection in WinCC flexible binds one driver to one interface on the panel, so there is no combined Ethernet-and-PROFIBUS type to select. The path you describe — S7-400 on Ethernet, Wi-Fi in the middle, PROFIBUS to the panel — can still carry an HMI link, but only if the box between the two media converts the S7 protocol. An access point and a router move frames and packets; they convert nothing. The decision: put a documented Ethernet-to-PROFIBUS gateway in the router position — the Siemens IE/PB LINK is the documented example — or change one segment so both ends share a medium. Because your panel is PROFIBUS-only and no new field cabling is allowed, the gateway is the branch that fits.

Why WinCC flexible shows no Ethernet-to-PROFIBUS choice #

A connection definition in WinCC flexible names a driver and the panel interface that carries it. The PROFIBUS entries expect the panel to sit on the controller's PROFIBUS network with its own PROFIBUS address; the Ethernet entries expect a panel interface on the controller's Industrial Ethernet network with a unique IP address. The software offers exactly the connection types the selected panel and driver support, so a path that changes media halfway is never a single entry: the media change belongs to the network infrastructure between the stations, or to a gateway configured as a station of its own.

An empty list where you expected Ethernet/PROFIBUS is the symptom, not the fault. Before buying anything, run the check in when the HMI software has no driver for your PLC: confirm the panel and driver pair supports an S7 connection over PROFIBUS at all, because a PROFIBUS port that speaks only fieldbus I/O cannot be configured into an HMI connection.

Counting protocol changes on the S7-400, Wi-Fi and PROFIBUS path #

Treat the reported path as a chain and count conversions instead of guessing.

Inputs #

  • Segment 1: S7-400 to access point over an Ethernet cable (your installation).
  • Segment 2: access point to router over Wi-Fi (your installation).
  • Segment 3: router to touch panel over a PROFIBUS cable (your installation).
  • Panel without an Ethernet port, and no field cabling may change (your constraints).
  • WinCC flexible lists no combined connection entry (your symptom).

Rule in words #

One workable HMI path carries exactly one S7 service from the panel driver to the CPU. Every media change inside the path consumes one device documented to convert that service. Transport devices — a bridge, an access point, a plain router — contribute zero conversions regardless of bandwidth.

Arithmetic #

Media changes on the path: 1 (Ethernet to PROFIBUS, at the router). Documented converters available: access point 0 + Wi-Fi link 0 + router 0 = 0. Missing conversions: 1 required - 0 available = 1.

Result and decision #

With one conversion missing, the path cannot carry an S7 connection, and the empty connection list is the correct report of that fact — no WinCC flexible setting closes a gap that is one gateway wide. Install one documented Ethernet-to-PROFIBUS gateway in the router position and the count flips: available 1, missing 1 - 1 = 0, path workable. Keep the rule for every future path on this machine: the connection exists when missing conversions equal 0, and any device that does not name S7 routing in its documentation counts as 0.

What the gateway must do #

Any device in the router position needs more than a PROFIBUS connector. PROFIBUS is the IEC 61158 fieldbus, with standard baud rates from 9.6 kbit/s to 12 Mbit/s (a segment at 1.5 Mbit/s is typical for a mixed I/O network), and the S7 services an HMI connection uses ride on top of it as vendor-specific traffic, which is why the converter must be documented for S7 routing, not merely for the fieldbus. The IE/PB LINK documentation states exactly this: the LINK family connects Industrial Ethernet and PROFIBUS so Ethernet stations reach PROFIBUS nodes, it routes S7 connections and PROFIBUS DP data sets between the two networks, and it operates on the PROFIBUS side as an active node in a DP master system.

Two consequences for your layout. First, the gateway becomes a configured station, with an address on each network declared like any other node — for example, as an illustrative addressing scheme, the CPU and gateway on Ethernet at 192.168.0.0/24 with subnet mask 255.255.255.0, and PROFIBUS address 3 for the gateway in the same network as the DP master. Second, the service list decides the purchase, not the connectors: a gateway that exchanges only DP data sets leaves the panel connection requests unanswered, because an HMI driver sends connection-based S7 traffic, not cyclic I/O. An ordinary IT router documents neither service, and that is the proof the box in your path counts as zero.

Configuring the path once the gateway is in place #

  1. Put the gateway Ethernet port on the same IP subnet as the S7-400. Bridging the Wi-Fi link so PLC and gateway share one subnet is the simplest case; if the link must route, configure the addresses for routed access exactly as the gateway manual prescribes.
  2. Configure the gateway itself per its manual: its Industrial Ethernet address, its PROFIBUS address, and its role as an active node of the DP master system.
  3. Create the panel PROFIBUS connection in WinCC flexible as the WinCC flexible PROFIBUS documentation sets out: panel networked with the controller's PROFIBUS network and given a valid, unique PROFIBUS address.
  4. Declare the routed S7 path across the gateway so the connection the panel uses is carried onto the Ethernet subnet, then download the project to the panel.
  5. Prove the CPU answers from the Ethernet side first: read a value from the S7-400 with the engineering station on that subnet before the panel joins the test.

Prove each segment, then the path #

  • From the engineering station on the Ethernet subnet, read a value from the S7-400. If this fails, nothing downstream matters yet.
  • Open the gateway diagnostics while the panel polls and confirm it reports routed S7 traffic, not merely a PROFIBUS link and a wireless signal.
  • Read a known value on the panel and cross-check it against the CPU.
  • Interrupt the Wi-Fi link for a few seconds, restore it, and confirm the panel recovers by itself and the connection resumes.

A path that hangs hours later usually fails in its wireless segment first, and the pattern matches the faults described in diagnosing intermittent HMI-to-PLC Ethernet comms hangs. One safety rule: if this panel writes setpoints or acknowledges alarms into the process, keep it out of operator hands until the drop test recovers cleanly and a test write is confirmed at the CPU.

Decisions for each layout #

  • Panel with a working Ethernet port — not your case, but the clean one: drop the PROFIBUS leg entirely, put the panel interface on the controller's Industrial Ethernet network with a unique IP, and configure the plain Ethernet S7 connection. One medium, no gateway.
  • Panel PROFIBUS-only and no field cabling may change — your case: add the documented S7-routing gateway at the router position. This is the only branch that keeps all three existing segments.
  • Available gateway documents only DP data exchange: it does not complete the path. Replace it with one whose documentation lists S7 connection routing, or change a segment.
  • No gateway can be added and no segment may change: those constraints cannot all hold at once. When the constraint that finally gives is the panel itself, replacing the PROFIBUS-only terminal with one of today's industrial panel PCs — which carry Ethernet natively — removes the media change at its source instead of adapting around it.

Questions asked

Can a Wi-Fi access point or router carry the HMI link by itself?

Only as transport. An access point bridges Ethernet frames onto and off the wireless segment, and a plain router forwards IP packets between subnets; neither understands the S7 services the panel driver needs, so both count as zero protocol conversions. The PROFIBUS side of the path still needs a device whose documentation names S7 routing between Ethernet and PROFIBUS. Until such a device is in the path, WinCC flexible has no connection it can configure.

Does it matter whether the touch panel is a Siemens panel or a third-party one?

Only through its driver support. A Siemens panel running WinCC flexible carries the S7 drivers for its PROFIBUS and Ethernet interfaces, so the gateway path is configured with tools that expect it. A third-party PROFIBUS-only panel must bring its own S7 driver, and the gateway must be documented for the same S7 service on both sides. If the panel documentation lists no S7 connection over PROFIBUS, no gateway can make that pair communicate.

What if the gateway documentation lists only PROFIBUS DP data exchange?

Then the panel still has no path. DP data exchange moves cyclic I/O between DP masters and slaves; it is not the connection-based S7 service an HMI driver uses, so a data-set-only gateway leaves the panel connection requests unanswered. The gateway documentation must list S7 connection routing between the two networks, as the IE/PB LINK documentation does, before configuration is worth the time.

Should the Wi-Fi segment bridge the two Ethernet sides or route between subnets?

Bridge it when you can. A transparent bridge keeps the S7-400 and the gateway Ethernet port on one IP subnet, the simplest case for a routed S7 path and the easiest to diagnose. Routing between subnets can work, but the addresses must then be configured for routed access exactly as the gateway manual prescribes, and every added hop is one more place for the intermittent hangs to start.

Keep reading

  • How-to

    Connecting an XBTGT HMI to an M241 PLC over Modbus TCP

    Delete the Generic Modbus TCP slave from the M241 device tree and activate the Modbus server on the controller's Ethernet interface instead — that slave makes the M241 a client, so both devices poll and neither answers. Then map Vijeo Designer driver address 40001 to PLC word %MW0, keep TCP port 502 open between panel and controller, and shift the address map by one word if a test read lands one register off.

    HMI and touchscreens

  • Troubleshooting

    Connecting a CompactLogix PLC to an HMI over EtherNet/IP

    A CIP transport unsupported fault on a Generic Ethernet/IP module in a CompactLogix project means the connection was built the wrong way around. For HMI tag access, delete the module, select the panel's Rockwell PLC driver, point it at the controller IP, and rebuild the tags — no assembly instances, I/O sizes, or EDS file.

    HMI and touchscreens

  • How-to

    Connecting an HMI Panel to an S7-1500 PLC

    Confirm the HMI's documented driver covers the S7-1500 for your exact panel model and software revision, put the panel and CPU on the same subnet, permit the connection in the CPU protection settings, then validate one known PLC tag before building screens. A working Ethernet link alone proves nothing about tag access.

    HMI and touchscreens