User Guide

427-0075-01-12 Revision 140 October 2019 54
This document does not contain any export-controlled information.
Basic Operation and Configuration
the day due to solar loading. Greater temperature differences in the scene generally will allow the
camera to produce higher-contrast imagery.
Performance may also be affected when objects in the scene are wet rather than dry, such as on a
foggy day or in the early morning when everything may be coated with dew. Under these conditions,
it may be difficult for the camera to show the temperature the object itself, rather than of the water
coating.
Unable To Communicate Over Ethernet: 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 camera IP address is shown on the Analog Visible Video monitor after
approximately 90 seconds.
Confirm that the IP address for the PC is on the same network as the camera.
By default the camera will broadcast a discovery packet two times per second. Use the FLIR
Discovery Network Assistant (DNA) a packet sniffer utility such as Wireshark and confirm the
packets are being received by the PC from the camera.
Determine if Windows Personal Firewall is blocking the packets. Turn off the firewall or add an
exception for the client program. Typically when a program runs for the first time, a pop-up
notification may ask for permission to communicate on the network. Select the check boxes
(domain/private/public) that are appropriate for the network.
Unable to View Video Stream: If the video stream from the camera is not displayed in a client
program, it could be that the packets are blocked by the firewall, or there could be a conflict with
video codecs that are installed for other video programs.
When displaying video with FLIR Latitude or a VMS for the first time, the Windows Personal Firewall
may ask for permission to allow the video player to communicate on the network. Select the check
boxes (domain/private/public) that are appropriate for the network.
If necessary, test to make sure the video from the camera can be viewed by a generic video player
such as VLC media player ( ). To view the video stream, specify RTSP
port 554 and the appropriate stream name. For example:
rtsp://192.168.0.250:554/stream1/sensor2.
In addition, to maintain compatibility with legacy systems the stream names are aliased as:
ch0 = stream1/sensor1, ch1 = stream2/sensor1, ch2 = stream1/sensor2, and ch3 = stream2/
sensor2.
The video streams can be accessed with the shortened strings, such as rtsp://192.168.0.250/ch0.
Refer to .
Noisy image: A noisy image is usually attributed to a cable problem (too long or inferior quality) or
the cable is picking up electromagnetic interference (EMI) from another device. Although coax cable
has built-in losses, the longer the cable, or the smaller the wire gauge, the more severe the losses
become; and the higher the signal frequency, the more pronounced the losses. Unfortunately this is
one of the most common and unnecessary problems that plagues video systems in general.
Cable characteristics are determined by a number of factors (core material, dielectric material and
shield construction, among others) and must be carefully matched to the specific application.
Moreover, the transmission characteristics of the cable will be influenced by the physical
environment through which the cable is run and the method of installation.