Controllers#
Controllers are required to work with controllers from different manufacturers for communication between VisionLabs systems and access control devices from other manufacturers.
All fields are required unless otherwise stated in the description.
ApacsController#
The Apacs controller is generated automatically when the Apacs service is running from the received pass points. Up to 4 readers are supported.
Setting up parameters for connecting to the Apacs controller#
Controller settings and possible values:
| Parameter | Description | Possible values | Default value |
|---|---|---|---|
| name | User-defined device name | Any text names. Latin and Cyrillic characters are supported. It is not recommended to enter more than 30 characters. | - |
| group | Name of the list for grouping components | Any numeric and text values | - |
| apacs_id | ID of the Apacs instance in Access | - | - |
| external_controller_id | The unique identifier of the device used in the integration. Specified in Access. | - | - |
| retry_entry_sleep_interval | The pause interval between the passage in seconds, the larger the flow of people, the more there should be a pause. | 1 ...10 | 5 |
| first_reader_name | The name of the first kntroller reader | - | - |
| first_reader_id | ID of the first controller reader | - | - |
| first_source | Event source (camera or terminal) linked to the first reader | - | - |
| second_reader_name | The name of the second reader of the controller | - | - |
| second_reader_id | ID of the second controller reader | - | - |
| second_source | Event source (camera or terminal) linked to the first reader | - | - |
| third_reader_name | The name of the third reader of the controller | - | - |
| third_reader_id | ID of the third controller reader | - | - |
| third_source | Event source (camera or terminal) linked to the first reader | - | - |
| forth_reader_name | The name of the fourth reader of the controller | - | - |
| forth_reader_id | ID of the fourth reader of the controller | - | - |
| forth_source | Event source (camera or terminal) linked to the first reader | - | - |
Gate controller#
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 Ethernet-Wiegand converter#
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.
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 | - | 5000 |
| 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 |
LaurentController#
The Laurent2 controller is designed to control and manage access together with the Luna Cars service.
- Supported devices: Laurent2.
- Supported firmware versions: L212.
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 device | IP address in the form of X.X.X.X | - |
| port | Port of the device | - | - |
| password | Controller password | - | -4 |
| enable_ssl | Method of encrypting data during transmission over the network. Depends on the network type in the solution. | On - https | Off |
| Off - http | |||
| delay_time | Relay pen time (sec) | 1...10 | - |
PercoСontroller#
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.
PercooСontroller 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. | - |
PusrController#
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 |
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 | Drop-down list for selecting 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#
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.
Strazh 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 | - |
| 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. | - |