Table of Contents
Advertisement
Nexus Configuration Guide
2—Verify Camera Operation with FSM
2.4
Troubleshooting Tips
If you need help during the installation process, contact your local FLIR representative or, call
877-773-3547 inside the US.
Before using serial communications, it may be necessary to configure the camera's serial
interface to operate with the other serial device. For more information, refer to section 4.6
"Serial Remote" on page 4-6.
2.4.1
Camera not discovered
By default the camera will broadcast a "discovery" packet two times per second. When FSM
starts up, it listens to the network for the discovery packets. If no cameras are listed in the
Discovered Servers list, press the Refresh button. If the list is still empty, it indicates no
discovery packets were received. This could be due to a wide variety of problems with the
network, the PC, or the camera.
First check to ensure the physical connections are intact and that the camera is powered on
and providing analog video to the monitor. When the camera is turned on, confirm the startup
information is displayed on the analog monitor after approximately 90 seconds. For example:
S/N: 1234567
IP Addr: 192.168.250.116
PelcoD (Addr:1): 9600 SW
Confirm that the IP address for the PC (for example, 192.168.250.1) is on the same network
as the camera.
Next determine if Windows Personal Firewall is blocking the packets. You can turn off the
firewall or add an exception for the FSM program. Typically when FSM runs for the first time, a
pop-up notification may ask for permission to allow the FLIR Sensors Manager (fsm.exe) to
communicate on the network, as in the following notification. Select the check boxes that are
appropriate for your network.
If necessary, use a packet sniffer utility such as Wireshark to capture packets and confirm the
packets are being received by the PC from the camera.
427-0030-00-28, version 100
January 2012
2-5
Advertisement
Table of Contents
