176
Handling Errors Section 8-1
: Flashing
: Not lit
---: Not applicable
yy: Indicates the Slave Unit type, as shown below.
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.
Indicators
: Lit
: Flashing
yy Actual
display
Slave Unit type
i Input (including inputs and
outputs together)
oOutput
bi Bit input
bo Bit output
r Repeater Unit
MS
indicator
NS
indicator
7-
segment
display
Item Error
history
(hex)
Probable cause of error Unit operation after error
detection
Countermeasures
Red
--- E4
Software set-
ting table
logic error
021A
1) The mode is the Software Set-
ting Mode (Mode 8) even
though the Software Setting
Table is disabled.
2) The Software Setting Table is
corrupted.
The error is registered in the
error history. Data and mes-
sage exchanges with the CPU
Unit are executed without
starting remote I/O communi-
cations.
1) Restart the Master
Unit in Mode 8.
2) Using the CX-Integra-
tor, reset the Software
Setting Table.
Red
--- E6
Network
parameters
logic error
021A
The Network Parameters Table is
corrupted.
Using the CX-Integrator,
reset the network parame-
ters.
Red
--- E7
Slave Unit
parameters
logic error
021A
The Slave Unit Parameters Table
is corrupted.
Using the CX-Integrator,
reset the Slave Unit
parameters.
Red
--- E8
Registration
Table logic
error
021A
1) The registration settings
(REGS) are enabled even
though the Registration Table
is disabled.
2) The Registration Table is cor-
rupted.
Using the CX-Integrator,
reset the Registration
Table.
Red
--- E9
Memory
access error
0602
One of the following errors
occurred when the non-volatile
memory in the Unit was
accessed:
1) Not all 64 records could be
used during initialization or
when registering an error in
the error history.
2) An error history reading or
writing error
3) A network parameters reading
or writing failure during initial-
ization
4) An identity information reading
failure during initialization
5) A Registration Table informa-
tion reading or writing failure
during initialization
6) A Software Setting Table infor-
mation reading or writing fail-
ure during initialization
For 1) and 2), access to
EEPROM stops from RAM
error history registration
onwards. All other normal
operations continue. (Regis-
tering the error history to RAM
continues.)
For 3), 5), and 6) (reading),
other operations continue
without starting the communi-
cations cycle.
For 3), 5), and 6) (writing), fur-
ther accessing of EEPROM is
stopped. Aside from these,
normal operations continue.
For 4), normal operations are
executed.
Restart the Master Unit. If
the same error occurs
again, replace the Master
Unit.
To Next Page
Loading...
