1769 CompactLogix Fault I/O Fault 16#0117 — Connection Failed

Overview

The Allen-Bradley 1769 CompactLogix I/O Fault 16#0117 (Connection Failed) indicates a Communication Connection Timeout or critical initialization failure. It signifies that the master CPU initiated a Common Industrial Protocol (CIP) connection request to a configured local or remote expansion module, but did not receive a valid handshake response within the configured time-limit parameters. The system is unable to pass cyclical data, leaving the corresponding module offline and often halting automation processor sequences to prevent unsafe operating conditions.

Symptoms

When a 16#0117 fault occurs, the control panel typically exhibits the following symptoms:

• I/O LED Status on CPU: The "I/O" status LED on the front display of the CompactLogix controller flashes red, indicating an active connection loss configuration error.
• Studio 5000 / RSLogix 5000 Diagnostics: Inside the Logix Designer controller organizer, a yellow caution triangle icon flashes next to the faulted module in the I/O Configuration tree.
• Module Properties Display: The Connection tab of the affected module's properties window displays the error message: Connection Fault: (16#0117) Connection Failed or Connection Request Error: Connection timed out.
• Controller State Change: Depending on your Studio 5000 system configurations, the controller may trip into a Major Recoverable Fault state, stopping code execution.
• Physical Module Indication: On localized distributed expansion networks (such as 1769-ADN or Point I/O drops), the network adapter or module's "Module Status" (MS) or "Network Status" (NS) indicator may flash red or turn completely unlit.

Possible Causes

Identifying the root cause of fault code 16#0117 requires looking at both physical link integrity and programming configurations. Common causes include:

1. Improper Backplane Bus Latching: The physical slide locking mechanism on 1769 expansion modules is not fully slid to the left (locked position), creating an open or high-resistance backplane connection link.
2. Missing or Misaligned End Cap (1769-ECR or 1769-ECL): A 1769-ECR (Right End Cap) or 1769-ECL (Left End Cap) is missing or damaged. The 1769 backplane bus operates as a high-speed parallel bus requiring terminal impedance matching; without an end cap, communication reflections disrupt data transmission.
3. Power Supply Distance Rating Exceeded: The physical distance rating of the target module exceeds its structural limitation relative to the system power supply (e.g., 1769-PA2 or 1769-PB4). Some 1769 analog and communication modules cannot be positioned more than 4 or 8 slots away from a power supply.
4. Electronic Keying Mismatch: The module configuration in the Studio 5000 project is set to "Exact Match" or "Compatible Module," but the hardware module installed has different firmware, series, or major revision levels, resulting in connection rejection.
5. Faulty Remote Network Settings: For remote I/O modules on EtherNet/IP (such as a 1734-AENT adapter), the IP address, subnet mask, gateway, or Requested Packet Interval (RPI) settings may be misconfigured, leading to dropped connection frames.
6. Backplane Contamination or Damage: Corrosion, metallic dust, or bent connection pins within the side-integrated expansion connectors can degrade high-speed logical signaling.
7. Inadequate System Bus Power: The combined load current (5V DC and 24V DC bus capacity) of all integrated modules exceeds the supply capacity of the active bank's power supply, causing intermittent micro-voltage drops.

Step-by-Step Troubleshooting

Step 1: Identify the Location of the Misfiring Module

Online with Studio 5000 Logix Designer, expand the I/O Configuration tree in the controller organizer. Determine if the module throwing the 16#0117 fault code is a local 1769 module physically attached to the CompactLogix controller backplane, or a remote distributed drop over an EtherNet/IP, ControlNet, or DeviceNet network.

Step 2: Perform Physical and Structural Checks (Local Bus)

If the faulted module resides on the local bus:

1. Power down the system completely. Working on live backplanes risks permanently damaging internal ASICs.
2. Check the visual alignment of all modules. Ensure they are correctly snapped onto the subpanel or DIN rail.
3. Locate the slide-lock lever on the top of each module. Verify that every lever is pushed completely to the left, capturing the adjacent module's bus connector.
4. Inspect the 1769-ECR (Right End Cap). Ensure it is mechanically locked in place. Inspect the metal contact fingers inside the cap and module connector ports for dirt, rust, or oxidation. Clean with an electrical contact residue-free solvent if needed.

Step 3: Audit Power Slot and Distance Compliance

Verify that the module has not compromised the "Power Supply Distance Rating" rules:

1. Cross-reference the module’s data sheet (e.g., 1769-IF4I, 1769-HSC, or 1769-OW16). Note its exact distance rating (most are 8, but some high-performance modules have a distance rating of 4 or 6).
2. Count the number of slots between the power supply module (e.g., 1769-PA4 or 1769-PB4) and the faulted module.
3. If the module exceeds this distance rating, reposition it physically closer to the power supply, or add an expansion power supply (e.g., 1769-PA2) with a bank-expansion cable (e.g., 1769-CRL3).

Step 4: Validate Electronic Keying Configuration

1. In Studio 5000, go offline and open the Module Properties for the target expansion card.
2. Note the Catalog Number, Series, and Firmware Revision.
3. Compare these parameters to the physical label affixed to the side of the module housing.
4. If there is a mismatch (e.g., programming expects Series B / Revision 3.001, but the physical card is Series A / Revision 1.005), temporarily set the electronic keying option in properties to Disable Keying.
5. Download the adjusted project to the controller. If the 16#0117 error resolves, the issue is an electronic keying validation failure.

Step 5: Diagnose Remote Network Failures (if on Remote I/O)

If the module is attached to a remote network interface adapter across EtherNet/IP:

1. Open a command line terminal on your PC and run a continuous test ping to the adapter's IP address: ping -t [IP_Address].
2. Look for packet loss or variations in response latency (jitter). System packet drop ratios over 0.1% can trigger 16#0117 timeouts.
3. Enter the module connection properties in Studio 5000 and check the RPI (Requested Packet Interval). If the RPI is set too fast (such as 1 ms or 2 ms) for standard non-managed network switches, increase the RPI parameter to 10 ms or 20 ms to observe stability changes.
4. Log into the Web Interface page of the adapter to review network port diagnostic statistics. Check for high numbers of "FCS Errors" or "Alignment Errors" which point to poorly shielded, damaged, or poorly structured Ethernet cabling.

Step 6: Step-by-Step Backplane Isolation Test

If physical issues are not solved and connection errors persist, perform an isolation test:

1. Power off the controller rack.
2. Disconnect all expansion cards, keeping only the CPU, the Power Supply, a single output/input module (the one experiencing problems), and the 1769-ECR end cap.
3. Power the system back on. Check if the controller establishes an error-free communication link to this single module.
4. If it succeeds, add modules back to the rack one by one, powering down between each change, until the fault returns. The last card added before the fault returns is likely the defective hardware component or the trigger for voltage drop limits.

Recommended Actions

• Establish Keying Best Practices: Use Compatible Module keying wherever possible. Always track revision sheets during plant maintenance cycles to avoid down-time after hot-swapping older module variations.
• Standardize Backplane Assembly Procedures: Instruct technicians to check slide locks during standard maintenance inspections. Add structural securing clips to DIN rails preventing lateral module slip, which physically breaks backplane logic contacts over time with thermal expansion/contraction.
• Check the Shielding and Grounding: Electrical noise (EMI) on the backplane can interrupt connection traffic. Ensure the DIN-rail is properly bonded to a low-impedance ground plane and that all high-voltage cabling is isolated from communication corridors.

Recommended Replacement Parts

If diagnostic isolating steps reveal hardware degradation, replace the broken items with the following Allen-Bradley parts:

Related Articles

• Troubleshooting 1769-ECR Right End Cap and Bus Termination Faults
• Understanding Studio 5000 Electronic Keying Configurations and Revision Discrepancies
• How to Calculate CompactLogix Power Supply Distance Ratings and Current Loading

FAQ

Q: Can I run a 1769 CompactLogix system without the 1769-ECR Right End Cap?

A: No. The CompactLogix system requires either a 1769-ECR (Right End Cap) or a 1769-ECL (Left End Cap) to terminate the high-speed parralel bus network. Operating without this termination cap causes transmission line reflections, leading to random bus errors and immediate 16#0117 connection failures across multiple modules.

Q: What is the difference between fault 16#0117 and 16#0114 in Logix Designer?

A: Fault 16#0117 is fundamentally a temporal time-out error; the controller initiated a connection request, but received no response back within the timeout parameters. Fault 16#0114 is an "Electronic Keying Mismatch" where physical communication occurs, but the module intentionally rejects configuration because its hardware series, revision, or catalog code doesn't match the software configuration parameters.

Q: How do I tell if the 16#0117 error is caused by a damaged module or a bad backplane bus connection?

A: Perform a localized bus isolation test. Isolate individual physical modules on the rack next to the controller and the power supply module. If the isolated module functions without a 16#0117 fault but fails once connected in its original position in a longer daisy-chain, the issue is likely a loose module slide lock or a broken system bus connection on an adjacent card.

Q: Will configuring a system with a too-low Requested Packet Interval (RPI) cause 16#0117 timeouts?

A: Yes. If the RPI is set too low (for example, under 5 milliseconds on a crowded 10/100 Mbps industrial network) the hardware can become overwhelmed with processing loads. When packets are delayed due to queue bottlenecks, the system records it as a lost connection and reports a 16#0117 fault.

Q: Does a 16#0117 fault put the PLC into a stopped/Major Fault state?

A: It depends on the module configuration settings. Under the Connection tab of the profile properties for each module in Studio 5000, there is a checkbox option labeled Major Fault on Controller if Connection Fails While in Run Mode. If checked, the PLC CPU will halt and enter Major Fault mode; if unchecked, the PLC remains in Run mode but sets system diagnostic tags to flag the down status of that I/O point.