Application Note: Video - ANV102
LPR Setup and Configuration Guide
2026-02-26 Revision 4.0
This Application Note is intended for Brivo Eagle Eye Video administrators responsible for configuring License Plate Recognition (LPR) in the VMS and making significant VMS-related settings changes. Working knowledge of the VMS is required before making any changes to LPR configuration settings.
Eagle Eye License Plate Recognition (LPR) is a camera-agnostic LPR engine from Brivo. Using Brivo Eagle Eye LPR, any suitable ONVIF camera connected to a compatible bridge can function as an LPR camera. The LPR runs on the bridge, and the data is visualized in the VSP (Vehicle Surveillance Package) feature in Brivo Eagle Eye Video. This document discusses the basics of LPR camera setup, including how to install LPR functionality and the appropriate configuration for LPR cameras and software.
The Eagle Eye License Plate Recognition System (LPR) is an AI-powered, cloud-managed, highly accurate license plate recognition technology that works with any surveillance camera under challenging conditions, increasing business security and efficiency while lowering costs. LPR is a video analytics solution that enables reading vehicle license plate information from associated video data. See Figure 1.
Figure 1: Basic LPR workflow
The License Plate Recognition (LPR) system uses an AI-based model to accurately read license plates. This AI model ensures high detection rates without false or repeated reads, and high accuracy in reading both standard and non-standard number plates.
Brivo Eagle Eye LPR allows any standard ONVIF camera connected to Brivo Eagle Eye Video to run LPR, rather than requiring an LPR-specific camera. The LPR analytic runs on the Bridge, and data is viewed through the Vehicle Surveillance Package module of the VMS. See Figure 2.
Figure 2: Brivo Eagle Eye LPR Architecture
Brivo Eagle Eye LPR is supported only on specific bridges. See Table 1 for supported bridges/CMVRs and their camera limits.
Table 1: Supported Hardware and Number of Cameras
The number of supported cameras changes when LPR is activated. Reference the latest datasheet and discuss with your sales representative before purchasing.
Number of additional analytics supported on the same bridge running LPR.
Find the LPR Product feature datasheet here.
Table 2 below provides the minimum recommended specifications for the cameras in each use case.
Recommended Brivo Eagle Eye LPR cameras are available here.
Brivo Eagle Eye LPR supports two types of integration to the Access control system:
For using BRIVO as the Access Control System, you will need the following accessories.
RS-485 USB Converter, available here.
Shielded Twisted Pair Cable.
Brivo-compatible panels, which can be found here.
For using MOXA to control the Access Control System, you will need the following accessories.
Moxa ioLogix E1214, available here.
Use the checklists in this section to ensure correct LPR installation.
Part 1: Before Installation
Part 2: After Installing the Camera and Bridge/CMVR
The right camera choice is crucial for achieving high accuracy in LPR reads. Factors such as resolution, lens, image enhancement, and Infrared (IR) power determine the quality of the imaging. The major factors in camera choice are the distance from the camera to the vehicle license plate capture position, and the width of the lane. These two factors affect the choice of lens and IR power. The greater the distance from the camera to the vehicle imaging area, the higher the need for increased zoom and higher-power IR.
Similar to camera choice, proper camera installation determines the success of license plate reads. Factors such as the imaging angle, installation height, and pan angle affect LPR accuracy. If local law requires license plates on the front of vehicles, install cameras to read these plates. Front plates deliver better results because the camera can track the vehicle across multiple frames as it approaches, capturing the best possible image. Also, the distance between the camera and the vehicle is always the same for front plates. To read rear license plates, the trigger point has to be chosen based on the longest vehicle, which may not be optimal for all vehicles. Optimal camera placement varies by site, depending on the layout and camera mounting location (ground, ceiling, wall, etc.).
If motorcycles are to be captured, rear license plates are preferred, as many do not have front plates; if present, the plates are typically much smaller than those of typical vehicles. The mounting varies by application. See below for the preferred mounting suggestions to achieve optimal imaging and the best LPR reading.
See Table 2 and Figure 3 below for gated installation specifications and setup.
Note: The maximum distance from the camera to the plate is 4 meters/12 feet.
Table 2: Gated Installation Specifications
Figure 3: LPR setup for gated installation
Figure 4 shows an example of a front license plate capture in a front-facing camera installation for gated LPR.
Figure 4: Front License Plate Capture Example
Figure 5 shows example images from a rear-facing camera installation for gated LPR.
Figure 5: Rear license plate capture examples
See Table 3 and Figure 6 below for gate/street installation specifications and setup. Installation recommendations apply for both front and rear LP capture.
Note: The maximum distance from the camera to the plate is 15 meters/50 feet
Table 3: Gate/Street Installations
Figure 6: LPR setup for gate/street installation
Figure 7 shows an example of a front license plate capture in a front-facing camera installation for street LPR.
Figure 7: Reference image from an LPR for street installation
The angle of camera installation is crucial for LPR to avoid license plate readings at an acute angle.
Vertical angle: The camera should always be angled downward to prevent sunlight and car headlights from falling directly on it, and to ensure rain or snow droplets do not fall onto the lens.
Pan angle: The camera's pan angle must be limited to 30°, as a wider view would affect the plate reading. See Figure 8 for an example.
Figure 8: Representation of pan angle and distance from the road to the camera installation pole
After mounting cameras, it is necessary to make tilt and rotation adjustments to ensure that the license plate is centered and horizontally oriented when the vehicle is at the ideal capture distance. To do this:
Position a vehicle in the middle of the lane. Look at the camera view and tilt it so the license plate is centered.
Rotate the camera to ensure that the license plate is horizontally aligned with the image. It may be harder to determine which is horizontal, so use a speed bump or a gate entry barrier as a reference.
After positioning the vehicle in the preferred capture area and tilting the camera, the camera view indicates that the license plate is centered. See Figure 9 for an example.
Figure 9: Reference image to ensure that the camera is centered for optimal performance
Table 4 below covers camera specifications that will help to get optimal readings for license plates in each use case.
Table 4: Additional camera specifications
*FPS of the camera and LPR processing FPS to be the same for optimized performance
Ideally, the LPR camera should be configured to capture in color during both daytime and nighttime. So that the vehicle color can be captured correctly during both day and night conditions. See Figure 10 for an example.
Figure 10: Images from a camera that runs on color during the day and night. Vehicle attributes such as Make are also visible here.
Often, at night or when the camera is indoors, there is insufficient external light to capture number plates clearly and brightly. In that case, the camera is set up with two configurations: one for daylight in normal color mode, and the second during the night in IR mode (black and white). See Figure 11 for examples of day and night modes.
Figure 11: a) Daytime - Color mode, b) Nighttime - Night (IR) mode
However, suppose LPR performance is affected by poor imaging, especially during dawn or dusk hours when the camera is incorrectly switched from day to night mode. In that case, we recommend keeping black-and-white (IR mode) active at all times. If the camera fails to switch to night mode when required or does not support two modes of operation, you may need to configure it for full-time IR mode operation. See Figure 12 for an example of the IR mode used during the daytime.
Figure 12: LPR detection using monochrome (IR mode) during daytime
A camera's ability to capture vehicle attributes, such as the vehicle's make or body type, at night depends on ambient light. In many circumstances, night-view images will show only the license plate. See Figures 13 and 15 for examples of license plate capture during no-light (zero lux) or low-light environments.
Figure 13: License plate capture at night under a zero-lux environment
Figure 14: Both the license plate and vehicle make are visible in this IR mode image, due to sufficient light from an external source
As mentioned previously, capturing the color of a vehicle at night or in indoor conditions requires sufficient illumination (from external sources) so that the camera does not need to switch to IR at any point when capturing license plate numbers. Capturing the vehicle's color while the camera is in IR mode is not possible.
Follow the steps below to ensure you have the proper setup. You should perform these steps in both day and night environments. These settings are configured on the camera separately; LPR does not do any auto-configuration.
Park a vehicle in the camera’s view and adjust the settings as described in this application note.
Adjust the settings to have the optimal image quality. Exposure should be limited, as noted in Table 4 under Camera Settings above.
Drive the vehicle at the maximum speed expected at the site and ensure there is no motion blur.
Adjust the gain as required to have clear images of the plates.
Verify the results for the next 24 hours and adjust the settings as needed to ensure all plates are clearly visible.
This section explains the basic LPR analytics configurations for both Bridge and Cloud deployments. While LPR on Bridge offers additional configurations, these are specific to access control and webhook integrations and will be covered in a later section, as they are not part of the basic setup.
Brivo Eagle Eye LPR is configured completely from within the VMS.
Navigate to the Camera Settings for your LPR camera.
Click the Analytics tab.
You should see License Plate Recognition listed there.
Enable License Plate Recognition (LPR) and select your preferred LPR option based on where you want to run it, either locally on the Bridge/CMVR or in the Eagle Eye Cloud.

Figure 15: Analytics Settings
Based on your selection, the corresponding settings will appear below.
Figure 16: License Plate Recognition Settings on Bridge
To view the LPR results, go to the VSP section in the VMS and select the Events page, where all detected license plates will be listed. If you have multiple LPR cameras enabled, filter events by camera.
Figure 19: VSP Events Page
This section provides information about integrating LPR with Brivo and Moxa access control systems.
Integrating Brivo Eagle Eye LPR with Brivo Access enables License Plate Credentials for automated access management of parking facilities. This is achieved by implementing LPR technology, which captures license plate information, to authorize entry for registered vehicles or generate alerts for unauthorized vehicles.
In access control systems, credentials serve as authentication mechanisms for granting access to secured areas. Traditional examples include physical badges, keyfobs, and mobile credentials. For customers utilizing both Brivo and Eagle Eye systems, the option to employ a vehicle’s license plate as a credential is available. The License Plate Credential procedure is detailed in the following sections.
Users must register the vehicle license plate within the Brivo Access platform. The registered license plate is then converted into a credential and stored in the Brivo Panel for authentication. See Figure 20.
Figure 20: Brivo access workflow
Brivo Eagle Eye LPR operates on the Bridge/CMVR, where captured license plate data is converted into a credential. This credential is transmitted to the Brivo Panel via the Open Supervised Device Protocol (OSDP). See Figure 21.
Figure 21: License plate transmission to the Brivo panel
The integration of Eagle Eye and Brivo operates locally, guaranteeing uninterrupted access control functionality during internet outages, with updates synchronized to the Eagle Eye Cloud upon restoration of connectivity.
Following the transmission of credentials from Eagle Eye, Brivo verifies them. Upon authorization confirmation, Brivo activates gate access based on the validated credential status.
The Eagle Eye and Brivo systems are physically connected via a serial interface using the OSDP protocol. This connection requires a USB-to-RS485 converter and an interface between the Eagle Eye Bridge/CMVR and the panel.
RS485 - Reference Product: Link
Note:
Ensure that Shielded Twisted Pair (STP) cables are used for the connection. It's essential to cross-verify this directly with the technician on-site. If STP cables are not used, this may lead to connectivity issues due to external interference or signal degradation. Such problems can be intermittent and challenging to diagnose or troubleshoot remotely through the Bridge or CMVR. Using proper STP cabling helps maintain stable and consistent communication between devices. See Figure 22.
Figure 22: STP Cable reference image
The distance between the Eagle Eye Bridge/CMVR and the Brivo Panel should be less than 1 meter. If the cable length exceeds 1 meter, it can affect connectivity due to signal loss, making it more challenging to diagnose remotely via Bridge/CMVR. See Figure 23 for a diagram of Eagle Eye and Brivo connections.
Figure 23: Eagle Eye/Brivo connections diagram
To Configure Brivo Eagle Eye LPR with Brivo Access Control:
Navigate to Camera Settings → Analytics → License Plate Recognition → Local ID
Set the Integration Type to Brivo.
If the USB-to-RS-485 converter is connected to the bridge, the corresponding USB serial number will automatically appear. Select the listed serial number.
If multiple USB-RS-485 converters are connected, configure them individually. This will help you identify the correct USB serial number for each configuration.
Choose the appropriate Peripheral Device ID based on the physical connections—this determines which Device ID corresponds to which peripheral.
Typically, one Peripheral Device ID is assigned for LPR, and another is assigned as a backup reader for access control. By default, PD0 is selected.
Set the Peripheral Device ID as PD0 if you do not have a backup reader with Brivo. If you have a backup reader, set the value to 1.
Click Save Changes to apply the configurations. See Figure 24.
Figure 24: LPR configurations with Brivo
This section provides information for integrating Brivo Eagle Eye LPR with the MOXA ioLogik E1214 I/O module for access control applications. Eagle Eye license plate recognition can be used for applications such as gate access control.
Brivo Eagle Eye LPR with Local ID enables license plate verification using a preconfigured allow list and/or deny list, and triggers an I/O event upon detection of an allowed or denied vehicle. The LPR service running on the Bridge is integrated with the MOXA ioLogik E1214 I/O module for access control applications (e.g., triggering a gate to open or close). This section describes how to configure this setup.
Eagle Eye currently supports the MOXA IoLogik E1214, which needs to be purchased separately. The user manual for Moxa ioLogik can be found here.
The MOXA unit incorporates six relay outputs, designated NO-1 through NO-6, which are utilized to actuate gate mechanisms. Each relay output possesses a corresponding common terminal, marked 'C', adjacent to the respective NO pins. It is imperative to distinguish relay outputs from digital outputs. Only the relay outputs, identified as RX_NO (where X denotes the output number), are employed in this configuration.
Should the gate be connected to R1_NO, it is necessary to configure output 1 on the LPR Configuration page of Brivo Eagle Eye Video to enable the allow list functionality. An illustrative connection diagram for channeling signals to the barrier and lighting systems is shown in Figure 25.
For comprehensive wiring specifications, consult the manufacturer's documentation here.
Figure 25: Moxa connection diagram for channeling signals
To Configure Brivo Eagle Eye LPR with Moxa ioLogik:
Navigate to Camera Settings → Analytics → License Plate Recognition → Local ID
Set the Integration Type to External I/O
The External I/O Module will automatically be selected as Moxa ioLogik.
Enter the IP Address of the Moxa device.
If you're unsure of the IP address, provide your Network Administrator with the MAC address of the Moxa. They can help locate the correct IP address and share it with you.
Enter the Allow, Deny, and Unlisted PINs based on the physical wiring and access control logic:
Allow: This PIN is triggered when the LPR recognizes an authorized vehicle.
Deny: This PIN is triggered when the LPR recognizes a registered vehicle with "Deny" access type.
Unlisted: This PIN is triggered when the LPR recognizes an unregistered vehicle.
Click Save Changes to apply the configurations. See Figure 26.
Figure 26: LPR Configuration with Moxa
Brivo Eagle Eye LPR on Bridge enables real-time license plate recognition results to be transmitted to a Webhook endpoint, which can be local or cloud-based, via an HTTP POST request. This functionality allows customers to directly integrate LPR results into their existing systems, such as kiosks, web portals, or third-party applications.
For integration, customers must have a webhook endpoint that can receive events in JSON format as outlined below. Once the endpoint is in place, they only need to configure the endpoint details within the Analytics Settings.
At this time, LPR images are provided exclusively in Base64 format. To integrate, customers need a webhook endpoint that can receive JSON-formatted events. After setting up the endpoint, they simply configure its details in the Analytics Settings. And for the vehicle and license plate crop images, they are only available in Base64-encoded format.
Sample LPR Event JSON
{
"custom": {
"camera_endTimestamp": 1752487309585.754,
"camera_startTimestamp": 1752487307116.509,
"endTimestamp": "1752487309603",
"endx": 666,
"endy": 55,
"event_attribute": "normal",
"event_message": "normal",
"event_type": "vehicle",
"startTimestamp": "1752487307132",
"startx": 26,
"starty": 360,
"variance": 44
},
"event": {
"aux_lp": [],
"confidence": 93,
"coordinates": {
"height": 36,
"width": 64,
"xmin": 67,
"ymin": 338
},
"det_confidence": 97,
"direction": "ENTRY",
"name": "9ROF044",
"priority": 1,
"properties": {
"path": [
"/uncanny/anpr/instance1/report/2025/07/14/LprData/fullimage_18460_KA01AB1460_1462.jpg",
"/uncanny/anpr/instance1/report/2025/07/14/LprData/18460_KA01AB1460_1462.jpg"
],
"video": "/uncanny/anpr/instance1/report/2025/07/14/LprData/18460_KA01AB1460_1462.jpg"
},
"reading": "9ROF044",
"vehicle_category": {
"confidence": 95,
"height": 388,
"type": "CAR",
"width": 477,
"xmin": 0,
"ymin": 122
},
"wait_time": 3287,
"lp_type": "GOODLP",
"db_match": false,
"signature_match": false,
"camera_esn": "1003a7a8",
"image_width": 1280,
"image_height": 720,
"external_camera_id": "101043d6",
"custom_id": "176434765987",
"tags": [
{
"key": "direction",
"value": "ENTRY"
},
{
"key": "confidence",
"value": 93
},
{
"key": "Dwell time",
"value": 3287
},
{
"key": "vehicle category",
"value": "CAR"
},
{
"key": "event_type",
"value": "normal"
},
{
"key": "database",
"value": "not matched"
},
{
"key": "state_code",
"value": "CA"
},
{
"key": "colour",
"value": "Black"
},
{
"key": "make",
"value": "Volkswagen"
},
{
"key": "lp",
"value": "9ROF044"
}
],
"match_type": "LP",
"main_reading": "9ROF044",
"db_mapped": false,
"is_duplicate_entry": "original",
"groupId": "534124_1752487307196",
"matched_lp": null,
"make": "Volkswagen",
"vehicle_make_confidence": 90,
"colour": "Black",
"colour_confidence": 81,
"state_code": "CA",
"state_code_confidence": 93
},
"info": {
"direction_setting": "Entry",
"event_timestamp": "1752487307196",
"external_camera_id": "101043d6"
},
"custom_info": null,
"evidence_image_path": "/uncanny/anpr/instance1/report/2025/07/14/LprData/fullimage_18460_KA01AB1460_1462.jpg",
"id": "40599v6amd2xp2ky",
"image_urls": {
"cloud_images": [],
"local_images": []
},
"extras": {},
"base64_images": []
}
To configure client integration, navigate to Camera Settings -> Analytics -> License Plate Recognition -> Client Integration in the VMS Enhanced Web Interface.
Example:
A Vehicle List is a list of plates grouped under a single name for easy management. The Vehicle List includes an access category and an access control schedule for LPR-based access control automation, integrated with Brivo Eagle Eye LPR (with Local ID). A Vehicle List can be integrated with an external database to enable automatic updates and management. A Vehicle List allows users to group vehicles under a list and map them to specific cameras and locations. See Figure 27.
Figure 27: Creating a new Vehicle List
The Vehicle List page is empty if no vehicle lists have been added. To add your first vehicle list, click Add Vehicle List as shown below, which will navigate you to the appropriate page.
If some vehicle lists already exist and you want to add another, click the waffle menu icon (three vertical dots) in the top-right corner of the Vehicle List page, then select Add Vehicle List. Refer to the screenshot below. See Figure 28.
Figure 28: Adding a new Vehicle List
Once you click Add Vehicle List, you will be directed to the page shown in Table 5.
Table 5: Adjusting Vehicle List settings
The new vehicle list appears under Vehicle List. See Figure 29.
Figure 29: Viewing the new Vehicle List
Vehicle list details:
List Name: Displays the name of the created vehicle list.
Vehicles: Indicates the number of vehicles added to the vehicle list.
Location: Shows the location associated with the vehicle list.
Camera: Displays the number of cameras linked to the vehicle list.
Status: Indicates the current status of the vehicle list.
To add vehicles to a Vehicle List, click the Vehicle List where you want to add vehicles. See Figure 30.
Figure 30: Adding vehicles to an existing Vehicle List
Add Vehicle: Use this option to add individual vehicle details. This is ideal for adding a small number of vehicles to the list.
Upload List via CSV: Use this option to add a large number of vehicles at once, suitable for bulk uploads.
If the vehicle list is empty, click Add Vehicle. This sends you to the appropriate dialogue. See Figure 31.
Figure 31: Adding individual vehicles to an empty Vehicle List
If there are already vehicles in the list and you wish to add more, click the Menu (three vertical dots) in the top-right corner of the Vehicle List page, then select Add Vehicle. See Figure 32.
Figure 32: Adding vehicles to a populated Vehicle List
Fill in the required details and click Add Vehicle.
Details for each field on the Add Vehicle page are shown in Figure 33.
Figure 33: Viewing Vehicle details
We have a template that needs to be filled out with vehicle details to add vehicles using a CSV file.
Go to the Menu (three vertical dots) in the top-right corner of the Vehicle List page, then click Upload list via CSV.
Click the Download template button to download the template. See Figure 34 for an example and Table 6 for the Vehicle List parameters and definitions.
Table 6: Vehicle List parameters and definitions
Figure 34: Downloading the Vehicle List template
Open the downloaded CSV file on your system, add the vehicle details, and save the file. See Figure 35.
Note: Fields marked with “*” (Plate and Access type) are mandatory. Ensure the data in the CSV matches the format mentioned in each column.
Figure 35: Saving the CSV file
Click Browse Files or drag and drop the file into the box.
Once the CSV is uploaded, click Next. See Figure 36.
Figure 36: Uploading the CSV file
The CSV file will be validated, and a table of all the data from the CSV file will be shown.
You will be notified of any entries that do not match the required format.
Plates that already exist in the vehicle list will also be indicated.
Review the data and click Done to insert the vehicles from the CSV file into the Vehicle List.
If changes are needed, click Cancel, make the necessary changes, and re-upload the CSV file.
Figure 42: Uploading the data from the CSV file to the Vehicle List
Once the data is successfully uploaded, you should see all the new entries in the vehicle list. See Figure 43.
Figure 43: Viewing new entries in the Vehicle List
If the plates already exist or there are errors in the input, the upload process will fail for those vehicles. The results will be shown as follows:
Failed Vehicles (Red Box): These plates were ignored because they already exist in the vehicle list.
Uploaded Vehicles (Green Box): These plates were successfully added to the vehicle list. See Figure 44.
Figure 44: Viewing Vehicles that fail to upload to the Vehicle List