Documentation for Axxon PSIM 2.0. Documentation for other versions of PSIM is available too.

Previous page Requirements for base PCs  Operating system requirements Next page


Requirements for PCs depend on Axxon PSIM software installation type. The following installation types are available:

  1. Servers are designed for digitization, processing, recording, transmission and displaying the incoming video signals from the cameras of the video surveillance system.
  2. Remote Administrator Workstations are designed for remote monitoring of video signals, for creating gateways and archives of video sequences, for logging the events registered by Axxon PSIM software and use as a web server for the transmission of video signals over HTTP (this protocol is used to transmit signals over the Internet and display them with standard Web-browsers). Configuration requirements for the Remote Administrator Workstation depend on the functions it is designed to perform.
  3. Remote Clients are designed to playback incoming video and audio signals from video surveillance system servers and to control cameras, microphones, PTZ units, etc.

Minimum requirements for computer configuration are specified in the table.

Component

Server and RAW

Client

QTY per computer

Additional information

Tower

Any

1

—

Motherboard

Any type that supports required processor and has the necessary set of pins and slots

1

Pay attention to the number of free PCI (-e) slots and socket type of the processor

Processor

Select the processor in accordance with the computer configuration using the on-line calculator: https://sale.axxonsoft.com/calc/calculator.jsf. Documentation on the calculator is available here: Documentation

1

If the total number of processor cores is more than 8, it is recommended to use only 64-bit operating systems: Windows 7 x64 Ultimate, Windows 7 x64 Professional, Windows Server 2008 R2 x64 or higher.

Processor supporting AVX instructions is required for the VA capture and recognition (the most recent Face PSIM documentation is available in AxxonSoft documentation repository)

RAM

At least 2 GB

—

Memory operating speed increase by using memory with greater frequency or using memory in the dual stream (or more) mode results in less CPU load and, consequently, greater Axxon PSIM performance

Hard drive 1

Space required for installation of the OS + 10 GB for installation of Axxon PSIM software + 20 GB for installation of MS SQL Server

Space required for installation of the OS + 10 GB for installation of Axxon PSIM software

1 (+1)

Mirroring can be used to improve the fault-tolerance

Hard drive 2

To maintain video/audio archive compatible with the requirements for the archive depth

—

—

External disk systems can be connected via SAS, SCSI, Fiber Channel interfaces.

Will be installed in cases where video/audio archives are required

DVD-RW

Any type of DVD-RW

1

To write the archive to an external carrier, for fallback recovery (optional)

Video card (GPU)

Discrete: NVIDIA GeForce GT520 1 GB RAM or with higher performance.

On-board: Intel HD Graphics 530 or with higher performance

1

Optional if it is not required to display video on the monitor.

Axxon PSIM can operate without a video card if the processor has a built-in video core

Audio cardStandard audio cards, MidiMan Delta, Comart Hera and Olkha 9P1Optional if audio surveillance is not required

Power supply unit

Any matching the PC tower. Capacity depends on the hardware configuration

1

Two fans are recommended: a suction fan and an induced draft fan. A redundant fan can also be installed

FAN & Temp Control

Any temperature control module

1

Optional

OS

OS Windows supported versions (see Operating system requirements)

1

Internet access is recommended to be switched off

Architecturex86, x64——

Attention!

If Axxon PSIM is installed on a computer with two processors, it is recommended to disable the Hyper-threading. If it is enabled, the operating system does not allow Axxon PSIM to run on two processors simultaneously.

Note

The system clock on the server must be synchronized with the client’s system clock, or run a couple of seconds ahead. Otherwise, problems during re-connecting (for example, on connection loss) may occur.
  • No labels