EttherN
Net/IP
P Errror C
Code Decoderr

Version
n 2.20
12/19//2014

 
  
 
This document is inte
ended to hellp the user id
dentify the ccauses of errror codes ge
enerated when
connectin
ng EtherNet/IP devices tot Omron PL LC and MAC C controllerss such as CS
S1, CJ2, CJ11,
and NJ products.
p Deetailed troub
bleshooting procedures
p ffor common errors are aalso provided
d.

Section
n 1: Readin
ng the Erro
or Code

1. Go
G online with the Omron
n Network Configurato
C or for EtherN
Net/IP.

2. Upload
U the pa arameters frrom the PLC
C / MAC if the
e configuration in the EttherNet/IP
module
m is diffferent from the
t configura
ation in the N
Network Connfigurator for EtherNet/IP
P by
right clicking on the PLC / MAC, and selecting Pa arameter / U
Upload.

3. Right
R Click on
n the PLC / MAC
M and se
elect Monito
or.

Paage 2 of 16 
 
  
 
4. Go
G to the Connection tab. The deta ailed error co
ode for eachh device is sh hown in Stattus.
Nodes
N with co
ommunicatio ons errors will
w be shown n with a red ccircle next to
o the node.
Refer
R to the error
e code lis
st in Section 2 of this do
ocument for tthe specific eerror
in
nformation.

Paage 3 of 16 
 
  
 
Section
n 2: Error Code
C List

Note:
N error codes show
wn in bold have
h troubl eshooting p
proceduress in section 3.

01:0
0100 Conne ection in use or
o duplicate fo
orward open
01:0
0103 Transpport class andd trigger combination not ssupported
01:0
0106 Ownership Conflictt
01:0
0107 Targett connection not
n found
01:0
0108 Invalid
d network con nnection parameter
01:0
0109 Invalid
d connection n size
01:0
0110 Targett for connection not configured
01:0
0111 RPI noot supported
01:0
0113 Out off connections
01:0
0114 Vendo or ID or Prodduct Code miismatch
01:0
0115 Produ uct Type Mismatch
01:0
0116 Revision Mismatc ch
01:0
0117 Invalid
d Produced or Consume ed application n path
01:0
0118 Invalid
d or inconsiste
ent configurattion applicatio
on path
01:0
0119 Non-LListen only connnection not opened
o
01:0
011A Targett object out off connections
s
01:0
011B RPI is smaller than the productio on inhibit time
e
01:0
011C Transpport Class No ot Supported
01:0
011D Production Trigger Not Supporte ed
01:0
011E Direction Not Supported
01:0
011F Invalid
d Originator to
o Target Netwwork Connecttion FIXVAR
01:0
0120 Invalid
d Target to Orriginator Netw
work Connecttion FIXVAR
01:0
0121 Invalid
d Originator to
o Target Netwwork Connecttion Priority
01:0
0122 Invalid
d Target to Orriginator Netw
work Connecttion Priority
01:0
0123 Invalid
d Originator to
o Target Netwwork Connecttion Type
01:0
0124 Invalid
d Target to Orriginator Netw
work Connecttion Type
01:0
0125 Invalid
d Originator to
o Target Netwwork Connecttion Redundant_Owner
01:0
0126 Invalid
d Configuratioon Size
01:0
0127 Invalid
d Originator to Target Siz ze
01:0
0128 Invalid
d Target to Originator
O Siz
ze
01:0
0129 Invalid
d Configuratioon Application
n Path
01:0
012A Invalid
d Consuming Application Path
P
01:0
012B Invalid
d Producing Application
A Pa
ath
01:0
012C Configguration Symb bol Does Not Exist
01:0
012D Consu uming Symbo ol Does Not Ex xist
01:0
012E Producing Symbol Does Not Exiist
01:0
012F Inconssistent Application Path Coombination
01:0
0130 Inconssistent Consuume Data Format

Paage 4 of 16 
 
  
 
01:0
0131 Inconssistent Produc ce Data Form mat
01:0
0132 Null Forward Open Function Not Supported
01:0
0133 Conne ection Timeou ut Multiplier Not
N Acceptable e
01:0
0203 Conne ection timed out
o
01:0
0204 Uncon nnected reque est timed out
01:0
0205 Parammeter error in unconnected request servvice
01:0
0206 Messa age too large for unconnec cted send serrvice
01:0
0207 Uncon nnected ackno owledgementt without replyy
01:0
0301 No buffer memory available
a
01:0
0302 Netwo ork bandwidth h not availablee for data
01:0
0303 No consumed conn nection ID filte
er available
01:0
0304 Not coonfigured to send
s scheduleed priority datta
01:0
0305 Sched dule signature e mismatch
01:0
0306 Sched dule signature e validation noot possible
01:0
0311 Port not available
01:0
0312 Link address
a not va
alid
01:0
0315 Invalid
d segment in connection pa ath
01:0
0316 Error in
i Forward Cllose service connection
c paath
01:0
0317 Sched duling not spe ecified
01:0
0318 Link address
a to self invalid
01:0
0319 Secon ndary resourc ce unavailable e
01:0
031A Rack connection
c allready established
01:0
031B Modulle connection already esta ablished
01:0
031C Misceellaneous
01:0
031D Redun ndant connec ction mismatch
01:0
031E No mo ore user confiigurable link consumer
c ressources
available in the prooducing module
01:0
031F No mo ore user confiigurable link consumer
c ressources
available in the prooducing module
01:0
0800 Netwo ork link in pathh to module iss offline
01:0
0810 No tarrget applicatioon data availa able
01:0
0811 No originator applic cation data av vailable

Paage 5 of 16 
 
  
 
Section
n 3: Troublleshooting
g common error code
es:

EDS
E file diffe
erences: Error
E codes 01:0114, 01 1:0115, and 01:0116, arre caused byy
differences in n the Identity
y Object betw
ween the .edds file installed in the Ne
etwork
Configurator
C for EtherNett/IP and the actual hardw
ware device. To correctt these errorrs,
re
ead the actual value of the paramete ers from the device, and d modify the .eds file (ussing
Notepad)
N to match
m the ha
ardware devvice.

1. Using the
e Network Coonfigurator fo
or EtherNet//IP, select Tools / Setupp Parameteers.
The Netwwork Configurator for Eth
herNet/IP mu
ust be online e to select th
his menu opttion.

Paage 6 of 16 
 
  
 
2. Using the
e Setup Para ameter tool, read the val ue of each o of the 4 para
ameters show wn,
and modiffy the .eds file for the de es read from the device. To
evice to matcch the value
read the data,
d send thhe message es to the IP A
Address of th
he device, using a servicce of
Get Attrib
bute Single. Refer to th he table beloow for Classs, Instance, a
and Attribute
e
informatio
on.

Cla
ass Insttance Atttribute
VendCodee 01 01 01
ProdType 01 01 02
ProdCode 01 01 03
MajRev/MinRev 01 01 04

3. Responsse to VendC Code: The re

esponse to rreading Attriibute 1 will b
be a hexadeccimal
number, which
w is byte
e swapped. Example: 22F00 = Vend dCode 47.

4. Responsse to ProdTy ype: The re

esponse to re
eading Attrib
bute 2 will be
e a hexadeccimal
number, which
w is byte
e swapped. Example: 0 0700 = ProddType 7.

5. Responsse to ProdCo ode: The re

esponse to A
Attribute 3 w
will be a hexa
adecimal
number, which
w is byte
e swapped. Example: 55104 = Vend dCode 1105.

Paage 7 of 16 
 
  
 

6. Responsse to MajRevv/MinRev: The

T responsse to Attributte 4 will be 2 digits of
MajRev in
n hexadecim
mal and 2 dig
gits of MinRe
ev in hexade
ecimal. Exam mple: 0201 =
MajRev 02,
0 MinRev 01.
0

7. The Device section of

o the .eds file should be
e modified to
o match the vvalues read from
meters, as sh
the param hown below..

Device]
[D
VendCoode = 47;
VendNaame = "OMR RON Corpora ation";
ProdTyp
pe = 7;
ProdTyp
peStr = "Genneral Purpos
se Discrete I/O";
ProdCodde = 1105;
MajRev = 2;
MinRev = 1;
ProdNamme = "ERT1-MD32SLH--1";

8. After mak
king the chan e from the product tree iin the
nges, save the file, delette the device
Network Configurator
C r for EtherNe
et/IP, and re move any in nstances of tthe device in
n the
network diagram.
d Reeload the .ed
ds file and co
omplete the connectionss.

Paage 8 of 16 
 
  
 
IO
O Size Mismmatches: Error
E codes 01:0109, 01 1:0127, 01:0
0128 and som metimes
01:031C are caused by differences
d in
n the producced or consu
umed data ssize specified d in
th
he connectio
on to a devicce, compared d to the actu
ual assemblyy sizes of the
e device. Too
co
orrect these errors, read
d the actual produced
p an
nd consumed assembly data from th he
device, determine the sizze from the response datta, and mod dify the connection size.

1. Using the
e Connection n for the devvice, determine the produ
n information uced and
consumed d assembly numbers forr the device.. Shown bellow are asse emblies 104 and
101.

2. Using the
e Network Coonfigurator fo
or EtherNet//IP, select Tools / Setupp Parameteers.
The Netwwork Configurator for Eth
herNet/IP mu
ust be online e to select th
his menu opttion.

Paage 9 of 16 
 
  
 
3. Using the
e Setup Para
ameter tool, read the raww data for eaach assemblly. To read tthe
data, send the messaages to the IP Address o of the device
e, using a se
ervice of Gett
Attribute Single. Us
se Class 4, Instance
I <A
Assembly N Number in hexadecimal>,
Attribute 3. From the
e example in n step 1, Asssembly 104 (Instance 6 68, which is 104
ecimal) and Assembly
in hexade A 1001 (Instancee 65, which is 101 in hexxadecimal) aare
read.

4. Count thee number of digits receivved in the Re esult, and divvide the num mber of digitts by
2 to deterrmine the nu
umber of byte es. If the re sponse in th
he Result win ndow is larg
ge,
highlight the
t entire Re esult, and co
opy / paste into Notepad d to facilitate
e counting thhe
number ofo digits. In the example above, the response to o reading the e data from
Assembly y 104 is 2 byytes long (4 digits) and tthe response e to reading the data froom
Assembly y 101 is 4 byytes long (8 digits).

Page 10 of 16 
 
  
 
5. Modify the
e Assembly Size for the device by:

a. Right click on the device in the netwo rk diagram, and selectin

ng Paramete
er /
Ed
dit.

b. Moodify the ass

sembly sizes
s as shown. After modiffying the sizzes, edit the Tag
siz
zes for the PLC
P / MAC, modify the C
Connection tto reflect the
e new sizes, and
do
ownload to thhe PLC / MAAC.

Page 11 of 16 
 
  
 
6. If the above steps do not resolve error code 01:0109, 01:0127, 01:0 0128 and
sometime es 01:031C, try the followwing to addrress a speciffic situation in which the
e .eds
file for the
e EtherNet/IPP device indicates that tthe product ddoes not use e a 32 Bit Ruun /
Idle Head der, but the hardware
h do
oes use a 32 dle Header. This Run / Idle
2 Bit Run / Id
Header mismatch
m cou
uld be in the
e produced cconnection, tthe consume ed connectioon, or
both conn nections, so there are 3 different commbinations tto try. See th he image onn the
following page for an example of each of the 3 combinatiions.

a. Addd 4 extra by
ytes to the Produced
P Daata (both the
e size for the
e device and the
Ommron PLC / MAC Tag).
b. Addd 4 extra by
ytes to the Consumed
C D
Data (both thhe size for th
he device and the
Ommron PLC / MAC Tag).
c. Addd 4 extra by
ytes to both the Produce
ed and Conssumed Data (both the size
for the device and the Ommron PLC / MMAC tags).

If this does resolvve the commmunication errror, the data

a in the Omrron PLC / MAAC
will bee offset by 4 bytes from the
t beginnin ng of the PLC
C tag or memory addresss.
The first 4 bytes will
w be the 322 Bit Run / Id
dle header, a
and should n not be used in
the PL LC / MAC prrogram.

Page 12 of 16 
 
  
 

Page 13 of 16 
 
  
 
Invalid Produced
P orr Consumed d Applicatioon Path: E Error code 001:0117 mayy be caused by
Tag Nam mes used in the
t Network k Configuratoor for EtherN
Net/IP that do
o not exist in
n the PLC /
MAC, do not have the same size e in the PLC as in the Neetwork Conffigurator for EEtherNet/IP,, or
are not marked
m as neetwork variables in the PLC
P / MAC.

1. Verify tha
at any Tag Names used in the Netwo ork Configurrator for Ethe
erNet/IP
a. Ex xist in the PL
LC / MAC, and are spell ed correctly.
b. Arre marked as s network va ariables or P
Publish Only.
c. Arre the correc ct size in the
e PLC to mattch the size in the Netwoork Configurrator
for EtherNet/IPP (in Bytes)..

Examp
ple from CX
X Programm
mer

Example fro
om Sysmac
c Studio

Page 14 of 16 
 
  
 
Other errror codes: Error code es other than n those desccribed in secction 3 of thiss document may
indicate that
t addition
nal modifications to the .e
eds file are n
necessary, oor that the product itself
does not comply with h the EtherN
Net/IP specifiication.

Please contact Omro

on and / or th
he EtherNet//IP device m
manufacturerr for addition
nal support.

Page 15 of 16 
 
  
 
Section
n 4: Other general EttherNet/IP troublesho
t ooting reco
ommendattions:

1. Use Poinnt to Point connections, instead of MMulticast con

nnections. S
Some devicees do
ort Multicast connections
not suppo s, or do not iimplement th
hem properly, and some
e IT
devices block
b Multica
ast packets.

2. Remove Ethernet
E switches from the
t network,, and use a ccrossover Ethernet cable
between the
t PLC / MAAC and the EtherNet/IP
P device.

ent Ethernett cables. Eth

3. Try differe hernet cable
es degrade w with rough usse in the fielld
(laptop baags, etc.). Also,
A sometim
mes cables aare over crim
mped duringg manufacturring,
causing inntermittent connections.
c

4. If the Stattus of the co

onnection as read in secction 1 is 00:00000, but the data receiived
from the EtherNet/IP
E ways 0 for a ll bytes rece
device is alw eived, this may indicate
improper implementation of the 32 3 Bit Run / IIdle Header in the EtherrNet/IP devicce.
Contact Omron
O Technical Support for assista
ance removin ng the Run / Idle Heade er
from the .eds file, andd add extra bytes
b as desscribed in ste ep 6 of sectiion 3 of this
documentt.

Page 16 of 16 
 
OMRON AUTOMATION AND SAFETY • THE AMERICAS HEADQUARTERS • Chicago, IL USA • 847.843.7900 • 800.556.6766 • www.omron247.com

OMRON CANADA, INC. • HEAD OFFICE OMRON ARGENTINA • SALES OFFICE

Toronto, ON, Canada • 416.286.6465 • 866.986.6766 • www.omron247.com Cono Sur • 54.11.4783.5300

OMRON ELECTRONICS DE MEXICO • HEAD OFFICE OMRON CHILE • SALES OFFICE

México DF • 52.55.59.01.43.00 • 01-800-226-6766 • mela@omron.com Santiago • 56.9.9917.3920

OMRON ELECTRONICS DE MEXICO • SALES OFFICE OTHER OMRON LATIN AMERICA SALES
Apodaca, N.L. • 52.81.11.56.99.20 • 01-800-226-6766 • mela@omron.com 54.11.4783.5300

OMRON ELETRÔNICA DO BRASIL LTDA • HEAD OFFICE

São Paulo, SP, Brasil • 55.11.2101.6300 • www.omron.com.br

OMRON EUROPE B.V. • Wegalaan 67-69, NL-2132 JD, Hoofddorp, The Netherlands. • +31 (0) 23 568 13 00 • www.industrial.omron.eu

Authorized Distributor: Automation Control Systems

• Machine Automation Controllers (MAC) • Programmable Controllers (PLC)
• Operator interfaces (HMI) • Distributed I/O • Software
Drives & Motion Controls
• Servo & AC Drives • Motion Controllers & Encoders
Temperature & Process Controllers
• Single and Multi-loop Controllers
Sensors & Vision
• Proximity Sensors • Photoelectric Sensors • Fiber-Optic Sensors
• Amplified Photomicrosensors • Measurement Sensors
• Ultrasonic Sensors • Vision Sensors
Industrial Components
• RFID/Code Readers • Relays • Pushbuttons & Indicators
• Limit and Basic Switches • Timers • Counters • Metering Devices
• Power Supplies
Safety
• Laser Scanners • Safety Mats • Edges and Bumpers • Programmable Safety
Controllers • Light Curtains • Safety Relays • Safety Interlock Switches

QSG EIP Error 12/14 Note: Specifications are subject to change. © 2014 Omron Electronics LLC Printed in U.S.A.

Printed on recycled paper.