175
Handling Errors Section 8-1
Errors in Remote I/O Communications
The following indicator patterns show that an error related to the CompoNet
Network has occurred.
Errors can basically be identified by the NS indicator flashing red and the
seven-segment display showing d*.
Indicators
: Lit
MS
indicator
NS
indicator
7-segment
display
Item Error
history
(hex)
Probable cause of
error
Unit operation after error
detection
Countermeasures
---
Red
d9
↓
yy
↓
zzz
Communica-
tions error
0374
A system disconnection
was detected.
System operations continue.
Each detected disconnection is
registered in the error history.
Participation of the disconnected
Slave Unit is awaited. When
there is no longer any cause of
an error, normal operation is
restored. (The NS indicator lights
green.)
Either of the following may be
the cause of the error.
1) Communications had to be
continually retried for the
applicable Slave Unit due to
noise, until the specified
number of retries was
exceeded.
2) Responses to communica-
tions from the Master Unit
are not possible because of
a malfunction, line discon-
nection, or communications
power supply interruption at
the Slave Unit itself.
Inspect the Slave Unit where
the disconnection was detected,
and remove the cause of the
error. There is no need to
restart the Master Unit.
---
Red
d 0
↓
yy
↓
zzz
Address
duplication
error
0376
An address duplication
error was detected for a
Slave Unit attempting
to participate.
The duplication error is regis-
tered in the error history. All sys-
tem operations continue.
A Slave Unit or Repeater Unit in
the same network is set for the
same node. Use the following
procedure:
1) Turn OFF the power to the
Master Unit and the Slave
Unit.
2) Change the duplicate node
number to a new value.
3) Turn the power back ON to
the Master Unit and the
Slave Unit.
---
Red
E5
Illegal config-
uration error
0378
It was detected that the
Slave Units and
Repeater Units
requesting to partici-
pate in the network
exceeded the permitted
number of Repeater
Unit segments (two).
Subsequent Slave Unit participa-
tion is prohibited from the point
where it is detected that the per-
mitted number of Repeater Unit
segments has been exceeded in
the participation processing.
Other system operations con-
tinue. The error is registered in
the error history. After normal
status is restored, the Unit recov-
ers by being restarted.
The maximum number of
Repeater Unit segments is reg-
istered to two in the Master Unit
and cannot be changed. This
error thus indicates that there
are three or more Repeater Unit
segments. Correct the wiring
and restart the Master Unit.
---
Red
d 5
↓
yy
↓
zzz
Verification
error (non-
existent
Slave Unit)
0370
It was detected that a
Slave Unit registered in
the Registration Table
is not participating
within a fixed time after
power is turned ON to
the Master Unit. The
monitoring time is set
using the CX-Integra-
tor.
The error is registered in the
error history. System operations
all continue, and remote I/O
operations start. Participation of
the Slave Unit where the error
occurred continues to be moni-
tored. When Slave Unit participa-
tion is completed, normal status
is restored. (The NS indicator
lights green.)
If the error is not cleared, check
the Slave Unit that is not partici-
pating.
---
Red
d 6
↓
yy
Verification
error (unreg-
istered Slave
Unit) 0372
Participation of an
unregistered Slave Unit
was detected.
The error is registered in the
error history. All other system
operations continue, without the
participation of the unregistered
Slave Unit. Recovery is attained
by restoring normal status and
restarting the Unit.
Check and correct the status of
the unregistered Slave Unit, and
then restart the Master Unit.
---
Red
A0
Communica-
tions have
stopped due
to a commu-
nications
error.
0375
A communications
error was detected
while communications
were set to be stopped
when a communica-
tions error occurred.
The error is registered in the
error history. System operations
continue. Remote I/O communi-
cations with the Slave Units stop,
and communications with the
CPU Unit continue. There is no
automatic recovery even after
the cause of the error is
removed. The Unit must be
restarted to recover.
Check and eliminate the cause
of the error, and then restart the
Master Unit.
To Next Page
Loading...
