«Document History Version Date Coment 100 Jan 2012 Initial Release 110 Jun 2013 New web interface (3.0), WW 1.4 release 120 Mar 2014 New default ...»
Nexus IP Camera
© 2013 FLIR Systems, Inc. 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 Systems, Inc.
Names and marks appearing on the products herein are either registered trademarks or trademarks of FLIR
Systems, Inc. and/or its subsidiaries. All other trademarks, trade names, or company names referenced herein are used for identification only and are the property of their respective owners.
This product is protected by patents, design patents, patents pending, or design patents pending.
The contents of this document are subject to change.
FLIR Systems, Inc.
70 Castilian Drive Goleta, CA 93117 Phone: 888.747.FLIR (888.747.3547) International: +1.805.964.9797 http://www.flir.com Document History Version Date Coment 100 Jan 2012 Initial Release 110 Jun 2013 New web interface (3.0), WW 1.4 release 120 Mar 2014 New default passwords for WW 1.4.1 427-0030-00-28 Version 120 Mar 2014 -ii Table of Contents Table of Contents Nexus IP Camera Configuration
1.2 Nexus IP Camera
1.3 Nexus Server Configuration
1.3.1 Serial and/or IP Communications
1.3.2 Serial Communications
1.4 System Information Displayed at Startup
1.5 FLIR Certified Systems Integrator (FCSI) Training
Basic Operation and Configuration
2.1 Power and analog video
2.2 Basic Test and Configuration Steps
2.3 Camera Bench Test
2.4 Web Browser Interface
2.4.1 Camera Control and Status
2.4.2 Web Control Panel
2.4.4 Log Off
2.5 Thermal Imaging Overview
2.6 Basic Camera Configuration
2.7 Expert and Admin Logins
2.7.1 Maintenance Menu
2.8 Troubleshooting Tips
2.8.1 Image freezes momentarily
2.8.2 No video
2.8.3 Performance varies with time of day
2.8.4 Unable To Communicate Over Ethernet
2.8.5 Unable to control the camera
2.8.6 General Errors
2.8.7 Unable to View Video Stream
2.8.8 Noisy image
2.8.9 Image too dark or too light
2.8.10 Eastern or Western Exposure
2.9 Setting the IP address on a Windows PC
3.1 Thermal Image Setup
3.1.3 Scene Presets
3.1.4 Digital Detail Enhancement (DDE)
3.1.5 Flat Field Correction (FFC)
3.1.6 Save Settings
3.2 Surveillance (Auto Scan / Scan List)
3.2.1 Auto Scan
3.2.2 Scan List
427-0030-00-28 Version 120 Mar 2014 iii Table of Contents
3.3 Maintenance Mode
3.3.1 Configuration Changes That Require Restart
3.4 Restarting the Server
3.5 Serial Communications (Serial Remote)
3.5.1 AutoPan Function
3.5.2 Serial Extensions
3.5.3 Preset Map File
3.6 Remote/VMS (ONVIF Interface)
3.7 On Screen Display (OSD)
3.8 Video Stream Parameters
3.8.1 RTP Settings
3.8.2 Network Options (Unicast/Multicast)
3.8.4 MJPEG Codec Type
3.9 Configuration File
3.10 Restoring the Factory Settings
427-0030-00-28 Version 120 Mar 2014 iv 1 Nexus IP Camera Configuration FLIR IP cameras use a client/server communication architecture knows as Nexus. 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 a FLIR thermal camera, refer to the installation manual provided with the camera.
This document includes the following topics:
Refer to the FLIR Sensors Manager User Manual (FLIR Pub. No. T559777) for detailed information about how to use the FLIR Sensors Manager (FSM) client to operate a camera, view video, and so on.
For cameras that do not have Nexus built-in, a JPC3G1 server or a Microsoft Windows-based PC server can be used to provide Nexus capabilities. The JPC3G server acts as a video encoder and primary interconnection junction box - it provides an IP connection for analog cameras and other devices.
Similarly, a PC running Windows can be used as a Nexus Server, and it can be used to integrate other sensors and devices with the FLIR cameras. For configuration information regarding these Nexus Servers, contact FLIR Technical Support.
1.1 IntroductionA FLIR IP Camera with Nexus2 can operate as both an analog camera and an IP camera. When used as an IP camera, the camera can be configured with a web browser by accessing the Web Configuration Tool, and this guide provides information about how to use that web tool. The latest release of the web tool also allows the user to view video and to operate the camera (for example, to zoom in or out). In addition, the camera can be operated using the FSM client, and this manual provides a brief introduction to using FSM to perform a bench test of the camera.
The FLIR Nexus IP Cameras have microprocessors that run a software process called the Nexus Server.
The Nexus Server software controls the devices such as thermal and daylight cameras, pan/tilt platforms and so on, and communicates across the TCP/IP network with command and control clients such as FLIR Sensors Manager (FSM) or another Video Management System (VMS).
The configuration interface for various types of Nexus IP cameras is similar in many respects, regardless of the camera model. In this manual, each Nexus IP camera may be referred to as a “Nexus Server”, or simply as a “server”, and, in a more general sense, it may be referred to as a camera. In some cases it may also be referred to as a “sensor”. Specific sections are included in the manual to point out when there are configuration differences between the various IP camera models.
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. Analog video requires a connection to a video monitor or an analog matrix/switch. For IP video streams, the cameras provide a choice of MPEG-4, M-JPEG or H.264 video
1. The JPC3G is the third generation of the Junction Protocol Converter (JPC) controller.
2. At the time of publication, this includes the following types of FLIR thermal cameras: DSeries, F-Series, FC-Series, PT-Series, and A310pt Series.
encoding. The IP video will require a connection to an Ethernet network switch, and a computer with the appropriate software (such as FSM or a web browser) for viewing the video.
Some Nexus Servers can be controlled through either serial or IP communications. For some cameras that use serial communications, those settings may be configured using hardware DIP switches rather than software settings. If available, the configuration of serial communications parameters using hardware DIP switches is described in the installation manual for the camera, rather than this document.
1.2 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 server to communicate with a video management client, such as FLIR Sensors Manager or with a third-party ONVIF-compatible 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 tool or web interface that listens on the network for web browser requests, and is used for the initial (and perhaps ongoing or occasional) configuration changes to the server. The latest release of the web tool also allows the user to view video and to operate 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.3 Nexus Server Configuration In general, it may be necessary for the installer to make a limited number of configuration changes for each server, 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.3.1 Serial and/or IP Communications For a camera that is installed in a legacy-type CCTV network using analog video, the camera may 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, encoder, 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. On Nexus IP cameras that support serial communications, these parameters can be set through software using a web browser, or, on some cameras, using hardware DIP switches.
427-0030-00-28 Version 120 Mar 2014 1-2 Nexus IP Camera Configuration 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 software or hardware (DIP switch settings, if available).
Note On cameras with serial communication DIP switches, 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.3.2 Serial Communications Cameras that have a serial interface support a limited set of pan/tilt/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.
If a web browser is used to configure the serial communication settings for the camera, refer to section 4.6 “Serial Remote” on page 4-6 for information about those settings.
Note On Nexus IP cameras with DIP switches, the 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.4 System Information Displayed at Startup When the camera is turned on, the video temporarily displays system information including the camera serial number, the IP address, and, on a camera with a serial interface, the serial communications parameters, such as the protocol (PelcoD or Bosch), the 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