====================== Products affected: AXIS 212 PTZ Network Camera Release date: 2006-06-13 Release type: Production Firmware version: 4.34 File name: 212PTZ_434.bin Preceding release: None ------------------------------------------------------------------------------- UPGRADE INSTRUCTIONS ==================== The firmware can be upgraded using HTTP, FTP or AXIS Camera Management. HTTP ==== 1. Download the upgrade file to a directory that is accessible from your local computer. 2. Go to the product's start page (e.g. http://192.168.0.90). 3. Click the Setup link and log in as "root" (or any other user with Administrator privileges). You must be logged in as an Administrator to upgrade the unit. 4. Click System Options in the menu to the left. 5. Click Maintenance. 6. Click the Browse button in the Upgrade Server section. 7. Select the upgrade file you downloaded (and maybe decompressed) from our site. This file is typically named 212PTZ_434.bin or axis212PTZ.bin. 8. Click the Open button. 9. Click the Upgrade button in the Upgrade Server section. 10. Wait for the flash load to complete, which may take 1-10 minutes. The upgrade procedure is in four steps: Step 1, Shut down: Running applications are shut down and active connections are terminated. Step 2, Uploading firmware: The old firmware will be erased and the new firmware will be saved. During this step, the Power LED will blink green/amber. After a while the progress of the upgrade will be displayed in the Web browser. Step 3, Reboot: The system restarts automatically. Step 4, Reconfiguration: The new firmware settings are configured to match the previous settings. The Status LED will be amber during this step. 11. After the upgrade has completed, the unit will automatically initiate the system, during which the Status LED blinks amber. When initiation is complete and the system is ready for use, the Status LED will be green. FTP === 1. You must be at the command prompt and in the directory that contains the upgrade file. Example: C:\Axis\212PTZ\4_34 2. From the command prompt, open an FTP connection to the unit you wish to upgrade. (Do not use a Windowsbased FTP-program to do this, use only command line FTP programs!) 3. Log in as root. You must be logged in as the root user to upgrade the unit. 4. Change to binary transfer mode by typing bin and press enter. 5. Type hash and press enter. (This will allow you to see how the upgrade progresses) 6. Type the command put XXX.bin flash where XXX.bin is the name of the upgrade file you downloaded (and maybe decompressed) from our site. This file is typically named 212PTZ_434.bin or axis212PTZ.bin. 7. Wait for the flash load to complete, which may take 1-10 minutes. The upgrade procedure is in four steps: Step 1, Shut down: Running applications are shut down and active connections are terminated. Step 2, Uploading firmware: The old firmware will be erased and the new firmware will be saved. During this step, the Power LED will blink green/amber. After a while the progress of the upgrade will be displayed in the command prompt. Step 3, Reboot: The FTP session terminates and the system restarts automatically. Step 4, Reconfiguration: The new firmware settings are configured to match the previous settings. The Status LED will be amber during this step. 8. After the upgrade has completed, the unit will automatically initiate the system, during which the Status LED blinks amber. When initiation is complete and the system is ready for use, the Status LED will be green. AXIS Camera Management ====================== AXIS Camera Management is a powerful and efficient installation and management tool specially designed to be used with Axis network video products. Using standard network protocols and methods, the tool can automatically find and set IP addresses, configure, show connection status and manage firmware upgrades of multiple devices. AXIS Camera Management is free to download at www.axis.com. RELEASE 4.34 ============ 4.34 is the first official production release for the AXIS 212 PTZ. Known limitations in 4.34 ========================= 4.34:L1 If you set compression to 0% the frame rate may decrease substantially for Motion JPEG for certain scenes. This is because the image size may not exceed 128 KB. Workaround: Set the compression to 5% instead. The image quality will not suffer noticeably, but the image size will be much smaller. 4.34:L2 Including format field #b or #B in text overlay will show incorrect bandwidth usage when frame rate is limited for Motion JPEG. 4.34:L3 Viewing full screen and sequencing through different external video sources with different video streams in a sequence will switch the full screen mode off. 4.34.L4 Viewing full screen and saving a snapshot image using a joystick button will switch the full screen mode off. 4.34:L5 The AXIS Media Control may stop displaying the MPEG-4 stream after the screen saver has been active or the computer has been locked. Workaround: Reload the Live View page. 4.34:L6 If using dual screens and moving the AXIS Media Control window from one screen to the other, the MPEG-4 stream may stop updating. Workaround: Reload the Live View page. 4.34:L7 The Axis Media Control should reload itself at audio configuration changes on server. Sometimes it does not. Workaround: Reload the Live View page. 4.34:L8 If you use G.726 audio encoding, audio will not be available when using QuickTime as viewer. Workaround: Choose G.711 or AAC encoding instead if you are using QuickTime as viewer. 4.34:L9 If you use G.726 or AAC audio encoding, audio will not be available when using AXIS Media Java Applet as viewer. Workaround: Choose G.711 encoding instead if you are using the AXIS Media Java Applet as viewer. 4.34:L10 If viewing the image stream on Mac OS X with Mozilla Firefox or Camino using the AXIS Media Java Applet, a third party plugin may be needed to get the browser to use the correct Java version. The Java Embedding Plugin can be found at http://javaplugin.sourceforge.net/. 4.34:L11 The AXIS Media Control toolbar is not available when using the Mozilla Firefox and Netscape Web browsers. This is because images are viewed with server push instead of ActiveX (AXIS Media Control). 4.34:L12 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.34:L13 The Mozilla Web 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.34:L14 Panning and tilting by clicking in the image is not available when using QuickTime as viewer. Workaround: Use the pan and tilt bars instead. 4.34:L15 Zooming using the mouse wheel is only available using the AXIS Media Control or the AXIS Media Java Applet viewers. Workaround: Use the zoom bar instead. 4.34:L16 When audio is enabled and AXIS Media Control snapshot functionality is used in the Live View, the video stream will stop and Internet Explorer can stop responding. Workaround: Go to Control Panel > AXIS Media Control > Snapshot and uncheck the box "Open the snapshot folder in the background". This issue will be corrected in the next firmware. 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