Objectives

At the end of this Section Participants will be able to:

Troubleshooting
Section 10
- Troubleshoot a wide variety of issues that are preventing the
system from running properly

Section 10 | Slide 2

The tenth section of the In-Sight EasyBuilder Standard training will focus on At the end of this section Participants will be able to:
Troubleshooting.
- Troubleshoot a wide variety of issues that are preventing the system from
running properly

Section 10 | Slide 1 Section 10 | Slide 2

 Troubleshooting Basics Diagnosing the Problem

The first question to ask is….

• Try to determine if the problem is confined to the In-
What has Changed since the last time the Sight unit
system worked?
• If it is the In-Sight, is it software or hardware related?

Section 10 | Slide 3 Section 10 | Slide 4

If something is not working as it should you can troubleshoot to determine the In order to diagnose the problem you must determine if the problem is confined to the
solution. In-Sight unit, and if so, is it software or hardware related.

Use this list as a guide to begin troubleshooting. - Try to determine if the problem is confined to the In-Sight unit.
- Can you replace it with a new / known good unit and the problem goes
- Start with the Hardware, then move to the Software away?
- Is it happening elsewhere on the line?
- Did someone touch the Hardware?
- Cabling re-wired - If it is the In-Sight, is it software or hardware?
- Lighting changed - Does a good system make the problem go away?
- Mounting adjusted - Have there been any other issues up to now?
- Is it doing basic functions like acquisition or outputs?
- Did someone change the software? - Is another line running the same application having similar problems?
- Tweak parameters
- Load a new program

- Is it possible to get back to a “pristine” system?

Section 10 | Slide 3 Section 10 | Slide 4

 Noting the Hardware Status Lights Noting the Hardware Status Lights

Power SD card User Network Error

status configurable activity

In-Sight 5000 & 7000

Series In-Sight 2000 Series and 7000 Gen II Series
In-Sight Micro

Section 10 | Slide 5 Section 10 | Slide 6

Check to make sure that power is applied to the system and the network is Check to make sure that power is applied to the system and the network is
connected. connected.

- 5000 & 7000 Series – The Power (middle) and Network Status (right) LEDs - 2000 Series and 7000 Gen II Series: power LED green, network LED
will be green. yellow
- Micro Series – The ENET (bottom) LED will be green.

Section 10 | Slide 5 Section 10 | Slide 6

 Environmental Effects Cleaning / Maintenance

Lighting and Optics can cause a system to fail. • Cleaning the Sensor Housing

• Is the light set-up as it should be?

• Cleaning the CCD Window

• Is the lens properly mounted?

Section 10 | Slide 7 Section 10 | Slide 8

Lighting and Optics can cause a system to fail. If the system is not clean or needs maintenance it can fail.

- Is the light set-up as it should be? - Cleaning the Sensor Housing

- Variations as to where it is pointing in regards to the camera - Clean outside with mild detergent or isopropyl alcohol on a cleaning cloth
- Intensity - Do Not pour directly on housing
- Color - Do Not use harsh or corrosive solvents, such as Lye, methyl ethyl ketone
- Ambient light being seen (MEK), or gasoline

- Is the lens properly mounted? - Cleaning the CCD Window

- Unfocused - Remove dust with a pressurized air duster (free from oil, moisture, or other
- Aperture incorrect contaminants)
- Debris on lens - Do Not touch the glass window
- For a tough smudge, use a cotton ball with ethyl alcohol and a little
pressure
- Do Not pour the alcohol directly on the window

Section 10 | Slide 7 Section 10 | Slide 8

 About In-Sight Explorer (Help Menu) Network Troubleshooting

Section 10 | Slide 9 Section 10 | Slide 10

The About In-Sight Explorer (Help Menu) displays the version and build
information, as well as hardware and network details about each In-Sight camera and
emulator detected on your network, including Explorer Host Table entries.
The In-Sight Network pane is a great starting point for the troubleshooting process.
If the In-Sight Network pane is not visible in your EasyBuilder view:
- Click View in the In-Sight Explorer toolbar.
- Click the In-Sight Network link.

Section 10 | Slide 9 Section 10 | Slide 10

 Network Troubleshooting Network Troubleshooting

Section 10 | Slide 11 Section 10 | Slide 12

The In-Sight sensor does not appear in the In-Sight Network pane. Ensure the sensor’s IP address is correctly configured.

- Click the Refresh button to make sure all units are being seen. - The basic IP address for the default Microsoft network is 192.168.0.X
- If the In-Sight sensor does not appear in the list, click the Add button. where X is equal to any number from 0 to 255. Do not use 0 or 255 in this
place as some systems reserve these numbers.

Section 10 | Slide 11 Section 10 | Slide 12

 Network Troubleshooting Network Troubleshooting

IP Address Detected

IP Address Not Detected

Section 10 | Slide 13 Section 10 | Slide 14

Ensure the sensor’s Subnet Mask is correctly configured. Ping the IP Address of the sensor to see if it is on the network.

- For the IP address of 192.168.0.X, the default subnet mask is - Open a command prompt and ping the IP address of the sensor. For
255.255.255.0. Use of 255 in the subnet mask means that the number in example, to ping a sensor with the IP address of 192.168.0.1, issue the
that placement must be the same on all devices; the use of 0 in the subnet following command: ping 192.168.0.1.
mask means that any number can be used.

Section 10 | Slide 13 Section 10 | Slide 14

 Network Troubleshooting arp –a Command Prompt

Section 10 | Slide 15 Section 10 | Slide 16

Confirm that the IP address of the In-Sight Explorer agrees with the actual IP address The arp command is a TCP/IP utility and Microsoft Windows command for viewing
of the PC running In-Sight Explorer. and modifying the local Address Resolution Protocol (ARP) cache, which contains
recently resolved MAC addresses of Internet protocol (IP) hosts on the network.
- Open a command prompt, type ipconfig, and note the IP address.
- On the Help menu of ISE, click About In-Sight Explorer. NOTE: The arp command is only available if TCP/IP is installed on the machine.
- Confirm that the PCHOST (emulator) IP address agrees with the IP
address noted from the ipconfig command.

Section 10 | Slide 15 Section 10 | Slide 16

 Properties Sensor Status View

Section 10 | Slide 17 Section 10 | Slide 18

The In-Sight Network pane is a ‘tree’ containing all of the In-Sight vision systems, and Right click on the camera in the In-Sight Network menu and select Show Sensor
emulators automatically detected on the subnet (including any enabled and Status View. The Sensor Status View displays information contained within the
configured RAM Disk folders), as well as any hosts that have been entered manually memory buffers that make up the Machine Status Stack.
into the Explorer Host Table. The In-Sight Network pane offers a great deal of
flexibility when managing multiple In-Sight devices at once. The In-Sight Explorer’s Sensor Status View shows the current Machine Status
information.
Right click on the camera in the In-Sight Network menu and select Properties. This
will display details of the vision system’s hardware information and network
identification, as well as the vision system’s flash and RAM memory configuration.

Note: This is the ONLY place in In-Sight Explorer that you can copy the entire IP
address.

Section 10 | Slide 17 Section 10 | Slide 18

 Firewalls Virus Protection Software

Section 10 | Slide 19 Section 10 | Slide 20

- Firewalls can sometimes block connection to the camera from the PC. Virus Protection Software can also interfere with the operation of In-Sight Explorer
- For troubleshooting – disable the firewall to confirm connection. and your ability to detect In-Sight sensors on the network.
- During normal operation – firewall can be on with ports 1069 and 1212
enabled.

Section 10 | Slide 19 Section 10 | Slide 20

 In-Sight Ports Summary

Port
Service
Number • The first step in troubleshooting is to determine what
TCP 21 FTP
has changed since the last time the system ran
TCP 23 Telnet
successfully.
UDP 68 DHCP (In-Sight Vision System Only)
TCP 502 Modbus
TCP 1069 In-Sight Protocol • The In-Sight Explorer Network is where you will find
UDP 1069 In-Sight Discovery important information about the sensor that can help
TCP 1070 Machine Status Data in the troubleshooting process.
UDP 2222 EtherNet/IP
TCP 5753 Audit Message Server
TCP 8087 Web HMI HTTP (Default)
TCP 8443 Web HMI HTTPS (Default)
UDP 45237 Base SLMP messaging (GetCommunicationSetting)
TCP 44818 EtherNet/IP
UDP 44818 EtherNet/IP

Section 10 | Slide 21 Section 10 | Slide 22

The ports used for In-Sight communications are listed above. In this section we covered the following topics:

- The first step in troubleshooting is to determine what has changed since

the last time the system ran successfully
- The In-Sight Explorer Network is where you can find important information
about the sensor that can help in the troubleshooting process.

Section 10 | Slide 21 Section 10 | Slide 22

 Skills Journal Lab Exercise

Complete:
Section 10
Skills Journal

Section 10 | Slide 23

Complete:
Skills Journal (image designed by pngtree)
Lab Exercise

Section 10 | Slide 23