FIRMWARE RELEASE NOTES ====================== Products affected: AXIS 210A/211A Network Camera Release date: 2008-10-09 Release type: Production Firmware version: 4.47 File name: 210A_447.bin Preceding release: 4.40.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 4.47 ============ New features ============ 4.47:F01 Added Access Logging. This log gathers information on accesses to the product and can be listed anytime from the log pages. 4.47: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.47:F03 Added support for Camera Tampering detection. The video stream is analyzed constantly to detect if the image changes significantly. This can detect if the lens is hooded, painted, severly defocused or redirected. The tampering detection is available in the event framework so an alarm can be sent. This functionality has to be configured to be enabled. 4.47:F04 Added HTTP Digest Authentication. 4.47:F05 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.47:F06 Added mirroring, i.e. possibility to mirror the video stream. It can be configured using VAPIX as well as through the GUI. 4.47:F07 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.47:F08 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.47:F09 Added the setting for a time interval (or delay) between triggered events. This is the minimum time period that the event type must wait after a trigger before it will be possible to trigger it again. The interval starts as soon as the first trigger occurs (see online help for more information). 4.47:F10 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.47:F11 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.47:F12 Possibility to display dynamic user text in image text overlay is added. Please use the online help file on the camera for more information. See also: http://www.axis.com/techsup/cam_servers/dev/cam_http_api_2.php# api_blocks_image_video_dynamic_text_overlay Modifications ============= 4.47: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.47:M02 The Server Report has been reformatted, in order to let the most important information come first. In order to avoid incomplete reports, the report is not displayed before its generating is finished. 4.47:M03 The product will perform DST time adjustment according to the new rules valid in the USA, starting 2007. More information about this change is available at: http://en.wikipedia.org/wiki/Energy_Policy_Act_of_2005 #Change_to_daylight_saving_time Re-apply and save the time zone and DST setting on the product for changes to take effect. 4.47:M04 New timezone for Venezuela has been added. 4.47:M05 The AXIS Media Control installation will now work on Windows Vista. 4.47:M06 Improved event handling with regards to stability. 4.47:M07 A new audio parameter, Audio.ReceiverTimeout, has been added. When receiving audio data from a client, the session is terminated if no data is received in this time span. Corrections in 4.47 since 4.40.1 ================================ 4.47: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.47:C02 It is now possible to add more than 12 users with usernames and passwords that have maximum length. 4.47:C03 The embedded HTTP client fills in the Host field in the HTTP header. 4.47:C04 When video stream is stopped don't start motion data stream when adding, removing and saving motion windows. 4.47: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.47: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.47: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.47:C08 In MPEG-4, audio and video syncronization has been improved. 4.47:C09 Corrected an issue regarding time limits for camera connections. The connection was closed at the right time, but then it immediately reconnected. 4.47:C10 The restart_stream.cgi now work as expected, i.e. a new I-frame is sent immediately. 4.47:C11 A change has been done that removes duplicate HTTP header from response to call to /axis-cgi/view/imagesize.cgi. 4.47:C12 Sending audio from PC to the camera could stop after a while. This issue is corrected now. Known limitations in 4.47 ========================= 4.47:L01 When entering only hostname for NTP server there will be problems with the DNS resolving. Instead one must use hostname + domainname, e.g. instead of "hostname" one has to enter "hostname.mydomain" or use the ip-address explicitly. 4.47:L02 When choosing an FTP/HTTP upload server and choose to upload events as long as trigger is active, entering a too high frame rate will give less uploaded pictures than a lower and more optimal frame rate. E.g. entering a framerate of 20 fps might give less pictures than 10 fps. 4.47:L03 Choosing a too high framerate during event upload through SMTP will cause less pictures to be uploaded compared to what's expected. A lower framerate gives higher accuracy. E.g. uploading 1 fps for 200 seconds might give 193 pictures while a higher framerate as 10 fps during 200 seconds might only give 1000 pictures. 4.47:L04 When having enabled ipv4 as well as ipv6 and creating a TCP event server, pressing "test" button causes a "502 Bad Gateway" error. 4.47:L05 Adding a "+"-sign in the message during pressing test for a TCP eventserver test will cause the "+" sign being omitted. E.g. message "my test + send" will be sent as "my test send" from the camera. 4.47:L06 During configuration of an FTP eventserver, leaving network address field blank and pressing test button will give rise to an error dialog. 4.47:L07 Viewing live view from AMC and choosing MPEG4. Go back to setup and change image resolution. Going back to Live View, the image has changed resolution but not size as expected. Refresh Live View page to get the desired result. Application Developer Information ================================= Supported HTTP API Image Resolutions Resolution Exceptions ========== ========== 768x576 1) 704x576 1) 2) 704x480 2) 704x288 2) 704x240 2) 640x480 480x360 384x288 352x288 2) 3) 352x240 2) 3) 320x240 240x180 4) 192x144 176x144 2) 3) 176x120 2) 3) 160x120 1) Not available as bitmap (bmp) image 2) Not equally scaled 3) No support for 90/270 degrees rotation 4) 176x240 when rotated 90/270 degrees The Axis Video API, RTSP - Interface Specification found at www.axis.com is supported by the AXIS 210A/211A. The following HTTP API groups are supported by the AXIS 210A/211A. For more information please refer to the HTTP API specification version 2, available at www.axis.com. Group Exceptions ===== ========== General Image and Video Video status Motion Detection I/O 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 'smtpaction' Event.E#.Actions 'source' Sequence.S0.Source 'tcpaction' Event.E#.Actions 'tcp_config' EventServers.TCP