Network Troubleshooting

CAUTION: The Add Sensor/Device to Network dialog overwrites your proc.set file if you choose to reset vision system settings to the factory defaults. For more information, see Add Sensor/Device to Network Dialog.

Install the In-Sight Explorer Software

Ensure you have local administrative rights when installing the In-Sight software on a PC.
Make sure all firewalls and antivirus software are disabled. For more information, see Firewalls.

Assign the IP Address

The In-Sight vision system is factory-configured with DHCP enabled. If your network does not have a DHCP server, use the Add Sensor/Device to Network dialog to assign the vision system a static IP address. For more information, see Add Sensor/Device to Network Dialog.

Note: Use DHCP only if you have a DHCP server on your network. When installing the vision system to an existing network, consult your network administrator to determine whether a DHCP server is available.

Migrating Vision Systems to a Different Network

If you have set up all your vision systems and need to change the IP addresses to a new network (such as deployment to a production line), use the Add Sensor/Device to Network dialog to change network settings for the vision systems. For more information, see Add Sensor/Device to Network Dialog.

Note: The PC needs to remain on the original network to recognize the vision systems and modify their IP addresses.

The PC is on a Different Subnet than the Vision System

If the vision system is configured to operate on a different subnet than the PC running In-Sight Explorer, the host name and IP address of the vision system must be entered in the Explorer Host Table before it will appear in the In-Sight Network pane. For more information, see Explorer Host Table Setup Dialog.

Unable to Connect to the Vision System When Directly Connected to the PC

Ensure the correct type of Network Cable is used.

Most In-Sight 5000 series vision systems have an Autosense capability, allowing the vision system to connect directly to a PC using either a straight-pinned network cable or a crossover cable. If your vision system does not have the Autosense capability, a crossover cable or a crossover coupler combined with a straight-pinned network cable can be used. To determine the correct configuration for your vision system, refer to the Part Number label on the back of your vision system. If the Part Number is P/N 800-5828, the vision system does not have the Autosense capability.
Ensure the PC has a Connection to the Network

When you plug the vision system's network cable into the PC's network card, a network connection icon should appear in the notification area at the bottom right of your screen. If the network connection icon does not appear, ensure the network cable is securely plugged in and in good working order.
Disable the Microsoft Media Sense Feature on the PC

If the Microsoft "Media Sense" feature (which automatically detects whether or not your network interface is linked to a network) is enabled, communication with a vision system may not be established. It is recommended to use a hub or switch with a standard Ethernet cable to configure the vision system or configure your PC to disable the Media Sense feature. See Microsoft Knowledge Base article 239924 for details on this process.

Unable to connect to the Vision System when Connected to a hub or switch

Note: A switch is the preferred networking method.

Ensure the network and power cables are properly connected to the switch and are in good working order; when the network cable is inserted into an Ethernet port on the switch, a small green light indicates that a connection is made on that port.
Verify that the 24VDC and ENET LEDs light up on the back of the vision system.
Ensure the switch does not have any additional functionality enabled, such as blocking ports or filtering.

The Vision System Does not Appear in the In-Sight Network Pane

Note:

After completing each of the following steps, click Refresh on the View menu to repopulate the In-Sight Network.
If each of the following methods fail, use the Add Sensor/Device to Network dialog to reconfigure the network settings of the vision system. For more information, see Add Sensor/Device to Network Dialog.

Ensure that power is applied to the vision system and that network communication is functioning.

Ensure that power and Ethernet cables are securely plugged into the vision system. To ensure that the vision system is receiving power and that a network connection is detected, verify that the 24VDC and ENET LEDs light up on the back of the vision system.
Ensure the vision system's IP address is correctly configured.

The basic IP address for the default Microsoft network is 192.168.0.x where x is equal to any number from 0 to 255. Do not use 0 or 255 in this placement as some systems reserve these numbers.
Ensure the vision system's subnet mask is correctly configured.

For the IP address of 192.168.0.x, the default subnet mask is 255.255.255.0.
- Use of 255 in the subnet mask means that the number in that placement must be the same on all devices.
- Use of 0 in the subnet mask means that any number can be used.
  
  For example, if a PC is assigned an IP address of 192.168.1.24 with a subnet mask of 255.255.255.0, and the vision system's IP address is 192.168.0.98, the PC will not automatically recognize the vision system because the third digit in the IP addresses do not match.
Ping the IP address of the vision system to see if it is on the network.

Open a command prompt and ping the IP address of the vision system. For example, to ping a vision system with the IP address of 192.168.0.1, issue the following command: ping 192.168.0.1. If you receive a message stating Request timed out, the specified IP address is not detected on the network.

Note: You may have to power down the vision system to see if any other devices are using the same IP address. IP addresses must be unique on the network.

Cannot Connect to the Local Emulator

Error 6003: Could not start the emulator. For more information, see Error Messages.

In-Sight Explorer is Detecting the Wrong IP Address for the PC

Open In-Sight Explorer.
Connect to your emulator.
From the Sensor menu, click Network Settings.
Locate the IP address of your emulator.

If the IP address is 127.0.0.1, your network card might be bad.

If the IP address is incorrect, In-Sight Explorer might have detected an alternate network card (such as a wireless network card). In-Sight Explorer uses the IP address of the network card used at startup on the PC. If multiple network cards are installed on the PC, you may need to change the binding order of the network cards. In-Sight uses the IP address at the top of the list.

The IP Address and Subnet Mask Allow Only 2 Digits

This is an artifact of the display settings on the PC.

Different Ports Available

A valid port assignment is any unused number between 1 and 65535, except for ports reserved for In-Sight communications. In-Sight emulator users should always assign port numbers 3000 (the default) and higher to prevent potential conflicts with ports reserved by services on the PC. For more information, see In-Sight Ports.

Unable to Update Firmware on the Vision System

Most firmware update problems are indicative of a firewall issue. Ensure that all firewalls are disabled. For more information, see Firewalls.

Unable to Transfer a File

Verify that another application is not controlling the FTP port

Close In-Sight Explorer.
Open a command prompt and issue the following command: netstat -a.
Look for an active TCP connection listening on port 21 (for example, "TCP 0.0.0.0:21"). This would indicate that an application (such as an FTP server) is using the default FTP port 21; in this case, the application must be stopped, or the port number must be changed.

A common application that might be using port 21 is the Windows Internet Information Services (IIS). Following are instructions about how to verify that IIS is not using this port on Windows 7/Windows 10.