Go to documentation repository
...
| Section | |||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Auto PSIM | |||||
Registry section | String parameter | Available values | Default | Product version | Parameter in effect |
x32: (x32)\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 | 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 | WriteSpeedOnTitles | 0, 1 | 0 | 1.0.0 and later | Defines whether to write speed values on titles. |
x32: (x32)\URMLPR | DisableUrmOutput | 0, 1 | 0 | 1.0.0 and later | Disables results output. |
x32: (x32)\URMLPR | GlobalUrmDebug | 0, 1 | 0 | 1.0.0 and later | Enables displaying CZoneInfo objects in dbgview. |
x32: (x32)\URMLPR | OneSpeedDetect | 0, 1 | 0 | 1.0.0 and later | Enables filtering the radar speed values. |
x32: (x32)\URMLPR | ReadSpeedFromTitles | 0, 1 | 0 | 1.0.0 and later | Defines whether to read speed from titles or not. |
x32: (x32)\URMLPR | TestWidth | NA | 0 | 1.0.0 and later | Image width change (internal use only). |
x32: (x32)\URMLPR | TestHeight | NA | 0 | 1.0.0 and later | Image height change (internal use only). |
x32: (x32)\URMLPR | Time | NA | NA | 1.0.0 and later | Saves time of the last viewed archive fragment in the test mode. |
x32: (x32)\URMLPR | UrmDebug | 0, 1 | 0 | 1.0.0 and later | Enables recording of tiff files to UrmDebug folder. |
x32: (x32)\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 | UseTry | 0, 1 | 0 | 1.0.0 and later | Enables the seh module. |
x32: (x32)\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 | CountryName | Text | RUS | 1.0.0 and later | Sets the test country name. |
x32: (x32)\URMLPR\UnitTest | Enabled | 0, 1 | 0 | 1.0.0 and later | Enables/disables test. |
x32: (x32)\URMLPR\UnitTest | ExecuteSecond | > = 0 | 3 | 1.0.0 and later | Sets time of test execution. |
x32: (x32)\URMLPR\UnitTest | Number | Text | M038EH150 | 1.0.0 and later | Sets the test number. |
x32: (x32)\URMLPR\UnitTest | PlateHeightPercent | > 0 | 15 | 1.0.0 and later | Sets the test license plate height. |
x32: (x32)\URMLPR\UnitTest | PlateWidthPercent | > 0 | 25 | 1.0.0 and later | Sets the test license plate width. |
x32: (x32)\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. |
| 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. 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 | SaveRawRecognitionResult | 0,1 | 0 | 1.0.0 and later | When value = 1, the key allows saving frames transmitted from Axxon PSIM to the CARMEN Parking / CARMEN-Auto module.
When value = 1, frames are not saved. |
x32: (x32)\URMLPR | TrackOnlyRedLight | 0, 1 | 1 | 1.0.0 and later | When value = 1, the key allows fixing violations by the traffic violations detection (crossing the stop line, stop over crosswalk line, running a red light) only for vehicles which crossed the stop line on red light. |
x32: (x32)\URMLPR | MaxStoppingSpeed | 0 – 10000 | 1000 | 1.0.0 and later | Controls maximal speed in relative units (relatively from width and height of frame) at which the vehicle is still considered as the stopped vehicle (for the Stop over crosswalk line violation). |
x32: (x32)\URMLPR | RayHardwareDelay | >0 | 0 | 1.0.0 and later | Sets time (in milliseconds) corresponding to the delay with which events about green/red traffic lights are received. Example. If the key value is RayHardwareDelay=2000 and an event is received at 12:00:00, then the system thinks the event is received at 11:59:58. |
x32: (x32)\URMLPR | TimestampFontSize | >0 | 130 | 1.0.0 and later | The key sets the font size of the caption on the vehicle photo containing date and time. The value of the key is font size multiplied by 10. For example, if the key is 139, then the font size will be 13,9pnt. |
x32: (x32)\URMLPR | TimestampFontSize.N Note. N is the number of license plate recognition channel in Axxon PSIM | >0 | 130 | 1.0.0 and later | The key sets the font size of the caption on the vehicle photo containing date and time. The value of the key is font size multiplied by 10. For example, if the key is 139, then the font size will be 13,9pnt. The key is created in the registry after the recognition channel is created, it is different for each channel. |
x32: (x32)\URMLPR | FontSize | >0 | 22 | 1.0.0 and later | The key determines the width of the black area for the caption on the vehicle photo containing date and time, measured in pixels. |
x32: (x32)\URMLPR | FontSize.N Note. N is the number of license plate recognition channel in Axxon PSIM | >0 | 22 | 1.0.0 and later | The key determines the width of the black area for the caption on the vehicle photo containing date and time, measured in pixels. The key is created in the registry after the recognition channel is created, it is different for each channel. |
x32: (x32)\URMLPR | PlateImprover | 0, 1, 2, 3 | 0 | 1.0.0 and later | 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 | SpeedField | "FASTEST", "STRONGEST" | "FASTEST" | 1.0.0 and later | "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 | Compress | 0, 1 | 1 | 1.0.0 and later | The parameter is intended for disabling compression when transferring video from the video subsystem (the Camera object) to the LPR channel, if the video subsystem and the LPR channel are on the same local computer. This allows reducing the load on the Server processor. 0 – the video is transmitted to the local LPR channel without compression. 1 – the video is transmitted to the LPR channel after compression. |
x32: (x32)\URMLPR | RemoteLpr.NearestTime | >=0 | 0 | 1.0.0 and later | 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. |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | RemoteLpr.x.NearestTime X is the object identifier of the LP recognition channel in the Axxon PSIM software. | >=0 | NA | 1.0.0 and later | 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. |
| x32: (x32)\URMLPR x64:(x64)\URMLPR | LprDB.Path | 0, 1 | C:\ProgramData\AxxonSoft\LprDB | 1.0.0 and later | Specifies the local or network folder for storing the recognized LP images and vehicle images if the LprDB.Use key value 1 (see below) is specified. |
| x32: (x32)\URMLPR x64:(x64)\URMLPR | LprDB.Use | 0, 1 | 1 | 1.0.0 and later | 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. |
| x32: (x32)\URMLPR x64:(x64)\URMLPR | LprDB.FreeMB | >0 | 5000 | 1.0.0 and later | 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). |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | Alarms.LimitedByBestResult | 0, 1 | 0 | 1.0.0 and later | 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. |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | Alarms.CrossWalkOne | 0, 1 | 0 | 1.0.0 and later | 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. |
| x32: (x32)\URMLPR x64:(x64)\URMLPR | SaveRecognitionResult | 0, 1 | 0 | 1.0.0 and later | 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. |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | AutoUragan.SDKVersion | 3.8, 3.7, 3.5 | 3.8 | 1.0.0 and later | 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. |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | AutoUragan.Parallel | 0, 1 | 0 | 1.0.0 and later | 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. |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | AutoUragan.Kernels | >=1 | 1 | 1.0.0 and later | 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. |
| x32: (x32)\URMLPR x64:(x64)\URMLPR | VIT.TimeoutLostNumber | >=0 | 0 | 1.0.0 and later | 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. |
| x32: (x32)\URMLPR x64:(x64)\URMLPR | SaveFilterToDB | 0, 1 | 1 | 1.0.0 and later | 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. |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | RemoveNewLine | 0, 1 | 1 | 1.0.0 and later | 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. |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | ExpiredPlateNumberMinutes | >=0 | 5 | 1.0.0 and later | 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. |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | RestartTimeout | 0, 1 | 0 | 1.0.0 and later | The key activates the automatic restart by the timeout for the Auto-URAGAN recognition module if no recognition results are received from it. |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | IgnorePhotoFromBaseCamera | 0, 1 | 0 | 1.0.0 and later | The key disables the receiving of photos from the main cameras of the recognizers. |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | FrameBuffer | >=0 | 0 | 1.0.0 and later | 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. |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | FrameBuffer | >=0 | 0 | 1.0.0 and later | 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. |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | SaveRecognitionResult | 0, 1 | 0 | 1.0.0 and later | 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. |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | InternalDirection | 0, 1, 2 | 1 | 1.0.0 and later | The key sets the mode of determining the vehicle direction of movement of the vehicle. 0 – the direction is determined by the SDK. |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | GueTrack.Timeout | >=0 | 0 | 1.0.0 and later | The key sets the waiting time in seconds required for the number to appear if the vehicle is detected several times after stopping. |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | Alarms.LimitedByBestResult | 0, 1 | 0 | 1.0.0 and later | The key activates the discarding of all tracks after the best frame which was defined by the recognition module. |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | Alarms.CrossWalkOne | 0, 1 | 0 | 1.0.0 and later | 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. |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | VehiclePlateSearch.Arabic | 0, 1 | 0 | 1.0.0 and later | The key enables the entry of an Arabic LP number in the search field. |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | VehiclePlateSearch.PersianCalendar | 0, 1 | 0 | 1.0.0 and later | It is necessary to activate this key if the Persian calendar is used on the LPR channel. |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | WritesAllSecondaryFrames | 0, 1 | 1 | 1.0.0 and later | 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. |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | Ulpr.NumberDetectedRestartTimeout | >=0 | 0 | 1.0.0 and later | 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. |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | AutoInfo.Use | 0, 1 | 0 | 1.0.0 and later | 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. |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | AutoInfo.Url | http-address | http://127.0.0.1:8091/GetAutoInfo | 1.0.0 and later | The key sets the http-address for the interaction with the Vehicle Type Recognition Module (UrlServer). |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | UrlServerFrameBuffer | Whole numbers | -1 | 1.0.0 and later | 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. |
| x32: (x32)\URL_SERVER x64: (x64)\URL_SERVER | SavePictures | String value | NA | 1.0.0 and later | 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). |
| x32: (x32)\URL_SERVER x64: (x64)\URL_SERVER | VehiclePlateSearch.RightToLeft | 0, 1 | 1 | 1.0.0 and later | 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. |
| x32: (x32)\URL_SERVER x64: (x64)\URL_SERVER | DeferLeft | >0 | 2.0 | 1.0.0 and later | 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. |
| x32: (x32)\URL_SERVER x64: (x64)\URL_SERVER | DeferRight | >0 | 2.0 | 1.0.0 and later | 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. |
| x32: (x32)\URL_SERVER x64: (x64)\URL_SERVER | DeferUp | >0 | 21.8 | 1.0.0 and later | 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. |
| x32: (x32)\URL_SERVER x64: (x64)\URL_SERVER | DeferDown | >0 | 3.8 | 1.0.0 and later | 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. |
| x32: (x32)\Video x64: (x64)\Video | RandomOrder | 0, 1 | 0 | 1.0.0 and later | 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. |
| x32: (x32)\URL_SERVER\An x64: (x64)\URL_SERVER\An | An.port | >0 | 20111 | 1.0.0 and later | Sets the port for connection to Axxon One (see Setting up the joint operation of Auto PSIM and Axxon One). |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | VehiclePlateSearch.ConnectTimeOut | >=0 | 10 | 1.0.0 and later | 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. |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | LprDB.Log | 0, 1 | 0 | 1.0.0 and later | 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. |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | RestPort | port number | 10001 | 1.0.0 and later | 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. |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | ClearOnlyFirstPageDB | 0, 1 | 1 | 1.0.0 and later | 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. |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | VehicleTracer.ShowDataFile | 0, 1 | 0 | 1.0.0 and later | 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 |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | VehicleTracer.DisableAutoScrollLineUp | 0, 1 | 0 | 1.0.0 and later | 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 |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | Carmen.DistanceX | >=0 | 10 | 1.0.0 and later | The key is the minimum horizontal distance in pixels between the license plate characters. The key is used to insert a separator into the license plate. The separator will be added where the distance between the characters is maximum and at the same time it is not less than the value specified in the key. The key is only used for Arabic license plate numbers |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | Carmen.ExcludeCountriesSpace | country codes separated by a comma | none | 1.0.0 and later | The key defines the countries for which special characters won’t be displayed during license plate recognition. Country codes are specified separated by a comma in ISO 3166 Alpha-3 format, case-insensitive, e.g. VAT,ARE for Vatican, UAE |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | IgnoreRepeatTime | >=0 | 0 | 1.0.0 and later | The key specifies the time in seconds, during which the repeated license plate recognitions on all channels within one physical server are ignored |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | IsProcessObject | 0, 1 | 0 | 1.0.0 and later | The key enables the mode of evenly distributing the load on the CPU cores. 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 |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | PicturesInNumberDetectedEvent | 0, 1 | 0 | 1.0.0 and later | 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 |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | VehiclePlateSearch.UseRestIp | 0, 1 | 0 | 1.0.0 and later | 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 |
| x32: (x32)\URMLPR x64: (x64)\URMLPR | TitleFields | Title elements (frame captions), separated by commas | N/A | 1.0.0 and later | 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" 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 |
Registry section
String parameter
Available values
Default
Product version
Parameter in effect
POS PSIM | |||||
|---|---|---|---|---|---|
Registry section | String parameter | Available values | Default | Product version | Parameter in effect |
x32: (x32)\POS | Capture | 0, 1 | 1 | 1.0.0 and later | Defines whether to store log-files or not. |
x32: (x32)\POS | Dos2Win | 0, 1 | 1 | 1.0.0 and later | Detects encoding: |
x32: (x32)\POS | GlobalTextDelay | NA | 0 | 1.0.0 and later | Sets the shift of Text data from video to TextSearch. |
x32: (x32)\POS | Nohotkey | 0, 1 | 1 | 1.0.0 and later | Allows disabling hot keys used for POSVIEWER and TITLEVIEWER. If Nohotkey = 1, then when clicking |
| x32:(x32)\POS x64:(x64)\POS | DecodeUtf8 | 0, 1 | 0 | 1.0.0 and later | The key enables the UTF-8 encoding to ensure the correct display of captions in cases when the incoming to the POS terminal packages have the UTF-8 encoding. |
x32: (x32)\POS | PosLogMaxsize | >0 | 10 | 1.0.0 and later | The key sets maximum size (in MBs) of the POS terminal’s log. Note. POS terminal logging is enabled using the Capture key – see above. |
| x32: (x32)\POS x64: (x64)\POS | SetFlowControlNone | 0, 1 | 1 | 1.0.0 and later | COM port control. Set to 0 if POS terminal fails to operate while connecting to POS PSIM. |
| x32:(x32)\POS x64:(x64)\POS | UseLocalTimestamp | 0, 1 | 0 | 1.0.0 and later | The key enables the received local timestamp conversion to UTC when creating a record in the corresponding POS PSIM database. 0 – received local timestamp will be recorded to the corresponding database without any changes. 1 – received local timestamp will be converted to UTC when creating a record in the corresponding database. |
| x32:(x32)\POS x64:(x64)\POS | UseLastCashierInfo | 0, 1 | 0 | 1.0.0 and later | In case the D-store POS-terminals are used, the key enables saving the info about the last cashier whose data was received by the POS-terminal. Until there is no data, the following default values are used: cashier_name = "Jane B."; cashier_number = "1147911"; 0 – the info about the last cashier whose data was received by the POS-terminal, is not saved. 1 – the info about the last cashier whose data was received by the POS-terminal, is saved. |
| x32:(x32)\POS x64:(x64)\POS | NewReceipt.Use | 0, 1 | 0 | 1.0.0 and later | In case the D-store POS-terminals are used, the key enables initiating the receipt creation by any data input. In addition to that, the text line specified in the NewReceipt.Word key (see below) is added to the receipt text. 0 – the receipt creation is initiated by the word specified to trigger the receipt creation. 1 – the receipt creation is initiated by any data input, and the text line specified in the NewReceipt.Word key (see below) is added to the receipt text. Note. This key works only if the UseLastCashierInfo key (see above) is enabled. |
| x32:(x32)\POS x64:(x64)\POS | NewReceipt.Word | String value | NEW RECEIPT | 1.0.0 and later | The key enables specifying the text line which will be added to the receipt text if the NewReceipt.Use key (see above) is enabled. |
| x32:(x32)\POS x64:(x64)\POS | PrintTime | 0, 1 | 0 | 1.0.0 and later | The key activates displaying in the Monitor the time (UTC) when each caption appeared. 0 – the captions timestamps (UTC) are not displayed in the Monitor. 1 – the captions timestamps (UTC) are displayed in the Monitor. |
| x32: (x32)\ |
| POS x64: (x64)\ |
| POS |
| WaitingBodys | 0, 1 |
| 0 | 1.0.0 and later | The key saves the beginning [PROLOG], middle [BODY], and end [EPILOG] of a receipt in the buffer and displays captions only after a receipt start event is received: 0—the beginning, middle, and end of a receipt aren't saved in the buffer; captions are displayed immediately 1—the beginning, middle, and end of a receipt are saved in the buffer; captions are displayed only after a receipt start event is received By default, the key isn't created, and its value is considered to be 0 |
IP integration (drivers and codecs pack for Axxon PSIM) | |||||||||||
Registry section | String parameter | Available values | Default | Product version | Parameter in effect | 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 | DoubleStream | 0, 1 | 1.0.0 and later | Defines whether asynchronous video display mode is enabled or not.|
x32: (x32)\Video | IpIntDrivers3 | ArchiveFps | 1-24Brand 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 listedSets the number of frames recorded to the archive (max.resolution). LiveFps and ArchiveFps parameters are not to exceed 24 in total. | ||||||
x32: (x32)\Video | IpIntDriverVersionDoubleStream | 20, 31 | 1.0.0 and later | Defines whether asynchronous video display mode is enabled or not. | |||||||
x32: (x32)\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: (x32)\Video | IpIntDriverVersion | 2, 3 | 1.0.0 and later | Defines the version number of loaded drivers the version number of loaded drivers: | |||||||
x32: (x32)\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) | 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. | ||||||
| x32: (x32)\Video\TransportProtocols x64: (x64)\Video\TransportProtocols | <Driver name> | <protocol> | NA | DP 1.0.0 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 Change 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 | 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). | NA | DP 1.0.0 and later | The 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 | >=0 | 60 | DP 1.0.0 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 | PresetCompatibility | 0, 1 | NA | DP 1.0.0 and later | 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. 1, or if the key is not created – the compatibility mode is in use: if preset 1 is selected/created in Axxon PSIM interface, then value 0 is sent to the driver. | ||||||
x32: (x32)\Video | FFTHREADCOUNT | >=0 | 1 | DP 1.0.0 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 | <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 data | DP 1.0.0 and later | 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:
| ||||||
| x32: (x32)\Video\UseSsrcChecking x64: (x64)\Video\UseSsrcChecking | RTSP | enable disable | enable | DP 1.0.0 and later | The key is intended for setting up synchronization source (SSRC) for RTSP stream: enable – SSRC check enabled; disable – SSRC check disabled. | ||||||
x32: (x32)\Video | FFLOGDELAY | 0, 1 | 0 | CP 1.580 | Enables 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>. |
| Depends on the brand | 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. | ||||||
| x32: (x32)\Video x64: (x64)\Video | MaxTimestampDeviation | >=0 | NA | DP 1.0.0 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 | ErrorSensitivity | 0, 1 | 0 | DP 1.0.0 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 | AudioSeparatedConnection | 0, 1 | 0 | DP 1.0.0 and later | Enables RTSP audio over a separate TCP connection. | ||||||
| x32: (x32)\Video x64: (x64)\Video | servicesVersion | auto, ver1, ver2 | auto | DP 1.0.0 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 | servicesSource | getServices, getCapabilities | getServices | DP 1.0.0 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 | playFileOnce | 0, 1 | 0 | DP 1.0.0 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 1.0.0 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 | DecompressorResetOnErrorTimeout | 0 – 180 | 60 | 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. | ||||||
| x32: (x32)\Video x64: (x64)\Video | IQS_ADDITIONTAL_VIDEO_FRAMES_COUNT | >=1 | 1 | DP 1.0.0 and later | The key sets the number of buffered decoded frames for the IntelQuickSync decoder. | ||||||
...
DetectorPack PSIM | |||||
|---|---|---|---|---|---|
Registry section | String parameter | Available values | Default | Product version | Description |
x32: (x32)\DetectorExt x64: (x64)\DetectorExt | MaxRestartsCount | >=1 | 1 | 1.0.0 and later | The key specifies the number of attempts to restart the detection tool in case of an internal error |
x32: (x32)\DetectorExt x64: (x64)\DetectorExt
| Recumbent.SkipSitPeople | 0, 1 | NA | 1.0.0 and later | 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
| Recumbent.SkipSitPeopleTimeOffset | >0 | 600 | 1.0.0 and later | 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
| Recumbent.SkipSitPeopleAreaOffset | >0 | 50 | 1.0.0 and later | 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 | ViDetectorDebug | 0, 1 | 0 | 1.0.0 and later | The key doesn't affect the operation of detectors. It serves to collect the information about the configuration of detectors, which simplifies debugging and testing. 0—the debug logging mode isn't enabled in the VI SDK, the VI detector configuration files aren't saved in the Modules64 folder. 1—the debug logging mode is enabled in the VI SDK, the VI detector configuration files are saved as two main and two additional files in the Modules64 folder when the filtration plugin is enabled. By default, the key isn't created, and its value is equal to 0 |
x32: (x32)\DetectorExt\BARCODE_DETECTOR x64: (x64)\DetectorExt\BARCODE_DETECTOR
| IsProcessObject | 0, 1 | 0 | 1.0.0 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 Barcode Detection: External Detector - BARCODE_DETECTOR.1 |
x32: (x32)\DetectorExt\BASE_POSE_DETECTOR x64: (x64)\DetectorExt\BASE_POSE_DETECTOR
| IsProcessObject | 0, 1 | 0 | 1.0.0 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 Pose Detection: External Detector - BASE_POSE_DETECTOR.1 |
x32: (x32)\DetectorExt\CONVEYOR_BELT_DETECTOR x64: (x64)\DetectorExt\CONVEYOR_BELT_DETECTOR
| IsProcessObject | 0, 1 | 0 | 1.0.0 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 Conveyor Belt Detection: External Detector - CONVEYOR_BELT_DETECTOR.1 |
x32: (x32)\DetectorExt\CROWD_COUNTER x64: (x64)\DetectorExt\CROWD_COUNTER
| IsProcessObject | 0, 1 | 0 | 1.0.0 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 Detection of moving against crowd flow: External Detector - CROWD_COUNTER.1 |
x32: (x32)\DetectorExt\CROWD_COUNTER_TVNESTIMATION x64: (x64)\DetectorExt\CROWD_COUNTER_TVNESTIMATION
| IsProcessObject | 0, 1 | 0 | 1.0.0 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 (TVNVA): External Detector -CROWD_COUNTER_TVNESTIMATION.1 |
x32: (x32)\DetectorExt\EQUIPMENT_DETECTOR x64: (x64)\DetectorExt\EQUIPMENT_DETECTOR
| IsProcessObject | 0, 1 | 0 | 1.0.0 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 Equipment detection (PPE): External Detector - EQUIPMENT_DETECTOR.1 |
x32: (x32)\DetectorExt\FIRE_DETECTOR x64: (x64)\DetectorExt\FIRE_DETECTOR
| IsProcessObject | 0, 1 | 0 | 1.0.0 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 Fire detection: External Detector - FIRE_DETECTOR.1 |
x32: (x32)\DetectorExt\FLUID_DETECTOR x64: (x64)\DetectorExt\FLUID_DETECTOR
| IsProcessObject | 0, 1 | 0 | 1.0.0 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 Fluid level detection: External Detector - FLUID_DETECTOR.1 |
x32: (x32)\DetectorExt\GLOW_DETECTOR x64: (x64)\DetectorExt\GLOW_DETECTOR
| IsProcessObject | 0, 1 | 0 | 1.0.0 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 Detection of light indication control: External Detector - GLOW_DETECTOR.1 |
x32: (x32)\DetectorExt\HEAT_ZONE_DETECTOR x64: (x64)\DetectorExt\HEAT_ZONE_DETECTOR
| IsProcessObject | 0, 1 | 0 | 1.0.0 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 Heat map detection: External Detector - HEAT_ZONE_DETECTOR.1 |
x32: (x32)\DetectorExt\HEAT_ZONE_DETECTOR x64: (x64)\DetectorExt\HEAT_ZONE_DETECTOR | ReportFrequency | >0 | 900 | 1.0.0 and later | Sets the data collection frequency (sec) for heat map detection tool |
x32: (x32)\DetectorExt\HEAT_ZONE_DETECTOR x64: (x64)\DetectorExt\HEAT_ZONE_DETECTOR | DebugReportFrequency | >0 | 10 | 1.0.0 and later | 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
| IsProcessObject | 0, 1 | 0 | 1.0.0 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 Neurocounter: External Detector - NEURO_COUNTER.1 |
x32: (x32)\DetectorExt\NEURO_TRACKER x64: (x64)\DetectorExt\NEURO_TRACKER
| IsProcessObject | 0, 1 | 0 | 1.0.0 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 Neurotracker: External Detector - NEURO_TRACKER.1 |
x32: (x32)\DetectorExt\NEURO_TRACKER\NEURO TRACKER_id x64: (x64)\DetectorExt\NEURO_TRACKER\NEURO TRACKER_id
| windowH windowStepH windowW windowStepW | nonnegative integer | absent | 1.0.0 and later | Sets the custom size of the scanning windows.
Example of custom settings for a 1920×1080 frame divided into four equal scanning windows: |
x32: (x32)\DetectorExt\OCCUPANCY_COUNTER x64: (x64)\DetectorExt\OCCUPANCY_COUNTER
| IsProcessObject | 0, 1 | 0 | 1.0.0 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 Queue length detection: External Detector - OCCUPANCY_COUNTER.1 |
x32: (x32)\DetectorExt\NEURO_COUNTER\NEURO COUNTER_id x64: (x64)\DetectorExt\NEURO_COUNTER\NEURO COUNTER_id
| windowH windowStepH windowW windowStepW | nonnegative integer | absent | 1.0.0 and later | Sets the custom size of the scanning windows.
Example of custom settings for a 1920×1080 frame divided into four equal scanning windows: |
x32: (x32)\DetectorExt\PEOPLE_COUNTER x64: (x64)\DetectorExt\PEOPLE_COUNTER
| IsProcessObject | 0, 1 | 0 | 1.0.0 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 People counter detection: External Detector - PEOPLE_COUNTER.1 |
x32: (x32)\DetectorExt\SMOKE_DETECTOR x64: (x64)\DetectorExt\SMOKE_DETECTOR
| IsProcessObject | 0, 1 | 0 | 1.0.0 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 Smoke detection: External Detector - SMOKE_DETECTOR.1 |
x32: (x32)\DetectorExt\STOPPED_CAR_DETECTOR x64: (x64)\DetectorExt\STOPPED_CAR_DETECTOR
| IsProcessObject | 0, 1 | 0 | 1.0.0 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 Stopped vehicle detection: External Detector - STOPPED_CAR_DETECTOR.1 |
x32: (x32)\DetectorExt\SWEETHEARTING_DETECTOR x64: (x64)\DetectorExt\SWEETHEARTING_DETECTOR
| IsProcessObject | 0, 1 | 0 | 1.0.0 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 Sweethearting at checkout detection: External Detector - SWEETHEARTING_DETECTOR.1 |
x32: (x32)\DetectorExt\TRAFFIC_LIGHTS x64: (x64)\DetectorExt\TRAFFIC_LIGHTS
| IsProcessObject | 0, 1 | 0 | 1.0.0 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 Traffic lights detection: External Detector - TRAFFIC_LIGHTS.1 |
x32: (x32)\DetectorExt\TRAIN_DETECTOR x64: (x64)\DetectorExt\TRAIN_DETECTOR
| IsProcessObject | 0, 1 | 0 | 1.0.0 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 Train detection: External Detector - TRAIN_DETECTOR.1 |
x32: (x32)\DetectorExt\VIDEO_INTELLECT_INTERNAL_DETECTOR x64: (x64)\DetectorExt\VIDEO_INTELLECT_INTERNAL_DETECTOR
| IsProcessObject | 0, 1 | 0 | 1.0.0 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 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 |
| x32: (x32)\Video\ x64: (x64)\Video\ | report_frequency | >=0 | 3000 | 1.0.0 and later | Sets the time period in milliseconds, during which the repeated triggering of the Sweethearting detection module is ignored |
| x32: (x32)\ x64: (x64)\ | ShowVideoIntellectObjects | ><=0 | NA | 1.0.0 and later | Hides the VideoIntellect detector objects from the Axxon PSIM objects tree. 0—the VideoIntellect detector objects are hidden ><0—VideoIntellect detector objects are displayed |
| x32: (x32)\Video x64: (x64)\Video | LongInZoneTimeout2 | >=0 | NA | 1.0.0 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 Axxon PSIM base version) |
WEB Report System PSIM | |||||
|---|---|---|---|---|---|
Registry section | String parameter | Available values | Default | Product version | Parameter in effect |
x32: (x32) | LogingPersonChangesRequired | 0, 1 | 0 | 1.0.0 and later | Enabling of this parameter is necessary for the correct operation of the Issued pass cards report. |
...
Monitoring PSIM | |||||
|---|---|---|---|---|---|
Registry section | String parameter | Available values | Default | Product version | Description |
x32: (x32-Monitoring) x64: (x64-Monitoring) | LPRDBsearchresultUnicodeBase64 | 0, 1 | 1 | 1.0 and later | The key sets how to process message in param0<> for the SEARCH_RESULT event of the LPRDB ("External database") object – as ANSI line or Unicode line additionally encoded in base64. 0 – ANSI 1 – UnicodeBase64 |
x32: (x32-Monitoring) x64: (x64-Monitoring) | PeakWorkingSetSizeQuota | >=0 | 100 | 1.0 and later | The maximum memory size in megabytes used by the process videosrv.exe on Agent Of Control. If the parameter is set to 0, then the check for the used memory is not performed. Once a day, the Agent Of Control checks the size of the memory it uses. The check is performed at the time specified by the TimeOfCheckWorkingSetSize key (see below). After exceeding the specified value, the videosrv.exe module is rebooted. |
x32: (x32-Monitoring) x64: (x64-Monitoring) | TimeOfCheckWorkingSetSize | >=0 | 3 | 1.0 and later | Time to check memory usage in hours. Default value is 3 (3:00 AM). See also the PeakWorkingSetSizeQuota key description above. |
x32: (x32-Monitoring) x64: (x64-Monitoring) | StoreVideoFiles | >0 | 3 | 1.0 and later | Time period for storage of not completely downloaded files on Agent Of Control. After the storage period is exceeded, the not completely downloaded files are deleted. |
x32: (x32-Monitoring) x64: (x64-Monitoring) | run_core | 0.1 | 1 | 1.0 and later | The key sets the Agent Of Control actions in case if the Axxon PSIM software is shut down. 0 – do not start the Axxon PSIM software 1 – start the Axxon PSIM software |
x32: (x32-Monitoring) x64: (x64-Monitoring) | socket_connect_tout | >=0 | 0 | 1.0 and later | The key defines TCP/IP connection mode with Server Of Control. 0 – blocking mode. Agent Of Control connects to Server Of Control without specifying connection timeout. >0 – non-blocking mode. Agent Of Control connects to Server Of Control with a connection timeout set by the socket_connect_tout > 0 parameter in seconds. |
x32: (x32-Monitoring) x64: (x64-Monitoring) | write_buffer_enable | 0.1 | 1 | 1.0 and later | Data buffering while recording on disc when receiving video data on Server Of Control. Agent Of Control transfers video data to Server Of Control in packages of 800 to 4096 bytes (4096 by default). When buffering is enabled, a 264 Kb block of memory is allocated to the Server Of Control for receiving video data, and data is saved to the disk when this memory block is full, not every time a packet is received from Agent Of Control. 0 – buffering is enabled. 1 – buffering is disabled. |
x32: (x32-Monitoring) x64: (x64-Monitoring) | stop_data_by_trx | 0.1 | 1 | 1.0 and later | The key determines the actions of Agent Of Control in case if, during the transfer of video data to ATM PSIM ARM, a financial transaction has begun on the ATM PSIM. 0 – video data transfer is not stopped. 1 – video data transfer is suspended until financial transaction if completed. |
x32: (x32-Monitoring) x64: (x64-Monitoring) | IPPort | > 0 | 7755 | 1.0 and later | The key specifies the port on the Server Of Control/Central Server Of Control used for connecting the clients. |
x32: (x32-Monitoring) x64: (x64-Monitoring) | financial_trx_tout | >0 | 60 | 1.0 and later | Timeout for waiting for the financial transaction to complete in minutes. If after the start of the financial transaction during the time-out, there is no message from the ATM about its end, it will be considered to be completed. |
x32: HKLM\SOFTWARE\BitSoft\VHOST\ULPR x64: HKLM\SOFTWARE\Wow6432Node\BitSoft\VHOST\ULPR | ULPRspecialProcessing | >=0 | NA | 1.0 and later | The key enables special operation mode of the Monitoring PSIM software joint with Auto PSIM. 1 – the special operation mode of the Monitoring software joint with Auto PSIM is enabled. Any other value – the special operation mode is disabled. Note. The key is created both on Agent Of Control and Server Of Control. |
x32: HKLM\SOFTWARE\BitSoft\VHOST\ULPR x64: HKLM\SOFTWARE\Wow6432Node\BitSoft\VHOST\ULPR | PlaceOfRecognitionN | 1,2 | NA | 1.0 and later | 2 – exit. Note 1. The key is in use in special operation mode of the Monitoring PSIM software joint with Auto PSIM. Note 2. The key is created at Agent Of Control |
x32: HKLM\SOFTWARE\BitSoft\VHOST\ULPR x64: HKLM\SOFTWARE\Wow6432Node\BitSoft\VHOST\ULPR | CamOfRecognitionN | >0 | NA | 1.0 and later | This parameter corresponds to the ID of a camera added to the recognition module. CamOfRecognitionN, where N is the ID of the LPR channel object. The value of this parameter corresponds to the Camera object ID specified in the LPR channel object settings. Note 1. The key is in use in special operation mode of the Monitoring PSIM software joint with Auto PSIM. Note 2. The key is created at Agent Of Control |
x32: HKLM\SOFTWARE\BitSoft\VHOST\ULPR x64: HKLM\SOFTWARE\Wow6432Node\BitSoft\VHOST\ULPR | AlarmMsgOne | >=0 | NA | 1.0 and later | The key enables the LP found in the database alarm both for Entrance and Exit recognition points. 0 – enables the LP found in the database alarm both for Entrance and Exit recognition points. Any other value – the LP found in the database alarm is generated for Entrance recognition point only. Note 1. The key is in use in special operation mode of the Monitoring software joint with Auto PSIM. Note 2. The key is created at Server Of Control |
x32: (x32-Monitoring) x64: (x64-onitoring) | TimeAlarmFromAgent | 0, 1 | 0 | 1.0 and later | The key enables registration of the alarm with the time it occurred on the site. 0 – In the Alarm date field in the interface objects, the time of loading the alarm into the database after it is received from the Agent Of Control is shown, not the time of occurrence of the alarm on site. 1 - In the Alarm date field in the interface objects, the time of alarm occurrence on site is shown. Note. The key is set on the Server Of Control. |
x32: (x32-Monitoring) x64: (x64-Monitoring) | FileQueryEnable | 0, 1 | 0 | 1.0 and later | The key enables automated video clip loading. 0 – automated video clip loading is disabled. 1 – automated video clip loading is enabled. Note. The key is created at Server Of Control and/or Additional Workstation |
x32: (x32-Monitoring) x64: (x64-Monitoring) | FileQueryPath | Text | C:\Query\ | 1.0.0 and later | The key sets folder to share data with third party systems which is necessary for automated video clip loading. Note. The key is created at Server Of Control and/or Additional Workstation |
x32: (x32-Monitoring) x64: (x64-Monitoring) | OldLogPanel | 0, 1 | 0 | 1.0 and later | The key changes the Log Panel interface color theme. 0 - dark interface theme. 1 - light interface theme. |
x32: (x32-Monitoring) x64: (x64-Monitoring) | StreamViewerExportPath | Text | <Axxon PSIM installation directory>\export | 1.0 and later | The key specifies the path to the catalog of frames and video clips which were exported from the Monitoring PSIM interface during the live and archive video playback from a certain camera. See Playing back live video and archive from a specific camera. |
x32: (x32-Monitoring) x64: (x64-Monitoring) | MonitoringReserving | 0, 1 | 0 | 1.0 and later | The key removes the restriction on adding the same cameras for tracking in different Partitions Of Control. 0 - the restriction is enabled. 1 - the restriction is removed. |
x32: (x32-Monitoring) x64: (x64-Monitoring) | AccessByCardEnable | 0, 1 | 0 | 1.0 and later | The key activates the special mode of Monitoring PSIM operation together with ACFA PSIM, as well as the ability to customize the long alarm description. 0 - Special operation mode is off. 1 - Special operation mode is on. |
x32: (x32-Monitoring) x64: (x64-Monitoring) | CustomisedLongAlarmName | Text | Object disarmed | 1.0 and later | The key changes the description of the long alarm Object disarmed in the Monitoring and Monitoring reports interface objects. |
x32: HKLM\SOFTWARE\BitSoft\MonitorSSTV\Loader x64: HKLM\SOFTWARE\Wow6432Node\BitSoft\MonitorSSTV\Loader | UseBulkInsert | 0, 1 | 1.0 and later | 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) | |
x32: (x32-Monitoring) x64: (x64-Monitoring) | PostfixForTimeOut | Text | NA | 1.0 and later | The key specifies the postfix in the identifier of the Partitions Of Control for which the waiting timeout specified in the TimeoutForPostfix key should be specified. |
x32: (x32-Monitoring) x64: (x64-Monitoring) | TimeoutForPostfix | >0 | 6 | 1.0 and later | The key sets the waiting timeout in minutes for the Server Of Control to receive the packets with the technical state of Agent Of Control. After this time the "No connection" error will be displayed. |
| HKEY_CURRENT_USER\SOFTWARE\BitSoft\MonitorSSTV | MAXRECORDSONPAGE | 1,000 - 2,000,000,000 | 10,000 | 1.0 and later | Sets the maximum number of events to be displayed in the Event Log window without navigation buttons. |
x32: (x32-Monitoring) x64: (x64-Monitoring) | PassiveModeForFTP | 0, 1 | 1 | 1.0 and later | The key sets the operation mode of the Central Server Of Control software via FTP. 0 - Active mode. 1- Passive mode. |
x32: (x32-Monitoring) x64: (x64-Monitoring) | PeriodRequestOfStatistic | > 0 | 5 | 1.0 and later | The key sets the statistics polling period in minutes for the Servers Of Control. |
x32: (x32-Monitoring) x64: (x64-Monitoring) | LogArchPeriod | > 0 | 168 | 1.0 and later | The key sets the log archiving period in hours of the Communication module (CentralNetServer.log) |
x32: (x32-Monitoring) x64: (x64-Monitoring) | LogMaxSize | > 0 | 100 | 1.0 and later | The key sets the maximum size of the communication module log file at which it begins to archive ignoring the LogArchPeriod parameter. |
x32: (x32-Monitoring) x64: (x64-Monitoring) | LogArchDelPeriod | > 0 | 3 | 1.0 and later | The key sets the log files archive retention period in months (CentralNetServer.log). |
x32: (x32-Monitoring) x64: (x64-Monitoring) | KeepDB | > 0 | 6 | 1.0 and later | The key sets the data retention period of closed errors and alarms in the ServerSSTV DB. |
x32: (x32-Monitoring) x64: (x64-Monitoring) | LastLoadThreshold | >= 0 | 30 | 1.0 and later | The key sets the time in minutes, after which, if the data in the MonitorSSTV database is outdated, the corresponding indication on the Server Of Control/CSC will appear. |
x32: (x32-Monitoring) x64: (x64-Monitoring) | DisableMonitoring | 0, 1 | 0 | 1.0 and later | 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:
|
x32: (x32-Monitoring) x64: (x64-Monitoring) | StreamViewerLowestPriority | 0, 1 | 0 | 1.0 and later | The key sets low priority of the StreamViewer process when it starts. 0 − The StreamViewer process starts with normal (medium) priority. 1 − The StreamViewer process starts with low priority. |
x32: (x32-Monitoring) x64: (x64-Monitoring) | SleepAfterDisarm | integer in msec | 50 | 1.0 and later | The key sets the time interval of recording delay in msec after disarming the camera |
x32: (x32-Monitoring) x64: (x64-Monitoring) | SleepAfterRecStop | integer in msec | 50 | 1.0 and later | If the continuous recording mode is enabled, the key sets the time interval of recording delay by camera in msec after it stops. If the camera is armed, the key sets the time interval of camera arming delay in msec after it stops |
x32: (x32-Monitoring) x64: (x64-Monitoring) | KeepVideoDataInBase | > 0 | 0 | 1.0 and later | If the parameter isn’t created or equals 0, the video data isn’t stored in the Monitoring database (MonitorSSTV or ServerSSTV). If the parameter > 0, its value equals the number of days the video data should be stored in the Monitoring database. When this period is exceeded, the video data is deleted from the database |
x32: (x32-Monitoring) x64: (x64-Monitoring)
| GroupingCameras | 1-200 | 0 | 2.0 and later | If you don't create the parameter or it equals 0, cameras aren't divided into groups If the parameter > 0, its value equals the number of cameras in the group |
x32: (x32-Monitoring) x64: (x64-Monitoring)
| CarPlatesBlackList | 0, 1 | 0 | 2.0 and later | If you don't create the parameter or it equals 0, the transmission of the LPs' blacklist is disabled. If the parameter value is 1, the transmission of the LPs' blacklist is enabled |
x32: (x32-Monitoring) x64: (x64-Monitoring)
| TcpPortForBlackList | TCP port addresses | 8888 | 2.0 and later | The key determines the connection port number of the Server of Control module to all Agent of Control modules |
x32: (x32-Monitoring) x64: (x64-Monitoring)
| TcpPortForBlackList<ID> | TCP port addresses | 8888 | 2.0 and later | The key determines the connection port number of the Server of Control module to a certain Agent of Control module For example, for the Agent of Control module with ID=550016, the used parameter is called TcpPortForBlackList550016 |
x32: (x32-Monitoring) x64: (x64-Monitoring) | ClearVideoDataPeriod | >0 | 0 | 2.0 and later | The key determines the number of hours after which the video information that appears in the Video data window can be deleted. The key is installed on the computer with the Server of Control module. If the parameter equals 0, the video data is deleted as usual after 30 days. If the parameter >0, the irrelevant data is deleted after this number of hours |
x32: (x32-Monitoring) x64: (x64-Monitoring) | HideIpCam | 0, 1 | 0 | 2.0 and later | The key hides the camera IP address in the Reaction to alarm window when you press the Camera button on the control panel: 0—the camera IP address is displayed 1—the camera IP address is hidden |
| 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_OPTION | 0, 1 | 0 | 1.0 and later | 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_OPTION | 0, 1 | 0 | 1.0 and later | 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_OPTION | 0, 1 | 0 | 1.0 and later | 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_OPTION | 0, 1 | 0 | 1.0 and later | 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_OPTION | 0, 1 | 0 | 1.0 and later | 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_OPTION | 0, 1 | 0 | 1.0 and later | 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_OPTION | 0, 1 | 0 | 1.0 and later | 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_OPTION | 0, 1 | 0 | 1.0 and later | 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_OPTION | 0, 1 | 0 | 1.0 and later | 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_OPTION | 0, 1 | 0 | 1.0 and later | 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_OPTION | 0, 1 | 0 | 1.0 and later | 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_OPTION | 0, 1 | 0 | 1.0 and later | 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_OPTION | 0, 1 | 0 | 1.0 and later | 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_OPTION | 0, 1 | 0 | 1.0 and later | 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_OPTION | 0, 1 | 0 | 1.0 and later | 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_OPTION | 0, 1 | 0 | 1.0 and later | 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_OPTION | 0, 1 | 0 | 1.0 and later | 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_OPTION | 0, 1 | 0 | 1.0 and later | 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_OPTION | 0, 1 | 0 | 1.0 and later | The key activates the Delete menu item which is used to remove the recordings from the archive (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_OPTION | 0, 1 | 0 | 1.0 and later | The key activates the Protect menu item which is used to protect the archive recordings from rewriting (see Protection of separate record and disable of protection). 0 - The Protect item is hidden. 1 - The Protect item is displayed. |
x32: (x32-Monitoring) x64: (x64-Monitoring) | RequestFullStatisticOnStartup | 0, 1 | 0 | 1.0 and later | By default, the Central Server Of Control requests a complete package of statistics from all Servers Of Control only once, when it first connects to the Servers Of Control. The key activates the request on the Central Server Of Control for a complete statistics package from all Servers Of Control every time the CentralNetServer.exe communication module is launched. 0 - disabled. 1 - a complete statistics package will be requested from all Servers Of Control each time the CentralNetServer.exe communication module is launched. Attention! Requesting a complete statistics package is a resource-intensive operation. It is only necessary to activate this key if absolutely necessary. |
x32: (x32-Monitoring) x64: (x64-Monitoring) | RequestFullStatistic[N] Note. [N] is the internal identifier of the Server Of Control object in Axxon PSIM | 0, 1 | 0 | 1.0 and later | By default, the Central Server Of Control requests a complete package of statistics from all Servers Of Control only once, when it first connects to the Servers Of Control. The key activates the request for a complete statistics package from a specific Server Of Control once. The request will be executed when the CentralNetServer.exe communication module is launched, and the value of this key will automatically change to 0. 0 - disabled. 1 - a complete statistics package from a specific Server Of Control will be requested once when the CentralNetServer.exe communication module is launched. Attention! Requesting a complete statistics package is a resource-intensive operation. It is only necessary to activate this key if absolutely necessary. |
x32: (x32-Monitoring) x64: (x64-Monitoring) | FtpPath | Text | <Axxon PSIM installation directory>\Vhost\DATA\FTP\ | 1.0 and later | Sets the path to the FTP directory on the Server Of Control for working with the Central Server Of Control. |
x32: (x32-Monitoring) x64: (x64-Monitoring) | ExportPath | Text | DISK:\Export\ , where DISK is the drive on which the operating system is installed | NA | Sets the path to the export directory on the Server Of Control |
...