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

A PLC communication failure can stop an automated production line, disconnect an HMI, cause remote I/O to go offline, or prevent PLCs, drives, robots, and other industrial devices from exchanging data.

Communication problems are common in modern manufacturing systems because PLCs increasingly depend on industrial Ethernet networks and distributed devices.

A communication failure does not necessarily mean the PLC itself has failed. The actual problem may be caused by a network cable, Ethernet switch, IP address, communication module, PLC configuration, HMI settings, remote I/O, firmware mismatch, or electrical noise.

This guide explains how to troubleshoot common PLC communication problems systematically.

Related resource: PLC Repair: Common PLC Problems and How to Troubleshoot Them

What Is a PLC Communication Failure?

A PLC communication failure occurs when the PLC cannot properly exchange information with another device.

Common communication partners include:

• HMI panels

• Remote I/O

• VFDs

• Servo drives

• Robots

• Vision systems

• Safety PLCs

• Other PLCs

• Industrial PCs

• SCADA systems

• MES systems

• Barcode readers

• Industrial sensors

• Ethernet switches

Common symptoms include:

• HMI cannot connect to PLC

• Remote I/O goes offline

• PLC reports communication fault

• Drives show communication errors

• HMI displays stale or missing data

• PLC devices intermittently disconnect

• Network connection works and then fails

• Multiple machines lose communication simultaneously

• PLC cannot discover a network device

• Ethernet port shows no link

• Communication works after restarting the PLC or switch

The first objective is to identify which communication path has failed.

Common Causes of PLC Communication Problems

The most common causes include:

1. Damaged Ethernet cable

2. Loose network connector

3. Failed Ethernet switch

4. Incorrect IP address

5. Duplicate IP address

6. Incorrect subnet configuration

7. PLC communication module failure

8. HMI configuration problem

9. PLC hardware configuration problem

10. Remote I/O configuration problem

11. Firmware incompatibility

12. Communication protocol mismatch

13. Network overload

14. Electrical noise or EMI

15. Poor grounding

16. Power supply failure

17. Damaged Ethernet port

18. Incorrect PLC program or network configuration

19. Device failure

20. Network topology problem

PLC Communication Troubleshooting: Start With the Network Path

A typical PLC communication path may look like:

PLC → Ethernet Switch → Ethernet Cable → HMI

or:

PLC → Switch → Remote I/O → Sensors/Actuators

or:

PLC → Switch → VFD/Servo Drive

Instead of immediately replacing the PLC, troubleshoot the communication path one section at a time.

1. Identify Which Devices Are Offline

Before changing anything, determine the scope of the failure.

Ask:

• Is only one device offline?

• Is the HMI offline?

• Is all remote I/O offline?

• Are several PLCs offline?

• Are multiple drives offline?

• Is the entire machine network down?

This is one of the most important diagnostic steps.

One Device Offline

Possible causes:

• Device power

• Cable

• Device Ethernet port

• Device configuration

• IP address

Multiple Devices Offline

Possible causes:

• Ethernet switch

• PLC network port

• Network power supply

• Main communication cable

• Network configuration

• Network infrastructure

Entire Network Offline

Investigate:

• PLC

• Main switch

• Network power

• Network architecture

• Major communication module

• Network configuration

2. Check Device Power

Communication cannot work if the device is not powered.

Check the power status of:

• PLC

• HMI

• Ethernet switch

• Remote I/O

• VFD

• Servo drive

• Robot controller

• Industrial PC

Look at the device status LEDs.

A device that appears to have a communication problem may actually have a power-supply problem.

For example:

Remote I/O OFF → No network communication

Replacing the Ethernet cable would not solve the problem.

3. Check Ethernet Link LEDs

Industrial Ethernet ports commonly have link/activity indicators.

Depending on the equipment, LEDs may indicate:

• Link

• Activity

• Speed

• Network status

• Module status

If there is no physical link, check:

• Ethernet cable

• Connector

• Switch port

• PLC Ethernet port

• Device Ethernet port

If the link LED is completely inactive, investigate the physical layer before troubleshooting PLC software.

4. Check the Ethernet Cable

A damaged Ethernet cable is one of the simplest possible causes of a communication failure.

Inspect for:

• Broken cable

• Damaged connector

• Loose connection

• Excessive bending

• Crushed cable

• Oil contamination

• Coolant contamination

• Poor crimping

• Incorrect cable type

• Damaged locking tab

Industrial environments can expose cables to:

• Vibration

• Heat

• Oil

• Coolant

• Welding

• Mechanical movement

For moving applications, verify that the cable is appropriate for continuous flexing.

5. Check the Ethernet Switch

An industrial Ethernet switch can be a critical single point of failure.

If several devices suddenly lose communication, inspect the switch.

Check:

• Switch power

• Port LEDs

• Link status

• Network activity

• Error indicators

• Port configuration

• Fiber connections, if applicable

If multiple devices connected to the same switch lose communication simultaneously, the switch or its power supply should be investigated.

6. Check the PLC Ethernet Port

Inspect the PLC's communication port.

Check:

• Link LED

• Activity LED

• Network status

• Error status

• Connector

• Cable

• Communication module

If the network is healthy but the PLC's Ethernet port does not establish a link with a known-good device, the port or communication hardware may require further diagnosis.

7. Check the IP Address

Incorrect IP addressing is a common cause of Ethernet communication problems.

Verify:

• IP address

• Subnet mask

• Gateway

• Device name, where applicable

• Network configuration

For example:

PLC: 192.168.1.10

HMI: 192.168.1.20

Both devices must be configured appropriately for the network architecture.

An incorrect IP address can make a healthy device appear offline.

8. Check for Duplicate IP Addresses

Two devices using the same IP address can create intermittent or complete communication problems.

Symptoms may include:

• Communication works intermittently

• Device repeatedly disconnects

• Network connection changes unexpectedly

• HMI sometimes connects and sometimes fails

• PLC device appears online and then offline

Check the network configuration and device address list.

Maintain an accurate industrial network IP address inventory.

9. Check Subnet Configuration

A device can have a valid IP address but still be incorrectly configured for the network.

Verify the:

• IP address

• Subnet mask

• Gateway

• Network segment

For example, if the PLC and HMI are configured for incompatible network segments, communication may fail even though both devices are powered and physically connected.

10. Check the PLC-to-HMI Connection

A common manufacturing problem is:

HMI cannot communicate with PLC.

Start by determining whether the PLC itself is operational.

Check:

1. PLC status

2. HMI status

3. Ethernet link

4. IP addresses

5. HMI PLC driver/configuration

6. PLC communication settings

7. Network switch

8. Ethernet cable

If the PLC programming software can communicate with the PLC but the HMI cannot, the problem may be on the HMI configuration or communication path.

11. Check HMI Configuration

An HMI needs the correct communication configuration to communicate with the PLC.

Depending on the platform, verify:

• PLC IP address

• Controller name

• Communication driver

• Device type

• Network path

• Controller shortcut

• Tag configuration

• Connection settings

After replacing a PLC or HMI, these settings may need to be updated.

12. Check Remote I/O Communication

Modern manufacturing systems often use distributed I/O instead of connecting every sensor directly to the main PLC rack.

A typical architecture is:

PLC → Ethernet Network → Remote I/O → Sensors/Actuators

If remote I/O goes offline, check:

• Remote I/O power

• Ethernet connection

• Network switch

• IP address

• Device configuration

• I/O module status

• Network topology

• Communication diagnostics

If the entire remote I/O station is offline, investigate its power and network connection before troubleshooting individual I/O channels.

13. Check the Communication Protocol

Industrial devices may use different communication protocols.

Examples include:

• EtherNet/IP

• PROFINET

• Modbus TCP

• Modbus RTU

• EtherCAT

• OPC UA

• DeviceNet

• PROFIBUS

The PLC and connected device must use compatible communication settings.

A device may be physically connected to Ethernet but still unable to communicate because the application-layer configuration is incorrect.

14. EtherNet/IP Troubleshooting

EtherNet/IP is widely used in industrial automation systems.

When troubleshooting EtherNet/IP communication, check:

• Ethernet link

• IP address

• Device configuration

• Module status

• Network topology

• I/O connection status

• Connection errors

• Electronic keying/configuration

• PLC hardware configuration

For systems using an EtherNet/IP scanner and adapters, determine which device is the scanner/controller and which device is the adapter/target.

15. PROFINET Troubleshooting

PROFINET systems commonly require checking:

• Ethernet connection

• Device name

• IP configuration

• Hardware configuration

• Device status

• Controller configuration

• Network topology

• GSD/GSDML-related configuration where applicable

• Device diagnostics

If a PROFINET device is physically connected but not recognized by the controller, verify the device configuration and network identity.

16. Check PLC Hardware Configuration

After replacing or modifying hardware, communication faults can occur because the PLC configuration no longer matches the actual system.

Possible changes include:

• New communication module

• New remote I/O

• New drive

• New HMI

• New PLC

• New Ethernet switch

• Hardware relocation

• Firmware update

Verify that the PLC engineering project matches the actual hardware installed on the machine.

17. Check Firmware Compatibility

Communication problems can occur when connected devices have incompatible or unexpected firmware versions.

Check:

• PLC firmware

• Communication module firmware

• HMI firmware

• Remote I/O firmware

• Drive firmware

• Configuration software version

Before updating firmware on production equipment, follow the equipment manufacturer's procedures and maintain appropriate backups.

18. Check Communication Diagnostics

Modern PLC platforms typically provide diagnostic information.

Look for:

• Communication status

• Module status

• Error codes

• Connection timeout

• I/O connection failure

• Device diagnostics

• Network faults

Record the exact fault code before clearing the fault or restarting equipment.

The diagnostic information can significantly reduce troubleshooting time.

19. Check for Electrical Noise

Industrial Ethernet networks can be exposed to electrical noise from:

• VFDs

• Servo drives

• Motors

• Welding equipment

• Contactors

• High-current equipment

Symptoms of electrical interference can include:

• Intermittent communication

• Random device disconnections

• Communication retries

• Network errors

• Communication failures during machine operation

Investigate:

• Cable routing

• Shielding

• Grounding

• Network cable condition

• Separation between power and communication cables

• Connector quality

20. Check Industrial Network Topology

Network architecture can affect reliability and troubleshooting.

Common topologies include:

• Star

• Line

• Ring

• Tree

Determine whether the failure is isolated to a particular section of the network.

For example:

PLC → Switch A → Switch B → Remote I/O

If all devices downstream of Switch B are offline, focus troubleshooting around:

Switch B → its power → uplink → cables

This is much more efficient than troubleshooting every individual device.

21. Check for Network Overload

Some networks may experience problems when traffic becomes excessive or abnormal.

Potential causes include:

• Excessive broadcast traffic

• Incorrect network configuration

• Faulty device

• Network loops

• Excessive polling

• High-frequency data exchange

• Improperly configured devices

If communication becomes unstable as production equipment starts operating, monitor the network and investigate whether traffic or machine activity correlates with the failure.

22. Check the PLC Program

Not every communication problem is a physical network problem.

The PLC program may:

• Disable a device

• Reset a communication connection

• Change communication parameters

• Use incorrect tags

• Use incorrect device addresses

• Generate a timeout

• Enter a fault state

Review recent program changes when the communication failure began after an engineering change.

23. Check Recent Maintenance Changes

Ask:

• Was the PLC replaced?

• Was the HMI replaced?

• Was an Ethernet switch replaced?

• Was a cable changed?

• Was the machine moved?

• Was the PLC program modified?

• Was firmware updated?

• Was a new device added?

• Was electrical work performed?

A recent change can provide an important starting point for troubleshooting.

PLC Communication Troubleshooting Flowchart

Use this basic process:

PLC communication failure

↓

Are the PLC and device powered?

• No → Troubleshoot power

• Yes → Continue

↓

Is there an Ethernet link?

• No → Check cable, connector, port and switch

• Yes → Continue

↓

Are network addresses correct?

• No → Correct IP/network configuration

• Yes → Continue

↓

Is the device visible to the PLC?

• No → Check protocol, hardware configuration and device identity

• Yes → Continue

↓

Does PLC diagnostic show a communication fault?

• Yes → Investigate diagnostic code

• No → Continue

↓

Can HMI/software communicate with the PLC?

• No → Check network and communication configuration

• Yes → Continue

↓

Does the problem occur intermittently?

• Yes → Investigate cable, switch, EMI, power and network traffic

• No → Continue

↓

Check PLC program and device configuration

PLC Communication Troubleshooting Checklist

PLC Communication Failure: Symptoms and Likely Causes

Why Restarting the PLC Sometimes Temporarily Fixes Communication

A power cycle may temporarily restore communication.

However, a restart should not be considered a permanent solution.

If communication returns after restarting but later fails again, investigate:

• Overheating

• Network congestion

• Power instability

• Firmware/software issues

• Faulty communication hardware

• Electrical noise

• Network configuration

• Device failure

A recurring communication fault should be investigated for its root cause rather than repeatedly resetting the system.

When Should You Replace a PLC Communication Module?

Consider replacing a communication module only after verifying:

• Network cable

• Switch

• Power

• IP configuration

• Device configuration

• PLC hardware configuration

• Communication protocol

• Firmware compatibility

• Connected devices

A communication module may be defective when:

• The network connection cannot be established despite a      verified-good network path.

• The module reports a hardware fault.

• The communication port behaves abnormally.

• Known-good cables and devices fail to communicate through the      module.

• Diagnostic information indicates a hardware failure.

For obsolete PLC systems, repair or refurbished replacement may be an alternative to finding new hardware.

PLC Communication Repair vs. Replacement vs. Upgrade

Repair

Repair may be considered when:

• The communication module is obsolete.

• Replacement parts are difficult to source.

• The machine depends on discontinued hardware.

• A qualified industrial electronics repair company is available.

Replacement

Replacement may be appropriate when:

• A compatible module is readily available.

• The hardware failure is confirmed.

• Replacement can minimize downtime.

Upgrade

An automation network upgrade may be considered when:

• The PLC platform is obsolete.

• Network hardware is no longer supported.

• Communication failures are recurring.

• The existing network lacks required performance or diagnostics.

• The plant is migrating to a newer automation platform.

How to Prevent PLC Communication Failures

1. Maintain Network Documentation

Maintain an up-to-date record of:

• PLC IP addresses

• HMI IP addresses

• Remote I/O addresses

• Drive addresses

• Switches

• Network topology

• Communication protocols

• Device names

• Network drawings

2. Maintain PLC and HMI Backups

Keep current backups of:

• PLC programs

• HMI programs

• PLC hardware configurations

• Network configurations

• Drive parameters

• Robot configurations where applicable

3. Maintain Critical Spare Parts

Consider stocking:

• PLC communication modules

• Ethernet switches

• Network cables

• Communication adapters

• Remote I/O modules

• Power supplies

4. Protect Industrial Ethernet

Use appropriate:

• Industrial-rated switches

• Industrial Ethernet cables

• Connectors

• Cable routing

• Shielding and grounding practices

5. Monitor Recurring Communication Faults

Track:

• Frequency

• Device

• Time of occurrence

• Machine state

• Network location

• Error code

• Recent changes

Patterns can help identify the root cause.

When to Call an Industrial Automation Repair Company

Professional support may be appropriate when:

• Multiple PLC devices lose      communication.

• The PLC communication module is obsolete.

• Communication failures are intermittent.

• The network architecture is complex.

• The PLC program is unavailable.

• HMI communication cannot be restored.

• Remote I/O repeatedly goes offline.

• Industrial Ethernet troubleshooting requires specialized      equipment.

• Production downtime is significant.

A qualified automation technician, controls engineer or industrial network specialist can help diagnose the communication path and identify whether the problem is hardware, software or network-related.

How MaintenanceFixer Can Help

A PLC communication failure can require more than a replacement PLC part.

Manufacturers may need:

• PLC troubleshooting

• HMI troubleshooting

• Industrial Ethernet support

• Remote I/O troubleshooting

• PLC communication module repair

• Network troubleshooting

• VFD communication troubleshooting

• Servo communication troubleshooting

• Industrial switch replacement

• Obsolete PLC support

• Emergency automation service

MaintenanceFixer is designed to connect manufacturers with industrial maintenance suppliers, repair companies and technical service providers.

Manufacturers can describe the actual problem—for example:

"HMI cannot communicate with Allen-Bradley PLC."

or:

"Remote I/O randomly goes offline."

Potential suppliers and service providers can then respond with parts, repair options or technical assistance.

Need help with a PLC communication problem? Find industrial automation suppliers, repair companies and technical service providers through MaintenanceFixer.

Frequently Asked Questions

Why can't my HMI communicate with my PLC?

Check PLC power, HMI power, Ethernet connection, IP addresses, subnet configuration, switch status, HMI communication settings and PLC configuration.

Why does my PLC communication work and then fail?

Intermittent failures can be caused by damaged cables, loose connectors, electrical noise, power problems, duplicate IP addresses, network equipment problems or device overheating.

Why is my remote I/O offline?

Check remote I/O power, Ethernet connection, switch, IP/device configuration, communication protocol and PLC hardware configuration.

Can a bad Ethernet cable cause a PLC communication fault?

Yes. A damaged, loose, improperly terminated or unsuitable cable can cause complete or intermittent communication failures.

Can a PLC communication module be repaired?

Depending on the PLC platform and module, industrial electronics repair specialists may be able to diagnose and repair failed communication hardware.

Should I replace the PLC when communication fails?

Not necessarily. The problem may be outside the PLC, such as the Ethernet cable, switch, IP configuration, HMI, remote I/O or communication settings.

Why does restarting the PLC fix the communication problem temporarily?

A restart can clear a temporary fault, reset communication connections or restore a device to its initial state. If the problem returns, the underlying cause should be investigated.

Related PLC Troubleshooting Articles

Continue the MaintenanceFixer PLC SEO series:

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

2. PLC CPU Fault: Common Causes and Troubleshooting Guide

3. PLC Input Not Working: Causes and Troubleshooting Guide

4. PLC Output Not Working: Common Causes and Solutions

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

6. PLC Program Errors: Common Causes and Troubleshooting

7. PLC Program Backup: Why Manufacturing Plants Need a Backup      Strategy

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

9. PLC Analog Input Problems: 4-20mA and 0-10V Troubleshooting

10. PLC Overheating: Causes, Symptoms and Prevention