9 Troubleshooting and Maintenance
9-36
CJ-series DeviceNet Units Operation Manual for NJ-series CPU Unit(W497)
The errors that may occur for this Unit are listed below.
The following abbreviations and symbols are used in the event level column.
* This symbol appears only for events for which the user can change the event level.
A version in parentheses in the Event code column is the unit version of the CPU Unit when the event
was added.
Refer to the NJ-series Troubleshooting Manual (Cat. No. W503) for all of the event codes that may
occur in an NJ-series Controller.
9-4-2 Error Table
Abbreviation Meaning
Maj Major fault level
Prt Partial fault level
Min Minor fault level
Obs Observation
Info Information
Symbol Meaning
S Event levels that are defined by the system.
U Event levels that can be changed by the user. *
Event code Event name Meaning Assumed cause
Level
Reference
Maj Prt Min Obs Info
04880000 hex Unit Memory
Error
An error occurred
when writing to
internal memory
where the error his-
tory is saved.
• There is a source of noise
nearby.
• Non-volatile memory failure
SU
page 9-42
04890000 hex Network
Power Error
Network power is
not being supplied.
• Communications power is not
being supplied normally from
the network.
S
page 9-42
148D0000 hex Invalid Scan
List Data
There is an error in
the contents of the
slave scan list or
master scan list
stored in non-vola-
tile memory.
• The power was interrupted dur-
ing writing the scan list to the
non-volatile memory.
S
page 9-43
148E0000 hex Invalid Setup
Data
There is illegal data
in the settings for
the slave function.
• The power was interrupted
while the system was writing
the parameters.
• Non-volatile memory life
S
page 9-43
24480000 hex Node
Address
Duplicated
Error
An error was dis-
covered during the
node address dupli-
cation check when
starting the
DeviceNet Unit.
• The node address of the
DeviceNet Unit is also set for
another node.
S
page 9-44
34BC0000 hex Routing Table
Error
There is illegal data
in the routing tables
set in the CPU Unit.
• The local DeviceNet Unit is not
in the routing tables.
• The routing table format is
incorrect.
• Reading the routing tables
timed out.
SU
page 9-44
To Next Page
Loading...
