Yamaha ERCX Manuel D’Utilisation

32

CHAPTER2  Ethernet Unit

When problems occur, then troubleshoot as needed by using the following information
as a guide. Be sure to always also refer to sections on “Troubleshooting” in the controller
user’s manual as well as the instruction manual for the other party’s equipment such as
PCs or HUB peripheral devices. If taking the troubleshooting steps listed there does not
eliminate the problem, then quickly contact your local YAMAHA sales dealer.

• Disconnect the controller from the 

network and connect the PC instead. 
(Use a PC capable of a good 
connection with the network. Make the 
same IP address, subnet mask and 
gateway settings as used on the 
controller.) 
Now try running “ping” from the client 
while setup as above, and check for a 
response.

• Check if securely attached to the 

modular connector. 

• Check for a disconnection (or break) in 

the cable or a miswire.

• Check if the straight-through cable or 

crossover cable are being used for the 
wrong connection.

• Try replacing the cables. 

• Try changing to another port.
• Check if the communication mode is 

manually set to other than 10Mbps/Half 
Duplex.

• Try another HUB

• Check the router settings.
• Try substituting with another router.

• Check the network settings on the 

client side.

• Try substituting with another network 

adapter on the client side.

• Check if the traffic load is appropriate.

• Check how and where the Ethernet 

cables are installed.

• If timeouts still occur when connected 

this way (using PC instead of 
controller), then the problem is on the 
client side or in the HUB peripheral 
device. (Check probable causes 1 
through 6.)

• If a replay comes back normally, then 

the problem is in the controller, so 
check probable causes 7 through 8.

• Insert in firmly until a click noise is 

heard.

• Correct the wiring if a miswire is 

found. Replace the cable if a break in 
the wiring is found.

• Use a straight-through cable between 

the HUB and controller. Use a 
crossover cable if connecting directly 
to the other party’s device.

• If operation returns to normal, then the 

problem is in the cables. Replace the 
cable.

• If operation returns to normal then the 

port is defective, so do not use that 
port.

• When setting the HUB communication 

mode manually, then set it to 
10Mbps/Half Duplex.

• If operation returns to normal then the 

HUB is defective, so replace the HUB.

• Redo the router settings.
• If operation returns to normal then the 

router is defective so replace the 
router.

• Redo the network settings on the client 

side.

• If operation returns to normal then the 

network adapter is defective so replace 
the adapter.

• Change the network structure to get a 

smaller traffic load.

• Separate the Ethernet cable from 

potential noise sources.

1

Ethernet cable 
defects, poor 
connection, or 
wrong specs. 

Defective HUB 
or wrong settings

Router is 
defective or 
wrong settings

Network adapter 
used by the client 
is defective or the 
settings on the 
client side are 
wrong.
Network traffic 
(communication 
data load) is too 
heavy.
Ethernet cable is 
too close to a 
noise source such 
as motor cables.

1)

2)

3)

4)

5)

6)

Cannot make 
TELNET 
connection. 
(Using “ping” 
only results in 
a timeout.)