User Manual for End Users and System Administrators
The Metrici Control Panel v4.0 is a central management application that allows you to configure, start, stop, and monitor various Metrici recognition and analysis applications. Think of it as a "command center" that gives you complete control over all your Metrici software from a single, easy-to-use interface.
The Control Panel can manage various types of Metrici applications, including:
Usually, Control Panel starts automatically when the server is powered on. Or you can start it from command line. The main window will appear, showing you the current status of your applications — see Fig.1 Control Panel.
If you need to run the Control Panel from the command line, the following options are available:
| Option | Description |
|---|---|
-nogui |
Starts the application without displaying the graphical interface. Useful for running in headless environments or as a service. |
-v |
Displays the version information and exits. |
When you first launch the Control Panel, check the license status indicator at the top of the window — see Fig.1 Control Panel (1). The indicator shows three key pieces of information:
| Status Color | Meaning |
|---|---|
| Green | Your license key is valid and active. The number of enabled licenses is displayed. |
| Orange | You are running in demo mode with limited functionality. |
| Red | No valid license key found. Applications cannot be started. |
The main window is divided into several sections that give you complete control over your Metrici applications.
The top section displays important information about your license — see Fig.1 Control Panel (1):
The main table displays all configured applications with their details — see Fig.1 Control Panel (2):
| Column | Description |
|---|---|
| ID | Unique identifier for the application instance |
| Name | Descriptive name you gave to this application instance |
| App type | What kind of Metrici application this is (LPR, QR, etc.) |
| CPU Cores | Number of CPU processor cores allocated to this application |
| Execution Type | How the application runs: Background or Foreground |
| GPU | Which GPU device the application uses (if any) |
| Log Level | How detailed the log files should be |
| Status | Current state: Stopped, Starting, or Started |
| Load | Current CPU load percentage |
The buttons at the bottom or side of the window provide quick access to common operations:
| Button | Function |
|---|---|
| Add | Create a new application configuration see Fig.1 Control Panel (3) |
| Edit | Modify an existing application's settings see Fig.1 Control Panel (4) |
| Delete | Remove an application configuration - see Fig.1 Control Panel (8) |
| Start | Launch the selected application see Fig.1 Control Panel (5) |
| Stop | Stop the running application see Fig.1 Control Panel (6) |
| View Log | View the log file for the selected application see Fig.1 Control Panel (7) |
| Licenses | Show detailed license information see Fig.1 Control Panel (13) |
| License Request | Generate a file to request new license activations see Fig.1 Control Panel (9) |
| License Update | Apply a new license update file see Fig.1 Control Panel (10) |
| About | Show information about the Control Panel software see Fig.1 Control Panel (11) |
| Quit | Close the Control Panel and all applications Fig.1 Control Panel (12) |
To add a new application instance:
Once you've configured an application, you can start it:
To stop a running application:
To modify an existing application's configuration:
To remove an application configuration:
To view an application's log file:
Log files are essential for troubleshooting. They contain information about:
When adding or editing an application, you'll need to configure various options. This section explains each option in detail.
A descriptive name to help you identify this application instance. While optional, giving each application a meaningful name makes it easier to manage multiple instances. — see Fig.2 Add Menu (2) .
This defines what kind of Metrici application this instance will be. Choose based on your licenses/needs — see Fig.2 Add Menu (3):
| Application Type | Use Case | Description |
|---|---|---|
| LPR | Vehicle access control, parking management | Recognizes license plates from camera images. Ideal for basic license plate reading tasks. LPR Documentation |
| LPR+ | High-security vehicle identification | Enhanced license plate recognition with additional features like vehicle color and brand. |
| QR Code | QR code scanning, inventory tracking | Reads and decodes QR codes from images or video streams. |
| Container Code | Logistics, shipping, port management | Recognizes shipping container identification codes. |
| Parking Place Detector | Smart parking systems | Detects whether parking spaces are occupied or empty. |
| Area Counter | People and vehicles counting | Counts people or objects within a defined area. |
| Line Counter | People and traffic counting | Counts objects that cross a virtual line in the video feed. |
| Thermal Analyzer | Thermal imaging analysis, fire detection | Analyzes thermal camera feeds for temperature monitoring or anomaly detection. |
| ID card reader | OCR | Automatically identifies text and saves it to Metrici database. |
| Snapshot | Image Capture | Take photo from IP cameras when triggered |
| Advanced Video Analytics | Special projects | Detection of custom objects. |
| Line Counter PE | Protection equipment counting | Detects if a person has protection equipment like vest, helmets etc |
| Area Counter PE | Protection equipment detection | Detects if a person has protection equipment like vest, helmets etc |
| Live View | Detections display | View as many engines in real time |
This setting determines how many CPU processor cores the application can use. More cores allow the application to process data faster, especially when handling multiple video streams — see Fig.2 Add menu (4).
This setting controls how and where the application runs — see Fig.2 Add Menu (5):
| Execution Type | Description | Use Case |
|---|---|---|
| Background | Application runs invisibly without a window. You won't see any interface, but the application processes data continuously. | Server installations, 24/7 operation, when no monitor is attached |
| Background with Watchdog | Runs in background like above, but if the application crashes or stops unexpectedly, it will automatically restart. | Critical applications that must run continuously without manual intervention |
| Foreground | Application runs with its own window visible on the screen. You can see what it's processing in real-time. | Testing, demonstrations, when you need to monitor the application visually |
| Foreground with Watchdog | Application runs in a visible window but will automatically restart if it crashes. | When you want to see the application running but also need automatic recovery |
Modern computer graphics cards (GPUs) can process visual data much faster than CPUs. This setting controls whether and how the application uses your GPU — see Fig.2 Add Menu (6) :
| Setting | Description | When to Use |
|---|---|---|
| Disabled (No GPU) | Application uses only the CPU for processing | Systems without GPUs, or when GPU is needed by another application |
| GPU [Device Number] | Application uses the specified GPU for processing | When you want maximum performance and have a dedicated GPU |
This determines how the application sends its results and data — see Fig.2 Add Menu (8) :
| Output Type | Description |
|---|---|
| Normal | Sends all event details plus pictures (plate/car images) to the URL using an HTTP POST. |
| Simplified | Sends only the basic event details (plate number, time, confidence, etc.) — usually without pictures. |
| Json | Sends the event details in JSON format (a structured text format). The receiving system must be able to read/parse JSON to use the data. |
External module selects a vendor integration mode. Choose Skidata or Bebarmatic only when your parking hardware/software is from that vendor, so Metrici sends plate events using that vendor’s interface instead of only using Metrici’s internal actions — see Fig.2 Add Menu (9) .
| Module Type | Description |
|---|---|
| None | Metrici works on its own. It saves plate events and uses its own rules/actions to control access (e.g., open a barrier). |
| Skidata | Select this if the installation uses a Skidata parking system. Metrici forwards plate events to Skidata so Skidata can handle access/parking logic. |
| Bebarmatic | Select this if the installation uses a Bebarmatic parking system. Metrici forwards plate events to Bebarmatic so Bebarmatic can handle access/parking logic. |
The log level determines how much detail is written to the application log file. More detailed logs are useful for troubleshooting but use more disk space — see Fig.2 Add Menu (7) :
| Log Level | Detail | Disk Usage | Use Case |
|---|---|---|---|
| None | No logging at all | Minimal | Maximum performance needed, no troubleshooting required |
| Low | Only important events (start, stop, errors) | Low | Normal operation, general monitoring |
| Medium | Standard events and important operations | Medium | Default recommendation for most users |
| High | Very detailed, including debug information | High | Troubleshooting specific issues |
The Metrici Control Panel manages also the software licenses. This section explains how to manage your licenses.
Your Metrici software is protected by a SENTINEL key
To see a summary of all your enabled licenses:
If you need to activate new licenses (for example, after purchasing additional applications):
.c2v will be created on your DesktopWhen your distributor sends you a license update file:
.v2c or .v2cp extension) to your computerThe Control Panel provides visual feedback about your license status:
| Status Display | Meaning | Action Required |
|---|---|---|
| "SENTINEL key is active, X engine licenses and Y web licenses enabled" | Normal operation, licenses working | None |
| "SENTINEL key is active, X demo engine license(s) and ALL demo web license(s) enabled" | Demo/trial version active | Contact distributor for full licenses |
| "SENTINEL key error: invalid, not active, missing or expired" | License key problem detected | Check USB connection, try different USB port, or contact support |
The Control Panel provides several ways to monitor your applications in real-time.
The status column shows the current state of each application — see Fig.1 Control Panel (2) :
| Status | Meaning |
|---|---|
| Stopped | Application is not running |
| Starting | Application is launching (this is temporary) |
| Started | Application is running and processing data |
The "Load" column shows the current CPU load of each application as a percentage. This helps you understand how heavily each application is using system resources — see Fig.1 Control Panel (2):
| Load Value | Interpretation |
|---|---|
| 0% | Application is idle or no data is being processed |
| 1-50% | Light processing load |
| 50-80% | Moderate processing load |
| 80-100% | Heavy processing, may affect real-time performance |
The Control Panel automatically checks the status of all applications every second. The display updates automatically when:
Applications configured with "Watchdog" execution type have built-in crash recovery:
Log files contain detailed records of what an application did. They're essential for understanding problems and monitoring performance.
Each application creates a log file with a name matching its ID (e.g., 1.log, 2.log). These files are stored in the same directory as the Control Panel.
To view an application's log:
The Control Panel automatically manages log file sizes. When a log file is older than one month, it's automatically rotated:
[id].old.log| Possible Cause | Solution |
|---|---|
| No valid license available | Check that all enabled licenses aren't already in use |
| SENTINEL key not detected | Restart Control Panel |
| Invalid configuration | Review application settings for errors |
| System resources exhausted | Stop some applications or reduce CPU core allocations |
| Possible Cause | Solution |
|---|---|
| Insufficient resources | Reduce CPU cores, disable GPU, or upgrade hardware |
| GPU driver issues | Update GPU drivers or disable GPU usage |
| Input stream problems | Check camera or video source connections |
| Possible Cause | Solution |
|---|---|
| Too many applications running | Stop unused applications |
| CPU cores over-allocated | Reduce CPU cores per application |
| High resolution video | Reduce video resolution or frame rate |
| Possible Cause | Solution |
|---|---|
| License expired | Contact your distributor to renew licenses |
When troubleshooting, check logs for:
A: Yes! The Control Panel allows you to create multiple instances of the same application type, as long as you have enough licenses. For example, you could have three different LPR applications monitoring three different cameras.
A: The maximum number of applications is determined by your license. Each license allows one concurrent instance. If you try to start more applications than you have licenses for, the Control Panel will show an error.
A: Yes! Use the -nogui command line option. The Control Panel will run in the background without showing a window. Use this for server installations or when you only need the applications running, not the management interface.
A: Application configurations are stored in the cpan.ini file. Simply copy this file to a safe location to backup your configurations. You can restore by copying it back when needed.
A: Background execution runs invisibly (no window), which is ideal for servers and 24/7 operation. Foreground execution shows a window where you can see the application processing in real-time, which is useful for testing and monitoring.
A: If you have a compatible GPU (NVIDIA, AMD or Intel Arc), enabling GPU processing can significantly improve performance, especially when processing video. However, some systems don't have GPUs, and integrated graphics may not provide benefits. Try both modes to see which works better for your setup.
A: For normal operation, use "Medium" logging. This provides enough information for troubleshooting while not using too much disk space. Increase to "High" only when you're actively debugging a specific problem, then reduce back to "Medium".
A: The watchdog automatically restarts an application if it crashes or stops unexpectedly. This is important for critical applications that must run continuously without manual intervention.
A: Contact your Metrici distributor to purchase additional licenses. They'll provide you with a product activation key. Use the "License Request" button to create a request file, send it to your distributor, and they will provide a license update file to install.
If you need help with the Metrici Control Panel or your Metrici applications:
| Contact Method | Details |
|---|---|
| support@metrici.ro | |
| Website | http://www.metrici.ro |
| Company | Metrici (Copyright 2026) |
To get faster assistance, please gather the following information before contacting support: