FIRMWARE RELEASE NOTES ====================== Products affected: AXIS A1001 Release date: 2016-06-20 Release type: Production Firmware version: 1.40.0.1 File name: A1001_1_40_0_1.bin Preceding release: 1.40.0 ------------------------------------------------------------------------------ UPGRADE INSTRUCTIONS ==================== The firmware can be upgraded using Axis Camera Management, HTTP or FTP. Please follow the instructions from the user's manual, the web page at http://www.axis.com/techsup/cam_servers/how_to_upgrade.htm or the file named howtoupgrade.txt. New Features ============ 1.40.0:F01 Added the possibility to export the event log from AEM to Excel (.xlsx) or plain CSV. 1.40.0:F02 New filter option in the event log in AEM. It is now possible to filter by a single user’s activities. 1.40.0:F03 New look and feel of the event logger page in AEM to support F01 and F02 without compromising AEMs user experience. 1.40.0:F04 Added API support for Aperio door monitoring and handle state detection (REX). Door monitoring without Aperio handle state detection is not supported. 1.40.0:F05 A new API has been added to fetch the total number of credentials in the system and as well as the number of disabled credentials in the system. 1.40.0:F06 A new default schedule has been added, "after hours" that is active Monday through Friday 17:00-09:00 as well as all of Saturday and Sunday. Corrections in 1.40.0.1 since 1.35.0 ==================================== 1.40.0:C01 An unnecessary lock transition (unlocked>locked>unlocked), can be noticed if performing an access request while the door is manually unlocked. 1.40.0:C02 It is not possible to access the device using the "access device" button in AVHS. 1.40.0.1:C03 Fixed a critical security vulnerability. Known Bugs/Limitations ====================== 1.40.0:L03 In Action Rule Setup, the text box for Additional conditions is out of the frame when using Explorer 10. 1.40.0:L04 When removing a group with a large amount of credentials being members of it, the deletion may sometimes fail and needs to be repeated. 1.40.0:L05 After a firmware update, the web browser cache may need to be cleared to avoid seeing pages originating from the old firmware. 1.40.0:L06 Specifying an IdPoint timeout value (waiting for PIN to be entered) greater than 10 seconds has no effect. 1.40.0:L09 If a LockDownDoor operation is performed towards a door that is unlocked, a subsequent LockDownReleaseDoor will not return the door to unlocked, but to locked. 1.40.0:L10 When using the API to add credentials with eg. CardRaw fields, where a hexadecimal representation of card data is used, it is important that lower case letters are used. 1.40.0:L14 Additional AccessDoor requests while a door is in Accessed state will not use the supplied AccessTime (if specified), but instead use the default access time of the door configuration. 1.40.0:L16 Changing the Time Zone will not work from ACS and ACM. 1.40.0:L18 It is not possible to create action rules with schedules, other than "Always (No Schedule)", when in a controller cluster. 1.40.0:L19 During start up of the device the web server is reachable earlier than in previous FW, before other sub-systems are operational, possibly resulting in AEM showing 'Failed to retrieve device info' on its overview page if accessed during this time. Reloading the page a few seconds later will resolve this issue. 1.40.0:L20 When Global Events is enabled, then action rules with additional conditions do not work and action rules with the schedule set to something other than Always will not work. 1.40.0:L21 The Long Access Time will not be shown in the Users report. 1.40.0:L23 If you have offline controllers in a controller cluster and try to remove one of the units that is online this requires a majority of all controllers being online excluding the controller being removed. 1.40.0:L24 If a door is placed in the state LockDown, a valid access will be shown in the event log as "Access Granted" even though the Access request was not approved. The door will not unlock. 1.40.0:L29 To change the recipient of an Action Rule, please click the "Modify..." button and change there. The drop-down in the Action Rule lists currently does not work. 1.40.0:L31 In Entry Manager Date & Time Settings you can only input the IP address of the ntp server, not the DNS name. DNS name of NTP server can be provided by going into Additional Controller Configuration > System Options > TCP/IP > Advanced > NTP Configuration. 1.40.0:L34 Creating an Action Rule triggering on Door Monitor with additional conditions or other schedule than Always(no schedule) will not work. 1.40.0:L35 If you have a door configured with a door monitor, the lock button in AEM will not immediately lock the door. It will only set the controller in a locking state. The door lock will be locked once the door monitor indicates that the door is closed. 1.40.0:L37 A schedule with a duration shorter or equal to one hour does not show its end time when viewed in "Show in calendar when the schedule applies". 1.40.0:L38 If the device is configured with two locks that are operating under scheduled unlock, the locks will lock after a system reboot even if the schedule states that they should be unlocked. 1.40.0:L42 If no NTP server is configured or if a NTP server is configured, but is not reachable, time synchronization in a controller cluster does not work.