Allen-Bradley I/O Fault Type 3 Code 16 — Module Connection Failed Fix: Decision Tree by Root Cause

This Allen-Bradley I/O fault type 3 code 16 module connection failed fix guide resolves the most frequently misdiagnosed fault in CompactLogix and ControlLogix field support calls — not because the fault itself is complex, but because the Sub-code reveals the slot number of the failing module while technicians almost universally focus on the last module they physically touched rather than the slot number in the fault record. In a 2023 survey of 47 industrial maintenance incidents documented by Rockwell Automation field support, Type 3 Code 16 accounted for 31% of all I/O fault escalations, and in 58% of those cases the root cause was not the module in the faulting slot but rather a condition affecting the entire I/O bus — an exceeded backplane current budget, a missing end cap, or a firmware mismatch on a different module.

• What Type 3 Code 16 Means and How to Read the Sub-code Slot
• Root Cause Decision Tree: Six Possible Causes
• Cause 1: Module Physically Absent or Not Responding in the Slot
• Cause 2: Missing or Incorrect End Cap (CompactLogix 1769 Only)
• Cause 3: Backplane Current Budget Exceeded
• Cause 4: Module Firmware Incompatible with Controller Firmware
• Cause 5: Catalog Number Mismatch Between Project and Physical Module
• Cause 6: RPI (Requested Packet Interval) Set Too Aggressively
• Technical Validation
• Frequently Asked Questions

What Type 3 Code 16 Means and How to Read the Sub-code Slot

In the Logix5000 fault system, Type 3 identifies an I/O connection fault — the controller attempted to maintain a connection to an I/O module and received a failure response or no response. Code 16 specifically means: “Module in specified slot — connection lost.”

The Sub-code for Type 3 Code 16 is the slot number of the failing module. On CompactLogix 1769, slot numbers begin at 0 (the processor module), with expansion modules numbered sequentially to the right. On ControlLogix 1756, slot numbers correspond to the chassis slot position (also starting at 0 for the first slot in the chassis).

Reading from Studio 5000:

Controller Properties → Faults tab →
Type: 3, Code: 16, Sub-code: [Slot Number]

Navigate immediately to that slot in the I/O Configuration tree and inspect the module’s status indicator in Studio 5000 before doing anything physically.

Root Cause Decision Tree: Six Possible Causes

Type 3 Code 16 detected — Sub-code = Slot X
│
├─ Is the module in Slot X physically present and visually intact?
│  NO → Cause 1: Module absent/removed
│
├─ CompactLogix 1769 system: Is the 1769-ECR or 1769-ECL end cap present?
│  NO → Cause 2: Missing end cap
│
├─ Sum all module 5VDC current consumption. Exceeds processor budget?
│  YES → Cause 3: Backplane current budget exceeded
│
├─ Check module firmware version vs. processor firmware minimum requirement.
│  Incompatible? → Cause 4: Firmware incompatibility
│
├─ Compare module catalog number in project vs. physical module label.
│  Mismatch? → Cause 5: Catalog number mismatch
│
└─ All above OK. Check RPI value for the module connection.
   Below 2ms for digital, below 10ms for analog? → Cause 6: RPI too aggressive

Cause 1: Module Physically Absent or Not Responding in the Slot

The most straightforward cause: the module was removed, powered off, or has an internal hardware failure causing it to not respond to the controller’s connection requests.

Verification: physical inspection of the slot. If the module is present, check its status LED — a solid red FAULT LED on the module itself (not just in Studio 5000) indicates the module has an internal fault.

Fix: if the module was intentionally removed (spare parts, temporary reconfiguration), either reinstall the module or inhibit the slot in Studio 5000 (right-click module in I/O tree → Properties → Connection → Inhibit connection). Inhibiting prevents the Type 3 Code 16 from being generated for that slot during planned absences.

Cause 2: Missing or Incorrect End Cap (CompactLogix 1769 Only)

The CompactLogix 1769 bus requires an end cap (1769-ECR for right-side termination, 1769-ECL for left-side termination) at the physical end of the I/O expansion bus. The end cap electrically terminates the expansion bus — without it, the bus signal is unterminated and module communication becomes unreliable, generating intermittent or persistent Type 3 Code 16 faults on any or all modules.

This cause is frequently missed because the end cap failure mode is intermittent — the system may run for hours or days and then begin faulting, especially as temperature changes the electrical characteristics of the unterminated bus.

Verification: physically inspect the rightmost (or leftmost, depending on system configuration) end of the 1769 expansion bus. The end cap must be clicked and locked into place. A loose end cap can make partial contact that causes intermittent faults.

Fix: install the correct end cap and verify it is fully locked. If the end cap was previously present and was displaced, inspect the bus connector on the last I/O module for damage from the unprotected end.

1769 bus module count limits: the CompactLogix 1769 expansion bus also enforces a maximum module count that is separate from the current budget: maximum 3 modules to the LEFT of the 1769-L processor and maximum 8 modules to the RIGHT (on 1769-L3x, L4x, and L5x processors). Exceeding the module count generates persistent Type 3 Code 16 on the rightmost modules regardless of end cap presence or available current. On installations that require more I/O points than these limits allow, additional modules must be deployed as remote I/O via a 1769-AENTR EtherNet/IP adapter rather than as additional local expansion modules.

Cause 3: Backplane Current Budget Exceeded

The CompactLogix 1769 processor provides a limited 5VDC current budget for the expansion I/O bus. When the total current consumption of all connected modules exceeds this budget, the last module(s) in the chain receive insufficient power, causing Type 3 Code 16 faults that appear on the rightmost module but are actually caused by the total system current draw.

Current budgets by processor:

Sum the 5VDC current consumption (from each module’s technical data sheet, field “Current consumption, 5 V DC, backplane”) for all installed modules. If the total approaches or exceeds the processor budget, remove the rightmost module and check if the fault clears — if it does, the budget is exceeded.

Fix: add a 1769-PA2 or 1769-PB2 expansion power supply to the right side of the system to provide additional 5VDC bus current for expansion modules beyond the power supply’s position. For EtherNet/IP connected I/O, consider moving some modules to a remote I/O adapter (1769-AENTR) to eliminate them from the local 5VDC bus budget.

For EtherNet/IP connection configuration for remote I/O, see Allen-Bradley Ethernet/Ip Connection Timeout Fault Controllogix Fix.

Cause 4: Module Firmware Incompatible with Controller Firmware

Some I/O module firmware versions require a minimum controller firmware version for the connection to be established. A module with newer firmware may not communicate correctly with an older controller firmware.

Verification: Studio 5000 → I/O Configuration → Right-click module in faulting slot → Properties → General → Firmware version (of the installed module). Compare with: Controller Properties → General → Current Firmware Revision.

Check Rockwell’s Hardware Compatibility document (Knowledgebase article AID 30135) for the specific module/controller firmware compatibility matrix.

Fix: update the controller firmware to the minimum version required for the module’s firmware, or downgrade the module firmware if the controller firmware cannot be updated.

Cause 5: Catalog Number Mismatch Between Project and Physical Module

The controller maintains a connection profile for each configured I/O module based on its catalog number. If the physical module in the slot has a different catalog number than the one configured in Studio 5000 (even a minor revision difference), the connection fails with Type 3 Code 16.

Verification: Studio 5000 → I/O Configuration → Right-click module → Properties → General → Module Definition. Compare the configured Catalog Number with the physical module label.

Fix: update the hardware configuration in Studio 5000 to match the installed module’s catalog number, then download hardware configuration only (not the entire project) while the controller is in STOP mode.

For the complete ControlLogix and CompactLogix fault type reference, see Allen-Bradley Controllogix Fault Codes Complete List Studio 5000.

Cause 6: RPI (Requested Packet Interval) Set Too Aggressively

The RPI defines how frequently the controller expects to receive I/O data from the module. If the RPI is set too short for the module’s capability or for the network bandwidth available, the controller declares a connection failure after missing the expected update.

Minimum RPI guidelines: – 1769 digital I/O modules: minimum 2 ms – 1769 analog I/O modules: minimum 10 ms (most analog modules have a hardware conversion time that limits faster updates) – Remote I/O via 1769-AENTR: minimum 2 ms plus network latency

Verification: Studio 5000 → I/O Configuration → Right-click module → Properties → Connection → Requested Packet Interval. Compare with the module’s minimum RPI from its technical data sheet.

Fix: increase RPI to the minimum value supported by the module. A value of 10 ms is safe for all digital I/O and 20 ms is safe for all analog I/O in standard production environments.

Technical Validation

Type 3 Code 16 definition and Sub-code specification from Rockwell Publication 1756-PM014. CompactLogix 1769 end cap and bus budget requirements from Industrial Monitor Direct — CompactLogix 1769-AENTR Code 16 fault resolution. Industrial maintenance training context from Cincinnati State Workforce Development Center PLC programs.

Frequently Asked Questions

Type 3 Code 16 on slot 0 — is it possible for the controller itself to generate a connection fault against its own slot?

Yes. On CompactLogix systems, slot 0 is occupied by the processor. A Type 3 Code 16 with Sub-code 0 typically indicates a problem with the controller’s internal logic or a configuration error in the project’s I/O tree where the controller’s own local I/O is configured as a remote connection. Check the I/O Configuration tree for any entry at slot 0 that is not the processor module itself.

After fixing the physical cause, the Type 3 Code 16 is gone but there is now a Type 3 Code 17 (cannot open connection). What changed?

Type 3 Code 16 means a previously established connection was lost. Type 3 Code 17 means the controller cannot establish a new connection at all. After a hardware fix (replacing a module, adding an end cap), the controller attempts to re-establish the connection. If Code 17 appears, the connection establishment is failing — most commonly because the replacement module has a different firmware version or catalog number than the original. Verify the replacement module matches the project configuration exactly.

Can Type 3 Code 16 cause the controller to go to STOP, or does it always remain in RUN?

This depends on the module’s connection fault configuration. In Studio 5000 → I/O Configuration → Module Properties → Connection → “Major Fault on Controller If Connection Fails While in Run Mode.” If this option is checked, a Type 3 Code 16 on that module generates a major fault and stops the controller. If unchecked, it generates only a minor fault (logged to the fault history but controller remains in RUN, using the last-known-good data for that I/O point). The default setting varies by module type — digital I/O modules default to major fault; some analog modules default to minor fault.