Table of Contents
Advertisement
2-13 Troubleshooting
2
32
No.
Symptom
Probable causes
7) Wrong IP address,
subnet mask or
gateway settings on
controller.
8) Ethernet unit is
defective
2
Cannot make
1) Wrong IP address
TELNET connection
used during Telnet
or cannot terminate
connection
the TELNET
connection right
2) Wrong Port No.
away. (ping reply is
used during
normal).
TELNET
connection.
3) Robot control is
already logged in
with another
TELNET terminal.
4) Alarm issued to
controller.
5) IP address is the
same as another
network device.
6) Network traffic
(communication
data load) is too
heavy.
3
An OK does not
1) Ethernet unit is not
come back after
enabled and not
login, or no replay
identified
comes back even
(recognized) by
after issuing a
controller.
command. (Some
2) I/O custom
unit control
command input
commands are
signal is set ON.
useable such as
LOGOUT or BYE.)
3) Commands such as
origin return, axis
movement
commands, or data
write commands are
being run from I/O
or RS-232C.
Checkpoints
• Check the settings by
• Redo the IP address, subnet mask and
referring to "2-4-2 Setting the
gateway settings correctly. Then turn on
IP address", "2-4-3 Setting
the controller power again.
the subnet mask", and "2-4-4
Setting the gateway".
• Try substituting the Ethernet
• If operation returns to normal, then the
unit.
Ethernet unit is probably defective, so
replace the Ethernet unit.
• Check that the IP address of
• Enter the correct IP address.
the robot controller you are
attempting to connect with is
correct.
• Check that the port No. of the
• Enter the correct IP address.
robot controller you are
attempting to connect with is
correct.
• When connected, the message
• Await termination of current TELNET
"telnet is already used!"
connection.
appears.
• Alarm message appears when
• Troubleshoot according to the type of
connected.
alarm.
• Connect the programming
box and check for an alarm.
• Status led is lit up in red.
• Check if the IP address and
• If the IP address and MAC address do not
MAC address have a correct
match each other, then the IP address is
match by using the "arp"
wrong, so try redoing the settings.
command incorporated in the
OS.
• Check all devices on the
• If found to be the same as another device,
network to find if the same IP
change the setting.
address is being used.
• Check if the traffic load is
• Change the network structure to get a
appropriate.
smaller traffic load.
• See "2-4-1 Validating the
• Enable the Ethernet unit and turn on the
Ethernet unit" and check if
power to the controller again.
the Ethernet unit is enabled.
• Check the I/O signal (Check
• Always use a pulse input for the custom
on the sequencer monitor,
command input.
etc.)
• Communication error is
issued when the programming
box is connected to controller.
• Reply comes back after axis
• When issuing TELNET commands, do not
movement or writing data.
run commands from the I/O or RS-232C.
Action
Advertisement
Table of Contents
