FIRMWARE RELEASE NOTES ====================== Products affected: AXIS 207W Network Video Camera Release date: 2006-02-03 Release type: Production Firmware version: 4.33 File name: 207W_433.bin Preceding release: None -------------------------------------------------------------------------------- UPGRADE INSTRUCTIONS ==================== The firmware can be upgraded using HTTP or FTP. HTTP ==== 1. Download the upgrade file to a directory that is accessible from your local computer. 2. Go to the AXIS 207W start page (e.g. http://192.168.0.90). 3. Click the Setup link and log in as root (or any other user with Administrator privileges) if you are prompted for a user name and password. You must be logged in as an Administrator to upgrade the unit. 4. Click System Options in the menu to the left. 5. Click Maintenance. 6. Click the Browse button in the Upgrade Server section. 7. Select the upgrade file you downloaded (and maybe decompressed) from our site. This file is typically named 207W_433.bin or axis207W.bin. 8. Click the Open button. 9. Click the Upgrade button in the Upgrade Server section. 10. Wait for the flash load to complete, which may take 1-10 minutes. The upgrade procedure is in four steps: Step 1, Shut down: Running applications are shut down and active connections are terminated. Step 2, Uploading firmware: The old firmware will be erased and the new firmware will be saved. During this step, the Power LED will blink green/amber. After a while the progress of the upgrade will be displayed in the web browser. Step 3, Reboot: The system restarts automatically. Step 4, Reconfiguration: The new firmware settings are configured to match the previous settings. The Status LED will be amber during this step. 11. After the upgrade has completed, the unit will automatically initiate the system, during which the Status LED blinks amber. When initiation is complete and the system is ready for use, the Status LED will be green. FTP === 1. You must be at the command prompt and in the directory that contains the upgrade file. Example: C:\Axis\207W\4_33> 2. From the command prompt, open an FTP connection to the unit you wish to upgrade. (Do not use a "Windows" based FTP-program to do this, use only command line FTP programs!) 3. Log in as root. You must be logged in as the root user to upgrade the unit. 4. Change to binary transfer mode by typing "bin" and press enter. 5. Type "hash" and press enter. (This will allow you to see how the upgrade progresses.) 6. Type the command "put XXX.bin flash" where XXX.bin is the name of the upgrade file you downloaded (and maybe decompressed) from our site. This file is typically named 207W_433.bin or axis207W.bin. 7. Wait for the flash load to complete, which may take 1-10 minutes. The upgrade procedure is in four steps: Step 1, Shut down: Running applications are shut down and active connections are terminated. Step 2, Uploading firmware: The old firmware will be erased and the new firmware will be saved. During this step, the Power LED will blink green/amber. After a while the progress of the upgrade will be displayed in the command prompt. Step 3, Reboot: The FTP session terminates and the system restarts automatically. Step 4, Reconfiguration: The new firmware settings are configured to match the previous settings. The Status LED will be amber during this step. 8. After the upgrade has completed, the unit will automatically initiate the system, during which the Status LED blinks amber. When initiation is complete and the system is ready for use, the Status LED will be green. RELEASE 4.33 ============ 4.33 is the first official production release for the AXIS 207W. Known limitations in version 4.33 ================================= 4.33:1 If you set compression to 0% the frame rate may decrease substantially for motion JPEG for certain motives. This is because the image size may not exceed 128 kb. Work around: Set the comnpression to 5% or above. The image quality will not suffer noticeably, but the image size will be much smaller. 4.33:2 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.33:3 If viewing the image stream on Mac OS X with Mozilla Firefox or Camino using the AXIS Media Applet, a third party plugin may be needed to get the browser to use the correct Java version. The Java Embedding Plugin can be found at http://javaplugin.sourceforge.net/. 4.33:4 The view size buttons in live view will not work if you are viewing via the QuickTime plugin. 4.33:5 Rotated video streams are not rotated in Motion Detection setup. 4.33:6 When starting a new live view stream or when getting a still image, running live view streams and events will be stopped for a short while. 4.33:7 When saving a snapshot image, some web browsers (e.g. Mozilla Firefox) will fetch a new picture and the saved picture will not match the displayed snapshot. 4.33:8 The Mozilla Firefox 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 Firefox solves these two problems. 4.33:9 The AXIS Media Control may stop displaying the MPEG-4 stream after the screen saver has been active or the computer has been locked. Workaround: Reload the Live View page. 4.33:10 If using dual screens and moving the AXIS Media Control window from one screen to the other, the MPEG-4 stream may stop updating. Workaround: Reload the Live View page. 4.33:11 The AXIS Media Control toolbar is not available when using the Mozilla Firefox and Netscape web browsers. This is because images are viewed with server push instead of ActiveX (AXIS Media Control). 4.33:12 Rescaling of video to 1/2 size in the Live View page can make the text overlay unreadable. 4.33:13 If the I/O input on the 207W is used and the electrical switch used bounces, then the 207W may reboot. Work around: Use a de-bounced switch. 4.33.14 Setting the same port as HTTP port and Alternate HTTP port will make the HTTP interface unaccessible. A factory default is needed to solve the problem. 4.33:15 If the WLAN configuration, e.g. ESSID or link encryption parameters, is modified to incorrect values the 207W may become unaccessible over HTTP for up to 20 minutes even after the configuration is corrected. 4.33:16 WLAN Ad-Hoc mode is non-working. 4.33:17 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.33:18 Accessing the web page for wireless configuration takes a long time due to the 207W scanning for wireless networks. 4.33:19 If WPA-PSK wireless security is used and manual hex key configuration is chosen then settings on the Wireless page can not be saved after the first time the manual hex key has been saved because the 207W does a format check on the blanked value and not the real key. Application Developer Information ================================= Supported HTTP API Image Resolutions Resolution Exceptions ========== ========== 640x480 480x360 352x288 1) 320x240 240x180 176x144 1) 160x120 1) Not equally scaled The Axis Video API, RTSP - Interface Specification found at www.axis.com is supported by the AXIS 207W. The following HTTP API groups are supported by the AXIS 207W. For more information please refer to the HTTP API specification version 2, available at www.axis.com. Group Exceptions ===== ========== General Image and Video Video status, Image overlay Motion Detection I/O 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