Troubleshooting guide

HMI not communicating with the PLC: the checklist that works on any brand

Nine times out of ten the machine is still running and the fault sits in the last meter of network or one configuration screen. The checklist below is brand-agnostic; the Siemens and Allen-Bradley traps are called out where they differ.

Put a screen on a phone meanwhile →

First: prove the PLC is alive (60 seconds)

Look at the controller itself — RUN light on, no fault LED — and ping it from a laptop on the same drop. Or faster: put the free LineKeeper app on the same network; it speaks EtherNet/IP, Siemens S7 and Modbus TCP. If the app sees the controller, your PLC and network are healthy and the fault is inside the HMI or its configuration — you've just cut the problem in half.

The universal checklist

CheckClassic failureBrand notes
1 · Cable and link lightsRe-patched switch, broken lock tab, flooded conduitAll brands equally
2 · IP and subnetDuplicate IP after a device swap; DHCP surprise after power cycleCheck from the HMI's own network settings, then ping from a laptop
3 · Driver / connection configPoints at the old controller, wrong rack/slot, wrong stationAB: the RSLinx Enterprise shortcut — dedicated PanelView guide. Siemens: connection partner, rack/slot. Modbus HMIs (Weintek, Delta): unit ID, station number
4 · CPU generation mismatchComms died the day the CPU was upgradedSiemens: S7-1200/1500 ship with PUT/GET disabled — enable it in CPU protection settings for classic connections. AB: old terminal firmware doesn't know the new Logix generation
5 · PLC program changesSpecific values error while others workRenamed tags (AB), moved or re-numbered DBs (Siemens) — and S7 optimized data blocks break absolute addressing entirely: the block must be non-optimized for classic HMI access
6 · Connection limitsComms drop when SCADA or a programmer connectsEvery controller caps simultaneous connections; count the clients

Reading the error language

  • Every display errors at once → transport problem: cable, IP, dead controller port, connection limit.
  • Specific values error, rest works → addressing problem: renamed tags, moved DBs, optimized blocks, wrong station on one device.
  • Worked until a hardware swap → identity problem: duplicate IP, changed rack/slot, protocol the new CPU speaks differently (PUT/GET, firmware generation).
  • Weintek "PLC no response" with a code → the code names the driver conversation that failed — station, IP or protocol mismatch on that specific device rather than the network: the dedicated Weintek guide.

If the HMI itself is the casualty

Comm hardware does die — a port killed by a nearby lightning event, a failed interface board. Before buying, check whether the panel is worth fixing at all: the black-screen triage covers the display-side faults, and for Allen-Bradley and Siemens units the PanelView timeline and Siemens replacement guide tell you whether you'd be repairing into a dead end.

Keep producing while you wait

Have the panel project export? Drop a FactoryTalk View, TIA Portal, Weintek or CSV export into our free HMI project converter — it runs in your browser, the file never leaves your PC, and every display becomes a page of buttons, indicators and values for the app, with the real tag names already in place.

Today, from a phone: the free LineKeeper app for iPhone and iPad speaks EtherNet/IP, Siemens S7 and Modbus TCP. On Allen-Bradley Logix it reads the controller's own tag list automatically; on S7 and Modbus you add the addresses you care about. Build a dashboard and an operator panel with start/stop buttons in about 15 minutes, mount a spare iPad in full-screen panel mode, and the operator has a screen before the first repair quote arrives. Reading is free; writes are a one-time unlock with confirmation and limit checks on every value.

Tag browser in the LineKeeper app: every tag of a ControlLogix or CompactLogix controller with live values and search, read straight from the PLC
The Logix controller hands over its whole tag list — live, searchable
Temporary operator panel in the LineKeeper app standing in for an HMI that lost communication with the PLC: start and stop push buttons, hold-to-run jog, speed setpoint and status lamps
The temporary panel: start/stop, jog, setpoints, status lamps
Guarded setpoint write in the LineKeeper app: allowed range shown and confirmation required before the value reaches the ControlLogix PLC
Writes are range-checked and confirmed before they reach the PLC
Free app · iPhone & iPad

The 15-minute temporary panel

Zero-config tag browser for Logix, drag-and-drop dashboard, operator panel, alarms — no changes to the PLC program.

Download on theApp Store
QR code — LineKeeper on the App StoreOn a desktop? Scan with your iPhone or iPad to get the free app.
See the app tour →

For the machine itself: the LineKeeper device — in development — is a self-contained 7″ or 10″ touchscreen built to live on the machine permanently — the same drag-and-drop screens, plus what a phone shouldn't carry:

  • Live view of every tag, refreshed twice a second — plus write access with a full audit log
  • Operator panel: start/stop, indicators, setpoints — hold-to-run buttons release safely
  • Stays useful after the repair: data logging, dashboards, machine diagnostics

Small hardware that helps while the panel is out

Amazon affiliate links — they never change the price you pay.

The plug-in LineKeeper device — a 7″ or 10″ touchscreen version of the same idea, with 24/7 logging — is in development ($1,290 planned, one-time). No preorders, no deposits; details on the pricing page.
FAQ

HMI-to-PLC communication questions

How do I tell whether the HMI or the PLC is at fault?

Put a second client on the same network drop — a laptop pinging the controller, or the free LineKeeper app reading it directly (EtherNet/IP, S7, Modbus TCP). If the second client sees the PLC, the controller and network are fine and the fault is the HMI's configuration or hardware. If nothing sees the PLC, work the network and the controller first.

Why did communication die right after replacing the PLC CPU?

Generation mismatch, almost always. Siemens S7-1200/1500 CPUs ship with PUT/GET communication disabled — classic HMI connections need it enabled in the CPU's protection settings — and optimized data blocks break absolute addressing. On Allen-Bradley, older terminal firmware may simply not know the new Logix generation, which surfaces as an unsupported-protocol warning.

Why does my Weintek HMI say “PLC no response”?

The EasyBuilder driver got no answer from the device the code points at: wrong station number or unit ID, wrong IP, wrong driver for the CPU generation, or the device genuinely offline. The error names the failing conversation, so check that one device's settings rather than the whole network.

Can I watch the PLC's data without the HMI?

Yes. The free LineKeeper app for iPhone and iPad reads Allen-Bradley Logix tag lists automatically over EtherNet/IP, and connects to Siemens S7 and Modbus TCP devices with the addresses you give it. It doubles as the fastest isolation test and as the operator's temporary screen while the HMI is being fixed.

Ask an engineer

Tell us about your panel

Free remote triage call — often the fault has a workaround that gets you producing before any hardware ships.