HMI Command Not Reaching PLC

Walt — Simple Man Takeaway

A button on the screen is not a command until the PLC sees it.

Plain-English Summary

Use this flow when an operator presses a button or enters a value on the HMI and nothing happens in the live PLC logic, or the PLC rejects the command immediately.

R.E.A.L. firstRead-only firstCapture before changingReverse-trace failed conditionsTrap intermittent ghosts

First-Check Flow

1. Confirm the HMI object is valid

Verify the screen object is enabled, visible, and available in the current mode/security level.

2. Check tag binding and data type

Confirm the HMI tag, PLC address, alias, data type, and write permissions.

3. Confirm communication health

Check HMI-to-PLC connection status, network/device status, and stale-data indicators.

4. Watch the PLC tag live

Press the HMI command while online and see whether the PLC bit/value changes.

5. Check immediate reject/unlatch logic

If the command appears and instantly clears, reverse-trace the logic that rejects or unlatches it.

6. Trap disappearing commands

If the command appears too briefly to catch, use Ghost Busting™ to capture the command, reject condition, and active mode context.

Field Checks

HMI object enabled and visible
Operator permissions/security level confirmed
Tag address/binding checked
HMI-to-PLC communication status checked
PLC tag observed live while command is pressed
Mode, recipe, alarm, safety, and interlock conditions checked
Reject/unlatch logic reverse-traced if command appears briefly

Watch Out For

HMI writes to old/wrong tag
PLC immediately unlatches command due permissive failure
Security level disables command silently
Comms issue leaves HMI displaying stale data
Wrong data type or bit offset
One-shot command too brief to see manually

Reverse-Trace or Ghost Busting™?

Use Reverse-Trace Logic Solving™
when the failure is stable and visible live. Open the PLC program, monitor in RUN mode, chase only failed conditions, find the driving OTE, and repeat failure-to-failure.

Use Ghost Busting™
when the failure is intermittent, self-clearing, timing-based, or disappears before maintenance sees it. Select the suspect routine from the HMI and let the comparator trap expected-vs-actual mismatch every scan.

Find the failed result. Identify the blocking condition. Reverse-trace only what is failing. If the truth disappears, trap the ghost.

Related Calculators / SWAT Screens

Industrial Controller™ Ethernet/IP / Modbus TCP Device Count Readiness Industrial Controller™ Backup / Restore Readiness

Walt says STOP! - Safety First

Make these checks prior to proceeding.

Do not bypass safety, force outputs, defeat guards, or work live beyond your qualification and site procedure. If motion, stored energy, live electrical exposure, lockout/tagout requirements, or personnel inside guarded areas are involved, stop and follow the required safety process.