Resolving EtherNet/IP EDS File Mismatch on Omron PLC Systems

1. Problem Overview

Connecting an Omron programmable controller (CJ-series, NX/NJ-series, or CP-series) as an EtherNet/IP scanner/originator to a third-party slave/adapter frequently surfaces an EDS (Electronic Data Sheet) identity mismatch. A documented field case involves an Omron C5G-class controller attempting to communicate with a B&R Automation X20IF10D3-1 EtherNet/IP adapter (slave) over an industrial EtherNet/IP network. The scanner rejects the slave during the CIP identity phase because the EDS file registered in the controller's configuration contains incorrect VendorID, DeviceType, ProductCode, or Revision fields when compared to the live hardware identity returned by the adapter.

Symptoms manifest as a persistent "Connection timed out," "Identity mismatch," or "EDS file not found" diagnostic at the scanner, even though the IP link is established and the slave responds to ping. Standard remedies — restarting the scanner, cycling power on the adapter, regenerating the project — fail because the controller compares each candidate slave's CIP identity reply (Class 1, Instance 1, Attribute 1–4) against the EDS record stored in its local database before opening a Class 3 or Class 1 connection.

2. EtherNet/IP EDS File Architecture

Every EtherNet/IP device must publish a CIP Identity Object (Class ID 0x01, Instance 1). The Identity Object carries four mandatory attributes used for matching against the registered EDS file:

The EDS file is a plain-text ASCII or UTF-8 INI-style document distributed by the device vendor. When imported into a configuration tool — Sysmac Studio, CX-Configurator, RSNetWorx, Studio 5000 Logix Designer, or TIA Portal — the four Identity attributes are parsed and stored against the device's IP address. The scanner compares the live Identity Reply to the stored values whenever a connection attempt is initiated.

Standard EDS sections that the scanner consults during match include:

• [Device] — top-level device block, declares VendorID, ProductCode, Revision, DeviceType.
• [Device Classification] — declares the device's CIP class membership.
• [Assembly] — declares Input/Output assembly instances used for cyclic I/O.
• [Connection] — declares connection path, RPI, and trigger parameters.
• [Param] and [Group] — vendor-specific configurable parameters.

3. Root Cause: Vendor ID and Identity Field Mismatches

The B&R X20IF10D3-1 is an EtherNet/IP adapter module in the X20 distributed I/O family. Its CIP Identity is published by the embedded firmware; however, the official EDS file distributed by B&R may list a placeholder or generic VendorID when the adapter ships with a vendor-neutral default. Common deviations observed in field diagnostics include:

The scanner's matching algorithm has two modes:

1. Compatible mode — the scanner accepts any device whose major revision is greater than or equal to the EDS major revision. Minor revisions are accepted regardless.
2. Exact match mode — the scanner requires VendorID, ProductCode, DeviceType, and Revision to match exactly. This is the strict mode many Omron controllers default to.

If the EDS file was never opened at low level (raw text editor) and verified, placeholder values propagate through the import and become the reference baseline.

4. Required Tools and Prerequisites

Before editing the EDS file, gather the following:

• Original EDS file from the device vendor (B&R Automation Center download portal or product CD).
• Plain-text editor with no automatic encoding conversion (Notepad++, VS Code, vim). Avoid Microsoft Word.
• EtherNet/IP diagnostic tool capable of issuing a ListIdentity / Get_Attribute_Single request — examples include ODVA conformance utilities, Wireshark with the CIP dissector enabled, or Rockwell FactoryTalk Linx browser.
• Live identity capture from the target adapter obtained via the scanner's built-in network browser.
• Sysmac Studio (NJ/NX-series) or CX-Configurator FDT (CJ/CP-series), depending on controller family.
• Static IP configuration documented for the adapter, scanner, and management laptop.

5. Step-by-Step EDS File Editing Procedure

5.1 Capture the live CIP identity from the adapter

1. Connect the engineering PC to the same subnet as the B&R X20IF10D3-1. Default X20 IP is often 192.168.1.10 if set by rotary switches, otherwise DHCP.
2. Open Sysmac Studio, right-click the EtherNet/IP port under Configurations and Setup → EtherNet/IP, and select Edit EtherNet/IP Device List.
3. Click Browse Remote Device. The controller issues a CIP ListIdentity command (Service Code 0x63). The response populates the dialog with the live Identity Object attributes.
4. Record the displayed VendorID, DeviceType, ProductCode, and Major/Minor revisions exactly as shown (decimal and hex).

Alternatively, from the controller's Web server on B&R X20 modules (port 80/443), navigate to Diagnostics → EtherNet/IP → Identity to read the same attributes.

5.2 Open the EDS file at low level

Locate the .eds file shipped with the adapter. For B&R X20IF10D3-1, the file typically follows the pattern X20IF10D3-1.eds or similar. Open it in a plain-text editor. The [Device] section appears near the top and resembles:

[Device]
VendorID = 0;
DeviceType = 12;
ProductCode = 0;
MajorRevision = 1;
MinorRevision = 0;
VendName = "B&R Industrial Automation";
ProdType = "Communications Adapter";
ProdName = "X20IF10D3-1";

5.3 Correct the Identity attributes

Replace the placeholder values with the values captured from the live device. Example for the B&R X20IF10D3-1:

[Device]
VendorID = 106;        ; 0x006A — B&R Automation, ODVA-assigned
DeviceType = 12;       ; 0x000C — Communications Adapter
ProductCode = 1234;    ; replace with value read from live identity
MajorRevision = 1;     ; confirm via live identity
MinorRevision = 5;     ; confirm via live identity
VendName = "B&R Industrial Automation";
ProdType = "Communications Adapter";
ProdName = "X20IF10D3-1 EtherNet/IP Adapter";

5.4 Validate syntax and re-import

1. Save the EDS file with the original filename and the .eds extension. UTF-8 encoding without BOM is mandatory.
2. Open Sysmac Studio and use Tools → EDS File Management → Install to register the modified file.
3. The installer parses the [Device] block and reports any syntax errors. Common failures: missing semicolon, mismatched brackets, non-ASCII characters in quoted strings.
4. Rebuild the controller's EtherNet/IP device list and re-add the adapter from the network browser. The scanner now sees the corrected VendorID and accepts the match.

6. Field Verification and Diagnostics

After the corrected EDS file is registered, validate the connection using the following checks:

1. Identity match log: Sysmac Studio's EtherNet/IP Connection Diagnostics tab displays the live VendorID, DeviceType, ProductCode, Revision, and Status word. Confirm each field equals the EDS file.
2. CIP Status word (Instance 1, Attribute 5): Bits 0–7 must read 0; bit 8 indicates a minor recoverable fault. Anything else indicates a residual mismatch.
3. Connection status in the scanner tag namespace: In Sysmac Studio, the device node exposes an _ConnStatus or equivalent structure tag. A value of 0x00 indicates an established connection; 0x01 indicates connecting; 0x10 indicates timeout.
4. Wireshark capture: Filter on enip and inspect the CIP SendRRData packet sequence. The scanner should issue a Forward_Open immediately after the identity match without an intervening Get_Attribute_Single rejection.
5. Process data update: Map a test word from the B&R X20IF10D3-1 input assembly (typically Instance 100) to a tag in the controller and observe cyclic update. A live counter incrementing once per RPI confirms bidirectional traffic.

7. Common Error Codes and Symptoms

8. B&R X20IF10D3-1 Specific Configuration

The X20IF10D3-1 is a single-port EtherNet/IP adapter (slave) for the B&R X20 I/O system. Key parameters that interact with the EDS-driven handshake include:

Cross-reference Omron's official CJ-series EtherNet/IP Connection Guide for parameter-by-parameter wiring into the CJ1W-EIP21 or CJ2 CPU built-in EtherNet/IP port.

9. Omron EtherNet/IP Scanner Integration

For Omron controllers configured in Sysmac Studio (NJ501, NX102, NX-EIC202) or CX-Configurator (CJ2M-CPU3x, CP1H with CJ1W-EIP21), the integration path is:

1. Add the EtherNet/IP port under Configurations and Setup → Controller Setup → Built-in Port / Ethernet Port. Assign an IP address in the same subnet as the X20IF10D3-1.
2. Open the EtherNet/IP Device List in the right-hand toolbox. Right-click and choose Add Device.
3. Select the registered EDS for the X20IF10D3-1. If the device does not appear, the EDS was not registered correctly — return to Section 5.
4. Configure the connection: choose Input Assembly 100, Output Assembly 150, Configuration Assembly 105, and set the RPI to 10 ms (or 5 ms for high-speed motion cells).
5. Tag mapping: link the input assembly variables to data areas in the controller. Use AT specifications for direct memory access on CJ-series, or variables with _EIP_IN attribute on NJ/NX.
6. Transfer and go online: download the project, place the controller in Run mode, and monitor the _EIP_EtnOnlineSta (NJ) or A20200 (CJ) flag.

Refer to the Siemens TIA Portal documentation for WinCC Unified + Omron EtherNet/IP for HMI-side tag subscription once the PLC-side path is established.

10. Multi-Vendor Best Practices

• Maintain a vendor library. Store all EDS files in a version-controlled repository (Git, SVN). Tag each EDS with the device firmware version it was captured against.
• Never trust an EDS at face value. Always open it in a text editor and verify VendorID, ProductCode, DeviceType, and Revision are non-zero and consistent with the manufacturer before importing.
• Document live identities. Capture the Identity Object attributes of every EtherNet/IP device in the cabinet as part of commissioning. Store in a CSV alongside the EDS file.
• Avoid mixing EDS revisions. Two adapters of the same model but different firmware may have different EDS files; import each variant explicitly to prevent the scanner from picking the wrong default.
• Use exact-match mode deliberately. If your Omron controller is set to Exact Match, every firmware update on the slave requires an EDS update on the scanner. Track this in your change-management system.
• Test on a bench before deployment. Stand up the scanner and slave on an isolated switch with Wireshark capture before installing in the panel. Forward_Open and Forward_Close sequences can be reviewed offline.
• Back up the original EDS. Before any edit, save the vendor-supplied file under vendor_original_*.eds. Vendor support may reject your warranty claim if the EDS is non-factory.

11. Frequently Asked Questions