FIRMWARE RELEASE NOTES
======================

Products affected: AXIS 211 Network Camera

Release date:      2004-09-22

Release type:      Production

Firmware version:  4.11

File name:         211_411.bin

Preceding release: 4.10

------------------------------------------------------------------------------

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 211_411.bin or axis211.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\211\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 211_411.bin or axis211.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.11
============

Improvements in 4.11
====================

4.11:01 It is now possible to select the HTTP response format so that every row 
	in the header ends with \r\n instead of \n\n. For \r\n, add 
	'&responseformat=rfc' to the HTTP-API command.

Corrections in 4.11
===================

4.11:02 A restart of the web server upon changes in the Users configuration has 
	been fixed.

4.11:03 The HTTP server test procedure now returns the proper web page in cases 
	where new lines are included in the reply from the HTTP server.

4.11:04 Corrected one cause of the problem in earlier releases where the AXIS 211 
	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.11:05 Fullscreen mode no longer stops.

4.11:06 The web server occasionally stopped responding. This has now been corrected.

4.11:07 An FTP upload restarts now automatically when the connection to the FTP 
	server is re-established after a temporary break.

4.11:08 Running triggered and scheduled events at the same time sometimes made these 
	stop and not restart. This has now been corrected.


Known limitations in 4.11
=========================

4.11:09 After changing the "Log Level for email" setting you may have to
        restart the unit for the setting to take effect.

4.11:10 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.11:11 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.11:12 Adding a new event or modifying an existing event will restart all
        active events.

4.11:13 Motion detection windows are adjusted so that their width and height
        are divisible by 8 (pixels).

4.11:14 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.11:15 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.11:16 Motion detection setup only works in Internet Explorer for Windows.

4.11:17 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.11:18 Viewing full screen and rotating through different external video
        sources with different video streams in a sequence will switch the full
        screen mode off.

4.11:19 The MPEG-4 stream cannot be uploaded by events.

4.11:20 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.11:21 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 211. 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
