Size:
19.68 Mb
Download

Using the LED Indicators and Display for Troubleshooting

 

Section 14-2

Errors Related to the

The 7-segmentdisplay alternates between the node address and error code.

Network

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Indicator

 

Error

Cause

Unit operation (Flag

Error

Countermeasure

 

 

 

 

 

 

status)

log

 

MS

NS

 

7-segment

 

 

 

 

 

 

 

(hex)

 

 

 

 

 

 

 

 

 

---

---

 

E1

Ethernet Link

The link with the

• The Unit will be

03D3

Check the follow-

 

 

 

 

Not Detected

switching hub

offline and unable to

 

ing items:

 

 

 

 

 

could not be

communicate. Errors

 

• Is the cable con-

 

 

 

 

 

detected.

will be returned to all

 

 

 

 

 

 

 

nected?

 

 

 

 

 

 

communications

 

 

 

 

 

 

Note This error

 

• Is the cable dam-

 

 

 

 

 

requests.

 

 

 

 

 

 

will not

 

aged or loose?

 

 

 

 

 

• Data exchanges

 

 

 

 

 

 

occur

 

• Is there excessive

 

 

 

 

 

when

(refreshing) will con-

 

 

 

 

 

 

 

noise?

 

 

 

 

 

data links

tinue with the CPU

 

 

 

 

 

 

 

 

 

 

 

 

 

are not

Unit.

 

 

 

 

 

 

 

set for

The Unit Error

 

 

 

 

 

 

 

version

Occurred Flag (n+10,

 

 

 

 

 

 

 

2.0 or

bit 00), Network Error

 

 

 

 

 

 

 

higher.

Occurred Flag (n+10,

 

 

 

 

 

 

 

 

bit 01), and Link OFF

 

 

 

 

 

 

 

 

Error Flag (n+10, bit

 

 

 

 

 

 

 

 

09) will go ON.

 

 

 

 

 

 

 

 

The Link Status Flag

 

 

 

 

 

 

 

 

(n+13, bit 14) will go

 

 

 

 

 

 

 

 

OFF.

 

 

 

 

 

 

 

 

 

 

 

355

Using the LED Indicators and Display for Troubleshooting

 

Section 14-2

 

 

 

 

 

 

 

 

 

 

Indicator

 

Error

Cause

Unit operation (Flag

Error

Countermeasure

 

 

 

 

 

 

status)

log

 

MS

NS

 

7-segment

 

 

 

 

 

 

 

(hex)

 

 

 

 

 

 

 

 

 

---

---

 

E3

Server Con-

An error

The DNS Server

03C4

Perform one of the

 

 

 

 

nection Error

occurred in

Error Flag (n+14, bit

De-

following:

 

 

 

 

 

communica-

05) will turn ON.

• Correct the DNS

 

 

 

 

 

tails:

 

 

 

 

 

tions with the

 

 

 

 

 

 

 

00xx

server settings.

 

 

 

 

 

DNS server.

 

 

 

 

 

 

 

 

• Check the com-

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

munications path

 

 

 

 

 

 

 

 

(EtherNet/IP Unit

 

 

 

 

 

 

 

 

or built-in

 

 

 

 

 

 

 

 

EtherNet/IP port,

 

 

 

 

 

 

 

 

cable connec-

 

 

 

 

 

 

 

 

tions, hubs, rout-

 

 

 

 

 

 

 

 

ers, and servers)

 

 

 

 

 

 

 

 

and correct any

 

 

 

 

 

 

 

 

problems.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

An error

Case 1:

03C4

Perform one of the

 

 

 

 

 

occurred with

The Unit will continue

De-

following:

 

 

 

 

 

the BOOTP

sending requests to

• Correct the

 

 

 

 

 

tails:

 

 

 

 

 

server.

the BOOTP server

 

 

 

 

 

06xx

BOOTP server

 

 

 

 

 

 

until there is a

 

 

 

 

 

1. There was no

 

settings.

 

 

 

 

 

response

response. In the

 

• Check the com-

 

 

 

 

 

meantime, the Unit

 

 

 

 

 

 

from the

 

munications path

 

 

 

 

 

will be offline and

 

 

 

 

 

 

BOOTP serv-

 

(EtherNet/IP Unit

 

 

 

 

 

er.

unable to communi-

 

or built-in

 

 

 

 

 

cate. Errors will be

 

 

 

 

 

 

2. The BOOTP

 

EtherNet/IP port,

 

 

 

 

 

returned to all com-

 

 

 

 

 

 

server at-

 

cable connec-

 

 

 

 

 

munications requests.

 

 

 

 

 

 

tempted to

 

tions, hubs, rout-

 

 

 

 

 

Data exchanges

 

 

 

 

 

 

set an invalid

 

ers, and servers)

 

 

 

 

 

(refreshing) will con-

 

 

 

 

 

 

IP address in

 

and correct any

 

 

 

 

 

tinue with the CPU

 

 

 

 

 

 

the EtherNet/

 

problems.

 

 

 

 

 

Unit.

 

 

 

 

 

 

IP Unit or

 

 

 

 

 

 

 

Case 2:

 

 

 

 

 

 

 

built-inEther-

 

 

 

 

 

 

 

Net/IP port.

The Unit will operate

 

 

 

 

 

 

 

 

with the default IP

 

 

 

 

 

 

 

 

address

 

 

 

 

 

 

 

 

(192.168.250.node_

 

 

 

 

 

 

 

 

address).

 

 

 

 

 

 

 

 

The Unit Error

 

 

 

 

 

 

 

 

Occurred Flag (n+10,

 

 

 

 

 

 

 

 

bit 00), Network Error

 

 

 

 

 

 

 

 

Occurred Flag (n+10,

 

 

 

 

 

 

 

 

bit 01), and BOOTP

 

 

 

 

 

 

 

 

Server Error Flag

 

 

 

 

 

 

 

 

(n+14, bit 10) will go

 

 

 

 

 

 

 

 

ON.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

An error

The SNTP Server

03C4

Perform one of the

 

 

 

 

 

occurred in

Error Flag (n+14, bit

De-

following:

 

 

 

 

 

communica-

11) will turn ON.

 

 

 

 

 

 

tails:

• Correct the SNTP

 

 

 

 

 

tions with the

 

 

 

 

 

 

 

03xx

server settings.

 

 

 

 

 

STNP server.

 

 

 

 

 

 

 

 

• Check the com-

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

munications path

 

 

 

 

 

 

 

 

(EtherNet/IP Unit

 

 

 

 

 

 

 

 

or built-in

 

 

 

 

 

 

 

 

EtherNet/IP port,

 

 

 

 

 

 

 

 

cable connec-

 

 

 

 

 

 

 

 

tions, hubs, rout-

 

 

 

 

 

 

 

 

ers, and servers)

 

 

 

 

 

 

 

 

and correct any

 

 

 

 

 

 

 

 

problems.

 

 

 

 

 

 

 

 

 

356

Using the LED Indicators and Display for Troubleshooting

 

Section 14-2

 

 

 

 

 

 

 

 

 

 

Indicator

 

Error

Cause

Unit operation (Flag

Error

Countermeasure

 

 

 

 

 

 

status)

log

 

MS

NS

 

7-segment

 

 

 

 

 

 

 

(hex)

 

 

 

 

 

 

 

 

 

---

---

 

E3

Server Con-

An error

---

03C4

Perform one of the

 

 

 

 

nection Error

occurred in

 

De-

following:

 

 

 

 

 

transmission to

 

• Correct the

 

 

 

 

 

 

tails:

 

 

 

 

 

the SNMP trap.

 

 

 

 

 

 

 

07xx

SNMP trap set-

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

tings.

 

 

 

 

 

 

 

 

• Check the com-

 

 

 

 

 

 

 

 

munications path

 

 

 

 

 

 

 

 

(EtherNet/IP Unit

 

 

 

 

 

 

 

 

or built-inEther-

 

 

 

 

 

 

 

 

Net/IP port, cable

 

 

 

 

 

 

 

 

connections,

 

 

 

 

 

 

 

 

hubs, routers, and

 

 

 

 

 

 

 

 

servers) and cor-

 

 

 

 

 

 

 

 

rect any prob-

 

 

 

 

 

 

 

 

lems.

 

 

 

 

 

 

 

 

 

---

Lit red

 

F0

IP Address

The IP address

• The Unit will be

0211

Check the IP

 

 

 

 

Duplication

of the EtherNet/

offline and unable to

 

addresses set on

 

 

 

 

 

IP Unit or built-in

communicate. Errors

 

other nodes.

 

 

 

 

 

EtherNet/IP port

will be returned to all

 

Restart the Ether-

 

 

 

 

 

is the same as

communications

 

Net/IP Unit or built-

 

 

 

 

 

the IP address

requests.

 

in EtherNet/IP port

 

 

 

 

 

set for another

• Data exchanges

 

after correcting the

 

 

 

 

 

node.

(refreshing) will con-

 

IP address settings

 

 

 

 

 

 

tinue with the CPU

 

to eliminate dupli-

 

 

 

 

 

 

Unit.

 

cations.

 

 

 

 

 

 

The Unit Error

 

 

 

 

 

 

 

 

Occurred Flag (n+10,

 

 

 

 

 

 

 

 

bit 00), Network Error

 

 

 

 

 

 

 

 

Occurred Flag (n+10,

 

 

 

 

 

 

 

 

bit 01), and IP

 

 

 

 

 

 

 

 

Address Duplication

 

 

 

 

 

 

 

 

Error Flag (n+10, bit

 

 

 

 

 

 

 

 

06) will go ON.

 

 

 

 

 

 

 

 

 

 

 

Flashing

---

 

F3

Address mis-

The target IP

• Operation will con-

---

Check the IP

red

 

 

 

match

address conver-

tinue with the set IP

 

address and the

 

 

 

 

 

sion method is

address as the local

 

Node Address Set-

 

 

 

 

 

set to Automatic

IP address.

 

ting Switch setting.

 

 

 

 

 

generation, but

The Address Mis-

 

 

 

 

 

 

 

the last byte of

match Flag (n+14,

 

 

 

 

 

 

 

the local IP

bit 14) will turn ON.

 

 

 

 

 

 

 

address does

 

 

 

 

 

 

 

 

not match the

 

 

 

 

 

 

 

 

value set on the

 

 

 

 

 

 

 

 

Node Address

 

 

 

 

 

 

 

 

Setting Switch.

 

 

 

 

 

 

 

 

 

 

 

 

357

Connection Status Codes and Error Processing

 

 

Section 14-3

 

 

 

 

 

 

 

 

 

 

Indicator

 

Error

Cause

Unit operation (Flag

Error

Countermeasure

 

 

 

 

 

 

status)

log

 

MS

NS

 

7-segment

 

 

 

 

 

 

 

(hex)

 

 

 

 

 

 

 

 

 

Flashing

Not lit

 

F4

Communica-

An error

• The Unit will be

020F

Replace the Ether-

red

 

 

 

tions Control-

occurred in the

offline and unable to

 

Net/IP Unit or (for

 

 

 

 

ler Error

Communica-

communicate. Errors

 

the built-inEther-

 

 

 

 

 

tions Controller

will be returned to all

 

Net/IP port) the

 

 

 

 

 

in the EtherNet/

communications

 

CPU Unit if the

 

 

 

 

 

IP Unit or built-in

requests.

 

error recurs when

 

 

 

 

 

EtherNet/IP

• Data exchanges

 

the Unit is

 

 

 

 

 

port.

(refreshing) will con-

 

restarted.

 

 

 

 

 

 

tinue with the CPU

 

 

 

 

 

 

 

 

Unit.

 

 

 

 

 

 

 

 

The Unit Error

 

 

 

 

 

 

 

 

Occurred Flag (n+10,

 

 

 

 

 

 

 

 

bit 00), Network Error

 

 

 

 

 

 

 

 

Occurred Flag (n+10,

 

 

 

 

 

 

 

 

bit 01), and Commu-

 

 

 

 

 

 

 

 

nications Controller

 

 

 

 

 

 

 

 

Error Flag (n+10, bit

 

 

 

 

 

 

 

 

05) will go ON.

 

 

 

 

 

 

 

 

 

 

 

Flashing

---

 

C8

Node Address

The Node

Operation will con-

---

Restart the Ether-

red

 

 

 

Setting

Address Setting

tinue.

 

Net/IP Unit or built-

 

 

 

 

Changed Dur-

Switch was

The IP Address

 

in EtherNet/IP port

 

 

 

 

ing Operation

changed during

Changed During

 

after setting the

 

 

 

 

 

operation.

Operation Flag (n+11,

 

correct node

 

 

 

 

 

 

bit 02) will turn ON.

 

address.

 

 

 

 

 

 

 

 

Errors Related to the Unit

The 7-segmentdisplay alternates between the node address and error code.

 

 

 

 

 

 

 

 

 

Indicator

 

Error

Cause

Unit operation (Flag

Error

Countermeasure

 

 

 

 

 

 

status)

log

 

MS

NS

 

7-segment

 

 

 

 

 

 

 

(hex)

 

 

 

 

 

 

 

 

 

Lit red

Not lit

 

---

Special Unit

An error

Records the error in

0601

Restart the CPU

 

 

 

 

Error

occurred in a

the error log.

 

Unit.

 

 

 

 

 

Special I/O Unit

Operation stops.

 

Replace the Ether-

 

 

 

 

 

or CPU Bus

 

 

 

 

 

 

 

 

Net/IP Unit or (for

 

 

 

 

 

Unit.

 

 

 

 

 

 

 

 

 

the built-inEther-

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Net/IP port) the

 

 

 

 

 

 

 

 

CPU Unit if the

 

 

 

 

 

 

 

 

error recurs.

 

 

 

 

 

 

 

 

 

14-3Connection Status Codes and Error Processing

This section explains how to identify and correct errors based on the tag data link’s connection status. The connection status can be read using the Connection Tab Page of the Network Configurator’s Monitor Device Window. For details, refer to14-1-1 The Network Configurator’s Device Monitor Function.

Note 1. The connection status has the same meaning as the Connection Manager’s General and Additional error response codes, as defined in the CIP specifications.

2.The Open DeviceNet Vendor Association, Inc. (ODVA) can be contacted at the following address to obtain a copy of the CIP specifications.

ODVA Headquarters

4220 Varsity Drive, Suite A

Ann Arbor, Michigan 48108-5006USA

TEL: 1 734-975-8840FAX: 1734-922-0027

358

Connection Status Codes and Error Processing Section 14-3

Email odva@odva.org

WEB www.odva.org

The following table shows the possible originator/target configurations.

Configuration

Originator

Target

 

 

 

Configuration 1

CS1W-EIP21,CJ1W-EIP21,

CS1W-EIP21,CJ1W-EIP21,

 

CJ2H-CPU@@-EIP,CJ2M-

CJ2H-CPU@@-EIP,CJ2M-

 

CPU3@

CPU3@

Configuration 2

CS1W-EIP21,CJ1W-EIP21,

Other company’s device

 

CJ2H-CPU@@-EIP,CJ2M-

 

 

CPU3@

 

Configuration 3

Other company’s device

CS1W-EIP21,CJ1W-EIP21,

 

 

CJ2H-CPU@@-EIP,CJ2M-

 

 

CPU3@

The following table shows the likely causes of the errors causes for each configuration and connection status (code).

Connection status

Source of error

 

Handling

 

 

 

 

 

 

 

General

Additional

 

Configuration 1

Configuration 2

Configuration 3

Status

Status

 

 

 

 

(hex)

(hex)

 

 

 

 

00

0000

Normal status code:

---

---

---

 

 

The connection has been

 

 

 

 

 

opened and the tag data link is

 

 

 

 

 

communicating normally.

 

 

 

 

 

 

 

 

 

01

0100

Error code returned from target:

This error does

Depends on the tar-

Depends on the orig-

 

 

Attempted to open multiple con-

not occur.

get’s specifications.

inator’s specifica-

 

 

nections at the same connec-

 

(Contact the target

tions.

 

 

 

device’s manufac-

(Contact the origina-

 

 

tion.

 

 

 

 

turer for details on

tor device’s manufac-

 

 

 

 

 

 

 

 

preventing the error

turer for details on

 

 

 

 

from occurring in the

preventing the error

 

 

 

 

future.)

from occurring in the

 

 

 

 

 

future.)

 

 

 

 

 

 

01

0103

Error code returned from target:

This error does

Confirm that the tar-

Confirm that the

 

 

Attempted to open a connection

not occur.

get supports Class

originator supports

 

 

with an unsupported transport

 

1.

Class 1.

 

 

 

 

 

 

 

class.

 

 

 

 

 

 

 

 

 

01

0106

Duplicate consumers:

If the tag data link

Depends on the tar-

If the tag data link is

 

 

Attempted to open multiple con-

is stopped or

get’s specifications.

stopped or started,

 

 

nections for single-consumer

started, this error

(Contact the target

this error may occur

 

 

may occur accord-

device’s manufac-

according to the tim-

 

 

data.

 

 

ing to the timing,

turer.)

ing, but the system

 

 

 

 

 

 

but the system will

 

will recover automat-

 

 

 

recover automati-

 

ically.

 

 

 

cally.

 

 

 

 

 

 

 

 

01

0107

Error code returned from target:

This error does

This error does not

This is not an error

 

 

Attempted to close a connec-

not occur.

occur.

because the connec-

 

 

 

 

tion is already

 

 

tion, but that connection was

 

 

 

 

 

 

closed.

 

 

already closed.

 

 

 

 

 

 

 

 

 

 

 

 

 

01

0108

Error code returned from target:

This error does

Check which con-

Check which con-

 

 

Attempted to open a connection

not occur.

nection types can be

nection types can be

 

 

with an unsupported connection

 

used by the target.

used by the origina-

 

 

 

(Contact the manu-

tor.

 

 

type.

 

 

 

 

facturer.)

(An error will occur if

 

 

 

 

 

 

 

 

 

 

 

 

 

Only multicast and

a connection other

 

 

 

 

point-to-pointcan be

than multicast or

 

 

 

 

set.

point-to-pointis set.)

 

 

 

 

 

 

359

Connection Status Codes and Error Processing

 

Section 14-3

 

 

 

 

 

 

Connection status

Source of error

 

Handling

 

 

 

 

 

 

 

General

Additional

 

Configuration 1

Configuration 2

Configuration 3

Status

Status

 

 

 

 

(hex)

(hex)

 

 

 

 

 

 

 

 

 

 

01

0109

Error code returned from target:

Check the connection sizes set in the originator and target.

 

 

The connection size settings

 

 

 

 

 

are different in the originator

 

 

 

 

 

and target.

 

 

 

 

 

 

 

 

 

01

0110

Error code returned from target:

Check whether

Depends on the tar-

Check whether the

 

 

The target was unable to open

the tag data link is

get’s specifications.

tag data link is

 

 

stopped at the tar-

(Contact the target

stopped at the origi-

 

 

the connection, because of its

 

 

get. (Restart the

device’s manufac-

nator. (Restart the

 

 

operating status, such as down-

 

 

loading settings.

tag data link com-

turer.)

tag data link commu-

 

 

munications with

 

nications with the

 

 

 

 

 

 

 

the control bit.)

 

control bit.)

 

 

 

 

 

 

01

0111

Error code returned from target:

This error does

Check the target’s

Set the originator’s

 

 

The RPI was set to a value that

not occur.

RPI setting specifica-

RPI setting to 10

 

 

 

tions.

seconds or less.

 

 

exceeds the specifications.

 

 

 

 

 

 

 

 

 

 

 

 

01

0113

Error code generated by origi-

Check the con-

Check the connec-

Check the connec-

 

 

nator or returned from target:

nection settings

tion settings (number

tion settings (number

 

 

Attempted to open more con-

(number of con-

of connections) at

of connections) at

 

 

nections) at the

the originator and

the originator and

 

 

nections than allowed by the

 

 

originator and tar-

target.

target.

 

 

specifications (CJ2M: 32, other

 

 

get.

Check the connec-

Check the connec-

 

 

CPU Units: 256).

 

 

 

 

 

 

 

tion specifications for

tion specifications for

 

 

 

 

another company’s

another company’s

 

 

 

 

devices.

devices.

 

 

 

 

 

 

01

0114

Error code returned from target:

This error does

Depends on the tar-

Check the origina-

 

 

The Vendor ID and Product

not occur.

get’s specifications.

tor’s connection set-

 

 

 

(Contact the target

tings.

 

 

Code did not match when open-

 

 

 

 

device’s manufac-

 

 

 

ing connection.

 

 

 

 

 

turer.)

 

 

 

 

 

 

 

 

 

 

Confirm that the tar-

 

 

 

 

 

get device’s EDS file

 

 

 

 

 

is correct.

 

 

 

 

 

 

 

01

0115

Error code returned from target:

This error does

Depends on the tar-

Check the origina-

 

 

The Product Type did not match

not occur.

get’s specifications.

tor’s connection set-

 

 

when opening connection.

 

(Contact the target

tings.

 

 

 

device’s manufac-

 

 

 

 

 

 

 

 

 

 

turer.)

 

 

 

 

 

Confirm that the tar-

 

 

 

 

 

get device’s EDS file

 

 

 

 

 

is correct.

 

 

 

 

 

 

 

01

0116

Error code returned from target:

Check the major

Depends on the tar-

Check the origina-

 

 

The Major/Minor Revisions did

and minor revi-

get’s specifications.

tor’s connection set-

 

 

sions set for the

(Contact the target

tings.

 

 

not match when opening con-

 

 

target device and

device’s manufac-

 

 

 

nection.

 

 

 

connection. If nec-

turer.)

 

 

 

 

 

 

 

 

essary, obtain the

Confirm that the tar-

 

 

 

 

EDS file and set it

 

 

 

 

get device’s EDS file

 

 

 

 

again.

 

 

 

 

is correct.

 

 

 

 

 

 

 

 

 

 

 

 

01

0117

Error code returned from target:

Check whether

Depends on the tar-

Check the origina-

 

 

The tag set specified in the con-

the originator and

get’s specifications.

tor’s connection set-

 

 

nection’s target variables does

target tag sets

(Contact the target

tings. Check whether

 

 

and tags are set

device’s manufac-

the target’s tag sets

 

 

not exist.

 

 

correctly.

turer.)

and tags are set cor-

 

 

 

 

 

 

CJ2 CPU Units

 

rectly.

 

 

 

 

CJ2 CPU Units Only:

 

 

 

Only: Check sym-

 

 

 

 

 

Check symbol set-

 

 

 

bol settings in the

 

 

 

 

 

tings in the CPU

 

 

 

CPU Unit.

 

 

 

 

 

Unit.

 

 

 

 

 

360

Connection Status Codes and Error Processing

 

Section 14-3

 

 

 

 

 

 

Connection status

Source of error

 

Handling

 

 

 

 

 

 

 

General

Additional

 

Configuration 1

Configuration 2

Configuration 3

Status

Status

 

 

 

 

(hex)

(hex)

 

 

 

 

 

 

 

 

 

 

01

011A

Error code returned from origi-

An unexpected

An unexpected net-

Follow the operating

 

 

nator:

network load may

work load may have

specifications for the

 

 

Connection could not be estab-

have been

been received. Use

originator. (Consult

 

 

received. Use the

the Network Configu-

the originator manu-

 

 

lished because the buffer was

 

 

Network Configu-

rator Device Monitor

facturer.)

 

 

full due to high traffic.

 

 

rator Device Moni-

or the Ethernet Tab

 

 

 

 

 

 

 

 

tor or the Ethernet

Page to check the

 

 

 

 

Tab Page to check

bandwidth usage,

 

 

 

 

the bandwidth

and correct the load.

 

 

 

 

usage, and cor-

If there are places

 

 

 

 

rect the load. If

where broadcast

 

 

 

 

there are places

storms occur, such

 

 

 

 

where broadcast

as loop connections

 

 

 

 

storms occur,

in the network con-

 

 

 

 

such as loop con-

nection format, then

 

 

 

 

nections in the

correct them.

 

 

 

 

network connec-

 

 

 

 

 

tion format, then

 

 

 

 

 

correct them.

 

 

 

 

 

 

 

 

01

011B

Error code returned from target:

This error does

Depends on the tar-

Set the originator’s

 

 

The RPI was set to a value that

not occur.

get’s specifications.

RPI setting to 0.5 ms

 

 

 

(Contact the target

or greater.

 

 

is below the specifications.

 

 

 

 

device’s manufac-

 

 

 

 

 

 

 

 

 

 

turer.)

 

 

 

 

 

 

 

01

0203

Error code returned from target:

Tag data link communications from the target timed out. Check

 

 

The connection timed out.

the power supply and cable wiring of the devices in the commu-

 

 

nications path, including the target and switches. If performance

 

 

 

 

 

 

has dropped due to heavy load, change the performance set-

 

 

 

tings. For example, increase the timeout time or RPI setting.

 

 

 

 

01

0204

Error code returned from target:

There was no response from the target. Check the power supply

 

 

The connection-openingpro-

and cable wiring of the devices in the communications path,

 

 

including the target and switches.

 

 

 

cess timed out.

 

 

 

 

 

 

 

 

 

 

 

 

01

0205

Error code returned from target:

This error does

Depends on the tar-

Depends on the orig-

 

 

There was a parameter error in

not occur.

get’s specifications.

inator’s specifica-

 

 

 

(Contact the target

tions. (Contact the

 

 

the frame used to open the con-

 

 

 

 

device’s manufac-

originator device’s

 

 

nection.

 

 

 

 

turer.)

manufacturer.)

 

 

 

 

01

0302

Error occurred at originator or

Check the origina-

Check the target’s

Check the originator

 

 

error code returned from target:

tor and target con-

connection settings

and target connec-

 

 

The tag data link’s allowable

nection settings

(number of connec-

tion settings (number

 

 

(number of con-

tions and RPI).

of connections and

 

 

bandwidth (pps) was exceeded.

 

 

 

nections and

 

RPI).

 

 

 

RPI).

 

 

 

 

 

 

 

 

01

0311

Error code returned from target:

This error does

Depends on the tar-

Depends on the orig-

 

 

There was a parameter error in

not occur.

get’s specifications.

inator’s specifica-

 

 

 

(Contact the target

tions. (Contact the

 

 

the frame used to open the con-

 

 

 

 

device’s manufac-

originator device’s

 

 

nection.

 

 

 

 

turer.)

manufacturer.)

 

 

 

 

01

0312

Error code returned from target:

This error does

Depends on the tar-

Depends on the orig-

 

 

There was a parameter error in

not occur.

get’s specifications.

inator’s specifica-

 

 

 

(Contact the target

tions. (Contact the

 

 

the frame used to open the con-

 

 

 

 

device’s manufac-

originator device’s

 

 

nection.

 

 

 

 

turer.)

manufacturer.)

 

 

 

 

01

0315

Error code returned from target:

This error does

Depends on the tar-

Depends on the orig-

 

 

There was a parameter error in

not occur.

get’s specifications.

inator’s specifica-

 

 

 

(Contact the target

tions. (Contact the

 

 

the frame used to open the con-

 

 

 

 

device’s manufac-

originator device’s

 

 

nection.

 

 

 

 

turer.)

manufacturer.)

 

 

 

 

361

Connection Status Codes and Error Processing

 

Section 14-3

 

 

 

 

 

 

Connection status

Source of error

 

Handling

 

 

 

 

 

 

 

General

Additional

 

Configuration 1

Configuration 2

Configuration 3

Status

Status

 

 

 

 

(hex)

(hex)

 

 

 

 

 

 

 

 

 

 

01

0316

Error code returned from target:

This error does

Depends on the tar-

Depends on the orig-

 

 

There was a parameter error in

not occur.

get’s specifications.

inator’s specifica-

 

 

 

(Contact the target

tions. (Contact the

 

 

the frame used to close the con-

 

 

 

 

device’s manufac-

originator device’s

 

 

nection.

 

 

 

 

turer.)

manufacturer.)

 

 

 

 

01

031C

Error code generated in origina-

This error does

The originator gener-

Depends on the orig-

 

 

tor:

not occur.

ates this code when

inator’s specifica-

 

 

Some other error occurred.

 

an unsupported

tions. (Contact the

 

 

 

response code is

originator device’s

 

 

 

 

 

 

 

 

returned from the

manufacturer.)

 

 

 

 

target in reply to a

 

 

 

 

 

connection-opening

 

 

 

 

 

request.

 

 

 

 

 

 

 

08

---

Error code returned from target:

This error does

Depends on the tar-

Depends on the orig-

 

 

There is no Forward Open or

not occur.

get’s specifications.

inator’s specifica-

 

 

 

(Contact the target

tions. (Contact the

 

 

Large Forward Open service in

 

 

 

 

device’s manufac-

originator device’s

 

 

the target device.

 

 

 

 

turer.)

manufacturer.)

 

 

 

 

D0

0001

Error code generated in origina-

The connection

The meaning of this

Depends on the orig-

 

 

tor:

was stopped

error code is defined

inator’s specifica-

 

 

The connection operation is

because the Tag

by each vendor, so it

tions. (Contact the

 

 

Data Link Stop Bit

depends on the tar-

originator device’s

 

 

stopped.

 

 

was turned ON, or

get’s specifications.

manufacturer.)

 

 

 

 

 

 

the settings data

(Contact the target

 

 

 

 

is being down-

device’s manufac-

 

 

 

 

loaded.

turer.)

 

 

 

 

Either turn ON the

 

 

 

 

 

Tag Data Link

 

 

 

 

 

Start Bit, or wait

 

 

 

 

 

until the settings

 

 

 

 

 

data has been

 

 

 

 

 

downloaded.

 

 

 

 

 

Includes Control-

 

 

 

 

 

ler stop errors,

 

 

 

 

 

Unit failure, and

 

 

 

 

 

EM bank files at

 

 

 

 

 

the refresh desti-

 

 

 

 

 

nation. To handle

 

 

 

 

 

these errors, refer

 

 

 

 

 

to 14-2-1Errors

 

 

 

 

 

Occurring at the

 

 

 

 

 

EtherNet/IP Unit

 

 

 

 

 

or built-inEther-

 

 

 

 

 

Net/IP port.

 

 

 

 

 

 

 

 

D0

0002

Error code generated in origina-

Wait until the

The meaning of this

Depends on the orig-

 

 

tor:

opening process-

error code is defined

inator’s specifica-

 

 

The connection is being opened

ing is completed.

by each vendor, so it

tions. (Contact the

 

 

(opening processing in

 

depends on the tar-

originator device’s

 

 

 

get’s specifications.

manufacturer.)

 

 

progress).

 

 

 

 

(Contact the target

 

 

 

 

 

 

 

 

 

 

device’s manufac-

 

 

 

 

 

turer.)

 

 

 

 

 

 

 

362

Connection Status Codes and Error Processing

 

Section 14-3

 

 

 

 

 

 

Connection status

Source of error

 

Handling

 

 

 

 

 

 

 

General

Additional

 

Configuration 1

Configuration 2

Configuration 3

Status

Status

 

 

 

 

(hex)

(hex)

 

 

 

 

 

 

 

 

 

 

Unique OMRON Error Codes

 

 

 

 

 

 

 

 

 

01

0810

Error code returned from target:

This error may

The meaning of this

The meaning of this

 

 

New data could not be obtained

occur if the CPU

error code is defined

error code is defined

 

 

Unit’s cycle time

by each vendor, so it

by each vendor, so it

 

 

from the CPU Unit when open-

 

 

was long when

depends on the tar-

depends on the origi-

 

 

ing connection. (The Unit will

 

 

opening the con-

get’s specifications.

nator’s specifica-

 

 

automatically retry, and attempt

 

 

nection, the speci-

(Contact the target

tions.

 

 

to open the connection again.)

 

 

fied EM bank was

device’s manufac-

(Contact the origina-

 

 

 

 

 

 

converted to file

turer.)

tor device’s manufac-

 

 

 

memory, or some

 

turer.)

 

 

 

problem in the

 

 

 

 

 

PLC caused the

 

 

 

 

 

PLC to stop.

 

 

 

 

 

If the cycle time

 

 

 

 

 

was too long, the

 

 

 

 

 

problem will be

 

 

 

 

 

resolved automat-

 

 

 

 

 

ically. If the EM

 

 

 

 

 

bank is set as file

 

 

 

 

 

memory, change

 

 

 

 

 

the storage loca-

 

 

 

 

 

tion for the tag

 

 

 

 

 

data. If the PLC

 

 

 

 

 

has stopped,

 

 

 

 

 

identify and cor-

 

 

 

 

 

rect the error.

 

 

 

 

 

If the PLC system

 

 

 

 

 

is stopped, iden-

 

 

 

 

 

tify the cause of

 

 

 

 

 

the error from the

 

 

 

 

 

CPU Unit error

 

 

 

 

 

data.

 

 

 

 

 

 

 

 

01

0811

Error code generated in origina-

This error may

The meaning of this

The meaning of this

 

 

tor:

occur if the CPU

error code is defined

error code is defined

 

 

New data could not be obtained

Unit’s cycle time

by each vendor, so it

by each vendor, so it

 

 

was long when

depends on the tar-

depends on the origi-

 

 

from the CPU Unit when open-

 

 

opening the con-

get’s specifications.

nator’s specifica-

 

 

ing connection. (The Unit will

 

 

nection, or the

(Contact the target

tions.

 

 

automatically retry, and attempt

 

 

specified EM bank

device’s manufac-

(Contact the origina-

 

 

to open the connection again.)

 

 

was converted to

turer.)

tor device’s manufac-

 

 

 

 

 

 

file memory.

 

turer.)

 

 

 

If the cycle time

 

 

 

 

 

was too long, the

 

 

 

 

 

problem will be

 

 

 

 

 

resolved automat-

 

 

 

 

 

ically. If the EM

 

 

 

 

 

bank is set as file

 

 

 

 

 

memory, change

 

 

 

 

 

the storage loca-

 

 

 

 

 

tion for the tag

 

 

 

 

 

data.

 

 

 

 

 

 

 

 

363

Error Log Function

Section 14-4

14-4Error Log Function

Errors detected by the EtherNet/IP Unit or built-inEtherNet/IP port are stored in the error log along with the date and time of their occurrence. The error log can be read and cleared from the Network Configurator.

Some error log records are cleared when the CPU Unit’s power goes OFF, and other records are not cleared.

14-4-1Error Log Data Specifications

Each error is recorded as one record in the error log.

Item

Specifications

 

 

Record length

10 bytes/record

 

 

Number of records

64 records max.

 

 

Data type

Binary (time information: BCD)

 

 

Structure of Each Record

Bit 15

 

Bit 00

 

Error code

 

 

 

Detail code

 

 

 

Minutes

 

Seconds

 

 

 

Day of month

 

Hour

 

 

 

Year

 

Month

 

 

 

14-4-2Error Log Registration

Error Log Storage Area

When an error occurs, information on the error and the time stamp are stored

 

in the Unit’s internal RAM as an error log record. Serious errors are recorded

 

in non-volatileEEPROM as well as RAM. The time read from the CPU Unit

 

during cyclic servicing is used for the time stamp.

 

The error log records stored in EEPROM are copied to RAM when the Unit

 

starts operating, so these records are retained even when the Unit’s power is

 

turned OFF or the Unit is restarted.

 

When the error log is read, the error log records in RAM are read. When the

 

error log is cleared, the error log records in both RAM and EEPROM are

 

erased.

Error Log Overflows

The error log can record up to 64 records. If another error occurs when the log

 

is full, the oldest record will be erased to make room for the new error record.

Power Interruptions when Saving to EEPROM

If the power supply is interrupted or the Unit is restarted while the error log is being written to EEPROM, the error log may be corrupted. When the Unit starts, it performs a checksum test on the error log data read from EEPROM to detect corrupted data.

14-4-3FINS Commands for Error Logs

The following FINS commands can be sent to the EtherNet/IP Unit or built-in

EtherNet/IP port to read or clear the error log.

Command code

Function name

 

 

 

MRC

SRC

 

 

 

 

21

02

ERROR LOG READ

 

 

 

 

03

ERROR LOG CLEAR

 

 

 

For details, refer to Appendix E FINS Commands Addressed to EtherNet/IP

Units or Built-in EtherNet/IP Ports.

364

Error Log Function Section 14-4

14-4-4Error Log Error Codes

Error

Error

Detail code

Saved in

code

 

 

 

EEPROM

 

First byte

Second byte

(hex)

 

 

 

 

 

 

0001

CPU Unit watchdog timer error

00 hex

00 hex

Yes

 

 

 

 

 

0002

CPU Unit service monitoring error

Monitoring time (ms)

 

Yes

 

 

 

 

0006

Other CPU error

Bit D11: Unit not in Registered I/O Tables

Yes

 

 

(Other bits are reserved for system use.)

 

 

 

 

 

 

000E

I/O bus error

00 hex

00 hex

Yes

 

 

 

 

 

000F

CPU Unit initialization error

00 hex

00 hex

Yes

 

 

 

 

 

0011

Event timed out

MRC (main command)

SRC (subcommand)

Yes

 

 

 

 

 

0012

CPU Unit memory error

01 hex: Read error

03 hex: Routing tables

Yes

 

 

02 hex: Write error

50 hex: CPU Bus Unit

 

 

 

 

Area (CIO or DM)

 

 

 

 

 

 

0015

CPU Unit fatal error

00 hex

00 hex

Yes

 

 

 

 

 

0017

Tag database error

00 hex

00 hex

Yes

 

 

 

 

 

0103

Resend count exceeded (send failed)

FINS Command:

 

No

 

 

Bit 15: OFF

 

 

0105

Node address setting error (send failed)

 

No

Bits 08 to 14: Source network address

 

 

 

0107

Remote node not in network (send failed)

No

Bits 00 to 07: Source node address

 

 

 

0108

No Unit with specified unit address (send

FINS Response:

 

No

 

failed)

Bit 15: ON

 

 

010B

CPU Unit error (send failed)

Bits 08 to 14: Destination network address

No

 

 

Bits 00 to 07: Destination node address

 

010D

Destination address not in routing tables

No

CIP Frame:

 

 

(send failed)

 

 

 

 

FFFF

 

 

010E

Not registered in routing tables (send failed)

 

No

 

 

 

 

 

 

 

010F

Routing table error (send failed)

 

 

No

 

 

 

 

 

0110

Too many relay points (send failed)

 

 

No

 

 

 

 

 

0111

Command too long (send failed)

 

 

No

 

 

 

 

 

0112

Header error (send failed)

 

 

No

 

 

 

 

 

0117

Internal buffers full; packet discarded

 

 

No

 

 

 

 

 

0118

Illegal packet discarded

 

 

No

 

 

 

 

 

0119

Local node busy (send failed)

 

 

No

 

 

 

 

 

0120

Unexpected routing error

 

 

No

 

 

 

 

 

0122

Service not supported in current mode;

 

 

No

 

packet discarded

 

 

 

 

 

 

 

 

0123

Internal send buffer full; packet discarded

 

 

No

 

 

 

 

 

0124

Maximum frame size exceeded; routing

 

 

No

 

failed

 

 

 

 

 

 

 

 

0125

Response timeout; packet discarded

 

 

No

 

 

 

 

 

020F

Communications controller error

00 hex

01 hex

Yes

 

 

 

 

 

0211

IP address duplication

Port number (always 02)

Lower byte of IP address

Yes

 

 

 

 

 

021A

Logic error in setting table

00 hex

02 hex: Network parame-

Yes

 

 

 

ters

 

 

 

 

03 hex: Routing tables

 

 

 

 

04 hex: Unit Setup

 

 

 

 

0E hex: Unit name

 

 

 

 

12 hex: Status area layout

 

 

 

 

setting error

 

 

 

 

13 hex: Status area layout

 

 

 

 

setting verification error

 

 

 

 

15 hex: Installation in a

 

 

 

 

PLC of another series

 

 

 

 

(e.g., from CJ1 to CJ2)

 

 

 

 

after setting the Unit.

 

 

 

 

 

 

365

Error Log Function

 

 

Section 14-4

 

 

 

 

 

 

Error

Error

 

Detail code

Saved in

code

 

 

 

 

EEPROM

 

First byte

 

Second byte

(hex)

 

 

 

 

 

 

 

 

0300

Parameter error; packet discarded

FINS Command:

 

 

No

 

 

Bit 15: OFF

 

 

 

 

 

Bits 08 to 14: Source network address

 

 

 

Bits 00 to 07: Source node address

 

 

 

FINS Response:

 

 

 

 

 

Bit 15: ON

 

 

 

 

 

Bits 08 to 14: Destination network address

 

 

 

Bits 00 to 07: Destination node address

 

 

 

CIP Frame:

 

 

 

 

 

FFFF

 

 

 

 

 

 

 

 

 

0347

I/O refreshing error

00 hex

 

00 hex

Yes

 

 

 

 

 

 

03C0

FINS/TCP setting error

01 to 10 hex:

 

01: Automatically allo-

No

 

 

Connection number

 

cated FINS node address

 

 

 

 

 

duplication

 

 

 

 

 

02: Destination IP address

 

 

 

 

 

error

 

 

 

 

 

03: Destination port num-

 

 

 

 

 

ber error

 

 

 

 

 

 

 

03C1

Server settings error

00 hex: DNS

 

01: IP address

No

 

 

03 hex: SNTP

 

02: Host name

 

 

 

 

03: Port number

 

 

 

04 hex: FTP

 

 

 

 

 

04: Other parameter

 

 

 

06 hex: BOOTP

 

 

 

 

 

 

 

 

 

07 hex: SNMP

 

 

 

 

 

08 hex: SNMP Trap

 

 

 

 

 

09 hex: FINS/UDP

 

 

 

 

 

0A hex: FINS/TCP

 

 

 

 

 

 

 

 

 

03C2

FINS/TCP packet discarded

01 to 10 hex:

 

02 hex: Reopening

No

 

 

Connection number

 

because remote node

 

 

 

 

 

closed

 

 

 

 

 

03 hex: Reopening

 

 

 

 

 

because of reception error

 

 

 

 

 

04 hex: Reopening

 

 

 

 

 

because of transmission

 

 

 

 

 

error

 

 

 

 

 

05 hex: Reopening

 

 

 

 

 

because RST received

 

 

 

 

 

from remote node

 

 

 

 

 

06 hex: Reopening

 

 

 

 

 

because of no keep-alive

 

 

 

 

 

response

 

 

 

 

 

07 hex: Illegal FINS/TCP

 

 

 

 

 

procedure

 

 

 

 

 

08 hex: Insufficient mem-

 

 

 

 

 

ory during server process-

 

 

 

 

 

ing

 

 

 

 

 

09 hex: Insufficient mem-

 

 

 

 

 

ory during client process-

 

 

 

 

 

ing

 

 

 

 

 

0A hex: Insufficient mem-

 

 

 

 

 

ory during node switching

 

 

 

 

 

 

 

03C3

FINS/UDP packet discarded

00 hex

 

01 to FE hex:

No

 

 

 

 

Source node address

 

 

 

 

 

 

 

366

Error Log Function

 

Section 14-4

 

 

 

 

 

Error

Error

Detail code

Saved in

code

 

 

 

EEPROM

 

First byte

Second byte

(hex)

 

 

 

 

 

 

03C4

Server connection error

00 hex: DNS

01 hex: Specified host

No

 

 

03 hex: SNTP

does not exist

 

 

 

02 hex: No such service at

 

 

 

04 hex: FTP

 

 

 

specified host

 

 

 

06 hex: BOOTP

 

 

 

03 hex: Timeout

 

 

 

07 hex: SNMP

 

 

 

06 hex: Host name resolu-

 

 

 

08 hex: SNMP Trap

 

 

 

tion error

 

 

 

 

 

 

 

 

07 hex: Transmission error

 

 

 

 

08 hex: Reception error

 

 

 

 

09 hex: Other error

 

 

 

 

0A hex: Obtaining IP

 

 

 

 

address error

 

 

 

 

 

 

03C6

Clock write error

0001: The clock time

Clear the error from the

No

 

 

could not be updated

CPU Unit.

 

 

 

because a error occurred

 

 

 

 

in the CPU Unit.

 

 

 

 

 

 

 

 

 

0002: The clock time

Refer to SECTION 12

 

 

 

could not be updated

Automatic Clock Adjust-

 

 

 

because the CPU Unit or

ment Function and check

 

 

 

operating mode does not

the application conditions.

 

 

 

support this function.

 

 

 

 

 

 

 

03D0

Ethernet basic setting error

01 hex: Ethernet setting

01 hex: Checksum error

Yes

 

 

error

11 hex: Inconsistent set-

 

 

 

 

 

 

 

 

tings

 

 

 

 

12 hex: Specified baud

 

 

 

 

rate is not supported.

 

 

 

 

 

 

 

 

02 hex: TCP/IP basic set-

01 hex: Checksum error

 

 

 

ting error

11 hex: Invalid IP address

 

 

 

 

 

 

 

 

12 hex: Invalid subnet

 

 

 

 

mask

 

 

 

 

13 hex: Invalid default

 

 

 

 

gateway address

 

 

 

 

14 hex: Invalid primary

 

 

 

 

name server

 

 

 

 

15 hex: Invalid secondary

 

 

 

 

name server

 

 

 

 

16 hex: Invalid domain

 

 

 

 

name

 

 

 

 

17 hex: Invalid host name

 

 

 

 

 

 

03D1

Ethernet advanced setting error

02 hex: FINS setting error

01 hex: Checksum error

Yes

 

 

 

10 hex: Invalid IP router

 

 

 

 

table

 

 

 

 

11 hex: Invalid FINS/UDP

 

 

 

 

setting

 

 

 

 

12 hex: Invalid FINS/TCP

 

 

 

 

setting

 

 

 

 

13 hex: Invalid FTP setting

 

 

 

 

14 hex: Invalid SNTP set-

 

 

 

 

ting

 

 

 

 

15 hex: Invalid SNMP set-

 

 

 

 

ting

 

 

 

 

16 hex: Invalid SNMP trap

 

 

 

 

setting

 

 

 

 

 

 

03D2

Packet discarded.

01 hex

00 hex

No

 

 

 

 

 

367

Troubleshooting

 

Section 14-5

 

 

 

 

 

Error

Error

Detail code

Saved in

code

 

 

 

EEPROM

 

First byte

Second byte

(hex)

 

 

 

 

 

 

03D3

Link OFF error

00 hex

00 hex

No

 

 

 

 

 

03D4

Verification error (Tag data link only)

Connection instance num-

Lower byte of IP address

No

 

Note For details on identifying the cause of

ber (0 to 255)

 

 

 

the verification error, refer to 14-3

 

 

 

 

Connection Status Codes and Error

 

 

 

 

Processing.

 

 

 

 

This error will not be stored when a

 

 

 

 

target node is missing for version 2.0

 

 

 

 

or higher.

 

 

 

 

 

 

 

 

03D5

Tag data link error

00 hex

Lower byte of IP address

No

 

 

 

 

 

0601

CPU Bus Unit error

Variable

 

Yes

 

 

 

 

 

0602

CPU Bus Unit memory error

01: Read error

02 hex: Network parame-

Yes

 

 

02: Write error

ter

(See

 

 

 

 

 

 

06 hex: Error log

note.)

 

 

 

09 hex: Identity data

 

 

 

 

0E hex: Unit name

 

 

 

 

0F hex: Ethernet basic

 

 

 

 

setting

 

 

 

 

10 hex: Ethernet

 

 

 

 

advanced setting

 

 

 

 

11 hex: MAC address

 

 

 

 

12 hex: Status area layout

 

 

 

 

setting

 

 

 

 

14 hex: Term Tag address

 

 

 

 

resolution memory write

 

 

 

 

error

 

 

 

 

 

 

Note If a memory error occurs in the error log area of EEPROM, the record will not be stored in EEPROM.

14-5Troubleshooting

14-5-1CPU Unit's ERR/ALM Indicator Lit or Flashing

Use the following table to troubleshoot the system when the CPU Unit’s ERR/

ALM indicator is lit or flashing when the EtherNet/IP Unit or built-inEtherNet/

IP port is mounted.

An I/O verification

• Confirm that the Unit is connected properly.

error occurred.

• Check the I/O table with the I/O Table Verification operation

 

and correct it if necessary. After correcting it, perform the I/O

 

Table Create operation.

 

 

A CPU Bus Unit

• The CPU Bus Unit model registered in the I/O tables does

setting error

not match the model of CPU Bus Unit actually mounted.

occurred.

Check the I/O tables with the I/O Table Verification operation

 

and correct it if necessary.

 

After correcting the I/O tables, perform the I/O Table Create

 

operation.

 

 

A CPU Bus error

• Confirm that the Unit is connected properly.

occurred.

• Restart the Unit. Replace the Unit if it doesn’t restart.

 

 

An I/O Bus error

• Confirm that the Unit is connected properly.

occurred.

• Restart the Unit. Replace the Unit if it doesn’t restart.

 

 

For details, refer to the CPU Unit’s Operation Manual.

368

Troubleshooting Section 14-5

14-5-2General Ethernet Problems

 

The 100M and 10M

• Confirm that the cable being used has the correct ratings.

 

Indicators on the

• Confirm that the cable is properly connected to the switching

 

EtherNet/IP Unit or

hub, and the hub’s power supply is ON. (The 7-segmentdis-

 

CPU Unit are both

play will indicate error E1.)

 

OFF.

• If the switching hub’s settings can be changed, confirm that

 

 

 

 

the Ethernet link settings are the same as the settings for the

 

 

EtherNet/IP Unit or built-inEtherNet/IP port. (For details,

 

 

refer to 3-4 Network Installation.)

 

 

 

 

The NS Indicator

• Check whether the same IP address is set on another node.

 

on the EtherNet/IP

(The 7-segmentdisplay will indicate error F0.)

 

Unit or CPU Unit is

 

 

lit red.

 

14-5-3Tag Data Links Fail to Start

 

Use the following table to troubleshoot tag data links when the Tag Data Links

Operating Flag (bit 15 in Communications Status 1) does not go ON.

The indicators on

• Check whether power is being supplied to the PLC.

the EtherNet/IP Unit

• Check whether the EtherNet/IP Unit or built-inEtherNet/IP

or CPU Unit are all

port is mounted in the Backplane correctly.

OFF.

• If a watchdog timer (WDT) error has occurred in the PLC, fol-

 

 

low the procedures described in the PLC’s Operation Man-

 

ual to correct the problem.

 

• All of the indicators for the EtherNet/IP Unit or built-inEther-

 

Net/IP port will be OFF if a CPU Bus Unit error has occurred.

 

Check for a CPU Bus Unit error.

 

• Restart the Unit. Replace the Unit if it doesn’t restart.

 

 

The MS indicator

• If the EtherNet/IP Unit's 7-segmentdisplay is displaying an

on the EtherNet/IP

error code, refer to the tables in 14-2 Using the LED Indica-

Unit or CPU Unit is

tors and Display for Troubleshooting.

lit green, but the NS

• Confirm that the cables are properly connected to the

indicator remains

switching hub and the power supply to the switching hub is

OFF.

ON.

 

• If data is being restored by the simple backup function, wait

 

until the restore operation is completed.

 

 

The MS indicator

• If the EtherNet/IP Unit's 7-segmentdisplay is displaying an

on the EtherNet/IP

error code, refer to the tables in 14-2 Using the LED Indica-

Unit or CPU Unit is

tors and Display for Troubleshooting.

lit green, but the NS

• The NS indicator will continue to flash green if the tag data

indicator contin-

link settings have not been set in the Unit. Use the Network

ues to flash green.

Configurator to set the tag data link settings in the Unit, and

 

then restart the Unit.

 

 

The MS indicators

• Identify the error code shown on the 7-segmentdisplay

is lit green on the

based on the tables in 14-2 Using the LED Indicators and

EtherNet/IP Unit or

Display for Troubleshooting, and eliminate the cause of the

CPU Unit, but the

error.

NS indicator con-

 

tinues to flash red.

 

 

 

369

Troubleshooting

Section 14-5

14-5-4Tag Data Link Problems

The tag data isn't simultaneous.

At startup, the received data is OFF unexpectedly.

The tag data links start and stop communicating intermittently.

Observe the following precautions when writing application programs:

Maintain the simultaneity of data in connection-unitsbetween the PLC and EtherNet/IP Unit orbuilt-inEtherNet/IP port.

If another company's device is being used, refer to that device's user's manual for details.

When received data is used in the ladder program, use the All Tag Data Links Operating Flag in Communications Status 1, or the Target Node PLC Operating Flag as a condition. If the Target Node PLC Operating Flag is used, the PLC status must be included in tag sets of both the sending and receiving nodes.

If the Output OFF function (Output Inhibit) is enabled in the output (produce) tag settings, all of the output data will be OFF if a fatal error occurs in the CPU Unit or the Output OFF Bit is turned ON. Check the status of the output (producer) PLC.

Check whether the baud rate is set to 10 Mbps, or a 10M or 100M repeater hub is being used. The tag data link performance is based on the use of switching hubs. The bandwidth listed in the specifications (CJ2M: 3,000 pps, other CPU Units: 6,000 pps) is achieved when the Unit auto-negotiatestofull-duplexat 100 Mbps.

Refer to 14-1 Checking Status with the Network Configurator for details on checking the error counters on the Monitor Device Window’s Ethernet InformationTab Page. The error and discarded packet counters indicate problems such as noise in the communications path, the use of substandard cables, damaged cables/connectors, loose connectors, abnormally high communications load, or incorrect wiring (loops) in the switching hub wiring.

Contact the switching hub manufacturer to determine whether there are any problems with the transfer capacity of the switching hubs in the communications path. If switching hubs are arranged in a cascade connection, there may be a heavy load concentrated at a mid-levelswitching hub. In the EtherNet/IP Unit orbuilt-inEtherNet/IP port itself, processing is performed with a higher priority than message communications, so specifications provide for a 3,000 pps bandwidth for the CJ2M and a 6,000 pps bandwidth for other CPU Units in tag data link performance only.

Refer to 14-1 Checking Status with the Network Configurator for details on checking the connection status on the Monitor Device Window’s ConnectionTab Page. Eliminate any errors, which can be identified in the tables in 14-3 Connection Status Codes and Error Processing.

370

Troubleshooting with FINS Response Codes

Section 14-6

14-5-5Message Timeout Problems

Timeout errors occur frequently in message services (CIP UCMM, CIP Class 3, or FINS).

When there is a high load in the tag data link, and the CPU Unit’s cycle time is relatively long or there are messages coming in from many nodes, the message service response time may be delayed and messages may be discarded occasionally.

In this case, the communications load must be reduced by increasing (slowing) the tag data link’s RPI, reducing the message load, or increasing the timeout value.

The tag data link’s bandwidth usage can be checked on the Monitor Device Window’s Ethernet Information Tab Page. Refer to14-1 Checking Status with the Network Configurator for details.

The error log error codes that indicate discarded messages (insufficient memory) due to heavy communications loads are 0117, 0119, 0123, 0125, 03C2 (detail code @@08, @@09, or @@0A), 03C3, and 03D2. Refer to 14-1 Checking Status with the Network Configurator for details on reading the error codes on theError History Tab Page.

For information on preventing high loads in FINS communications, refer to 8-7 Precautions on High Traffic in FINS Communications.

14-6Troubleshooting with FINS Response Codes

The cause of errors that occur when using the SEND(090), RECV(098), or CMND(490) instructions can be identified from the response codes. (Refer to the description of Communications Port Completion Codes in8-6-4 Writing Programs for the storage locations of response codes generated by the SEND(090), RECV(098), or CMND(490) instructions.)

This section describes the completion codes produced by EtherNet/IP Units. For details on completion codes produced by CPU Units, other CPU Bus Units, or computers equipped with FINS services, refer to the device’s operation manual.

The 6th, 7th, and 15th bits of the response codes have specific functions. The 6th bit will be ON when anon-fatalerror has occurred in the PLC at the remote node; the 7th bit will be ON when a fatal error has occurred in the PLC at the

remote node; and the 15th bit will be ON when a network relay error has occurred. The following table explains the meaning of the completion codes.

 

 

 

 

First byte

 

 

 

 

 

 

 

 

 

Second byte

 

 

 

Bit

7

6

5

4

3

2

1

0

7

6

5

4

3

2

1

0

 

 

 

Main response code (RES)

 

 

 

 

 

 

Sub response code (SRES)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

PLC Fatal Error Flag

 

 

 

 

PLC Non-fatalError Flag

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Relay Error Flag

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Main response

Sub response code

Item to check

Likely cause

Corrective action

 

code

 

 

 

 

 

 

 

 

 

 

Value and

Value and meaning

 

 

 

meaning

 

 

 

 

 

 

 

 

 

 

 

00

Normal

00

---

---

---

---

 

completion

 

 

 

 

 

 

 

 

 

 

 

 

371

Troubleshooting with FINS Response Codes

 

Section 14-6

 

 

 

 

 

 

 

 

 

 

Main response

 

Sub response code

Item to check

Likely cause

Corrective action

 

 

 

code

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Value and

 

Value and meaning

 

 

 

 

 

meaning

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

01

 

Local node

03

 

Local node send

---

Lack of available space in

The load (traffic) on the Ether-

 

 

 

error

 

 

error

 

internal buffers

net Unit is too heavy. Check

 

 

 

 

 

 

 

 

 

your user applications.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

05

 

Node address set-

Local IP

The network cannot be

Correct the local IP address.

 

 

 

 

 

 

ting error

address

used because the IP

 

 

 

 

 

 

 

 

 

address setting is incor-

 

 

 

 

 

 

 

 

 

rect.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

07

 

Local node busy

System load

Lack of available space in

The load (traffic) on the Ether-

 

 

 

 

 

 

(send failed)

 

internal buffers

net Unit is too heavy. Check

 

 

 

 

 

 

 

 

 

your user applications.

 

 

 

 

 

 

 

 

 

 

 

02

 

Remote

01

 

Remote node not in

IP address

IP address of remote

Set IP address of remote

 

 

 

node error

 

 

network

table and IP

node not set correctly.

node into IP address table

 

 

 

 

 

 

 

router table

 

and, if internetwork transmis-

 

 

 

 

 

 

 

 

 

sion is required, into the IP

 

 

 

 

 

 

 

 

 

router table.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

02

 

No Unit with speci-

Instruction’s

There is no Unit with the

Check the remote node's unit

 

 

 

 

 

 

fied unit address

control data

specified unit address.

address.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

05

 

Response timeout

Transfer condi-

Message packet was cor-

Increase the number of trans-

 

 

 

 

 

 

 

tions

rupted by transmission

mit retry attempts.

 

 

 

 

 

 

 

(Use FINS

error.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

status read

 

 

 

 

 

 

 

 

 

commands.)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Instruction’s

The response monitoring

Set a longer response moni-

 

 

 

 

 

 

 

control data

time is too short.

toring time.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Read the error

The transmission frame

Read out the error log and

 

 

 

 

 

 

 

log.

may be corrupted or the

correct the system as

 

 

 

 

 

 

 

 

internal reception buffer

required.

 

 

 

 

 

 

 

 

full.

 

 

 

 

 

 

 

 

 

 

 

 

03

 

Unit error

01

 

Communications

Affected con-

Error occurred in the

Take corrective action, refer-

 

 

 

(Controller

 

 

controller error

troller’s ERC

communications control-

ring to troubleshooting proce-

 

 

 

error)

 

 

 

indicator

ler.

dures in this section.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

02

 

PLC error

Affected

CPU Unit error occurred

Clear the error in the CPU

 

 

 

 

 

 

 

node’s LED

in the PLC at the remote

Unit. (Refer to the PLC's oper-

 

 

 

 

 

 

 

indicators

node.

ation manuals.)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

04

 

Unit number setting

Unit number

The unit number setting

Confirm that the unit number

 

 

 

 

 

 

error

 

is incorrect.

set on the switch is within the

 

 

 

 

 

 

 

 

 

specified range and that the

 

 

 

 

 

 

 

 

 

same unit number is not used

 

 

 

 

 

 

 

 

 

twice in the same network.

 

 

 

 

 

 

 

 

 

 

 

04

 

Service not

01

 

Unsupported com-

Command

The specified command

Check the command code.

 

 

 

supported

 

 

mand

code

code is not supported by

 

 

 

 

 

 

 

 

 

the destination Unit.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

FINS header

A short frame (4 bytes) is

The EtherNet/IP Unit does not

 

 

 

 

 

 

 

frame length

being used for the FINS

support short headers.

 

 

 

 

 

 

 

 

header frame.

 

 

 

 

 

 

 

 

 

 

 

 

05

 

Routing

01

 

Routing table setting

Routing tables

Remote node is not set in

Set the destination address in

 

 

 

error

 

 

error

 

the routing tables.

the routing tables.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

02

 

Routing tables not

Routing tables

Destination is unknown

Set routing tables at the local

 

 

 

 

 

 

registered

 

because there are no

node, remote node, and any

 

 

 

 

 

 

 

 

routing tables.

relay nodes.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

03

 

Routing table error

Routing tables

Routing table error

Set the routing tables cor-

 

 

 

 

 

 

 

 

 

rectly.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

04

 

Too many relay

Network con-

The maximum number of

Redesign the network, or

 

 

 

 

 

 

points

figuration

network levels (3) was

reconsider the routing tables

 

 

 

 

 

 

 

 

exceeded in the com-

to reduce the number of relay

 

 

 

 

 

 

 

 

mand.

nodes in the command.

 

 

 

 

 

 

 

 

 

 

 

372

Troubleshooting with FINS Response Codes

 

Section 14-6

 

 

 

 

 

 

 

 

Main response

 

Sub response code

Item to check

Likely cause

Corrective action

 

 

code

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Value and

 

Value and meaning

 

 

 

 

meaning

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

10

 

Command

01

 

Command too long

Command

The command is too

Check the command format of

 

 

format error

 

 

 

data

long.

the command and set it cor-

 

 

 

 

 

 

 

 

rectly.

 

 

 

 

 

 

 

The command exceeded

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

1,473 bytes when broad-

 

 

 

 

 

 

 

 

casting.

 

 

 

 

 

 

 

 

 

 

 

 

 

02

 

Command too short

Command

The command is too

 

 

 

 

 

 

 

data

short.

 

 

 

 

 

 

 

 

 

 

 

 

 

03

 

Number of items

Command

The specified number of

Check the number of items

 

 

 

 

 

does not match

data

items does not match the

and amount of data, and

 

 

 

 

 

amount of data

 

amount of write data.

make them agree.

 

 

 

 

 

 

 

 

 

 

 

 

05

 

Header parameter

Command

Data for another node on

Check the command format of

 

 

 

 

 

error

data

the same network was

the command and set it cor-

 

 

 

 

 

 

 

received from the net-

rectly.

 

 

 

 

 

 

 

work.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Attempted to send

 

 

 

 

 

 

 

 

response data for a

 

 

 

 

 

 

 

 

broadcast address.

 

 

 

 

 

 

 

 

 

 

11

 

Parameter

00

 

Parameter error

Parameters in

The specified parame-

Check the command data and

 

 

error

 

 

 

command

ters are incorrect.

set the parameters correctly.

 

 

 

 

 

 

data

 

 

 

 

 

 

 

 

The UDP/TCP socket

Be sure the socket number is

 

 

 

 

 

 

 

 

 

 

 

 

 

 

number was not within

between 1 and 8.

 

 

 

 

 

 

 

the proper range.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

The local UDP port num-

Set the local UDP port num-

 

 

 

 

 

 

 

ber might be set to 0.

ber correctly.

 

 

 

 

 

 

 

 

 

 

 

01

No data area code

Variable type

A correct memory area

Check the command’s data

 

 

 

 

 

 

in command

code has not been used

area code in the Results Stor-

 

 

 

 

 

 

data

or EM Area is not avail-

age Area and set the appro-

 

 

 

 

 

 

 

able.

priate code.

 

 

 

 

 

 

 

 

 

 

 

 

03

 

Address out-of-

First word

The first word is in an

Check the data area range,

 

 

 

 

 

range error

address in

inaccessible area.

and set a first word that is in

 

 

 

 

 

 

command

 

an accessible area.

 

 

 

 

 

 

data

 

 

 

 

 

 

 

 

The specified bit number

Check the command’s data

 

 

 

 

 

 

 

 

 

 

 

 

 

 

is not 00.

area code in the Results Stor-

 

 

 

 

 

 

 

 

age Area. The bit address

 

 

 

 

 

 

 

 

must be 00 for EtherNet/IP

 

 

 

 

 

 

 

 

Units.

 

 

 

 

 

 

 

 

 

 

 

 

04

 

Address range over-

Command

The address range speci-

Set the address in the com-

 

 

 

 

 

flow

data

fied in the command is

mand data so that the start

 

 

 

 

 

 

 

not correct.

address plus the number of

 

 

 

 

 

 

 

 

words does not exceed

 

 

 

 

 

 

 

 

accessible memory.

 

 

 

 

 

 

 

 

 

 

 

 

0B

 

Response too long

Command

The response frame is

Correct the number of data

 

 

 

 

 

 

data

longer than allowed.

elements or other parameters

 

 

 

 

 

 

 

 

in the command data for

 

 

 

 

 

 

 

 

which the response is being

 

 

 

 

 

 

 

 

returned.

 

 

 

 

 

 

 

 

 

 

 

 

0C

 

Parameter error

Parameters in

The specified parame-

Check the command data and

 

 

 

 

 

 

command

ters are incorrect.

set the parameters correctly.

 

 

 

 

 

 

data

 

 

 

 

 

 

 

 

 

 

 

21

 

Cannot

08

 

Cannot change

IP address

A FINS message was

Correct the relationships

 

 

write

 

 

 

conversion

received from an IP

between IP addresses and

 

 

 

 

 

 

method

address that differed from

FINS node addresses. Refer

 

 

 

 

 

 

 

the ones in the Unit

to SECTION 5 Determining IP

 

 

 

 

 

 

 

Setup with FINS node

Addresses for details.

 

 

 

 

 

 

 

addresses that could not

 

 

 

 

 

 

 

 

be dynamically changed.

 

 

 

 

 

 

 

 

 

 

373

Troubleshooting with FINS Response Codes

 

Section 14-6

 

 

 

 

 

 

 

 

 

 

Main response

 

Sub response code

Item to check

Likely cause

Corrective action

 

 

 

code

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Value and

 

Value and meaning

 

 

 

 

 

meaning

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

22

 

Status error

0F

 

Cannot execute

Socket status

The same socket service

Use the corresponding socket

 

 

 

(operating

 

 

because service is

area

is already in progress at

status flag in PLC memory to

 

 

 

 

 

being processed.

 

the specified socket num-

be sure that socket service

 

 

 

mode dis-

 

 

 

 

 

 

 

 

 

 

ber.

has finished before starting

 

 

 

agreement)

 

 

 

 

 

 

 

 

 

 

 

 

services again.

 

 

 

 

 

 

 

 

 

 

 

 

 

10

 

Socket not open

Socket status

The specified socket is

Open the socket. (For TCP

 

 

 

 

 

 

 

area

not open.

sockets, wait until the connec-

 

 

 

 

 

 

 

 

 

tion is made.)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

11

 

Local node busy

System load

Lack of available space in

The load (traffic) on the Ether-

 

 

 

 

 

 

(send failed)

 

internal buffers

net Unit is too heavy. Check

 

 

 

 

 

 

 

 

 

your user applications.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

20

 

FINS/TCP not con-

Unit Setup

Not opened due to sys-

Correctly set the Unit Setup,

 

 

 

 

 

 

nected

 

tem settings.

FINS/TCP connection num-

 

 

 

 

 

 

 

 

 

ber, remote IP address, and

 

 

 

 

21

 

 

 

Not opened due to a

 

 

 

 

 

 

 

remote port number.

 

 

 

 

 

 

 

 

change command from

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

the FINS/TCP connec-

 

 

 

 

 

 

 

 

 

tion’s remote node.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

22

 

 

 

Closed by remote node;

 

 

 

 

 

 

 

 

 

opening again.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

23

 

 

 

Opening again because

 

 

 

 

 

 

 

 

 

of a reception error.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

24

 

 

 

Opening again because

 

 

 

 

 

 

 

 

 

of a send error.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

25

 

 

 

Opening again because

 

 

 

 

 

 

 

 

 

of an RST response in

 

 

 

 

 

 

 

 

 

keep-alive.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

26

 

 

 

Opening again because

 

 

 

 

 

 

 

 

 

there was no response in

 

 

 

 

 

 

 

 

 

keep-alive.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

30

 

Establishing connec-

Command

A connection is already

Correct the settings for the

 

 

 

 

 

 

tion

data

established with the

FINS/TCP connection num-

 

 

 

 

 

 

 

 

specified remote node.

ber, the remote IP address,

 

 

 

 

 

 

 

 

 

and the remote port number.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

31

 

Cannot change con-

Unit Setup

The specified connection

Correct the settings for the

 

 

 

 

 

 

nection

and com-

number is not set as a

Unit Setup, the FINS/TCP

 

 

 

 

 

 

 

mand data

FINS/TCP client in the

connection number, the

 

 

 

 

 

 

 

 

Unit Setup.

remote IP address, and the

 

 

 

 

 

 

 

 

 

remote port number.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

32

 

Cannot execute

Command

While a remote node

Correct the settings for the

 

 

 

 

 

 

because service was

data

change was being pro-

FINS/TCP connection num-

 

 

 

 

 

 

interrupted

 

cessed for the specified

ber, the remote IP address,

 

 

 

 

 

 

 

 

connection number, a

and the remote port number.

 

 

 

 

 

 

 

 

request for a change was

 

 

 

 

 

 

 

 

 

received and the pro-

 

 

 

 

 

 

 

 

 

cessing was stopped.

 

 

 

 

 

 

 

 

 

 

 

 

23

 

No such

05

 

Parameters

Unit Setup

IP address conversion

Check the IP address and

 

 

 

Unit (Envi-

 

 

 

 

failed.

subnet mask in the Unit

 

 

 

ronment

 

 

 

 

 

Setup, and correct if neces-

 

 

 

error)

 

 

 

 

 

sary.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

07

 

Configuration error

IP address

IP address conversion is

Check the IP address conver-

 

 

 

 

 

 

 

conversion in

set for automatic conver-

sion setting in the Unit Setup.

 

 

 

 

 

 

 

Unit Setup

sion only.

This error will be generated

 

 

 

 

 

 

 

 

 

for the READ IP ADDRESS

 

 

 

 

 

 

 

 

 

TABLE command only.

 

 

 

 

 

 

 

 

 

 

 

374