FIRMWARE RELEASE NOTES ====================== Products affected: AXIS 212PTZ Video Camera Release date: 2009-06-29 Release type: Production Firmware version: 4.49 File name: 212PTZ_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 Logging. 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 which IP is connected, the user 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, i.e. on the same page where the root password is defined. 4.49:F05 Added a Event monitor function to VAPIX. By using this interface, an application can get information about all trigger information available in the product. 4.49:F06 Added Advanced MJPEG settings (Video&Image -> Advanced). Using these settings, you can easily control the frame size of the JPEG images. The compression level is then adjusted automatically if the images for some reason become too large (e.g. sensor noise at night, complex motive). 4.49:F07 Possibility to display dynamic user text in image text overlay is added. Please use the online help file on the camera for more information. 4.49:F08 Added possibility to start guardtour from an event. Modifications ============= 4.49:M01 The motion detection algorithm has been improved to work better under low light conditions and to be less sensitive for 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 with regards to sensitivity. Previously when using a high sensitivity almost any move caused 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:M03 In order to avoid incomplete server reports, the report is no longer displayed before its generating is finished. 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 with regards to stability. 4.49:M08 It is now possible to send TCP Notifications continously. 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 don't start motion data stream when adding, removing and saving motion windows. 4.49:C05 Only print nc's output if it returns an error code. Otherwise the webpage will report that connection failed if the tcp server sends any reply. 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 ================= 4.49:L01 Changing of brigthess can cause problems when changes are made in small steps, e.g. changing from 10 to 20 can cause no visual change. A workaround would be to first change from 10 to 50 and then 50 to 20, i.e. to make larger changes. 4.49:L02 When using IP address filtering, when not all referrals are allowed no videostream at all will be displayed and HTTP 403 will be returned. 4.49:L03 When using regular updates from AXIS Internet Dynamic DNS and update interval to 1 hour the actual interval will measure 1 hour 10 minutes. 4.49:L04 When streaming MJPEG over https the video and audio will be marked with an errornous DCSP. 4.49:L05 If using overlay text and having two or more streams, repositioning of overlay text isn't possible if not all streams are stopped. To reconfigure first stop all streams. 4.49:L06 When configuring an external video source and choosing a resolution and rotation for that source, the source will not turn up in the source drop down list. Application Developer Information ================================= Supported AXIS VAPIX API Image Resolutions Resolution Exceptions ========== ========== 640x480 480x360 352x288 1) 352x240 1) 320x240 240x180 176x144 1) 176x120 1) 160x120 1) Not equally scaled AXIS VAPIX API (Application Programming Interface) available at www.axis.com is supported by AXIS 212 PTZ. AXIS VAPIX RTSP API for MPEG-4 is supported and the following groups in AXIS VAPIX HTTP API are supported: Group Exceptions ===== ========== General Image and Video Video status Motion Detection I/O IP filter Audio PTZ PTZ driver update PTZ administation Set PTZ parameters PTZ control queue Built in templates for dynamic parameters are: Template Group ======== ===== 'button' PTZ.Auxiliary.A1.Button 'event' Event 'external_video' ExternalVideo 'ftpaction' Event.E#.Actions 'ftp_config' EventServers.FTP 'guardtour' GuardTour 'httpaction' Event.E#.Actions 'http_config' EventServers.HTTP 'hwaction' Event.E#.Actions 'motion' Motion 'position' PTZ.Preset.P0.Position 'ptzaction' Event.E#.Actions 'smtpaction' Event.E#.Actions 'source' Sequence.S0.Source 'tcpaction' Event.E#.Actions 'tcp_config' EventServers.TCP 'tour' GuardTour.G#.Tour