FIRMWARE RELEASE NOTES ====================== Products affected: AXIS 240Q Video Server Release date: 2006-12-04 Release type: Production Firmware version: 4.40 File name: 240Q_440.bin Preceding release: 4.30 ------------------------------------------------------------------------------ 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 4.40 ============ New features ============ 4.40:F01 Support for IPv6. 4.40:F02 Support for QoS. The product uses the DiffServ model and marks the following classes: Live Video, Event/Alarm and Management. 4.40:F03 Support for 802.1x/EAPOL(Extensible Authentication Protocol Over Lan) using EAP-TLS (EAP-Transport Layer Security). 4.40:F04 Added a parameter containing the path to the administrator web page (root.Properties.API.HTTP.AdminPath). 4.40:F05 Now possible to disable network services such as FTP, RTSP etc. See System Options | Support | System Overview for a list of the services that can be disabled. 4.40:F06 Added process list, /proc/netstat, ifconfig and vmstatus to the Server Report. 4.40:F07 A toolbar with a play and stop button is now available when using the Mozilla/Firefox browser. 4.40:F08 AXIS Media Control now has a reconnection strategy accessible from Control Panel on the Windows client. This allows the user to decide how the AMC client should handle a loss of connectivity with the product, i.e., for how long the product will try to reconnect and at which interval. 4.40:F09 Now possible to configure the mail server's port (default 25). 4.40:F10 Added Areazoom. It is possible to draw an area in the Live View and zoom into it. This feature is only available for drivers which support absolute pan/tilt/zoom. 4.40:F11 Added settings of a time interval (or delay) between triggered events. In Triggered Event Type Setup, set min time interval between triggers is the minimum time period that the event must wait after a trigger before it will be possible to trigger it again. The interval starts as soon as the first trigger occurs. Note that, the shortest possible interval is 1 second and the longest is 23 hours, 59 minutes and 59 seconds. By default it is set to 00:00:00 which means no time interval. 4.40:F12 Added the possibility to schedule a Guardtour. From Event settings, choose to add a scheduled event. The guardtour will run as long as the event is active. If two scheduled guardtours overlap, the priority is given to the one scheduled to start first. The second sceduled guardtour will start when the first one is becoming inactive. Modifications ============= 4.40:M01 The view size buttons in Live View have been removed. 4.40:M02 Added Seoul in GMT+9 time zone. 4.40:M03 Reduced latency for I/O alarm trigger. 4.40:M04 PTZ: Added AXIS 295 joystick support. 4.40:M05 Allow setting the Device ID for PTZ control. 4.40:M06 Allow having the same preset position name on different video sources. 4.40:M07 Allow preset names including '&' characters. 4.40:M08 In Guardtour settings, a new parameter "Pause between runs" defines how long the guardtour will pause before starting a new sequence. 4.40:M09 In Guardtour settings, view time and move speed have changed place. Corrections in 4.40 since 4.30 ============================== 4.40:C01 Improved event error handling, especially while using motion detection 4.40:C02 When an event failed to upload its images, it could happen that the buffer data was not removed from the file system, eventually causing a 'Cache Full'. At this point no more images could be uploaded. This issue has now been corrected. 4.40:C03 The HTTP response is now correct when the time is set backwards using the VAPIX. 4.40:C04 It is now possible to use the 'force' option (param.cgi) in VAPIX. 4.40:C05 FTP login issue due to long signon message (longer than 256 chars) has been resolved. 4.40:C06 It is now possible to upgrade the product when NAT traversal functionality is enabled. 4.40:C07 In Guardtour settings, view time defines the time spent in a defined guardtour position. It is not needed to measure, and add the time for the motion of the controlled camera. 4.40:C08 Corrected RTC low voltage detection. When the battery was replaced, the system would continue claiming that the voltage was low. This is now corrected. 4.40:C09 Corrected Output monitoring. It is now possible to use the following VAPIX http request: http:///axis-cgi/io/output.cgi?monitor=1,2,... 4.40:C10 Corrected duplicate names in PTZ positions. It is now possible to use the same name for different predefined positions. Known limitations in 4.40 ========================= 4.40:L01 The verification of event duration configuration contains limitations and will not disallow alphabetic characters. 4.40:L02 During an HTTP upload, unnecessary log messages may appear and files may be missing in the uploaded file sequence. 4.40:L03 Rotated video streams are not rotated in Motion Detection setup. 4.40:L04 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.40:L05 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.40:L06 Motion detection windows are adjusted so that their width and height are divisible by 8 (pixels). 4.40:L07 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.40:L08 The Mozilla 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.40:L09 Viewing full screen and sequencing through different external video sources with different video streams in a sequence will switch full screen mode off. 4.40:L10 PTZ click in picture will not work when using the Java applet as the image viewer. Application Developer Information ================================= Supported HTTP API Image Resolutions Resolution Exceptions ========== ========== 4CIF 704x576 1) 704x480 2) 2CIFEXP 704x288x2 1) 704x480x2 2) 2CIF 704x288 1) 704x240 2) CIF 352x288 1) 352x240 2) QCIF 3) 176x144 1) 3) 176x120 2) 3) 1) Only available for PAL cameras 2) Only available for NTSC cameras 3) Not available for quad images 90/180/270 degress rotation is not supported for quad images. The Axis Video API - Interface Specification found at www.axis.com is supported by the AXIS 240Q. The following HTTP API groups are supported by the AXIS 240Q. For more information please refer to the HTTP API specification version 2, available at www.axis.com. Group Exceptions ===== ========== General Image and Video PTZ 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 'preset' PTZ.PresetPos 'preset_hidden' PTZ.PresetPos 'ptzaction' Event.E#.Actions 'smtpaction' Event.E#.Actions 'source' Sequence.S0.Source 'tcpaction' Event.E#.Actions 'tcp_config' EventServers.TCP