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