FIRMWARE RELEASE NOTES ====================== Products affected: AXIS P1344/P1344-E Network Camera Release date: 2011-10-27 Release type: Production Firmware version: 5.40.4 File name: P1344_5_40_4.bin Preceding release: 5.22.2 AMC version: 6.0.6.3-1 ------------------------------------------------------------------------------ UPGRADE INSTRUCTIONS ==================== The firmware can be upgraded using Axis Camera Management, 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. New Features/Functionality ========================== 5.40.4:F01 Edge storage with support for CIFS/SMB (Microsoft Network share). 5.40.4:F02 ext4 file system support for SD Card. Axis recommends SD Card users to use the camera to format the SD Card with ext4 instead of the default vFAT. ext4 will increase recording reliability compared to vFAT. Note that SD Cards formatted with ext4 cannot be read by a Microsoft PC without installing additional ext4 drivers on the PC. 5.40.4:F03 VAPIX Edge Storage API 1.0. See VAPIX documentation for further information. 5.40.4:F04 The internal Event Management system has been redesigned. The internal Utask has been removed and VAPIX has been extended with a new Event-API based on Web-Services. You may need to be cautious when upgrading a camera from a previous firmware that has user-defined events/action rules. The legacy user action rules in the camera will continue to work but will not be visible in the camera user interface. The user interface allows you to convert the old events, making them visible and editable in the GUI. This is not recommended when using a VMS with the old event API. However creating new events and keeping old events works fine. 1. Recurrence event: The camera can now execute actions periodically, for example every X minute, hour or day. 2. Additional Conditions: Action rules provide the possibility to use additional conditions that must be valid before an action is executed. Example of an action rule: Record video to SD Card upon Motion Detection but only if the digital input port is high. 3. Storage Available Detection: Possibility to trigger actions when the Storage Device (e.g. SD Card) is connected or disconnected. 4. Schedule profiles: Possibility to create schedules that can be used/reused in action rules. The camera also has some preconfigured schedule profiles. 5. Network Share Recipient: Possibility to upload/store images to a Network Share similar to the FTP upload. 6. Status LED action: Possibility to flash the camera Status LED upon a detected event. 5.40.4:F05 Event Management user interface (GUI) has been redesigned. "Event servers" are now called "Recipients". Motion Detection, Tampering and Audio Detection have been moved to a new menu group called "Detectors". 5.40.4:F06 All triggers except Tampering, Recurrence and some ACAP events are now stateful, meaning that action rules that depend on them will trigger on the state rather than the state change. 5.40.4:F07 Always Multicast. Provides the ability to multicast video regardless of clients accessing the streams or not. 5.40.4:F08 ONVIF 1.02 support. 5.40.4:F09 Server Report download. Possibility to download a ZIP-file server report (with or without camera snapshot). This simplifies the process of attaching the server report when submitting a support ticket. 5.40.4:F10 Audio Detection history graph (GUI). The audio history level graph simplifies configuration of audio detection. 5.40.4:F11 Continuous Recording user interface changes. The continuous recordings configuration and listing has been modified. 5.40.4:F12 Storage Management 1. Clean up policy is enabled by default and the default value for the parameter is 1 week. 2. Parameter for clean up level has been removed from web UI. The default value is approximately 80%. 5.40.4:F13 Recordings in general 1. The start time of a recording is updated when data is removed due to clean up policy. 5.40.4:F14 Port status is now located under System Options -> Ports & Devices -> I/O Ports. Modifications since 5.22.2 ========================== 5.40.4:M01 Parameter root.PTZ.ImageSource.I0.PTZEnabled is default set to false. 5.40.4:M02 Stream cache is now set to 30MB. Corrections since 5.22.2 ======================== 5.40.4:C01 Issue with latency/lag in recordings when using pre-buffer is solved. 5.40.4:C02 Frame rate limitation when switching from night to day light conditions now works as expected. 5.40.4:C03 Improved camera responsiveness. 5.40.4:C04 Issue with occasional Ethernet failures is solved. 5.40.4:C05 Fix included for '$' and '}' in password. 5.40.4:C06 Configuration of time zone for Australia will now appear correctly in the web interface. 5.40.4:C07 JPEGs are no longer influenced by the maxframesize option. 5.40.4:C08 It is now possible to use HTTPS and port forwarding. 5.40.4:C09 Output port can now be activated/inactivated via the web interface properly. 5.40.4:C10 Improved FTP upload function over longer periods. 5.40.4:C11 Improved memory handling when using motion detection. 5.40.4:C12 Corrected date string format in SMTP. 5.40.4:C13 I/O trigger data is now included in the video stream as expected. 5.40.4:C14 The relay output triggering via ONVIF interface now works. 5.40.4:C15 Up to 127 characters can now be used in the 'From email address' field. Known Bugs/Limitations ====================== 5.40.4:L01 It is recommended to unmount the SD Card before ejecting it. 5.40.4:L02 Recordings made with an earlier firmware than 5.20 will not be readable on the SD Card from the 5.40 firmware. Backup important recordings and reformat the SD Card after the firmware upgrade. 5.40.4:L03 Stream Profiles are not associated with any particular View area. They are profiles that can be used with any view area. The View area is not saved with the Stream Profile. 5.40.4:L04 Remote back focus operation will be disabled when the temperature is too low. Information will be shown in system log. 5.40.4:L05 Check and repair is only available if the file system is ext4. 5.40.4:L06 Recording streams to SD Card with a total bit rate above 12Mbit/sec may cause missing frames/sequences. 5.40.4:L07 When using action rule resulting in short recordings it is recommended to extend post-event time. 5.40.4:L08 With audio enabled, the initial connection latency is increased. 5.40.4:L09 Sometimes IR filter switches between ON/OFF after factory default when illuminance is 7-10 lux. APPLICATION DEVELOPER Information ================================= The AXIS VAPIX Application Programming Interface is supported by the AXIS P1344/P1344-E. The following groups are supported by the AXIS P1344/P1344-E. For more information, please refer to the AXIS VAPIX HTTP API specification version 3, part of the AXIS VAPIX API, available at www.axis.com. Group Exceptions ===== ========== General Image and Video Motion Detection I/O IP filter Audio Active Storage digital PTZ View Areas Temperature control Not Fan/Heater Focus Assistant Remote Zoom and Focus Only Remote Back Focus Built in templates for dynamic parameters are: Template Group ======== ===== 'button' PTZ.Auxiliary.A1.Button 'daynightaction' Event.E#.Actions 'event' Event 'ftp_config' EventServers.FTP 'ftpaction' Event.E#.Actions 'guardtour' GuardTour 'guardtouraction' Event.E#.Actions 'http_config' EventServers.HTTP 'httpaction' Event.E#.Actions 'motion' Motion 'ptzaction' Event.E#.Actions 'hwaction' Event.E#.Actions 'recordaction' Event.E#.Actions 'smtpaction' Event.E#.Actions 'tcp_config' Eventservers.TCP 'tcpaction' Event.E#.Actions 'tour' GuardTour.G#.Tour 'streamprofile' StreamProfile Supported AXIS VAPIX API Image Resolutions for AXIS P1344 Resolution Exceptions ========== ========== 1280x800 1280x720 1024x768 1024x640 800x600 800x500 800x450 640x480 640x400 640x360 480x360 480x300 480x270 320x240 320x200 320x180 240x180 176x144 160x120 160x100 160x90 1440x900 1) 768x576 1) 720x576 1) 704x576 1) 704x480 1) 704x288 1) 704x240 1) 384x288 1) 352x288 1) 352x240 1) 240x135 1) 192x144 1) 176x120 1) 80x50 1) 1) Not visible in web user interface