Go to documentation repository
Improved the window for adding multiple events to the Incident handler (the Add button on the Incident handler settings panel):
In Incident manager, it is now possible to set the minimum and maximum height for a comment in the event handling logic
Added UPDATE_ESCALATE_STATUS command to Incident manager. The command can be used in scripts for escalating the specified events INC_SERVER
It is now possible to use an external database for the Incident Server
In the Incident manager, updated the Last comment and All comments columns: now only the first line of the comment is displayed in them, and the full comment is displayed in the tooltip
Updated the Incident handler: now when you select the events for display and processing, you can select any camera events, not just alarms
Now in Video surveillance monitor, the Direct3D display mode is used by default instead of DirectDraw
In the Monitor object, added a column with a unique camera identifier (Guid) to the table of the Camera list tab
Now, the sorting of the cameras list in the Video surveillance monitor functional menu (by ID or by name) can be set using the SortCamsById registry key
Adjusted the name settings for the final export file in the Export period:
if the Default file name checkbox is set, then the resulting file will have the name "<Camera and camera number><Date and time><Video episode number>.avi".
if the Default file name checkbox is clear, then the file path becomes editable and you can set your own file name in it.
Added the SET_FILTERS command to the Events protocol (EVENT_VIEWER), which can be used in scripts to filter out the events.
Added events to the Map (MAP):
ACTIVATE_OBJECT—activation of the object. The event is received when an object is selected (activated by a single mouse click) on the Map.
OBJDBLCLK—the event is received when you double-click on an object on the Map MAP
Optimized system performance when the MemFile registry key value is set to -1 (default):
now the statistics displays the buffer size for writing, the limit of which is set in the WriteBufferSize parameter;
added the FileSystem.PreAllocateFileSize parameter, which sets the minimum size of the created temporary file in MB;
added the FileSystem.WriteBufferMemoryLimit parameter, which sets the maximum possible size of the RAM buffer in MB for the channel before the data from the buffer is written to the archive.
These improvements are made so that frames are not skipped when recording to archive under high system load
Added a new SCRIPT_ERROR event for the SLAVE object. This event is generated if the script execution fails SLAVE
For the request API for receiving video subsystem events http://IP-address:port/web2/secure/events/ added the ability to specify several objects separated by commas in the objectId parameter, and to receive all triggers from objects of the same type Getting events of video subsystem in blocks
Supported the TLS version 1.2 certificate in the Web-server.
Now Axxon Player generates a text file AxxonPlayer.lh, which contains the log of video archive views via the Player
If Axxon PSIM is installed as a Service, you can now specify the executable file of the program module using the core_module_name key
In User permissions, added the Allow VMDA filters use option which allows the Operator to use templates
The release includes the Drivers Pack 3.75.30 for IP devices support. Detailed information about the Drivers Pack, where to find the latest set of drivers, and the list of supported hardware is available at https://www.axxonsoft.com/integrated_security_solutions/supported-ip/.
Run the newer version installation program and install Axxon PSIM over the 1.0.0 version. No need for uninstalling.