HMI display lags behind PLC values: find where the delay enters

Watch the value in two places

Put the machine in RUN and open the programming software's data view on two addresses: the analog input word, and the register the panel tag is supposed to show. Apply the load, hold it, release it. Record how fast each value moves in each direction: the input word, the program register, and the number on the screen. Note apply and release separately. In the case worked below, the release lag ran two to three times the apply lag, and that asymmetry is a clue worth keeping.

Three results cover every case:

• Input word and program register prompt, panel late. The delay enters at the panel: the tag address, the data format, the refresh period, the communication settings, or the cable, grounding and supply on the panel-to-PLC link. This is the outcome in the worked example.
• Input word prompt, program register late. The delay lives in the rungs between the input and the displayed register: a scaling rung executed only under a condition, a moving average or filter, or an intermediate word updated on some scans.
• Input word late in the data view. The problem is at the input: card configuration, input wiring, or the measurement. Terminal mode gives a quick look at the raw channel, but the PLC in this case ran no calculations there, so make the final call in RUN with the real load applied.

What each symptom points to

• Data view settles in a fraction of a second, panel trails by 5-6 s on apply. Panel side. Start at the tag address and the refresh period.
• Release lag 2-3 times the apply lag, here 15 s against 5-6 s. The displayed register itself decays slowly: an average, a filter, or a rung that writes only when a condition is true.
• Register and panel late together, input word prompt. The rungs between input and register own the delay.
• Intermittent communication timeouts alongside the lag. The link: cable type, routing, shield, ground, supply. Why an HMI shows an intermittent PLC communication timeout treats that version.
• Wrong numbers immediately, on every read, in both directions. A data format mismatch such as BCD against signed decimal corrupts the value on the first read; why an HMI panel shows nonsense numbers from a PLC BCD analog register covers that failure.
• Button presses on the same panel also feel slow. Panel processing load, often from heavy screens; why an HMI button response delay runs several seconds covers it.

Checks, in order

Work down the list one item at a time, and repeat the same apply-and-release test after each change so the numbers compare.

1. Tag address and format. Confirm the panel tag points at the register the logic writes, the word you watched in the data view, and that the tag's data format matches the PLC value. A tag aimed at a copy or an intermediate word displays a value that never catches up, whatever else you fix.
2. Tag refresh period. Panels read their tags on a cycle set per tag or per connection, and a change can wait nearly one full period before the panel polls it. One documented installation ran its tag refresh at 1 s where the application needed 100-200 ms; the maker's support documentation records the refresh being raised to 100-200 ms, so check the range your panel documents for the same tag. For a value people watch move, set the refresh at or below 200 ms.
3. Communication delay and timeout. One HMI family documents a communication delay setting spanning 0-255 ms with a default of 0 ms, and a timeout spanning 10-2000 ms. Compare yours against the values printed in your panel's manual before changing anything. If the delay was raised above its default to quiet a noisy link, set it back and fix the noise, because a raised delay holds back every response. Serial handshake timings, how long a line is held before transmitting, are millisecond-scale tuning and cannot reach seconds.
4. The link. Use the cable type the wiring standard calls for. Route it away from all other wiring. Shield it and ground the shield at one end. Ground the panel and the PLC to the same point.
5. The panel supply. The panel in this case was specified a dedicated 24 V DC supply rated 1.5 A. A shared or undersized supply shows its trouble in communications first. Measure the supply while the screen redraws under load; a sag there reads exactly like a comms fault.
6. What the screen carries. A screen loaded with heavy graphics slows tag updates on the same panel. Fix an HMI bitmap that slows PLC data updates shows that failure and its fix.

If the data view is the late value, go to the logic fix below instead. One safety rule before you change anything: if you cannot positively identify the address, the tag, or the wiring you are about to touch, stop and have the program reviewed before the machine returns to service.

Fix the side the comparison names

Panel side. Correct the tag address and format. Drop the refresh to 200 ms or less for any watched value; cutting it from 1 s to 200 ms removes up to 800 ms of worst-case wait. Return the communication delay to its documented default of 0 ms. Re-terminate the link: correct cable, routed clear of other wiring, shield grounded at one end, panel and PLC on one ground point. Give the panel its dedicated 24 V DC, 1.5 A supply. Retest after each change and watch the lag shrink in steps.

Logic side. Save a copy of the working program first. Find the rung that writes the displayed register and check its execute condition, any average or filter on the value, and whether the intermediate words feeding it update every scan. Hold off adding a timer or a filter to mask the delay until you know where the value stops moving promptly; a filter dropped in at the wrong point makes the register later.

Input side. Check the card's range and configuration against the 0-10 V wiring, then the input wiring and the measurement itself. If the input word stays slow in the data view, resolving analog update delays on an 8-channel analog input card goes deeper on the card side.

Example: a load-cell readout lags 5-6 seconds, 15 seconds on release

Inputs, and where each comes from:

• Two 8-channel analog input cards set to 0-10 V, reading load cells. The machine's configuration; the cards see the voltage change instantly.
• Apply lag 5-6 s, release lag up to 15 s. Measured against the load at the machine.
• Tag refresh period 1 s. The refresh one documented HMI ships with.
• Communication delay setting spanning 0-255 ms, default 0 ms. Documented for one HMI family.

The rule, in words. A polled tag waits at most one refresh period before the panel reads it. The communication delay adds at most its own maximum. Logic that writes the displayed register every scan holds the value at most one scan, and a compact PLC scans in the low milliseconds. So the slowest documented settings, added together, bound the delay the configuration can produce.

The arithmetic.

• Refresh at 1 s: worst-case wait 1000 ms.
• Communication delay at its documented maximum: 255 ms; at its default: 0 ms.
• Worst case from settings: 1000 + 255 = 1255 ms, about 1.3 s.
• Apply lag: 5 s - 1.255 s = 3.7 s, and 6 s - 1.255 s = 4.7 s, unaccounted for.
• Release lag: 15 s - 1.255 s = 13.7 s unaccounted for.

Result. With every documented setting at its slowest position, the configuration produces about 1.3 s. The machine shows 5-6 s on apply and 15 s on release. Between 3.7 and 13.7 s is being manufactured somewhere the settings do not reach: in the rungs between the input and the displayed register, or in the link's wiring, grounding, or supply.

Decision, with its threshold. Watch the displayed register in the data view through one apply and one release; the input word is already known to move instantly here. If the register settles well under a second and moves at the same speed in both directions, the delay sits on the panel side, and checks 2 to 6 above find it. If the register lags more than about 1 s, or shows the same asymmetry as the screen, a few seconds up and many seconds down, the delay is in the logic, starting at the rung that writes the register. The 15 s release against a 5-6 s apply is exactly the asymmetry to chase, and wherever it appears first, register or screen, is where the delay enters.

Recommendation

Recommendation: treat a panel that trails a prompt data view by seconds as a panel-side fault and fix in this order: tag address and format; tag refresh at or below 200 ms for any value people watch; communication delay back to its documented default of 0 ms; then the link, meaning the correct shielded cable routed away from other wiring, shield grounded at one end, panel and PLC on one ground point; then a dedicated 24 V DC, 1.5 A panel supply. Re-run the same apply-and-release test after each change. Edit logic only when the data view itself lags, and start at the rung that writes the displayed register.

Where the number goes once it is current

A value the shift can trust is worth placing where the shift actually looks. How to display a PLC counter value where operators can see it covers placing a live PLC value on a board the floor reads. One boundary worth knowing: a signage display plays files from its own storage and takes no live input from the PLC, so it cannot mirror this register. If the plant wants a second board, a target, a status line, a notice, fed by its own player, start from our display range.

Questions