Page History

x32: (x32)\POS
x64: (x64)\POS

Capture

0, 1

1

1.0.0 and later

Defines whether to store log-files or not. 
Log-files are stored in the <Axxon PSIM Folder>\Modules\PosCapture folder.

x32: (x32)\POS
x64: (x64)\POS

Dos2Win

0, 1

1

1.0.0 and later

Detects encoding:
1 – read XML encoding in DOS codepage;
0 – read  XML as it is

x32: (x32)\POS
x64: (x64)\POS

GlobalTextDelay

NA

0

1.0.0 and later

Sets the shift of Text data from video to TextSearch.

x32: (x32)\POS
x64: (x64)\POS

Nohotkey

0, 1

1

1.0.0 and later

Allows disabling hot keys used for POSVIEWER and TITLEVIEWER. If Nohotkey = 1, then when clicking
Ctrl+Shift+E – the frame export folder is opened;
Ctrl+Shift+T – the Tools folder is opened.

The key enables the UTF-8 encoding to ensure the correct display of captions in cases when the incoming to the POS terminal packages have the UTF-8 encoding.

x32: (x32)\POS
x64: (x64)\POS

PosLogMaxsize

>0

10

1.0.0 and later

The key sets maximum size (in MBs) of the POS terminal’s log.

Note. POS terminal logging is enabled using the Capture key – see above.

The key enables the received local timestamp conversion to UTC when creating a record in the corresponding POS PSIM database.

0 – received local timestamp will be recorded to the corresponding database without any changes.

1 – received local timestamp will be converted to UTC when creating a record in the corresponding database.

In case the D-store POS-terminals are used, the key enables saving the info about the last cashier whose data was received by the POS-terminal. Until there is no data, the following default values are used: cashier_name = "Jane B."; cashier_number = "1147911";

0 – the info about the last cashier whose data was received by the POS-terminal, is not saved.

1 – the info about the last cashier whose data was received by the POS-terminal, is saved.

In case the D-store POS-terminals are used, the key enables initiating the receipt creation by any data input. In addition to that, the text line specified in the NewReceipt.Word key (see below) is added to the receipt text.

0 – the receipt creation is initiated by the word specified to trigger the receipt creation.

1 – the receipt creation is initiated by any data input, and the text line specified in the NewReceipt.Word key (see below) is added to the receipt text.

Note. This key works only if the UseLastCashierInfo key (see above) is enabled.

NewReceipt.Word

The key activates displaying in the Monitor the time (UTC) when each caption appeared.

0 – the captions timestamps (UTC) are not displayed in the Monitor.

1 – the captions timestamps (UTC) are displayed in the Monitor.

The key saves the beginning [PROLOG], middle [BODY], and end [EPILOG] of a receipt in the buffer and displays captions only after a receipt start event is received:

0—the beginning, middle, and end of a receipt aren't saved in the buffer; captions are displayed immediately

1—the beginning, middle, and end of a receipt are saved in the buffer; captions are displayed only after a receipt start event is received

By default, the key isn't created, and its value is considered to be 0

x32: (x32)\DetectorExt

x64: (x64)\DetectorExt

The key specifies the number of attempts to restart the detection tool in case of an internal error

x32: (x32)\DetectorExt

x64: (x64)\DetectorExt

The key excludes repeated triggering of the Pose detection tool when there is a recumbent person in the frame:

0—repeated triggering of the detection tool isn't excluded

1—repeated triggering of the detection tool is excluded

The registry key is created manually.

If Recumbent.SkipSitPeople=1, and the values of other keys (Recumbent.SkipSitPeopleTimeOffset and Recumbent.SkipSitPeopleAreaOffset) aren't specified or only one is specified, then the default values are used for the missing keys. To specify the values different from default values, you must manually specify the Recumbent.SkipSitPeopleTimeOffset and Recumbent.SkipSitPeopleAreaOffset registry keys

x32: (x32)\DetectorExt

x64: (x64)\DetectorExt

You must manually create the registry key with the value Recumbent.SkipSitPeople=1, otherwise the Recumbent.SkipSitPeopleTimeOffset registry key doesn't work. 

The key specifies the time period in seconds during which repeated triggering of the Pose detection tool when there is a recumbent person in the frame is excluded.

If Recumbent.SkipSitPeople=1, and the values of other keys (Recumbent.SkipSitPeopleTimeOffset and Recumbent.SkipSitPeopleAreaOffset) aren't specified or only one is specified, then the default values are used for the missing keys. To specify other value, you must create the Recumbent.SkipSitPeopleTimeOffset registry key manually

x32: (x32)\DetectorExt

x64: (x64)\DetectorExt

You must manually create the registry key with the value Recumbent.SkipSitPeople=1, otherwise the Recumbent.SkipSitPeopleAreaOffset registry key doesn't work. 

The key specifies the percentage of increase in the original size of the alarm border, in which repeated triggering of the Pose detection tool when there is a recumbent person in the frame is excluded.

If Recumbent.SkipSitPeople=1, and the values of other keys (Recumbent.SkipSitPeopleTimeOffset and Recumbent.SkipSitPeopleAreaOffset) aren't specified or only one is specified, then the default values are used for the missing keys. To specify other value, you must create the Recumbent.SkipSitPeopleAreaOffset registry key manually

x32: (x32)\DetectorExt
x64: (x64)\DetectorExt

The key doesn't affect the operation of detectors. It serves to collect the information about the configuration of detectors, which simplifies debugging and testing.

 0—the debug logging mode isn't enabled in the VI SDK, the VI detector configuration files aren't saved in the Modules64 folder.

1—the debug logging mode is enabled in the VI SDK, the VI detector configuration files are saved as two main and two additional files in the Modules64 folder when the filtration plugin is enabled.

By default, the key isn't created, and its value is equal to 0

x32: (x32)\DetectorExt\BARCODE_DETECTOR

x64: (x64)\DetectorExt\BARCODE_DETECTOR

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1—detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Barcode Detection: External Detector - BARCODE_DETECTOR.1

x32: (x32)\DetectorExt\BASE_POSE_DETECTOR

x64: (x64)\DetectorExt\BASE_POSE_DETECTOR

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1—detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Pose Detection: External Detector - BASE_POSE_DETECTOR.1

x32: (x32)\DetectorExt\CONVEYOR_BELT_DETECTOR

x64: (x64)\DetectorExt\CONVEYOR_BELT_DETECTOR

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1—detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Conveyor Belt Detection: External Detector - CONVEYOR_BELT_DETECTOR.1

x32: (x32)\DetectorExt\CROWD_COUNTER

x64: (x64)\DetectorExt\CROWD_COUNTER

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1—detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Detection of moving against crowd flow: External Detector - CROWD_COUNTER.1

x32: (x32)\DetectorExt\CROWD_ESTIMATION

x64: (x64)\DetectorExt\CROWD_ESTIMATION

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1—detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Crowd detection (TVNVA): External Detector -CROWD_ESTIMATION.1

x32: (x32)\DetectorExt\EQUIPMENT_DETECTOR

x64: (x64)\DetectorExt\EQUIPMENT_DETECTOR

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1—detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Equipment detection (PPE): External Detector - EQUIPMENT_DETECTOR.1

x32: (x32)\DetectorExt\FIRE_DETECTOR

x64: (x64)\DetectorExt\FIRE_DETECTOR

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1—detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Fire detection: External Detector - FIRE_DETECTOR.1

x32: (x32)\DetectorExt\FLUID_DETECTOR

x64: (x64)\DetectorExt\FLUID_DETECTOR

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1—detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Fluid level detection: External Detector - FLUID_DETECTOR.1

x32: (x32)\DetectorExt\GLOW_DETECTOR

x64: (x64)\DetectorExt\GLOW_DETECTOR

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1—detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Detection of light indication control: External Detector - GLOW_DETECTOR.1

x32: (x32)\DetectorExt\HEAT_ZONE_DETECTOR

x64: (x64)\DetectorExt\HEAT_ZONE_DETECTOR

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1—detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Heat map detection: External Detector - HEAT_ZONE_DETECTOR.1

x32: (x32)\DetectorExt\HEAT_ZONE_DETECTOR

x64: (x64)\DetectorExt\HEAT_ZONE_DETECTOR

Sets the data collection frequency (sec) for heat map detection tool

x32: (x32)\DetectorExt\HEAT_ZONE_DETECTOR

x64: (x64)\DetectorExt\HEAT_ZONE_DETECTOR

Sets the data update frequency (sec) from heat map detection tool in the Debug window in seconds

x32: (x32)\DetectorExt\NEURO_COUNTER

x64: (x64)\DetectorExt\NEURO_COUNTER

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1—detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Neurocounter: External Detector - NEURO_COUNTER.1

x32: (x32)\DetectorExt\NEURO_TRACKER

x64: (x64)\DetectorExt\NEURO_TRACKER

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1—detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Neurotracker: External Detector - NEURO_TRACKER.1

x32: (x32)\DetectorExt\NEURO_TRACKER\NEURO TRACKER_id

x64: (x64)\DetectorExt\NEURO_TRACKER\NEURO TRACKER_id

Sets the custom size of the scanning windows. 

1. In the registry, create a new section NEURO_TRACKER_id, where id is the id of the neurotracker, which window sizes you want to change.
2. In this section, create four registry keys:
   1. windowH—scanning window height;
   2. windowW—scanning window width;
   3. windowStepH—scanning window step height;
   4. windowStepW—scanning window step width.
3. Specify the required values for all four keys. Otherwise, the default settings will be used.

Example of custom settings for a 1920×1080 frame divided into four equal scanning windows:
windowH=540
windowStepH=540
windowW=960
windowStepW=960

x32: (x32)\DetectorExt\OCCUPANCY_COUNTER

x64: (x64)\DetectorExt\OCCUPANCY_COUNTER

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1—detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Queue length detection: External Detector - OCCUPANCY_COUNTER.1

x32: (x32)\DetectorExt\NEURO_COUNTER\NEURO COUNTER_id

x64: (x64)\DetectorExt\NEURO_COUNTER\NEURO COUNTER_id

Sets the custom size of the scanning windows. 

1. In the registry, create a new section NEURO COUNTER_id, where id is the id of the neurocounter, which window sizes you want to change.
2. In this section, create four registry keys:
   1. windowH—scanning window height;
   2. windowW—scanning window width;
   3. windowStepH—scanning window step height;
   4. windowStepW—scanning window step width.
3. Specify the required values for all four keys. Otherwise, the default settings will be used.

Example of custom settings for a 1920×1080 frame divided into four equal scanning windows:
windowH=540
windowStepH=540
windowW=960
windowStepW=960

x32: (x32)\DetectorExt\PEOPLE_COUNTER

x64: (x64)\DetectorExt\PEOPLE_COUNTER

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1—detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the People counter detection: External Detector - PEOPLE_COUNTER.1

x32: (x32)\DetectorExt\SMOKE_DETECTOR

x64: (x64)\DetectorExt\SMOKE_DETECTOR

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1—detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Smoke detection: External Detector - SMOKE_DETECTOR.1

x32: (x32)\DetectorExt\STOPPED_CAR_DETECTOR

x64: (x64)\DetectorExt\STOPPED_CAR_DETECTOR

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1—detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Stopped vehicle detection: External Detector - STOPPED_CAR_DETECTOR.1

x32: (x32)\DetectorExt\SWEETHEARTING_DETECTOR

x64: (x64)\DetectorExt\SWEETHEARTING_DETECTOR

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1—detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Sweethearting at checkout detection: External Detector - SWEETHEARTING_DETECTOR.1

x32: (x32)\DetectorExt\TRAFFIC_LIGHTS

x64: (x64)\DetectorExt\TRAFFIC_LIGHTS

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1—detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Traffic lights detection: External Detector - TRAFFIC_LIGHTS.1

x32: (x32)\DetectorExt\TRAIN_DETECTOR

x64: (x64)\DetectorExt\TRAIN_DETECTOR

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1—detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Train detection: External Detector - TRAIN_DETECTOR.1

x32: (x32)\DetectorExt\VIDEO_INTELLECT_INTERNAL_DETECTOR

x64: (x64)\DetectorExt\VIDEO_INTELLECT_INTERNAL_DETECTOR

Activates the start of the VideoIntellect detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1—detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. 

Examples of separate processes for the VideoIntellect detection tools:

VideoIntellect embedded detector: External Detector - VIDEO_INTELLECT_INTERNAL_DETECTOR.1
VideoIntellect detection of movement in prohibited area: External Detector - VI_FORBIDDEN_DETECTOR.1
VideoIntellect detection of prohibited direction: External Detector - VI_DIRECTION_DETECTOR.1
VideoIntellect detection of crowd: External Detector - VI_CROWD_DETECTOR.1
VideoIntellect abandoned objects detection: External Detector - VI_ABANDONED_DETECTOR.1
VideoIntellect detection of camera state: External Detector - VI_FAULTER_DETECTOR.1
VideoIntellect abandoned objects street detection: External Detector - VI_ABANDONED_STREET_DETECTOR.1

Hides the VideoIntellect detector objects from the Axxon PSIM objects tree.

0—the VideoIntellect detector objects are hidden

><0—VideoIntellect detector objects are displayed

The key sets the time in seconds which defines the time the object stays in the zone, after which the NeuroTracker VMDA detection tools with the Staying in the area for more than 10 sec detector type, created under the Neurotracker object, are triggered. If this key is not specified, then it is considered equal to the LongInZoneTimeout key value (see Axxon PSIM base version)

x32: (x32-Monitoring)

x64: (x64-Monitoring)

LPRDBsearchresultUnicodeBase64

0, 1

1

1.0 and later 

The key sets how to process message in param0<> for the SEARCH_RESULT event of the LPRDB ("External database") object – as ANSI line or Unicode line additionally encoded in base64.

0 – ANSI

1 – UnicodeBase64

x32: (x32-Monitoring)

x64: (x64-Monitoring)

PeakWorkingSetSizeQuota

>=0

100

1.0 and later

The maximum memory size in megabytes used by the process videosrv.exe on Agent Of Control. If the parameter is set to 0, then the check for the used memory is not performed.

Once a day, the Agent Of Control checks the size of the memory it uses. The check is performed at the time specified by the TimeOfCheckWorkingSetSize key (see below).

After exceeding the specified value, the videosrv.exe module is rebooted.

x32: (x32-Monitoring)

x64: (x64-Monitoring)

TimeOfCheckWorkingSetSize

>=0

3

1.0 and later

Time to check memory usage in hours. Default value is 3 (3:00 AM). See also the PeakWorkingSetSizeQuota key description above.

x32: (x32-Monitoring)

x64: (x64-Monitoring)

StoreVideoFiles

>0

3

1.0 and later

Time period for storage of not completely downloaded files on Agent Of Control. After the storage period is exceeded, the not completely downloaded files are deleted.

x32: (x32-Monitoring)

x64: (x64-Monitoring)

run_core

0.1

1

1.0 and later

The key sets the Agent Of Control actions in case if the Axxon PSIM software is shut down.

0 – do not start the Axxon PSIM software

1 – start the Axxon PSIM software

x32: (x32-Monitoring)

x64: (x64-Monitoring)

socket_connect_tout

>=0

0

1.0 and later

The key defines TCP/IP connection mode with Server Of Control.

0 – blocking mode. Agent Of Control connects to Server Of Control without specifying connection timeout.

>0 – non-blocking mode.  Agent Of Control connects to  Server Of Control with a connection timeout set by the socket_connect_tout > 0 parameter in seconds.

x32: (x32-Monitoring)

x64: (x64-Monitoring)

write_buffer_enable

0.1

1

1.0 and later

Data buffering while recording on disc when receiving video data on Server Of Control.  Agent Of Control transfers video data to Server Of Control in packages of 800 to 4096 bytes (4096 by default). When buffering is enabled, a 264 Kb block of memory is allocated to the Server Of Control for receiving video data, and data is saved to the disk when this memory block is full, not every time a packet is received from Agent Of Control.

0 – buffering is enabled.

1 – buffering is disabled.

x32: (x32-Monitoring)

x64: (x64-Monitoring)

stop_data_by_trx

0.1

1

1.0 and later

The key determines the actions of Agent Of Control in case if, during the transfer of video data to ATM PSIM ARM, a financial transaction has begun on the ATM PSIM.

0 – video data transfer is not stopped.

1 – video data transfer is suspended until financial transaction if completed.

x32: (x32-Monitoring)

x64: (x64-Monitoring)

The key specifies the port on the Server Of Control/Central Server Of Control used for connecting the clients.

x32: (x32-Monitoring)

x64: (x64-Monitoring)

financial_trx_tout

>0

60

1.0 and later

Timeout for waiting for the financial transaction to complete in minutes. If after the start of the financial transaction during the time-out, there is no message from the ATM about its end, it will be considered to be completed.

x32: HKLM\SOFTWARE\BitSoft\VHOST\ULPR

x64: HKLM\SOFTWARE\Wow6432Node\BitSoft\VHOST\ULPR

The key enables special operation mode of the Monitoring PSIM software joint with Auto PSIM.

1 – the special operation mode of the Monitoring software joint with Auto PSIM is enabled.

Any other value – the special operation mode is disabled.

x32: HKLM\SOFTWARE\BitSoft\VHOST\ULPR

x64: HKLM\SOFTWARE\Wow6432Node\BitSoft\VHOST\ULPR

This parameter corresponds to the point of recognition. PlaceOfRecognitionN, where N is the ID of the LPR channel object.

1 – entrance.

2 – exit.

Note 1. The key is in use in special operation mode of the Monitoring PSIM software joint with Auto PSIM.

Note 2. The key is created at Agent Of Control

x32: HKLM\SOFTWARE\BitSoft\VHOST\ULPR

x64: HKLM\SOFTWARE\Wow6432Node\BitSoft\VHOST\ULPR

This parameter corresponds to the ID of a camera added to the recognition module. CamOfRecognitionN, where N is the ID of the LPR channel object. 

The value of this parameter corresponds to the Camera object ID specified in the LPR channel object settings.

Note 1. The key is in use in special operation mode of the Monitoring PSIM software joint with Auto PSIM.

Note 2. The key is created at Agent Of Control

x32: HKLM\SOFTWARE\BitSoft\VHOST\ULPR

x64: HKLM\SOFTWARE\Wow6432Node\BitSoft\VHOST\ULPR

The key enables the LP found in the database alarm both for Entrance and Exit recognition points.

0 – enables the LP found in the database alarm both for Entrance and Exit recognition points.

Any other value – the LP found in the database alarm is generated for Entrance recognition point only.

Note 1. The key is in use in special operation mode of the Monitoring software joint with Auto PSIM.

Note 2. The key is created at Server Of Control

x32: (x32-Monitoring)

x64: (x64-onitoring)

The key enables registration of the alarm with the time it occurred on the site.

0 – In the Alarm date field in the interface objects, the time of loading the alarm into the database after it is received from the Agent Of Control is shown, not the time of occurrence of the alarm on site.

1 - In the Alarm date field in the interface objects, the time of alarm occurrence on site is shown.

Note. The key is set on the Server Of Control.

x32: (x32-Monitoring)

x64: (x64-Monitoring)

FileQueryEnable   

The key enables automated video clip loading.

0 – automated video clip loading is disabled.

1 – automated video clip loading is enabled.

Note. The key is created at Server Of Control and/or Additional Workstation

x32: (x32-Monitoring)

x64: (x64-Monitoring)

FileQueryPath

The key sets folder to share data with third party systems which is necessary for automated video clip loading.

Note. The key is created at Server Of Control and/or Additional Workstation

x32: (x32-Monitoring)

x64: (x64-Monitoring)

The key changes the Log Panel interface color theme.

0 - dark interface theme.

1 - light interface theme.

x32: (x32-Monitoring)

x64: (x64-Monitoring)

The key specifies the path to the catalog of frames and video clips which were exported from the Monitoring PSIM interface during the live and archive video playback from a certain camera.

See Playing back live video and archive from a specific camera.

x32: (x32-Monitoring)

x64: (x64-Monitoring)

The key removes the restriction on adding the same cameras for tracking in different Partitions Of Control.

0 - the restriction is enabled.

1 - the restriction is removed.

x32: (x32-Monitoring)

x64: (x64-Monitoring)

The key activates the special  mode of Monitoring PSIM operation together with ACFA PSIM, as well as the ability to customize the long alarm description.

0 - Special operation mode is off.

1 - Special operation mode is on.

x32: (x32-Monitoring)

x64: (x64-Monitoring)

The key changes the description of the long alarm Object disarmed in the Monitoring and Monitoring reports interface objects.

x32: HKLM\SOFTWARE\BitSoft\MonitorSSTV\Loader

x64: HKLM\SOFTWARE\Wow6432Node\BitSoft\MonitorSSTV\Loader

The key accelerates the speed of data loading from files to the MonitorSSTV database by activating the group operator of data loading if the database is installed locally.

0 - do not use the BULK INSERT operator (if the SQL Server is remote)
1 - use the BULK INSERT operator (if the SQL Server is local)

x32: (x32-Monitoring)

x64: (x64-Monitoring)

x32: (x32-Monitoring)

x64: (x64-Monitoring)

TimeoutForPostfix

x32: (x32-Monitoring)

x64: (x64-Monitoring)

The key sets the operation mode of the Central Server Of Control software via FTP.

0 - Active mode.

1- Passive mode.

x32: (x32-Monitoring)

x64: (x64-Monitoring)

The key sets the statistics polling period in minutes for the Servers Of Control.

x32: (x32-Monitoring)

x64: (x64-Monitoring)

The key sets the log archiving period in hours of the Communication module (CentralNetServer.log)

x32: (x32-Monitoring)

x64: (x64-Monitoring)

The key sets the maximum size of the communication module log file at which it begins to archive ignoring the LogArchPeriod parameter.

x32: (x32-Monitoring)

x64: (x64-Monitoring)

The key sets the log files archive retention period in months (CentralNetServer.log).

x32: (x32-Monitoring)

x64: (x64-Monitoring)

The key sets the data retention period of closed errors and alarms in the ServerSSTV DB.

x32: (x32-Monitoring)

x64: (x64-Monitoring)

The key sets the time in minutes, after which, if the data in the MonitorSSTV database is outdated, the corresponding indication on the Server Of Control/CSC will appear.

x32: (x32-Monitoring)

x64: (x64-Monitoring)

The key disables the ability to accept alarms and force error closing.

0 - the ability to confirm alarms and force error closing is enabled.

1 - the ability to confirm alarms and force error closing is disabled.

If the key is set to 1, then:

• the area for comments and buttons for confirming the alarm are not displayed in the Reaction to alarm window; when you set the Confirm checkbox, nothing happens;
• when you click on the Force error closing button on the toolbar, the window with confirmation of force error closing does not open.

x32: (x32-Monitoring)

x64: (x64-Monitoring)

The key sets low priority of the StreamViewer process when it starts.

0 − The StreamViewer process starts with normal (medium) priority.

1 − The StreamViewer process starts with low priority.

x32: (x32-Monitoring)

x64: (x64-Monitoring)

x32: (x32-Monitoring)

x64: (x64-Monitoring)

If the continuous recording mode is enabled, the key sets the time interval of recording delay by camera in msec after it stops.

If the camera is armed, the key sets the time interval of camera arming delay in msec after it stops

x32: (x32-Monitoring)

x64: (x64-Monitoring)

If the parameter isn’t created or equals 0, the video data isn’t stored in the Monitoring database (MonitorSSTV or ServerSSTV).

If the parameter > 0, its value equals the number of days the video data should be stored in the Monitoring database. When this period is exceeded, the video data is deleted from the database

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

The key hides the camera's menu.

0 - The menu is displayed.

1 - The menu is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

The key hides the Arm menu option.

0 - The Arm menu option is displayed.

1 - The Arm menu option is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

The key hides the Start recording menu option.

0 - The Start recording menu option is displayed.

1 - The Start recording menu option is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

The key hides the Camera menu option.

0 - The Camera menu option is displayed.

1 - The Camera menu option is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

The key hides the Show titles menu option.

0 - The Show titles menu option is displayed.

1 - The Show titles menu option is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

The key hides the Processing menu option.

0 - The Processing menu option is displayed.

1 - The Processing menu option is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

The key hides the Export menu option.

0 - The Export menu option is displayed.

1 - The Export menu option is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

The key hides the Deinterlacing menu option.

0 - The Deinterlacing menu option is displayed.

1 - The Deinterlacing menu option is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

The key hides the Zoom-in menu option.

0 - The Zoom-in menu option is displayed.

1 - The Zoom-in menu option is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

The key hides the Contrast menu option.

0 - The Contrast menu option is displayed.

1 - The Contrast menu option is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

The key hides the Detector mask menu option.

0 - The Detector mask menu option is displayed.

1 - The Detector mask menu option is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

The key hides the Sharpen menu option.

0 - The Sharpen menu option is displayed.

1 - The Sharpen menu option is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

The key hides the Archive button.

0 - The Archive button is displayed.

1 - The Archive button is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

The key hides the time.

0 - The time is displayed.

1 - The time is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

The key hides the camera name.

0 - The camera name is displayed.

1 - The camera name is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

The key hides the Menu button.

0 - The Menu button is displayed.

1 - The Menu button is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

The key hides the toolbar that also contains the FPS, frame size, and stream resolution:

0—the toolbar is displayed

1—the toolbar is hidden

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

The key disables the control over the CamMonitor component using the hotkeys available for Video Monitor (see Video surveillance monitor).

0 - The control over the CamMonitor component using the hotkeys is enabled.

1 - The control over the CamMonitor component using the hotkeys is disabled.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

The key enables the Telemetry control using the CamMonitor component (see Telemetry control).  

0 - The Telemetry control using the CamMonitor component is disabled

1 - The Telemetry control using the CamMonitor component is enabled.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

The key activates the Delete menu item which is used to remove the recordings from the archive (see Deleting video recordings Delete videos from the archive).

0 - The Delete item is hidden.

1 - The Delete item is displayed.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

The key activates the Protect menu item which is used to protect the archive recordings from rewriting (see Protection of separate record and disable of protection).

0 - The Protect item is hidden.

1 - The Protect item is displayed.

x32: (x32-Monitoring)

x64: (x64-Monitoring)

RequestFullStatisticOnStartup 

By default, the Central Server Of Control requests a complete package of statistics from all Servers Of Control only once, when it first connects to the Servers Of Control.

The key activates the request on the Central Server Of Control for a complete statistics package from all Servers Of Control every time the CentralNetServer.exe communication module is launched.

0 - disabled.

1 - a complete statistics package will be requested from all Servers Of Control each time the CentralNetServer.exe communication module is launched.

Attention! Requesting a complete statistics package is a resource-intensive operation. It is only necessary to activate this key if absolutely necessary.

x32: (x32-Monitoring)

x64: (x64-Monitoring)

RequestFullStatistic[N]

Note. [N] is the internal identifier of the Server Of Control object in Axxon PSIM

By default, the Central Server Of Control requests a complete package of statistics from all Servers Of Control only once, when it first connects to the Servers Of Control.

The key activates the request for a complete statistics package from a specific Server Of Control once. The request will be executed when the CentralNetServer.exe communication module is launched, and the value of this key will automatically change to 0.

0 - disabled.

1 - a complete statistics package from a specific Server Of Control will be requested once when the CentralNetServer.exe communication module is launched.

Attention! Requesting a complete statistics package is a resource-intensive operation. It is only necessary to activate this key if absolutely necessary.

x32: (x32-Monitoring)

x64: (x64-Monitoring)

Sets the path to the FTP directory on the Server Of Control for working with the Central Server Of Control.

x32: (x32-Monitoring)

x64: (x64-Monitoring)

DISK:\Export\

, where DISK is the drive on which the operating system is installed