Fanuc R-30iB Ethernet/IP Scanner Setup for Omron NX-EIC202

1. Problem Statement

An EtherNet/IP scanner running on a Fanuc R-30iB / R-30iB Plus robot controller is configured to talk to an Omron NX-series EtherNet/IP Coupler Unit (catalog NX-EIC202). After all parameters are entered the connection reaches the PING OK state but never advances to RUNNING. The robot's I/O diagnostic screen shows the adapter instance exists, the heartbeat is alive, but the implicit (Class 1) connection repeatedly times out and re-opens. Output bits driven from the robot TP program never reach the NX digital output modules on the backplane, while input bits from the NX side are visible in the scanner's input table. The asymmetry — inputs work, outputs do not — is the diagnostic fingerprint of an incorrect Output Assembly Instance, an incorrect Minor Revision, or both.

The root cause is rarely a cable or IP addressing fault. The symptom appears even when:

• Subnets, default gateways, and node addresses (e.g. 192.168.0.3) are correct on both ends.
• The robot can ping the coupler with full reply from response.
• EDS-imported identity parameters (Vendor ID, Device Type, Product Code) match the coupler.
• The NX-EIC202 has been commissioned through Sysmac Studio and the I/O map is downloaded to the NX backplane.

This article documents the exact scanner-side configuration that resolves the failure, with field-verified values from working R-30iB ↔ NX-EIC202 installations. The values correct the commonly published defaults (Output Instance 150, Configuration Instance 0, Minor Revision 2) that originate from the NX-EIC202 firmware revision 1.0 EDS.

2. Hardware Identification: Omron NX-EIC202 Specifications

The NX-EIC202 is the EtherNet/IP backbone coupler of the modular NX-series I/O platform. It hosts the fieldbus interface and distributes power and the internal NX-bus to the slices (digital inputs, digital outputs, analog, safety, motion, etc.) mounted to its right.

Specifications are sourced from the official Omron product family page (NX-EIC202 Specifications) and the NX-series EtherNet/IP Coupler Unit User's Manual (W536).

3. EDS File Reference and CIP Identity Parameters

The Electronic Data Sheet (EDS) is the contract between scanner and adapter. Fanuc's robot-side configuration tool imports the EDS file delivered with the coupler (or downloaded from Omron's support portal) and pre-fills the CIP identity attributes. The four identity fields and one configuration field must match what the coupler advertises on the network, otherwise the scanner rejects the connection before any implicit messaging is attempted.

When importing the EDS into the Fanuc robot, the Major/Minor revision must be set to match the firmware of the actual hardware on the bench. A v1.2 NX-EIC202 reports Major 1, Minor 3; a v1.0 unit reports Major 1, Minor 2. Mismatching the minor revision is the second most common reason the scanner stops at PING and never transitions to RUNNING.

4. Scanner / Adapter Topology Rules

An EtherNet/IP network has exactly two roles for Class 1 (implicit) connections:

• Scanner — originates the connection, requests the data, holds the RPI timer. In this application the Fanuc robot is the scanner.
• Adapter — accepts the connection, consumes the scanner's O→T data, produces the T→O data back. The NX-EIC202 is always an adapter.

The scanner must therefore be configured with the appropriate EtherNet/IP scanner option installed and licensed on the robot controller. On Fanuc R-30iB and R-30iB Plus this is option R-784 (EtherNet/IP Scanner). Without this option the robot can act only as an adapter and cannot open Class 1 connections to remote I/O.

Verify before troubleshooting parameters:

1. On the teach pendant, press MENU → 0 (Next) → 4 (Status) → 2 (Version ID) → F4 (Config) and confirm that option R-784 (EtherNet/IP Scanner) is present.
2. Under MENU → 5 (I/O) → F4 (I/O Config) → EtherNet/IP, the configured device must show Type = Scanner. If it shows Adapter, the configuration is inverted.

5. Assembly Instance Configuration (Critical Correction)

This is the single highest-impact field on this integration. The original poster configured Output Assembly Instance as 150; this value is wrong for Fanuc scanners talking to NX-EIC202 revision 1.2. The output assembly is consumed by the adapter, and the NX-EIC202 firmware 1.2 expects an Output Instance of 148, not 150.

The instance numbers are defined by the NX-EIC202 EDS revision 1.2. The Input/Output column heading in the Fanuc configurator refers to the assembly from the scanner's viewpoint: Input means the scanner receives it, Output means the scanner transmits it. This matches the CIP convention. A common mistake is to swap these when reading the Fanuc menu, which produces exactly the input-works / output-does-not symptom described in the source.

6. Firmware Revision Differences: v1.0 vs v1.2

Omron shipped two production firmware revisions of the NX-EIC202 relevant to this application:

Omron's documentation describes revision 1.2 as containing improvements specifically targeting third-party (non-Sysmac) EtherNet/IP master interoperability. If the unit on the bench is revision 1.0, request an RMA from the Omron distributor and order the v1.2 replacement, or, if a v1.2 cannot be sourced, accept that only the input half of the connection will operate reliably.

7. Fanuc R-30iB Controller Port Selection

Two physical Ethernet ports are present on the R-30iB / R-30iB Plus mainboard:

• Port 1 (CD38A / Ethernet) — reserved by Fanuc convention for EtherNet/IP connections to Allen-Bradley / Rockwell PLCs.
• Port 2 (CD38B / Ethernet #2) — required by Fanuc's Ethernet/IP manual (chapter 2, section 2.3) for all other EtherNet/IP masters and adapters, including Omron, Siemens, ABB, and Yaskawa products.

Even with the network configuration identical between the two ports, plugging into Port 1 when the peer is an Omron NX-EIC202 typically produces a connection that opens then closes within a few seconds, because the port-1 default route table entries include routes that conflict with the scanner's connection management. Plugging the same cable into Port 2 — with no other changes — produces a stable RUNNING connection.

8. Complete Configuration Parameter Reference

The following table consolidates the field-verified scanner-side parameter set for a Fanuc R-30iB Plus with EtherNet/IP scanner option R-784 talking to an Omron NX-EIC202 with firmware 1.2.

9. Step-by-Step Configuration Procedure

1. Verify scanner option. From the Fanuc TP: MENU → 0 (Next) → 4 (Status) → F4 (Config). Confirm option R-784 EtherNet/IP Scanner is ordered and active.
2. Identify the NX-EIC202 revision. Read the label on the side of the coupler or use Sysmac Studio to confirm firmware. If the unit is revision 1.0, swap for v1.2 before proceeding.
3. Set the coupler IP address. Either through Sysmac Studio (USB port on the front of the NX-EIC202) or via the rotary switches (if present) — set to a static address on the same subnet as the robot Port 2 (example: 192.168.0.3).
4. Import the EDS. From MENU → 5 (I/O) → F4 (I/O Config) → EtherNet/IP → F2 (Add Device) → EDS Import. Point to the EDS file matching the revision 1.2 firmware. Confirm Vendor 47, Device Type 12, Product Code 1660 are auto-filled.
5. Create the scanner device. F2 (Add Device), set the IP address, leave the connection type as Scanner.
6. Apply the correct assembly instances. Override the default Output Instance from 150 to 148. Override Configuration Instance from 0 to 199. Keep Input Instance at 100.
7. Set identity parameters. Force Major = 1, Minor = 3. Vendor, Device Type, Product Code are pre-filled and must match exactly.
8. Configure I/O sizes and RPI. Set Input/Output sizes to match the sum of the NX slices attached (example: 6 bytes in / 4 bytes out). RPI = 32 ms.
9. Set transport and header options. UNICAST transport. O→T header = Run/Idle. T→O header = Modeless. Quick Connect = FALSE. Alarm = STOP. Reconnect = True. Timeout Multiplier = Default.
10. Save and cycle the connection. F5 (Apply) → F8 (Reset Connection) on the EtherNet/IP menu.
11. Plug the fieldbus cable into Port 2 of the robot. Do not use Port 1. Verify the link LED is solid green on both ends.
12. Monitor the connection state. MENU → 5 (I/O) → F1 (I/O Status) → EtherNet/IP. The state should transition from PING to RUNNING within 1–2 RPI cycles (32–64 ms).

10. Verification and Diagnostics

After applying the corrected configuration, perform the following four checks before declaring the integration successful.

10.1 Connection state

On the Fanuc TP I/O Status screen, confirm the NX-EIC202 entry shows RUNNING with a non-zero Packets Sent and Packets Received counter that is incrementing each RPI. A steady RUNNING state must persist for at least 5 minutes without dropping back to IDLE or PING.

10.2 Input path

Force an input bit on a digital input slice attached to the NX-EIC202 (e.g. short the input to 24 VDC). Within 32 ms (1 RPI), the corresponding input register in the robot's I/O table must show the bit transition. Confirm the mapping in MENU → 5 (I/O) → F2 (I/O Mapping).

10.3 Output path

From a TP program, set DO[1] = ON. Within 32 ms, the LED on the corresponding NX digital output terminal must illuminate. If the LED illuminates but the field-side device does not switch, the problem is downstream of the NX slice (wiring, 24 V supply, sinking vs sourcing) — not EtherNet/IP.

10.4 Error counters

On the EtherNet/IP menu press F6 (Detail). Confirm that Connection Timeouts, ForwardOpen Failures, and CRC Errors are all zero after 30 minutes of stable RUN. Any non-zero count points to either a flaky cable, an IP address conflict on the subnet, or a switch port with duplex mismatch.

11. Troubleshooting Matrix

12. Network Topology Diagram

13. Frequently Asked Questions