ThermovisionFLIR FCSeries Installation Manual

							427-0073-12-12 Version 110 June 2014 3-21
3Advanced Configuration
Alarm Actions:  Just as there can be many 
sources of alarms, there are also a variety of 
responses or actions to these alarms. Some of 
the alarm actions are only used with pan/tilt 
cameras. Actions such as Point, Load ScanList, 
Go To Preset, and Engage Radar Track would 
only be used with a pan/tilt camera and are not 
used with the FC-Series fixed camera. For the 
FC-Series, typically a rule will be configured to 
Send a Notification, Capture an Image, or 
generate an Output on the GPIO device. An 
example of each one of these configurations is 
provided below.
Selecting the Send Notification as the Action in 
the rule requires selecting a Notification List 
(Default List in this example) and that a Message 
System and a Notification List has been 
configured. Refer to 
Services Menu, pg. 2-8.
To attach a snapshot taken during the alarm, 
select All Non Radiometric—the FC-Series 
cameras do not take radiometric images. 
Each rule that sends a notification also has the 
option to send an activity report to the same 
notification list every 6, 12, or 24 hours. The 
activity report indicates whether or not an alarm 
was triggered during the specified time period. 
Note that this can be selected on a rule by rule 
basis.
Alarm Rule Examples:  The following examples show rules that control actions from alarms that are 
sourced internally from the camera. The first three lines and the fifth line of these rules are always the 
same as the alarm is coming from the FC-Series camera which is a single device (single IR sensor).
Enter
Subject
Enable each
Alarm Rule
Default
Settings
FC-Series Options 
Video Analytics,  
Radiometry IR (FC-Series R only), and 
GPIO
Single
IR Sensor 
						

							427-0073-12-12 Version 110 June 2014 3-22
3Advanced Configuration
Video Analytics Alarm to Email:  Shown at the 
right is an example of an alarm rule that causes an 
email notification (including a snapshot image) to 
be sent when a motion alarm occurs in VA Area 0 
or 1 (refer to 
Creating Motion Detection Areas, pg. 
3-5).
The Alarm Source Device Type is set to Video 
Analytics with Alarm Id 0,1 corresponding to VA 
Areas 0 and 1.
The Action, Send Notification, references the 
Default Notification List (refer to 
Notification Lists, 
pg. 2-9). When an email account is setup (Msg 
Systems, pg. 2-9), the Alarm Manager can attach a 
snapshot from the camera to an alarm email. 
Select All Non Radiometric for Attach Image 
File—the FC-Series cameras do not take 
radiometric images. 
GPIO Input to Snapshot:  Shown at the right is 
an example of an alarm rule that reads the GPIO 
input signal (refer to 
GPIO, pg. 3-14), then takes a 
snapshot and stores it in the Media Browser, pg. 3-
24.
The Alarm Source Device Type is set to GPIO with 
Input Id 1 corresponding to the GPIO input.
The Action, Capture Image File, takes a snapshot 
when the alarm occurs. Select All Non 
Radiometric for Snapshot Type—the FC-Series 
cameras do not take radiometric images.
Radiometric IR Alarm to GPIO Output:  Shown 
at the right is an example of an alarm rule that 
causes a GPIO output to be set when a 
Temperature Alarm is received (Alarm Id 1 from 
Radiometric IR is 1:SCR_SPOT on the Live Video 
page, refer to 
Live Video Page, pg. 2-3).
The GPIO Output State Mode can be set as Bound 
or Unbound. If Bound, when an alarm occurs, the 
output goes high and remains high until the alarm 
is cleared or the Output Reset Interval is reached 
(see 
GPIO, pg. 3-14).
If Unbound, when an alarm occurs, the output 
goes high and remains high until reset by the 
Output Reset Interval time-out or from a VMS (for 
example, from FSM using the IO Advanced panel).
Internal
Alarm
Enter
Subject
Output
duration 
						

							427-0073-12-12 Version 110 June 2014 3-23
3Advanced Configuration
3.2.2Files Menu
The admin actions for transferring files are accessed 
through the Files menu on the left side of the page. 
Selected actions from the Configuration and Media 
Browser are described below. 
Use the Configuration page to see the Nexus 
Configuration File, perform Backup & Recovery of local 
files (on the camera), and perform Upload & Download 
of configuration files to another computer for backup, or 
to install a new configuration file to the camera. 
Shown at the top of the screen is the configuration script file in a scrollable window. This can be useful 
if help is ever need help from a support engineer.
In the Backup & Recovery section, click the Restore link associated with the factory.defaults 
configuration to restore the camera to its factory settings. This file can not be modified or deleted, so it 
is always available.
Use the Backup button to make a backup of the 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 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.
Scroll down
to see entire
configuration 
						

							427-0073-12-12 Version 110 June 2014 3-24
3Advanced Configuration
Media Browser:  The Media Browser page shows all of the images captured by the camera as a 
result of an alarm action. The image files can be downloaded to another computer for backup. 
After selecting a file, the file will appear in the 
Preview window.
The file name contains the year, month, day, 24 
hour clock time, and the sensor that captured 
the image. In this case IR0 is the only sensor.
Select Download to download the selected file 
the PC. Select Refresh to check for any 
additional images since landing on the Media 
Browser page.
Select Edit to select and delete individual 
images or all images. Any time the camera is 
rebooted or the power removed, the media 
directory will be emptied. 
Select to preview
Select to Refresh
Select All
Select Individually
Select all media files by clicking on the Select 
All check box. If all files are not selected, the 
Select All box will have a minus sign.
The following prompt will appear prior to 
deleting any files. 
						

							427-0073-12-12 Version 110 June 2014 3-25
3Advanced Configuration
3.2.3 Product Info Menu
The admin functions accessed through the Product Info menu on the 
left side of the page are shown. Selected actions from the Config File 
page are described below. 
Use the Config File page to change the Friendly Name which 
appears in FSM by default. You can also include the Friendly Name on 
the video feeds and adjust its appearance on the OSD page (refer to 
On Screen Display (OSD), pg. 3-18). 
Click on the Update button to save the settings. The changes will not 
take effect until the server is stopped and started. 
Enter name
Click Update 
						

							427-0073-12-12 Version 110 June 2014 3-26
3Advanced Configuration
3.3 Restoring the Factory Settings
The camera comes configured from the factory with a default IP address (192.168.250.116), the login 
passwords (user, expert, fliradmin), and all of the other configuration parameters (stored in a file 
called server.ini). 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 temporarily connecting a loopback device to the Ethernet port during initial power-up (this 
can be accomplished by using conventional power rather than PoE+). Approximately 30 seconds after 
power is turned on, the loopback device should be removed to allow the camera to finish booting up.
Note
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 (including the IP settings, user passwords, and configuration file), and to 
revert to the same configuration and behavior as when the camera left the factory. 
The custom loopback connector is described below.
The RJ45 loopback termination ties pin 1 to pin 3, and pin 2 to pin 6. The other pins are not 
connected. This type of device is available commercially (the Smartronix Superlooper Ethernet 
Loopback Jack and Plug is one example), or it can be easily made with an RJ45 plug, a couple wires, 
and a crimp tool.
After the camera boots up, 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
The camera will not finish booting up while the loopback device is connected to the camera. The 
camera will display analog video, but the Nexus Server will not start until the loopback device is 
removed from the camera.
Pin #SignalTied to pin #
1Tr a n s m i t  +3
2Transmit - 6
3Receive +1
4UnusedN/A
5UnusedN/A
6Receive -2
7UnusedN/A
8UnusedN/A