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

Products affected: AXIS 2460 Network DVR

Release date: 2003-10-21

Release type: Production

Firmware version: 3.11

File name: 2460_311.bin

Preceding release:  3.10

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

UPGRADE INSTRUCTIONS
====================
         

1.  You must be at the command prompt and in the directory that contains the
    upgrade file.
    For example: C:\Axis\2460\3_11>

2.  From the command prompt, open an FTP connection to the unit to 
    upgrade. (Do not use a Windows-based FTP program for this - use only 
    command line FTP programs!)

3.  Log in as root. The default password for the user root is "pass", unless
    this has been changed. 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_all" where XXX.bin is the name of the 
    upgrade file you downloaded (and maybe decompressed) from our site. This 
    file is typically named 2460_311.bin or axis2460.bin. 

7.  Wait for the flash load to complete, which may take 3-10 minutes. The
    upgrade procedure is in three steps:
    Step 1, Uploading firmware:
      The old firmware will be erased and the new firmware will be saved.
      During this step the Power LED will blink green and amber and all other
      LED:s will be off.
    Step 2, Reboot:
      The FTP session terminates and the system automatically restarts. During
      this step all LED:s will be amber.
    Step 3, Reconfiguration:
      The new firmware settings are configured to match the previous 
      settings. During this step the Status LED will be amber. 
   
8.  After the upgrade has completed, the unit will automatically initiate the
    system, during which the Status LED blinks amber. When the system is initiated 
    and ready for use, the Status LED will be green. 
    


RELEASE 3.11
============


New features in 3.11:
=====================

3.11.1  Progress when checking disks for errors is displayed.

3.11.2  Start and stop of events are logged in the info log.

3.11.3  New database lookup method makes searching for exact times in a 
	recording by moving the time bar in the video player much faster.
        


Corrections in 3.11 since 3.10:
===============================

3.11.4  Looking up video sequences by moving the time bar in the video player
        does not hang other live or player sessions.
        
3.11.5  If looking up a video sequence by moving the time bar in the video
        player took longer than 150 seconds, progress would stop at 99% and
        the player would hang. This problem is now corrected.
        
3.11.6  Time triggered events no longer stop 59 secs prematurely. Previously, 
	an end time of 20:59 would record until 20:59:00. It will now record 
	until 20:59:59, as explained in the user's manual.
        
3.11.7  When an event stop time is set to 23:59, no additional one second
	recording 00:00:00-00:00:01 is created.

3.11.8  Some events started to record two identical recordings when a camera
        was enabled. Only one of these recordings stopped when the event was
        ended, the other continued to record. This problem is now corrected.

3.11.9  Previously, no-video detection was too fast. Minor signal glitches 
	(e.g. when using video multiplexers) of up to 16 frames are now accepted.
        
3.11.10 Triggering events for an enabled camera without a video signal is now
        handled correctly. Previously, this caused recordings with incorrect 
	start times.
        
3.11.11 The old FTPserver (sftpd) is replaced by a newer (vftpd). The previous 
	version could time out a client when upgrading the firmware on systems 
	with a very large recording database (usually systems with 4 disks and 
	high resolution and/or low compression images).
        
3.11.12 The application that mails system logs will no longer put itself in a
        endless logging-loop when smtp errors occurr, e.g when an incorrect
        smtp server address is set.
        
3.11.13 Disabled the disk mount count on formatted disks. This prevents an
        unnecessary warning about error checking after 26 system starts.
        
3.11.14 Previously, disk error handling did not work if disk errors were 
	detected during a specific phase of the system setup (database search 
	and restoration). This is now corrected.
        
3.11.15 Internal client-sever communications sometimes failed at system
        shutdown, causing warning messages (IPC error). Now corrected.

3.11.16 System shell (ash) updated to a newer version.
        
3.11.17 Player.cgi arguments "step", "direction" and "keepalive" do not 
	require "frame", "startframe", "time" or "starttime" to be used.



Application developer / scripting in 3.11:
==========================================

The following HTTP API groups are supported by the AXIS 2460. For more 
information, please see the HTTP API document available at www.axis.com.


Group         Exceptions
=====         ==========
General       Get property
Jpeg/Mjpg     JPEG/MPEG quad, halfsize, fullsize, hugesize
              JPEG buffer
              JPEG/MPEG CGI only supports parameters camera and timeout
PTZ
Recording     Play recording requires either parameter sessionid or both
              parameter recordingid and parameter camera
              Play single image requires parameter step
I/O
Serial port
PPP
Event
Firewall



Known problems and limitations:
===============================    

             
L1.  Maximum number of events is 25, due to performance limitations.

L2.  Disk utilization is limited to 40GB per disk. Larger disks may be
     installed, but only 40 GB per disk will be used.

L3.  Recordings are not listed with 1/100 sec accuracy. All time and frame
     data is listed as xxxxxx:00.

L4.  Deleting (not removing) all Events will trigger a bug that prevents any
     new Events from being added.
     
L5.  Pressing any button in the player window before the first image has
     been displayed will cause the player to terminate the player session
     by sending illegal requests to the server.