There could be a few reasons for this problem. I assumed it worked in the past which means that either something broke or something has changed. After making sure the cable is connected at both ends you can verify the settings by the following steps:
The Ethernet card should have a static IP address set with an appropriate mask. To get the IP addresses (one for the controller and one for the computer) start PC-DMIS, switch to RS-232 when prompted, then select Edit - Machine Interface setup and press the terminal button at the top right of the dialog that appears. Enter the command SHOW HOST_IP then press return. The first 4 digits of the 6 digit number is the IP address of the computer. Then enter the command SHOW CNTRL_IP and press return. The first 4 digits of the 6 digit number is the IP address of the controller.
Once you have this information open the settings for the network card that the controller is plugged into and make sure it is setup with a static IP address as shown from the HOST_IP command. The net mask may be 255.255.255.0 or 255.255.0.0 (one of them will work).
Once this is setup then verify the settings in the 'Machine Interface Setup' of PC-DMIS. The IP address should be the value returned from CNTRL_IP. The port number is always 2001.
You can verify the connection to the controller by opening a command prompt and type PING <IP_ADDRESS_OF_CONTROLLER> and it should return a round trip time (as opposed to 'not reachable').
Make sure the Ethernet cable is plugged into the computer and controller. When you plug the cable into the computer you should see a couple of LED's light up next to the connector. If you don't then maybe the other end of the cable is not plugged in OR something is wrong at the other end of the cable.
A bad Ethernet cable could cause this kind of problem but it is rare. Even more rare is a bad Ethernet card in the computer. There are ways to test these items without a lot of effort.
There could be a few reasons for this problem. I assumed it worked in the past which means that either something broke or something has changed. After making sure the cable is connected at both ends you can verify the settings by the following steps:
The Ethernet card should have a static IP address set with an appropriate mask. To get the IP addresses (one for the controller and one for the computer) start PC-DMIS, switch to RS-232 when prompted, then select Edit - Machine Interface setup and press the terminal button at the top right of the dialog that appears. Enter the command SHOW HOST_IP then press return. The first 4 digits of the 6 digit number is the IP address of the computer. Then enter the command SHOW CNTRL_IP and press return. The first 4 digits of the 6 digit number is the IP address of the controller.
Once you have this information open the settings for the network card that the controller is plugged into and make sure it is setup with a static IP address as shown from the HOST_IP command. The net mask may be 255.255.255.0 or 255.255.0.0 (one of them will work).
Once this is setup then verify the settings in the 'Machine Interface Setup' of PC-DMIS. The IP address should be the value returned from CNTRL_IP. The port number is always 2001.
You can verify the connection to the controller by opening a command prompt and type PING <IP_ADDRESS_OF_CONTROLLER> and it should return a round trip time (as opposed to 'not reachable').
Make sure the Ethernet cable is plugged into the computer and controller. When you plug the cable into the computer you should see a couple of LED's light up next to the connector. If you don't then maybe the other end of the cable is not plugged in OR something is wrong at the other end of the cable.
A bad Ethernet cable could cause this kind of problem but it is rare. Even more rare is a bad Ethernet card in the computer. There are ways to test these items without a lot of effort.
