AutomationDirect logoTroubleshooting Guide: WinPLC, RuntimePC & Windows NT 4.0


Symptoms:
You are unable to find your Think & Do WinPLC using "Find CE Runtime..." option from ProjectBinder or ESP.

Possible Cause(s):

  1. Bad or wrong Ethernet cable.
  2. The Subnet Mask of the WinPLC and on your PC does not match.
  3. Conflicting IP Address.
  4. The DHCP Server is unavailable or your PC is not connected to the network.

Resolution:

  1. If the Link LED is off on the WinPLC you have a bad or wrong Ethernet cable, which needs to be replaced.
  2. Correct the Subnet Mask or assign a static IP address and Subnet Mask to your PC.

Symptoms:
You can find your Think & Do WinPLC, using "Find CE Runtime…" option from ProjectBinder, but you are unable to download to the WinPLC or you are unable to scan the WinPLC using IOView.

Possible Cause(s):

  1. LMHOSTS File lookup is disabled.
  2. "Enable IP Forwarding" is disabled.
  3. You do not have administrator privileges on Windows NT.

Resolution:

  1. The LMHOSTS lookup option must be enabled in the TCP\IP Protocol configuration. Select Settings ... Control Panel from the Start Menu. Double-click on the Network Icon. . Select the Protocols tab and double-click TCP\IP Protocol. Select the WINS Address tab and place a check in the Checkbox next to "Enable LMHOSTS Lookup". Select the OK button and you will have to reboot your computer in order for the changes to take affect.
  2. If the system has two or more Ethernet cards, "Enable IP Forwarding" needs to be enabled. This is down in the TCP/IP Properties on the routing tab.
  3. Log On to Windows NT as the administrator or a user with administrator privileges.

Symptoms:
When you start to download and run your project, there is a long pause, about 3-5 seconds, before you see the files being download. Or it takes approximately 5-10 seconds before ESP connects to the WinPLC.

Possible Cause(s):
Your PC may normally be connected to a network where a DNS Server exists and your PC relies on the DNS Sever for HOSTS name resolution. When you are not connected to the network, your computer waits for a response from the DNS Server in which it will not receive a reply. This time period can last anywhere between 6-12 seconds.

Resolution:
If you are not connected to your network at the time you would like to communicate to the WinPLC, you should remove the DNS Server(s) IP Address from your TCP\IP configuration. Select Settings ... Control Panel from the Start Menu. Double-click on the Network Icon. . Select the Protocols tab and double-click TCP\IP Protocol. Select the DNS tab and look for IP addresses in the "DNS Service Search Order" list. Record any IP addresses listed, so you may re-enter them later, then remove all IP addresses in the list. Reboot your computer and download your project again to verify that this resolves your problem.


Symptoms:
You can use the "Reset Using IPX" option to find and configure a WinPLC but can not see it when using the "Find CE Runtime.." option.

Possible Cause(s):
The Default Gateway is not set on the WinPLC.

Resolution:
When using a PC with one or more Ethernet cards, the WinPLC's Default Gateway needs to be set to the IP address of the Ethernet card to which it is connected.