FIRMWARE RELEASE NOTES ====================== Products affected: AXIS 221 Network Camera Release date: 2005-12-09 Release type: Production Firmware version: 4.30 File name: axis221.bin Preceding release: 4.20 ------------------------------------------------------------------------------- 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 221 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 221_420.bin or axis221.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\221\4_30> 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 221_420.bin or axis221.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.30 ============ News in 4.30 ============ 4.30:N1 A System Overview web page has been introduced giving a quick overview of the status of the AXIS 221. 4.30:N2 Event handler support dynamic notification with new format codes. These new format codes affects and can be used in the following cases: The 'Subject' and 'Additional information' fields in E-mail upload/notification The 'Message' fields in HTTP notification The 'Message' field in TCP notification 4.30:N3 JavaApplet is now usable in Internet Explorer/Mozilla/Firefox/Safari for MJPEG. JavaApplet is also usable for setting up Motion Detection. Requires JVM (J2SE) 1.4.2 or higher, or JRE (J2SE) 5.0 or higher 4.30.N4 Quicktime is an option for viewing MPEG-4 streams. Used as default viewer for other browsers when MPEG-4 is default video format. Requires that "Video Object Type" is changed to "Simple". Note that Quicktime default will buffer stream which adds to latency. 4.30:N5 User data is now by default excluded from the MPEG-4 GOV header to ensure support by media players such as Real Player. To enable user data, set the UserDataEnabled parameter to "yes" in plain config, and restart the camera. Improvements in 4.30 ==================== 4.30:I1 Improved upgrade process over a slow connection. An upgrade attempt will no longer time out after 30 seconds. 4.30:I2 A stability issue that, in some circumstances, could cause the AXIS 221 to hang has been resolved. 4.30:I3 The IP address filtering has been improved to accept or deny addresses in IP address list. 4.30:I4 added several new time zones (to a total of 50): GMT-14, GMT-13, Newfoundland, Kathmandu, Rangoon, Norfolk, Fiji, Kamchatka, Marshall, Tongatapu, Chatham 4.30:I5 Possible to remove logmessages about time adjustments by adding -q to TIME_HAMDLER_OPTIONS. This is done in file /etc/rc3.d/S51time_handler with script editor. 4.30:I6 Use of wildcards supported when listing parameters through HTTP API. 4.30:I7 New HTTP API buffer commands have been added to retrieve several images within one command. 4.30:I8 An NTP server can be received from DHCP. 4.30:I9 Virtualinput.cgi can now handle delays same way as output.cgi. See Http-API for more information. 4.30:I10 Added max exposure time 1/60s. 4.30:I11 Network TCP/IP settings are split into Basic TCP/IP settings and Advanced TCP/IP settings. 4.30:I12 Event can now be triggered by change on input port and combination start-stops for motion detection. Corrections in 4.30 =================== 4.30:C1 Requesting several HTTP API video streams with/without the date and time will generate video with/without date and time overlay. 4.30:C2 A problem with FTP upload retries when a retry attempt does not succeed during the event type duration has been corrected. 4.30:C3 A problem with gaps in the file name sequence during FTP upload has been corrected. 4.30:C4 A problem monitoring I/O status has been corrected. 4.30:C5 Before uploading an overlay image it is checked to see if it is not too big. 4.30:C6 Corrected a problem with output.cgi/virtualinput.cgi on some browsers where / and \ would fail to change io-port. 4.30:C7 A problem with trigger data in MJPEG header fixed. IO0 (status for digital input 0) and M0 ... Mn (motion detection status for window 0 to n) now works as described at http://www2.axis.com/files/developer/camera/Trigger_data_1_1.pdf 4.30:C8 External sources which cannot be viewed using the current web browser are removed from the list on the Live View page. 4.30:C9 The FTP Server can now correct handle changed listen port. 4.30:C10 It should now be possible to configure the AXIS 221 while the maximum number of clients are connected. 4.30:C11 The hostname of the AXIS 221 is set uniquely and based on the serial number of the AXIS 221 (axis-00408cxxxxxx instead of AxisProduct). 4.30:C12 Verification of allowed characters in an event name or in an event server name has been corrected. 4.30:C13 A problem with sending e-mails with large bodies has been corrected. 4.30:C14 Corrected an issue with imagesize.cgi where it failed when camera wasn't specified. 4.30:C15 Corrected cause of the problem in earlier releases where the AXIS 221 could deny access to video streams when other clients were requesting frequent snapshots. AXIS Media Control displayed the message: 503 Error: Maximum number of clients reached. 4.30:C16 An email upload will no longer include empty files when the number of images in the buffer to upload is less than the images per mail configuration for the event type. 4.30.C17 Adjusted JPEG quantization to avoid washed-out pictures when setting compression to 25 Known limitations in 4.30 ========================= 4.30:L1 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.30:L2 Motion detection windows are adjusted so that their width and height are divisible by 8 (pixels). 4.30:L3 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.30:L4 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.30:L5 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.30:L6 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.30:L7 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.30:L8 A snapshot image of the MPEG-4 stream will not be aspect ratio corrected when using the AXIS Media Control to take the snapshot image while aspect ratio correction is enabled. 4.30:L9 The text overlay in a 90/270 degree rotated NTSC image is garbled in both MJPEG and MPEG-4 when the image width is not evenly divisible by 16. 4.30:L10 Including format field #b or #B in text overlay will show incorrect bandwidth usage when frame rate is limited for Motion JPEG. 4.30:L11 Rotated video streams are not rotated in Motion Detection setup. 4.30:L12 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. 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 Axis Video API, RTSP - Interface Specification found at www.axis.com is supported by the AXIS 221. The following HTTP API groups are supported by the AXIS 221. 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 Serial port 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