Configuring Access components

All fields are required unless otherwise stated in the description.

Services

Services in Access are required to select options for connecting to external systems.

Service list:

Name in Access	Name	Version	Comment
Apacs	APACS 3000	8.3.1.0
Bastion	Bastion	2.1.11.2337
Bolid	Bolid	1.20.3
FaceStream	VisionLabs FaceStream	4.0 and up
Luna	VisionLabs LUNA PLATFORM	5.31 and up
LunaAceConverter	LUNA ACE	1.2.23
LunaCars	VisionLabs LUNA CARS	2.0.1	CARS Installer version
Parsec	Parsec	3.11.629 39
PercoWEB	PERCo-Web 2.0	4.30
Rusguard	RusGuard	3.3.1.
Salto	Salto	6.6.3.0
Sigur	Sigur	1.1.1.9s
SigurThroughDatabase	Sigur	1.1.1.9s
Strazh	Rubezh Strazh	1.2.211201.648

Apacs

This service is designed to interact with the APACS 3000 ACS.

Software integration of the APACS ACS software with the face recognition system is implemented to ensure the passage of recognized faces through the turnstile / door with a magnetic lock.

The supported version of the APACS ACS is 8.3.1.0.

Apacs service functionality

Main functions:

• adding devices with which LP will work;
• receiving regular updates from the ACS software database;
• sending requests for adding/changing data to the LP;
• receiving identification events;
• sending a request to the ACS software about identification events;
• logging of events about an attempt by an unidentified employee to pass through the turnstile.

Configuring parameters for connecting to the APACS ACS

Service settings and possible values:

Parameter	Description	Possible values	Default value
name	User-defined service name	Any textual names. Only Latin characters are supported. It is not recommended to enter more than 30 characters.	-
host	IP address of the server with installed APACS software	IP address in the form X.X.X.X	-
port	Port on which APACS is deployed	-	7010
login	Login of ACS software user	User created in APACS ACS software	-
password	User password created in APACS ACS software	User password	-
feature_profile	Profile key belonging to the system's master key. The key data is located in the APACS ACS software: [Help] > About.	-	-
luna_id	Dropdown list to select Luna Service ID in Access.	-	-
default_list_id	Identifier of the LLS list with which APACS will synchronize employees	Identifier of the list created in the LLS.	-
user_limit	Maximum number of employees to synchronize. The number is set based on the number of employees who will pass through the ACS.	1...10000	1000
vl_access_host	IP address of the server on which Access is installed	IP address in the form X.X.X.X	-
vl_access_port	Port of the server where Access is deployed	-	9091
facility_code_N	Parameter for entering card numbers without offset for their recognition by the system	-	-
shift_N	Shifts for the corresponding facility codes (for example, an employee has a card 070.56458, it is entered in the ACS as 156458, where 1 is the shift. Accordingly, in the service settings, we must specify facility_code_1 = 70, and shift_1 = 1).

Bastion

Software integration of the Bastion ACS software with the face recognition system (LP5) is implemented to ensure the passage of recognized persons through the turnstile/door with a magnetic lock.

Supports Bastion ACS version 2.1.11.2337.

This service is designed to interact with the Bastion ACS.

The ACS synchronizes employees with the list in Luna and listens to events based on which it decides to open or not open the turnstile. These events are generated in Access by the CreateBastionEvent pipeline.

Bastion functionality

Main features:

• adding devices that LP5 will work with;
• receiving regular updates from the ACS software database;
• sending requests to add/change data to LP5;
• receiving identification events;
• sending requests to the ACS software about identification events;
• logging events about an attempt by an unidentified employee to pass through the turnstile.

Bastion settings

The following settings are used when creating a new service:

Parameter	Description	Values	Default value
name	Service name specified by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
default_list_id	Luna List ID that Bastion will synchronize employees with	The ID of the list created in Luna	-
luna_id	Drop-down list with Luna service IDs in Access	-	-
host	IP address of the server with installed Bastion software	IP address in the form of X.X.X.X	-
port	ONVIF port of Bastion service	-	10112
username	Bastion ONVIF user login	The user created in Bastion	-
password	Bastion ONVIF user password	User password	-
vl_access_host	IP address of the server where Access is installed	IP address in the form of X.X.X.X	-
vl_access_port	Port of the server where Access is deployed	-	9091

Setting up Bastion ACS software

1․ Go to the server where the Bastion ACS is deployed and open the ACS software.

2․ Go to the Operator Window -> Drivers -> Face Driver -> Configuration tab.

3․ In the Main settings section, set the port, ONVIF login and password.

4․ In the KBI Server section, add a new server by clicking "+".

5․ In the new server setup, enter the addresses of the person profile management service and the event service, the Access address in the "host:port" format, set the login and password for both services.

6․ In the Waypoint setting, add a new waypoint by pressing "+".

7․ Select the entry point Door N RM.

8․ In the Description field, enter the name of the camera that works with this access point.

9․ Select the operating mode "Access in identification mode"

The description of the access point must match the name of the device in Access.

10․ Save your changes by clicking on the floppy disk icon.

11․ Set up the management of passes on the tab Tools -> Passes -> Pass Bureau.

12․ Create an application for a pass. Go to Application -> General -> Pass Management -> New Application.

13․ Fill in the required fields and click OK.

14․ Issuance of passes. Go to Application -> General -> Pass management -> Issue -> Generate card number -> Ok.

Issued passes are displayed on the Issued tab.

15․ Editing a pass. Go to the section Issued -> Required pass -> Editing -> Ok.

Bolid

Hardware and software integration required for LP5 communication with the Bolid ACS software to provide control of the associated device (S-2000 series devices or other devices compatible with the Bolid software).

Supports Bolid version 1.20.3, Orion Pro integration module version 1.4.

Information interaction is provided through the Orion Pro automated workplace software.

The Orion PRO licensed integration module must be installed and launched.

The integration module is a SOAP web service accessed via the HTTP/HTTPS protocols. The description of the web service complies with the WSDL version 2.0 specification.

The service runs under Windows 7/8/8.1/10 (32 bit or 64 bit).

Bolid functionality

Main features:

• sending a pair of “user ID” — “managed device” via the Orion Pro API;
• data replication from the ACS software database.

Bolid settings

The following settings are used when creating a new service:

Parameter	Description	Values	Default value
name	Service name specified by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
luna_id	Drop-down list with Luna service IDs in Access	-	-
default_list_id	Luna List ID that Bolid will synchronize employees with	The ID of the list created in Luna	-
login	Bolid user login. It is created in Bolid Database Administrator → go to Passwords → go to Password type — Remote control	The user created in Bolid	-
password	Bolid user password	User password	-
host	IP address of the server with installed Bolid software	IP address in the form X.X.X.X	-
port	Bolid service port	-	8090
max_workers	Number of data replication handlers from the Luna list to Bolid. If there is a large amount of data, it is recommended to set from 2 to 5.	2...5	2
token_update_sec	Time to refresh the access token (in seconds)	It is not recommended to change this Parameter	100
save_additional_card	Saving the number of the second card to the event, if available	On — save the card number;	Off
		Off — save the event number

Preparatory actions with Orion Pro software

To launch and configure Bolid, you need to perform preparatory steps with the Orion Pro software:

1․ On the OrionShell panel, run the BDA (Bolid Database Administrator) module (Figure 122):

Figure 122. Launching BDA on the OrionShell panel

2․ Add a new employee. Fill in the required fields according to the rules for creating employees at the facility (Figure 123).

3․ Go to the Employees section

4․ Click the "add" button

5․ Fill in the required employee fields

Select the status of “Administrator” or another department with employees who have full access to the system.

Figure 123. Adding a new employee

6․ Add “Maximum” access level to the new user and set a password (Figure 124).

7․ Go to the Access section

8․ Click Add

9․ Select the desired employee, enter the password

10․ Select access level Maximum

Figure 124. Setting an access level for an employee

11․ Add new section (Figure 125):

12․ Select the “System structure” tab;

13․ Select “Sections”;

14․ Select all “Sections”;

15․ Add a new section with default settings and name it.

Figure 125. Adding a new section

16․ Bind devices to the newly created section (Figure 126).

17․ Select a section

18․ Click the “Add” button at the bottom left.

Figure 126. Binding devices to a section

19․ select the required device in the list of devices (Figure 127);

20․ select it with the “>>” button and move it to the right field;

21․ confirm the changes with the “OK” button;

22․ click the “Save” button at the bottom left.

Figure 126. Binding devices to a section

23․ Edit the orion.ini file in the folder with the installed Orion Pro application (for example, C:\BOLID\ARM_ORION_PRO1_20_3), adding Parameters to it (if there are none):

[Checkerdb]
Remarks=1
timechecker=5
Logon=1
RemoteCmd=1
CmdOn=1
[ChangeDB]
on=1

24․ Restart all Orion Pro applications.

Configuring the “ORION PRO INTEGRATION MODULE” application

To configure the “ORION PRO INTEGRATION MODULE” application, follow these steps:

1․ Download the official distribution kit of the “ORION PRO INTEGRATION MODULE” application (link).

2․ Run the installation. After the installation is complete, launch the module, check the database connection settings. If everything works correctly, close the module.

3․ Install the module to run as a service. To do this, run the command in the terminal as administrator in the folder with the installed module (for example: C:\BOLID\IntegrServ):

IntegrServ.exe /INSTALL

4․ In the system control panel, find the installed service and run it by clicking the right mouse button and selecting “Start” (Figure 128).

Figure 128. System control panel

FaceStream

Service for working with FaceStream. The service is designed to receive a list of stream names from FaceStream for subsequent transmission to the ACS.

Supported version is FaceStream 4.0 and later.

Configuring FaceStream settings

Service settings and possible values:

Parameter	Description	Possible values	Default value
name	User-defined service name	Any textual names. Only Latin characters are supported. It is not recommended to enter more than 30 characters.	-
host	IP address of the server with installed FaceStream	IP address in the form X.X.X.X	-
port	Port of the server where FaceStream is deployed	-	34569
enable_ssl	Method of encrypting data during transmission over the network. Depends on the network type in the solution.	On - https	Off
		Off - http

Luna

The service is designed to redirect data from/to LP to external systems and devices.

If there is no face_stream_url, only local devices will be used as source values in all dependent components.

Luna settings

The following settings are used when creating a new service:

Parameter	Description	Values	Default value
name	Service name specified by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
host	IP address of the server where Luna is installed	IP address in the form of X.X.X.X	-
port	Port of the server where Luna is deployed	-	5000
username	Admin login in LP5	-	-
password	Admin password in LP5	-	-
handler_id	UUID of the handler for working with passage events, created in Luna	-	-
min_face_similarity	Minimum value of the quality of a recognized face, at which identification will be carried out	The value is formed at the design stage and corrected at the testing stage (0,00...1,00)	0,5

LunaAceConverter

Service for sending data received from LUNA ACE devices to LP5. The received request from the device is redirected to the RRL, then a response is generated for the device based on the received response from the LP5.

Supported version LUNA ACE 1.2.23

LuaAceConverter settings

The following settings are used when creating a new service:

Parameter	Description	Values	Default value
name	Service name specified by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
luna_id	Drop-down list with Luna service IDs in Access	-	-

Setting up LUNA ACE

1․ Connect to the device via SSh.

2․ Open the file: vi /opt/luna_ace/ace_device.conf .

3․ Specify the URL of the LunaAceConverter service in the luna_platform_address parameter.

To get the URL of the service, you need to go to the created LunaAceConverter service in Access and copy the full path from the browser search bar:

http://<ip_address>:9092/service/<UUID>.

4․ Change to the directory: cd /opt/luna_ace/services/ace_device

5․ Restart the device: restart

LunaCars

Software and hardware integration required for communication between LUNA CARS and barriers (boom barriers, sliding gates, bollards, and others) for vehicle access control.

Supported LUNA CARS modules:

• LUNA CARS API: v.1.0.3;
• LUNA CARS Stream: v.2.0.4;
• LUNA CARS Analytics: v.3.0.3.

Access links to LUNA CARS Analytics backend.

Events in the queue are of type CarDetectionEvent.

LunaCars settings

The following settings are used when creating a new service:

Parameter	Description	Values	Default value
name	Service name specified by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
host	IP address of the server where LUNA CARS is installed	IP address in the form of X.X.X.X	-
port	Port of the server where LUNA CARS is deployed	-	8080
api_port	Port of the server where LUNA CARS API is deployed	-	8100
login	LUNA CARS Analytics administrator login	-	admin@test.ru
password	LUNA CARS Analytics administrator password	-	admin
event_expiry_time	After how many seconds events can be skipped as obsolete. It is necessary to reduce the time to ~15 seconds if the vehicle flow is constant	15...60	60
min_license_plate_accuracy	Minimum accuracy of vehicle registration plate recognition	The value is formed at the design stage and corrected at the testing stage (0,00...1,00)	0,6
event_memory_time	Time during which the service does not create a repeat event for the same vehicle (in seconds). It is necessary to increase the value if the vehicle stands in the recognition zone for a long time in the queue for entry, etc.	60…180	90
timeout	Timeout for an unsuccessful attempt to connect to the service. It is necessary to increase the time if there is a large delay between servers	The time is selected based on the delay in the network to maintain performance	-

Parsec

This service is designed to interact with the Parsec ACS to ensure the passage of recognized persons through a turnstile/door with a magnetic lock.

The service executes the following requests to the ACS:

• sending url address of ONVIF services;
• receiving card swipe events;
• getting access point IDs.

Supports ParsecNET 3 ver. 3.11.629 39.

Performs user data replication from the Parsec ACS to the specified Luna list and generates ParsecController controllers from the received list of devices for execution of entry or exit requests.

Parsec functionality

Main features:

• transferring a list of employees to a Luna list;
• adding/editing/deleting employees in the Luna list;
• receiving detection events from devices.

Parsec settings

The following settings are used when creating a new service:

Parameter	Description	Values	Default value
name	Service name specified by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
default_list_id	Luna List ID that Parsec will synchronize employees with	The ID of the list created in Luna	-
luna_id	Drop-down list with Luna service IDs in Access	-	-
host	IP address of the server where Parsec is installed	IP address in the form of X.X.X.X	-
port	Port of the server where Parsec is deployed	-	-
username	Parsec user login	-	-
integration_key	Parsec integration key.Used as a password to connect to the device	-	-
vl_access_host	IP address of the server where Access is installed	IP address in the form of X.X.X.X	-
vl_access_port	Port of the server where Access is deployed	-	9091

Configuring Access and Parsec PACS integration

To launch and configure the Parsec ACS software, install Parsec.NET and run the Administration program and check the settings (Figure 129):

1․ Make sure that “Advanced Mode” is running (“File” → “Advanced Mode”).

2․ Go to the “Equipment editor” section and make sure that the controllers are connected .

Figure 129. “Equipment editor” section

3․ For each required controller, set the following settings in the “Access Modes” tab (Figure 130).

Figure 130. “Access Modes” tab

4․ Go to the “System settings editor” section, then open the “Face Recognition (ONVIF)” tab (Figure 131).

Figure 131. “Face Recognition (ONVIF)” tab

5․ In the “Face recognition (ONVIF)” window, click the “Change” button and make sure that the “Use FRS” item is enabled, and the “FRS type” is set to “ONVIF face recognition”.

6․ In the “IP Address” and “Port” fields, enter the Access server data.

7․ Click the “Check connection” button only after configuring Access, this will require the “Integration key”.

8․ After clicking on the “Check connection” button, the fields in the “Face recognition system services” block will be filled in automatically.

9․ Click the “Save” button.

10․ Replicate employees to the Luna list by clicking the “Transfer employees and visitors” button. Before, make sure that all staff members are correctly added in the "Staff Editor" section, see «Adding staff to Parsec ACS»

Example of displaying staff member unloaded from Parsec ACS to LUNA PLATFORM list (Figure 132).

Figure 132. Displaying staff member in LUNA PLATFORM

Configuring access groups in Parsec ACS

1․ Click the «Access group editor» section.

2․ Add a new access group.

3․ Add an access territory where the access points are included (Figure 133).

Figure 133. Configuring Access Groups

4․ Click the Save button.

Adding staff to Parsec ACS

Adding staff members to Parsec ACS is necessary for their subsequent upload to LUNA PLATFORM (Figure 134).

Figure 134. Edit Staff section. Adding a new staff member

1․ Click the «Staff Editor» section.

2․ Click the button of adding a new staff member.

3․ Fill in the «Last Name» and «First Name» fields.

4․ Add a photo of the staff member.

5․ Fill in the «Card code» field. The «PIN» field will be filled in automatically.

If card access is not provided at the facility or the staff member does not have a card, enter any value in the «Card code» field.

6․ Select the staff member's access group.

7․ Click the Save button.

If you add staff members correctly, all new or changed data will be added to the LUNA PLATFORM database automatically.

PercoWEB

Software integration of the PERCo-Web ACS software with LP5 is implemented to ensure the passage of recognized persons through a turnstile/door with a magnetic lock.

Supports PERCo-Web system version 2.0, build number 4.30.

Performs user data replication from the PERCo ACS to the specified Luna list and generates PercoController controllers from the received list of devices for execution of entry or exit requests.

PercoWEB functionality

Main features:

• adding devices that LP5 will work with;
• receiving regular updates from the ACS software database;
• sending requests to add/change data to LP5;
• receiving identification events;
• sending requests to the ACS software about identification events;
• logging events about an attempt by an unidentified employee to pass through the turnstile.

PERCo-Web settings

The following settings are used when creating a new service:

Parameter	Description	Values	Default value
name	Service name specified by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
host	IP address of the server where PERCo is installed	IP address in the form of X.X.X.X.	-
port	Port of the server where PERCo is deployed	-	-
enable_ssl	Network connection type	On - https	Off
		Off - http
login	PERCo user login	The user created in PERCo	-
password	PERCo user password	User password	-
token_ttl_min	Security token expiration time in minutes. The value must match the PERCo-Web software, location in PercoWeb Manager -> Settings -> Advanced settings -> Session lifetime. (default 1 day). At the end of the time, the token must be refreshed manually.	-	1440
luna_id	Drop-down list with Luna service IDs in Access	-	-
default_list_id	Luna List ID that Perco will synchronize employees with	The ID of the list created in Luna	-
min_face_similarity	Minimum face similarity threshold when performing verification	The value is formed at the design stage and corrected at the testing stage (0,00...1,00)	0,7

Rusguard

Software integration of Rusgurad ACS software with SRL is implemented to ensure the passage of recognized faces through the turnstile.

Rusguard functionality

Main functions:

• adding devices with which SRL will work;
• receiving regular updates from the ACS software database;
• sending requests for adding/changing data to the SRL;
• receiving identification events;
• sending a request to the ACS software about identification events;
• logging of events about an attempt by an unidentified employee to pass through the turnstile.

Configuring parameters for connecting to Rusguard

Service settings and possible values:

Parameter	Description	Possible values	Default value
name	User-defined service name	Any textual names. Only Latin characters are supported. It is not recommended to enter more than 30 characters.	-
default_list_id	UUID of the CRL list with which Rusguard will synchronize employees	List UUIDs created in the CRL.	-
luna_id	Dropdown list to select Luna Service ID in Access.	-	-
host	IP address of the server with installed Rusguard	IP address in the form X.X.X.X.	-
port	Port of the server where Rusguard is deployed	-	8089

Salto

This service is designed to interact with the Salto ACS.

• Supported system version: 6.6.3.0.

Replicates user data from the Salto PACS to the specified Luna list and generates "SaltoController" controllers from the received list of devices for subsequent execution of pass.

To configure the Salto ACS software, please refer to the official documentation.

Salto settings

The ACS synchronizes employees with the list in Luna and listens to the events, based on which it decides to open or not open the turnstile. These events are generated in Access by the SendToSalto pipeline.

The following settings are used when creating a new service:

Parameter	Description	Values	Default value
name	The service name specified by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
default_list_id	Luna List ID that Sigur will synchronize employees with	The ID of the list created in Luna	-
luna_id	The Drop-down list with Luna service IDs in Access	-	-
host	IP address Salto	-	-
port	Port of the server where Salto is deployed	-	-
login	Salto user login	The user created in Salto	-
password	Salto user password	User password	-

Sigur

Sigur

Supports Sigur ACS version 1.1.1.9s.

This service is designed to interact with the Sigur ACS.

Software integrations with Sigur ACS software are implemented to provide:

• with LP5 for the passage of recognized persons through the turnstile / door with a magnetic lock.
• with LUNA CARS to provide access control of vehicles when passing through barrier devices.

Configuring Access and Sigur PACS integration

To launch and configure the Sigur PACS software, follow these steps:

1․ Make sure you are using Sigur PACS software version 1.1.1.9.s or newer.

2․ In the menu of the Sigur control program, select “Help” → “About the program”.

3․ Check the software version against the one listed on www.sigur.com (https://sigur.com/last_releases/).

4․ Update the software to the latest version if necessary.

5․ Set up interaction between the integration module and the Sigur PACS software server.

6․ In the menu of the Sigur control program, select “File” → “Settings”.

7․ In the “Edit Settings” dialog, go to the “Video Surveillance” item.

8․ Add video surveillance server (Figure 135).

Figure 135. Adding a video surveillance server

9․ “Server name” — enter the server name;

10․ “Server type” — “User system”;

11․ click “OK”;

12․ enter the server (Figure 136)

Figure 136. Editing video surveillance server Parameters

13․ “Server address” and “Server port (HTTP)” are used when accessing the server from the PACS via HTTP protocol;

14․ “Server address” corresponds to the IP address of the machine on which Access is running;

15․ “Server port (HTTP)” is the port for the integration module (the default value is 9091; if the port is already in use, change it);

16․ "Path to service" sets the common path prefix on the server for all requests from the ACS. This value should be taken from the information block of the Sigur component in Access, the value of the webhook-url field (Figure 137).

17․ Enable the flag Upload photos to the server when using the Sigur service, disable when using the SigurThroughDatabase service.

18․ Activate the flag Receive events from the server.

Figure 137. Webhook link

19․ Enable face recognition.

20․ In the “Edit Settings” dialog, go to the “Face Recognition” item.

21․ Check the box next to “Enable face recognition” (Figure 138).

Figure 138. Enabling face recognition in system settings

Configuring access points in Sigur

You may need to restart the Sigur PACS server in order for it to be able to connect to the integration module.

To configure access points in Sigur, follow these steps:

1․ In the side menu of the Sigur control program, select the “Equipment” item (Figure 139).

Figure 139. Sigur control software side menu

2․ Select the required access point and configure video surveillance settings for it (Figure 140):

3․ “System” — select the name of the created user system;

4․ “Camera” — select a camera. When you click on the drop-down list, it should show the names of all devices created in Access. This indicates that the integration is working properly and Sigur was able to connect to Access. Select the device that is used to identify the required access point;

5․ check the box next to “Enable face recognition”;

6․ click the “Apply” button.

Figure 140. Configuring the Parameters of video surveillance equipment

Direct connection

Sigur functionality

Main features:

• adding devices that LP5 and LUNA CARS will work with;
• receiving regular updates from the ACS software database;
• sending requests to add/change data to LP5;
• receiving identification events;
• sending requests to the ACS software about identification events;
• logging events about an attempt by an unidentified employee to pass through the turnstile.

Sigur settings

The ACS synchronizes employees with the list in Luna and listens to the events, based on which it decides to open or not open the turnstile. These events are generated in Access by the SendToSigur pipeline.

The following settings are used when creating a new service:

Parameter	Description	Values	Default value
name	The service name specified by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
default_list_id	Luna List ID that Sigur will synchronize employees with	The ID of the list created in Luna	-
luna_id	The Drop-down list with Luna service IDs in Access	-	-
host	IP address Sigur.	-	-
luna_cars_id	LUNA CARS service ID in Access	-	-
mark_for_ignore	When synchronizing with Sigur, if this combination occurs in the body of an employee's request, then the request is ignored.This is required to distribute different copies of Sigur in one system	On — ignore requests;	Off
		Off — execute requests

Connecting through the database — SigurThroughDatabase

The service is designed to interact with the Sigur ACS directly through its database. It synchronizes employees from the database with the list in Luna. The ACS opens a connection in which the service returns events to it as they occur. These events are generated in VL Access by the SendToSigur pipeline.

SigurThroughDatabase functionality

Main features:

• adding devices that LP5 will work with;
• receiving regular updates from the ACS software database;
• sending requests to add/change data to LP5;
• receiving identification events;
• sending requests to the ACS software about identification events;
• logging events about an attempt by an unidentified employee to pass through the turnstile.

SigurThroughDatabase settings

The following settings are used when creating a new service:

Parameter	Description	Values	Default value
name	Service name specified by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
host	IP address of the Sigur database	IP address in the form of X.X.X.X.
db_username	Username used to connect to the Sigur database	-	-
db_password	Sigur database user password	-	-
default_list_id	Luna List ID that Sigur will synchronize employees with	The ID of the list created in Luna	-
luna_id	Drop-down list with Luna service IDs in Access	-	-

Strazh

Strazh functionality

Supported software version of Strazh: 1.2.211201.648.

Performs replication of user data from the Strazh ACS to the specified Luna list and generates StrazhController controllers from the received list of devices for execution of entry or exit requests.

Strazh settings

The following settings are used when creating a new service:

Parameter	Description	Values	Default value
name	Service name specified by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
luna_id	Drop-down list with Luna service IDs in Access	-	-
default_list_id	Luna List ID that Strazh will synchronize employees with	The ID of the list created in Luna	-
login	Strazh user login	The user created in Strazh	-
password	Strazh user password	User password	-
host	IP address of the server where Strazh is installed	IP address in the form of X.X.X.X.	-
port	Port of the server where Strazh is deployed	-	443
enable_ssl	Network connection type	On - https	Off
		Off - http

Configuration of Strazh ACS software

Follow these steps to set up the software:

1․ Add the parameter "Travel confirmation by an external system" at the passage point.

2․ Add the parameter "Maximum waiting time for confirmation of passage by an external system, sec.

3․ Adjust the timeout for waiting for an external system response and the default solution if the system does not have time to process the request.

After that, when trying to pass through this point with a card whose privilege level is less than the privilege level of the point, an event with type access_confirmation and data will be sent through the SSE mechanism in the form of a JSON object with the request and response fields. The request contains a request for a hike, the response contains a preliminary decision of the ACS on the possibility of a hike (i.e. a decision after standard checks of the profile, schedule, etc.). Next, the ACS expects that it will be sent a decision on the campaign by HTTP POST to /access_confirmation indicating the UUID of the request and the decision to let it in or not. Regardless of the ACS solution, the external system may or may not let it in in response.

Controllers

Controllers are required to work with controllers from different manufacturers for communication between VisionLabs systems and access control devices from other manufacturers.

Controller list:

Name	Comment
GateController
LaurentController
PercoController
PusrController
StrazhController

Gate controller

Driver to work with Gate Ethernet-Wiegand converter.

The module is not a complete standalone solution. The purpose of the module is to connect the face recognition system with the converter.

The code of the user's personal card (facility & card number) or its decimal representation is transferred to the adapter.

Gate controller functionality

A specialized Gate-Ethernet/Wiegand interface converter (version 2) is used to connect recognition servers (face, vehicle registration plate or other identification feature) to the ACS controller using a special protocol. The converter provides reception of a code message via the Ethernet network from the recognition server, decoding of the received message and issuance of an identifier code to the required Wiegand input of the ACS controller. The converter is configured using a special utility — a program running under the Windows operating system. The program sets the initial IP address of the device and other communication Parameters.

The GateController controller is designed to work with the GateEthernetWiegand converter, which can be used to send the Wiegand format card number to the controller. To run the controller, specify IP, port, and component identifiers to the corresponding device outputs in order to understand which direction to open when receiving detections from devices.

Gate controller settings

The following settings are used when creating a new controller:

Parameter	Description	Values	Default value
name	Device name specified by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
group	List name for grouping components	Any numeric or text values	-
host	IP address of the server where Gate is installed	IP address in the form of X.X.X.X	-
port	Port of the server where Gate is deployed	-	-
entry_source	The name of the event source, expected as the source of the event bound to the card reader 0	Any textual names. Latin and Cyrillic input is supported. It is not recommended to enter more than 30 characters.	-
exit_source	The name of the event source, expected as the source of the event bound to the card reader 1	Any textual names. Latin and Cyrillic input is supported. It is not recommended to enter more than 30 characters.	-
retry_entry_sleep_interval	Pause interval between passages (in seconds).The greater the flow of people, the longer the pause should be	1...10	7
min_face_similarity	The minimum face similarity threshold when performing verification	The value is formed at the design stage and corrected at the testing stage (0,00...1,00)	0,7
use_second_card	The flag for using a key card for authorization.	On - use,	Off
	Off - do not use

Laurent controller

The Laurent2 controller is designed to control and manage access together with the Luna Cars service.

• Supported devices: Laurent2.
• Supported firmware versions: L206.

Laurent controller settings

The following settings are used when creating a new controller:

Parameter	Description	Values	Default value
name	Device name specified by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
group	List name for grouping components	Any numeric or text values	-
host	IP address of the server where Gate is installed	IP address in the form of X.X.X.X	-
port	Port of the server where LUNA CARS Analytics Backend is deployed	-	-
delay_time	Relay pen time (sec)	1...10	-

PERCo controller

The PERCo controller is generated automatically during the operation of the PERCo-Web service from the devices received at startup. To use it, you must manually enter the entry_source and exit_source values ​​for each of the created controllers.

PERCo controller settings

The following settings are used when creating a new controller:

Parameter	Description	Values	Default value
name	Device name specified by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
group	List name for grouping components	Any numeric or text values	-
perco_web_id	PercoWEB service instance ID in Access	-	-
external_controller_id	Unique ID of the device used in the integration. Specified in Access	-	-
description	Additional field for entering a description of the passage point	Russian and Latin characters are supported. It is not recommended to enter more than 50 characters	-
entry_source	The name of the event source, expected as the source of the event bound to the card reader 1	Any textual names. Latin and Cyrillic input is supported. It is not recommended to enter more than 30 characters.	-
exit_source	The name of the event source, expected as the source of the event bound to the card reader 2	Any textual names. Latin and Cyrillic input is supported. It is not recommended to enter more than 30 characters.	-

Pusr controller

The controller is designed to work with the WGNetConverter converter, which can be used to send the Wiegand format card number to the controller.

• Supported devices: WG-TCP
• Supported firmware: V6005

It is important that the converter is in TCP Server mode. To do this, during the initial setup, select the appropriate Work Mode in the web interface in the Serial Port section.

Pusr controller settings

The following settings are used when creating a new controller:

Parameter	Description	Values	Default value
name	Device name specified by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
group	List name for grouping components	Any numeric or text values	-
host	IP address of the server where Pusr is installed	IP address in the form of X.X.X.X	-
port	Port of the server where Pusr is deployed	-	-
entry_source	The name of the event source, expected as the source of the event bound to the card reader 1	Any textual names. Latin and Cyrillic input is supported. It is not recommended to enter more than 30 characters.	-
exit_source	The name of the event source, expected as the source of the event bound to the card reader 2	Any textual names. Latin and Cyrillic input is supported. It is not recommended to enter more than 30 characters.	-
retry_entry_sleep_interval	Pause interval between passages (in seconds).The greater the flow of people, the longer the pause should be	1...10	5
use_second_card	The flag for using a key card for authorization.	On - use	Off
	Off - do not use
min_face_similarity	The minimum face similarity threshold when performing verification	The value is formed at the design stage and corrected at the testing stage (0,00...1,00)	0,7

Salto controller

The Salto controller is generated automatically when the Salto service is running from the received pass points. For use and operation, after generation, it is necessary to manually enter the entry_source value for each of the created controllers.

Salto controller settings

The following settings are used when creating a new controller:

Parameter	Description	Values	Default value
name	Device name specified by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
group	List name for grouping components	Any numeric or text values	-
salto_id	Salto service instance ID in Access	-	-
external_controller_id	Unique ID of the device used in the integration. Specified in Access	-	-
entry_source	The name of the event source, expected as a source event bound to the door	Any textual names. Latin and Cyrillic input is supported. It is not recommended to enter more than 30 characters.	-
retry_entry_sleep_interval	Pause interval between passages (in seconds).The greater the flow of people, the longer the pause should be	1...10	5

Strazh controller

Strazh controller settings

The Strazh controller is generated automatically when the Strazh service is running from the devices received at startup. After generation, it is necessary to manually enter the source value for each of the created controllers.

The following settings are used when creating a new controller:

Parameter	Description	Values	Default value
name	Device name specified by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
group	List name for grouping components	Any numeric or text values	-
strazh_id	Strazh service instance ID in Access	-	-
external_controller_id	Unique ID of the device used in the integration. Specified in Access	-	-
second_factor_expiry_time	Time limit in seconds to receive the second factor when using two-factor authentication. It is not recommended to set the limit to more than 10 seconds.	0...10	-
entry_source	The name of the event source, expected as the source of the event bound to the card reader A	Any textual names. Latin and Cyrillic input is supported. It is not recommended to enter more than 30 characters.	-
exit_source	The name of the event source, expected as the source of the event bound to the card reader B	Any textual names. Latin and Cyrillic input is supported. It is not recommended to enter more than 30 characters.	-

Devices

To perform hardware-software integration of LP5/LUNA CARS for access control, it is necessary to use devices - a terminal, cameras, etc.

Beward terminal

The biometric terminal with temperature measurement, mask detection, and built-in relay.

• Supported devices: TFR80-210T1Q / TFR80-210.
• Supported firmware versions: 1.2.13.0 / 2.1.6.0.

Beward settings

The following settings are used when creating a new device:

Parameter	Description	Values	Default value
name	Device name specified by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
handler_id	UUID of the passage event handler, created in Luna	-	-
group	List name for grouping components	Any numeric or text values	-
host	IP address of the server where Beward is installed	IP address in the form of X.X.X.X	-
port	Port of the server where Beward is deployed	-	-
login	Beward user login	The user created in Beward	-
password	Beward user password	User password	-
open_door_time	Relay closing time in milliseconds	The time is taken from the relay manual	2000
vl_access_host	IP address of the server where Access is installed	IP address in the form of X.X.X.X	-
vl_access_port	Port of the server where Access is deployed	-	9091
event_expiry_time	Event validity time (in seconds).It is necessary to reduce the time, with a large flow of people, as the device cache may overflow	10...100	60
min_face_similarity	Minimum face similarity threshold when performing verification	The value is formed at the design stage and corrected at the testing stage (0,00...1,00)	0,7
successful_pass_message_template	Message on successful identification. To display the username on the terminal screen upon successful identification, you must use the full name variables. The order of words in the greeting message can be any.	Any text names and Full name variables. Only Latin characters are supported. It is not recommended to enter more than 33 characters	Welcome!
unsuccessful_pass_message_template	Message on unsuccessful identification. To display the username on the terminal screen upon successful identification, you must use the full name variables. The order of words in the greeting message can be any.	Any text names. Only Latin characters are supported. It is not recommended to enter more than 33 characters	Face is not identified

BioSmart Quasar terminal

• Supported devices: BioSmart Quasar.
• Supported firmware versions: 2.3.0.46.

BioSmart Quasar settings

The following settings are used when creating a new device:

Parameter	Description	Values	Default value
name	Device name specified by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
handler_id	UUID of the passage event handler, created in Luna	-	-
group	List name for grouping components	Any numeric or text values	-
host	IP address of the server where Quasar is installed	IP address in the form of X.X.X.X	-
port	Port of the server where Quasar is deployed	-	80
luna_id	Drop-down list with Luna service IDs in Access	-	-
score	Minimum face similarity threshold when performing verification	The value is formed at the design stage and corrected at the testing stage (0,00...1,00)	0,7

To subscribe to events, go to “Settings” on the terminal → go to “Server Identification” → select the server type: BioSmartLite → enter the endpoint for sending data: http://server_IP/vl-access/webhook/biosmart/ → save the settings.

The device does not generate events and does not put anything in the queue. Requests to Luna are sent directly from endpoints.

Dahua camera

Some models of Dahua cameras have a relay and the ability to control it programmatically.

During the implementation of the project, LP5 is integrated with this functionality, which allows to control the relay when a face from a certain list appears in the frame.

For example, it is possible to send a signal to an electronic door lock so that the door opens or does not open.

The device starts a stream connection, generates, and puts a face detection event in the queue.

Dahua settings

The following settings are used when creating a new device:

Parameter	Description	Values	Default value
name	Device name specified by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
handler_id	UUID of the passage event handler, created in Luna	-	-
group	List name for grouping components	Any numeric or text values	-
device_id	Internal ID of the device. Specified in the device settings	-	-
host	Dahua camera IP address	IP address in the form of X.X.X.X	-
port	Port for connecting to Dahua camera	-	-
login	Dahua user login	The user created in Beward	-
password	Dahua user password	User password	-

Dahua Thermo camera

Some models of Dahua cameras have a relay and the ability to control it programmatically.

During the implementation of the project, LP5 is integrated with this functionality, which allows to control the relay when a face from a certain list appears in the frame.

For example, it is possible to send a signal to an electronic door lock so that the door opens or does not open.

• Supported system version: 2.631.0000000.31.T, build date 2020-07-06.

The device starts an HTTP stream connection to the thermal imaging camera and captures faces by sending a thermal detection event of the face to the queue.

Dahua Thermo settings

The following settings are used when creating a new device:

Parameter	Description	Values	Default value
name	Device name specified by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
handler_id	UUID of the passage event handler, created in Luna	-	-
group	List name for grouping components	Any numeric or text values	-
host	IP address of Dahua Thermo camera	IP address in the form of X.X.X.X	-
port	Port for connecting to Dahua Thermo camera	-	-
login	Dahua Thermo user login	The user created in Beward	-
password	Dahua Thermo user password	User password	-
timeout	Timeout for an unsuccessful attempt to connect to the service. It is necessary to increase the time if there is a large delay between servers	The time is selected based on the delay in the network to maintain performance	-

Fortuna315 thermal imaging camera

Generates Thermo events in the SendThermalEventToLuna queue based on the received data from devices. Includes paired devices — thermal imaging camera and camera.

Supported firmware versions of the camera: V4.02.00, the camera thermal imaging camera: 2.20.0.0.R26130.alpha8 V1.0. Supported hardware versions: V1.0. Supported algorithm versions: smart2.0.0-06-2020.06.17.16:06:42.

Fortuna315 settings

To subscribe to events, create a device with the following settings:

Parameter	Description	Values	Default value
name	Device name specified by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
handler_id	UUID of the passage event handler, created in Luna	-	-
group	List name for grouping components	Any numeric or text values	-
device_id	Internal ID of the device. Specified in the device settings	-	-
host	IP address of Dahua Thermo camera	IP address in the form of X.X.X.X	-
port	Port for connecting to Dahua Thermo camera	-	-
thermo_host	IP address of the Dahua Thermo thermal imaging camera	IP address in the form of X.X.X.X	-
thermo_port	Port of the Dahua Thermo thermal imaging camera	-	-

HikvisionCamera camera

A camera for generating a video stream for LP5 with subsequent integration with ACS.

• Supported devices: DS-2CD3126G2-IS.
• Supported firmware versions: V5.5.134 build 200430.

The device generates events of type FaceDetectionEvent.

HikvisionCamera settings

To subscribe to events, create a device with the following settings:

Parameter	Description	Values	Default value
name	Device name specified by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
handler_id	UUID of the passage event handler, created in Luna	-	-
group	List name for grouping components	Any numeric or text values	-
host	IP address of the HikvisionCamera camera	IP address in the form of X.X.X.X	-
port	Port for connecting to HikvisionCamera camera	-	-
login	HikvisionCamera user login	User created to access the device	-
password	HikvisionCamera user password	User password	-
timeout	Timeout for an unsuccessful attempt to connect to the service. It is necessary to increase the time if there is a large delay between servers	The time is selected based on the delay in the network to maintain performance	10

HikvisionCameraThermo camera

A camera with temperature measurement and data transfer functions in LP5.

• Supported devices: DS-2CD3126G2-IS.
• Supported firmware versions: V5.5.134 build 200430.

Events in the queue are of type ThermalEvent.

HikvisionCameraThermo settings

To subscribe to events, create a device with the following settings:

Parameter	Description	Values	Default value
name	Device name specified by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
handler_id	UUID of the passage event handler, created in Luna	-	-
group	List name for grouping components	Any numeric or text values	-
host	IP address of the HikvisionCameraThermo camera	IP address in the form of X.X.X.X	-
port	Port for connecting to HikvisionCameraThermo camera	-	-
login	HikvisionCameraThermo user login	User created to access the device	-
password	HikvisionCameraThermo user password	User password	-
timeout	Timeout for an unsuccessful attempt to connect to the service. It is necessary to increase the time if there is a large delay between servers	The time is selected based on the delay in the network to maintain performance	10

HikvisionRecognitionOnBoard terminal

The biometric terminal with recognition function.

• Supported devices: DS-K1T341AMF, DS-K1T341AM, DS-K1T680D-E1.
• Supported firmware versions: V3.2.30 build 220210.

Events in the queue are of type FaceDetectionEvent.

HikvisionRecognitionOnBoard settings

To subscribe to events, create a device with the following settings:

Parameter	Description	Values	Default value
name	Device name specified by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
handler_id	UUID of the passage event handler, created in Luna	-	-
group	List name for grouping components	Any numeric or text values	-
host	IP address of the HikvisionRecognitionOnBoard camera	IP address in the form of X.X.X.X	-
port	Port for connecting to HikvisionRecognitionOnBoard camera	-	-
login	HikvisionRecognitionOnBoard user login	User created to access the device	-
password	HikvisionRecognitionOnBoard user password	User password	-
vl_access_host	IP address of the server where Access is installed	IP address in the form of X.X.X.X	-
vl_access_port	Port of the server where Access is deployed	-	9091
luna_id	Drop-down list with Luna service IDs in Access	-	-
default_list_id	Luna List ID that HikvisionRecognitionOnBoard will synchronize employees with	The ID of the list created in Luna	-
recognition_interval	Interval between the start of recognition. It is set depending on the flow of people	1...10	1
event_expiry_time	Event validity time (in seconds). It is necessary to reduce the time, with a large flow of people, as the device cache may overflow	10...100	60

HikvisionTerminalThermo terminal

The biometric terminal with temperature measurement, mask detection, and built-in relay.

Only events of the AccessControllerEvent type (having a measured temperature) will be processed, events of this type come from the terminal.

Events in the queue are of type ThermalEvent.

Hikvision terminal with temperature measurement function.

• Supported devices: DS-K1TA70MI-T, DS-K1T671TM-3XF, DS-K5671-3XF/ZU.
• Supported firmware versions: V3.2.32 build 210525.

HikvisionTerminalThermo settings

To subscribe to events, create a device with the following settings:

Parameter	Description	Values	Default value
name	Device name specified by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
handler_id	UUID of the passage event handler, created in Luna	-	-
group	List name for grouping components	Any numeric or text values	-
host	IP address of the HikvisionTerminalThermo camera	IP address in the form of X.X.X.X	-
port	Port for connecting to HikvisionTerminalThermo camera	-	-
login	HikvisionTerminalThermo user login	User created to access the device	-
password	HikvisionTerminalThermo user password	User password	-
event_expiry_time	Event validity time (in seconds).It is necessary to reduce the time, with a large flow of people, as the device cache may overflow	10...100	60
recognition_interval	Interval between the start of recognition.It is set depending on the flow of people	1...10	1
liveness_level	Degree of checking the level of liveness	low— fast processing speed, accuracy is reduced;	low
		middle — average processing speed and recognition accuracy;
		high — accurate definition, increased resource consumption
attempts_check_liveness	Number of attempts to pass the liveness check.It is necessary to increase the number of verification attempts at complex angles and shooting conditions in order to avoid false positive recognitions	5...15	10
vl_access_host	IP address of the server where Access is installed	IP address in the form of X.X.X.X	-
vl_access_port	Port of the server where Access is deployed	-	9091
successful_pass_message	Message on successful identificationTo display the username on the terminal screen upon successful identification, you must use the special flag. The order of words in the greeting message can be any. Any text names.	Any text names and Full name variables. Only Latin characters are supported. It is not recommended to enter more than 50 characters.	Welcome
unsuccessful_pass_message_template	Message on unsuccessful identification. To display the username on the terminal screen upon successful identification, you must use the full name variables. The order of words in the greeting message can be any.	It is not recommended to enter more than 50 characters	Face is not identified
light_brightness_led	Brightness level of the LED backlight. The darker the area in front of the terminal, the brighter the backlight should be	0...100	50
light_brightness_ir	Brightness level of the infrared (IR) illumination. The darker the area in front of the terminal, the brighter the illumination should be	0...100	50

LunaFast4A1 terminal

The biometric terminal with recognition function.

• Supported devices: DS-K1T680D-E1, DS-K1T341AMF, DS-K1T341AM, VL LUNA FAST 4A1, VL LUNA FAST 8A1, 671, DS-K1T671M, ACT-T1341M.
• Supported firmware versions: V3.2.30 build 210415, V3.2.30 build 210525, V3.2.30 build 210526, V3.2.30 build 210812, V3.2.30 build 211025, V3.2.30 build 220607, V3.2.30 build 220803, V3.2.30 build 221027, V3.2.33 build 210816, V3.2.35 build 220415, V3.2.35 build 220817.

Events in the queue are of type FaceDetectionEvent.

To disable the output of the greeting on the terminal screen, you must disable the LunaEventListener pipeline.

LunaFast4A1 settings

To subscribe to events, create a device with the following settings:

Parameter	Description	Values	Default value
name	Device name specified by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
handler_id	UUID of the passage event handler, created in Luna	-	-
group	List name for grouping components	Any numeric or text values	-
host	IP address of the LunaFast4A1 camera	IP address in the form of X.X.X.X	-
port	Port for connecting to the LunaFast4A1 terminal	-	-
login	LunaFast4A1 user login	User created to access the device	-
password	LunaFast4A1 user password	User password	-
event_expiry_time	Event validity time (in seconds).It is necessary to reduce the time, with a large flow of people, as the device cache may overflow	Values > 0	60
card_recognition_interval	Interval between card recognitions	0...10	3
face_recognition_interval	Interval between recognizing images with faces	1...10	3
liveness_level	The degree of checking the level of liveness	low— fast processing speed, accuracy is reduced;	low
		middle — average processing speed and recognition accuracy;
		high — accurate definition, increased resource consumption
attempts_check_liveness	Number of attempts to pass the liveness check.It is necessary to increase the number of verification attempts at complex angles and shooting conditions in order to avoid false positive recognitions	Values > 0	10
vl_access_host	IP address of the server where Access is installed	IP address in the form of X.X.X.X	-
vl_access_port	Port of the server where Access is deployed	-	9091
successful_pass_message	Message on successful identificationTo display the username on the terminal screen upon successful identification. The order of words in the greeting message can be any. Any text names.	Any text names and Full name variables. It is not recommended to enter more than 50 characters.	Welcome
		Full name example: Welcome, {fullname}.
unsuccessful_pass_message_template	Message on unsuccessful identification. To display the username on the terminal screen upon successful identification, you must use the full name variables. The order of words in the greeting message can be any.	Only Latin characters are supported. It is not recommended to enter more than 50 characters	Face is not identified
light_brightness_led	Brightness level of the LED backlight. The darker the area in front of the terminal, the brighter the backlight should be	0...100	50
light_brightness_ir	Brightness level of the infrared (IR) illumination. The darker the area in front of the terminal, the brighter the illumination should be	0...100	50

Panda thermal imaging camera

A thermal imaging camera with face recognition.

• Supported devices: SN-T5/13, SN-F22-13.
• Supported firmware versions: v3.6.0825.1004.1.0.23.0.0, v3.6.0840.1004.1.45.1.0.2.

Events in the queue are of type ThermalEvent.

Panda settings

To subscribe to events, create a device with the following settings:

Parameter	Description	Values	Default value
name	Device name specified by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
handler_id	UUID of the passage event handler, created in Luna	-	-
group	List name for grouping components	Any numeric or text values	-
host	IP address of the Panda camera	IP address in the form of X.X.X.X	-
port	Port for connecting to Panda camera	-	80

Go to the web interface of the device → sign in → go to the “Configuration” tab → select the “Network Service” section on the left panel → go to “CGI Alarm Service Center”.

Fill in the fields in the “CGIAlarm” section: assign endpoint as URL Start and URL End to send data to Access — http://:/vl-access/webhook/device/event/. If necessary, in the “Proxy Settings” section, fill in the Address and Port fields: Access host and Access port, respectively. Save settings after configuring.

RusguardTerminal

The biometric terminal with protective mask detection and centralized control.

• Supported devices: R20-Face-T8.
• Supported firmware versions: GD-V32.7267.

RusguardTerminal settings

The following settings are used when creating a new device:

Parameter	Description	Values	Default value
name	Device name specified by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
handler_id	UUID of the passage event handler, created in Luna	-	-
group	List name for grouping components	Any numeric or text values	-
host	IP address of the server where RusguardTerminal is installed	IP address in the form of X.X.X.X	-
port	Port of the server where RusguardTerminal is deployed	-	8080
password	RusguardTerminal user password	User password	-
vl_access_host	IP address of the server where Access is installed	IP address in the form of X.X.X.X	-
vl_access_port	Port of the server where Access is deployed	-	9091
event_expiry_time	Event validity time (in seconds).It is necessary to reduce the time, with a large flow of people, as the device cache may overflow		10
time_zone	Time zone	-12...+12	+3
successful_pass_message_template	Message on successful identification. To display the username on the terminal screen upon successful identification, you must use the full name variables. The order of words in the greeting message can be any.	Any text names and Full name variables. Only Latin characters are supported. It is not recommended to enter more than 33 characters	Welcome!
unsuccessful_pass_message	Message on unsuccessful identification. To display the username on the terminal screen upon successful identification, you must use the full name variables. The order of words in the greeting message can be any.	Any text names. Only Latin characters are supported. It is not recommended to enter more than 33 characters	Face is not identified

UniUbi terminal

The biometric terminal with temperature measurement, mask detection, and built-in relay control functions.

• Supported devices: Uface 8-C temp, Uface 8T temp, R20-Face-T8.
• Supported firmware versions: GD-V30.7219, GD-V32.7247, GD-V32.7267.

When using a terminal without measuring the temperature, you need to change the SentThermalEventToLuna pipeline to SendToLuna.

UniUbi settings

To subscribe to events, create a device of the UniUbi type.

The following settings are used when creating a new device:

Parameter	Description	Values	Default value
name	Device name specified by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
handler_id	UUID of the passage event handler, created in Luna	-	-
group	List name for grouping components	Any numeric or text values	-
host	IP address of the UniUbi terminal	IP address in the form of X.X.X.X	-
port	Port for connecting to the UniUbi terminal	-	-
password	UniUbi user password	User password	-
enabled_temp_mode	Temperature measurement mode. If disabled, change the SentThermalEventToLuna pipeline to SendToLuna.	On — enabled;	On
		Off — disabled
vl_access_host	IP address of the server where Access is installed	IP address in the form of X.X.X.X	-
vl_access_port	Port of the server where Access is deployed	-	9091
event_expiry_time	Event validity time (in seconds). It is necessary to reduce the time, with a large flow of people, as the device cache may overflow	10...100	60
time_zone	Time zone	-12...+12	+3
successful_pass_message_template	Message on successful identification. To display the username on the terminal screen upon successful identification, you must use the full name variables. The order of words in the greeting message can be any.	Any text names and Full name variables. Only Latin characters are supported. It is not recommended to enter more than 27 characters	Welcome
unsuccessful_pass_message	Message on unsuccessful identification	Any text names. Only Latin characters are supported. It is not recommended to enter more than 27 characters	Face is not identified

VKVision02 terminal

Terminal with functions of video recording and display of images on the screen.

• Supported devices: VANCOR VK VISION 02.

VKVision02 settings

The following settings are used when creating a new device:

Parameter	Description	Values	Default value
name	Device name specified by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
handler_id	UUID of the passage event handler, created in Luna	-	-
group	List name for grouping components	Any numeric or text values	-
host	IP address of the VKVision01 terminal	IP address in the form of X.X.X.X	-
port	Port for connecting to the VKVision01 terminal	-	-
enable_ssl	SSL encryption support for messages.Activate if privacy is required. When activated, the load on the device and the message transmission time increases	On — enabled;	Off
		Off — disabled
min_face_similarity	Minimum face similarity threshold when performing verification	The value is formed at the design stage and corrected at the testing stage (0,00...1,00)	0,7
success_status_image_ttl	Display time (ms) of the image on the terminal with the status “Success” (in seconds)	5000...20000	10000
success_status_image_ttl	Display time (ms) of the image on the terminal with the status “Denied” (in seconds)	5000...20000	10000
luna_id	Drop-down list with Luna service IDs in Access	-	-

Pipelines

Apacs2FA

The Apacs2FA pipeline implements custom two-factor authentication for the Apacs service. Listening to events that occurred when reading the card, as well as face detection events. They are matched by their source. When the first factor arrives with a certain source, then the second factor starts waiting, the time for waiting for it is set in the expiry_time setting, as soon as it is received, the validation of this pair begins.

• The similarity of the best matching candidate must not be lower than that specified in the min_similarity setting.
• The card number received from the reader must match the card number of the person in the Luna list.

Upon completion of the authentication procedure, the corresponding text is displayed on the screen of the device. After successful validation, the card number is sent to the corresponding output of the Gate Ethernet Wiegand controller.

To create a pipeline, you need to specify:

Parameter	Description	Possible values	Default value
name	Pipeline name set by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters.	-
luna_id	Dropdown list to select the Luna Service ID in Access.	-	-
apacs_id	Drop-down list to select the APACS service ID in Access.	-	-
expiry_time	Time limit in seconds to get the second factor.	0...10	5
min_face_similarity	Minimum face similarity threshold when performing verification.	The value is formed at the design stage and corrected at the testing stage.	0.00...1.00
unknown_card_message	Message when sending an unknown card to make an access decision.	Any text names. Only Latin characters are supported. It is not recommended to enter more than 50 characters.	The card has been read and sent to the controller
waiting_time_exceeded_message	Message when the second factor timed out	Any text names. Latin and Cyrillic input is supported. It is not recommended to enter more than 50 characters.	Timeout exceeded
access_denied_card	Card number of the user created to notify about unsuccessful passes. You must specify the number so that in the connected ACS you can see the log that the authorization failed.	-	None
use_cards_without_face	Using and sending to the controller cards that are not linked to faces	On - send	On
		Off - do not send

CreateBastionEvent

The pipeline listens to LunaEvent event queue in Luna and generates a BastionEvent event. Works with the Bastion ACS.

The following settings are used when creating a new pipeline:

Parameter	Description	Values	Default value
name	Pipeline name given by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
luna_id	Drop-down list with Luna service IDs in Access	-	-
bastion_id	The unique ID of the Bastion device used in the integration. Specified in Access.	-	-
min_face_similarity	Minimum face similarity threshold when performing verification	The value is formed at the design stage and corrected at the testing stage (0,00...1,00)	0,7
retry_delay_sec	Pause for reattempting the passage	1...15	5

Custome2FA

The Custom2FA pipeline implements custom two-factor authentication. Card swiping events are listened to, as well as regular face detection events. Events are matched by their source and saved to the mapping. When the first factor arrives with a specific source, the waiting for the second factor starts. The time for waiting for it is set in the expiry_time setting, as soon as it is received, the validation of this pair begins:

• the similarity of the best matching candidate must not be lower than that specified in the min_face_similarity setting;
• the card number received from the reader must match the card number of the face in the Luna list.

When the authentication procedure is completed, the corresponding text is displayed on the screen of the device. After successful validation, the card number is sent to the corresponding controller Gate Ethernet Wiegand output.

The following settings are used when creating a new pipeline:

Parameter	Description	Values	Default value
name	Pipeline name set by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters.	-
luna_id	Dropdown list to select the Luna Service ID in Access.	-	-
default_list_id	Identifier of the list of LP with which employees will be synchronized	Identifier of the list created in the LP.	-
expiry_time	Time limit in seconds to get the second factor.	0...10	5
min_face_similarity	The minimum quality value of a recognized face, at which identification will be carried out. The lower the quality, the higher the probability of false positives.	0.0...1.0	0.7
unknown_card_message	Message when sending an unknown card to decide on access	Any text names. Only Latin characters are supported. It is not recommended to enter more than 50 characters.	The card has been read and sent to the controller
waiting_time_exceeded_message	Message when the second factor timed out	Any text names. Latin and Cyrillic input is supported. It is not recommended to enter more than 50 characters.	Timeout exceeded
use_cards_without_face	Using and sending to the controller cards that are not linked to faces	On - send	On
		Off - do not send

LunaEventListener

LunaEventListener listens events from Luna generated by Luna internal service, FaceStream, or any other external software. Launches controllers of event components (event authors) or launches the functionality of controllers connected to components or taken by name.

The following settings are used when creating a new pipeline:

Parameter	Description	Values	Default value
name	Pipeline name given by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
luna_id	Luna service ID in the system	-	-
enable_fake_events	Handling requests with failed Liveness checks to view such events. For activation, the enable_fake_events parameter in the SendToLuna pipeline must be active	On - handle	Off
		Off - do not process

SendCarsToLaurent

A pipeline for sending events from LunaCars to Laurent. Listens to the Event event queue and generates SigurCarEvent events.

The following settings are used when creating a new pipeline:

Parameter	Description	Values	Default value
name	Pipeline name given by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
controller_id	UUID of Laurent controller in Access	-	-
relay_{N}_scenario_id	UUID Scenario in LUNA CARS Analytics, according to which the license plate is checked for the relay {N}.	-	-

SendCarsToSigur

A pipeline for sending events from LunaCars to Sigur. Listens to the Event event queue and generates SigurCarEvent events. The following settings are used when creating a new pipeline:

Parameter	Description	Values	Default value
name	Pipeline name given by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-

SendThermalEventToLuna

Listens to the heat detection event queue and generates events in Luna. To launch, specify the component_id of the Luna service running in the system. The pipeline works with several lists: default list and blacklist. It distributes the received data between lists depending on the set thresholds for the lower and upper temperature values.

The following settings are used when creating a new pipeline:

Parameter	Description	Values	Default value
name	Pipeline name given by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
luna_id	Luna service ID in the system	-	-
handler_id	UUID of the passage event handler, created in Luna	-	-
default_list_id	Luna list ID with which the device will synchronize people who have access (optional)	The ID of the list created in Luna	-
black_list_id	Luna list ID with which the device will synchronize people who are denied access (optional)	The ID of the list created in Luna	-
to_high_temperature	The upper threshold of a person's temperature at which a person cannot be allowed to pass	3## 37
to_low_temperature	The lower threshold of a person's temperature at which a person cannot be allowed to pass	3## 35
use_lists		On — match;	On
		Off — do not match
min_face_similarity	Minimum face similarity threshold when performing verification	The value is formed at the design stage and corrected at the testing stage (0,00...1,00)	0,89

SendToBars

Listens to the LunaEvent, DoorEvent event queues and generates the BarsEvent event.

The following settings are used when creating a new pipeline:

Parameter	Description	Values	Default value
name	Pipeline name given by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
luna_id	Drop-down list with Luna service IDs in Access	-	-
bars_host	IP address or network name of the PC with installed Bars server	-	-
bars_port	Bars server port
retry_delay_sec	Pause for reattempting the passage	1...10	5
min_face_similarity	Minimum face similarity threshold when performing verification	The value is formed at the design stage and corrected at the testing stage (0,00...1,00)	0,7

SendToLuna

The pipeline sends the received FaceDetectionEvent events to Luna.

The following settings are used when creating a new pipeline:

Parameter	Description	Values	Default value
name	Pipeline name given by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
luna_id	Luna service ID in the system	-	-
enable_fake_events	Submitting faces with failed liveness to view Liveness hack attempts. To activate, the enable_fake_events parameter in the LunaEventListener pipeline must be active	On - send	Off
		Off - do not send

SendToParsec

Listens to LunaEvent event queue in Luna and generates the ParsecEvent event.

The following settings are used when creating a new pipeline:

Parameter	Description	Values	Default value
name	Pipeline name given by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
luna_id	Drop-down list with Luna service IDs in Access	-	-
parsec_id	Unique ID of the Parsec device used in the integration.Specified in Access	-	-
retry_delay_sec	Pause for reattempting the passage	1...10	5
min_face_similarity	Minimum face similarity threshold when performing verification	The value is formed at the design stage and corrected at the testing stage (0,00...1,00)	0,7

SendToPerco

The pipeline listens to the LunaEvent event queue, in case of successful validation of the face in the event, it sends a request to the PercoWeb service to grant access.

When creating a new pipeline, the following settings are used:

Parameter	Description	Possible values	Default value
name	Pipeline name set by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters.	-
min_face_similarity	Minimum face similarity threshold when performing verification.	The value is formed at the design stage and corrected at the testing stage.	0.00...1.00

SendToSalto

Listens to the queue of LunaEvent, in case of successful face validation from the event, sends request to the Salto service to pass through the access point and displays the result of successfull/unsuccessfull pass on the screen of device.

When creating a new pipeline, the following settings are used:

Parameter	Description	Possible values	Default value
name	Pipeline name set by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters.	-
min_face_similarity	Minimum face similarity threshold when performing verification.	The value is formed at the design stage and corrected at the testing stage.	0.00...1.00

SendToSigur

Listens to LunaEvent event queue in Luna and generates the SigurEvent event.

The following settings are used when creating a new pipeline:

Parameter	Description	Values	Default value
name	Pipeline name given by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
luna_id	Drop-down list with Luna service IDs in Access	-	-
sigur_id	Unique ID of the Sigur device used in the integration. Specified in Access	-	-
retry_delay_sec	Pause for reattempting the passage	1...10	5

SendToStrazh

If the controller is not in 2FA mode: Listens to the LunaEvent event queue, in case of successful face validation in the event, sends a request to the Strazh service to pass through the access point.

If the controller is in 2FA mode: Events that occurred when reading the card are listened to, as well as regular face detection events. They are matched by their source. When the first factor arrives with a certain source, then the second factor is waited for, the time for waiting for it is set in the second_factor_expiry_time setting, as soon as it is received, the validation of this pair begins.

The following settings are used when creating a new pipeline:

Parameter	Description	Values	Default value
name	Pipeline name given by the user	Any text names. Only Latin characters are supported. It is not recommended to enter more than 30 characters	-
strazh_id	Dropdown list to select Strazh service ID in Access.	-	-
min_face_similarity	Minimum face similarity threshold when performing verification	The value is formed at the design stage and corrected at the testing stage (0,00...1,00)	0,9
waiting_time_exceeded_message	Message when the second factor timed out	Any text names. Latin and Cyrillic input is supported. It is not recommended to enter more than 50 characters.	Timeout exceeded