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

Products affected: AXIS P1311 Network Camera

Release date:      2008-12-23

Release type:      Production

Firmware version:  5.01

File name:         P1311_5_01.bin

Preceding release: n/a

AMC version:	   5.4.17.13-1

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

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

The firmware can be upgraded using Axis Camera Management 2.0, HTTP or FTP.
Please follow the instructions from the user's manual, the web page at
http://www.axis.com/techsup/cam_servers/how_to_upgrade.htm or the file named 
howtoupgrade.txt.


RELEASE 5.01
============

5.01 is the first official release for the AXIS P1311.

Known limitations
=================

5.01:L01 The image is always showed with zero rotation at the Motion Detection
         and the Exposure settings page.

5.01:L02 The effect of backlight compensation on/off may not be noticable.

5.01:L03 Stream profile names are limited to alphanumerical characters.

5.01:L04 If IPv6 is enabled while IPv4 is disabled, the DHCP options received 
         from IPv4 are not removed. Also there is no IPv6 address in the mail 
         body of an SMTP test mail.

5.01:L05 The NTP implementation will not synchronize to NTP servers that
         signal an alarm condition (clock not synchronized) in its Leap
         Indicator.

5.01:L06 After changing the date/time of the camera, the video stream will 
         stop after 60 seconds with an RTSP session time out. It does not 
         matter if the media stream is started before or after the time is 
         changed.
         Workaround: Reboot the camera after the time has been changed 
         manually or by NTP.

5.01:L07 It is not supported to configure always multicast RTP.

5.01:L08 If three different types of MPEG streams are running concurrently 
         (e.g. with different resolutions), it will not be possible to start
         a fourth type of stream. This could prevent an upload or recording 
         event from running.

5.01:L09 The event combination option "Include pre-trigger buffer" and "Upload
         as long as the trigger is active" does not work together, only the
         pre-buffer is saved/uploaded.
         Workaround: Use post buffer as well.

5.01:L10 When an event or event server is added, modified or deleted all 
         running events will be stopped and restarted.

5.01:L11 When recording JPEG to SD-card, live view performance is degraded, 
         and full FPS is not possible.

5.01:L12 If the SD-card becomes full, is unmounted or the power to the device 
         is lost during an active storage recording, the ongoing recording 
         may be lost or made non-seekable.

5.01:L13 If there are many recordings on a SD-card in the unit, then the 
         FPS will be degraded and the video will stutter while the recordings
         are being read, i.e. when the card is mounted.

5.01:L14 It is not possible to play recordings directly from SD-card on a PC if
         the recording was terminated incorrectly (if the SD-card got full or 
         if the size of the recording reached 2GB), or if the recordings was
         done by a scheduled event. It may still be playable from the camera's
         Recording List web interface.

5.01:L15 It is not possible to play H.264 recordings directly from SD-card on a
         PC with some media players, e.g. VLC. These recordings are still 
         playable from the camera's Recording List web interface or Windows
         Media Player (with AXIS Matroska File Splitter).

5.01:L16 It is not possible to seek in an H.264 or MPEG-4 recording, i.e. you
         can't specify a certain time to start play back from.

5.01:L17 A scheduled recording will not be resumed if the SD-card is unmounted
         and remounted.
         Workaround: Disable and re-enable the event.

5.01:L18 If RTSP authentication is switched off, streaming H.264 with QuickTime 
         and other Apple compatible clients will not work as they require 
         authentication of the RTSP, but do not allow HTTP authentication.

5.01:L19 The AXIS Media Control client may stop displaying the H.264 video 
         stream after the PC has been locked.
         Workaround: Reload the Live View page.

APPLICATION DEVELOPER Information
=================================

The AXIS VAPIX Application Programming Interface is supported by the AXIS P1311.

The following groups are supported by the P1311. 
For more information, please refer to the AXIS VAPIX HTTP API specification 
version 3, part of the AXIS VAPIX API, available at www.axis.com.

Group            Exceptions
=====            ==========
General
Image and Video  Video status
Motion Detection
I/O
IP filter
Audio

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
'motion'         Motion
'smtpaction'     Event.E#.Actions
'recordaction'   Event.E#.Actions
'tcpaction'      Event.E#.Actions
'tcp_config'     EventServers.TCP

Supported AXIS VAPIX API Image Resolutions:

Resolution       Exceptions
==========       ==========

 704x576         1)
 704x480         1)
 704x288         1)
 704x240         1)
 640x480
 480x360
 384x288
 352x288         1)
 352x240         1)
 320x240
 240x180
 192x144
 176x144         1)
 176x120         1)
 160x120

1) Not equally scaled