Nexus IP Camera Configuration Guide - Flir Systems

Nexus IP Camera
Configuration Guide
FLIR Commercial Systems, Inc.
70 Castilian Drive
Goleta, CA 93117
Phone: 888.747.FLIR (888.747.3547)
International: +1.805.964.9797
www.flir.com
Document Number: 427-0030-00-28
Version: 100
Issue Date: January 2012
This document is controlled to FLIR Technology Level 1. The information contained in this document pertains to a dual use product controlled for
export by the Export Administration Regulations (EAR). FLIR trade secrets contained herein are subject to disclosure restrictions as a matter of law.
Diversion contrary to US law is prohibited. US Department of Commerce authorization is not required prior to export or transfer to foreign persons
or parties unless otherwise prohibited.

Nexus Configuration Guide
© FLIR Commercial Systems, Inc., 2011. All rights reserved worldwide. No parts of this manual, in whole or in part,
may be copied, photocopied, translated, or transmitted to any electronic medium or machine readable form without the
prior written permission of FLIR Commercial Systems, Inc.
Names and marks appearing on the products herein are either registered trademarks or trademarks of FLIR
Commercial Systems, Inc. and/or its subsidiaries. All other trademarks, trade names, or company names referenced
herein are used for identification only and a100re the property of their respective owners.
This product is protected by patents, design patents, patents pending, or design patents pending.
The Nexus thermal imaging system is controlled by US export laws. There are special versions of this system that are
approved for international distribution and travel. Please contact FLIR Systems if you have any questions.
FLIR Commercial Systems, Inc.
70 Castilian Drive
Goleta, CA 93117
Phone: +1.888.747.FLIR (+1.888.747.3547)
http://support.flir.com/
http://www.flir.com/training
-ii January 2012 427-0030-00-28, version 100

1 Nexus IP Camera Configuration
Table of Contents
1.1 Warnings and Cautions ....................................................................... 1-1
1.2 Introduction ....................................................................................... 1-2
1.3 Nexus IP Camera ................................................................................ 1-2
1.4 Camera Configuration .......................................................................... 1-2
1.5 Serial and/or IP Communications ......................................................... 1-3
1.6 Serial Communications ....................................................................... 1-3
1.7 System Information Displayed at Startup ................................................ 1-4
1.8 FLIR Certified Systems Integrator (FCSI) Training ..................................... 1-4
2 Verify Camera Operation with FSM
2.1 Power and analog video ....................................................................... 2-1
2.2 Verify IP Communications ..................................................................... 2-1
2.3 Using FLIR Sensors Manager (FSM) ...................................................... 2-2
2.3.1 Running FSM ............................................................................. 2-2
2.4 Troubleshooting Tips ........................................................................... 2-5
2.4.1 Camera not discovered ................................................................ 2-5
2.4.2 Unable to control the camera ....................................................... 2-6
2.4.3 General Errors ........................................................................... 2-7
2.4.4 Unable to View Video Stream ........................................................ 2-7
2.5 Restoring the Factory Network Settings ................................................. 2-9
3 Web Configuration Tool
3.1 Web Configuration Overview ................................................................. 3-1
3.1.1 Web Configuration Tool login ........................................................ 3-1
3.1.2 Saving Configuration Changes ....................................................... 3-3
3.1.3 Restarting the Server .................................................................. 3-3
4 Nexus Camera Configuration
4.1 IP Communications ............................................................................. 4-1
4.1.1 IP Configuration Steps ................................................................. 4-1
4.2 Basic Web Configuration ..................................................................... 4-2
4.3 Settings ............................................................................................ 4-2
4.4 LAN Settings ..................................................................................... 4-3
4.4.1 D-Series LAN Settings ................................................................. 4-4
4.5 Server Status ..................................................................................... 4-5
4.5.1 Setting the Date and Time ............................................................ 4-5
4.5.2 Software Upgrades ..................................................................... 4-5
427-0030-00-28, version 100 January 2012 -iii

Nexus Configuration Guide
4.5.3 Rebooting the Camera ................................................................. 4-5
4.6 Serial Remote .................................................................................... 4-6
4.6.1 Serial Extensions ........................................................................ 4-7
4.6.2 Preset Map File .......................................................................... 4-7
4.6.3 AutoPan Function ....................................................................... 4-8
4.7 Network Remote / VMS ..................................................................... 4-9
4.7.1 ONVIF ....................................................................................... 4-9
4.8 Video IR .......................................................................................... 4-10
4.8.1 RTP Settings ............................................................................ 4-11
4.8.2 Network Options (Unicast/Multicast) ...........................................4-11
4.8.3 Settings .................................................................................4-12
4.9 Video DLTV ..................................................................................... 4-13
4.10 Video Matrix .................................................................................. 4-14
4.11 OSD (On Screen Display) .................................................................. 4-15
4.12 Log File ......................................................................................... 4-16
4.13 Configuration File ............................................................................ 4-17
4.14 Help ............................................................................................. 4-18
-iv January 2012 427-0030-00-28, version 100

1 Nexus IP Camera Configuration
This manual provides a brief guide to configuration of FLIR Nexus IP cameras. If you need help
during the installation and configuration process, contact your local FLIR representative or, call
877-773-3547 inside the US.
For specific information about how to mount and connect the camera, refer to the installation
manual provided with the camera.
This manual includes the following topics:
• Camera configuration overview
• Web Configuration Tool
• Bench testing the camera
• Troubleshooting Tips
• Basic configuration of the camera
For safety, and to achieve the highest levels of performance from the system, always follow the
warnings and cautions in this manual when handling and operating the camera.
1.1 Warnings and Cautions
WARNING!
If mounting the camera on a pole, tower or any elevated location, use industry standard safe
practices to avoid injuries.
Caution!
Except as described in this manual, do not open the camera for any reason. Disassembly of
the camera (including removal of the cover) can cause permanent damage and will void the
warranty.
Be careful not to leave fingerprints on the camera’s infrared optics.
Operating the camera outside of the specified input voltage range or the specified operating
temperature range can cause permanent damage.
427-0030-00-28, version 100 January 2012 1-1

1—Nexus IP Camera Configuration Nexus Configuration Guide
1.2 Introduction
The FLIR Nexus IP Camera is both an analog camera and an IP camera. In general, the camera
is configured using a web browser to access the Web Configuration Tool, and this guide
provides information about how to use that web tool.
The video from the camera can be viewed over a traditional analog video network, and it can be
viewed by streaming it over an IP network using MPEG-4, M-JPEG and H.264 encoding. Analog
video requires a connection to a video monitor or an analog matrix/switch. The IP video will
require a connection to an Ethernet network switch, and a computer with the appropriate
software for viewing the video.
Some cameras can be controlled through either serial or IP communications. For a camera
that uses serial communications, those settings can be configured using hardware DIP
switches instead. The configuration of serial communications parameters using hardware DIP
switches is described in the installation manual for the camera, rather than this document.
1.3 Nexus IP Camera
When a camera has Nexus capabilities, that means there is a microprocessor inside that runs
the Nexus server software. The Nexus server provides a number of services, including camera
control, video streaming, and geo-referencing capabilities. The Nexus communications protocol
is an open, standards-based protocol that allows the camera to communicate with a video
management client, such as FLIR Sensors Manager or with a third-party ONVIF-compatible
Video Management System (VMS) client.
Custom VMS applications can be developed using the open Nexus Software Developers Kit
(SDK) components. Applications can also be developed using Extensible Markup Language
(XML) or Common Gateway Interface (CGI) tools.
There are two main components to the Nexus Server software. One is a web server known as
the Web Configuration Tool that listens on the network for web browser requests, and is used
for the initial (and perhaps ongoing or occasional) configuration changes to the camera. The
other process, known as the Nexus Server, listens on the network for connections from clients
such as FSM or other VMS clients. These clients are used to control the camera and stream
video during day-to-day operations of the camera.
1.4 Camera Configuration
In general, it may be necessary for the installer to make a limited number of configuration
changes for each camera, such as setting the serial and/or IP communication parameters.
For example, each camera comes from the factory with the same default IP address, so adding
more than one camera to an IP network requires each camera to be configured with a different
IP address, at a minimum. On the other hand, many of the configuration parameters will
remain unchanged from the factory default settings. This document provides a brief guide to
setting the configuration parameters which are most commonly changed in order to get the
camera to communicate and to operate normally.
In order to control the camera, it is necessary to communicate with it either over serial
communications (RS-232 or RS-422), or over Ethernet using Internet Protocol (IP). In either
case, it is likely there are some communication parameters that are specific to each
installation.
1-2 January 2012 427-0030-00-28, version 100

Nexus Configuration Guide 1—Nexus IP Camera Configuration
1.5 Serial and/or IP Communications
For a camera that is installed in a legacy-type CCTV network using analog video, the camera will
commonly be controlled with serial communications. The serial cable from the camera will be
connected to a keyboard/joystick device, or to a video switch or DVR that has a serial
communication port. In this case the installer may want to configure parameters such as the
address of the camera, the baud rate, and so on. These parameters can be set either using
hardware DIP switches or through software using a web browser.
For a camera installed in an IP network, the camera will commonly be controlled over Ethernet
by a PC or laptop running FLIR Sensors Manager (FSM) or a third-party Video Management
System (VMS) software. FSM is an integral part of the Nexus architecture—it is a client
program that communicates with the Nexus server on the camera. It allows control of the
camera and video streaming and many other sophisticated functions.
In many cases, a camera will be installed with both serial and Ethernet communications. As
such, the camera can be controlled by means of a serial device or through software. When
someone tries to control the camera with a serial device at the same time as someone does
through the software IP interface, the serial device takes priority.
If serial control is used, the installer must first decide if the serial communications settings will
be configured via hardware (DIP switch settings) or software.
A single DIP switch (SW102-9, Software Override) determines whether the serial
communications configuration comes from the hardware DIP switches or the software
settings. By default the configuration comes from software settings.
If the camera does not have an Ethernet connection, the DIP switches must be used to set the
serial communication options. In the future, configuration changes may require accessing the
camera on a tower or pole, dismounting it, and removing the back and so on. Refer to the
camera installation manual for information about setting the switches.
For a camera installed in an IP network, configuration changes (including settings related to
serial communications) are made using a web browser. If the camera has an Ethernet
connection, generally it will be easier (and more convenient in the long run) to make
configuration settings via software. Then configuration changes can be made over the network
without physically accessing the camera. Also the settings can be saved to a file and backed up
or restored as needed.
Refer to Chapter 3 “Web Configuration Tool” on page 3-1 for general information about the web
interface and about saving configuration changes. For specific configuration information, refer
to Chapter 4 “Nexus Camera Configuration” on page 4-1.
Not all parameter settings are described in these sections. If you need help during the
configuration process, contact your local FLIR representative or, call 877-773-3547 inside the
US.
1.6 Serial Communications
Cameras that have a serial interface support a limited set of zoom and focus commands over
RS-422 or RS-232 serial communications using common protocols (Pelco D or Bosch). By
default, the camera is configured for RS-422 standard, 9600 Baud, 8 bits, no parity, 1 stop
bit, using the Pelco D protocol, and address 1, and configuration changes are made with a web
browser, rather than DIP switches.
427-0030-00-28, version 100 January 2012 1-3

1—Nexus IP Camera Configuration Nexus Configuration Guide
If you are using the IP interface to configure the serial communication settings for the camera,
refer to section 4.6 “Serial Remote” on page 4-6.
The DIP switches are only used to control serial communications parameters. Other settings,
related to IP camera functions etc., must be modified via software (using a web browser).
1.7 System Information Displayed at Startup
When the camera is turned on, the video temporarily displays system information including the
serial number, IP address, Pelco address, Baud rate, and setting of the serial control DIP
switch: SW - software control (the default) or HW - hardware.
S/N: 1234567
IP Addr: 192.168.250.116
PelcoD (Addr:1): 9600 SW
1.8 FLIR Certified Systems Integrator (FCSI) Training
This configuration guide provides a brief description of the configuration parameters that are
available through the basic user login. For installers and integrators that are interested in a
more advanced level of configuration, the FLIR Certified Systems Integrator (FCSI) certification
program offers hands-on training with a variety of FLIR cameras, and focuses on integration
design and installation with other third-party security sensors and equipment. For more
information, contact your local FLIR representative or visit one of the following web sites:
http://support.flir.com/
http://www.flir.com/training
1-4 January 2012 427-0030-00-28, version 100

2 Verify Camera Operation with FSM
This chapter provides information on how to perform a bench test with a new camera that has
not yet been configured. A bench test can be used to verify camera operation before the
camera is configured for the local network.
2.1 Power and analog video
Install the camera cables as described in the installation manual. Apply power to the camera
and confirm it is supplying video to the monitor.
After the camera is turned on and finishes the bootup process (after approximately 90
seconds), the video temporarily displays system information including the serial number, IP
address, Pelco address, Baud rate, and the setting of the Software Override DIP switch: SW -
software control (the default) or HW - hardware.
S/N: 1234567
IP Addr: 192.168.250.116
PelcoD (Addr:1): 9600 SW
2.2 Verify IP Communications
As shipped from the factory, the Nexus camera has an IP address of 192.168.250.116 with
a netmask of 255.255.255.0.
Step 1 Configure a laptop or PC with another IP address from this network (for example,
192.168.250.1).
Step 2 Connect the camera and the laptop to the same Ethernet switch (or back-to-back with
an Ethernet crossover cable). 1
Step 3 Open a web browser 2 ,
enter http://192.168.250.116 in the
address bar, and press Enter.
.The Web Configuration tool will start at the Login screen.
The Login screen shows a picture of the camera and allows
you to enter a User and Password. The login screen for the
F-Series camera appears to the right.
If the Login screen appears, then you have established IP
communications with the camera.
At this time, it is recommended a bench test of the camera
should be performed with the FLIR Sensors Manager
software, using the camera’s factory-configured IP address.
1. In some cases, a straight Ethernet cable can be used, because many PCs have auto detect
Ethernet interfaces.
2. FLIR Web Configuration Tool is optimized for Microsoft Internet Explorer; other web browsers
may not work as well.
427-0030-00-28, version 100 January 2012 2-1

2—Verify Camera Operation with FSM Nexus Configuration Guide
2.3 Using FLIR Sensors Manager (FSM)
The following provides a brief description of how to use FSM to control a camera and stream
video from the camera. For more detailed information on how to use FSM, refer to the FLIR
Sensors Manager User Manual (the manual is available as a pdf file from the Start menu, once
the software is installed).
If the FSM software has not been installed yet, locate the CD that came with the camera and
install it on the PC. The latest version of FSM can be dowloaded at http://ns.flir.com.
The installer must have administrative privileges on the PC to install the software and to grant
network access if the Personal Firewall is enabled.
2.3.1 Running FSM
Run the FSM software by double clicking the icon on the desktop, or click on the
Windows Start button and select Programs > FLIR Sensors Manager > FLIR
Sensors Manager.
Initially the FLIR Sensors Manager splash screen will be displayed. The software version may be
different than the version displayed below.
2-2 January 2012 427-0030-00-28, version 100

Nexus Configuration Guide 2—Verify Camera Operation with FSM
After a brief while, the FSM main window will appear, and a popup FSM Notification window will
appear in the lower right of the screen indicating that no cameras (servers) have been
discovered yet.
Click on the Accept button to acknowledge the notification.
The FLIR Sensors Manager uses a type of “client/server”
architecture. The FSM software is considered a client, and
the cameras are considered servers (also known as
sensors). Note, in this client/server model there may be
many servers (cameras), and the servers are decentralized since they are distributed around
the network.
The Sensors Panel in the upper left of the window
indicates no sensors have been discovered and added to
the list of Active Sensors. The FSM software can
automatically discover FLIR cameras and other sensors
on the network. Each FSM user can choose to add one or
more discovered sensors to the Sensors Panel as needed.
Use the following steps to add the camera to the Sensors Panel, and to verify the operation of
the camera by opening up a video stream and controlling the camera.
Step 1 Select the Setup tab along the top of the window (it may be selected already by
default) and then the Discovery button on the right side panel to bring up the
Discovery Panel.
Step 2 When the Discovery Panel is displayed, click the Refresh button.
The FLIR camera will appear in the list of Discovered Servers 1 . The asterisk in
parenthesis “(*)” indicates the camera has not been added to the list of Active
Servers on the right.
Step 3 In the Discovered Servers list, click on the name of the camera to select it, and then
click on the center bar “>” to move the camera over to the list of Active Servers on
the right.
By default, the FSM software will automatically:
• discover sensors in the network,
• connect to the first camera it finds,
• take control of the camera, and
• display the video from the camera in Video Wall 0.
1. If the camera is not displayed in the list of Discovered Sensors, there could be a problem with
the network, the PC, or the camera. See “Troubleshooting Tips” on page 2-5.
427-0030-00-28, version 100 January 2012 2-3

2—Verify Camera Operation with FSM Nexus Configuration Guide
No Sensors Discovered
Control Panel Select camera name
Refresh
Setup
Discovery
Move to Active Servers list
Step 4 Select the Video Wall 0 tab and confirm that video is streamed to the monitor.
Step 5 Confirm it is possible to control the camera using buttons in the Control Panel. For
example, click on the zoom in button (magnifying glass with +), and the video will zoom
to 2X. For a pan/tilt camera, use the up/down and pan left/right controls to move
the camera.
Once you have verified the basic operation of the camera and successfully streamed video, you
may want to make some configuration changes. For example, the camera can be configured
with an IP address that matches the installation network. Refer to Chapter 4.1 “IP
Communications” on page 4-1for a brief guide on how to configure the camera.
When you are ready to install the camera in its final location, confirm the cables are properly
attached and the DIP switches are set as desired. Reassemble the rear cover after confirming
the ground wire is connected properly, and tighten the cable gland nuts to ensure a good seal
all around.
2-4 January 2012 427-0030-00-28, version 100

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

2—Verify Camera Operation with FSM Nexus Configuration Guide
2.4.2 Unable to control the camera
If you are unable to control the camera with serial communications, ensure the communication
parameters of the camera (such as baud rate, address, and communication standard) match
the parameters of the other serial device. If using RS-422, confirm the receive pair on the
camera are connected to the transmit pair of the other device. Also confirm that the Software
Override DIP switch (SW102-9) is set correctly. This switch determines whether the serial
configuration comes from the hardware DIP switches or the software settings. Refer to the
camera installation manual for information on how to set the DIP switches.
If the camera does not respond to commands from FSM (for example, the camera does not
zoom when the zoom in button is clicked), the camera may not be the “Active” camera, or you
may not have control of the camera. By default FSM will automatically request control of the
camera and make it active, but if there are multiple cameras and/or multiple FSM clients, it
may be necessary to manually make the camera active and take control of it.
In the Sensors Panel, if the camera is the active sensor, there will be an
“(Active)” notification next to the name of the camera. Only one camera or
sensor can be active at a time. To make the camera active, right click on the
icon to the left of the camera name and select “Set Active”, or simply doubleclick
on the icon.
The icon to the left of the camera name indicates the status of the sensor. The following is a list
of the possible icons and the meaning of each one.
Connected and Controlled
This icon indicates the camera has been discovered and added to the list of active servers, and
the camera is actively “connected” to the FSM client and receiving status updates. The joystick
in the icon indicates the user has control of the camera. To release control of the camera, right
click on the icon and select “Release Control”.
Discovered
This icon indicates the camera has been discovered and added to the list
of active servers, but the camera is not actively “connected” to FSM, and
therefore FSM is not receiving status updates. To connect to the camera,
right click on the icon and select “Connect”. Alternatively, it is possible to
double-click the icon to connect.
Connected
This icon indicates the camera has been discovered and added to the list
of active servers, and the camera is actively “connected” to FSM and
receiving status updates. To take control of the camera, right click on the
icon and select “Request Control”. Alternatively, it is possible to doubleclick
the icon to take control.
Not Connected
This icon indicates the camera has been discovered and added to the list of active servers, and
the camera is actively “connected” to the FSM client and receiving status updates. To connect
to the camera, right click on the icon and select “Connect”.
2-6 January 2012 427-0030-00-28, version 100

Nexus Configuration Guide 2—Verify Camera Operation with FSM
2.4.3 General Errors
In the status bar at the bottom of the screen there may be an indication that an error has
occurred. When you position the cursor over the error icon (exclamation mark), the error will
be displayed in a temporary pop-up. It is possible to view all the error messages by selecting the
Tools tab at the top of he screen, and then select the Log button to the left.
2.4.4 Unable to View Video Stream
If the video stream from the camera is not displayed in FSM, 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 FSM for the first time, the Windows Personal Firewall may ask for
permission to allow the FLIR Video Player (vp.exe) to communicate on the network, as in the
following notification. Select the check boxes that are appropriate for your network.
427-0030-00-28, version 100 January 2012 2-7

2—Verify Camera Operation with FSM Nexus Configuration Guide
If necessary, test to make sure the video from the camera can be viewed by a generic video
player such as VLC media player (http://www.videolan.org/vlc/).To view the video stream,
specify RTSP port 554 and the appropriate stream name such as “ch0”. For example:
rtsp://192.168.250.116:554/ch0)
2-8 January 2012 427-0030-00-28, version 100

Nexus Configuration Guide 2—Verify Camera Operation with FSM
2.5 Restoring the Factory Network Settings
The camera comes configured from the factory with a default IP address (192.168.250.116).
In some cases, it may be necessary to restore the network settings of the camera to the
original factory settings. If necessary, the camera IP address can be restored to this factory
default address by connecting a loopback device to the Ethernet port.
At each power-up, the system transmits a packet and then checks to determine if that same
packet has been received. Detection of the received packet indicates the camera has a custom
loopback connector installed on its Ethernet interface. The detection of the loopback packet
cues the camera to restore Factory Defaults and to revert to the same configuration and
behavior as when the camera left the factory.
The custom loopback connector is described below.
Pin # Signal Tied to pin #
1 Transmit + 3
2 Transmit - 6
3 Receive + 1
4 Unused N/A
5 Unused N/A
6 Receive - 2
7 Unused N/A
8 Unused N/A
The RJ45 loopback termination ties pin 1 to pin 3, and pin 2 to pin 6. The other pins are not
connected.
427-0030-00-28, version 100 January 2012 2-9

2—Verify Camera Operation with FSM Nexus Configuration Guide
2-10 January 2012 427-0030-00-28, version 100

3 Web Configuration Tool
This chapter describes the use of the Web Configuration Tool to configure camera settings. If
you need help during the installation and configuration process, contact your local FLIR
representative or, call 877-773-3547 inside the US.
3.1 Web Configuration Overview
This section provides a brief overview of how to use a web browser to connect to the camera
and make configuration changes using the Web Configuration Tool. First familiarize yourself with
the information in this section, and then refer to the following sections for specific information
about how to configure camera settings including the IP interface, since the web browser
communicates using the IP interface.
3.1.1 Web Configuration Tool login
Once you are able to use a web browser to connect to the camera (as described in Chapter 2
“Verify Camera Operation with FSM” on page 2-1), the login screen will appear; select Login as
Basic User, or type “basic” as the User and click on Login (there is no password for the Basic
user).
Note
Prior to making changes to the configuration, it may be wise to bench test the camera using
the factory configured IP address. See “Verify IP Communications” on page 2-1.
It is also possible to open the Web Configuration Tool through FSM by right-clicking on the
sensor icon and selecting Admin. Tools > Open Web Configuration Tool.
.Although it is also possible to login with the user “admin”,
generally it is better to use the “basic” user login. The “basic”
user login is simpler to use and is less prone to making
configuration changes that lead to unintended results.
427-0030-00-28, version 100 January 2012 3-1

3—Web Configuration Tool Nexus Configuration Guide
Once you are logged in, the Help screen will appear. If it is necessary to contact FLIR Technical
Support for assistance, it will be helpful to have the information from this page (such as
Software Version) on hand.
The web links available on the left side of the page (Settings, LAN Settings, and so on)
correspond to different groups of configuration parameters.
Figure 3-1: Web Configuration Tool Help Screen
The current status of the Nexus server is displayed in the upper left (it should show as
“Server Running…”).
Note
Before making any configuration changes, it may be wise to back up the existing configuration.
See “Configuration File” on page 4-17.
3-2 January 2012 427-0030-00-28, version 100

Nexus Configuration Guide 3—Web Configuration Tool
3.1.2 Saving Configuration Changes
After making any configuration changes, it is necessary to save the changes to the server
(there is a Save button at the bottom of each configuration page). Once you save configuration
changes to the server, the changes do not take effect immediately. Generally it is also
necessary to stop and restart the server for the changes to become effective. The server has
a configuration that is active and running, and another configuration that is saved (and possibly
different than the running configuration). The following message indicates the saved
configuration is different than the active (running) configuration: “You must restart the server
for the changes to be effective”.
3.1.3 Restarting the Server
To restart the server, first click on the Stop button at the top of the page, and wait for the page
to refresh.
Note:
It may take up to 20 seconds or more to stop the server, especially when there are multiple
video streams open. Be patient when stopping the server.
When the server is stopped and the page is refreshed, the status will show as “Server
Stopped” and the button at the top of the page will change to Start rather than Stop.
Click on the Start button to restart the server, and when the page refreshes, the status will
again show as “Server Running…”. The Start button will be replaced by a Stop button when the
startup procedure has completed.
When configuration changes are made with the web browser, the settings are saved to a
configuration file. It is a good idea to make a backup of the existing configuration file prior to
making changes. If necessary the camera can be restored to its original factory configuration
also. For more information, refer to section 4.13 “Configuration File” on page 4-17.
427-0030-00-28, version 100 January 2012 3-3

3—Web Configuration Tool Nexus Configuration Guide
3-4 January 2012 427-0030-00-28, version 100

4 Nexus Camera Configuration
This chapter describes the Nexus configuration parameters that are available through the basic
user login. If you need help during the installation and configuration process, contact your local
FLIR representative or, call 877-773-3547 inside the US.
4.1 Configuration using IP Communications
The camera has an Ethernet connection that allows for configuration and control of the camera
and for streaming video over an IP network. It is possible to control the camera and stream
video from the camera as configured from the factory, without making any changes. However in
most cases the camera will have at least some configuration changes to allow it to connect
with other devices on the existing network. Prior to making changes with the Web Configuration
Tool, be sure you are familiar with the information in Chapter 3 “Web Configuration Tool” on
page 3-1.
Getting the camera IP interface set up and working may require a level of familiarity with
managing IP networks that is new to many security professionals. Prior to configuring the IP
interface and streaming video parameters, make sure you know how to manage and configure
the other equipment in the network (for example, any PC or device that will connect to the
camera, any router or firewall that will carry the IP traffic, and so on). FLIR technical support
can provide limited support in this regard.
The camera comes configured from the factory with a default IP address (192.168.250.116).
If necessary, the camera IP address can be restored to this factory default address by
connecting an RJ-45 loopback device to the Ethernet port. See “Restoring the Factory Network
Settings” on page 2-9.
4.1.1 IP Configuration Steps
Assuming the existing network uses IP addresses that are unique and different than the default
address on the camera, configuring the camera for IP communications generally involves the
following steps:
Step 1 Connect the Ethernet port to an IP network that is isolated from the existing network
(for example, a standalone switch)
Step 2 Connect a PC or laptop to the same network
Step 3 Temporarily set the IP address of the PC or laptop to be compatible with the factory
network address of the camera (for example, 192.168.250.1)
Step 4 Perform a bench test of the camera using FSM, prior to making any parameter
changes (this step is optional but recommended)
Step 5 Open a web browser, enter http://192.168.250.116/ in the address bar and
press Enter to connect to the camera
Step 6 Make a backup of the existing configuration
Step 7 Configure the camera settings: configure the IP network settings, serial
communications settings, and video streaming parameters so the camera is
compatible with the existing network equipment
Step 8 Test the camera with the new settings
Step 9 Save the configuration changes and restart the server
Step 10 Connect the camera to the existing network and test the camera
Step 11 Make a backup of the new configuration
427-0030-00-28, version 100 January 2012 4-1

4—Nexus Camera Configuration Nexus Configuration Guide
4.2 Basic Web Configuration
To make configuration changes with software, use a web browser to
connect with the camera. If the IP address of the camera is known,
you can type the IP address into the browser. As shipped from the
factory, the camera has an IP address of 192.168.250.116 with a
netmask of 255.255.255.0.
The Web Configuration Tool will start at the Login screen, which
shows an image of the camera. When this screen appears, the PC is
successfully connected to the camera over the IP network.
4.3 Settings
Select Login as Basic User, or type “basic” as the User and click on
Login (there is no password for the Basic user). Initially, the Help page
will be displayed. This page has information about the camera including
hardware and software revision numbers, part numbers, and serial
numbers. If you need to contact FLIR for support, this information will be
useful to the support engineer. On the left side of the page is a list of
hyperlinks to the web pages that are used to configure the Nexus
camera.
For most installations, the “basic” login provides access to the
parameters that will typically be changed. For more advanced
configurations, it is also possible to login as “admin”, and that login
provides access to a greater number of configuration parameters. The
“admin” login requires a password (initially “indigo”) and this password
can be changed for security purposes.
The remainder of this guide describes the configuration parameters that
are available to the basic user. The sections are organized in the same
order as the links on the left.
In most cases the Settings page is not used. If necessary, the Log max size can be set to a
non-zero number to allow log messages to be displayed. See “Log File” on page 4-16.
4-2 January 2012 427-0030-00-28, version 100

Nexus Configuration Guide 4—Nexus Camera Configuration
4.4 LAN Settings
The LAN Settings page can be used to set the hostname, default gateway, and IP address for
the camera. In FSM, the Hostname will appear as the name of the sensor. The default IP
Address mode is static; the mode can also be set to DHCP.
When the LAN settings are changed and the Save button is clicked, a pop-up message will
appear to indicate the network interface will be restarted.
Note
Once the IP address of the camera is changed, the PC may no longer be on the same network
and therefore may not be able to access the camera until the IP address on the PC is changed
also. For that reason, you may wish to change the IP address after making other configuration
changes.
Note
If the Hostname is changed, the new name may not show up in FSM until the camera is
rebooted. To reboot the camera, save any configuration changes, then select Server Status
and click the Reboot button.
427-0030-00-28, version 100 January 2012 4-3

4—Nexus Camera Configuration Nexus Configuration Guide
4.4.1 D-Series LAN Settings
For the D-Series cameras, if the user is logged in as “admin”, there are some important
differences on the LAN Settings page. In particular, there are two Ethernet interfaces (eth0
and eth1). In most cases, the eth1 interface should not be changed. The eth1 interface is used
for internal communications within the camera, and the eth0 interface connects the camera to
the network.
Note
The eth0 and eth1 interfaces must have unique IP addresses on separate IP networks. Do
not set the eth0 interface to an address that is in the same range of addresses as the eth1
interface.
The eth1 interface has a default address of 192.168.2.101. In some installations that
address is from a range of addresses that are being used already on the network. If it is
necessary for the camera to be connected to a network that uses the 192.168.2.x range of
addresses, contact your local FLIR representative or, call 877-773-3547 inside the US for
information about configuring the IP interfaces for that environment. Do not make haphazard
changes to the eth1 interface, as it will interrupt communications with the other internal
Ethernet devices.
4-4 January 2012 427-0030-00-28, version 100

Nexus Configuration Guide 4—Nexus Camera Configuration
4.5 Server Status
The Server Status page is used when it is necessary to set or change the camera date and
time, to shutdown or reboot the camera, or to update the server files. The name of the Server
Status page may be somewhat misleading, as it does not provide server status information
when logged in as basic.
4.5.1 Setting the Date and Time
Select the Date Format from the pulldown
menu to either Europe or
America and click Set. This will set
the date format to dd/mm/yyyy or
mm/dd/yyyy, respectively.
Set the Date by typing in the dialog
boxes and click Set. Changing the
date of the camera may cause the
user to be logged out of the Web
Configuration Tool.
Set the Time by typing in the dialog
boxes and click Set. Changing the
time of the camera may cause the
user to be logged out of the Web
Configuration Tool.
4.5.2 Software Upgrades
If a new version of software becomes
available, the server and web files
can be uploaded to the camera from
a PC using the various Upload
buttons on this page.
4.5.3 Rebooting the Camera
When the Reboot button is clicked, a pop-up notification
will confirm if you really want to reboot. Another pop-up
notification will indicate it takes about 3 minutes to
reboot the host. After approximately 3 minutes, refresh
the web browser page to connect to the camera again.
427-0030-00-28, version 100 January 2012 4-5

4—Nexus Camera Configuration Nexus Configuration Guide
4.6 Serial Remote
In some installations, a serial device such as a keyboard, joystick, or other device is used to
control camera functions such as pan/tilt or zoom. A serial device can also be used to access
functions that are specific to thermal cameras, such as changing the polarity from white hot to
black hot. Refer to section 4.6.1 “Serial Extensions” on page 4-7 for additional information.
The Serial Remote settings are used to configure the serial communication parameters when
the camera is controlled with a serial device. The Serial Remote option is not available on some
cameras that do not have serial communication interfaces.
The settings will take effect if the Software Override DIP switch is set to Off (the default),
allowing software settings to control the camera. If the switch is set to On, software
configuration changes through the web browser will have no effect. For more information about
the DIP switches, refer to the camera installation manual.
For serial communications, it is necessary to set the parameters such as the signalling
standard (RS-232 or RS-422), baud rate, number of stop bits, parity and so on. It is also
necessary to select the communication protocol used (either Pelco D or Bosch) and the
camera address.
On the Serial Remote Configuration
page, the pull-down in the upper right
allows configuration of three serial
devices: 0, 1, and 2. Device ID 0 is
used as a switch to select either Pelco
D or Bosch serial communications
protocol. The actual serial parameters
are configured for either Device ID 1
(for Pelco D) or Device ID 2 (for
Bosch).
With Device ID 0 selected, set the
Serial Remote Protocol to either Pelco
D Serial Remote or Bosch Serial Remote. Ensure the Enabled parameter is set to Yes. If
necessary, click Save to save the changes.
If the Pelco D protocol is to be used, select Device ID 1 and
wait for the page to refresh, and then configure the
Remote Port Settings such as Speed (baud rate), Data
Bits, Parity and Stop Bits. Set the Address parameter to
the appropriate Pelco address.
If the Preset Map File is set to yes, then presets can be
used to access certain settings that are specific to the FLIR
thermal camera, such as switching between White Hot and
Black Hot settings. See section 4.6.2 “Preset Map File” on
page 4-7 for information about the Preset Map File.
The Initial Selected Camera is used to designate which camera (IR or DLTV) in a multi-sensor
camera is selected as the initial Active camera. Select the appropriate Hardware Protocol (RS-
422 or RS-232).
4-6 January 2012 427-0030-00-28, version 100

Nexus Configuration Guide 4—Nexus Camera Configuration
In the Joystick settings, the Mode parameter, when set to FOV Dependant, allows a pan/tilt
camera to adjust the pan speed automatically, depending on the current field of view (FOV). For
a narrow FOV, the camera moves more slowly. If you do not want to limit the pan speed
according to the FOV, set the parameter to Absolute.
The Pilot Mode parameter controls the direction of tilt when the joystick is moved forward or
backward. When Pilot Mode is set to yes, the camera points downward when the joystick is
moved forward, similar to the way an aircraft would move. If the mode is set to no, the joystick
operates as one would expect with a video game controller.
The parameters in the Advanced Settings are related to Scan Lists and the AutoPan feature.
Refer to section 4.6.2 “Preset Map File” and section 4.6.3 “AutoPan Function” below for more
information about these features.
If any of the parameters for Device ID 1 are changed, click Save to save the changes. Generally
most of the other Serial Remote parameters do not need to be changed (for Device ID 1 and
Device ID 2, it is ok if the Enabled parameter is set to no).
If the Bosch protocol is to be used instead, select Device ID 2 and wait for the page to refresh,
and then configure the Remote Port Settings such as Speed (baud rate), Data Bits, Parity and
Stop Bits. Select the appropriate Hardware Protocol (RS-422 or RS-232), and set the Address
parameter to the appropriate Bosch address. If necessary, click Save to save the changes.
4.6.1 Serial Extensions
In addition to the set of standard commands that would be used on an ordinary CCTV camera,
control commands that allow access to more advanced features, or features that are specific
to a particular type of equipment, are available through extensions to the serial protocol. These
extended commands are quite useful when controlling features that are specific to FLIR thermal
cameras.
In the Pelco D protocol, these additional functions can be accessed using the Aux On and Aux
Off extensions and are available by default. Many keyboards that support Pelco protocols have
Aux On and Aux Off buttons for selecting these functions. As an example, the following functions
are typically supported by default.
Table 4-1: Aux Functions
AuX ON 1 IRPolarityBlackHot
AUX OFF 1 IRPolarityWhiteHot
AUX ON 2 DLTVChangeActiveSource
AUX OFF 2 IRChangeActiveSource
AUX ON 3 TogglePlateauValue
AUX OFF 3 IRToggleAGCType
AUX ON 4 ToggleAutofocus
AUX OFF 4 IRStartNUCCalibration
AUX OFF 5 IRToggleLUTPalette
AUX ON 6 IRToggleDDEGain
AUX OFF 6 IRToggleAGCROI
AUX ON 7 IRToggleFOV
AUX OFF 7 IRToggleAGCMaxGain
427-0030-00-28, version 100 January 2012 4-7

4—Nexus Camera Configuration Nexus Configuration Guide
AUX ON 8 SwitchCameraOn
AUX OFF 8 SwitchCameraOff
AUX ON 9 InitializePT
AUX OFF 9 GoToParkPosition
4.6.2 Preset Map File
Most pan/tilt cameras support predetermined pan/tilt locations that are stored as “presets’.
A collection of presets is known as a Scan List (also referred to as a Pattern or Tour), A Scan
List is used to direct the camera to a sequence of locations that are typically viewed, or are
considered important or high-priority. Using the FSM software, multiple scan lists for a camera
can be set up and scheduled according to time of day and other factors.
However, presets can also be used to access other functions. For keyboards that do not have
the Aux buttons, camera presets can be used to accomplish the extended functions described
above. For example, if preset 41 is not being used for an actual preset location, it can be
mapped to one of the above functions, such as IRPolarityBlackHot. To allow mapping of the
serial functions, set the “Use Preset Map File” parameter to yes.
On the Server Status page, use the Download PelcoD Map File link to open the text file that is
used for mapping the functions to Aux commands and Presets. If it is necessary to change the
mapped functions, edit the file and upload the new map file to the camera using the Upload
button. Once a file has been edited and tested, it can also be uploaded to other cameras so
that each camera operates the same way.
4.6.3 AutoPan Function
Table 4-1: Aux Functions
In many cases with a pan/tilt camera, it may be desirable to use a simple back-and-forth (leftright)
scan pattern, rather than a Scan List set of presets. To use the AutoPan feature, set the
left and right pan limits and the pan speed, and then start the AutoPan mode. The functions for
setting up the AutoPan limits and for controlling the AutoPan function are available using
presets and are described in the following table..
Table 4-2: AutoPan functions
PRESET GOTO 90 GoToPanLimitLeft
PRESET GOTO 91 GoToPanLimitRight
PRESET GOTO 92 SetPanLimitLeft
PRESET GOTO 93 SetPanLimitRight
PRESET GOTO 94 IncrementAutoPanSpeed
PRESET GOTO 95 DecrementAutoPanSpeed
PRESET GOTO 96 StopAutoPan
PRESET GOTO 99 StartAutoPan
4-8 January 2012 427-0030-00-28, version 100

Nexus Configuration Guide 4—Nexus Camera Configuration
4.7 Network Remote / VMS
Several types of third-party Video Management System (VMS) systems are supported by FLIR
IP cameras. Because these systems tend to evolve and change over time, contact your local
FLIR representative or FLIR Technical Support if you have any difficulties or questions about
using this feature.
Select the Network Remote / VMS link on the left side of the page to configure the camera to
operate with a VMS Interface. By default no VMS Interface is configured; use the pull-down to
select the appropriate type of VMS and click the Add button.
The New Device Creation screen will appear. Set the communication parameters to match the
remote system and click on the Create button.
After the device is created, click on the Save button to save the configuration, and then restart
the server.
4.7.1 ONVIF
The most common choice for Network Remote / VMS is ONVIF v2.0. The ONVIF (Open
Network Video Interface Forum) is an open industry forum for the development of a global
standard for the interface of network video products. An ONVIF-compliant VMS can be used to
control a FLIR camera, display video, and access up to 50 pan/tilt presets.
Contact your local FLIR representative or refer to the FLIR web site for application notes on how
to configure the camera to work with specific third-party VMS packages.
427-0030-00-28, version 100 January 2012 4-9

4—Nexus Camera Configuration Nexus Configuration Guide
4.8 Video IR
By default, a single video stream is enabled for the thermal (IR) camera, and for multi-sensor
cameras such as the D-Series and PT-Series cameras, a single video stream is enabled for the
second sensor 1 , the daylight camera (the DLTV). To modify parameters that affect the IP Video
stream from the thermal camera, select the Video IR link on the left. To modify parameters
that affect the IP Video stream from the daylight camera, select the Video DLTV link on the left
(refer to the section 4.9 “Video DLTV” on page 4-13).
The default settings for each video stream provide high-quality, full frame-rate video. In general,
for most installations it will not be necessary to modify the default parameters. However in
some cases, such as when a video stream is sent over a wireless network, it may be useful to
“tune” the video stream to try to reduce the bandwidth requirements. In particular, the RTP
Settings, Network Options and the Settings parameters are described below.
There are some challenges with streaming video over an IP network, when compared to other
traditional IP applications which are less time-critical, such as email and web browsing. In
particular, there are requirements which must be fulfilled to ensure satisfactory video quality in
professional security environments. There are many parameters and factors related to network
infrastructure, protocols, codecs and so on that can affect the quality and bit rate of a video
stream when it is established between the camera and a client.
The video streaming is done using a protocol generally referred to as Real-time Transport
Protocol (RTP), but there are actually many protocols involved, including Real-Time Transport
Control Protocol (RTCP) and Real Time Streaming Protocol (RTSP). In the background, a
“negotiation” takes place to establish a session between the client (such as FSM, or a third
party VMS or video player) and the camera. The ports which form a session are negotiated
using a protocol such as RTSP. A client typically requests a video stream using its preferred
settings, and the camera can respond with its preferred settings. As a result, many of the
details are established dynamically, which may run contrary to network security requirements.
In some networks, the RTP/RTSP traffic is carried (tunnelled) over Hypertext Transfer Protocol
(HTTP) as that may allow the traffic to cross network boundaries and firewalls. While this
method involves more overhead due to encapsulation, it may be necessary for clients to access
the video streams when HTTP proxies are used.
It is possible to enable a second video stream for a camera and this requires logging in to the
Web Configuration Tool as “admin”. Turning on additional video streams places a higher load on
the video microprocessor and could lead to poor performance overall if not done properly. If you
have problems or questions contact your local FLIR representative or FLIR Technical Support.
Each video stream has a Device ID associated with it. The default video stream from the
thermal camera (the Video IR channel) is known as Device ID 0. The second video stream
(disabled by default) from the thermal cameras is Device ID 1. For a multi-sensor camera, the
default video stream from the daylight camera (the Video DLTV channel) is Device ID 2, and the
second DLTV video stream (disabled by default) is Device ID 3.
1. In future product releases, the second sensor could be another thermal camera,
rather than a daylight camera.
4-10 January 2012 427-0030-00-28, version 100

Nexus Configuration Guide 4—Nexus Camera Configuration
4.8.1 RTP Settings
According to the specification, RTP is originated and received on even port numbers and the
associated RTCP communication uses the next higher odd port number; the default RTP Port is
554. The Stream Name is used when establishing a session from a client. The default value
recognized by FSM for the thermal camera is ch0; the complete connection string is:
rtsp://192.168.250.116/ch0. If necessary, enter the appropriate Stream Name for your
installation.
By default the video stream uses the IP address of the camera. If the Use External IP
parameter is set to “yes”, an alternate IP address can be entered.
Note
Always use an even port number for the RTP Port parameter.
4.8.2 Network Options (Unicast/Multicast)
By default, the video streams from the camera are sent using unicast packets rather than
multicast. This means a given packet of IP Video will be sent separately to each client that has
that video stream open (for example, FSM clients, nDVR, and so on). Therefore each additional
client will cause the bandwidth consumption to go up and cause more overhead on the system
in comparison to multicast.
On the other hand, video packets sent using multicast are shared by streaming clients, so
additional clients do not cause bandwidth consumption to go up as dramatically. If the video
streams are used by more than one client/location, it may be wise to use multicast for more
efficient bandwidth usage.
To set the camera to use Multicast, set the Enable Multicast parameter to “yes”, and set the
Destination Network address and Destination Port to a unique combination that will not conflict
with other IP Video devices on the network (the Destination Port must be an even number).
Note
If more than one camera is providing multicast streams on the network, be sure to configure
each stream with a unique multicast Destination Network IP address and Destination Port
combination. The destination address on each camera will default to 232.0.1.1 when the
Enable Multicast parameter is set to “yes”.
427-0030-00-28, version 100 January 2012 4-11

4—Nexus Camera Configuration Nexus Configuration Guide
4.8.3 Settings
The parameters in the Settings section will have a significant impact on the quality and
bandwidth requirements of the video stream. In general it is recommended that the default
values are used initially, and then individual parameters can be modified and tested
incrementally to determine if the bandwidth and quality requirements are met.
For each video stream, the Codec Type
options are MPEG4, H.264 or MJPEG.
MPEG4 requires the least amount of
processing, and MJPEG requires the
most.
The Bit Rate parameter is only used
when the Rate Control parameter is set
to CBR (Constant Bit Rate). With the
CBR setting, the system attempts to
keep the resulting bit rate of the video at or near the target bit rate.
The I-Frame Interval parameter controls the number of P-frames used between I-frames. Iframes
are full frames of video and the P-frames contain the changes that occurred since the
last I-frame. A smaller I-Frame Interval results in higher bandwidth (more full frames sent) and
better video quality. A higher I-Frame Interval number means fewer I-frames are sent and
therefore results in lower bandwidth and possibly lower quality.
The Image Size parameter controls the video resolution size and therefore can have a
considerable impact on bandwidth usage. The larger the size of the frame, the better the
resolution and the larger the network bandwidth required. The following table provides the
corresponding resolution for each Image Size setting.
Table 4-3: Image Size Settings
Image Size NTSC PAL
D1 720x480 720x576
4CIF 704x480 704x576
VGA 640x480 N/A
CIF N/A 320x240
SIF 353x240 352x288
QVGA 320x240 N/A
QCIF N/A 176x144
As a rule of thumb, if the video will be viewed on its own and on a reasonably large screen, a
large image size setting may look better. On the other hand, if the video is shown as a tile in a
video wall, a smaller image size may look as good and consume less bandwidth.
4-12 January 2012 427-0030-00-28, version 100

Nexus Configuration Guide 4—Nexus Camera Configuration
4.9 Video DLTV
By default, a single video stream is enabled for the Daylight TV (DLTV) camera. To modify
parameters that affect the IP Video stream from this camera, select the Video DLTV link on the
left. The default video stream from the thermal camera is known as Device ID 3.
The default settings for the Video DLTV stream provide high-quality, full frame-rate video. In
general, for most installations it will not be necessary to modify the default IP video parameters.
However in some cases, as with the Video IR stream, it may be useful to modify certain
parameters to try to reduce the bandwidth requirements. In particular, the RTP Settings,
Network Options and the Settings parameters are similar to the same parameters that were
described for the thermal camera above.
The Interlaced parameter controls if the video frames are interlaced or not. By default, it is set
to No for the DLTV video stream. Interlacing is defined as the interleaving of two video fields to
produce a frame and is typically adopted to reduce screen flicker for a given frame rate.
For the F-Series camera, the Video DLTV page is not used.
427-0030-00-28, version 100 January 2012 4-13

4—Nexus Camera Configuration Nexus Configuration Guide
4.10 Video Matrix
For some multi-sensor cameras (having both thermal and DLTV sensors, or multiple thermal
sensors) such as the PT-Series 1 , the Video Matrix web page allows the configuration of the
parameters that control how the multiple video channels are controlled and displayed.
The Video Matrix (also known as VIDMUX) allows the output video from either sensor (IR or
DLTV) to go to either analog video output. It also allows the output from one sensor to be
displayed as a picture-in-picture (PIP) in the other sensor.
In a multi-sensor camera, one video channel is designated as Main (or primary) and the other
channel is designated as Aux (or auxiliary). The Operation Mode parameter can be set to
Manual (default) or Active Camera. When the mode is set to Active Camera, the active sensor
(as selected in FSM or with a serial control device) is output to the Main analog output, and the
other sensor is output on the Aux analog output. This allows the analog video outputs to toggle
between the two sensors. or when only one monitor is available, to display the Active Camera
on the primary analog output.
The Initial Video Switch can be used to switch the Main
channel to the second camera at startup. The Video Source
designated as Tube-A CVBS is the IR camera, and Tube-B
CVBS is the DLTV camera. When the Video PIP parameter
is set to “yes”, then the video from the other channel is
displayed as an overlay. The Video PIP Preset parameter
controls where the smaller PIP appears in the larger video.
1. Due to hardware constraints, this feature is not available in the D-Series cameras.
4-14 January 2012 427-0030-00-28, version 100

Nexus Configuration Guide 4—Nexus Camera Configuration
4.11 OSD (On Screen Display)
The OSD configuration page allows certain camera-related information such as the camera
name or the date and time to be displayed in the analog video and in the IP video streams.
It is possible to display the following
parameters as an overlay on the video
channels: Date, Time, Label, Preset.
The Label can display the Hostname
(as configured on the LAN Settings
page) or a custom text string (using
the Text Mode parameter).
If Preset is displayed, it displays the
number of the preset when the pan/tilt
is positioned at a preset location. Refer
to the FSM Users Manual for
information on how to set presets.
The appearance of each text string can
be controlled with the following
parameters:
• State (on or off)
• Transparency (on indicates only the
letters are displayed, off indicates
the letters are displayed inside an
opaque block)
• Color (changes the color of the letters)
• Style Mode (can be Preset, which
indicates the information is displayed
in certain preset sizes and
locations, or Manual, which
requires additional size and location
settings)
• Size (text size - small, medium or
large)
• Location (preset location on the
screen where the information will
appear)
The Initial System Info parameters
control how the initial system
information is displayed, such as the IP
address and serial communication
parameters.
427-0030-00-28, version 100 January 2012 4-15

4—Nexus Camera Configuration Nexus Configuration Guide
4.12 Log File
The Log File page allows log messages to be displayed. This may be useful when
troubleshooting a problem. In order to display log messages, it is necessary for the Log max
size parameter to be set to a non-zero number. See “Settings” on page 4-2.
The log file can also be saved to a PC or laptop using the Download Log File link.
4-16 January 2012 427-0030-00-28, version 100

Nexus Configuration Guide 4—Nexus Camera Configuration
4.13 Configuration File
The Configuration File web page allows the Nexus Server configuration to be displayed or
backed up locally (on the camera). The configuration file can also be downloaded to another
computer for backup, or a new configuration file can be uploaded from a computer to the
camera.
Shown at the top of the screen is
the configuration script file in a
scrollable window. This can be useful
if you ever need help from a support
engineer.
Click Restore in the Factory Backup
& Recovery section to restore the
camera to its factory settings. This
file can not be modified or deleted,
so it is always available.
In the Customer Backup & Recovery
section, use the Backup button to
make a backup of your final settings.
This will make a backup copy of the
configuration file and store it locally
on the camera.
In the Upload & Download section,
the Download Configuration File link
can be used to save a copy to a PC
for safe keeping. A pop-up window
will ask for a file name and
destination folder.
The Upload button is used to
transfer a configuration file from a
PC to the camera.
427-0030-00-28, version 100 January 2012 4-17

4—Nexus Camera Configuration Nexus Configuration Guide
4.14 Help
Initially, the Help page will be displayed. This page has information about the camera including
hardware and software revision numbers, part numbers, and serial numbers. If you need to
contact FLIR for support, this information will be useful to the support engineer.
The Help information will look similar to the information below.
4-18 January 2012 427-0030-00-28, version 100