FIRMWARE RELEASE NOTES ====================== Products affected: AXIS 207MW Network Video Camera Release date: 2006-09-05 Release type: Production Firmware version: 4.40 File name: 207MW_440.bin Preceding release: None -------------------------------------------------------------------------------- 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.40 ============ 4.40 is the first official production release for the AXIS 207MW. Known limitations in version 4.40 ================================= 4.40: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.40:L02 The Motion JPEG compression rate should not be set below 10% since it will give poor frame rates or may cause camera instability. 4.40: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.40:L04 If you have more than one IE window open running the AXIS Media Control and audio enabled, you may experience a delay that increases over time in all but the topmost window. 4.40:L05 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.40:L06 The Axis Media Control should reload itself on audio configuration changes on server. Sometimes it does not. Workaround: Reload the Live View page. 4.40:L07 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.40:L08 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.40:L09 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.40:L10 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.40:L11 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. Workaround: Restarting Mozilla solves these two problems. 4.40:L12 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.40:L13 Storing multiple parameters simultaneously (with ACM) can trigger unexpected behaviour. Workaround: In most cases restarting the camera will correct this. 4.40:L14 AMC may stop or restart after many reconnection attempts when streaming MPEG4 with AAC. This limitation has been corrected in a new version of AMC available from the AXIS web site. Workaround: Restart the application using AMC. 4.40:L15 In noisy or busy wireless environments the available WLAN data rate may drop, causing video artifacts to occur due to insufficient bandwidth being available to carry the video stream. 4.40:L16 If WPA-PSK wireless security is used and manual hex key configuration          is selected, the settings on the Wireless page cannot be saved until the manual hex key has been entered.          Workaround: Type in the manual hex key value before saving the page. 4.40:L17 Simultaneous use of different video formats, e.g. 16:9 and other resolutions, or simultaneous use of normal and inverted video rotation, will cause the frame rate to drop. Note that when motion detection always uses an uncropped, unrotated video stream. The image formats that can be used with motion detection with no frame rate penalty due to this effect are 1280x1024, 1280x960, 640x480, 480x360, 352x288, 320x240, 240x180, 176x144 and 160x120, all unrotated. 4.40:L18 Event triggered MPEG-4 file upload will stop working after a few hundred MPEG-4 files have been uploaded. Workaround: Restart the camera. 4.40:L19 Setting multiple event triggers where "Audio trigger" is one of the          triggers will not work as expected.          Workaround: Do not use "Audio trigger" in combination with other event          triggers or modify the event through VAPIX or the plain config interface. Application Developer Information ================================= The AXIS VAPIX API - Application Programming Interface (available at www.axis.com) is supported by the AXIS 207MW. The following groups are supported by the AXIS 207MW. 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, Bitmap, Image overlay Motion Detection I/O IP filter Audio Built in templates for dynamic parameters are: Template Group ======== ===== 'event' Event '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 'tcpaction' Event.E#.Actions 'tcp_config' EventServers.TCP Supported AXIS VAPIX API Image Resolutions: Resolution Exceptions ========== ========== 1280x1024 1280x960 1) 1280x720 640x480 1) 640x360 480x360 1) 480x270 352x288 1) 320x240 1) 320x180 240x180 1) 240x135 176x144 1) 160x120 1) 160x90 1) Not equally scaled