IOI SD Release Notes Firmware Version 2.2.0.16 Ver. 12 August 16, 2017
2017 FLIR Systems, Inc. All rights reserved worldwide. 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. 6769 Hollister Ave. Goleta, CA 93117 Phone: 888.747.FLIR (888.747.3547) International: +1.805.964.9797 www.flir.com/security For technical assistance, please call us at +1.888.388.3577 or visit the Service & Support page at www.flir.com/security. Document History Version Date Comment 12 August 16, 2017 Initial FLIR release 2 IOI SD FW v. 2.2.0.16 Release Notes August 16, 2017
Table of Contents Table of Contents 1. Version Content... 5 1.1 Firmware Version Location... 5 2. Supported Products and Platforms... 9 3. Key Features... 11 3.1 PTZ Tracking with PT-Series, PT-Series HD, and A310pt Cameras... 11 3.2 Hand-off from FLIR FC-Series ID Cameras to TRK-101-P... 13 3.3 Support for Third-Party Management System Vendors... 13 4. Known Issues and Limitations in the Current Version... 15 5. Upgrading the Firmware... 19 6. Latitude Compatibility... 21 7. Disclaimer... 23 Appendices... 25 A.1. Preparing the Camera for PTZ Tracking... 25 A.2. Binding the Camera to the PTZ Tracker via Latitude... 27 A.3. Binding the Camera with a Third-Party Management System or Analog DVR... 28 A.4. Setting the Camera Model on TRK-101-P... 30 A.5. Binding the FC-Series ID Camera to the TRK-101-P... 32 A.6. Camera Installation Guidelines... 35 A.6.1 Installation Best Practices... 35 A.6.2 Recommendations... 36 A.6.3 Site Design Considerations... 36 A.6.4 PTZ Hand-off Design Considerations... 37 A.7. Configuring Analog DVR Settings on TRK-101-P... 38 A.8. Control TRK Arm Status via IO Input... 39 A.9. Connecting Two TRK Units to a FLIR Multi-Sensor Camera... 42 August 16, 2017 IOI SD FW v. 2.2.0.16 Release Notes 3
4 IOI SD FW v. 2.2.0.16 Release Notes August 16, 2017
Version Content 1. Version Content This release supports the key features listed in section 3 for the TRK-101-P PTZ Tracker for the supported cameras. In addition to documenting the Key Features, these release notes cover Supported Products and Platforms, Known Issues and Limitations in the Current Version, Upgrading the Firmware, and Latitude Compatibility. Caution: This firmware should not be installed on units that do not support SoE (units shipped with firmware lower than version 2.1.1). If such a unit is upgraded with this firmware version, the Analytic Decoder mode of the IOI IP functionality will not operate. In this case, the unit will operate only in Analog mode. 1.1 Firmware Version Location This firmware version is located in the folder named 2.2.0.16, which can be downloaded from here. Select the ioi_sd_2_2_0_16_pal.utk file or the ioi_sd_2_2_0_16_ntsc.utk file according to your TV system. August 16, 2017 IOI SD FW v. 2.2.0.16 Release Notes 5
Version Content. August 16, 2017 IOI SD FW v. 2.2.0.16 Release Notes 6
8 IOI SD FW v. 2.2.0.16 Release Notes August 16, 2017
Supported Products and Platforms 2. Supported Products and Platforms This version is applicable to the following products: Product Name TRK-101-P PTZ Tracker FLIR PT-Series camera FLIR PT-Series HD camera FLIR A310pt camera Latitude 7.0 Update 7.0.0.5776 or higher DNA 1.0 or higher Description Encoder with built-in PTZ video analytics and H.264 compression. PTZ binding of the supported cameras is possible only when using Latitude 7.0.0.5776 or higher and TRK-101-P operating in Analog or Decoder (IP) modes. The PTZ Tracker is designed for perimeter protection and tracking objects on the ground. It is not designed to track objects on the water or in the air. Includes PT-606, PT-610, PT-612, PT-618, PT-625, PT-645, PT-606E, PT-610E, PT-612E, PT-618E, PT-625E, and PT-645E. Includes PT-606Z HD, PT-608 HD, PT-612 HD, PT-617 HD, PT-625 HD, PT-644 HD, and PT-602CZ-R HD. Supports A310pt-xx DLTV payload in IP and Analog modes. Supports A310pt-15-NTSC and A310pt-25-NTSC Thermal payload in IP mode only. Latitude update over 7.0 that supports PTZ tracking over multi-sensor Thermal PTZ cameras. DNA version 1.0.4.0 or higher. Click here to download the latest DNA Release Notes. Click here to download the latest DNA User Manual. Note: PTZ tracking is supported only on cameras operating at 25/30 fps. Units with 8.3/7.5 fps do not support PTZ tracking over the Thermal payload. August 16, 2017 IOI SD FW v. 2.2.0.16 Release Notes 9
10 IOI SD FW v. 2.2.0.16 Release Notes August 16, 2017
Key Features 3. Key Features Version 2.2.0.16 includes the following key features: PTZ Tracking with PT-Series, PT-Series HD, and A310pt Cameras Hand-off from FLIR FC-Series ID Cameras to TRK-101-P Support for Third-Party Management System Vendors 3.1 PTZ Tracking with PT-Series, PT-Series HD, and A310pt Cameras This firmware version fully supports PTZ Tracking on FLIR PT-Series, PT Series HD, and A310pt cameras. PTZ Tracking requires binding the cameras in a video management system. This can be done via either of these two options: Latitude VMS See Appendix A.2 Third-party management system See Appendix A.3 The options for the physical connection of the camera, PTZ Tracker and Latitude VMS are illustrated below. In the IP-only Connection with Latitude VMS illustration above, the TRK-101-P is configured in Digital input, digital analytics output over IP operating mode. When selecting Decoder mode in Latitude, the streaming settings are verified by Latitude and the operating mode is configured automatically by Latitude. See Appendix A.2. August 16, 2017 IOI SD FW v. 2.2.0.16 Release Notes 11
Key Features In the Analog Connection with Latitude VMS illustration above, the TRK-101-P is configured in Analog input, digital analytics output over IP operating mode. The operating mode is configured automatically when selecting Analog mode in Latitude. See Appendix A.2. In the IP-only Connection with Third-Party VMS illustration above, configure the TRK-101-P in Digital input, digital analytics output over IP operating mode. See Appendix A.3. In the Analog DVR Connection illustration above, configure the TRK-101-P in Analog input, analog video and analytics operating mode. See Appendix A.3. 12 IOI SD FW v. 2.2.0.16 Release Notes August 16, 2017
Key Features 3.2 Hand-off from FLIR FC-Series ID Cameras to TRK-101-P TRK-101-P now supports hand-off from FC-Series ID, in addition to already-supported hand-off from IOI HD and TRK-101-P. Note: 1. The FC-Series ID camera must have firmware version V2.2.03.P03 and above. 2. The FC-Series ID camera is discovered automatically only if: The camera and TRK-101-P are configured on the same VLAN on the TRK-101-P PTZ Setup > PTZ Synchronization screen The camera and the TRK-101-P are connected to the same switch 3.3 Support for Third-Party Management System Vendors The camera and the TRK-101-P are officially supported by several third-party management systems. The user should verify that the vendor supports both products. For complete details on each vendor s management system, refer to Supported 3 rd Party Platforms FLIR Security Cameras. Note: The following limitations on TRK-101-P functionality exist with third-party management platforms: No analytic overlays: the VMS is not capable of combining the metadata with the video stream Binding from TRK web interface No Manual PTZ and Auto-Rearm functions Limited arm/disarm control from the management system Note: ExacqVision VMS systems operate with TRK-101-P and the supported cameras with the above limitations. However, TRK-101-P has not been officially certified by ExacqVision. August 16, 2017 IOI SD FW v. 2.2.0.16 Release Notes 13
14 IOI SD FW v. 2.2.0.16 Release Notes August 16, 2017
Known Issues and Limitations in the Current Version 4. Known Issues and Limitations in the Current Version Note: This version does not support Backup & Restore from IOI HD cameras to/from the TRK-101/ TRK-101-P. Firmware versions that support this function are available from FLIR TCX. The following table includes known issues and limitations in the current version: BUG ID TYPE DESCRIPTION COMMENTS 44737 Bug 44735 Bug 44605 Bug 44573 Bug 44572 Bug 44539 Limitation 44550 Bug 44541 Bug 44490 Limitation 44437 Limitation 44388 Bug 43748 Limitation Type & Model screen > The Enable Noise Reduction setting cannot be saved. NVR operating mode > The video is corrupted when operating in 4CIF. Type & Model screen > Japanese GUI > The Start PTZ Setup button is not aligned correctly. TRK-101-P > The camera does not go to preset if armed by an event action. TRK-101-P > PTZ >Tracking triggers an ARM event (configured on the Events setup page) TRK-101-P and FLIR multi-sensor cameras > Hand-off > Camera does not respond to a handoff alarm that is received within 5 seconds after returning to a previous preset. A310pt > Thermal > PAL > Tracking is not supported. TRK-101-P > PT or Quasar cameras > The Save configuration occurs twice. TRK-101-P > Binding in VMS > The TRK web page "alarm" box is not synced with Latitude Analytics status after "clear alarm" command from Control Center. FLIR multi-sensor cameras & TRK-101-P > Web interface allows "GoToPreset" within 5 seconds from last "GoToPreset", which causes a queue of commands to the camera. TRK-101-P and Latitude 7 > After removing the bind, Latitude still displays the IOI presets. Latitude > Auto Rearm can cause TRK to be armed and therefore not stream video while configuring the TRK unit. Use D1 resolution. Add action Go To Preset as an event response. Wait 5 seconds between GoToPreset command. Before set up from the TRK web interface, tile must be closed in Control Center and make sure the unit is armed from UVMS. August 16, 2017 IOI SD FW v. 2.2.0.16 Release Notes 15
Known Issues and Limitations in the Current Version BUG ID TYPE DESCRIPTION COMMENTS 43676 Limitation TRK-101-P > Synchronize with NTP > Cannot insert server name (for example ntp.time.com). An error message is displayed. 43584 Bug Latitude > User can overwrite an existing preset. 43405 Bug 43173 Limitation 42991 Limitation 42957 Bug 42931 Bug 42804 Limitation 42708 Limitation 42362 Limitation 42243 Limitation 42194 Limitation 41987 Limitation On IE 9, the System > User Accounts screen is not accessible. FLIR FC-ID > When handing off to a PTZ camera from the FC-ID camera, the Last detection object feature does not work on the FC-ID camera. When handing off the camera to a PTZ camera, if the IOI HD streaming is on MJPEG, the video is not displayed on the TRK-101-P. Latitude > System Settings > Alarm types > Action > Units that are bound with activated alarms (analytics have been cleared) are not displayed as Available. When operating in DVR mode with Enhanced detection enabled, after clicking the Arm button, the unit reboots after defining depth. TRK-101-P and CP-4221-301 > Only VGA resolution is supported. TRK-101-P and Latitude 6.4.0.6852 > When binding a unit, the user does not receive a warning message that it is not possible to add new Presets in Latitude. TRK-101-P > A fixed camera should be disarmed and in Decoder mode when defining PTZ hand-off. In Decoder mode, when the unit is powered on, the unit does not display its IP address in the analog video output. FLIR Fixed family > TRK-101-P > Uncheck the Enable PTZ functionality checkbox in Latitude before binding the camera. Latitude > Presets > TRK-101-P and PTZ camera > When clicking a Preset, after a while Latitude configures the camera as Preset 1. 41933 Limitation The unit did not send E-mail on events to Gmail. 41920 Bug 41745 Limitation The batch Solo Setup recording is not working on units in Decoder mode. Latitude > FLIR T4350BN > Camera > Video > The resolution 640x360 is not support by the Analytics. Use numerical IP address (xxx.xxx.xxx.xxx). Occurs only with Quasar 30X. We recommend using IE 10 or 11. Changing the setup is supported only on H.264. Bind the units in Latitude and select Decoder mode on the TRK unit. This automatically sets camera and TRK settings. Works as designed. Configure presets from the TRK unit. Disarm the fixed camera before setting up the hand-off. See Appendix. Generic issue for PTZ binding. Use Exchange or Yahoo Mail. It is recommended to use Auto calibration. Use VGA resolution with TRK analytics. 16 IOI SD FW v. 2.2.0.16 Release Notes August 16, 2017
Known Issues and Limitations in the Current Version BUG ID TYPE DESCRIPTION COMMENTS 39318 Bug 39303 Bug 39295 Bug 39080 Limitation 36235 Bug 36163 Bug 36155 Bug 35896 Limitation 35632 Limitation 35610 Bug 35460 Bug 31659 Bug 31450 Limitation 25223 Limitation 20590 Limitation 20344 Limitation A custom direction arrow is displayed on a Loitering rule when changing the rule from IT to Loitering. Depth > Solo Setup >The close-up view window always returns back to the left upper side of the picture when the Solo Setup clip running. IOI > The user has to run IE 10/11 as administrator for the Solo Setup files to be created and saved on Windows 8 and 8.1. Use a bit rate 900 or higher with D1 resolution when a rule is defined on a static object. The audio alert did not function on the Site-Live page upon detection of an event. When selecting an IOI-controlled PTZ camera in Latitude, Meridian, and Horizon, the PTZ protocol type is listed as IOImage PTZ instead of IOI PTZ Tracker. Only IOI units that support SOE recording are listed in the Units drop-down list on the web interface in the Events > Responses page, including units that are added manually. It is not possible to sync the encoder when it is armed and set as a PTZ camera in Analog, DVR and Decoder modes, because there is no video stream. There is no option to play a clip on a full screen on the Site Playback page in the web interface. The 64-bit version of VLC cannot be installed and used by Site Playback. A recording on the Site Playback page in MPEG-4 and H.264 did not play correctly. The video flickers in the web interface when the user scrolls down using Windows 8.1 and Windows 10. Site Viewer > There was no audio alert for the 1.5.7.x units. Web video rendering is supported only on display adapters that fully support Direct X (e.g., NVidia, ATI, and most Intel on-board adapters). It was not possible to install ActiveX on 64-bit versions of Internet Explorer 9. Use IE 11. The noise reduction function does not operate properly on MJPEG. Select this setting (default) for an IOI encoder set up as a PTZ camera. Disarm the fixed camera, sync the unit, and rearm the fixed camera. The units require IE 32- bit browsers. Install the 32-bit VLC version. Disarm the unit from which you are playing the clip. This is supported on units with version 2.1.1 and 2.1.2. August 16, 2017 IOI SD FW v. 2.2.0.16 Release Notes 17
18 IOI SD FW v. 2.2.0.16 Release Notes August 16, 2017
Upgrading the Firmware 5. Upgrading the Firmware Units with previous firmware versions can be updated over the web or by using the Discovery Network Assistant (DNA) tool. Note: From the encoder s Setup > Camera > Streaming screen, select the upgrade file according to the camera s Video Standard (PAL or NTSC). To upgrade the firmware 1. Open the Setup > System > Firmware screen. 2. Browse for the firmware file in the directory to which you saved the file. 3. Click Upgrade. Caution: This firmware should not be installed on units that do not support SoE (units shipped with firmware lower than version 2.1.1). If such a unit is upgraded with this firmware version, the Analytic Decoder mode of the IOI IP functionality will not operate. In this case, the unit will operate only in Analog mode. August 16, 2017 IOI SD FW v. 2.2.0.16 Release Notes 19
20 IOI SD FW v. 2.2.0.16 Release Notes August 16, 2017
Latitude Compatibility 6. Latitude Compatibility Support for TRK-101-P with PTZ tracking on the PT-Series, PT-Series HD, and A310pt cameras is available only with Latitude VMS 7.0.0.5776 or higher. Refer to Latitude documentation for the upgrade procedure. Contact TCX to obtain the Latitude Update. August 16, 2017 IOI SD FW v. 2.2.0.16 Release Notes 21
22 IOI SD FW v. 2.2.0.16 Release Notes August 16, 2017
Disclaimer 7. Disclaimer By providing this document, FLIR Systems, Inc. is not making any representations regarding the correctness or completeness of its contents and reserves the right to alter this document at any time without notice. FLIR Systems, Inc. 2017. All rights reserved. August 16, 2017 IOI SD FW v. 2.2.0.16 Release Notes 23
24 IOI SD FW v. 2.2.0.16 Release Notes August 16, 2017
Appendices Appendices A.1. Preparing the Camera for PTZ Tracking Before following the procedure below, make sure that Scale Factor Speed is set to 1000 and Scale Factor is set to 10. Several files need to be uploaded for the camera to support PTZ tracking. To upload the required files 1. Download the version package that can be found here. Note: The TRK Ready folder contains the files required for supporting PTZ tracking. It also contains a folder with the TRK_Configuration.flir for the PT-Series and PT-Series HD cameras and another folder for the A310pt camera. 2. Stop the Nexus server. 3. If your camera s Nexus firmware is lower than 2.5.30.46, upload the Nexus firmware file (nexus-server-gd_thg_v2.5.30.46.zip) in the Maintenance > Files > Firmware tab. Skip this step if the camera s Nexus firmware is higher than 2.5.30.46. 4. Upload the Nexus Dictionary file (dictionary.txt) in the same tab. August 16, 2017 IOI SD FW v. 2.2.0.16 Release Notes 25
Appendices 5. Upload the Pelco-D Map file (PelcoD.map) in the Maintenance > Files > Config Files tab. 6. Upload the TRK_Configuration.flir macro file in the same tab (Select the correct file according to your camera model). 7. Run the Nexus Server. 8. If an analog connection is required, make sure it is enabled for the selected camera on the Maintenance > Sensor > Serial Remote screen. 26 IOI SD FW v. 2.2.0.16 Release Notes August 16, 2017
Appendices A.2. Binding the Camera to the PTZ Tracker via Latitude The multi-sensor camera and the TRK-101-P are bound to each other from the Latitude AdminCenter. Make sure that the camera is prepared for PTZ tracking. See Appendix A.1. To bind the TRK-101-P to the camera Open the Latitude AdminCenter on the desired site. Make sure that the TRK-101-P is not listed in the site. Select the Analytics tab. Select the camera that you want to bind from the Available Cameras list. Make sure that you select the correct scene (DLTV/IR). Use the arrow button to add it to the Camera table. Caution: Make sure that the TRK-101-P unit is not attached to Latitude. In the table, do the following: In the Connection Type column, from the drop-down list, select Decoder or Analog mode. Note: In Decoder mode, Latitude verifies the stream settings according to the table in Appendix A.3. for each model/payload. In the Analytic Device IP column, enter the IP address of the TRK unit that you want to attach to the PTZ camera. Set the Rearm Time in the Auto Rearm column. This is the number of seconds until the camera is rearmed after being automatically disarmed due to manual PTZ control. The Rearm countdown starts from the moment the camera tile is deselected in ControlCenter. The default is 30 seconds. Click Save. On the PTZ Tracker, when operating in Analog mode only, configure the correct camera model according to the table in Appendix A.4. On the PTZ Tracker, configure the TRK encoder presets. Configure Depth and Rule settings for each preset on the PTZ Tracker. Arm the camera from the web interface or from Latitude. August 16, 2017 IOI SD FW v. 2.2.0.16 Release Notes 27
Appendices A.3. Binding the Camera with a Third-Party Management System or Analog DVR Note: The following limitations on TRK-101-P functionality exist when using a third-party management system or without a management system: No analytic overlays: the VMS is not capable of combining the metadata with the video stream Binding from TRK web interface No Manual PTZ and Auto-Rearm functions Limited arm/disarm control from the management system To bind the camera on the TRK-101-P Select the camera(s) that you want to bind. Make sure that each camera is prepared for PTZ tracking. See Appendix A.1. If you are using an IP connection, do the following: Set the camera stream via 3 rd party VMS or camera web for each model: Model Bitrate FPS Resolution PT-Series DLTV PT-Series Thermal A310pt DLTV A310pt Thermal PT-Series HD DLTV PT-Series HD Thermal 1000 kbps 25-30 D1 VGA 640x512 (Native) On the TRK-101-P System > Unit Information screen, select Digital input. Digital analytics output over IP. 28 IOI SD FW v. 2.2.0.16 Release Notes August 16, 2017
Appendices On the System > Unit Information screen, enter the following RTSP URL in the Insert RTSP stream URL text box. For <ip>, enter the camera s IP address. <X> represents the stream number that was configured in the camera s web interface as per the table above. FLIR PT-Series and A310pt: o DLTV - rtsp://<ip>/ch2 o IR - rtsp://<ip>/ch0 FLIR PT-Series HD cameras: o DLTV - rtsp://<ip>/stream<x>/sensor1 o IR - rtsp://<ip>/stream<x>/sensor2 Set the camera model on the Camera > Type & Model screen. For more information, see Appendix A.4 for options. On the TRK-101-P Camera > Type & Model screen, enter the network details and enter 8090 in the Port text box. If you are using an analog connection: Select one of the Analog modes. For more information about the analog mode options, refer to Setting Operating Modes in the IOI HTML Edition Units User s Guide. Set the camera model on the Camera > Type & Model screen. For more information, see Appendix A.4 for options. August 16, 2017 IOI SD FW v. 2.2.0.16 Release Notes 29
Appendices A.4. Setting the Camera Model on TRK-101-P The table below describes the setup required on the TRK-101-P for each camera model, scene and connection type. The Camera Model column in the table refers to the driver that is selected from the Model dropdown list on the TRK-101-P Camera > Type & Model screen. xx in the Camera Model column stands for Analog or IP (for example, FLIR Analog A310- Thermal). The FOV/Zoom column refers to the options available when selecting the Camera Model. The column for camera models with a zoom lens is labelled Zoom (for example FLIR xx-606-uz). In the user interface, the field is labelled Max. Zoom. The column for camera models with a fixed lens is labelled FOV (for example FLIR xx-hd-thermal). In the user interface, the field is labelled Field of View. Note: Using FLIR cameras in Analog mode does not require network access to the camera nor to the TRK-101-P. However, there must be network connectivity between the TRK-101-P and the camera. This can be a local connection. Make sure to provide network details in the configuration wizard (also if operating in Analog mode). The port should be 8090. 30 IOI SD FW v. 2.2.0.16 Release Notes August 16, 2017
Appendices Binding the Thermal Scene Binding the DLTV Scene Model Number Camera Model FOV/Zoom Camera Model FOV/Zoom PT-606Z HD FLIR xx 606-UZ x4 PT-602CZ-R HD FLIR xx 602-CZ x15 PT-608 HD 8 PT-612 HD 12 FLIR xx PT-HD-Visible x30 PT-617 HD FLIR xx HD-Thermal 17 PT-625 HD 25 PT-644 HD 44 A310pt-15 A310pt-25 FLIR xx A310-Thermal 15 FLIR xx A310-Visible x30 PT-606 PT-606E 6 PT-610 PT-610E 10 PT-612 PT-612E 12 FLIR xx PT-Thermal PT-618 PT-618E 18 FLIR xx PT-Visible x30 PT-625 PT-625E 25 PT-645 PT-645E 45 August 16, 2017 IOI SD FW v. 2.2.0.16 Release Notes 31
Appendices A.5. Binding the FC-Series ID Camera to the TRK-101-P To implement a hand-off from the FC-Series ID camera to a PTZ camera, the FC-Series ID camera and PTZ Tracker (TRK-101-P) are bound together from the web interface of both units. The FC-Series ID camera should run V2.02 or higher. Note: 1. Before starting the procedure below, wait until the calibration of the FC-Series ID camera reaches 100% on the Live Video page. 2. Disarm the analytics by clicking the Analytics Disable icon on the FC-Series ID Live Video page. On the FC-Series ID camera Select Maintenance > Sensor > Communications > VMS Remote. Verify that the server is running. Click + (Plus). 32 IOI SD FW v. 2.2.0.16 Release Notes August 16, 2017
Appendices From the drop-down list, select IOI Interface. Click Create. Restart the server by doing the following: a. Click the green button next to Server Running to stop the server. b. Click the green button next to Server Stopped to start the server. On the Setup > Analytics screen, from the Calibration Mode drop-down list, select Auto or Manual to set the depth. Wait one minute after the process reaches 100%. On the TRK-101-P From the Camera > Type & Model screen, verify that the Camera Model is configured as PTZ. Click Start PTZ Setup. On the Detection and Tracking screen, select Detection from another camera with Automatic PTZ tracking. Click Next. Click Calibrate and follow the instructions on the web interface. Click Next. From the PTZ Setup > PTZ Synchronization screen, follow the procedure described in the IOI HTML Edition Units User Guide which can be downloaded from here. Refer to Step 3: PTZ Synchronization with Fixed Cameras in the section Using the PTZ Camera Definition Wizard. If the camera and encoder are located on the same VLAN, the camera s IP address is displayed automatically in the IP address text box. If the FC-Series ID camera is located on a different VLAN than the TRK-101-P, or if its IP address has changed, you must add the FC-Series ID camera manually in the Fixed Camera Selection section of the TRK-101-P PTZ Synchronization screen. In the IP Address text box, set the HTTP port to 8084, where the IP address is <IP address>:port (for example 173.25.19.111:8084). August 16, 2017 IOI SD FW v. 2.2.0.16 Release Notes 33
Appendices After binding the units, set 8 correlation points on the ground, as described in the procedure To set correlation points in a preset in the User Guide. You can set a few presets for each fixed camera. The PTZ camera will automatically go the relevant preset according to the intrusion location on the fixed camera. 34 IOI SD FW v. 2.2.0.16 Release Notes August 16, 2017
Appendices A.6. Camera Installation Guidelines Following are some guidelines for installing the camera. A.6.1 Installation Best Practices Thermal cameras should be installed at least 4 meters (13 feet) height. For improved performance at long distances, install the camera at least 8 meters (26 feet) high. Note: Quasar cameras should be installed at least 6 meters (20 feet) high. Following are the minimum and maximum distances recommended for PTZ tracking for the various models: Model Minimal Distance Maximum Distance [m] [ft] [m] [ft] Quasar 30X 10 33 250 820 PT DLTV 10 33 330 1083 PT-606 50 164 330 1083 PT-610 50 164 300 984 PT-612 45 148 200 565 PT-618 30 99 135 443 PT-625 20 66 100 328 PT-645 10 33 50 164 PT-HD DLTV 10 33 330 1083 PT-608 HD 48 158 250 820 PT-612 HD 45 148 165 541 PT-617 HD 30 99 115 377 PT-625 HD 20 66 80 263 PT-644 HD 10 33 45 148 PT-606Z HD 20 66 330 1083 PT-602CZ HD 20 66 640 2100 A310pt DLTV 10 33 330 1083 A310pt-15 35 115 130 427 A310pt-25 20 66 80 263 August 16, 2017 IOI SD FW v. 2.2.0.16 Release Notes 35
Appendices A.6.2 Recommendations The recommended camera mounting height is a by-product of many considerations. As a guideline, it should not be too high or too low. The higher the camera, the sharper the angle that the camera requires in order to see the ground and objects. This creates more depth in the scene. Mounting the camera too high is not recommended, because objects should occupy 10%-20% of the frame when using analytic presets. Mounting the camera too high requires a lot of zoom when using presets. It is recommended to use the default object size (49) or a setting within the range of 40-60 on the PTZ Setup > Tracking Parameters screen. Camera height should be measured relative to the scene plane. Users who are not professional installers should set the height to Unknown in the camera s web interface to allow the algorithm to calculate the mounting height. The horizon should be parallel to the X axis of the camera surface. The camera should be installed without any roll angle (variation from 180 along the longitude) or the minimal roll angle possible. After completing the depth configuration, verify that the horizon line (percentage of the camera FOV) was calculated properly. It is recommended that the horizon does not exceed 30% of the FOV, meaning that the scene occupies maximum 70% of the frame. A.6.3 Site Design Considerations Minimum camera mounting height: 4m/13 feet Note: 6m/20 feet is the minimum height for Quasar 30X cameras. Object size: 10%-20% of the scene Minimal tracking angle: 10 relative to the pole Maximal tracking angle: less than 90 relative to the pole 36 IOI SD FW v. 2.2.0.16 Release Notes August 16, 2017
Appendices PTZ tracking can be initiated by detection on presets, hand-off from a fixed camera, or clicking on the object (Click-and-Track) once this feature is released in United VMS. Note that it is not possible to configure the camera for hand-off from a fixed camera and detection on presets at the same time. A.6.4 PTZ Hand-off Design Considerations When bound to a FLIR multi-sensor camera, the system can support up to 30 presets. Hand-off can be configured from presets from multiple fixed cameras (see Figure 1) or multiple presets per fixed camera (see Figure 2) to arrive at a total of 30 presets on the PTZ camera. Figure 1: Multiple PTZ presets and fixed cameras Figure 2: Multiple PTZ presets with one fixed camera August 16, 2017 IOI SD FW v. 2.2.0.16 Release Notes 37
Appendices A.7. Configuring Analog DVR Settings on TRK-101-P When connecting to a DVR, configure the following settings: On the System > Unit Information screen, in the Operating Mode section, select Analog input, analog video and analytics (use with DVRs). Click Apply. On the Camera > OSD screen, select Enable analog video output. Click Apply. 38 IOI SD FW v. 2.2.0.16 Release Notes August 16, 2017
Appendices A.8. Control TRK Arm Status via IO Input On the Events > Responses > Triggering Event screen, click Add to configure Response_1. In the External alarm (dry contact) field, select Close. From the Actions tab, select Arm camera. Click Add to add a Go to Preset action. From the Action drop-down list, select Control PTZ camera. Do one of the following: Select Go to Preset. From the Go to Preset drop-down list, select the desired preset. Select After. In the After text box, enter 5 seconds. The rule arms the analytics, and the unit goes to the selected preset after 5 seconds. Select Start/Resume playlist. The rule arms the analytics and starts the predefined preset playlist. August 16, 2017 IOI SD FW v. 2.2.0.16 Release Notes 39
Appendices Click Apply. On the Events > Responses > Triggering Event screen, click Add to configure Response_2. Set External alarm (dry contact) to Open. 40 IOI SD FW v. 2.2.0.16 Release Notes August 16, 2017
Appendices On the Responses > Actions tab, from the Action drop-down list, select Disarm Camera. On the Actions tab, click Add to add another action. From the Action drop-down list, select Control PTZ Camera. Select Stop Playlist. Click Apply. August 16, 2017 IOI SD FW v. 2.2.0.16 Release Notes 41
Appendices A.9. Connecting Two TRK Units to a FLIR Multi-Sensor Camera To take full advantage of the multi-sensor camera, you can use two TRK-101-P devices run the analytics and PTZ tracking on both Thermal and Daylight scenes. This feature is supported only on PT-Series HD cameras. Both IP and analog connections to the TRK unit are supported. For this procedure, we define the TRK-101-P that is connected to the DLTV payload as Unit A and the TRK unit that is connected to the Thermal payload as Unit B. Note: If you are using Latitude ControlCenter, it is recommended not to use the Auto Rearm feature, but to manually rearm the unit after taking control of the unit. Disable the Auto Ream feature by removing the checkmark on the Analytics Tab in Latitude AdminCenter. To configure two TRK units with a multi-sensor camera On Unit A, complete the binding procedure and follow the calibration process on the web interface. Use only presets 1-15 for Unit A. On Unit B, complete the binding procedure and follow the calibration process on the web interface. Use only presets 16-30 for Unit B. Note: Do not use preset 31 even if it is displayed in the web interface. Set and match the time and date on Unit A and Unit B. This can be done using an NTP server or sync with PC time. Configure the following rules to make sure that only one of the units will be armed at the time. Do the following on Unit A: a. From the Scheduled Actions > Actions tab, click Add to create an action. b. From the Action tab, select Arm from the Action drop-down list to define an action. c. Click Add to add another action. d. Select Go to Preset from the Action drop-down list. 42 IOI SD FW v. 2.2.0.16 Release Notes August 16, 2017
Appendices e. On the Scheduled Actions > Schedule tab, define the time and date to activate this action. f. Click Apply. g. From the Responses > Triggering Event tab, click Add to add Response_1. h. Select Arm. i. On the Responses > Actions tab, from the Action drop-down list, select Disarm camera. August 16, 2017 IOI SD FW v. 2.2.0.16 Release Notes 43
Appendices j. Click the Perform on this unit link. k. In the Select remote unit popup window, set the IP address for Unit B. l. Click OK. m. On the Responses > Actions tab, click Apply. The IP address of Unit B is displayed in the link. On Unit B, repeat Step 5. 44 IOI SD FW v. 2.2.0.16 Release Notes August 16, 2017
FLIR Systems, Inc. 6769 Hollister Ave Goleta, CA 93117 USA PH: +1 805.964.9797 PH: +1 877.773.3547 (Sales) PH: +1 888.388-3577 (Support) FX: +1 805.685.2711 http://www.flir.com/security Corporate Headquarters FLIR Systems, Inc. 27700 SW Parkway Ave. Wilsonville, OR 97070 USA PH: +1 503.498.3547 FX: +1 503.498.3153 Document: IOI SD FW v. 2.2.0.16 Release Notes Version: 12 Date: August 16, 2017 Language: en-us