FIRMWARE RELEASE NOTE ===================== Products affected: Axis Companion Recorder 8CH Release date: 2016-07-01 Release type: Production Firmware version: 1.00.0.1 File name: ACR_1_00_0_1.bin Preceding release: 1.00.0 -------------------------------------------------------------------------------- Upgrade instructions ===================== Upgrade the firmware with HTTP. Follow the instructions given in the User Manual, at http://www.axis.com/support/tecnical-notes/how-to-upgrade, or howtoupgrade.txt, which is included in the firmware folder. New Features ============ 1.00.0.1:F1 Added language support for the following languages: - Chinese (simplified) - Chinese (traditional) - French - German - Italian - Japanese - Polish - Portuguese (brasilian) - Russian - Spanish Corrections =========== 1.00.0.1:C1 Fixed a memory leak when the DHCP server option 'Avoid DHCP conflicts' was enabled. 1.00.0.1:C2 It is now possible to change UPNP name. 1.00.0.1:C3 Fixed a problem where occasionally the PoE controller did not boot up correctly. The device would then trigger PoE alert (device would beep/send emails according to configuration) with all ports status set to "Unknown device port status". 1.00.0.1:C4 Fixed a problem where occasionally during boot, there was a false PoE port overload alert, which was immediately cleared. This caused the device to beep once during boot and possibly send out an overpower email alert. 1.00.0.1:C5 It is now possible to remove the alert email server configuration. 1.00.0.1:C6 Solved problems with interruptions in the recordings when 'Avoid DHCP conflicts' was enabled. 1.00.0.1:C7 Solved problem whith disabling the DHCP server if the DHCP address range did not match the current IP settings. Known Bugs/Limitations ====================== 1.00.0.1:L1 If a non-supported PoE class 4 device is connected, Axis Companion Recorder will trigger an alert saying that the port is overloaded. When the device is then disconnected, this alert is not automatically cleared. Connecting/disconnecting any other camera clears the alert. 1.00.0.1:L2 It is not possible to connect a self powered PoE class 4 device. 1.00.0.1:L3 Sometimes at startup the LAN port does not get any link. When this happens the LAN LED stays unlit and the NVR can not be reached via LAN. Restarting the device solves the problem. 1.00.0.1:L4 WLAN might under some circumstances stop working. Temporarily reducing the load might solve the problem, otherwise a restart is required.