Hardware manual

Impact Reference Guide Troubleshooting
6-49 Datalogic Automation Inc.
Reconnect the cable between the PC and/or switch and the device
Check the device’s Ethernet status light, it should be on steady, not blinking
The IP addresses and/or IP masks for the PC and Impact device are incompatible
Change the IP address or IP mask on the PC or device to be compatible (see “TCP/IP Settings” on
page 6-28 and “IP Address Configuration” on page 1-3)
The device does not respond to a "ping" from the PC
Check power to the device
Check the cable connections
Temporarily connect a different device to the same cable and try the "ping" again
Firewall exceptions for the Impact Java bin directory and the emulator directory are not defined
Define the exceptions as described in the Configure PC Firewall section of the Readme file
The device or the PC has an older version of Impact software installed
Install the most recent version (8.3.0 or greater)
When antivirus software and the firewall on the PC are temporarily disabled, the device appears in the
device connection list
Adjust the firewall or antivirus software settings to allow the Impact device ports to be used (see
“Impact software TCP Ports” on page 6-28)
Please note that Datalogic cannot guarantee the performance of M-Series systems which have addi-
tional software installed on them, including, but not limited to, anti-virus and firewall software.
Datalogic recommends that M-Series systems remain disconnected from networks that access the
Internet in order to minimize security risks. Datalogic will attempt to support systems with anti-virus
software installed, but we cannot guarantee system performance.
Issue: Message is No Camera Connected
The message "No Camera Connected" is displayed.
Things to check
The camera is not an Impact or a Datalogic-supported third-party camera. When you look at the sys-
tem log you will see one of these entries: "GigE Camera: Can not connect to camera. It is not a Data-
logic camera" or "GigE Camera: Can not connect to unknown or unlicensed camera."
The camera is configured with a subnet that happens to be the same subnet used by IMPACTDevice
programs (192.168.0.x). The automatic address re-assignment will fail because there are multiple
routes to the camera. This should be rare, because cameras come from Datalogic with 172.31.x sub-
nets.
Re-assign the IMPACTDevice subnets using Settings/General or by editing the NetworkInter-
face.txt files, then restart IMPACTDevice. It should successfully re-assign the camera to the CAMx
network. Finally, reset the IMPACTDevice subnet to the original settings.
M-Series Processor does not have a specific environment variable set.
Using the Windows Control Panel System option, set an environment variable named
PYLON_SUPPORT_ 3RDPARTY equal to 1.
The Network connections named CAM1, CAM2, CAM3, and/or CAM4 were changed to something
else
Change the connection names back to the correct name.
Issue: Could not Start On-screen keyboard