FIRMWARE RELEASE NOTE ===================== Products affected: Axis Companion Recorder 8CH Release date: 2016-05-18 Release type: Production Firmware version: 1.00.0 File name: None Preceding release: None -------------------------------------------------------------------------------- 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 ============ N/A Corrections =========== N/A Known Bugs/Limitations ====================== 1.00.0:L1 There is a memory leak when the DHCP server option 'Avoid DHCP conflicts' is enabled. 1.00.0:L2 It is not possible to change UPNP name. 1.00.0:L3 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:L4 Occasionally the PoE controller does not boot up correctly. The device will then trigger PoE alert (device will beep/send emails according to configuration) with all ports status set to "Unknown device port status". 1.00.0:L5 Occasionally during boot, there is a false PoE port overload alert, which is immediately cleared. This causes the device to beep once during boot and possibly send out an overpower email alert. 1.00.0:L6 It is not possible to remove the alert email server configuration. 1.00.0:L7 It is not possible to connect a self powered PoE class 4 device. 1.00.0:L8 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:L9 If the device is configured to automatically detect an external DHCP server (default behaviour) and a external DHCP server is present this could lead to interruptions in the recordings. Disabling the DHCP service on the device solves the problem. 1.00.0:L10 Disabling the DHCP server does not work if the DHCP address range does not match the current IP settings.