Documentation for Monitoring 13.0. Documentation for other versions of Monitoring is available too.

Previous page Agent of Control technical condition data collection periods  Monitoring 13.0 Release Notes Next page

On the page:

New Features and Improvements

  1. It is now possible to relay alarm events from the Server of Control to Telegram bot. Along with the alarm message, the geocoordinates of the alarm object and a frame in jpeg format can be sent
  2. You can now restrict the user's access rights to view the video stream from certain cameras on the Server of Control and Additional workstations
  3. Added a special operator mode on the Server of Control and Additional workstations. In this mode, the operator cannot accept alarms in the Reaction to alarm window and close the alarm forcibly. To enable this mode, use the DisableMonitoring registry key
  4. Windows with information messages in the Monitoring interface objects now have common style
  5. Improved the Monitoring as a service mode:
    • now during installation, the IntellectServiceUser user is no longer created which was used to launch the ITV Monitoring Vrecover service by default. Now this service is launched using the LocalSystem by default;
    • when the active account is changed, the Monitoring modules are restarted
  6. Updated the Agent of Control since the calculation of CPU load in the task manager has changed starting with Windows 8:
    • for Windows 8 and newer OS, the % Processor Utility counter is used;
    • for older operating systems, the % Processor Time counter is used
  7. Now you can select a physical monitor for all interface objects of Monitoring
  8. The following fields in interface objects now have autocomplete option:
    • search by titles field in Search in archive object;
    • filter field in the Alarms report and vehicle number field in the Vehicle LPs report in Monitoring Reports object
  9. Optimized the StreamViewer module for viewing live video:
    • now when you select the All cameras of Partition of Control menu item, only one ActiveX instance of the CamMonitor.ocx component is created with the required number of cameras:
    • the StreamViewer module can now be run with a low priority
  10. Increased the total number of cameras that one Agent of Control can process to 320
  11. Now you can specify the path to the FTP directory located on the Server of Control and intended for interaction with the Central Server of Control
  12. When you select an object in the Monitoring interface, a corresponding message is sent to the Intellect core. This allows you to implement various work scenarios using scripts, for example, to display the scheme of the selected object

Bug Fixes

  1. Fixed a bug that caused Intellect crash if there was no connection with the MonitorSSTV database when selecting the configuration forms of the Monitoring interface objects.
  2. Fixed a bug due to which zero values of archives for all cameras were sent to the Server of Control during the Agent of Control launch if Intellect was not running at that moment.
  3. Fixed a bug that prevented the Search in archive module from connecting to the database if the provider in the connection string was different from SQLOLEDB.
  4. A number of minor bugs fixed.
  5. Some fixes and improvements in the documentation.


  • No labels