Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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 on the basis of each Computer object from which this event should be received. The object doesn't need any configuration

  • 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 on the basis of each Computer object from which this event should be received. The object doesn't need any configuration
  • If Axxon PSIM has unloaded
  • If the network is off, the event is received 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

Used 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.

Info
titleNote

If several Servers are added to the configuration, then after the restart of the main Server, the events with the 5 identifier will be sent to those Servers that are turned on or were turned on at the time of the restart of the main Server. At the same time, the event with the 6 identifier won’t be sent to those Servers that were turned off at the time of the restart of the main Server.