IMDTouchKnowledge BaseShop main store

Troubleshooting

When an M580 Downloads but Sends No Data to the HMI

HMI and touchscreens Published 6 min read

Short answer

Both projects download because programming access and runtime data access are separate channels out of the CPU. On Control Expert v16.x, Engineering Link Mode set to Enforced in the Security tab refuses the HMI's reads while downloads still succeed, and a Data Dictionary enabled after the last build never delivers the symbols. Set Full Access, do a full rebuild, download, and confirm the Data Dictionary was on before that rebuild; a force test in RUN proves it.

On this page
  1. Why the panel connects and still reads nothing
  2. The suspects in test-cost order
  3. Set Full Access, rebuild, download
  4. The Data Dictionary must be on before the rebuild
  5. The addressing check, with the arithmetic
  6. When some objects appear and others do not
  7. Prove the link before you call it fixed
  8. Questions asked

The downloads tell you the network and the CPU are fine; the dead screen tells you the CPU is refusing to serve data. On EcoStruxure Control Expert v16.x, the Engineering Link Mode in the project's Security tab gates runtime data access separately from the engineering download, and Enforced blocks the HMI's reads while both transfers still succeed. Open the Security tab, set Engineering Link Mode to Full Access, run a full rebuild of the project, download to the CPU, and force a bound variable in RUN: the panel should follow within a screen refresh. Then confirm the Data Dictionary option in the CPU project settings was enabled before that rebuild, because symbols only reach the CPU through a full rebuild and download.

Why the panel connects and still reads nothing #

Programming access and data access are two separate channels out of an M80 CPU. The engineering download rides one; the panel's runtime reads ride the other, and a successful transfer of both projects proves only the first. On Control Expert v16.x, the Engineering Link Mode in the Security tab decides what that second channel carries: with Enforced, the CPU keeps refusing the HMI's data access while the programming path keeps working — a clean download, a forced variable in RUN, and a dead HMIS6700 screen.

Objects vanish rather than show zeros because a button or graphic whose visibility is animated by a PLC variable takes its hidden state whenever that variable cannot be read. The object is not failing to draw; its controlling value is unreadable.

The same separation bites PC runtimes. On that side, choosing a data path from an M80 PLC walks through the equivalent options.

The suspects in test-cost order #

Rank the candidates by what each costs to test, then spend the cheap ones first:

  • Engineering Link Mode set to Enforced (v16.x, Security tab). The panel stays reachable and the CPU stays programmable while every read is refused. Cost: one setting, a rebuild, a download. Decisive reading: values start moving under Full Access.
  • Data Dictionary enabled after the last build. The option decides what a full build stores; symbols reach the CPU only through a rebuild and a download, so a checkbox added afterwards leaves the controller without them. Cost: a rebuild and a download. Decisive reading: the Operator Terminal Expert import lists the current variables.
  • Variables bound to a stale device. Objects resolve to no source and stay blank. Cost: the HMI build output. Decisive reading: no unresolved-variable warnings.
  • Runtime path different from the engineering path. The download can reach the CPU through a port or IP the panel never uses. Cost: comparing two addresses. Decisive reading: the CPU IP in Control Expert equals the HMI's target IP, same subnet, same mask.

Test the first, then the second. Both are free, and both fail in exactly the reported way: connected, programmable, no data.

Set Full Access, rebuild, download #

  1. Confirm the release is v16.x, open the project's Security tab, and read Engineering Link Mode. Enforced is the primary suspect, and you should not commission an HMI link under it.
  2. Set Full Access for the test.
  3. Run a full rebuild of the project and clear every error the build reports.
  4. Download to the CPU and put it in RUN.
  5. Force a bound BOOL with no machine effect, or write a bound word, and watch the panel: the object should answer within a normal screen refresh.

One security note, because this is a security control and not a commissioning convenience: once the link passes, re-run the force test under the strictest mode you intend to ship with, keep that mode only if the panel still tracks, and record the final mode in the project documentation.

The Data Dictionary must be on before the rebuild #

The Data Dictionary option in the CPU project settings decides what the build stores: with it enabled, a full rebuild places the variable symbols into the application that lands on the CPU. The order is the whole fix, because enabling the option in a saved project does nothing to the running controller.

  1. Verify the option is checked in the saved project.
  2. Full rebuild of the project, then download, CPU in RUN — even though no logic changed.
  3. In Operator Terminal Expert, re-run the variable import against the PLC project so the panel's list matches the symbols now actually in the CPU.
  4. Rebuild and download the HMI application.

Decisive reading: the import shows the current Control Expert variable names, none flagged invalid.

The addressing check, with the arithmetic #

Even with the mode fixed, a subnet mismatch shows the same dead screen, and it is a two-minute check. The standard IPv4 rule: the network address is the bitwise AND of the address and the mask, and two stations deliver to each other directly only when those ANDs match.

Illustrative example, mask 255.255.255.0 (/24) on both stations:

  • CPU at 192.168.10.31: 192.168.10.31 AND 255.255.255.0 = 192.168.10.0
  • Panel at 192.168.10.50: 192.168.10.50 AND 255.255.255.0 = 192.168.10.0
  • 192.168.10.0 equals 192.168.10.0, so delivery is direct and no router is involved.
  • A panel at 192.168.11.50 gives 192.168.11.0, which does not equal 192.168.10.0: different network, and with no route configured every runtime request dies while a download that took another path still succeeds.

Decision: with a /24, the first three octets must match, and 10 against 11 fails here. Make the CPU IP in Control Expert equal the panel's target IP and mask before you blame the Security tab.

When some objects appear and others do not #

If values animate but some objects never appeared, the link is healthy and the fault is per-variable. Check each missing object:

  • its visibility and value animations reference a variable that exists in the imported list;
  • that variable's source is the device configured for this CPU, not an internal tag or an old device entry;
  • its type matches the Control Expert type — the IEC 61131-3 types BOOL, INT and REAL must line up on both sides.

One object working while the rest stay dead is binding; none working points back at Engineering Link Mode or the network path. The device and driver checks used when Operator Terminal Expert talks to a different controller are the same checks here — connecting Operator Terminal Expert to a third-party PLC lays them out.

Close the fault out with four readings, CPU in RUN:

  • Force the bound BOOL to 1, then 0 — the indicator toggles each time.
  • Write a value to a numeric variable from Control Expert — the panel shows the same value.
  • Press a panel button that writes a CPU variable — the change appears where you are watching in Control Expert.
  • Power-cycle the HMI — objects render and update with no re-download, which proves the link comes back on its own.

If the link passes all four and drops out hours later, that is a different fault: diagnosing intermittent HMI to PLC Ethernet comms hangs covers it.

Questions asked

Does Engineering Link Mode exist in Control Expert releases before v16.x?

The Security tab gate this fix targets is a v16.x feature; an older release simply does not show it, and the same symptom there points at the Data Dictionary build order or the tag bindings instead. On v16.x, read the tab first: it is a one-look check that either convicts the setting or clears it, and it costs nothing.

Is Filtered mode a good setting to leave on the CPU?

Filtered mode (https) is the documented middle option between Full Access and Enforced: the engineering link still works, carried over https, with restrictions on what passes. After commissioning, run the force test under the strictest mode the HMI must live with, keep that mode if the panel still tracks, and record it in the project documentation.

Do I have to download the HMI application again after the CPU-side rebuild?

Yes. The panel keeps its own copy of the symbol bindings, so after refreshing the variable import in Operator Terminal Expert you rebuild and download the HMI project as well. A CPU-side rebuild alone updates the symbols in the controller and leaves the panel working from its old list, which reads as a link that half works.

Can I check the CPU side without standing at the HMI?

Yes. With Control Expert online and the CPU in RUN, watch the bound variable while the logic writes it: if the value moves in the software but never on the panel, the program and its symbols are fine and the fault sits between the panel and the data-access gate — Engineering Link Mode, addressing, or the panel's device configuration. If the value never moves in Control Expert either, the fault is in the logic, not the link.

Keep reading

  • Troubleshooting

    Fix WinCC Professional runtime not connecting to the S7-1500

    WinCC Professional Runtime can start, load screens and raise no error while the HMI connection leaves through the wrong PC network adapter, because the access point selects the interface automatically. Disable that automatic option, assign the access point to the PLC-facing adapter in Set PG/PC interface, re-download the runtime and restart.

    HMI and touchscreens

  • Troubleshooting

    WinCC receives no data from an S7 PLC: trace the path

    There is no fixed interval at which an S7 PLC sends data to WinCC: WinCC polls each external tag at the acquisition cycle configured on that tag, and the CPU only answers. When no data arrives, trace the driver, the connection and the tag mapping in that order, beginning with the running project, and fix the connection before touching tag addresses.

    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