FIRMWARE RELEASE NOTES ====================== Products affected: AXIS 216FD Network Camera Release date: 2015-03-27 Release type: Production Firmware version: 4.47.6 File name: 216FD_4_47_6.bin Preceding release: 4.47.5 ------------------------------------------------------------------------------ UPGRADE INSTRUCTIONS ==================== The firmware can be upgraded using Axis Camera Management 2.0, 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. RELEASE 4.47.6 ============== Improvements ============ 4.47.6:I01 Frequent changing of camera settings will now work over longer period of time. Known limitations ================= 4.47.6:L01 If you choose to rotate the image in the Video & Image setup, be aware that the coordinates for motion detection windows created in the Motion Detection setup will not be rotated. Workaround: When defining motion detection windows, temporarily configure the image for 0 degrees of rotation. Change back to the desired rotation again after having defined the motion windows. 4.47.6:L02 If you set compression to 0% the frame rate may decrease substantially for Motion JPEG for certain scenes. This is because the image size may not exceed 128 KB. Workaround: Set the compression to 5% instead. The image quality will not suffer noticeably, but the image size will be much smaller. 4.47.6:L03 Including format field #r, #R, #b or #B in the text overlay will show an incorrect frame rate and bandwidth usage when the frame rate is limited for Motion JPEG. 4.47.6:L04 If you have more than one IE window running the AXIS Media Control and audio enabled, you may experience a delay that increases over time in all but the topmost window. 4.47.6:L05 Viewing full screen and sequencing through different external video sources with different video streams in a sequence will switch the full screen mode off. 4.47.6:L06 The AXIS Media Control may stop displaying the MPEG-4 stream after the screensaver has been active, or when the computer has been locked. Workaround: Reload the Live View page. 4.47.6:L07 Using dual screens and moving the AXIS Media Control window from one screen to the other can result in unexpected behavior. Workaround: Reload the Live View page. 4.47.6:L08 The Axis Media Control should reload itself on audio configuration changes on server. Sometimes it does not. Workaround: Reload the Live View page. 4.47.6:L09 When using G.726 audio encoding, audio will not be available in QuickTime. Workaround: Choose G.711 or AAC encoding instead if you are using QuickTime. 4.47.6:L10 If viewing the image stream on Mac OS X with Mozilla Firefox using the AXIS Media Java Applet, a third party plug-in may be needed to get the browser to use the correct Java version. The Java Embedding Plug-in can be found at http://javaplugin.sourceforge.net/. 4.47.6:L11 If you use G.726 or AAC audio encoding, audio will not be available in the AXIS Media Java Applet. Workaround: Choose G.711 encoding when using the AXIS Media Java Applet. 4.47.6:L12 When saving a snapshot image, some Web browsers (e.g. Mozilla) will fetch a new picture and the saved picture will not match the displayed snapshot. 4.47.6:L13 The Mozilla Web browser does not always close the image stream properly when leaving the Live View page. Restarting the stream can sometimes fail as well. Restarting Mozilla solves these two problems. 4.47.6:L14 If the RTSP port is changed when the RTSP server is disabled, then "Unicast RTP" and "RTP over RTSP" will not work in AMC when the RTSP server is enabled again ("RTP over RTSP over HTTP" will however work). Workaround: Disable the RTSP server and then re-enable it again. 4.47.6:L15 Storing multiple parameters simultaneously (with ACM) can trigger unexpected behaviour. The workaround in most cases is to restart the camera. 4.47.6:L16 When retrieving two (or more) video streams with differing rotations, some frames may be of incorrect rotation. 4.47.6:L17 When using Flicker-free mode 50Hz, the exposure time cannot go below 1/100s despite having set Max Exposure Time to a faster exposure time. The reason is that there are no flicker safe exposure times below 1/100s for this flicker-free mode. The same applies to Flicker-free mode 60 Hz where the exposure time cannot go below 1/120s as this is the fastest flicker safe exposure time. Application Developer Information ================================= The AXIS VAPIX API - Application Programming Interface (available at www.axis.com) is supported by the AXIS 216FD. The following groups are supported by the AXIS 216FD. For more information, please refer to the AXIS VAPIX HTTP API specification version 2, part of the AXIS VAPIX API, available at www.axis.com Group Exceptions ===== ========== General Image and Video Video status Motion Detection I/O IP filter Audio Built in templates for dynamic parameters: Template Group ======== ===== 'event' Event 'external_video' ExternalVideo 'ftpaction' Event.E#.Actions 'ftp_config' EventServers.FTP 'httpaction' Event.E#.Actions 'http_config' EventServers.HTTP 'hwaction' Event.E#.Actions 'motion' Motion 'smtpaction' Event.E#.Actions 'source' Sequence.S0.Source 'tcpaction' Event.E#.Actions 'tcp_config' EventServers.TCP Supported AXIS VAPIX API Image Resolutions: Resolution Exceptions ========== ========== 640x480 480x360 352x288 1) 352x240 1) 320x240 240x180 176x144 1) 176x120 1) 160x120 1) Not equally scaled