Troubleshooting
Why an MER Download Shows No Live Data on the HMI
Short answer
The terminal runs the new MER against the communication configuration already stored on it, because the transfer skipped Replace Communications. Every tag returns Bad quality, so screens draw but show no live data. Re-download with Replace Communications checked, let the terminal reboot once, then prove the path with a heartbeat count.
On this page
The download completes, the runtime starts, every ping answers — and the screens still show no live data. The MER file is fine and the network is fine: the transfer left the terminal's stored communication configuration in place, so the new project runs against an old device shortcut that returns Bad quality for every tag. The fix is to re-download the MER with Replace Communications selected, let the terminal reboot once, and prove the path with a heartbeat count. In the case this page was written from — FactoryTalk View Studio v12 pushing a version 5.1 MER to a terminal on firmware 5.10.06.09 — that one checkbox was the whole fix. Below: what the symptom looks like, why the same project passes test runtime on the PC, the exact transfer setting, and the numbers that confirm the repair took.
What "no live data" looks like #
The runtime launches, navigation works, and every network check passes: a static IP matching the plant network, ping to the controller and the panel, both stations visible in RSLinx. What fails is data. Numeric displays show asterisks, string indicators show question marks, some objects draw as outlines because the runtime never received a value, and a diagnostics pop-up reports lost communication with the controller.
The failure can also stay quiet. Rockwell's support notes for FactoryTalk Linx document a shortcut referencing a wrong or unreachable controller leaving objects wireframed or data-less for extended periods — up to 8–10 minutes or longer — before the condition is reported. A panel that wakes up on its own after several minutes is still showing the stale-shortcut signature, not a recovering network.
Note what does not happen: the download itself succeeds and the runtime starts. That separates this fault from transfer-stage problems where an HMI is detected but the project download fails. Here the file landed; the tag path is what is broken.
| What you see | What the runtime is telling you | First check |
|---|---|---|
Numeric display shows ***** |
tag read returned Bad quality, no value | the comm path stored on the terminal |
String indicator shows ???? |
string tag read failed | the comm path stored on the terminal |
| Objects draw as outlines only | no data received; can persist 8–10 minutes or longer | the shortcut's target controller and path |
Why the panel runs but every tag reads Bad #
An MER carries more than screens and tags: it embeds the project's communication configuration, device shortcuts included. The transfer treats that cargo as optional. Without Replace Communications selected, the download writes the new project onto the terminal and leaves the terminal's stored communication setup — RSLinx Enterprise on this firmware generation, FactoryTalk Linx on newer ones — exactly as it was. The terminal then runs fresh screens against a stale shortcut, and every read comes back Bad. If you meet "download fine, runtime fine, no data" on this terminal family, the stored-path mismatch is the first suspect, whatever the media: Ethernet, serial or a routed path.
Test runtime explains the confusing part. Launching the project with the running-man test tool reads tags through the PC's own runtime communication configuration — the same one Studio used to build the MER — so it proves the project's paths while never touching the terminal's stored copy. One green test plus one blank panel is the signature of exactly that split.
A passing ping sits one layer below all of it: the network reaching both boxes says nothing about whether the terminal's comm server can resolve the shortcut inside the MER. The same layer split shows up elsewhere in the field, for instance in an HMI that pings successfully but cannot connect over the plant network.
Re-download with Replace Communications #
If this panel is the only operator interface for a running line, warn the floor first: the transfer and the reboot leave the HMI blind for a couple of minutes, so another means of stopping the machine has to be at hand.
- In Studio, confirm the project's Target and Runtime communication settings still resolve to the controller. In the documented case they were set correctly, so nothing needed rebuilding — verify, then move on.
- Start the ME Transfer Utility from the Studio project and select the terminal over Ethernet.
- Expand the transfer options and check Replace Communications. This is the setting that overwrites the terminal's stored comm configuration with the one embedded in the MER, device shortcuts included.
- Know the setting's edge before you make it a habit: the standard guidance is that you do not always want it checked, because the MER also carries network driver settings, and a project built for drivers different from the target terminal's would overwrite a working setup. If this MER crossed machines or sites, confirm the terminal's network settings and the shortcut path right after the transfer.
- Start the download and let it finish. Do not power-cycle the terminal mid-transfer.
- When the transfer completes, let the terminal reboot; if it does not on its own, cycle power once. The comm server binds the replaced configuration at startup, so the new path is not fully in force until that reboot — and the reboot is what makes the runtime start automatically at the next power-up.
- Open a screen with live values and run the count in the next section.
In the documented case, the terminal came up running with live data after exactly this sequence — no rebuild, no firmware change, one checkbox.
Prove the repair with a heartbeat count #
Put a number on it instead of eyeballing one screen. Use a controller heartbeat bit shown in a numeric display on the panel, and give that tag a 200 ms update interval in the project's communication settings — the value for this example, not a required setting. The arithmetic: updates per second = 1 s ÷ 0.2 s = 5 updates per second, so a 10-second watch should show 5 × 10 = 50 value changes.
Before the fix the count is zero: the display holds asterisks (Bad quality) or one frozen value. After the Replace Communications download and the reboot, the same 10-second count should land near 50, the runtime diagnostics list on the terminal should show Good quality with a climbing update count instead of communication faults, and any string tag that read ???? should show text again. If the number on the display never changes across the 10 seconds, that is a frozen value, not live data — the same verdict as before the download.
If Replace Communications does not fix it #
- Rebuild before blaming the panel: connect the PC to the same physical network as the controller, run test runtime there, and if it passes, reboot the PC, rebuild the MER and download the fresh file. Practitioners use this as a standard workaround for this exact symptom, and it clears stale state on the build side.
- Check the generation gap. The documented case pairs a v12 Studio with a terminal on firmware 5.10.06.09 — a comm client from the era when firmware 5.10 was state of the art, roughly fifteen years earlier. Studio v12 and its embedded FactoryTalk Linx can browse a modern controller that the client embedded in the terminal may not; if the controller is substantially newer than the terminal, the terminal's firmware support for that controller is the next thing to verify.
- A download that never starts at all is a different fault class, usually a version mismatch between the MER and the terminal rather than a comm-path problem; that case is walked through in fixing an HMI MER runtime version mismatch.
If the terminal's generation turns out to be the blocker and the repair is not worth it, the fallback is to replace the aging operator panel with industrial panel PCs.
Questions asked
Does Replace Communications change the terminal's IP address?
No. The checkbox replaces the communication configuration stored on the terminal — device shortcuts and the paths behind them — not the terminal's own network settings. The terminal keeps its IP address, subnet mask and gateway, which is why a panel that pinged fine before the re-download still pings after it. If the network side does drop after a transfer, suspect the driver settings the MER carried rather than the address fields.
Can a power cycle alone fix blank data after an MER download?
Sometimes. The communication server holds its configuration across downloads and rebinds it at startup, so a terminal that comes up blank occasionally connects after one more power cycle. That only works when the stored path was already correct but had not bound. If the stored shortcut belongs to another project or a removed controller, no number of reboots helps — the path itself has to be overwritten with Replace Communications.
Do two terminals running the same project share one comm path?
No. Each terminal stores its own copy of the communication configuration, and a plain download leaves each copy untouched. A project downloaded onto a second terminal without Replace Communications runs against that terminal's stored shortcut, which may point at a different controller or at none. Both panels can ping perfectly and still show no data; each needs its own replaced communication configuration to match the MER.
Should Replace Communications be checked on every download?
No. Check it when the terminal's stored path should change: the first download to a terminal, a project moved onto a different machine, or a shortcut edited in Studio. For repeated downloads of the same project to the same terminal it can stay off, and vendor guidance notes cases where it should stay off, because a MER built for different network drivers would overwrite the terminal's working driver setup.