FIRMWARE RELEASE NOTES ====================== Products affected: AXIS 240QB Video Server Release date: 2010-02-22 Release type: Production Firmware version: 4.49 File name: 240QB_449.bin Preceding release: 4.40 ------------------------------------------------------------------------------ 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.49 ============ New features ============ 4.49:F01 Added Access Log information. This log gathers information on accesses to the product and can be listed anytime from the log pages. 4.49:F02 Added Connection list. It gives an overview of the connections made to the product specifying the connected IP address, user name and protocol used. 4.49:F03 Added HTTP Digest Authentication. 4.49:F04 Added Secure Initial Configuration. This makes it possible to enable HTTPS the first time the user accesses the product, located on the same page where the root password is defined. 4.49:F05 Added Advanced MJPEG settings (Video&Image -> Advanced). Using these settings, the frame size of the JPEG images can be easily controlled. The compression level is then adjusted automatically if the images become too large (e.g. sensor noise at night,complex motion). 4.49:F07 Added the setting for a minimum trigger interval before the event is started. This can be used to trigger event after a trigger has been set active for a given amount of time. 4.49:F08 It is now possible to create a separate folder for each event when uploading images via FTP. The folder name can include modifiers commonly used in file names (see the online help for more information). N.B: This is only possible for triggered events. 4.49:F09 Added the possibility to display dynamic user text in image text overlay. (See online help file for more information) Modifications ============= 4.49:M01 The motion detection algorithm has been improved to work better under low light conditions and to be less sensitive to exposure changes. The number of false triggers should be lower with this improvement. Motion detection settings might need to be modified after firmware upgrade to assure the desired function. 4.49:M02 The motion detection algorithm has been improved in regard to sensitivity. Previously when using high sensitivity almost any movement would cause high red peaks due to noise generation. This has been improved and the new algorithm will only affect behaviour when using high sensitivity. 4.49:M04 The product will perform DST time adjustment according to the new rules valid in the USA. Re-apply and save the time zone and DST setting on the product for changes to take effect. 4.49:M05 New timezone for Venezuela has been added. 4.49:M06 The AXIS Media Control installation will now work on Windows Vista. 4.49:M07 Improved event handling in regards to stability. Corrections in 4.49 since 4.40 ============================== 4.49:C01 Corrected an issue in the Axis Internet Dynamic DNS functionality. The complete server list is now used if the first host name in the list cannot be resolved. 4.49:C02 It is now possible to add more than 12 users with usernames and passwords that have maximum length. 4.49:C03 The embedded HTTP client fills in the Host field in the HTTP header. 4.49:C04 When video stream is stopped motion data stream is not started when adding, removing and saving motion windows. 4.49:C06 When creating a self signed certificate, if the validity time entered is more than the maximal validity (defined on the web page), then set it to the maximum, and not to 30. 4.49:C07 Corrected an issue in the Web server so that it now handles manually created certificate files where LF at the end of the file may be missing. 4.49:C08 Corrected an issue regarding time limits for camera connections. The connection closed at the right time, but then it immediately reconnected. 4.49:C09 Restart_stream.cgi work as expected, i.e. a new I-frame is sent immediately. 4.49:C10 Removes duplicate HTTP header from response to call to /axis-cgi/view/imagesize.cgi. 4.49:C11 Corrected the guard tour handling to avoid some occasional lockups. Known limitations in 4.49 ========================= 4.49:L01 The verification of event duration configuration contains limitations and will not disallow alphabetic characters. 4.49:L02 During an HTTP upload, unnecessary log messages may appear and files may be missing in the uploaded file sequence. 4.49:L03 Rotated video streams are not rotated in Motion Detection setup. 4.49: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.49: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.49:L06 Motion detection windows are adjusted so that their width and height are divisible by 8 (pixels). 4.49: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.49: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.49: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.49:L10 PTZ click in picture will not work when using the Java applet as the image viewer. 4.49:L11 Upload a PTZ driver on camera and choose a specific camera type. Go to PTZ config -> Advanced and press restore button. The movement limits will be restored to overall limits and not to the ones specific to the chosen camera type. 4.49:L12 Upload a PTZ driver on camera. After upload, closing the window from "Close" button will redirect you to a blank page. Workaround: Close the popup using the "X" sign from the up-right corner of the window and/or refresh the browser. 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 240QB. The following HTTP API groups are supported by the AXIS 240QB. 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