HMI Cannot Communicate With PLC: Troubleshooting Guide

When an HMI cannot communicate with a PLC, the machine operator may suddenly see an offline screen, communication error, frozen data, missing values, or incorrect machine status.

HMI-to-PLC communication problems are common in industrial automation systems. The cause may be something simple, such as a disconnected Ethernet cable, incorrect IP address, or loss of power. However, communication failures can also result from PLC configuration changes, network problems, firmware compatibility, damaged communication hardware, or electrical interference.

This guide explains how to troubleshoot an HMI that cannot communicate with a PLC, including Ethernet, IP address, network, communication settings, PLC configuration, and hardware problems.

What Does "HMI Cannot Communicate With PLC" Mean?

An HMI communicates with a PLC to read and write machine information.

Typical HMI functions include displaying:

• Machine status

• Sensor status

• Production counts

• Alarms

• Temperatures

• Pressures

• Motor speeds

• VFD status

• Servo status

• Recipe information

• Operator commands

When communication fails, the HMI may display messages such as:

• PLC Communication Error

• PLC Offline

• Connection Failed

• Device Not Responding

• Timeout

• Communication Timeout

• No Connection to Controller

• Controller Not Available

• Network Error

• Tag Communication Error

The exact message depends on the HMI and PLC manufacturer.

Common Causes of HMI-to-PLC Communication Failure

The most common causes include:

1. HMI or PLC power loss

2. Ethernet cable failure

3. Network switch failure

4. Incorrect IP address

5. Duplicate IP address

6. Incorrect subnet configuration

7. Incorrect PLC address

8. Incorrect HMI communication driver

9. PLC program or configuration changes

10. HMI tag/address problems

11. Communication module failure

12. Ethernet port failure

13. Firmware incompatibility

14. Industrial network problems

15. Electrical noise

16. Network congestion

17. Damaged connectors

18. Incorrect routing or network configuration

19. Recent hardware replacement

20. Missing or incorrect HMI project configuration

The key is to troubleshoot the communication path systematically rather than immediately replacing the PLC or HMI.

HMI-to-PLC Communication Path

A typical Ethernet-based system may look like this:

HMI

↓

Ethernet Cable

↓

Industrial Ethernet Switch

↓

Ethernet Cable

↓

PLC Ethernet Port

↓

PLC CPU

↓

PLC Program / Data

If the HMI cannot communicate with the PLC, the problem can exist anywhere along this path.

Step 1: Check HMI Power

Start with the simplest possibility.

Confirm that the HMI is:

• Powered ON

• Fully booted

• Not frozen

• Displaying the normal application

• Not showing a hardware fault

• Not repeatedly restarting

If the HMI itself is not operating correctly, communication troubleshooting should wait until the HMI hardware is verified.

Step 2: Check PLC Power

Verify that the PLC is powered and operating normally.

Check:

• PLC power LED

• CPU status

• RUN/STOP status

• Fault LED

• Communication LED

• I/O status

• Power supply status

If the PLC is in a fault or stopped state, the HMI may not operate correctly even though the Ethernet connection itself is working.

For PLC CPU troubleshooting, see:

PLC CPU Fault: Common Causes and Troubleshooting Guide

Step 3: Check the Ethernet Link LEDs

Most industrial Ethernet devices have link/activity indicators.

Check the Ethernet ports on:

• HMI

• PLC

• Ethernet switch

A missing link indication can point toward:

• Bad cable

• Loose connector

• Damaged port

• Switch problem

• Device power problem

If the link LED is ON but communication still fails, continue to the network configuration checks.

Step 4: Check the Ethernet Cable

Inspect the cable between the HMI and network switch or PLC.

Look for:

• Broken cable

• Loose connector

• Damaged RJ45 connector

• Incorrect cable termination

• Cable pulled from connector

• Excessive bending

• Mechanical damage

• Contamination

If appropriate, test with a known-good cable.

Do not assume that an Ethernet cable is good simply because it looks normal.

Step 5: Check the Industrial Ethernet Switch

If the HMI and PLC communicate through a switch, inspect the switch.

Check:

• Power

• Link LEDs

• Port activity

• Fault indicators

• Network connections

• Configuration

A failed switch can cause multiple devices to appear offline.

A useful diagnostic clue is:

If several devices lose communication at the same time, investigate the network infrastructure before replacing individual devices.

Step 6: Check the PLC IP Address

For Ethernet-based communication, confirm the PLC's IP address.

For example:

PLC: 192.168.1.10

The HMI must be configured to communicate with the correct PLC address.

An incorrect IP address can occur after:

• PLC replacement

• Network modification

• Hardware configuration change

• Software download

• Commissioning

• Maintenance work

Always verify the actual PLC IP address using the appropriate engineering software or device diagnostics.

Step 7: Check the HMI IP Address

The HMI also needs a valid network configuration.

Check:

• IP address

• Subnet mask

• Gateway when required

• Network interface

• Ethernet adapter configuration

For example:

HMI: 192.168.1.20

PLC: 192.168.1.10

The addresses must be configured appropriately for the network design.

Do not simply change IP addresses randomly. Document the original configuration before making changes.

Step 8: Check for Duplicate IP Addresses

A duplicate IP address can create confusing intermittent communication problems.

For example:

PLC: 192.168.1.10

Another device is accidentally configured as:

Device: 192.168.1.10

The network may behave unpredictably.

Possible symptoms include:

• Communication works intermittently

• HMI disconnects

• PLC appears online and offline

• Multiple devices report network errors

• Communication changes when another machine starts

If a duplicate IP address is suspected, investigate the complete network configuration.

Step 9: Check the Subnet

The HMI and PLC need appropriate network settings to communicate.

For example:

HMI

IP: 192.168.1.20

Subnet: 255.255.255.0

PLC

IP: 192.168.1.10

Subnet: 255.255.255.0

If the subnet configuration is incorrect, devices may not communicate as expected.

Network design varies by plant, so do not assume every PLC/HMI system uses the same subnet.

Step 10: Test Basic Network Connectivity

If the network architecture permits it, test connectivity between the HMI/PLC network devices using appropriate diagnostic tools.

A common PC-based test is a network connectivity test such as ping.

For example:

ping 192.168.1.10

If the PLC does not respond, investigate:

• PLC power

• Ethernet link

• Cable

• Switch

• IP address

• Subnet

• Network configuration

However, a failed ping does not by itself prove that the PLC is defective. Some devices or network configurations may block or not respond to ICMP traffic.

Step 11: Check the HMI Communication Driver

The HMI must use the correct communication driver or protocol for the PLC.

Depending on the equipment, this might involve:

• EtherNet/IP

• PROFINET

• Modbus TCP

• OPC UA

• Manufacturer-specific protocols

• Other industrial Ethernet protocols

If the HMI project is configured for the wrong driver, communication may fail even when the physical Ethernet connection is working.

Step 12: Check the PLC Connection Configuration

Open the HMI communication configuration and verify:

• PLC name

• PLC IP address

• Controller type

• Communication driver

• Connection path

• Rack/slot information where applicable

• Port configuration

• Communication parameters

The exact settings depend on the PLC and HMI platform.

Step 13: Check Rack and Slot Configuration

Some PLC systems require more than an IP address.

The HMI may also need the correct:

• Rack

• Slot

• Controller path

• CPU location

This becomes especially important after:

• PLC replacement

• Rack modification

• CPU replacement

• Remote I/O changes

• Hardware configuration changes

A system can have a working Ethernet connection but still fail to communicate because the HMI is addressing the wrong controller path.

Step 14: Check HMI Tags

Sometimes the HMI is connected to the PLC, but individual values are not working.

For example:

• Some tags work

• Some tags show errors

• Buttons do not work

• Alarm information is missing

• Certain data displays as zero

This can indicate a tag or address problem rather than a complete network failure.

Check:

• Tag name

• PLC address

• Data type

• Controller scope

• Array index

• Structure

• Data block

• Program changes

Step 15: Check PLC Program Changes

A recent PLC program download can cause HMI communication or data problems.

Ask:

What changed before the problem started?

Potential changes include:

• PLC program update

• HMI update

• New tags

• Deleted tags

• Changed addresses

• New data structures

• Hardware configuration change

• Firmware update

If the HMI project still expects an old PLC data structure, some tags may no longer work correctly.

Step 16: Check HMI Project Changes

The HMI application may have been changed independently of the PLC.

Check whether someone recently:

• Downloaded a new HMI project

• Changed PLC connection settings

• Changed tags

• Changed communication drivers

• Changed IP settings

• Changed screen configuration

• Updated HMI firmware

If the HMI was replaced, confirm that the correct project was downloaded to the new unit.

Step 17: Check Firmware Compatibility

A PLC or HMI replacement can introduce firmware compatibility issues.

Check:

• PLC firmware

• HMI firmware

• Communication driver version

• Engineering software version

• Hardware configuration

• Supported protocols

A hardware replacement should be checked against the machine's documented configuration before commissioning.

Step 18: Check Remote I/O

If the HMI communicates with the PLC but the PLC has lost remote I/O, the HMI may display machine alarms or missing data.

Check:

• Remote I/O status

• Network status

• I/O adapter

• Ethernet connections

• PROFINET devices

• EtherNet/IP devices

• I/O diagnostics

See:

PLC Communication Failure: Troubleshooting Ethernet, I/O and HMI Problems

Step 19: Check for Electrical Noise

Electrical noise can cause intermittent communication problems.

Investigate especially when the problem occurs during:

• VFD operation

• Servo movement

• Motor starting

• Solenoid activation

• Welding

• High-current switching

Check:

• Grounding

• Shielding

• Cable routing

• Ethernet cable condition

• Network hardware

• VFD installation

• Cabinet layout

See:

PLC Electrical Noise: How EMI Causes Intermittent PLC Problems

Step 20: Check Communication Diagnostics

Use the PLC and HMI engineering software to review diagnostic information.

Look for:

• Connection timeout

• Device offline

• Communication error

• Network error

• Protocol error

• Controller fault

• Tag error

• Connection retry

• Device unavailable

Record the exact error before resetting the system.

The diagnostic information can help distinguish between:

Physical network problem

and

Configuration/software problem

HMI Cannot Communicate With PLC Troubleshooting Flowchart

Use this basic sequence:

HMI cannot communicate with PLC

↓

Is HMI powered and operating?

→ No → Troubleshoot HMI power/hardware

→ Yes → Continue

↓

Is PLC powered and running normally?

→ No → Troubleshoot PLC

→ Yes → Continue

↓

Are Ethernet link LEDs active?

→ No → Check cable, port, switch, power

→ Yes → Continue

↓

Is PLC IP address correct?

→ No → Correct documented configuration

→ Yes → Continue

↓

Is HMI IP/subnet configuration correct?

→ No → Correct configuration

→ Yes → Continue

↓

Is communication driver correct?

→ No → Correct driver

→ Yes → Continue

↓

Is PLC connection/path correct?

→ No → Correct configuration

→ Yes → Continue

↓

Do all tags fail or only some?

→ All → Investigate network/connection

→ Some → Investigate HMI tags/program/data structure

↓

Does failure correlate with VFD/servo/motor operation?

→ Yes → Investigate EMI

→ No → Continue PLC/HMI/network troubleshooting

HMI Communication Troubleshooting Checklist

Symptoms and Possible Causes

Why Does HMI Communication Work After Restart?

This is a common troubleshooting clue.

If restarting the HMI temporarily restores communication, possible causes include:

• HMI software issue

• Communication connection timeout

• Network instability

• PLC communication overload

• Ethernet hardware problem

• Firmware/software issue

• Electrical interference

• Configuration problem

A restart may temporarily clear the symptom without fixing the root cause.

Therefore, record the fault information before restarting whenever possible.

Should You Replace the HMI or PLC?

Do not immediately replace either device.

First determine where the communication path is failing.

A useful diagnostic approach is:

HMI → Cable → Switch → PLC Ethernet Port → PLC CPU → PLC Program

Test each section.

If another known-good HMI can communicate with the PLC using the same network connection, the original HMI or its configuration becomes more suspect.

If multiple HMIs cannot communicate with the same PLC, investigate the PLC/network side.

Use controlled substitution tests whenever possible and document configuration before changing hardware.

Repair, Replacement, or Reconfiguration?

An HMI communication failure may require very different solutions.

Reconfiguration

Possible when the problem is:

• Wrong IP address

• Wrong subnet

• Wrong PLC address

• Wrong driver

• Incorrect controller path

• Incorrect HMI project

Repair

May be appropriate when:

• Ethernet port is damaged

• HMI hardware has failed

• PLC communication hardware has failed

• Network equipment is defective

Replacement

May be necessary when:

• Hardware is obsolete

• Repair is uneconomical

• Spare parts are unavailable

• Equipment has reached end of life

Upgrade

May be appropriate when:

• PLC/HMI is obsolete

• Network architecture needs modernization

• Replacement hardware is no longer compatible

• Cybersecurity or support requirements have changed

Preventing HMI-to-PLC Communication Problems

Manufacturing plants can reduce communication failures with a structured maintenance strategy.

Maintain PLC and HMI Backups

Keep current backups of:

• PLC programs

• HMI projects

• PLC hardware configurations

• HMI configurations

• Network configurations

• IP address lists

• Firmware information

See:

PLC Program Backup: Why Manufacturing Plants Need a Backup Strategy

Maintain Network Documentation

Document:

• PLC IP addresses

• HMI IP addresses

• Ethernet switches

• Network topology

• Remote I/O

• Communication protocols

• Cable routes

• Spare equipment

This can dramatically reduce troubleshooting time.

Control Configuration Changes

Document changes to:

• PLC programs

• HMI projects

• IP addresses

• Network equipment

• Firmware

• Hardware

An uncontrolled change can create a difficult-to-diagnose communication problem.

When to Call an Industrial Automation Specialist

Professional automation support may be appropriate when:

• Communication fails intermittently

• Multiple PLCs/HMIs are affected

• Network topology is complex

• Industrial Ethernet problems are recurring

• PLC or HMI firmware compatibility is uncertain

• PLC programs are missing

• HMI projects are missing

• The PLC is obsolete

• The HMI is obsolete

• EMI is suspected

• Production downtime is significant

A controls specialist can analyze the PLC, HMI, network, electrical system, and software configuration together.

MaintenanceFixer Can Help

Finding the correct technical resource can be difficult when an HMI suddenly loses communication with a PLC.

MaintenanceFixer is designed to help manufacturing companies find:

• PLC repair companies

• HMI repair companies

• PLC programmers

• Controls engineers

• Industrial automation technicians

• Ethernet/network specialists

• VFD specialists

• Servo specialists

• Industrial automation parts suppliers

• Emergency maintenance support

If your HMI cannot communicate with your PLC, you can use MaintenanceFixer to find a supplier, repair company, or technical service provider that matches the problem.

Frequently Asked Questions

Why can't my HMI communicate with my PLC?

Common causes include power problems, Ethernet cable failures, switch problems, incorrect IP addresses, incorrect communication drivers, PLC configuration changes, HMI configuration problems, firmware incompatibility, and electrical interference.

How do I check if my HMI and PLC are connected?

Start by checking device power and Ethernet link indicators. Then verify IP addresses, subnet configuration, network connectivity, communication driver, and PLC connection settings.

Can a bad Ethernet cable cause an HMI communication error?

Yes. A damaged or poorly terminated Ethernet cable can cause complete or intermittent communication failures.

Can two devices have the same IP address?

Yes, accidental duplicate IP addresses can occur. They can cause unpredictable or intermittent network behavior.

Can a VFD interfere with HMI-to-PLC communication?

Electrical interference from drives and other high-power equipment can contribute to communication problems, especially when network and signal cables are improperly routed or installed.

Why does my HMI work after restarting it?

A restart may temporarily clear a communication timeout, software condition, or network issue. It does not necessarily correct the underlying root cause.

Why can I communicate with the PLC from engineering software but not from the HMI?

This can indicate an HMI-specific configuration problem, such as an incorrect IP address, driver, controller path, tag configuration, or HMI project.

Why does only one HMI lose communication?

If other HMIs continue communicating normally, investigate the affected HMI, its Ethernet cable, network port, configuration, and connection settings before focusing on the PLC itself.

Final HMI-to-PLC Troubleshooting Checklist

Before replacing an HMI or PLC:

• Check HMI power

• Check PLC power

• Check PLC RUN/FAULT status

• Check Ethernet link LEDs

• Check Ethernet cable

• Check Ethernet switch

• Verify PLC IP address

• Verify HMI IP address

• Verify subnet

• Check for duplicate IP

• Verify communication driver

• Verify PLC connection path

• Check rack/slot where applicable

• Check HMI tags

• Check PLC program changes

• Check HMI project changes

• Check firmware compatibility

• Check remote I/O

• Check network diagnostics

• Check for electrical noise

• Record fault codes

• Document recent changes

• Test with known-good equipment when appropriate

An HMI that cannot communicate with a PLC is not necessarily a failed HMI or PLC. A systematic check of power → physical network → IP configuration → communication driver → PLC configuration → tags → diagnostics → electrical environment can help identify the actual root cause.

Related PLC Troubleshooting Articles

• PLC Repair: How to Diagnose a PLC That Will Not Power On

• PLC CPU Fault: Common Causes and Troubleshooting Guide

• PLC Input Not Working: Causes and Troubleshooting

• PLC Output Not Working: Common Causes and Solutions

• PLC Communication Failure: Troubleshooting Ethernet, I/O and      HMI Problems

• PLC Program Errors: Common Causes and Troubleshooting Guide

• PLC Program Backup: Why Manufacturing Plants Need a Backup      Strategy

• PLC I/O Module Failure: Symptoms, Causes and Repair Options

• PLC Analog Input Problems: 4–20mA and 0–10V Troubleshooting

• PLC Overheating: Causes, Symptoms and Prevention

• PLC Electrical Noise: How EMI Causes Intermittent PLC Problems