Documentation for Axxon PSIM 1.0.0-1.0.1.

Previous page Next page


You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Axxon PSIM allows sending events from the system objects to the VideoGuard server (see http://videoguard.ae/). In this case, Axxon PSIM acts as a client of the VideoGuard system.

The integration with the VideoGuard system is configured as follows:

  1. Create the VideoGuard integration client object on the basis of the Computer object on the Hardware tab of the System Settings dialog box (1). If data from several Axxon PSIM servers in a distributed system are to be sent to VideoGuard, then create and configure separate VideoGuard integration client objects under each server.

    Note

    A single VideoGuard integration client object is enough to send messages about the loss of connection with any server. See also step 7.


  2. Set the Server name in full format checkbox (2) if it is necessary to display the full server name. By default, short server name is displayed.
  3. In the Server address field, enter the connection address to the VideoGuard server (3).
  4. In the Device ID on the server field, enter the identifier which is assigned to Axxon PSIM on the VideoGuard server (4). There should be no more than 6 digits in this field.
  5. From the IP-interface drop-down list, select the network adapter which is used to connect this computer to the VideoGuard server (5).
  6. From the IP address drop-down list (6) select the IP address for connection.
  7. In the Ping sending period field, specify the Heart Beat messages sending frequency in seconds (7). By default, the Heart Beat message is sent right after the Axxon PSIM starts and then every 5 minutes (300 seconds).
  8. Configure the correspondence between the VideoGuard and Axxon PSIM events. By default, the correspondence table contains the mandatory events, and their correspondence with the Axxon PSIM objects events is configured. If necessary, you can change this correspondence, add or remove additional events:
    1. From the Server event ID drop-down list, select the event identifier on the VideoGuard server (8). See the supported values in the table below.
    2. From the Computer drop-down list, select the name of the Computer object. The selected events of the objects, which are based on this Computer object, will be sent to the VideoGuard (9). If the value is not specified, the events are sent from the specified objects, regardless of which Computer object they are based on; in this case such events may not be processed correctly in VideoGuard.
    3. From the Type drop-down list, select the Axxon PSIM object type, the events from which should be sent to the VideoGuard server (10).
    4. From the Number drop-down list, select the Axxon PSIM object identifier, the events from which should be sent to the VideoGuard server (11). If the identifier is not specified, then events are sent from all objects of the selected type.
    5. After you select the object type and identifier, the Name field will be automatically filled with the name of the selected Axxon PSIM object (12).
    6. From the Event drop-down list, select the event which is coming from the Axxon PSIM object of the selected type and which corresponds to the VideoGuard server event with the specified identifier (13).
    7. To add new event, click Add filter (14), then perform steps a-f to configure it.
    8. To remove an event, select corresponding row in the table and click Remove filter (15).
  9. If there is one VideoGuard integration client object and several Computer objects, then connection loss events from all computers in the distributed system are transmitted to VideoGuard software by default. If you do not need to transmit connection loss events from some computers, go to the Computers tab (1) and uncheck the boxes (2) opposite the corresponding Computer objects (3).

  10. Click Apply.

The integration with the VideoGuard system is configured.

Restart Axxon PSIM after connecting to the VideoGuard server to synchronize the time with the VideoGuard server. After Axxon PSIM restart, the time zone in Windows is synchronized with the specified VideoGuard server. Subsequently, the Axxon PSIM server will synchronize with the NTP server of the VideoGuard system (by calling the GetNTPServerInfo method). During synchronization, the VideoGuard system server will return the time synchronization period (120 seconds by default), and within 24 hours after synchronization with the NTP server, time synchronization will be performed at the specified interval.

The event identifiers supported on the server:

IDDescriptionCorresponding Axxon PSIM event
1No video signalCamera: Connection lost
2Video source connection

Camera: Connection

3Disk overflow-
4Error writing to diskComputer: Disc unmounted
5Client connection

VideoGuard integration client: Video module started

Note. The event is generated in the following cases:

  • If the video module has loaded. Create the Video.run Watcher object under each Computer from which this event should be received. The object does not have any settings.

  • If Axxon PSIM has loaded
  • If the network is on
6Client disconnection

VideoGuard integration client: Video module unloaded

Note. The event is generated in the following cases:

  • If the video module is unloaded. Create the Video.run Watcher object under each Computer from which this event should be received. The object does not have any settings (see above).
  • If Axxon PSIM has unloaded
  • If the network is off, the event comes after the network is turned on
7Motion detection triggerCamera: Alarm
8Case opening (Shelter Alarm)-
9Start of recording to the archiveCamera: Harddisk rec
10End of recording to the archiveCamera: Record on disk stopped
11Change of recording to the archive schedule-
100Additional event

Designed to send additional events to the VideoGuard server. In this case, the event source identifier is added to the event identifier.

Example:

The event with the "101" identifier will be sent to the VideoGuard server.

  • No labels