7 Troubleshooting
: Not lit
---: Not applicable
yy: Indicates the Slave Unit type, as shown below.
yy
Actual display
i
Word Input Slave Unit (including Mixed I/O
Slave Unit)
o
Word Output Slave Unit
bi
Bit Input Slave Unit
bo
Bit Output Slave Unit
r
Repeater Unit
zzz: Node address where the error occurred (2 digits decimal) (Note: The 100s digit is displayed with a dot.)
Errors in Memory Access Processing
The following indicator patterns show that an error has occurred in the CPU Unit where the Master Unit
is mounted.
MS
NS
7-seg-
indi-
indi-
ment dis-
cator
cator
play
Software set-
---
E4
ting table logic
Red
error
Network param-
---
E6
eters logic error
Red
Slave Unit
---
E7
parameters
Red
logic error
Registration
---
E8
Table logic error
Red
Memory access
---
E9
error
Red
Indicators
: Lit
: Flashing
: Not lit
---: Not applicable
7-6
Slave Unit type
Error
Item
history
Probable cause of error
(hex)
1) The communications mode is set to
the Software Setting Mode (mode 8)
even though a Software Setting
Table has not been made. (By
021A
default, there is no Software Setting
Table.)
2) The Software Setting Table is cor-
rupted.
The Network Parameters Table is cor-
021A
rupted.
The Slave Unit Parameters Table is cor-
021A
rupted.
1) The registration settings (REGS)
are enabled even though the Regis-
021A
tration Table is disabled.
2) The Registration Table is corrupted.
One of the following errors occurred
when the non-volatile memory in the
Unit was accessed:
1) None of the 64 records could be
used during initialization or when
registering an error in the error his-
tory.
2) An error history reading or writing
error
0602
3) A network parameters reading or
writing failure during initialization
4) An identity information reading fail-
ure during initialization
5) A Registration Table information
reading or writing failure during ini-
tialization
6) A Software Setting Table information
reading or writing failure during ini-
tialization
CJ-series CompoNet Master Unit Operation Manual for NJ-series CPU Unit (Cat. No. W493)
Unit operation after error
Countermeasures
detection
1) Restart the Master
Unit in Mode 8.
2) Using the CX-Inte-
grator, reset the Soft-
ware Setting Table.
The error is registered in
the error history. Data and
message exchanges with
Using the CX-Integra-
the CPU Unit are exe-
tor, reset the network
cuted without starting
parameters.
remote I/O communica-
Using the CX-Integra-
tions.
tor, reset the Slave Unit
parameters.
Using the CX-Integra-
tor, reset the Registra-
tion Table.
For 1) and 2), access to
EEPROM stops after the
error history is registered
in RAM. All other normal
operations continue. (Reg-
istering the error history to
RAM continues.)
For 3), 5), and 6) (reading),
Restart the Master Unit.
other operations continue
If the same error occurs
without starting the com-
again, replace the Mas-
munications cycle.
ter Unit.
For 3), 5), and 6) (writing),
further accessing of
EEPROM is stopped.
Aside from these, normal
operations continue.
For 4), normal operations
are executed.