TL;DR
A failed I/O module shows a red fault LED and logs a fault code in Studio 5000. Note the slot number and module catalog number, go online with the PLC, inhibit the module, swap it, and re-enable it without modifying the program.
What you might see
- I/O module fault LED solid red
- Studio 5000 or Logix Designer shows module fault in the I/O tree
- connected field devices show no signal on that module
- controller fault log shows 4xxx series I/O fault code
Likely causes
Module component failure from age or transient surge damage to I/O circuitry
Over-voltage on a field wiring terminal exceeding the module's input rating
Electrostatic discharge during prior maintenance damaging the module
Water or condensation contact with the module connectors
Required tools
- Laptop with Studio 5000 Logix Designer (licensed, compatible version)
- Ethernet cable for PLC connection
- Replacement I/O module (exact catalog number match)
- Insulated screwdrivers
Safety first
- Field wiring on I/O modules can carry live process voltages (24V DC, 120V AC, or higher for analog modules). De-energize field circuits before handling wiring connectors.
- Always inhibit the module in Studio 5000 before hot-swapping. Removing an active module without inhibiting can cause a controller major fault and trigger safety-critical outputs.
Procedure
- 1
Open Studio 5000 Logix Designer, go online with the controller, and navigate to the I/O Configuration tree. Identify the slot number and the fault code for the failed module.[1]
- 2
Record the module catalog number from the tree and from the physical label on the module.
- 3
Check whether the module supports hot-swap by consulting the module manual. Many CompactLogix I/O modules support hot-swap without a controller fault.[1]
- 4
If hot-swap is supported: right-click the module in the I/O tree and select 'Inhibit Module'. Confirm the inhibit. This removes the module from the scan list.[1]
- 5
Remove the wiring connector from the module (disconnect block pulls off without removing wiring). Slide the module out of the chassis.
Warning: Even with the module inhibited, field wiring on the connector may carry live voltage from field devices. De-energize the field circuit before handling the wiring connector. - 6
Insert the replacement module of the exact same catalog number into the same slot. Seat it firmly.
- 7
Re-attach the wiring connector.
- 8
In Studio 5000, right-click the module and select 'Uninhibit Module'. The controller will re-establish communication. Confirm the module status LED shows green.
Sources
Allen-Bradley CompactLogix 5380 Controllers User Manual (Pub 5069-UM001), Rockwell Automation (Allen-Bradley)
Allen-Bradley CompactLogix 5380 Controllers User Manual, I/O module replacement and inhibit procedures (general)
View source
More guides for Allen-Bradley (Rockwell) CompactLogix 5380
How to replace the backup battery on an AB CompactLogix 5380 PLC
The CompactLogix 5380 battery alarm is straightforward: order the correct lithium battery, replace it with the controller powered on to preserve memory, and acknowledge the alarm. The battery typically lasts 5 to 7 years.
How to fix EtherNet/IP communication errors on an AB CompactLogix 5380
EtherNet/IP communication errors on a CompactLogix 5380 start with physical layer checks: cable, switch port, and IP address. Then check the Studio 5000 connection configuration for timeout and RPI settings.
How to recover from program corruption on an AB CompactLogix 5380
Program corruption shows as a major fault on power-up or a checksum error in the fault log. Restore from the latest validated ACD backup in Studio 5000 or from the SD card if auto-restore was configured.
How to diagnose sensor reading drift on an AB CompactLogix 5380 analog input
Analog input drift is usually wiring noise or a loose field terminal. Measure the sensor signal directly at the field terminal and compare to the PLC tag value. If they differ, the I/O module or scaling is the issue. If the signal itself is noisy, fix the cable shielding.
Stop fixing the same fault twice.
Dovient turns guides like this into your team's shared playbook, with AI that catches recurring issues before they break the line.