IOI SD. Release Notes. Firmware Version

Transcription

1 IOI SD Release Notes Firmware Version Ver. 2 September 22, 2016

2 2016 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 Hollister Ave. Goleta, CA Phone: FLIR ( ) International: For technical assistance, please call us at or visit the Service & Support page at Document History Version Date Comment 2 September 22, 2016 Revised release 2 IOI SD FW v Release Notes September 22, 2016

3 Table of Contents Table of Contents Version Content Firmware Version Location... 5 Supported Products and Platforms... 7 Key Features Rebranding and New UI Look and Feel Automatic Calibration Support for FLIR Thermal Cameras Support for Third-Party Cameras Support for IOI HD Fixed Camera Hand-Off to PTZ Camera Support for Intrusion Detection on Presets Support for Windows Known Issues and Limitations in the Current Version Known Issues and Limitations from Previous Versions Upgrades Latitude Compatibility United VMS Compatibility Upgrade Procedure United 6.4 Update Patch United 7.0 Update Patch Disclaimer Appendices A.1. Binding a Camera to the TRK Encoder A.2. Configuring RTSP Support for a Camera on the TRK Unit September 22, 2016 IOI SD FW v Release Notes 3

4 Table of Contents List of Figures Figure 1: Horizon Line... 9 Figure 2: Analytics > Depth Screen Figure 3: Binding a FLIR Camera to the TRK Encoder Figure 4: Unit Information Screen Figure 5: PTZ Configuration Screen Figure 6: Analytics Tab Figure 7: RTSP Settings Dialog Box Figure 8: Camera Table IOI SD FW v Release Notes September 22, 2016

5 Version Content Version Content This release supports the key features listed in section 3 for the TRK-101 analytic encoder and TRK-101-P PTZ Tracker. Features and functions of the units are identical, except that the TRK-101 does not support the RS-485 connection nor PTZ functionality of the TRK-101-P. In addition to documenting the Key Features, these release notes cover Supported Products and Platforms, Known Issues and Limitations in the Current Version, Known Issues and Limitations from Previous Versions, Upgrades, Latitude Compatibility, and United VMS Compatibility. Warning: 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 available from here. September 22, 2016 IOI SD FW v Release Notes 5

6 6 IOI SD FW v Release Notes September 22, 2016

7 Supported Products and Platforms Supported Products and Platforms This version is applicable to the following products: Product Name TRK-101-P PTZ Tracker TRK-101 United 7.0 Update and higher DNA 1.0 or higher Description Encoder with built-in PTZ video analytics and H.264 compression. Supported by Latitude Update over 6.3 CP1. Supported by United 6.4 and 7.0 for Latitude, Horizon and Meridian. Encoder with built-in video analytics and H.264 compression. Supported by Latitude over 6.3 CP1. Supported by United 6.4 and 7.0 for Latitude, Horizon and Meridian. Update that supports binding FLIR cameras with TRK-101 and TRK-101-P. Binding TRK-101/TRK-101-P is supported only on Latitude. Horizon and Meridian support all other features. Click here to download the update file for Latitude, Horizon, or Meridian. DNA version or higher. Click here to download the latest DNA Release Notes. Click here to download the latest DNA User Manual. September 22, 2016 IOI SD FW v Release Notes 7

9 Key Features Key Features Version includes the following key features: Rebranding and New UI Look and Feel Automatic Calibration Support for FLIR Thermal Cameras Support for Third-Party Cameras Support for IOI HD Fixed Camera Hand-Off to PTZ Camera Support for Intrusion Detection on Presets Support for Windows Rebranding and New UI Look and Feel The TRK-101 and TRK-101-P have been rebranded as FLIR models and feature a new user interface. 3.2 Automatic Calibration The Automatic Calibration function automatically configures scene depth. The system discovers people in the scene and configures human markers automatically. This function eliminates the time and effort required to manually add human markers. The Auto Calibration algorithm calculates camera height, focal length, and tilt angle according to the scene depth. Note: The Auto Calibration function does not support multiple PTZ presets. To automatically configure depth settings 1. Verify that the camera is installed at a height of at least four meters (13 feet). 2. Verify that the horizon is less than 30% of the Field of View (FoV). Figure 1: Horizon Line September 22, 2016 IOI SD FW v Release Notes 9

10 Key Features 3. From the Setup tab, select Analytics > Depth. The Auto depth screen opens. Figure 2: Analytics > Depth Screen 4. From the Units drop-down list, select Feet or Meter. 5. Select Set estimated height. 6. Enter the estimated camera height in the text box. 7. Click START. The camera starts the automatic depth calibration procedure. 8. Be sure that a person is walking along the Y (Vertical) axis of the FoV while Auto Calibration is in process. When the progress bar reaches 100%, Auto Calibration is completed and the unit resets. Calculated results are displayed in the Results area. The unit displays the Step 2: Verification tab. Note: While Auto Calibration is in progress, you can proceed with the next steps in the analytic configuration if you are operating in the first mode (NVR mode). In all other modes, the video is not displayed in the web interface during Auto Calibration. This is the normal behavior. Caution: 1. The Auto Calibration algorithm takes at least five minutes to run. If you stop the procedure before the progress bar reaches 100%, the analytic process will reset. 2. If you change from Auto to Manual mode, you must wait until the analytic process resets in order to use Manual mode. 9. Verify that the human marker settings are correct by selecting the buttons in the top left corner of the screen. 10 IOI SD FW v Release Notes September 22, 2016

11 Key Features 10. In the Results area, verify that the horizon and camera height are correct. Note: If the results are unsatisfactory, run Auto Calibration again (follow Step #1 on-screen) or click MANUAL to manually configure the depth settings. 3.3 Support for FLIR Thermal Cameras The firmware supports the following FLIR thermal cameras: F-Series, FC-Series (R, S, and ID models) and TCX Series. For optimal performance, the following image settings are recommended on the F-Series and FC-Series camera Setup > IR web page: AGC > Gain: 8-10 AGC > Plateau: 110 AGC > ITT :120 Digital Detail Enhancement: Auto The camera s streaming settings must be: (a) D1, 4CIF, VGA, or 640x512; (b) H.264 (Main Profile only); (c) a bit rate lower than 1500 bps. Note: You must change the camera s factory default settings upon configuring the camera. Caution: Make sure that the camera is configured in the camera web page as PAL or NTSC according to the camera model type. The TRK unit must also be configured as PAL or NTSC according to the camera model type. Thermal cameras are supported by binding them to the TRK-101/TRK-101-P encoder via Latitude. See Appendix 1 for instructions how to bind the camera and encoder. The following schematic illustrates the connection. Figure 3: Binding a FLIR Camera to the TRK Encoder September 22, 2016 IOI SD FW v Release Notes 11

12 Key Features Each camera has its own syntax for the URL which connects it to the RTSP server and defines the video stream that is sent from the camera to the TRK unit via RTSP. After binding the camera and the TRK unit in Latitude, the camera s URL is displayed automatically in the Insert RTSP stream URL text box on the TRK s Setup > System > Unit Information screen Operating Modes section. If RTSP authentication is required, select the checkbox and enter the User Name and Password. Figure 4: Unit Information Screen Note: When using Latitude to bind the camera and encoder, Latitude automatically selects the fourth Operating Mode option (Digital input, digital analytics output over IP). The syntax for each supported camera is: Model F-Series and FC-Series (R, S, and ID models) TCX Series T43xxBN Syntax rtsp://<ip>/ch0 rtsp://<ip>/cam/realmonitor?channel=1&subtype=1&proto=onvif Note: RTSP Authentication is not required for these FLIR units. 12 IOI SD FW v Release Notes September 22, 2016

13 Key Features 3.4 Support for Third-Party Cameras The TRK-101 and TRK-101-P support the following third-party cameras: Axis Sony Bosch HIK For instructions how to configure viewing of the RTSP stream from the camera, see Appendix Support for IOI HD Fixed Camera Hand-Off to PTZ Camera TRK-101-P supports fixed camera hand-off from an IOI HD camera (CF-52x2-00 and CB-5222-x1) to a PTZ camera. Note: When configuring the hand-off in the TRK-101-P Camera > PTZ Setup > PTZ Synchronization screen, the IOI HD camera must be configured to D1 resolution. After completing the configuration, you may change the resolution to any supported resolution. 3.6 Support for Intrusion Detection on Presets The TRK-101 and TRK-101-P now support intrusion detection on PTZ presets for the following PTZ cameras: Quasar CP x Quasar CP x FLIR TCX DNZ30TL2R To add intrusion detection on presets 1. Bind the TRK unit to the PTZ camera in Latitude. See Appendix After binding the units, configure the TRK unit from its web interface. 3. Add presets on the TRK unit. 4. Configure rules and depths for each preset. 5. In the TRK unit, create a playlist if required. 3.7 Support for Windows 10 The TRK-101 and TRK-101-P now support the Windows 10 operating system when using the Internet Explorer browser only. Note: You must select Internet Explorer as your browser. The Windows 10 default browser, Edge, is not supported. September 22, 2016 IOI SD FW v Release Notes 13

15 Known Issues and Limitations in the Current Version Known Issues and Limitations in the Current Version The following table includes known issues and limitations in firmware version : BUG ID SEVERITY SUMMARY COMMENTS Bug Bug Bug Bug Bug Limitation Limitation Limitation Latitude > Presets > Quasar CP & TRK-101-P > > If user clicked on a Preset, after a while Latitude configured the camera as Preset 1. Latitude > Analytics > When binding a PTZ camera to the TRK-101-P, new messages were not displayed. Latitude > Bosch > It was not possible to bind the camera to the TRK-101-P in Decoder mode. Latitude > Quasar fixed cameras > On versions and lower, binding should be performed only in Decoder mode. Latitude > Quasar Gen II cameras > The Manual RTSP URL is not displayed automatically. TRK-101-P > The hand-off from a fixed camera to a PTZ camera can be configured when the TRK unit that is connected to the fixed camera is disarmed when not set to NVR mode. In PAL format, use any resolution except VGA in Decoder mode. TRK-101-P and Quasar CP-4221 PTZ camera > Camera setting web page on the TRK should be accessed only when the camera is online. Use Manual RTSP mode. Do not use Manual RTSP mode. Enter the RTSP URL manually. September 22, 2016 IOI SD FW v Release Notes 15

17 Known Issues and Limitations from Previous Versions Known Issues and Limitations from Previous Versions The following table includes known issues and limitations in firmware versions prior to : BUG ID SEVERITY SUMMARY COMMENTS Limitation Limitation Bug Bug Bug Limitation Use a bit rate 900 or higher with D1 resolution when a rule is defined on a static object. Use Tripwire and Fence rules when enhanced detection is disabled.. ioi - web - The user has to run IE10/11 as administrator for the Solo setup files to be created and saved on Windows 8 & 8.1. Depth > Solo Setup >The close-up view window always returned to the left upper corner of the image when the solo setup clip is running. A custom direction arrow is displayed on a Loitering rule when changing the rule from IT to Loitering. Latitude > FLIR T4350BN > Camera > Video > Sub Stream > Use VGA resolution with TRK analytics Bug The unit did not send on events to Gmail Bug Limitation Bug Bug Limitation Limitation FLIR PT-Series > Pelco > RS-485 serial control interfaces commands are opposite (moves up instead of down). FLIR Fixed family > TRK-101-P > Uncheck the Enable PTZ functionality checkbox in Latitude before binding the camera. In AUTO DEPTH mode, video was displayed during Auto Calibration only in NVR Operating Mode. In AUTO DEPTH mode, not all the information on the web page is displayed if the user changes to MANUAL DEPTH mode and clicks on a marker or guideline and returns to AUTO DEPTH mode. In Decoder mode, when the unit is powered on, the unit does not display its IP address in the analog video output. TRK-101-P > An IOI HD camera must be in D1 resolution when configuring PTZ hand-off during the binding procedure. Use Exchange or Yahoo Mail. In the PT camera Setup > Maintenance screen, set Sensor- >Communications- >Serial Remote->Serial Remote 1 Pilot Mode to "No", save, and restart the server. See Appendix. Auto Calibration is not affected. Refresh the screen. After configuring the hand-off, the IOI HD camera can be configured to any supported resolution. September 22, 2016 IOI SD FW v Release Notes 17

18 Known Issues and Limitations from Previous Versions BUG ID SEVERITY SUMMARY COMMENTS Limitation TRK-101-P > After binding, when binding a PTZ camera from Latitude, the Analytics tab is not displayed in the web interface sidebar after setting presets. Refresh the page after setting presets. The following table includes known issues and limitations in firmware version , reported after version : BUG ID SEVERITY SUMMARY COMMENTS Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Site Viewer There was no audio alert for the x units. The video flickers in the web interface when the user scrolls down using Windows 8.1 and Windows 10. A recording on the Site Playback page in MPEG-4 and H.264 did not play correctly. TRK-101-P It is possible to set the unit as a decoder and as a PTZ camera at the same time. The 64-bit version of VLC cannot be installed and used by Site Playback. There is no option to play a clip on a full screen on the Site Playback page in the web interface. It is not possible to play recordings in VLC in the Windows 7 32-bit version. There is no support for Unicode in DNA. Names with non-english characters are not displayed correctly. It is possible to search for an SoE video clip only in NVR mode. It is not possible to use enhanced detection in PTZ mode. 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. 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. 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. The audio alert did not function on the Site- Live page upon detection of an event. Limitation. This is supported on units with version & Disarm the unit from which you are playing the clip. Limitation. Decoder mode is not supported by PTZ cameras. The units require IE 32-bit browsers. Install the 32- bit VLC version. Limitation This is a bug in VLC that is corrected in a future VLC version. It is now available as beta version by VLC. Limitation. Only units that support SOE and are set in NVR mode can be queried for playback. Limitation Limitation. Disarm the fixed camera, sync the unit, and rearm the fixed camera. Select this setting (default) for an ioi encoder set up as a PTZ camera. 18 IOI SD FW v Release Notes September 22, 2016

19 Known Issues and Limitations from Previous Versions The following table includes known issues and limitations in firmware version , reported after version : BUG ID SEVERITY SUMMARY COMMENTS Bug The noise reduction function does not operate properly on MJPEG. Limitation Bug It was not possible to install ActiveX on 64-bit versions of Internet Explorer 9. Limitation Bug Web video rendering is supported only on display adapters that fully support Direct X (e.g., NVidia, ATI, and most Intel on-board adapters). Limitation September 22, 2016 IOI SD FW v Release Notes 19

21 Upgrades Upgrades Units with firmware version lower than version can be updated over the web or by using the Discovery Network Assistant (DNA) tool. From the unit s web interface, go to Setup > System > Firmware. Note: From the encoder s Setup > Camera > Streaming screen, select the upgrade file according to the camera s Video Standard (PAL or NTSC). Browse for the firmware file in the directory to which you saved the file. Press Upgrade. If you are upgrading from firmware version , follow the instructions in the Release Notes for firmware version September 22, 2016 IOI SD FW v Release Notes 21

23 Latitude Compatibility Latitude Compatibility The firmware was approved for Latitude: United 6.4 and 7.0 support TRK-101 and TRK-101-P on Latitude, Horizon and Meridian September 22, 2016 IOI SD FW v Release Notes 23

25 United VMS Compatibility United VMS Compatibility It is necessary to install an Update Patch in order the unit to operate with United VMS 6.4 and United VMS 7.0. Select the Update Patch file according the platform (Latitude, Horizon, or Meridian). Note: The following procedure should be performed only in one of the following cases: If you want to upgrade your VMS software to version 7.0 If you want to bind the TRK encoder to a PTZ camera with Latitude. Binding TRK-101 or TRK-101-P is not supported on Horizon or Meridian. If you are connecting to a third-party camera Warning: 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. 8.1 Upgrade Procedure If you do not have United VMS 6.4 or United VMS 7.0: If you have Latitude 6.2, first upgrade to Latitude 6.3. If you have Latitude 6.3, upgrade to United VMS Install United VMS 6.4 on all client and server machines. 2. Install the Update Patch or higher version on all servers. If you have United VMS 6.4, you can upgrade directly to United VMS United 6.4 Update Patch To install the United 6.4 Update Patch Download the Update Patch required for your VMS or NVR from here. Run the file on every server and workstation in the system. Upgrade the Directory/EDB. Upgrade each Archiver. After all the servers are upgraded, upgrade the workstations using the method below. In the Latitude client application, from the Help tab, select the Check for Updates option. A popup opens, indicating that there is an update to download from the Update server. Select Yes to download the update file. A popup appears on the screen. Click Install. The installation may take several minutes. September 22, 2016 IOI SD FW v Release Notes 25

26 United VMS Compatibility United 7.0 Update Patch To install the United 7.0 Update Patch ( or higher) Download the Update Patch required for your VMS or NVR from here. Run the file on every server and workstation in the system. Upgrade the Directory/EDB. Upgrade each Archiver. After all the servers are upgraded, upgrade the workstations using the method below. In the Latitude client application, from the Help tab, select the Check for Updates option. A popup opens, indicating that there is an update to download from the Update server. Select Yes to download the update file. A popup appears on the screen. Click Install. The installation may take several minutes. 26 IOI SD FW v Release Notes September 22, 2016

27 Disclaimer 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 All rights reserved. September 22, 2016 IOI SD FW v Release Notes 27

29 Appendices Appendices Binding a Camera to the TRK Encoder Configuring RTSP Support for a PTZ Camera on the TRK Unit The camera and the TRK-101/TRK-101-P are bound to each other from the Latitude AdminCenter. If you have a PTZ camera, skip to Step 7 below. Before binding a fixed camera, make sure that the camera is configured as a fixed camera in the Camera Type section of the TRK-101/TRK-101-P Camera > Type & Model page. If your fixed camera has Digital PTZ functionality, it must be disabled in Latitude because you must have a fixed Field of View in order for the analytics to work properly. Note: Binding TRK-101/TRK-101-P is not supported on Horizon or Meridian. To bind the TRK-101 or TRK-101-P to the camera if a fixed camera is discovered as a PTZ camera 1. Open the Latitude AdminCenter in the Physical View tab for the desired camera. 2. Select the camera. 3. Select the PTZ Configuration tab. Figure 5: PTZ Configuration Screen 4. If the Enable PTZ functionality checkbox is checked, uncheck it. 5. From the Toolbar at the top of the screen, click Save. Make sure that the camera icon is for a fixed camera. 6. Select the top-level System in the Camera Tree. September 22, 2016 IOI SD FW v Release Notes 29

30 Appendices 7. Select the Analytics tab. Figure 6: Analytics Tab 8. Select the camera that you want to bind from the Available Camera list. 9. Use the arrow button to add it to the Camera table. Caution: Make sure that the TRK unit is not attached to Latitude. 10. In the table, do the following: In the Connection Type column, from the drop-down list, select Analog or Manual RTSP (for IP cameras). In the Analytic Device IP column, enter the IP address of the TRK unit that you want to attach to the PTZ camera. i. If you select Manual RTSP, click the RTSP Setting button. The RTSP Settings dialog box opens. ii. Figure 7: RTSP Settings Dialog Box If the camera s RTSP URL is not displayed automatically in the Camera RTSP Stream URL text box, enter the camera s RTSP URL manually. For example, if the FLIR camera s RTSP URL is rtsp://<ip>/ch0, enter /ch0 in the Camera RTSP Stream URL text box. 30 IOI SD FW v Release Notes September 22, 2016

31 Appendices iii. If authentication is required for the RTSP connection, select the Authorization Required checkbox. Then enter the User Name and Password in the respective text box. Click OK. 11. Click Save. Figure 8: Camera Table For PTZ cameras, set the Rearm Time in the Auto Rearm column. This is the number of seconds until the camera is rearmed after being disarmed. The default is 30 seconds. Note: 1. Review the IOI PTZ Supported Cameras list for PTZ cameras supported by TRK-101-P at 2. On CP-4221 PTZ cameras, do not use VGA resolution on the camera in PAL format. 3. This feature currently is supported only on the FLIR CP x, CP x and DNZ cameras. 12. Configure the TRK encoder: a. On fixed cameras, from the Setup > Depth screen and Setup > Rules screen of the TRK unit s web interface, configure the analytic settings. b. On PTZ cameras, configure presets. Then configure depth and rule settings for each preset. September 22, 2016 IOI SD FW v Release Notes 31

32 Appendices The video stream of the camera is viewed on the TRK unit via an RTSP connection. Each supported camera has its own syntax for the URL that attaches it to the RTSP server. The URL is entered in the TRK-101/TRK-101-P Setup > System > Unit Information screen. See Figure 4: Unit Information Screen. The syntax for each supported camera follows. For <ip>, enter the camera s IP address. FLIR F-Series and FC-Series (ID, R, and S) rtsp://<ip>/ch0 FLIR TCX rtsp://<ip>/cam/realmonitor?channel=1&subtype=1&proto=onvif Quasar rtsp://<ip>/h264_2 Note: Quasar uses Stream 2 for RTSP streaming ( h264_2 ). Axis rtsp://<ip>:<rtsp_port>/axismedia/media.amp?videocodec=h264&audio=0&camera=1&fps=<fps>&compression=50&resolution=640 x480&videobitrate=<bitrate>&videobitratepriority=quality&videokeyframeinterval=<keyframe_interval> Where: <rtsp_port> used rtsp port (default 554) <fps> - frames per second required <bitrate> - desirable bitrate (bit per second should be set to 1500 and 1000 for static rules) <keyframe_interval> - desirable interval between key frames (GOP) in frames Note: Used VGA resolution (640x480) Example: rtsp:// :554/axismedia/media.amp?videocodec=h264&audio=0&camera=1&fps=25&compression=50&resolution=640x4 80&videobitrate=1500&videobitratepriority=quality&videokeyframeinterval=50 Note: The stream number is not defined as a parameter in the Axis syntax. The above parameters are configured directly in the Insert RTSP stream URL text box on the TRK-101/TRK-101-P Setup > System > Unit Information screen. No additional configuration is required in the camera. 32 IOI SD FW v Release Notes September 22, 2016

33 Appendices Sony rtsp://<ip>/media/video2 Note: Sony uses Stream 2 for RTSP streaming ( video2 ). Before entering the URL, the video stream parameters must be configured on the camera s web page. The video stream parameters cannot be configured in the Insert RTSP stream URL text box on the TRK-101/TRK-101-P Setup > System > Unit Information screen. Bosch rtsp://<ip>/video?inst=2 Note: Bosch uses Stream 2 for RTSP streaming ( video?inst=2 ). Before entering the URL, the video stream parameters must be configured on the camera s web page. The video stream parameters cannot be configured in the Insert RTSP stream URL text box on the TRK-101/TRK-101-P Setup > System > Unit Information screen. September 22, 2016 IOI SD FW v Release Notes 33

34 FLIR Systems, Inc Hollister Ave Goleta, CA USA PH: PH: (Sales) PH: (Support) FX: Corporate Headquarters FLIR Systems, Inc SW Parkway Ave. Wilsonville, OR USA PH: FX: Document: IOI SD FW v Release Notes Version: 2 Date: September 22, 2016 Language: en-us