SOFTWARE RELEASE NOTES ====================== Products involved: AXIS 2130 PTZ Network Camera Release date: 2003-04-24 Release type: Production Software version: 2.34 Filename: 2130_234.bin Last preceding release: 2.32 ----------------------------------------------------------------------- Upgrade instructions: Important: 0. Upgrade to version 2.34 can only be done if version 2.12 or later is installed. 1. Make sure that "active applications" such as continuous transmission of images via ftp or smtp from the Axis Network Camera are disabled prior to initiating upgrade. 2. Make sure to take notes of your application/layout and other settings prior to upgrading since these settings will be lost during upgrade. 3. You must be at the command prompt and in the directory that contains the Upgrade File. Example: C:\Axis\2130\2_34> 4. Open an ftp connection to the unit you want to upgrade from a command prompt. (Do not use a "windows" based ftp-program for this, use only command line ftp programs!) 5. Login as root. The default password for the root user is "pass" unless changed by the user. You must be logged in as the root user to flash upgrade the unit. 6. Change to binary transfer mode by typing "bin" and press enter. 7. Type "hash" and press enter. (This will allow you to see how the upgrade progresses) 8. Type the command "put XXX.bin flash_all" where XXX.bin is replaced by the name of the name of upgrade file you downloaded (and maybe decompressed) from our site, it is typically named 2130_234.bin or axis2130.bin. 9. Wait for the flash load to finish, this may take 1-10 minutes. Always wait at least 10 minutes for the flash upgrade to complete. 10. Your unit will automatically restart using the new firmware. 11. Reconfigure your settings. RELEASE 2.34 ============ News in 2.34 ============ 2.34:1 AXIS products no longer synchronize simultaneously with the NTP server when e.g. switching to daylight saving time. 2.34:2 The Real Time Clock is reinitiated at reboot, which means no more clock problems after a battery replacement. 2.34:3 Multiple FTP servers can now be configured for image upload. If the primary server fails, the images will be sent to the secondary server. 2.34:4 All passwords within the parameter lists are now represented with asterisks (*). 2.34:5 It is now possible to specify an empty path for the FTP upload. Corrections in 2.34 since 2.32 ============================== 2.34:6 The former image transfer interruptions at low bandwidth have been eliminated. 2.34:7 Problems with the passive FTP mode have been resolved. 2.34:8 No new IP-address notification is sent as long as the IP address remains the same. 2.34:9 It is now possible to specify multiple E-mail recipients. 2.34:10 All references to the domain "somewhere.com" have been removed. 2.34.11 Configuration of the text color within the personalized layout is now effective. 2.34:12 A security flaw in the internal web server has been corrected. 2.34:13 The java applet has been upgraded. 2.34:14 The handling of large image buffers has been improved. 2.34:15 The alarm handling speed has been enhanced. 2.34:16 Some issues with discontinued video stream under certain conditions have been solved. 2.34:17 Some problems with the NTP communication have been solved. 2.34:18 The clock drift has been significantly reduced. 2.34:19 The event scheduler no longer tries to start applications after they have been disabled. 2.34:20 Alarm buffers configured without a pre-buffer now work correctly, the frame rate is no longer altered. 2.34:21 The body message when sending email messages is now corrected, the product access line is no longer duplicated. 2.34:22 The realm field stated in the HTTP header is now correct. Application developer / scripting news in 2.34 ============================================== 2.34:23 Configurable timeouts have been added for the SMTP, FTP and HTTP clients. 2.34:24 The status of the I/O ports can now be checked using the HTTP API. 2.34:25 It is now possible to set up buffers and specify parameters like e.g. the compression level over the HTTP API. 2.34:26 The handling of the HTTP API buffer commands has now been corrected. The following HTTP API groups are supported by the AXIS 2130. For more information please check the HTTP API document available at www.axis.com. Group Exceptions ===== ========== General Get property Jpeg/Mjpg PTZ I/O control Known limitations in version 2.34 ================================= L1. A maximum of one PHP3 script may run at any one time. L2. Up to 4 MB of RAM memory is available for pre/post alarm image storage.