Versions Compared

Key

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

...

ACFA Intellect

Registry section

String parameter

Available values

Default

Product version

Parameter in effect

Rovalant A6-A16 ISS 






x32: (x32)\Rovalant_A6_A16
x64: (x64)\Rovalant_A6_A16

access_point_count

-

10

4.7.6 and later

Internal module setting. You’d better not modify the key.

x32: (x32)\Rovalant_A6_A16
x64: (x64)\Rovalant_A6_A16

rele_count

-

20

4.7.6 and later

Internal module setting. You’d better not modify the key. 

Apollo (AAN 100, AAN 32, AIM-4, AIM-4SL)






x32: (x32)\Apollo
x64: (x64)\Apollo

DisableLogOffLineEvents

0, 1

0

4.7.4 and later

Disables event logging when the controller is in the offline mode.

x32: (x32)\Apollo
x64: (x64)\Apollo

EnableHardwareReset

0, 1

1

4.7.4 and later

Enables hardware reset before forwarding configuration.

x32: (x32)\Apollo
x64: (x64)\Apollo

nCardType

0, 1

0

4.7.4 and later

Defines the card type. When the value is 1, support for Weigand32 is enabled.

x32: (x32)\Apollo
x64: (x64)\Apollo

nPINType

0, 1, 2

1

4.7.4 and later

Defines whether PIN is in use:
0 – not is use;
1- PIN 4 figures;
2 - PIN 6 figures.

x32: (x32)\Apollo
x64: (x64)\Apollo

SetLinkParametersAfterReset

0, 1

1

4.7.4 and later

Sets link parameters after reset.

ABC (Access Net) 






x32: (x32)\ABC
x64: (x64)\ABC

UseDynamic

0, 1

0

4.7.4 and later

Defines whether the Dynamic checkbox is available in the controller settings. In this case configuration forwarding in a separate stream can cause module crash.

x32: (x32)\ABC
x64: (x64)\ABC

UseMultiThreaded

0, 1

0

4.7.4 and later

Sets the use of the multithreading mode.

Perco Card Reader






x32: (x32)\Perco CR
x64: (x64)\Perco CR

ReadTotalTimeoutConstant

> = 0

-

4.7.4 and later

Sets timeout of reader query. If connection is lost sometimes, then the value is to be increased.

PERCO-SYSTEM-12000L ACS 






x32: (x32)\Perco
x64: (x64)\Perco

AdditionNumberOfCard


0

4.7.4 and later

If the number of card is read with displacement (error of COM Server Perco), then the value of this parameter defines the displacement.

x32: (x32)\Perco
x64: (x64)\Perco

AutoconfigType

0, 1,2,3

0

4.7.5 and later

Sets auto configuration mode:
0 – feature is not available;
1 – controllers that do not exist are deleted;
2  - controllers that do not exist are deleted and new found controllers are stored at the end of the object tree;
3 – new found controllers are stored at the end of the object tree.

x32: (x32)\Perco
x64: (x64)\Perco

DisableOffLine

0, 1, 2

0

4.7.4 and later

0  - standard action;
1 - controller access  to all cards with  shift schedule is forbidden;
2 - controller access to all cards is forbidden.

x32: (x32)\Perco
x64: (x64)\Perco

RequestTime

> = 0

1000

4.7.4 and later

Sets the time period during which the log is read, at the end of this period the reading stops and commands are executed (ms).

x32: (x32)\Perco
x64: (x64)\Perco

SendLevelBeforePerson

0, 1

0

4.7.4 and later

Defines whether to send the access level after sending person to controller or not.

x32: (x32)\Perco
x64: (x64)\Perco

ShowSendLevel

0, 1

0

4.7.4 and later

Defines whether the Send access levels button is shown for Perco object in Intellect settings or not:
0 - disabled (by default);
1 – enabled.

x32: (x32)\Perco
x64: (x64)\Perco

Show_progress

0, 1

0

4.7.4 and later

Defines whether to show progress bar when forwarding configuration or not.

x32: (x32)\Perco
x64: (x64)\Perco

TimeOut

-

-

4.7.4 and later

Set the gateway query timeout.

x32: (x32)\Perco
x64: (x64)\Perco

VerifyLogMesDB

-

-

-

The key is not in use.

Rubeg






x32: (x32)\RUBEG8_ISB
x64: (x64)\RUBEG8_ISB

ConvertUserBcpToUserIntellect

0, 1

0

4.7.4 and later

Defines whether to allow Rubeg users to access Intellect or not:
0 - forbid importing Rubeg users to Intellect;
1 - allow importing Rubeg users to Intellect.

x32: (x32)\RUBEG8_ISB
x64: (x64)\RUBEG8_ISB

ShowError

0, 1

0

4.7.4 and later

Defines whether to show dialog boxes with Rubeg COM server errors:
0  - forbid displaying dialog boxes;
1 - allow displaying dialog boxes.

x32: (x32)\RUBEG8_ISB
x64: (x64)\RUBEG8_ISB

UseThreadDynamicProcess

0, 1

1

4.7.5 and later

Sets the thread for forwarding user configuration:
0 - forwarding in the primary thread;
1 - forwarding in the secondary thread.

x32: (x32)\RUBEG8_ISB
x64: (x64)\RUBEG8_ISB

UseCorrectDuplicateUsers0, 104.7.6 and later

1 - algorithm of correction of duplicated users is in use;
0 - algorithm of correction of duplicated users is not in use.

x32: (x32)\RUBEG8_ISB
x64: (x64)\RUBEG8_ISB

UseConfigurationManager0, 10ACFA 6.1

The key is required for operation of integration with Failover module.

0 – do not save Rubezh server configuration to DB.

1 – save Rubezh server configuration to DB.

If Rubezh server configuration is not saved to DB, then it is stored in rcf files. When moving configuration to backup server these files will stay at dead computer and become unavailable, i.e. all settings will be reset to their defaults.

NAC-501/W6500.CNT ACS controller






x32: (x32)\Nac\Dll
x64: (x64)\Nac\Dll

delay

> = 1

1

4.7.4 and later

Delay (ms) when sending users between them. Default - 1 (no delay).

x32: (x32)\Nac
x64: (x64)\Nac

Delay green led

> = 0

0

4.7.4 and later

Defines how much time (ms) the reader (NAC51P only) is excluded from the query after receiving the event.

x32: (x32)\Nac
x64: (x64)\Nac

Delay open door

> = 0

500

4.7.4 and later

Defines how much time (ms) the reader (NAC51P only) is excluded from the query after authorized access.

x32: (x32)\Nac
x64: (x64)\Nac

Delay prohibited access

> = 0

250

4.7.4 and later

Defines how much time (ms) the reader (NAC51P only) is excluded from the query after enabling the prohibited access mode.

x32: (x32)\Nac
x64: (x64)\Nac

Delay red led

> = 0

250

4.7.4 and later

Defines how much time (ms) the reader (NAC51P only) is excluded from the query after prohibiting access.

x32: (x32)\Nac
x64: (x64)\Nac

enable_thread

1

1

4.7.4 and later

Checkbox of forwarding configuration in a separate thread; the value is always 1 (do not modify). The key is out of date.

x32: (x32)\Nac
x64: (x64)\Nac

fqLinkSet

> = 0

1000

4.7.4 and later

Defines the rate (ms) of attempts to connect the reader if there is no connection.

x32: (x32)\Nac
x64: (x64)\Nac

FlagsLog

0x01 - erroneous file recording/reading
0x02 - sent commands
0x04 - poll
0x08 - erroneous answers to sent commands
0x10 - erroneous answers to poll commands
0x20 - the reader is occupied, repeat is in nn ms
0x40 - card status confirmation
0x80 - master card is shown
0x100 - door open/close
0x200 - TIMEOUT

0x02F9

4.7.4 and later

Sets bit values for logging to log file (what to log).

x32: (x32)\Nac\Dll
x64: (x64)\Nac\Dll

show_progress

0, 1

1

4.7.4 and later

Defines whether to show the progress when forwarding the configuration.

SATEL FAS ACS






x32: (x32)\Satel
x64: (x64)\Satel

Get_Outputs

0, 1

1

4.7.4 and later

1 - Allow getting relay states;
0 - Forbid getting relay states.

x32: (x32)\Satel
x64: (x64)\Satel

Get_Troubles

0, 1

1

4.7.4 and later

1 - Allow getting states of troubles;
0 - Forbid getting states of troubles.

x32: (x32)\Satel
x64: (x64)\Satel

Timeout

Any positive number

300

4.7.4 and later

Timeout of getting next message byte from the controller, ms.

x32: (x32)\Satel
x64: (x64)\Satel

Transmit_Cmd_Timeout

Any positive number or 0 to forbid receiving states

 

1000

4.7.4 and later

Rate of getting states (relay and troubles) in ms.

x32: (x32)\Satel
x64: (x64)\Satel

Verify_Link_Timeout

Any positive number

500

4.7.4 and later

Max. waiting time (ms) of getting an event from controller.
If the value is exceeded, then module considers that there is no connection with controller.

"HoneyWell N1000" (Northern Computers)




x32: (x32)\nc

x64: (x64)\nc

bLogReact0, 114.7.4 and laterDisplaying incoming reactions in the debug window of the module and recording them to the log file.

x32: (x32)\nc

x64: (x64)\nc

bLogEvent0, 114.7.4 and laterDisplaying incoming events in the debug window of the module and recording them to the log file.

x32: (x32)\nc

x64: (x64)\nc

bLogCOM_Write0, 114.7.4 and laterDisplaying instructions sent to the terminal. Used for debugging.

x32: (x32)\nc

x64: (x64)\nc

bLogCOM_Read0, 114.7.4 and laterDisplaying transactions (events), received form the terminal, in the debug window of the module. Used for debugging.

x32: (x32)\nc

x64: (x64)\nc

bLogCOM_ReadAnswer0, 114.7.4 and laterDisplaying responses to the sent instructions in the debug window of the module. Used for debugging.

VMS (Visitor Management System)






x32: (x32)\id_limit
x64: (x64)\id_limit

PERSON_MINID

1-99999

-

4.7.6 and later

These keys are created to generate disjoint IDs of objects on different computers.
PERSON_MINID - PERSON_MAXID – allowed range of user IDs to edit access control service.
If PERSON_Restrict = 0, then keys are not active.

x32: (x32)\id_limit
x64: (x64)\id_limit
PERSON_MAXID1-99999-4.7.6 and later
x32: (x32)\id_limit
x64: (x64)\id_limit
PERSON_Restrict0, 104.7.6 and later
Photo ID




x32: (x32)\

x64: (x64)\

Note. If this section has not been created, then the system will look for the key in the section.

HKEY_CURRENT_USER\Software\ITV\INTELLECT\

 NOT_DELETE_PHOTO 0, 1 0 ACFA 6.0

In ACFA 5.4 and later versions it is possible to delete irrelevant photos in the Photo identification module: when the Photo identification module gets an event and if there is no photo on the Server that gets the event, then this photo is considered irrelevant and the clients connected to the Server get a command to delete the photo.

They key allows keeping irrelevant photos on the computer where the key value is 1.

0 – delete irrelevant photos on the computer.

1 – do not delete irrelevant photos on the computer.

Access Manager




x32 and x64: HKEY_CURRENT_USER\Software\ITV\INTELLECT\Account Manager(n*)\Folder name GUID**

Note 1. n* is Access Manager object ID in Intellect.

Note 2. Folder name GUID** is automatically generated. If Intellect is run with no authorization (i.e. no login or password entered at start), folder name is zero GUID, i.e. 00000000-0000-0000-0000-000000000000. If Intellect is run with authorization, folder name is this user's GUID, e.g. 3bf041df-8b39-e711-80b7-c0bfc074aae0.

ApplyOnEnter>=0-ACFA 6.5

The key enables confirmation (OK) by Enter in Full name of new user and Edit card dialog boxes.

0 – nothing happens when pressing Enter in these dialog boxes.

>0 – pressing Enter is equal to clicking OK in Full name of new user and Edit card dialog boxes.

x32 and x64: HKEY_CURRENT_USER\Software\ITV\INTELLECT\Account Manager(n*)\Folder name GUID**

Note 1. n* is Access Manager object ID in Intellect.

Note 2. Folder name GUID** is automatically generated. If Intellect is run with no authorization (i.e. no login or password entered at start), folder name is zero GUID, i.e. 00000000-0000-0000-0000-000000000000. If Intellect is run with authorization, folder name is this user's GUID, e.g. 3bf041df-8b39-e711-80b7-c0bfc074aae0.
RotateAngle0, 1, 2, 30ACFA 6.5

The key sets rotation angle for the template while printing.

0 – 0 degrees

1 – 90 degrees

2 – 180 degrees

3 – 270 degrees

Bolid SDK Orion v.2




x32: (x32)\SDKOrion

x64: (x64)\SDKOrion

AllUsersInDevices0, 10ACFA 6.0

The key specifies default value of the Save in device checkbox:

0 – checkbox is removed on default while user creation.

1 – checkbox is set on default while user creation.

x32: (x32)\SDKOrion

x64: (x64)\SDKOrion

SkipUnusedInputs0, 10ACFA 6.0

The key is in use if it's required to add only configured (not disabled) loops on the dual loop controller while automatic search and configuring of integration objects.

0 – disabled loops are adding to hardware tree.

1 – disabled loops are not adding to hardware tree.

...

ATM-Intellect

Registry section

String parameter

Available values

Default

Product version

Description

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

PeakWorkingSetSizeQuota

>=0

100

from 8.0


The maximum memory size in megabytes used by the process videosrv.exe on ATM-Intellect Pro. If the parameter is set to 0, then the check for the used memory is not performed.

Once a day, the ATM-Intellect Prochecks 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-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

TimeOfCheckWorkingSetSize

>=0

3

from 8.0

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

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

StoreVideoFiles

>0

3

from 5.0

Time period for storage of not completely downloaded files on ATM-Intellect Pro. After the storage period is exceeded, the not completely downloaded files are deleted.


x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)


run_intellect


0.1


1


from 5.0

The key sets the ATM-Intellect Pro actions in case if the Intellect software is shut down.

0 – do not start the Intellect software

1 – start the Intellect software




x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)




socket_connect_tout




>=0




0




from 5.0

The key defines TCP/IP connection mode with ATM-Intellect Workstation.

0 – blocking mode. ATM-Intellect Pro connects to ATM-Intellect Workstation without specifying connection timeout.

>0 – non-blocking mode. ATM-Intellect Pro connects to ATM-Intellect Workstation with a connection timeout set by the socket_connect_tout > 0 parameter in seconds.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

write_buffer_enable

0.1

1

from 7.0

Data buffering while recording on disc when receiving video data on ATM-Intellect Workstation. ATM-Intellect Pro transfers video data to ATM-Intellect Workstation in packages of 800 to 4096 bytes (4096 by default). When buffering is enabled, a 264 Kb block of memory is allocated to the ATM-Intellect Workstation 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 ATM-Intellect Pro.

0 – buffering is enabled.

1 – buffering is disabled.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

stop_data_by_trx

0.1

1

from 5.0

The key determines the actions of ATM-Intellect Pro in case if, during the transfer of video data to ATM-Intellect ARM, a financial transaction has begun on the ATM.

0 – video data transfer is not stopped.

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

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

IPPort> 07755from 5.0

The key specifies the port on the ATM-Intellect Workstation used for connecting the clients.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

financial_trx_tout

>0

60

from 7.0

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: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

TimeAlarmFromAgent


0, 10from 10.0The 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 ATM-Intellect Workstation.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

FileQueryEnable0, 10from 10.0

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 ATM-Intellect Workstation and/or Additional workstation

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

FileQueryPath
TextC:\Query\from 10.0

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 ATM-Intellect Workstation and/or Additional workstation

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

OldLogPanel0, 10from 11.0

The key changes the Log Panel interface color theme.

0 - dark interface theme.

1 - light interface theme.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

StreamViewerExportPathText<Intellect installation directory>\exportfrom 11.0

The key specifies the path to the catalog of frames and video clips which were exported from the Monitoring 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-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

MonitoringReserving0, 10from 11.0

The key removes the restriction on adding the same cameras for tracking in different Surveillance Objects.

0 - the restriction is enabled.

1 - the restriction is removed.

x32: HKLM\SOFTWARE\BitSoft\MonitorSSTV\Loader

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

UseBulkInsert0, 1
from 10.0

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-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

PrefixForTimeOutText-from 10.0The key specifies the prefix in the identifier of the Surveillance Objects for which the waiting timeout specified in the TimeoutForPrefix key should be specified.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

TimeoutForPrefix>06from 10.0The key sets the waiting timeout in minutes for the ATM-Intellect Workstation to receive the packets with the technical state of ATM-Intellect Pro. After this time the "No connection" error will be displayed.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

UsingTimeoutForPrefix0, 10only 10.0The key enables the waiting timeout set in the TimeoutForPrefix key for all Surveillance objects with the identifier prefix specified in the PrefixForTimeOut key.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

PostfixForTimeOutText-from 11.0The key specifies the postfix in the identifier of the Surveillance Objects for which the waiting timeout specified in the TimeoutForPostfix key should be specified.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

TimeoutForPostfix>06from 11.0The key sets the waiting timeout in minutes for the ATM-Intellect Workstation to receive the packets with the technical state of ATM-Intellect Pro. After this time the "No connection" error will be displayed.
HKEY_CURRENT_USER\SOFTWARE\BitSoft\MonitorSSTVMAXRECORDSONPAGE1,000 - 2,000,000,00010,000from 11.0Sets the maximum number of events to be displayed in the Event Log window without navigation buttons.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

LastLoadThreshold >= 030from 11.0

The key sets the time in minutes, after which, if the data in the MonitorSSTV database is outdated, the corresponding indication on the ATM-Intellect Workstation will appear.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

DisableMonitoring0, 10from 13.0

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-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

StreamViewerLowestPriority0, 10from 13.0

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-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

SleepAfterDisarminteger in ms50from 14.0

The key sets the time interval of recording delay in ms after disarming the camera

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

SleepAfterRecStopinteger in ms50from 14.0

If the continuous recording mode is enabled, the key sets the time interval of recording delay by camera in ms after the camera is stopped.

If the camera is armed, the key sets the time interval of camera arming delay in ms after the camera is stopped

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

KeepVideoDataInBase>00from 14.0

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

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

Restricting the Operator’s access to the camera's functional menu and its options

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

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

MENU_DISABLE_OPTION0, 10from 11.0

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

MENU_ARM_DISABLE_OPTION0, 10from 11.0

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

MENU_REC_DISABLE_OPTION0, 10from 11.0

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

MENU_CAMS_DISABLE_OPTION0, 10from 11.0

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

MENU_TITLES_DISABLE_OPTION0, 10from 11.0

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

MENU_PROCESSING_DISABLE_OPTION0, 10from 11.0

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

MENU_EXPORT_DISABLE_OPTION0, 10from 11.0

The key hides the Export menu option.

0 - The Export menu option is displayed.

1 - The Export menu option is hidden.

Restricting the Operator’s access to the Processing menu within the camera's functional menu

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

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

MENU_PROCESSING_DEINTERLACE_DISABLE_OPTION0, 10from 11.0

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

MENU_PROCESSING_ZOOM_DISABLE_OPTION0, 10from 11.0

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

MENU_PROCESSING_CONTRAST_DISABLE_OPTION0, 10from 11.0

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

MENU_PROCESSING_MASK_DISABLE_OPTION0, 10from 11.0

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

MENU_PROCESSING_SHARPNESS_DISABLE_OPTION0, 10from 11.0

The key hides the Sharpen menu option.

0 - The Sharpen menu option is displayed.

1 - The Sharpen menu option is hidden.

Restricting the Operator’s access to the CamMonitor component buttons

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

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

BUTTON_ARCH_DISABLE_OPTION0, 10from 11.0

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

BUTTON_TIME_DISABLE_OPTION0, 10from 11.0

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

BUTTON_NAME_DISABLE_OPTION0, 10from 11.0

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

BUTTON_MENU_DISABLE_OPTION0, 10from 11.0

The key hides the Menu button.

0 - The Menu button is displayed.

1 - The Menu button is hidden.

Restricting the Operator’s access to the CamMonitor control via the keyboard and mouse

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

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

KEYS_DISABLE_OPTION0, 10from 11.0

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

TELEMETRY_ENABLE_OPTION0, 10from 11.0

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

ARCH_DELETE_ENABLE_OPTION0, 10from 11.0

The key activates the Delete menu item which is used to remove the recordings from the archive. It is used only in Intellect version 4.11 and higher (see Deleting video recordings 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

ARCH_PROTECT_ENABLE_OPTION0, 10from 11.0

The key activates the Protect menu item which is used to protect the archive recordings from rewriting. It is used only in Intellect version 4.11 and higher (see Protection of separate record and disable of protection).

0 - The Protect item is hidden.

1 - The Protect item is displayed.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

ExportPathText

DISK:\Export\

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

-

Sets the path to the export directory on ATM-Intellect Workstation

 TABLE OF CONTENTS

 

ATM Event Capture

Registry section

String parameter

Available values

Default

Product version

Parameter in effect

x32: (x32-ATM Event Capture)

x64: (x64-ATM Event Capture)

JrnTOut

>0

10

from 9.0


Timeout in seconds for waiting for the information about the card insertion to appear in the ATM log after the actual card insertion.

For m_JrnMode=2 mode only (MAK3 TUSSON)

x32: (x32-ATM Event Capture)

x64: (x64-ATM Event Capture)

Mask>=0--

Specifies the options for masking the card number. By default, the first 6 and last 4 characters of the card number are not masked.

0 – if no mask to be applied to the card number.

1-6 – number of digits in the beginning of the card number which are not masked.

x32: (x32-ATM Event Capture)

x64: (x64-ATM Event Capture)

JrnMode>=00-

Defines the mode of operating the journal.

0 – card number is read from the card reader

1 – card number is read from the ATM journal through the Protopas software (Wincor)

2 – card number is read from the ATM journal through the MAK3 (TUSSON) software

3 – card number is read from the ATM journal through the TellMe (SCS) software

4 – card number is read from the ATM journal through the APTRA Advance NDC (NCR) software

x32: (x32-ATM Event Capture)

x64: (x64-ATM Event Capture)

JrnPath >=0--

Specifies the path to the ATM journal.

If JrnMode = 1, then JrnPath = C:\JOURNAL\

If JrnMode = 2, then JrnPath = C:\scs\atm_h\PRJ\

If JrnMode = 3, then JrnPath = C:\scs\atm_h\PRJ\

If JrnMode = 4, then JrnPath = C:\program files\ncr aptra\advance ndc\data\

x32: (x32-ATM Event Capture)

x64: (x64-ATM Event Capture)

JrnTrack2Substring >=0--

Specifies the substring for searching the card number.

If JrnMode = 1, then JrnTrack2Substring = (TRACK 2 DATA)

If JrnMode = 2, then JrnTrack2Substring = @++

If JrnMode = 3, then JrnTrack2Substring = CARD

If JrnMode = 4, then JrnTrack2Substring = CARD

x32: (x32-ATM Event Capture)

x64: (x64-ATM Event Capture)

LogEnable0, 10-

Enables logging the ATM Event Capture utility operation

0 - event log is disabled

1 - event log is enabled. After you quit and start ATM Event Capture utility again, the EventATM.log file appears in the installation folder.

...

IP integration (drivers and codecs pack for Intellect)

Registry section

String parameter

Available values

Default

Product version

Parameter in effect

x32: (X32)\Video
x64: (x64)\Video

ArchiveFps

1-24


4.7.5 and later

Sets the number of frames recorded to the archive (max.resolution). LiveFps and ArchiveFps parameters are not to exceed 24 in total.

x32: (X32)\Video
x64: (x64)\Video

ArecontVision

0, 1


up to  4.8.0

Enables the protocol for integrating Arecont cameras. The key is not in use.

x32: (X32)\Video
x64: (x64)\Video

DoubleStream

0, 1


4.7.5 and later

Defines whether asynchronous video display mode is enabled or not.

x32: (X32)\Video
x64: (x64)\Video

IpIntDrivers3

Brand name: Axis; Acti, etc.


4.7.3 and later

The IpIntDrivers3 string parameter is created and the names of brands that need 3.0 driver are listed.

x32: (X32)\Video
x64: (x64)\Video

IpIntDriverVersion

2, 3


4.7.3 and later

Defines the version number of loaded drivers:
2 – to load drivers version 2.0;
3 - to load drivers version 3.0;
This parameter has a high priority and cancels IpIntDrivers3 parameter.

x32: (X32)\Video
x64: (x64)\Video

LiveFps

1-24


4.7.5 and later

Sets the number of frames displayed in the 800x600 format. LiveFps and ArchiveFps parameters are not to exceed 24 in total.

x32: (X32)
x64: (x64)

LoadIpIntDirectly

0, 1

 

4.9.0 and later 

1 - enable IntegratedDevice via video.run. If the setting is enabled and at least one IntegratedDevice is added, then other IP video capture cards are disabled.

0 - IIntegratedDevice operates as a separate run-module.

x32: (X32)\Video\TransportProtocols
x64: (x64)\Video\TransportProtocols
<Driver name><protocol>-DP 3.1.1 and later

The key is used to change a transport protocol used by the IP device.

Example of the key value: "ONVIF"="tcp" means that TCP protocol is used to transfer data via ONVIF.

See details in Changing the transport protocol used by IP-device

Example of the key value: "rtsp"="multicast" allows enabling Multicast mode of the RTSP Server. The object configuration is required in addition to the key.

See details in Configuring RTSP Server module.

x32: (X32)\Video\MetadataTransportProtocols
x64: (x64)\Video\MetadataTransportProtocols

The name of camera driver (in the driver parameter of the

C:\Program Files\ Common Files\ AxxonSoft\ Ipint.DriverPack \3.0.0\ Ipint.<Driver name>.rep file)
The name of transport protocol (is to be the same as one of the values specified in metadataTransportProtocol property in the corresponding .rep file).-DP 3.31.1613 and laterThe key is used to change a metadata transport protocol. At the time of writing this documentation change of a metadata transport protocol was available for ONVIF driver only (possible values are tcp and udp).
x32: (X32)\Video
x64: (x64)\Video
UnloadUnusedDriverTimeout>=060DP 3.32.1638 and later

The key sets unused driver unload timeout for cameras. For instance, if camera brand is in several drivers, all of them are loaded at camera connection. To unload the unused drivers, set non-zero value to this key.

If the key is not created, then unused drivers are unloaded in 60 seconds.

0 – drivers do not unload (such behavior was in DriverPack versions older than the current one).

The key value that is > 0 sets unused driver unload timeout.

If the key is created but it consists of NaN value, then unused driver unload timeout is set to the default value – 60 seconds.

x32: (X32)\TELEMETRY
x64: (x64)\TELEMETRY

PresetCompatibility0, 1-DP 3.43.1950 and later

The key is used to enable the compatibility between presets in Intellect and previous versions of Drivers Pack, i.e. to decreasing the preset number by 1 when sending it to the driver.

0 – a new operation mechanism with presets the same as in AxxonNext is in use in Intellect. If preset 1 is selected in Intellect interface, then value 1 is sent to the driver.

1, or if the key is not created – the compatibility mode is in use: if preset 1 is selected/created in Intellect interface, then value 0 is sent to the driver.

x32: (x32)\Video
x64: (x64)\Video

FFTHREADCOUNT>=01DP 3.43.1955 and later

The key sets the number of streams created in FFmpegDecoder.

0 – decoder automatically selects the number of created streams.

>0 – sets the number of streams in use.

By default if there is no key or the value is incorrect, then value 1 is in use.

Auto selection of the number of streams can result in the system load reduction or its increase as the number of streams recreated during decoding increases – this affects the performance.

x32: (x32)\EventSources
x64: (x64)\EventSources

<brand>.<model> (for example, ONVIF.1_channel_device).

If all models of some manufacturer require a specific method of getting events, then there must be a string key named <brand> in the section.

Pull point

Meta data

Disable

Meta dataDP 3.35.1692

By the date the documentation in created, this key is supported for three brands: ONVIF, RVi and IDIS. For models of these brands, the key is created automatically when the Drivers Pack is installed.

The key sets a method of getting data about the analytics and the sensors of the device:

  • Pull point – getting events by http request of the camera
  • Meta data – getting events from the metadata stream
  • Disable – getting events is disabled.
All other values (including an empty string) or if there is no key for the model and brand in the specified section mean that you must use the default method, created as default in the rep file for the given model.
x32: (x32)\Video\UseSsrcChecking
x64: (x64)\Video\UseSsrcChecking
RTSP

enable

disable

enableDP 3.45.2055

The key is intended for setting up synchronization source (SSRC) for RTSP stream:

enable – SSRC check enabled;

disable – SSRC check disabled.

x32: (x32)\Video
x64: (x64)\Video

FFLOGDELAY0, 10CP 1.580Enables logging of delays of frames decoding and idle time for FFMPEG codec.
x32: (x32)\Video\TsConverters
x64: (x64)\Video\TsConverters

<brand>.<model>, for example, Tattile.ANPR Mobile

If all brand's models require a certain method of the timestamp adjustment, then the section must contain a string key with the name <brand>.

  • InfrequentTs
  • ValidDeviceTs
  • None
Depends on the brandDP 3.34 and later

The keys in this section specify the method of the frame timestamp adjustment.

If the key is not created, the timestamp transferred to the Intellect equals 0, and then the current time is set as its value.

The None value is used if it is necessary to disable the adjustment and transfer the timestamp received from the camera as is.

The ValidDeviceTs value means that the timestamp adjustment method is used before the timestamps transmission to the Intellect if the timestamp received from the camera differs from the current time by the value greater than the one specified in the MaxTimestampDeviation key (see below). After the adjustment, the timestamp calculated on the basis of the previous frame's timestamp and the time elapsed since its reception is transmitted to the Intellect.

InfrequentTs value discards the relative timestamps, transferring 0 to the Intellect instead (i.e., the current time is set as the timestamp value), and it also transfers the absolute timestamps with the ETimestampValidityFlag flag. This adjustment method should be used for the devices with the license plates recognition which transfer the separate frames to the external system, rather than a continuous video stream.

For some manufacturers, when installing the Drivers Pack, the keys with the necessary values are automatically created in the appropriate registry key.

x32: (x32)\Video
x64: (x64)\Video
MaxTimestampDeviation>=0-DP 3.34 and later

The key is used for the ValidDeviceTs key value from the TsConverters branch (see above).

The key sets the maximum permissible deviation of the frame timestamp from the current Server time.

x32: (x32)\Video
x64: (x64)\Video
ErrorSensitivity0, 10DP 3.54 and later

The key enables the interruption of the H.265 video decoding via the ffmpeg decoder in case of the slightest error in the video stream.

0 - if the video stream contains errors, then a buffer with artifacts will be received from the ffmpeg decoder.

1 - if the video stream contains errors, then an empty buffer will be received from the ffmpeg decoder.

x32: (x32)\Video\RTSP
x64: (x64)\Video\RTSP
AudioSeparatedConnection0, 10DP 3.60 and laterEnables RTSP audio over a separate TCP connection.
x32: (x32)\Video
x64: (x64)\Video
servicesVersionauto, ver1, ver2autoDP 3.61 and later

The key sets the version of ONVIF services (only for ONVIF and ONVIF 2.X):

auto – get available versions and choose the latest if possible.

ver1 – use old versions of services.

ver2 – use new versions of services.

x32: (x32)\Video
x64: (x64)\Video
servicesSourcegetServices, getCapabilitiesgetServicesDP 3.61 and later

The key determines the source of the ONVIF services version (only for ONVIF and ONVIF 2.X):

getServices – get a list of services using the new interface.

getCapabilities – get a list of services using the old interface.

x32: (x32)\Video\Virtual
x64: (x64)\Video\Virtual
​playFileOnce0, 10DP 3.62 and later

Disables looping files in a virtual video capture device of a Virtual bench type.

0 - videos in a Virtual bench virtual capture device are played in a loop.

1 - videos in a Virtual bench virtual capture device are played once.

See also Creating and configuring a virtual Video Capture Device.

x32: (X32)\TELEMETRY
x64: (x64)\TELEMETRY
cgiPrefix

"/cgi-bin/ptz.cgi?", "/stw-cgi/ptzcontrol.cgi?"

-DP 3.58 and later

The key is required for PTZ operation with Hanwha Techwin IP-devices:

"/cgi-bin/ptz.cgi?" – for old models (not X-series)

"/stw-cgi/ptzcontrol.cgi?" –  for new models X-series

x32: (x32)\Video
x64: 
(x64)\Video

DecompressorResetOnErrorTimeout0 - 18060

DP 3.69 and later

Compatibility: Intellect 4.10.5.4526 and later

Time in seconds before the decompressor resets after an error. The value for the key should be selected empirically based on the stream parameters of a particular video camera.

Attention! It is recommended to change the value for the key only with the assistance of technical support.

x32: (x32)\Video
x64: (x64)\Video
IQS_ADDITIONTAL_VIDEO_FRAMES_COUNT>=11DP 3.71 and later

The key sets the number of buffered decoded frames for the IntelQuickSync decoder.

TABLE OF CONTENTS


x32HeatZoneDetectorx64HeatZoneDetector

Activates the start of the detector in a separate process.

0 - the detector is started in one shared detector shared . - the detector runs process DetectorTypeId detector a subdetectors An example a fire detector FIREDETECTOR.

Detector types:

BARCODE_DETECTOR − bar code detector;

BASE_POSE_DETECTOR − base pose detector;

CROWD_COUNTER − counter crowd movement detector;

EQUIPMENT_DETECTOR − equipment detector;

FIRE_DETECTOR − fire detector;

FLUID_DETECTOR − fluid gauging detector;

GLOW_DETECTOR − indicating glow detector;

HEAT_ZONE_DETECTOR − store “cold/hot” zones detector;

NEURO_COUNTER − neuro counter;

NEURO_TRACKER − neuro tracker;

OCCUPANCY_COUNTER − queue length detector;

PEOPLE_COUNTER − people counter detector;

SMOKE_DETECTOR − smoke detector;

STOPPED_CAR_DETECTOR − stopped car detector;

SWEETHEARTING_DETECTOR − sweethearting detector;

TRAFFIC_LIGHTS − traffic lights detector;

TRAIN_DETECTOR − train detector;

VIDEO_INTELLECT_INTERNAL_DETECTOR − Video Intellect internal detector.

Detectors pack

DetectorPack Intellect

Registry section

String parameterAvailable valuesDefaultProduct versionParameter in effect

x32: (

х32)\DetectorExt\

BARCODE_DETECTOR

x64: (

х64)\DetectorExt\

ReportFrequency >09004.9.0 and later

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

x32: (x32)\DetectorExt\HeatZoneDetector

x64: (x64)\DetectorExt\HeatZoneDetector

DebugReportFrequency >0104.9.0 and later

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

x32: (X32)\Video\
x64: (x64)\Video\
report_frequency>=030002.6 and laterSets the time period in milliseconds, during which the repeated triggering of the Sweethearting detection module is ignored.
x32: (X32)\
x64: (x64)\
ShowVideoIntellectObjects ><=0-2.8 and later

Hides the VideoIntellect detector objects from the Intellect objects tree.

0 - the VideoIntellect detector objects are hidden.

><0 - VideoIntellect detector objects are displayed.

x32: (X32)\Video
x64: (x64)\Video
LongInZoneTimeout2>=0-2.8 and later

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 Intellect Enterprise base version).

BARCODE_DETECTOR

IsProcessObject0, 10DP 2.8 and later

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

1detection 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: (х32)\DetectorExt\BASE_POSE_DETECTOR

x64: (х64)\DetectorExt\BASE_POSE_DETECTOR

 

IsProcessObject0, 10DP 2.8 and later

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

1detection 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: (х32)\DetectorExt\CONVEYOR_BELT_DETECTOR

x64: (х64)\DetectorExt\CONVEYOR_BELT_DETECTOR

 

IsProcessObject0, 10DP 2.8 and later

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

1detection 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: (х32)\DetectorExt\CROWD_COUNTER

x64: (х64)\DetectorExt\CROWD_COUNTER

 

IsProcessObject0, 10DP 2.8 and later

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

1detection 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: (х32)\DetectorExt\CROWD_COUNTER_TVN

x64: (х64)\DetectorExt\CROWD_COUNTER_TVN

 

IsProcessObject0, 10DP 2.8 and laterx32: (X32)\DDP
x64: (x64)\DDP
IsProcessObject_BARCODE_DETECTOR
IsProcessObject_BASE_POSE_DETECTOR
IsProcessObject_CROWD_COUNTER
IsProcessObject_EQUIPMENT_DETECTOR
IsProcessObject_FIRE_DETECTOR
IsProcessObject_FLUID_DETECTOR
IsProcessObject_GLOW_DETECTOR
IsProcessObject_HEAT_ZONE_DETECTOR
IsProcessObject_NEURO_COUNTER
IsProcessObject_NEURO_TRACKER
IsProcessObject_OCCUPANCY_COUNTER
IsProcessObject_PEOPLE_COUNTER
IsProcessObject_SMOKE_DETECTOR
IsProcessObject_STOPPED_CAR_DETECTOR
IsProcessObject_SWEETHEARTING_DETECTOR
IsProcessObject_TRAFFIC_LIGHTS
IsProcessObject_TRAIN_DETECTOR
IsProcessObject_VIDEO_INTELLECT_INTERNAL_DETECTOR
0, 102.8 and later

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 (TVN): External Detector -

CROWD_

COUNTER_TVN.1

...

x32: (х32)\DetectorExt\EQUIPMENT_DETECTOR

x64: (х64)\DetectorExt\EQUIPMENT_DETECTOR

 

IsProcessObject0, 10DP 2.8 and later

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

1detection 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: (х32)\DetectorExt\FIRE_DETECTOR

x64: (х64)\DetectorExt\FIRE_DETECTOR

 

IsProcessObject0, 10DP 2.8 and later

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

1detection 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: (х32)\DetectorExt\FLUID_DETECTOR

x64: (х64)\DetectorExt\FLUID_DETECTOR

 

IsProcessObject0, 10DP 2.8 and later

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

1detection 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: (х32)\DetectorExt\GLOW_DETECTOR

x64: (х64)\DetectorExt\GLOW_DETECTOR

 

IsProcessObject0, 10DP 2.8 and later

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

1detection 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: (х32)\DetectorExt\HEAT_ZONE_DETECTOR

x64: (х64)\DetectorExt\HEAT_ZONE_DETECTOR

 

IsProcessObject0, 10DP 2.8 and later

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

1detection 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\HeatZoneDetector

x64: (x64)\DetectorExt\HeatZoneDetector

ReportFrequency >0900Intellect 4.9.0 and later

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

x32: (x32)\DetectorExt\HeatZoneDetector

x64: (x64)\DetectorExt\HeatZoneDetector

DebugReportFrequency >010Intellect 4.9.0 and later

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

x32: (х32)\DetectorExt\NEURO_COUNTER

x64: (х64)\DetectorExt\NEURO_COUNTER

 

IsProcessObject0, 10DP 2.8 and later

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

1detection 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: (х32)\DetectorExt\NEURO_TRACKER

x64: (х64)\DetectorExt\NEURO_TRACKER

 

IsProcessObject0, 10DP 2.8 and later

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

1detection 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: (х32)\DetectorExt\OCCUPANCY_COUNTER

x64: (х64)\DetectorExt\OCCUPANCY_COUNTER

 

IsProcessObject0, 10DP 2.8 and later

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

1detection 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: (х32)\DetectorExt\PEOPLE_COUNTER

x64: (х64)\DetectorExt\PEOPLE_COUNTER

 

IsProcessObject0, 10DP 2.8 and later

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

1detection 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: (х32)\DetectorExt\SMOKE_DETECTOR

x64: (х64)\DetectorExt\SMOKE_DETECTOR

 

IsProcessObject0, 10DP 2.8 and later

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

1detection 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: (х32)\DetectorExt\STOPPED_CAR_DETECTOR

x64: (х64)\DetectorExt\STOPPED_CAR_DETECTOR

 

IsProcessObject0, 10DP 2.8 and later

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

1detection 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: (х32)\DetectorExt\SWEETHEARTING_DETECTOR

x64: (х64)\DetectorExt\SWEETHEARTING_DETECTOR

 

IsProcessObject0, 10DP 2.8 and later

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

1detection 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: (х32)\DetectorExt\TRAFFIC_LIGHTS

x64: (х64)\DetectorExt\TRAFFIC_LIGHTS

 

IsProcessObject0, 10DP 2.8 and later

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

1detection 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: (х32)\DetectorExt\TRAIN_DETECTOR

x64: (х64)\DetectorExt\TRAIN_DETECTOR

 

IsProcessObject0, 10DP 2.8 and later

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

1detection 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: (х32)\DetectorExt\VIDEO_INTELLECT_INTERNAL_DETECTOR

x64: (х64)\DetectorExt\VIDEO_INTELLECT_INTERNAL_DETECTOR

 

IsProcessObject0, 10DP 2.8 and later

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

1detection 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

x32: (X32)\Video\
x64: (x64)\Video\
report_frequency>=03000DP 2.6 and laterSets the time period in milliseconds, during which the repeated triggering of the Sweethearting detection module is ignored
x32: (X32)\
x64: (x64)\
ShowVideoIntellectObjects ><=0-DP 2.8 and later

Hides the VideoIntellect detector objects from the Intellect objects tree

0—the VideoIntellect detector objects are hidden

><0—the VideoIntellect detector objects are displayed

x32: (X32)\Video
x64: (x64)\Video
LongInZoneTimeout2>=0-DP 2.8 and later

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 Intellect Enterprise base version)

TABLE OF CONTENTS

 

Intellect Web Report System

Registry section

String parameter

Available values

Default

Product version

Parameter in effect

x32: (x32)
x64: (x64)


LogingPersonChangesRequired

0, 1

0

3.4 and later


Enabling of this parameter is necessary for the correct operation of the Issued pass cards report

x32: (x32)
x64: (x64)
RestPortport number224413.5 and later, Intellect 4.11.3 and later

Sets the port that is used for the data exchange via HTTP requests with Intellect Web Report System

If the key value is 0, data exchange via HTTP won't work

...