CompactLogix flashing I/O light after adding an Ethernet module

What the flashing I/O light means

The I/O indicator answers one question: are the configured I/O connections talking to the controller? It has three states.

Flashing green is the state to diagnose. One faulted device starts the flashing, and the light stays flashing until every configured connection responds, so the indicator hands you a count, never a name. The name comes from the controller's connection diagnostics, which list each configured connection with its status.

Symptoms and what each points to

• Flashing I/O light, processor in Run. A configured connection is down, and the program keeps solving, so go online with the line in its normal state.
• Device missing from the network, and it has power. Verify that the device has an IP address, for example 192.168.10.25 with subnet mask 255.255.255.0, and that the subnet masks put both ends on the same network; that subnet check is the first step in the controller vendor's EtherNet/IP troubleshooting application note.
• Device visible on the network, no data on the panel. The application connection is down. This is the classic fault behind a flashing I/O light after a new Ethernet module, and the connection list decides it.
• The module's own status LED flashing. On the module itself, a flashing status LED means it is powering up or has no connection to the controller. Read it as a device-side symptom, next to the controller's list.
• Flashing began right after an HMI firmware update. The panel side usually owns the fault; start with the HMI panel that stops communicating after a firmware update.
• The panel had live data and lost it while outputs held their last state. That is a communication timeout, and it has its own checklist: an HMI communication timeout with outputs holding state.

Example: a controller in Run, one new Ethernet module, an HMI that pings but updates nothing

Inputs, and where each comes from:

• Processor mode: Run, and the processor would not leave Run during the incident (the reported case).
• I/O indicator: flashing green (the reported case).
• Network: controller at 192.168.10.10, panel at 192.168.10.25, both on subnet mask 255.255.255.0, so both ends sit on one 192.168.10.0/24 subnet and the panel still pings (the reported case).
• I/O configuration: 1 Ethernet module newly added to the I/O configuration, plus 1 HMI panel that reaches the controller over that module's network (the reported case).
• Panel behavior: visible on the network, no live values on screen for at least 30 seconds of watching (the reported case).

The rule in words: on this CompactLogix family, a flashing green I/O indicator means the controller is in Run or Remote Run and one or more configured I/O connections are not responding. Online, the programming software lists every configured connection with its status and marks the faulted entries.

The arithmetic:

• Entries to account for in the connection list: 1 for the new module's I/O connection + 1 for the HMI panel's controller connection = 2 entries minimum.
• Faulted entries the diagnostics marked: 1, and it was the HMI panel's connection.
• Healthy entries: 2 - 1 = 1. The healthy entry belonged to the new module, so the module, its configuration and the Ethernet hardware all checked out. The fault was confined to the panel's path.

Result: correcting the panel's controller target and communication settings let the panel exchange data, and within 5 seconds of that connection coming up the I/O light went solid. That is how the reported case closed.

Decision: read the list before touching hardware. If the faulted entry is the panel's connection, fix the panel's target, driver and data references. If the faulted entry is the new module's, correct that module's address, slot assignment or keying; a keying setting of "exact match" against a module of a different revision holds the connection down. Replace hardware only for an entry that stays faulted after both endpoints verify.

Checks, in order

1. Record two separate observations, in under 2 minutes of reaching the panel: processor mode, Run or Program, and the I/O indicator state. Write the mode down first so the two never merge into one story.
2. Go online with the programming software. The connection status reads while the controller stays in Run, so the floor keeps its logic running while you diagnose.
3. Open the controller's connection diagnostics and write out every configured connection with its status. Each entry carries the configured device name and path.
4. Mark the faulted entries, and let the list pick the first endpoint you examine. The most recent configuration change is a hint, never the verdict.
5. For a faulted panel entry: check the target address the panel dials, the communication driver it uses, and that every tag the panel calls exists in the controller project. The test is watching 1 value change live on the screen over 30 seconds.
6. For a faulted module entry: match the configured address against the device, check the slot or rail assignment, and read the keying setting.
7. Apply 1 correction per download, then re-read the same diagnostics about 5 seconds after the download completes. One change at a time keeps the result attributable.

Make each download under your site's change control, with the crew that owns the line warned before you apply the fix.

The fix for each endpoint

Panel side. Point the panel's controller target at the controller's actual address, for example 192.168.10.10, set the driver to match the controller family, and create any tag the panel calls that the project lacks. When the panel is new to this controller and has never exchanged data, the same silence comes from a protocol mismatch; the checklist for replacing a PLC operator panel without a protocol mismatch walks that comparison.

Module side. Bring the configured address, the slot or rail assignment and the keying into agreement with the hardware in the rack. A status LED that keeps flashing on the module after a clean configuration points at the module or its cable, and that is where a spare module becomes the fastest test.

Network side. A network interface can report running while connections over it sit faulted; a ControlNet card that runs while its I/O connections fault shows the same split on a different network. The card's green light clears nothing in the connection list.

Recommendation: after any download that leaves the I/O light flashing, go online and read the connection list before you reseat or replace anything. Fix the endpoint the list names: the panel's target, driver and tags when the faulted entry is the panel's connection, and the module's address, slot or keying when the entry is the module's. Treat hardware as the last suspect, reserved for a connection that stays faulted after both endpoints verify.

When the light will not go solid

• The I/O indicator never lights at all: no project is loaded in the controller. Reload the project and re-read the indicator before diagnosing connections.
• One connection repaired, still flashing after 10 seconds: a second faulted entry hides behind the first repair. Re-read the whole list and clear the remaining entries one at a time.
• The list reads clean and the panel still shows no data: the fault sits in the panel's own application, its driver or its tag references. Recheck the panel side against the controller project.

A screen for the whole floor

If the crew needs a bigger view of line status than the operator panel gives, that is a separate purchase: a dashboard runs on a PC at a desk, and a signage display hangs on the wall and plays its own content, offline files or your own Android app. We build those displays, and the live factory data display: signage or a dashboard comparison lays out the choice.

Questions