Yaskawa MP940 Hardware Manual - Manual (Page 38)

MotionSuite™ MP940 Machine Controller Hardware Manual Section 5: Communications
35
„ Slave
Troubleshooting Slaves
Indicators Problem Probable Cause Possible Solution
MS not lit
NS lit No DeviceNet
communica-
tions No power
supply to
MP940D Check the network power supply to the MP940D.
MS red lit
NS not lit Hardware
malfunction Replace the MP940D.
MS red lit
NS red lit Hardware
malfunction Replace the MP940D.
MS green lit
NS red lit Duplicate
MAC ID (1) Change the MAC ID address for the MP940D and
cycle the power
(2) Change the MAC ID addresses for other DeviceNet
devices and cycle the power to the MP940D.
Bus-OFF (1) Check the wiring and connections for DeviceNet
cables and connectors.
(2) Check the power supply voltage and connections for
communications power.
(3) Check for network power supply voltage on the
DeviceNet connector of the MP940D (11 to 24V).
(4) Check the baud rate for each DeviceNet device on the
network.
(5) Check the terminator (121
Ω) and connection status.
(6) Check the length of the network.
(7) Replace the MP940D. Then, either cycle the power
for the MP940D or disconnect and reinsert the DeviceNet
connectors.
MS green lit
NS not lit Communica-
tions power
supply error (1) Check the wiring and connections for DeviceNet
cables and connectors.
(2) Check the power supply voltage and connections for
network power.
(3) Check the communications power supply voltage on
the DeviceNet connector of the MP940D (11 to 24V).
(4) Check the terminator (121
Ω) and connection status.
MS red lit
NS not lit DeviceNet
network error (1) Check the wiring and connections for DeviceNet
cables and connectors.
(2) Check the baud rate for each device.
(3) Check the terminator (121
Ω) and connection status.
(4) Check the operation status of the DeviceNet master.
(5) Replace the MP940D.
MS green lit
NS green flash-
ing Connection not
established
with
DeviceNet
device (1) Check the DeviceNet master scan list settings.
(2) Check the wiring and connections for DeviceNet
cables and connectors.
(3) Check the baud rate for each device.
(4) Check the operation status of the DeviceNet master.