Troubleshooting Yaskawa A1000 EtherNet/IP Connection to Omron CJ2

1. Problem Overview

Field installations that pair a Yaskawa A1000 drive (or A1000-family equivalent) carrying the SI-EN3/V EtherNet/IP option with an Omron CJ2-series PLC using the built-in EtherNet/IP port (CJ2M-CPU3x / CJ2H-CPU6x-EIP) frequently stall at the CIP connection phase. Typical symptoms observed in Omron Network Configurator for EtherNet/IP:

• Target device registers in the EDS browser and responds to PING or the web server (HTTP, port 80) of the option card.
• NS (Network Status) LED on the SI-EN3/V remains solid red or flashes red/green, never reaching the steady green required for an established CIP Class 1 connection.
• Connection attempt with Assembly 101 (Input) and 151 (Output) at an RPI of 50 ms (or any RPI between 10 ms and 100 ms) fails with CIP error code 0x01 (Connection failure) returned in the Network Configurator monitor screen.
• No connection object appears in the EDS Compare tool after the configuration download.

The drive otherwise responds to standard TCP services, and Wago 750-341 or Rockwell Logix controllers can communicate with other EtherNet/IP nodes on the same subnet. The fault is therefore localised to the Yaskawa-to-Omron path and is almost always attributable to one of two root causes:

1. Product Code mismatch between the EDS file registered with the Omron Configurator and the actual Product Code returned by the drive's Identity Object (Class 0x01, Instance 1, Attribute 1).
2. SI-EN3/V firmware bug in early option-card revisions (firmware 220.x and earlier) that prevents CIP Class 1 connection establishment with non-Yaskawa scanners.

2. Root Cause Analysis

2.1 CIP Identity Object and EDS Matching

EtherNet/IP scanners (including the Omron CJ2 EIP scanner) verify, before opening a Class 1 connection, that the device responding to the Identity Object Get_Attribute_Single request matches the EDS file the configuration was built from. The four matching fields are:

• Vendor ID (Attribute 1): Yaskawa = 0x01A9 (425 decimal). Always constant for Yaskawa drives.
• Device Type (Attribute 2): AC Drive = 0x02.
• Product Code (Attribute 3): A drive-specific value encoded as 0x8F## (YEC / Yaskawa Electric America A1000) or 0x90## (YEA / Yaskawa Europe Asia A1000), where ## is the decimal value of drive parameter o2-04 (kVA selection / model code).
• Major / Minor Revision (Attributes 4 / 5): Bound to the option firmware version.

If Product Code in the EDS does not equal the value the SI-EN3/V option reports from NVS, the Omron scanner rejects the connection and the NS LED remains red. This is by design: it prevents a PLC project built around a different drive rating from accidentally controlling the wrong hardware.

2.2 Why the Mismatch Happens

Yaskawa issues regional drive variants under different model-number prefixes:

Prototype or pre-production units shipped to integrators often ship without an EDS on the official Yaskawa EtherNet/IP product page. Engineers fall back to an EDS borrowed from a sister SKU (for example AU2A0004_UTC000280__v1.02.zip) where the Product Code is set to 0x9062 (a generic 0.4 kW AU2A0004 entry), but the drive under the panel reports 0x8F62 (an AA2A0004 unit) because o2-04 = 62. The 0x8F vs 0x90 high byte is the failure point.

2.3 SI-EN3/V Firmware Defect

Independent of the Product Code, the SI-EN3/V EtherNet/IP option card (Yaskawa part number SI-EN3/V, option-attachment manual AN.AFD.09) had a known regression in early firmware that caused the CIP Forward_Open service to time out against Omron CJ-series scanners. Confirmed versions:

3. Yaskawa A1000 Hardware Reference

The A1000 (CIMR-AU#A / AA#A) is a general-purpose flux-vector drive. For EtherNet/IP connectivity the SI-EN3/V option is mounted on drive CN5 and parameterised as follows (verified against the A1000 option installation manual TOBPC73060058):

To read o2-04 from the keypad: MENU > 4 (Monitor) > U1-25 (software version) / o2-04 (drive model code) or simply MENU > o2-04 directly via the parameter group menu.

4. EDS File Product Code Requirements

4.1 Product Code Encoding

Yaskawa encodes the EtherNet/IP Product Code as a 16-bit word combining the regional prefix and the model code from o2-04:

Product Code (Attribute 3) = 0x8F00 | o2-04      // YEC A1000 (AA prefix)
Product Code (Attribute 3) = 0x9000 | o2-04      // YEA A1000 (AU prefix)
Product Code (Attribute 3) = 0x9100 | o2-04      // YEA V1000 / selected models

For the documented example drive AA2A0004 with o2-04 = 62:

4.2 Common Product Codes by Drive Frame

5. Procedure: Editing the EDS Product Code

5.1 Prerequisites

• EDS file AU2A0004_UTC000280__v1.02.zip (or the regional equivalent matching the drive prefix).
• Omron Network Configurator for EtherNet/IP (bundled with CX-One / CX-Integrator).
• Yaskawa DriveWizard Plus or the A1000 keypad to read o2-04.
• Plain-text editor capable of saving ISO-8859-1 (Notepad++ recommended).

5.2 Step-by-Step

1. Read the actual Product Code the drive reports. Use the SI-EN3/V web interface (default http://192.168.1.20) and open Diagnostics > Identity Object, or use the Omron Explicit Message tool against Instance 1, Attribute 3 of the drive. Record the value.
2. Confirm the regional prefix on the drive nameplate: AA#A#### = YEC (0x8F), AU#A#### = YEA (0x90).
3. Extract the EDS ZIP to a working folder. Open the .eds file in Notepad++.
4. Locate the [Device] section. The line will read:

   ProductCode = 36962   ;  0x9062  - AU2A0004 (YEA)

   Replace the decimal value (and the hex comment) with the correct one for your drive. For an AA2A0004 with o2-04 = 62:

   ProductCode = 36706   ;  0x8F62  - AA2A0004 (YEC)

5. Also update the Catalog, Description, and Product Name fields in the same section so the new device can be distinguished in the EDS catalog.
6. Save the EDS file with Encoding: ISO-8859-1. Saving as UTF-8 will scramble the CP/CS comment markers and the Network Configurator will reject the file.
7. Re-register the EDS in Omron Network Configurator: EDS File > Install and select the modified .eds. Overwrite when prompted if the catalog already contains the original.
8. Re-import the drive into the configuration. The Identity Object now reports the matching Product Code and the CIP Class 1 connection opens.

5.3 Sample EDS [Device] Block After Edit

[Device]
  VendorID             = 425 ;  0x01A9  Yaskawa Electric America
  VendorName           = "Yaskawa Electric America"
  DeviceType           = 2   ;  0x02    AC Drive
  ProductCode          = 36706 ; 0x8F62  AA2A0004 (YEC A1000, o2-04=62)
  MajorRevision        = 1
  MinorRevision        = 2
  Catalog              = "A1000 AA2A0004 EtherNet/IP"
  Description          = "Yaskawa A1000 0.4 kW 200V, EtherNet/IP option SI-EN3/V"
  ProductName          = "A1000 EtherNet/IP Drive"

6. SI-EN3/V Firmware Verification

6.1 Reading Firmware Revision

The SI-EN3/V revision is exposed as Identity Object Attribute 5 (Minor Revision) and as a numeric value on the option's web page. Typical web-page snippet:

Identity Object
  Vendor ID           : 425 (0x01A9)
  Device Type         : 2 (AC Drive)
  Product Code        : 36706 (0x8F62)
  Major Revision      : 1
  Minor Revision      : 1     <-- corresponds to firmware 1.10 / 221.x
  Serial Number       : xxxx
  Device Name         : A1000-EN3V

Cross-check with the drive keypad: MENU > U4 (Maintenance Monitors) > U4-31 (option CPU version) / U4-32 (option FPGA version).

6.2 Replacement Procedure if Firmware is Defective

1. Power down the drive; wait 5 minutes for the bus capacitors to discharge (DC bus voltage indicator on the keypad must be OFF).
2. Remove the SI-EN3/V card from CN5.
3. Install the replacement (Yaskawa part number SI-EN3/V) verified to be firmware 221.x or higher. Re-seat firmly; ensure the option is detected on power-up (keypad displays "Opt. Com. Card Initializing" then "Online").
4. Set the IP address to the planned value (F7-01 IP, F7-02 subnet, F7-03 gateway).
5. Power cycle the drive. Confirm web server is reachable and Identity Object reports the expected Product Code.
6. Re-attempt CIP Class 1 connection from the CJ2.

7. Omron Network Configurator Diagnostics

7.1 Monitoring the CIP Connection State

1. Open Network Configurator and load the project containing the CJ2 scanner.
2. Right-click the CJ2EIP node in the network tree and choose Monitor.
3. Navigate the tabs to Connection Status. The relevant fields:
   • Open Count – number of successful CIP Forward_Open requests.
   • Close Count – number of Forward_Close or scanner-induced closes.
   • Error Code – last CIP error from the scanner's perspective.
   • Extended Error – 16-bit vendor-specific supplementary code.

7.2 Common CIP Error Codes

7.3 Explicit Message Test for Identity Verification

Before opening a Class 1 connection, perform an explicit Get_Attribute_Single on the Identity Object to confirm Product Code without risking connection state corruption:

1. Network Configurator > Tools > Explicit Message.
2. Target IP = drive IP, Class = 0x01, Instance = 1, Attribute = 3 (Product Code), Service = 0x0E (Get_Attribute_Single).
3. Send. The returned 16-bit value must match the Product Code in the active EDS exactly. If not, the EDS is the source of the connection failure.
4. Repeat for Attribute 4 (Major Revision) and Attribute 5 (Minor Revision).

7.4 Using EDS Compare

Network Configurator's EDS Compare tool uploads the live Identity Object from each device and overlays it against the EDS registered in the project. Mismatched fields are highlighted in red. Use it after every EDS modification to verify that the catalog is now consistent.

8. Assembly Object and Connection Parameters

The A1000 SI-EN3/V exposes the following standard AC-drive assemblies. The CJ2 scanner must reference these exactly:

Recommended connection (matches the source field setup):

Output Assembly Instance : 101 (8 bytes)
Input  Assembly Instance : 151 (8 bytes)
Configuration Assembly   : 100 or 0 (none)
RPI                    : 50 ms (10-100 ms acceptable for A1000)
Connection Type         : Point-to-Point, Class 1
Trigger Type            : Cyclic
Transport Class         : 0 (no ACK)
Priority               : Low (default)

8.1 CJ2 Tag Setup (RSLogix / CX-Programmer Equivalent)

In Network Configurator, edit the connection's Tag Set:

Output Tag Name : VFD_A1000_OUT  (size 8 bytes, mapped to e.g. CIO 2000)
Input  Tag Name : VFD_A1000_IN   (size 8 bytes, mapped to e.g. CIO 2010)
Connection Path : 192.168.1.20 (drive IP)  -- or --  Backplane, Slot 0, IP address

The eight output bytes for assembly 101 are laid out as:

9. Verification and Commissioning

1. Web verification: Drive SI-EN3/V web page shows IP, MAC, Identity Object fields consistent with EDS.
2. Explicit verification: Explicit Get_Attribute_Single on Class 1, Instance 1, Attribute 3 returns the Product Code matching the EDS.
3. NS LED: Solid green on both the SI-EN3/V option and the CJ2 EIP port. NS flashing green = connection idle; solid green = Class 1 connection active.
4. Network Configurator Monitor: Open Count = 1 (or higher after comm-loss events), Error Code = 0, Status = "Connected".
5. Drive keypad: U1-10 (Output Frequency) and U1-13 (Output Current) update in real time as the CJ2 writes the Speed Reference.
6. Loop-back write: Write a fixed Speed Reference from the CJ2 (e.g. 0x04B0 = 1200 rpm for a 60 Hz motor), confirm Drive Status Word bit 0 (Running) asserts within two RPIs.

10. Field-Troubleshooting Matrix

11. SVG Topology Sketch

12. Preventive Recommendations

• Always include the SI-EN3/V option manual (TOBPC73060058) and the Yaskawa A1000 EtherNet/IP application note (AN.AFD.09) in the project documentation folder.
• Maintain a per-drive EDS library on the engineering workstation, keyed by model code (o2-04 value) and regional prefix.
• Before deployment, run the Explicit Message Identity Object test and capture the response into the commissioning report. This is the single most useful diagnostic for any future field issue.
• For multi-drive panels, build the EDS once, prove the connection on one unit, then duplicate the EDS modification pattern for the rest.
• Specify in procurement documents that the SI-EN3/V be supplied at firmware 221.x or later.