Page History

x32: (x32)\FRS
x64: (x64)\FRS

The key defines on how many CPU cores the face recognition module will operate (firserver.run process). All cores are in use by default.

x32: (x32)\FRS
x64: (x64)\FRS

The key determines how many CPU cores will be used for face search:

0—the number of cores specified in the CpuCoreCount key. The cores are used sequentially. Each core is assigned its own recognition instance.

1—only 1 fixed core is used

2—only 2 fixed cores are used

and so on

The key sets the timeout upon which Face Server ‘loses’ the face if there is no new data about it.

Sets the parameters of generating and attaching face biometrics in the detection tool:

1 – Face detection tools generate and attach face biometrics to the photo. 

0 – Face detection tools do not generate face biometrics – the face is only captured.

Note. Face recognition Server that performs search in the user database checks up whether it has attached biometrics when it gets a face photo. If yes, then biometrics are not further generated for search in the database – data attached to the photo is in use. If no, then recognition Server generates biometrics itself using the photo. 

The key is used to configure the face detection tool – it sets time on the expiry of which the face is considered lost.

For instance, if timeUntilLost = 1 and a man covers his face with the hands in front of the camera and then shows it again, then the face detection tool does not capture it as it considers that the face was lost for the time it was covered.

The key enables function of ignoring repeatedly recognized faces. While enabling this function all vectors of captured faces are saved in cache for the specified time interval. When new face is captured, its biometric vector is comparing with already existed vectors in cache. If it coincides with one of such vectors with specified similarity rate then it doesn't send to the further processing. Duration of vector storing in a cache is specified using the Skip repeated recognitions, sec parameter of the Face Recognition Server object. Similarity rate for comparison is came from the Similarity level parameter of the same object. See also Face PSIM software package. Administrator's Guide, section Configuring the captured faces recognition parameters.

The key sets the storage mode for metadata, images and vectors of captured and reference faces.

0 – metadata, images and vectors are stored only in the database.

1 – metadata, images and vectors are stored in the database, and images and vectors are also stored in a folder on disk. The path to the folder is set by the FaceDB parameter (you can specify both local and network folders).

2 – metadata is stored in the database, and images and vectors are stored only in a folder on disk. The path to the folder is set by the FaceDB parameter (you can specify both local and network folders).

Note 1. Metadata is stored in the database in the Hits table, regardless of the value of the UseFaceDB key. 

Note 2. Images of reference faces are stored in the <Axxon PSIM software installation directory>\Bmp\Person folder, regardless of the UseFaceDB key value.

Note 3. Only the UseFaceDB = 2 mode is supported, which is set automatically when Face Axxon PSIM starts if a mode other than this is detected.

The key is used if the the UseFaceDB parameter value is 1 or 2 (see above). The key sets the size of free disk space in megabytes. Once the specified size is reached, the old images, vectors and metadata of captured faces will be deleted. The cleanup is performed on a loop in portions equivalent to 1000 megabytes.

CpuCoreCountAddPerson

The key defines the number of CPU cores where the vectors of persons are generated when adding a reference face to the database.

0 – vectors are generated on the number of cores specified in the CpuCoreCount key. The cores are used successively. Recognition sample is bound to each core.

1 – only 1 fixed core (different from those specified in CpuCoreCount) is in use when adding a reference face to the database.

2 – only 2 fixed cores (different from those specified in CpuCoreCount) are in use when adding a reference face to the database.

Face.HardwareCPU

The key defines the order of binding streams to CPU cores when generating vectors of persons.

no value or 0 – streams are bound randomly to CPU cores.
1 – streams are bound successively to CPU cores depending on their total number.
2 – streams are bound to first cores of each CPU.

Mechanism of displaying faces. When a new mechanism of displaying is enabled, the photo in the list of captured faces is not duplicated – it is updated in the same cell while the tracker "sees" it.  

0 – new mechanism of displaying faces. 

1 – old mechanism of displaying faces. 

The key enables saving the last recognized face and all its necessary data to a file. This image file can be sent directly to the recognition server via the iidk_client utility.

0 – General operation mode.

1 – When the face is captured, the captureFrame (cam_N) .log file is created (where N is the camera number that captured the face) in the <Axxon PSIM Installer directory>\Modules64\Firserver folder\. This file will contain the last recognized face and all its necessary data. This image file can be sent directly to the recognition server via the iidk_client utility.

Note. The file is overwritten every time a new face is captured.

The key restricts resolution (width) of the photo when adding it to the faces database.

Set greater value to the key if the following message appears when adding a face to DB: "Adding error. The face was not added. Insufficient image quality to add".

The key restricts resolution (height) of the photo when adding it to the faces database.

The key enables selecting the face recognition and search algorithm.

0 – less resource intensive algorithm is in use

1 – more resource intensive algorithm is in use 

Important! Biometric vectors received using this algorithm cannot be used with alternative one. For proper operation of Face PSIM after changing this parameter biometric vectors are to be converted as described in Switching between the face recognition modules section. 

An alternative algorithm for filtering false triggerings of the tracker. This key is in use if Va.GlobalTrackingDetectionFilter=0 and Va.DetectionFilterValue > 0 (see the corresponding parameters below). 

0 – ALG1

1 – ALG2

Note. It is not recommended to change this parameter without consulting with AxxonSoft technical support.

Configuring alternative algorithm filtering. It is in use if the value of Va.GlobalTrackingDetectionFilter is more than 0 (see the corresponding parameter below).

Note. It is not recommended to change this parameter without consulting with AxxonSoft technical support.

Activates an additional check to filter out false triggerings of the tracker. If faces in masks are not recognized, it is recommended to disable this check, however, this can cause false triggerings of the tracker.

0 – disabled

1 – enabled

Note. It is not recommended to change this parameter without first consulting with AxxonSoft technical support.

Face detection operation mode (identification). The recommended parameter value is 0.

0 – ALG1

1 – ALG2

Note. It is not recommended to change this parameter without consulting with AxxonSoft technical support.

This parameter affects the detector captioning capacity. If there is a great value, the tracks can rend.

Note. It is not recommended to change this parameter without consulting with AxxonSoft technical support.

Face detector confidence threshold (do not confuse with face quality).

Note. It is not recommended to change this parameter without consulting with AxxonSoft technical support.

The key enables selecting the algorithm for recognition and face search.

0 – ALG1 less resource-intensive algorithm is in use.

1 – ALG2 identification of the higher quality, but more resource-intensive.

2 – PRECISE the highest quality of recognition, but the most resource-intensive. This algorithm is recommended if significantly less time is spent on face recognition than on detection (if there are few people in the frame).

Important! Since the biometric vectors received by one algorithm cannot be used by another, then after changing the algorithm, the biometric vectors are automatically recreated. The biometric vectors can also be recreated manually (see Switching between the face recognition modules or SDK versions).

Specifies the number of seconds to accumulate the best frames of a track for recognition. The increase in time makes it possible to average out the recognized face characteristics, but it can result in the poorer accuracy of the face characteristics recognition.

Note. For example, if the 1 second value is set, the average error in determining the age will be 2-3 years, and if the 5 seconds value is set, it will be 3-4 years.

Time since the last recognition after which the track is considered ended.

Note. It is not recommended to change this parameter without consulting with AxxonSoft technical support.

Sets the sensitivity of the closed eyes recognition. The higher the value, the less sensitive the closed eyes detector.

Specifies which frames will be recognized.

0 − only 0—only the best frame defined by VA by VA will be recognized.

1 − all 1—all frames will be recognized, as a result the quality of recognition increases, but the CPU load increases, too

Activates the Eyes closed event generation when closed eyes are detected.

The key defines the operating mode for the frame-based artificial face detection algorithm:

0—the algorithm is disabled

1—standard operation mode of the algorithm

2—slower but more accurate operation mode of the algorithm

This key can be used together with the Va.LivenessTextureDetectionAlgorithm key for better results

The key

defines the operating mode for the texture-based artificial face detection algorithm. The following conditions are required for proper operation: high-quality video image, a large face size, and a region of interest (ROI) focused on the center of the frame.

0—the algorithm is disabled

1—standard operation mode of the algorithm

2—slower but more accurate operation mode of the algorithm

3—enables combined operation with the frame-based artificial face detection algorithm (the registry key Va.LivenessDetectionAlgorithm value must be set to 1 or 2)

Enables the launch of each Face Recognition Server in a separate process.

0 – all Face Recognition Servers launch in the same process.

1 – each Face Recognition Server is launched in a separate processActivates the Eyes closed event generation when closed eyes are detected.

IsProcessObject

Enables the launch of each Face Recognition Server in a separate process.

0 – all Face Recognition Servers launch in the same process.

1 – each Face Recognition Server is launched in a separate process

Enables ignoring threads affinity to kernels inside firserver.run.

0 – ignoring threads affinity to kernels is disabled.

1 – ignoring threads affinity to kernels is enabled. The key is used in conjunction with the IsProcessObject=0 key.

Enables ignoring threads affinity to kernels inside firserver.run.

0 – ignoring threads affinity to kernels is disabled.

1 – ignoring threads affinity to kernels is enabled. The key is used in conjunction with the IsProcessObject=0 key.

ResizeWidth

Sets the video resolution that is sent from cameras to all Face Detection modules.

Sets the video resolution that is sent from cameras to all Face Detection modules.

Actually, the width of the video image is set, and the height is adjusted automatically based on the aspect ratio of the original video. For example, if the original video has a resolution of 2560x1920, then if you set the value to 960, then the video will be converted to a resolution of 960x720.

If the value is set to 0, then the video image will be received in its original resolution.

Enables compliance check of Face PSIM users with Axxon PSIM users:

0—compliance check is disabled, user changes are not checked

1—compliance check is enabled. All user changes made in the Axxon PSIM database, but missing in the Face PSIM database, are transferred there. User parameters that are present in the Face PSIM database, but missing in the Axxon PSIM database, are deleted

SaveThermalJson

Enables saving all json and images received from the thermal camera during face recognition to the folder. The data from the camera will be saved at the following address:

• In case of face recognition: <Axxon PSIM installation directory>\Modules64\Firserver\ThermalImages\{Face detection tool ID}
• In case the face is not recognized: <Axxon PSIM installation directory>\Modules64\Firserver\ThermalImages\{Face detection tool ID}\NoFaces

0 – data from the thermal camera is not saved to the folders

1 – data from the thermal camera is saved to the folders

ForceProcessWholeImage

The key is used in case the Combined work with thermal camera and Get photo from thermal camera checkboxes are set on the settings panel of the Face Recognition Server object.

Enables the face search throughout the entire frame if a face was not previously recognized due to incorrect coordinates of the face frame received from the thermal camera.

Details on this mode:

• The number of recognitions and the system load will increase.
• The negative face images will be displayed in the Face recognition and search interface module.
• The same temperature will be indicated for all recognized faces in the frame.

0 – Unrecognized faces are ignored.

1 – Enables the face search throughout the entire frame if a face was not previously recognized.

Update.CpuCoreCount

Sets the number of threads on which the biometric vectors are re-generated when switching between different face recognition modules or SDK versions.

Auto PSIM

Registry section

Available values

Default

Product version

Parameter in effect

x32: (x32)\LPRVIEWER
x64: (x64)\LPRVIEWER

protocollimit

<1000

NA

1.0.0 and later

Sets number of lines shown in the protocol (this parameter is for testing only).

x32: (x32)\radar
x64: (x64)\radar

EmulateRefreshSpeed

1 – 2147483647

100

1.0.0 and later

Radar emulator. Sets time period (ms) for refreshing data about speed in the radar emulation mode. 0 value blocks data refreshing.

x32: (x32)\radar
x64: (x64)\radar

WriteSpeedOnTitles

0, 1

0

1.0.0 and later

Defines whether to write speed values on titles.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

DisableUrmOutput

0, 1

0

1.0.0 and later

Disables results output.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

GlobalUrmDebug

0, 1

0

1.0.0 and later

Enables displaying CZoneInfo objects in dbgview. 

x32: (x32)\URMLPR
x64: (x64)\URMLPR

OneSpeedDetect

0, 1

0

1.0.0 and later

Enables filtering the radar speed values.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

ReadSpeedFromTitles

0, 1

0

1.0.0 and later

Defines whether to read speed from titles or not.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

TestWidth

NA

0

1.0.0 and later

 Image width change (internal use only).

x32: (x32)\URMLPR
x64: (x64)\URMLPR

TestHeight

NA

0

1.0.0 and later

 Image height change (internal use only).

x32: (x32)\URMLPR
x64: (x64)\URMLPR

Time

NA

NA

1.0.0 and later

Saves time of the last viewed archive fragment in the test mode.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

UrmDebug

0, 1

0

1.0.0 and later

Enables recording of  tiff files to UrmDebug folder.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

UrmSendProcessEvents

0, 1

0

1.0.0 and later

Sends beginning (VEHICLES_BEGIN) and ending (VEHICLES_END) parameters of license plate recognition to the core.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

UseTry

0, 1

0

1.0.0 and later

Enables the seh module.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

WriteUraganErrorBuf

0, 1

0

1.0.0 and later

If failure occurs, the uragan.buf file is created (only of UseTry=1). 

x32: (x32)\URMLPR\UnitTest
x64: (x64)\URMLPR\UnitTest

CountryName

Text

RUS

1.0.0 and later

Sets the test country name.

x32: (x32)\URMLPR\UnitTest
x64: (x64)\URMLPR\UnitTest

Enabled

0, 1

0

1.0.0 and later

Enables/disables test.

x32: (x32)\URMLPR\UnitTest
x64: (x64)\URMLPR\UnitTest

ExecuteSecond

> = 0

3

1.0.0 and later

Sets time of test execution.

x32: (x32)\URMLPR\UnitTest
x64: (x64)\URMLPR\UnitTest

Number

Text

M038EH150

1.0.0 and later

Sets the test number.

x32: (x32)\URMLPR\UnitTest
x64: (x64)\URMLPR\UnitTest

PlateHeightPercent

> 0

15

1.0.0 and later

Sets the test license plate height.

x32: (x32)\URMLPR\UnitTest
x64: (x64)\URMLPR\UnitTest

PlateWidthPercent

> 0

25

Sets the test license plate width.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

ParkingMode

0, 1

NA

1.0.0 and later

Enabling the parking mode for the CARMEN-Auto recognizer:

1 – parking mode is enabled. Recognition starts at ULPR|START reaction. As soon as one license plate is recognized, the recognition stops.

0 – parking mode is disabled. Recognition continues till getting the ULPR|STOP reaction. 

Important! For correct operation of the key make sure that the Enable on motion detection trigger checkbox is set on the settings panel of the LPR channel object corresponding to the CARMEN-parking recognition module (see Setting the joint operation of the LPR channel and the motion detector of the Axxon PSIM platform).

Note. The ULPR|START and ULPR|STOP reactions are created using the scripts. Operator command, sensor triggering, motion detection tool triggering, etc. can cause the reaction.

Enabling the parking mode for the CARMEN-Auto recognizer:

1 – parking mode is enabled. Recognition starts at ULPR|START reaction. As soon as one license plate is recognized, the recognition stops.

0 – parking mode is disabled. Recognition continues till getting the ULPR|STOP reaction. 

Note. If you set the 1 value on the settings panel of the LPR channel object, the Enable on motion detection trigge checkbox will be automatically set without the possibility of removing it until this key value is set to 0 (see Setting the joint operation of the LPR channel and the motion detector of the Axxon PSIM platform).

Note. The ULPR|START and ULPR|STOP reactions are created using the scripts. Operator command, sensor triggering, motion detection tool triggering, etc. can cause the reaction.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

When value = 1, the key allows saving frames transmitted from Axxon PSIM to the CARMEN Parking / CARMEN-Auto module.

• For CARMEN Parking the frames are saved to the following folders:
  < Axxon PSIM installation folder>\Modules64\UrmLpr\CPD_RawResults\idDetector\ – frames with data for recognition.
  <Axxon PSIM installation folder >\Modules64\UrmLpr\CPD_RawResults\idDetector\NotFound – frames with no data for recognition.If value = 0, then frames are not saved.

• For CARMEN Auto the results are stored to the <Axxon PSIM>\Modules64\UrmLpr\CarmenResults\idDetector\ folder. The results are represented by pairs of files: ‘<recognition time in UTC format>.bmp’ file (with a frame to be recognized) and xml file with settings of the recognizer and recognition results.

• If the module is restarted, the Apply button is clicked or 5000 files are saved, then the specified folder and the data in it are automatically deleted and the folder is recreated. 

When value = 1, frames are not saved.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

x32: (x32)\URMLPR
x64: (x64)\URMLPR

x32: (x32)\URMLPR
x64: (x64)\URMLPR

Sets time (in milliseconds) corresponding to the delay with which events about green/red traffic lights are received.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

x32: (x32)\URMLPR
x64: (x64)\URMLPR

TimestampFontSize.N

Note. N is the number of license plate recognition channel in Axxon PSIM

x32: (x32)\URMLPR
x64: (x64)\URMLPR

FontSize

x32: (x32)\URMLPR
x64: (x64)\URMLPR

FontSize.N

Note. N is the number of license plate recognition channel in Axxon PSIM

x32: (x32)\URMLPR
x64: (x64)\URMLPR

The key sets an algorithm of frame preparation before sending it to the Carmen license plate recognition module:

0 – frames are sent to the Carmen license plate recognition module without pre-processing.

1 – rectangular areas that may contain a license plate are searched in the frame. Only those rectangular areas that may contain a license plate are then forwarded to the Carmen license plate recognition module.

2 – if any rectangular area that may contain a plate number is detected on the frame, the frame in whole is forwarded to the Carmen license plate recognition module. If the Carmen license plate recognition module detects a license plate, it tries to find another plate number, and time for recognition increases as a result.

3 – if any rectangular area that may contain a plate number is detected on the frame, the frame in whole is forwarded to the Carmen license plate recognition module. If the Carmen license plate recognition module detects a license plate, it does not try to find another license plate.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

"FASTEST" – a speed trap sends speed of the fastest object to the Axxon PSIM software

"STRONGEST" – a speed trap sends speed of the biggest object to the Axxon PSIM software

Important! If values other than above are specified for the key, the Axxon PSIM software does not recieve speed data from speed traps.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

x32: (x32)\URMLPR
x64: (x64)\URMLPR

The key specifies the time difference (in milliseconds) between the moments of receiving the frame and license plate recognition event, sufficient to allow these events to be linked. The key is to be in use if data about recognized license plates are not displayed on the On-line monitor in Auto PSIM, although there are recognition events in the Debug window.

RemoteLpr.x.NearestTime

X is the object identifier of the LP recognition channel in the Axxon PSIM software.

>=0

For the specified object of the LPR channel with the assigned remote recognition module, the key sets the time difference in milliseconds between the moments of receiving the frame and event on the LP recognition enough to bind these events. You should use the key if the data on the recognized LPs are not displayed in the Active Monitor of the Auto PSIM although they are found in the Debug window and Event protocol.

Specifies the way of storing images.

0 – metadata and images are stored only in the database.

1 – metadata is stored in the database, and images are stored in the local or network folder. Full path to the folder is specified by the LprDB.Path key (see above).

Note. Recognized LP numbers information is stored in the database regardless of the LprDB.Use key.

Specifies the amount of free storage space in a directory. When its limit is exceeded, the overwriting process starts, rewriting the oldest images with the most recent ones. The key is used if the LprDB.Use key value is 1 (see above).

The parameter allows ignoring all the tracks after the best frame detected by SDK.

0 – tracks after the best frame detected by SDK are not ignored.

1 – all the tracks after the best frame detected by SDK are ignored.

The parameter activates alarm even if only one plate is recognized at the crosswalk (regardless of if the vehicle was moving or not).

0 – the system tries to detect crossing the crosswalk and only after that activates alarm.

1 – activates alarm even if only one plate is recognized at the crosswalk.

Activates saving the recognition results to the hard drive. It is used for the Traffic violations detection module debugging.

0 – the recognition results are saved to the Auto PSIM DB.

1 – the recognition results are saved to the hard drive.

The key sets the SDK version which is being used in the Auto-Uragan software module.

Note. It is applied to all activated Auto-URAGAN software modules in Auto PSIM.

The key activates the LP numbers recognition simultaneously on several CPUs using parallel computing, which increases the performance of the Auto-URAGAN software module.

Note. It is applied to all activated Auto-URAGAN software modules in Auto PSIM.

The key sets the number of CPUs that will be used for parallel computing by the Auto-URAGAN software module, if the parallel computing is activated.

Note. It is applied to all activated Auto-URAGAN software modules in Auto PSIM.

The key enables the tracking of the recognized number disappearance and sets the time in milliseconds, after which the lost number event will be generated if this number has disappeared from the camera field of view.

0 – tracking of the recognized number disappearance is disabled.

>1 – after the specified time has passed, if the recognized number disappeared from the camera field of view, a lost number event will be generated.

The key enables saving the filtered numbers to the database.

0 – filtered numbers are saved to the database.

1 – filtered numbers are not saved to the database.

The key activates the display of two-line numbers in the Event Log in two lines.

0 – two-line numbers are displayed in two lines.

1 – two-line numbers are displayed in one line.

The key sets the time in minutes, after which the violation detected by the main recognizer is ignored if the second recognizer, which is paired with the main one, also detected a violation.

The key activates the automatic restart by the timeout for the Auto-URAGAN recognition module if no recognition results are received from it.

The key disables the receiving of photos from the main cameras of the recognizers.

The key sets the number of frames that are stored in the buffer for the CARMEN-Auto module. It is applicable if there is skipping of numbers, but it may cause a delay in the numbers recognition.

The key sets the number of unprocessed frames that are stored in the buffer for all license plate recognition modules. It is applicable if there is skipping of numbers, but it may cause a delay in the numbers recognition.

The key activates the saving of the number recognition result in the * .jpg format for the VIT module. As a result of the module operation, the AutoRecongitionResult folder will be created at the path: <Axxon PSIM installation directory>\Modules64\UrmLpr\, into which the files with the following names will be saved: recognizer ID in Axxon PSIM – recognized number – violation <if any>.jpg.

Note. This setting is required for debugging.

The key sets the mode of determining the vehicle direction of movement of the vehicle.

0 – the direction is determined by the SDK.
1 – the direction is calculated by the position of the upper part of the number. If at the start of tracking the upper part of the number is lower than the upper part of the number at the end of tracking, then the direction is defined as “From the camera”, otherwise “To the camera”.
2 – the direction is calculated by the area of the LP number. If at the start of tracking the area of the number is larger than at the end of tracking, then the direction is defined as “From the camera”, otherwise “To the camera”.

The key sets the waiting time in seconds required for the number to appear if the vehicle is detected several times after stopping.

The key activates the discarding of all tracks after the best frame which was defined by the recognition module.

The key activates an alarm if there is at least one number identification at the pedestrian crossing. Vehicle traffic is not taken into account.

Note. By default, the system tries to determine the traffic on a pedestrian crossing.

The key enables the entry of an Arabic LP number in the search field.

It is necessary to activate this key if the Persian calendar is used on the LPR channel.

Internal setting. Disables saving of frames from a synchronous video camera to the LprDB.Path folder and the [lprex].[dbo].[FramesSecondary] database.

0 – saving of all images from a synchronous video camera is disabled.

1 – saving of all images from a synchronous video camera is enabled.

Ulpr.NumberDetectedRestartTimeout

This key should be created if the LP recognition on one or more LPR channels stop from time to time. The key sets the time in minutes; if during this time no LPs were recognized, then the reaction is sent to the Axxon PSIM software core:

ULPR|N|NUMBER_DETECTED_TIMEOUT

where N is the identifier of the LPR channel object. Having received this reaction, the core re-sends the settings to the recognition module, thus emulating the Apply button click on the settings panel of the LPR channel object.

AutoInfo.Use

The key automatically enables the display of the vehicle type in the Online Monitor window if the Vehicle Type Recognition Module (UrlServer) is activated.

0 – the detected vehicle type is not displayed in the Online Monitor window.

1 – the detected vehicle type is displayed in the Online Monitor window.

Note. The key value changes automatically.

AutoInfo.Url

http-address

http://127.0.0.1:8091/GetAutoInfo

The key sets the http-address for the interaction with the Vehicle Type Recognition Module (UrlServer).

The key sets the number of frames that are stored in the buffer for the Vehicle Type Recognition Module (UrlServer). It is defined as the approximate time spent by the vehicle in the frame multiplied by the fps of video.

If 0 – then the MMR (VIT) works.

If < 0 – then the Vehicle Type Recognition Module (UrlServer) works with the 350 value.

If > 0 – then the Vehicle Type Recognition Module (UrlServer) works with the specified value.

The key specifies the folder into which the frames processed by the Vehicle Type Recognition Module (UrlServer) will be saved (cropped frames containing only the vehicle). These frames are necessary for training a neural network (see Saving the frames processed by the Vehicle Type Recognition module).

VehiclePlateSearch.RightToLeft

When using the CARMEN-Auto software module and the Arabic license plate numbers recognizer, the key sets the sequence of Latin numbers and letters in the second line of the recognized LP number displayed in the Online monitor.

0 – Latin numbers are displayed first, then letters.

1 – Latin letters are displayed first, then numbers.

The key works only if saving the frames processed by the Vehicle Type Recognition module (UrlServer) is enabled. 

The key value indicates the coefficient by which the number plate width will be multiplied. The photo will be cropped from the left relative to the number plate at a distance equal to the product.

The key works only if saving the frames processed by the Vehicle Type Recognition module (UrlServer) is enabled. 

The key value indicates the coefficient by which the number plate width will be multiplied. The photo will be cropped from the right of the number plate at a distance equal to the product.

The key works only if saving the frames processed by the Vehicle Type Recognition module (UrlServer) is enabled. 

The key value indicates the coefficient by which the number plate height will be multiplied. The photo will be cropped from the top relative to the number plate at a distance equal to the product.

The key works only if saving the frames processed by the Vehicle Type Recognition module (UrlServer) is enabled. 

The key value indicates the coefficient by which the number plate height will be multiplied. The photo will be cropped from the bottom relative to the number plate at a distance equal to the product.

The key allows you to send a message about the number, even if the frame dimensions, which are necessary for the correct calculation of the number plate coordinates, are not initialized. This solves the problem of incorrect linking of numbers when sending the number plate coordinates.

0 – a message about the number is not sent if the frame dimensions are not initialized.

1 – a message about the number is sent even if the frame dimensions are not initialized.

Sets the timeout in seconds for connecting to the selected Auto PSIM servers when the Event search in the Recognizers DBs window is opened. If the specified time is exceeded, connection attempts are stopped and a list of servers to which it was not possible to connect is displayed.

LprDB.Log

Enables recording of LP recognition logs to the Logs table of the lprex DB. The records in the table are cleared according to the specified records retention period in the database. Used for debugging.

The key is used if the standard port 10001 used by the LPR channel for communication with the Vehicle Tracer module client is occupied by a third-party application that cannot be disabled. The key allows you to set a new port number for communication between the server and client parts.

The key is used to control the number of events to be deleted from the Auto PSIM internal database.

0—all records that exceed the specified amount of archive storage will be deleted from the database.

1—a maximum of 1000 records will be deleted from the database with a 3-minute timeout.

The key displays the data file about the triggered engine in the Online monitor window.

0—the data file is not displayed.

1—the data file is displayed

0

The key compensates for automatic scrolling when the element is added to the Online monitor window:

0—automatic scrolling is compensated, this key value is used for all versions of Windows OS except 8 with the installed package KV4486105.

1—automatic scrolling is not compensated, this key value is used for Windows OS version 8 with the installed package KV4486105.

The key value depends on the installed version of Windows OS

The key specifies the time in seconds, during which the repeated license plate recognitions on all channels within one physical server are ignored

The key enables the mode of evenly distributing the load on the CPU cores.0—the mode

0—the mode of evenly distributing the load on the CPU cores isn't enabled, all recognition channels are started in one process

1—the mode of evenly distributing the load on the CPU cores is enabled, each recognition channel is started in a separate process

The key adds to the NUMBER_DETECTED event the image parameter that stores the image of the entire frame, and the image_plate parameter that stores the image of the cropped frame, encoded using Base64:

 0—the NUMBER_DETECTED event is generated without the image and image_plate parameters

1—the NUMBER_DETECTED event is generated with the image and image_plate parameters

The key enables the event search in the recognizer databases, if the Server/Remote Administrator’s workstation and Remote Client configuration is used.

0—recognizers aren’t displayed, search doesn’t work

1—recognizers are displayed, search works

The key enables the event search in the recognizer databases, if the Server/Remote Administrator’s workstation and Remote Client configuration is used.

0—recognizers aren’t displayed, search doesn’t work

1—recognizers are displayed, search works

The key defines the composition of the titles (frame captions) that will be displayed in the online monitor, when printing the LP number, and in the frame caption. The titles are specified in the format "date_and_time, number, country, speed, direction, allowed_speed, device_number, place_control, gps, type, make, model, color" insensitive to case, spaces between elements are optional. If the field is empty, it will not be added to the caption. Elements can be deleted and rearranged.

date_and_time—"Date and time of receiving the vehicle data - %s"
number—"Vehicle license plate - %s"
country—"Country - %s"
speed—"Vehicle speed - %s km/h"
direction—"Vehicle direction - %s"
allowed_speed—"Speed, permitted on the controlled road area - %s km/h"
device_number—"ID of speed detector - %s"
place_control—"Control point—name of the camera that captured the vehicle - %s"
gps—"GPS coordinates - %s"
type—"Type of license plate - %s "
make—"Vehicle vendor - %s "
model—"Vehicle model - %s "
color—"Vehicle color - %s ",
where %s is a string. 

The size of the black area and the font size of the caption are adjusted using the keys FontSize = 22 and TimestampFontSize = 130 respectively. If the string does not fit or a large font size (TimestampFontSize) is specified, the text will automatically wrap to the second line. In this case, it is necessary to increase the value of the FontSize parameter

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

ArchiveFps

1-24

1.0.0 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: (X32x32)\Video
x64: (x64)\Video

DoubleStream

0, 1

1.0.0 and later

Defines whether asynchronous video display mode is enabled or not.

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

IpIntDrivers3

Brand name: Axis; Acti, etc.

1.0.0 and later

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

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

IpIntDriverVersion

2, 3

1.0.0 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

1.0.0 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

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

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 the RTSP Server module.

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

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

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.

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

The key is used to enable the compatibility between presets in Axxon PSIM 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 Axxon One is in use in Axxon PSIM. If preset 1 is selected in Axxon PSIM interface, then value 1 is sent to the driver.

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

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.

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

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.

enable

disable

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

<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

DP 1.0.0

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 Axxon PSIM 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 Axxon PSIM 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 Axxon PSIM.

InfrequentTs value discards the relative timestamps, transferring 0 to the Axxon PSIM 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.

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.

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.

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.

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.

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.

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

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

DP 1.0.0 and later

Compatibility: Axxon PSIM 1.0.0 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.

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

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\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_COUNTER_TVN

x64: (x64)\DetectorExt\CROWD_COUNTER_TVN

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: (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)