Documentation for ATM Intellect 14.0. Documentation for other versions of ATM Intellect is available too.

Previous page Monitoring unadded objects  ATM Intellect 14.0 Release Notes Next page

On the page:

Data loading from database to the interface objects

The information on Control panel and Log panel is updated every time data is loaded from the database. The time of the last download from the database is shown in the CUT field.

Periods of data updating are different for Control panel and Log panel:

  1. Control panel.
    1. Data are updated from the database once a minute (by timer).
    2. At receiving of a command from Data loader to forcibly update information, which can appear after a new load to the database.
  2. Log panel. Data are updated from the database once a minute (by timer).

To get the latest database information, click the  button (Refresh data). This forces the data to load.

Data loading to the database

The date of last load of data to the database (see section Alarm list navigation) is refreshed when changes in the database appear.

If there was no change in the database for 5 minutes, the CUT field is forcibly updated and then updates once a minute. This will cause a gap from the current system time by 5 minutes. After coming of new information from any ATM-Intellect Pro, the CUT becomes equal to the current system time of the computer.

Loading data to the database is performed by the Data loader for Monitoring module.

If files with technical information are received from ATM-Intellect Pro (e.g. camera enabled), these files are loaded to the database with a period specified while configuring Data loader in the Loading period parameter (10 seconds by default). If files with information on alarms are received from ATM-Intellect Pro (e.g. vibration sensor triggered), this information is loaded to the database immediately.

After each load to the database, a message is sent to the Control panel interface component to update the information.

If, after receiving files with technical condition, ATM-Intellect Workstation determines that object state has not changed, then nothing is loaded to the database. This is why the timer is used to forcibly update interfaces.

In the Alarm date field in the interface objects, the time of alarm information load to the database after receiving it from the ATM-Intellect Pro is displayed, not the time of alarm appearing at the site.

Note.

To enable alarm registration with the time it emerged on site, create the TimeAlarmFromAgent key in the Windows registry and set it to 1 (see Registry keys reference guide for more details on the key and the Working with Windows OS registry section of Intellect software. Administrator's Guide for more details on how to operate registry keys).

Sending data from ATM-Intellect Pro to ATM-Intellect Workstation

ATM-Intellect Pro sends to ATM-Intellect Workstation packages with its technical condition with a period set while setting up the Partition of Control object at the ATM-Intellect Pro side using the Ping frequency parameter (see ATM-Intellect. Administrator's Guide, section Configuring connection between ATM-Intellect Pro and ATM-Intellect Workstation). The default ping frequency is 2 minutes (120 seconds).

Information on long-term alarms comes to the ATM-Intellect Workstation from ATM-Intellect Pro together with the information on technical condition once in the ping period.

Information about short-term alarms comes to the ATM-Intellect Workstation immediately after they have appeared at the ATM-Intellect Pro.

Data transmission scheme

The picture gives a general scheme of data transferring from the ATM-Intellect Pro to the ATM-Intellect Workstation.

Features of displaying information on short-term and long-term alarms

Information about long-term alarm can be not recorded into the Monitoring database and not displayed in its interfaces in the following cases:

  1. If a long-term alarm had started and ended within two polls of ATM-Intellect Pro (within the Ping frequency interval, see ATM-Intellect. Administrator's Guide).
  2. If a long-term alarm had started and ended when the connection between ATM-Intellect Pro and ATM-Intellect Workstation was lost.

When there is no connection with ATM-Intellect Workstation, the short-term alarms are stored in the “holding” data files on the ATM-Intellect Pro. When connection with ATM-Intellect Workstation is restored, they are transferred to the ATM-Intellect Workstation, stored in the Monitoring database and displayed in its interfaces.

ATM-Intellect Pro technical condition data collection periods

ATM-Intellect Pro technical condition data collection periods are given below:

  1. Information on disk failures (the Disk failure alarm type) and its re storing is updated in the following cases:
    1. at ATM-Intellect Pro startup and then every 15 minutes.
    2. at receiving local message SLAVE|NO_DISC (No disk for archive storage) from Intellect core.
    3. at receiving local message DISC_EXIST (Disk for archive storage found) from Intellect core.
    4. at receiving local message DISC_UNMOUNT (Disk unmounted) from Intellect core.
    5. at receiving local message DISC_MOUNT (Disk mounted) from Intellect core.
  2. Information on archive size (the Archive size too small alarm type) is updated at ATM-Intellect Pro startup and then every 15 minutes.
  3. Information on the computer normal and abnormal  restarts is displayed in the interface in 5 minutes.
  4. Information on free disk space is updated every 1 hour.

  5. ATM-Intellect Pro initiates the connection with ATM-Intellect Workstation and once in a ping period (2 minutes by default) sends a package with technical data to the ATM-Intellect Workstation. If ATM-Intellect Workstation have not been receiving any data from ATM-Intellect Pro within 6 minutes, the “No connection” error is displayed for such object.

    Note

    The waiting timeout for receiving the packets with the technical state of ATM-Intellect Pro can be adjusted. To do this:

    1. On the ATM-Intellect Pro side, in the settings panel of the Surveillance Object, add a one-character postfix to the identifier of this object (for example, if the Surveillance Object has an identifier equal to 123, then the identifier with the postfix will look like 123X, where X is the specified postfix).
    2. On the ATM-Intellect Pro side, it is recommended to adjust the ATM-Intellect Workstation polling period so that it does not exceed the waiting timeout for receiving the packets with the ATM-Intellect Pro technical condition (see Setting up a connection between ATM Intellect Pro and ATM Intellect Workstation).
    3. On the ATM-Intellect Workstation side, delete the existing Surveillance Object with a 123 identifier.
    4. On the ATM-Intellect Workstation side, create a new Surveillance Object with a 123X identifier.
    5. On the ATM-Intellect Workstation side, for the PostfixForTimeOut registry key, set the value equal to the previously specified postfix. For the TimeoutForPostfix registry key, set the timeout value in minutes (for details, see Registry keys reference guide, for more information about working with the registry, see Working with Windows OS registry).
  6. The Video.run process status (hangup) is checked at startup of Videosrv.exe module and then every 15 minutes, and besides that each time the  Videosrv.exe module reconnects with the Intellect software, i.e. if the Intellect software was shut down and started again. 
  7. Availability of running processes "Intellect.exe" and "Video.run" is checked every 10 seconds.