Overview
This guide covers the most common EtherNet/IP failures seen in gateway and PLC integrations: missing EDS files, bad Assembly Object sizes, read/write mismatches, and CIP connectivity problems. The strongest internal support history is in Allen-Bradley and Allen-Bradley-adjacent PLC environments, so start by identifying the exact EtherNet/IP variant before changing packet-level details. Use it alongside the EtherNet/IP guide and the EtherNet/IP Integration Guide: EDS Files, Read/Write Configuration & Common Pitfalls.
Diagnostic Flow
- Confirm the device is reachable by IP and that the correct ports are open.
- Confirm whether the job uses explicit or implicit messaging.
- Verify the EDS file revision and scanner expectations.
- Verify Assembly Object instance numbers, byte counts, and direction.
- Validate read-only versus write-required points.
- Recheck whether the job is actually DATA_TABLE_READ / WRITE or PCCC rather than generic CIP.
Symptoms & Solutions
| Symptom | Likely Cause | Action | Related KB |
|---|---|---|---|
| Device browses but will not exchange I/O | Wrong assembly instance or size | Recheck input/output assembly numbers and total byte counts | Assembly Object |
| Reads work but writes fail | Point mapped as read-only or wrong service behavior | Reclassify points and review write-capable mapping rules | DATA_TABLE_READ / WRITE |
| Scanner cannot auto-configure the device | Missing or stale EDS file | Import the correct EDS revision and refresh the device profile | EDS File |
| No communication at all | IP, firewall, or port issue | Verify addressing and reachability on TCP 44818 and UDP 2222 | EtherNet/IP |
| PLC data layout is shifted or nonsensical | Byte or word packing mismatch in the controller tag layout | Recheck array structure and controller interpretation | CIP |
| The network path looks correct but the job still behaves inconsistently | The wrong EtherNet/IP variant was assumed at intake | Recheck whether the source expects DATA_TABLE_READ / WRITE or PCCC behavior | PCCC |
Configuration Issues
Check the EDS First
Many EtherNet/IP support cases begin with the wrong or missing EDS file. If the PLC or scanner cannot classify the target correctly, the rest of the configuration can look wrong even when the network is healthy.
Verify Assembly Direction
If the controller expects data in one direction and the gateway is configured for the other, values may appear static or writes may never land. Verify input assemblies, output assemblies, and any produced or consumed I/O direction assumptions.
Separate Read and Write Intent
If an integration must command setpoints or control outputs, confirm that those points are not configured as read-only. This is a recurring cause of “reads are fine, writes do nothing” failures.
Identify The EtherNet/IP Variant Up Front
Some projects are described generically as EtherNet/IP even though the real configuration burden sits inside a narrower Allen-Bradley-specific path.
Check whether the job depends on:
- DATA_TABLE_READ / WRITE behavior
- PCCC command-family assumptions
- A standard CIP assembly exchange with no Allen-Bradley-specific file semantics
[!WARNING] If the intake never identified the EtherNet/IP variant, do that before rewriting assemblies or captures. Internal support history shows this is often the real blocker.
Tools
| Tool | Type | Description |
|---|---|---|
| RSLinx Classic | Browser | Device discovery, browsing, and communication validation |
| EIPScan | Scanner | Explicit and implicit EtherNet/IP test utility |
| Wireshark | Packet Analyzer | CIP packet inspection and error confirmation |
Need Help?
If the network is reachable but the PLC still refuses to exchange data, capture the EDS revision, assembly numbers, expected byte counts, and one packet capture before changing the config repeatedly. That is usually enough to separate a scanner problem from a gateway mapping problem.