FIRMWARE RELEASE NOTES ====================== Products affected: AXIS 210 Network Camera Release date: 2004-07-20 Release type: Production Firmware version: 4.10 File name: 210_410.bin Preceding release: 4.02 ------------------------------------------------------------------------------ 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) 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 210_410.bin or axis210.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. During this step, all LEDs will be off. 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\210\4_10> 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. The default password for the root user is "pass", unless this has been changed by the user. 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 210_410.bin or axis210.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. Step 3, Reboot: The FTP session terminates and the system restarts automatically. During this step, all LEDs will be off. 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.10 ============ News in 4.10 ============ 4.10:01 Support for generating MPEG-4 streams according to ISO/IEC 14496-2:2003 using the Advanced Simple Profile at level 3 or 5. The MPEG-4 stream is delivered using multicast RTP/UDP. 4.10:02 Support for decoding MPEG-4 streams using the Simple Profile or the Advanced Simple Profile has been added to AXIS Media Control. Requires DirectX 9, which can be installed using Windows Update. Note: The AXIS Media Control can be configured from the Windows Control Panel. For example, the multicast network interface to use can be configured. For more information, view the readme file available from the Control Panel. 4.10:03 Support for external video sources that deliver MPEG-2 or MPEG-4 streams. 4.10:04 Support for allowing the unit to be found using AXIS IP Utility v2.01. 4.10:05 Support for including trigger information in the Motion JPEG images and the MPEG-4 stream. More information can be found at http://www.axis.com/. 4.10:06 Third party software license texts added to the web interface. Improvements in 4.10 ==================== 4.10:07 Image quality and exposure dynamics have been enhanced. 4.10:08 More fine grained compression control for Motion JPEG. Different compressions are now achieved for 0, 10, 20, .. 100 (previously it was 10, 30, .. 90). 4.10:09 Improved Motion JPEG performance. 4.10:10 Improved accessibility of the product when using the AXIS Internet Dynamic DNS service and the Internet is accessed through a NAT with a dynamically assigned IP address. 4.10:11 Improved the web pages so they load faster. 4.10:12 The AXIS Media Control no longer unnecessarily decodes Motion JPEG images if the image is not visible on the display. Corrections in 4.10 =================== 4.10:13 If White Balance and/or Exposure Control are set to Hold and the product is restarted, they will be changed to Auto to prevent the initial startup values from being held. 4.10:14 The minimum bandwidth limit is now 30 kbit/s to make sure the web interface is always accessible. 4.10:15 A problem with retrieving motiondata.cgi without specifying the User-Agent has been corrected. Known limitations in 4.10 ========================= 4.10:16 After changing the "Log Level for email" setting you may have to restart the unit for the setting to take effect. 4.10:17 Adding a new event or modifying an existing event will restart all active events. 4.10:18 An active event will be stopped if the connection to the upload server fails. 4.10:19 Motion detection windows are adjusted so that their width and height are divisible by 8 (pixels). 4.10:20 When saving a snapshot image, some browsers (e.g. Mozilla) will fetch a new picture and the saved picture will not match the displayed snapshot. 4.10:21 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.10:22 The motion detection setup only works in Internet Explorer for Windows. 4.10:23 The Axis Media Control toolbar is not available when using the Mozilla and Netscape web browsers. This is because images are viewed with server push instead of Active X (AXIS Media Control). 4.10:24 The MPEG-4 stream cannot be uploaded by events. 4.10:25 The AXIS Media Control may stop displaying the MPEG-4 stream after the the screen saver has been active or the computer has been locked. Workaround: Reload the Live View page. 4.10:26 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. Application Developer Information ================================= Supported HTTP API Image Resolutions Resolution Exceptions ========== ========== 768x576 1) 704x576 1) 2) 704x480 2) 704x288 2) 704x240 2) 640x480 480x360 384x288 352x288 2) 3) 352x240 2) 3) 320x240 240x180 4) 192x144 176x144 2) 3) 176x120 2) 3) 160x120 1) Not available as bitmap (bmp) image 2) Not equally scaled 3) No support for 90/270 degrees rotation 4) 176x240 when rotated 90/270 degrees The following HTTP API groups are supported by the AXIS 210. 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 Motion Detection I/O IP filter 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