FIRMWARE RELEASE NOTES ====================== Products affected: AXIS 210A/211A Network Camera Release date: 2010-06-10 Release type: Service Firmware version: 4.47.1 File name: axis210A.bin Preceding release: 4.47 ------------------------------------------------------------------------------ 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.1 ============== Corrections in 4.47.1 since 4.47 ================================ 4.47.1:C01 In a rare case, unit might get inaccessible through HTTP after upgrade and change of HTTP authentication policy. 4.47.1:C02 More sensitive motion detection is introduced. 4.47.1:C03 Corrected a problem with sockets in motion detection. 4.47.1:C04 A time handler issue has been corrected. Known limitations in 4.47.1 =========================== 4.47.1:L01 When entering only hostname for NTP server DNS resolution might fail. Instead of "hostname" enter "hostname.mydomain" or use the ip-address explicitly. 4.47.1: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.1: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 instead of 200 while a higher framerate as 10 fps during 200 seconds might only give 1000 pictures instead of 2000. 4.47.1: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.1: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.1: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.1:L07 When viewing Live View using AMC and choosing MPEG4, go to setup in another access session and change image resolution. When going back to Live view, the image has changed resolution but not size as expected. Refresh Live View after changes. 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