480
Troubleshooting
Section 12-5
12-5-3 Troubleshooting Communications Errors
The following troubleshooting flowchart is for when MECHATROLINK commu-
nications errors occur.
Use this flowchart to determine the cause, such as whether the error is due to
MECHATROLINK communications settings or installation.
N
Y
N
N
Y
Y
N
Y
N
Y
N
Y
N
Y
N
Y
N
Y
An error in MECHATROLINK
communications has occurred.
RUN indicator: Lit
ERC indicator: Flashing
ERM indicator: Lit
Is the Unit Error Flag
turned ON?
Is the Error Flag
turned ON?
Check the error code for the
corresponding axis. Has the
Synchronous Communications Alarm
(3010) occurred?
Check the error code for the
corresponding axis. Has a
Communications Alarm (3011)
occurred?
Check the error code for the
corresponding axis. Has a Command
Timeout (3012) occurred?
Has the error occurred
in all axes?
Has the error occurred in the
corresponding axis only?
Check the Unit error code. Has an
MLK Initialization Error (0020)
occurred?
Check the Unit error code. Has an
MLK Communications Error
(0025) occurred?
Illegal data is set in
the PCU or an
illegal operation was
executed.
Check the Unit Error
Flag and Error
Flags.
Check the Unit for
which the Error Flag
is ON or the axis
error code and clear
the error according
to the method
shown in the list of
error codes.
Check the Error Flags for
all axes being used,
check the axes in which
the MECHATROLINK
communications error
occurred, and then follow
the steps in the
troubleshooting flowchart
related to
communications again.
(MECHATROLINK
communications errors
are given a high level of
priority among axis
errors and are indicated
by the indicator display in
order of priority.)
No MECHATROLINK
communications re-
sponse has been re-
ceived from the corre-
sponding axis. Check
that no error has occur-
red in the MECHATRO-
LINK device connected
to the corresponding ax-
is.
Release the connection
and execute CONNECT
again to enable the
PCU to recover.
If the error has occurred
in all the axes connected
before the specified axis,
the probable cause of
the error is in the
communications line
between the specified
axis and the immediately
previous (normal) axis.
Check that there are no
disconnections, faulty
contacts or breaks in the
communications cable.
Release the connection
and execute CONNECT
again to enable the PCU
to recover.
The probable cause is
due to the external envi-
ronment such as noise
or an interruption to the
MECHATROLINK de-
vice power supply, pre-
venting the correspond-
ing axis from
communicating normal-
ly. Check the installation
environment and
grounding status of the
MECHATROLINK de-
vice for the correspond-
ing axis. Release the
connection and execute
CONNECT again to en-
able the PCU to recov-
er.
MECHATROLINK
communications are not
being performed normally
due to disconnections,
faulty contacts, or breaks
in the terminating
resistance or
MECHATROLINK
communications cables.
Check the
communications
connection conditions.
Release the connection
and execute CONNECT
again to enable the PCU
to recover.
Check the Unit
Error Flag and Unit
error code again.
If the problem
occurs again, the
probable cause is a
faulty PCU. Replace
the PCU.
Summary of Contents for CJ1W-MA - REV 10-2008
Page 3: ...iv ...
Page 5: ...vi ...
Page 21: ...xxii ...
Page 57: ...30 Starting Operation Section 2 2 ...
Page 97: ...70 Wiring Section 3 4 ...
Page 247: ...220 Transferring Servo Parameters Section 5 3 ...
Page 281: ...254 Standard Settings for Servo Drives Using MECHATROLINK Section 6 4 ...
Page 343: ...316 Absolute Encoder Origin Section 8 6 ...
Page 375: ...348 Linear Interpolation Section 9 7 ...
Page 423: ...396 DEVIATION COUNTER RESET Section 10 10 ...
Page 631: ...604 Additional Functions for the CJ1W NCF71 MA Appendix F ...
Page 641: ...614 Index ...
Page 643: ...616 Revision History ...