====================== Products affected: AXIS 216FD/216FD-V Network Cameras Release date: 2006-03-27 Release type: Production Firmware version: 4.34 File name: 216FD_434.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 product's 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). 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 216FD_434.bin or axis216FD.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\216FD\4_34 2. From the command prompt, open an FTP connection to the unit you wish to upgrade. (Do not use a Windowsbased 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 216FD_434.bin or axis216FD.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.34 ============ 4.34 is the first official production release for the AXIS 216FD. Known limitations in 4.34 ========================= 4.34:1 It is not possible to upload your own Web pages to the camera. 4.34:2 If you have choosen to rotate the image in the Video & Image setup, be aware that 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.34:3 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.34:4 Including format field #b or #B in text overlay will show incorrect bandwidth usage when frame rate is limited for Motion JPEG. 4.34:5 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.34:6 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.34:7 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.34:8 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.34:9 The Axis Media Control should reload itself at audio configuration changes on server. Sometimes it does not. Workaround: Reload the Live View page. 4.34:10 QuickTime may hang when viewing the MPEG-4 stream. If you experience this it may help to disable audio and text overlay. 4.34:11 The view size buttons in Live View will not work if you are viewing via the QuickTime plugin. 4.34:12 If you use 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.34:13 If viewing the image stream on Mac OS X with Mozilla Firefox or Camino using the AXIS Media Java 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.34:14 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 instead if you are using the AXIS Media Java Applet. 4.34:15 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.34:16 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.34:17 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. Application Developer Information ================================= 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 The AXIS VAPIX API - Application Programming Interface - found at www.axis.com is supported by the AXIS 216FD. The following groups are supported by the AXIS 216FD. Fore 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 are: 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