FIRMWARE RELEASE NOTES ====================== Products affected: AXIS 213 PTZ Network Camera Release date: 2005-03-24 Release type: Production Firmware version: 4.12 File name: 213_412.bin Preceding release: 4.03 -------------------------------------------------------------------------------- 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 213_412.bin or axis213.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. 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. 11. After the upgrade has completed, the unit will automatically initiate the system. FTP === 1. You must be at the command prompt and in the directory that contains the upgrade file. Example: C:\Axis\213\4_12> 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 213_412.bin or axis213.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. 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. 8. After the upgrade has completed, the unit will automatically initiate the system. RELEASE 4.12 ============ New in 4.12 ==================== 4.12: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.12: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. Improvements in 4.12 ==================== 4.12:03 The hostname is passed to the DHCP server. 4.12:04 Specifying the fps parameter in an HTTP API video request overrides the default frame rate setting. Corrections in 4.12 =================== 4.12:05 When saving settings on the TCP/IP page in the product's web interface, error 404 page was returned instead of the proper page. The correct page is now returned. 4.12:06 The hostname of the AXIS 213 is set uniquely and based on the serial number of the AXIS 213 ("axis-00408cxxxxxx" instead of "AxisProduct"). 4.12:07 Requesting multiple video streams by using HTTP-API, both with and without date and/or time overlay, will now give the expected results. 4.12:08 An issue with preset positioning using the 'on boot' trigger has been corrected. 4.12:09 In a rare case, the IR lamp did not turn off correctly. This issue is corrected now. 4.12:10 A problem with consecutive alarms has been corrected. 4.12:11 Rotating the image stream 90 or 270 degrees could sometimes lead to corrupt images. This has now been corrected. 4.12:12 A problem with FTP upload retries when a retry attempt does not succeed during the event type duration has been corrected. 4.12:13 Input/Output status is now correctly reported in the web interface. 4.12:14 The command for querying positions returns now the correct coordinates even when the image is rotated. 4.12:15 PTZ Queue request for control doesn't open unnecessary password prompts. Known limitations in version 4.12 ================================= 4.12:16 After changing the "Log Level for email" setting you may have to restart the unit for the setting to take effect. 4.12:17 Copying an event configuration does not work properly. Some parameters may not be copied correctly. Please verify each parameter value in the cloned event configuration. 4.12:18 Adding a new event or modifying an existing event will restart all active events. 4.12:19 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.12:20 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.12:21 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 ActiveX (AXIS Media Control). 4.12:22 PTZ click in image will not work when using the Java applet as the image viewer. 4.12:23 PTZ click in image coordinates will not be correct in Mozilla when resizing the image using the view size buttons. 4.12:24 Audio will only work with AXIS Media Control and Internet Explorer. 4.12:25 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. Application Developer Information ================================= The following HTTP API groups are supported by the AXIS 213 PTZ. For more information please refer to the HTTP API 2.00 document available at www.axis.com. Group Exceptions ===== ========== General Image and Video PTZ Audio I/O IP filter 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 'preset' PTZ.PresetPos 'preset_hidden' PTZ.PresetPos 'ptzaction' Event.E#.Actions 'smtpaction' Event.E#.Actions 'source' Sequence.S#.Source 'tcpaction' Event.E#.Actions 'tcp_config' Eventservers.TCP