SOFTWARE RELEASE NOTES ====================== Application: AXIS Perimeter Defender Release date: 2019-06-14 Release type: Production Software version: 2.6.0 File name: AXIS_Perimeter_Defender.exe Preceding Release: 2.5.2 ------------------------------------------------------------------------------- Contact Information =================== Please contact Axis Communications for product information, updates and support at http://www.axis.com. ------------------------------------------------------------------------------- Installation instructions ========================= Use AXIS Perimeter Defender application to install the ACAP and license key, calibrate perspective and define scenarios on the camera and pair cameras for AXIS Perimeter Defender PTZ Autotracking. For more instructions see the User Manual. Compatible products =================== See complete list of compatible products at www.axis.com. New Features in 2.6.0 since 2.5.2 ================================= * Added demo mode for AXIS Perimeter Defender PTZ Autotracking * Time-based filtering added for all scenarios – Intrusion and Loitering scenarios are now merged * Added Limit Pre-detection Trajectory in scenarios Changes in Axi Perimeter Defender PTZ Autotracking 1.0.3 since 1.0.2 ============================ F08: Fixed incorrect control when calibrated with pan close to 180° F09: Fixed large wobbling when movement appears at the edge of the PTZ field of view F10 Fixed issue where zoom would vary when out of zone targets were detected by APD F11: Improved error condition information on metadata (user is now made aware of why control doesn't start) F12: Fixed issue where PTZ would not start at home position Changes in 2.6.0 since 2.5.2 ============================ F01: Fix issue with multi-camera devices F02: Fix issue where it was possible to have an old configuration when creating a 2D scenario F03: PTZ pairing device selection no longer shown when single possibility available F04: Fixed issue where incorrect messages could be shown on a camera first connected with bad password F05: Fixed issue where user could be queried to restore last connections and nothing was restored F06: Fixed issue where scenario edition could be interrupted during multi-camera calibration F07: Fixed issue with Q3708-PVE that kept requesting the video source every time you start up APD. F08: Fixed the "Configure" tab under Outputs. The tab now contains the APIs for firmware 9.20 and higher as well as 9.10 or lower to the camera event system. Changes in 2.5.2 since 2.3.2 ============================ F01: Fixed issue where 2 calibration videos could coexist and prevent correct PTZ calibration. F02: Fixed issue where Outputs tab was not available for 2D analytics. F03: Fixed issue where burnt-in parameters were not available right after connection. F04 Fixed bug on AVHS where lists of servers would be incorrectly handled. F05: Much faster connexion time to AVHS servers when connecting as administrator account. F06: Improved stability through AVHS connections. F07: Fixed bug where activating anonymous viewer on camera would crash Axis Perimeter Defender. F08: Fixed crash caused by sending empty HTTP requests to Axis Perimeter Defender. Changes in 2.3.2 since 2.3.0 ============================ F01: Fixed burnt-in metadata support on FW 8.20 and later. F02: Fixed bug leading, in thermal mode, to vehicles not being classified when not selected in the scenarios. Changes in 2.3.0 since 2.2.0 ============================ F01: Improved Burnt-In rendering when Live Text Overlay is activated at the same time F02: Fixed Burnt-In incompatibility problem with View Areas whose number is greater than 1 F03: Fixed issue where clearing configuration would not reset analytics parameters F04: Fixed issue where available update would not be shown in AVHS connections Changes in 2.2.0 since 2.1.0 ============================ F01: Burnt-in metadata overlay: Support of all the resolutions compatible with the native stream resolution. Changes in 2.1.0 since 2.0.2 ============================ F01: Fixed issues when adding the license key when APD is set to Russian. F02: Fixed metadata archive retrieval method returns error 404 under AVHS F03: Fixed https connection through the setup interface for firmware 7.20 or higher Changes in 2.0.2 since 2.0.1 ============================ F01: Fixed metadata archive retrieval when method returns error 404. F02: Fixed possible application failure when start it with some rare camera configurations/calibrations. F03: Faster start time of analytics package. Changes in 2.0.1 since 2.0.0 ============================ F01: Fixed aspect ratio error with resolution 3x2. F02: Increased license expiration check. F03: Forbid creation of scenario with space in their name. Changes in 2.0.0 since 1.2.1 ============================ F01: Improved detection distance (up to 2x ) – refer to design tool for details. F02: Support added for most recent Axis cameras. F03: Scenarios are now visible when editing another scenario for easier PTZ zones definition. Considerations ============== CO1: It is not recommended to run other CPU demanding ACAP's at the same time on the camera. CO2: AXIS Perimeter Defender requires Windows 7, 8 or 10, Intel Core 2 Duo or later and 2GB RAM. C03: After upgrading firmware on the camera the ACAP will be removed and all the settings deleted. Make sure to save the camera configuration in the AXIS Perimeter Defender before the upgrade in order to load the old settings to the new camera firmware. Known Bugs/limitations ====================== KL01: Long-range mode is only available for older thermal devices KL02: Scene with moving trees can create a faulty calibration KL03: Error messages stay visible even if the camera is deleted or another camera selected KL04: Setup Interface is sometimes degraded when used using Remote Desktop KL05: Looping video in detection results (during calibration validation) may freeze interface for a few seconds depending on computer performance and recording length KL06: If one camera is selected, selecting the license folder will not install the camera license KL07: Interface may crash when too many devices are connected KL08: Same camera can be added with IP and hostname KL09: Camera live view becomes blank in edge-browser panel KL10: Installing a licence does not work if the folder has characters not supported by the OS KL11 Burnt-in Metadata Overlay and Dynamic Overlay form the camera will not coexist, please use the legacy Text Overlay as explained blow on "KL 12". KL12: Cameras with firmware version 7.20 or connected through AVHS can show double overlay if burnt-in metadata overlay is enabled on streams having the same resolution as the ones used by the Setup Interface. KL13: If enabling “burnt-in metadata overlay” and “text overlay” on firmware 8.20 with APD 2.3.2, does not work, please follow the instructions below. 1) On the cameras GUI access System>Plain Config>Image>Image I0 Text and set 'String' (if not set already) and 'Text enabled' to the parameters below. Do not forget to save the settings. String: %X Text enabled: "just tick the box" (It is also possible, to enable the legacy text overlay using the following VAPIX command: https://camera-ip-address/axis-cgi/param.cgi?action=update&root.Image.I0.Text.TextEnabled=yes). 2) Restart the ACAP on the camera, either through the camera GUI, or through the APD application. 3) Optionally, you can also remove the new dynamic text overlay if set or converted during the upgrade to firmware 8.20.