Container Code Recognition v2.5

1. Introduction

Welcome to the Container Code Recognigtion (CCR) v2.5 user manual. This software application is designed to automatically recognize and read container codes and license plates from video streams captured by cameras. The application processes video in real-time, identifies vehicles, extracts license plate numbers and container codes, and can trigger various actions based on the recognition results.

The CCR system is widely used in:

• Container Terminals: Tracking shipping containers as they enter or exit facilities
• Vehicle Access Control: Monitoring and controlling vehicle access at secured entrances
• Logistics Centers: Recording vehicle movements and cargo information
• Toll Gates: Automatic vehicle identification and billing
• Parking Facilities: Entry and exit tracking

Key Features

The CCR application offers a comprehensive set of features designed for reliable and efficient automatic recognition:

• Multi-Camera Support: Connect to various types of IP cameras and video sources
• Real-Time Processing: Analyze video streams and recognize plates and codes in real-time
• Multiple Recognition Engine Modes: Choose between continuous scanning or trigger-based operation
• Configurable Detection Area: Define exactly where on the screen recognition should be made
• Direction Detection: Determine whether vehicles are entering or leaving
• Integration Capabilities: Connect with external systems like barriers, sensors, and databases
• Reporting: Send recognition results to remote servers for logging and processing
• GPS Support: Record location data with each recognition event
• Hardware Integration: Connect to weight scales and radar devices

3. Main Interface Overview

The CCR application main window is divided into several key areas that provide visual feedback and control over the recognition process.

Main Window Components

Video Display Area

The main video display shows the live video feed from your connected camera. This area:

• Displays the processed video with recognition overlays
• Highlights detected license plates and codes with bounding boxes
• Shows recognized characters
• Indicates the detection window (if configured)

Connection Status Indicators

Located near the video display, these indicators show the current connection status:

Frame Rate Display

Shows the current processing speed in frames per second (FPS). This helps you monitor system performance.

Last Detected CC (Container Code)

This area displays the most recently recognized container code:

• The recognized container code
• Confidence level (how sure the system is of the recognition)
• Timestamp of when the code was detected
• A thumbnail image of the detected code

Codes History Table

A scrolling table showing all recently detected codes with:

• Timestamp of detection
• Recognized code
• Direction (entering/leaving)
• Confidence level

Control Buttons

The main toolbar contains these essential buttons:

GPS Status Display

If GPS integration is enabled, this area shows:

• Current GPS connection status
• Latitude and longitude coordinates
• Signal quality indicator

4. Camera and Video Stream Configuration - Input Stream

Configuring your camera correctly is essential for reliable license plate recognition. The CCR application supports a wide variety of camera types and video streaming protocols.

Supported Camera Types

The CCR application supports numerous camera manufacturers and video formats:

RTSP Streaming Cameras with H.264 and H.265 protocols

Real-Time Streaming Protocol (RTSP) is the industry standard for IP cameras:

HTTP Streaming Cameras

Cameras that stream video over HTTP:

Specialized Camera Types

• Video File: Process pre-recorded video files instead of live cameras

Configuring Camera Settings

Step-by-Step Camera Configuration

1. Click the "Settings" button on the main toolbar
2. Expand the "Input Stream" section in the settings tree
3. Configure the following parameters:

Stream Type Selection

From the dropdown menu, select the type of video stream:

Stream Type: [Generic RTSP H.264 ▼]

Choose the option that matches your camera manufacturer and streaming protocol.

Camera Address

Enter the network address of your camera. The format depends on the stream type:

TCP Port

For RTSP streams, specify the TCP port number:

• Default RTSP Port: 554
• Alternative RTSP Ports: 555, 8554, 10554
• HTTP Port: Usually 80 or 8080

TCP Port: [554]

Authentication Credentials

If your camera requires login credentials:

Username: [admin]

Password: [••••••••]

FPS Limit

Set a maximum frame rate to limit processing load:

Example FPS Limit: [6]

Video Resolution set in Camera's menu

Configure the video resolution for optimal recognition:

RTSP Stream Settings

For RTSP streams, additional options are available:

• RTSP Latency: Delay buffer for RTSP streams (typically 100-500ms). Higher values improve stability but add delay.
• Protocol Selection: Choose between UDP, TCP, or HTTP tunneling depending on your network conditions. Settings done in .ini file. See below.

Testing Camera Connection

After configuring camera settings, test the connection:

1. Click "Save" in the Settings window
2. Return to the main window
3. Watch the connection status indicator
4. If the status changes to Connected, the camera is working
5. If it shows Disconnected, check your settings

Troubleshooting Camera Connection

5. Companion Stream (Secondary Camera)

The CCR application supports a second video stream called the Companion Stream. This secondary camera can provide additional views or capture different angles of the same vehicle/ code for improved recognition reliability.

Configuring Companion Stream

1. Click "Settings" on the main toolbar
2. Expand the "Companion Stream" section
3. Configure stream type, address, and credentials (same as main camera)
4. Click "Save"

Companion Stream Settings

The companion stream configuration options are identical to the main input stream:

• Stream type selection (RTSP, HTTP, etc.)
• Camera address
• TCP port
• Username and password

Display Options

The companion stream video can be displayed:

• Tabbed View: Switch between main and companion with tabs

6. CCR Recognition Settings

Fine-tune the container code recognition engine to achieve optimal results for your specific environment and requirements.

Plate Detection Parameters

CCR Minimum Length

Set the minimum number of pixels expected for the codes:

Maximum CCR Length

Set the maximum number of characters expected:

Single CC mode

Single Plate Mode: [✓] Enabled / [ ] Disabled

When enabled, the system assumes only one container code is in the detection area at a time:

Same Code Delay

Set the minimum time between recognizing the same code :

This prevents duplicate recognition of the same vehicle.

Vehicle Direction Settings

Direction Indicator

Configure how the system determines vehicle direction:

Code Direction: [0-360 degrees]

Set the expected direction of vehicle movement. Arrange the arrow on the dial accordingly

Event Type

Define what happens when a vehicle/ code is detected:

Event Type: [Coming ▼]

• Coming: Vehicle is approaching/arriving at the detection point
• Leaving: Vehicle is departing from the detection point

This setting affects how recognition events are reported and logged.

Recognition Engine Working Mode

Continuous Mode

Working Mode: [Continuous ▼]

In continuous mode, the system constantly analyzes every video frame:

• Pros: Maximum detection probability, no risk of missing vehicles
• Cons: Higher CPU/GPU usage, may detect stationary vehicles

Best for: High-traffic areas where vehicles are always present.

Trigger Mode

In trigger mode, recognition only occurs when triggered by an external signal:

• Pros: Lower resource usage, more accurate triggering of events
• Cons: Requires external trigger hardware (loop detectors, sensors)

Best for: Controlled environments with external vehicle sensors.

7. Detection Window Configuration

The detection window defines the specific area of the video frame where the system will look for codes. Properly configuring this area improves accuracy and reduces processingp>

Why Use a Detection Window

Setting a detection window provides several benefits:

• Improved Accuracy: The system only searches for plates in the defined area
• Faster Processing: Smaller search area means faster recognition

Enabling the Detection Window

1. Click "Settings" on the main toolbar
2. Expand the "Detection Window" section
3. Check the "Detection Window Active" option
4. Click "Save"

Setting Detection Window Position

Origin Coordinates (Top-Left Corner)

Origin X: [100] pixels

Origin Y: [200] pixels

These values define where the top-left corner of the detection area starts:

• Origin X: Horizontal position from the left edge (0 = left edge)
• Origin Y: Vertical position from the top edge (0 = top edge)

Window Size

Resolution X: [640] pixels

Resolution Y: [480] pixels

These values define the width and height of the detection area.

Visual Adjustment Method

For easier configuration, you can visually adjust the detection window:

1. In the Settings window, click on the video display area
2. Click and drag to draw a rectangle where you want the detection area
3. The coordinates will automatically update in the settings fields
4. Release the mouse button to set the final position

Best Practices for Detection Window

Optimal Window Position

• Position where vehicles/codes are perpendicular to the camera (best angle for reading )
• Include the full path of vehicle travel
• Exclude areas where non-vehicle objects might cause false detections

Testing Detection Window

After setting up the detection window:

1. Save your settings
2. Watch the main video display
3. A green rectangle shows the detection area
4. Verify the code is detected when inside the green rectangle
5. Adjust the window if necessary

8. Live View Feature

The Live View feature allows you to broadcast the video feed with recognition overlays to a remote web server or monitoring system.

Purpose of Live View

Live View is useful for:

• Remote Monitoring: Watch the video feed from anywhere via web browser
• Central Control Rooms: Display feeds on video walls
• Mobile Access: View on smartphones or tablets
• Recording: External systems can capture and record the stream

Enabling Live View

1. Click "Settings"
2. Expand the "Live View" section
3. Check "Live View Active"
4. Enter the destination URL
5. Click "Save"

Live View URL Configuration

Live View URL: [http://your-server.com/io/ccr/live_view.php]

The URL must point to a server-side script that can receive and process the video stream.

9. Reporting and Check Action

The CCR application can automatically report recognition events to external servers for logging, processing, and integration with other systems.

Reporting URL

Reporting URL: [http://your-server.com/io/ccr/reporting_event.php]

This is the main endpoint where recognition events are sent. Each time a code is recognized, the application sends data including:

• Code number
• Timestamp
• GPS coordinates (if available)
• Direction (coming/leaving)
• Event ID

Check Action URL

Check Action URL: [http://your-server.com/io/ccr/check_action_event.php]

This URL allows the system to query external databases or decision systems before taking action. Flow:

1. Code is recognized
2. System sends plate data to Check Action URL
3. Remote server processes the request
4. Server returns instructions (allow, deny etc )
5. CCR takes action based on response

Authentication

Secure your reporting and check action endpoints:

Check Action Auth Key: [your-secret-key]

Check Action ID: [1]

The auth key is the communication intermediary between engine and database. The check action ID identifies which installation is. These are to be retrieved from Metrici Interface when creating location and camera

Data Format

Data is typically sent as HTTP POST requests with JSON or form-encoded data:

POST /reporting.php
Content-Type: application/json

{
    "plate": "ABC123",
    "timestamp": "2024-01-15 14:30:25",
    "confidence": 95,
    "direction": "coming",
    "gate_id": 1,
    
}

Trigger UDP Port

Trigger UDP Port: [3500]

For simple integrations, the CCR can send UDP packets when plates are detected. This is useful for triggering external hardware or simple scripts.

10. Barrier and Traffic Light Control

The CCR application can integrate with barrier (gate) systems to automatically open barriers for authorized vehicles/ codes.

Barrier Control Overview

When combined with the Check Action feature, the system can:

• Automatically open barriers for authorized vehicles
• Keep barriers closed for unauthorized vehicles
• Log all access attempts
• Integrate with existing access control systems

Configuration

Open Barrier URL

Open Barrier URL: [http://barrier-controller/open]

This URL is called when the system needs to open the barrier (typically for authorized vehicles).

Close Barrier URL

Close Barrier URL: [http://barrier-controller/close]

This URL is called to close the barrier after a vehicle has passed.

Open/Close Delay

Open-Close Delay: [5] seconds

Time between opening the barrier and automatically closing it. Adjust based on your requirements:

Secondary Traffic Light

For installations with two barriers (entry and exit) or other device:

Traffic Light ON URL: [http://barrier-controller2/open]

Traffic Light OFF URL: [http://barrier-controller2/close]

Open-Close Delay 2: [5] seconds

Barrier Control Flow

1. Vehicle approaches and is recognized
2. Code is sent to Check Action URL
3. Server responds with action (e.g., "ALLOW")
4. If allowed: Open Barrier URL is called
5. Barrier opens
6. System waits for Open-Close delay
7. Close Barrier URL is called
8. Barrier closes

11. External Triggers

External triggers allow the CCR application to be activated by hardware sensors or external systems rather than continuously processing video.

Types of External Triggers

Hardware Triggers

• Barionet 50 I/O: Network-connected digital input module
• Inductive Loop Detectors: Detect vehicles via magnetic field changes
• Photoelectric Sensors: Detect vehicles via light beam interruption
• Pressure Mats: Detect vehicles via weight sensors

Virtual Triggers

• Metrici Virtual Trigger: Software-based trigger from other systems

Trigger Configuration

Trigger Type

External Trigger Type: [Barionet 50 I/O 1 ▼]

Select the type of trigger device you are using.

Trigger Sensitivity

Trigger Seconds: [2] seconds

This setting defines how long the detection is done after the trigger is received.

12. GPS Integration

The CCR application can receive GPS coordinates from an external GPS device and include location data with each recognition event.

Purpose of GPS Integration

• Location Logging: Record exact location of each recognition
• Mobile Installations: Use with vehicles or portable setups
• Geo-Fencing: Verify vehicles are in expected locations
• Multiple Site Management: Identify which site recorded each event

GPS Status Indicators

The main interface shows GPS connection status:

GPS Data Display

When GPS is connected and working, the interface shows:

• Latitude: North/South position (e.g., 40.7128° N)
• Longitude: East/West position (e.g., 74.0060° W)
• Coordinates Format: Decimal degrees (DD.DDDD°)

Connecting a GPS Device

1. Connect GPS device to computer via USB or serial port
2. Install necessary drivers for the GPS device
3. The application should automatically detect the GPS device
4. Wait for GPS signal acquisition (may take a few minutes)
5. Verify status shows Good Signal

GPS Data in Reports

GPS coordinates are included in reports sent to:

• Reporting URL
• Local log files

{
    "plate": "ABC123",
    "timestamp": "2024-01-15 14:30:25",
    "gps_latitude": 40.7128,
    "gps_longitude": -74.0060
}

13. Weight Scale Integration

The CCR application can read weight data from connected weight scales and combine it with license plate recognition for comprehensive vehicle logging.

Why Integrate Weight Scales

• Weight Verification: Confirm loaded vs. empty vehicle weights
• Overload Detection: Identify overweight vehicles
• Comprehensive Logging: Record both identity and weight
• Revenue Tracking: Weight-based billing or tolling

Configuration

Weight Scale Type

Weight Scale Type: [Barix Cantar I30 ▼]

Weight Scale Address

Weight Scale Address: [192.168.1.200]

Network IP address of the weight scale device.

TCP Port

TCP Port: [80]

Communication port for the weight scale (typically 80 or 3050).

Weight Data Display

When connected, weight data is displayed:

• Current Weight: Live weight reading
• Unit: Kilograms (kg) or pounds (lbs)
• Connection Status: Connected/disconnected indicator

Weight Data in Reports

Weight data is included with recognition events:

{
    "plate": "ABC123",
    "timestamp": "2024-01-15 14:30:25",
    "weight": 12500.5,
    "weight_unit": "kg"
}

14. Radar/Speed Detection

The CCR application can integrate with Metrici Observer Radar device to measure vehicle speed and combine it with license plate recognition or container codes.

Purpose of Radar Integration

• Speed Measurement: Record vehicle speed during recognition
• Speed Limit Enforcement: Identify vehicles exceeding speed limits
• Safety Monitoring: Track speeding incidents
• Traffic Analysis: Gather speed data for traffic studies

Radar Data in Reports

Speed data is included with recognition events:

{
    "plate": "ABC123",
    "timestamp": "2024-01-15 14:30:25",
    "speed": 45.5,
    "speed_unit": "km/h"
}

15. Recognition Engine Mode

The CCR application offers two modes of operation for the license plate recognition engine.

Continuous Mode (Default)

In continuous mode, the recognition engine analyzes every video frame all the time:

• Maximum detection probability - won't miss passing vehicles
• Constant CPU/GPU usage
• Best for high-traffic areas
• Recommended for most installations

Triggered Mode

In triggered mode, the recognition engine only activates when triggered by an external signal:

• Lower resource usage - only processes when needed
• Requires external trigger device (see External Triggers section)
• More precise timing - captures vehicle at exact moment
• Best for installations with vehicle sensors

Changing the Mode

1. Click "Settings"
2. Navigate to "LPR Engine Working Mode"
3. Select mode from dropdown:

Working Mode: [Continuous ▼]

Working Mode: [Started by Trigger ▼]

Performance Comparison

16. Command Line Options

The CCR application can be started with various command line options for advanced configuration and deployment scenarios.

Basic Command Line Syntax

ccr [options]

Available Options

Headless Mode

-nogui

Runs the application without the graphical interface. Use this for server deployments or headless systems.

ccr -nogui

GPU Configuration

-disable_gpu

Disables GPU acceleration, forcing the application to use CPU processing only. Use when GPU is unavailable or causing issues.

ccr -disable_gpu

-gpu [id]

Specifies which GPU to use for acceleration when multiple GPUs are available.

ccr -gpu 0        // Use first GPU
ccr -gpu 1        // Use second GPU

Processing Threads

-detection_threads [number]

Sets the number of threads used for recognition processing. Default is 1, maximum is 8.

ccr -detection_threads 4    // Use 4 processing threads

Logging Configuration

-log_level [0-3]

Sets the verbosity of log output:

• 0: NONE - No logging
• 1: LOW - Only important events
• 2: MEDIUM - Standard logging (default)
• 3: HIGH - Verbose, includes debug information

ccr -log_level 1    // Low logging
ccr -log_level 3    // Verbose debugging

Application Instance

-app_id [0-15]

Identifies which application instance this is when running multiple instances on one system. Each instance uses a separate configuration file.

ccr -app_id 0        // First instance (uses 0.ini)
ccr -app_id 1        // Second instance (uses 1.ini)

Application Name

-app_name [name]

Sets a custom name for this application instance, displayed in the title bar and logs.

ccr -app_name "Entry Gate North"

Output Format

-output_type [format]

Specifies the output format for external integrations.

ccr -output_type default    // Standard format
ccr -output_type vidux         // Vidux format

Version Information

-v

Displays version information and exits without starting the application.

ccr -v

Debug Mode

-debug

Enables debug mode with additional diagnostic information.

ccr -debug

Complete Example

ccr -nogui -detection_threads 4 -log_level 2 -app_id 0 -app_name "Main Entrance"

This command runs the application:

• Without GUI (headless mode)
• With 4 processing threads
• With medium log verbosity
• As application instance 0
• Named "Main Entrance"

17. Troubleshooting

This section addresses common problems and their solutions.

Camera Connection Issues

Problem: Cannot Connect to Camera

Problem: Video Freezes or Lags

Recognition Issues

Problem: Poor Recognition Accuracy

Problem: Missing Detections

Problem: False Detections

Performance Issues

Problem: Low Frame Rate

Integration Issues

Problem: Reports Not Being Sent

Problem: Barrier Not Opening

GPS Issues

Problem: GPS Not Connecting

Problem: GPS Signal Weak

Logs and Diagnostics

When troubleshooting, enable detailed logging:

ccr -log_level 3 -debug

Log files contain valuable diagnostic information including:

• Connection attempts and results
• Recognition confidence scores
• Error messages and stack traces
• Timing information

18. Technical Support

If you need additional help, please contact technical support.

Before Contacting Support

To help us assist you quickly, please gather the following information:

• Software Version: Run ccr -v to get version information
• Log Files: Enable -log_level 3 and capture the logs during the issue
• Configuration: Export or describe your current settings
• Hardware Information: Computer specs, camera model
• Network Setup: IP addresses, network topology
• Issue Description: Detailed description of the problem
• Steps to Reproduce: How to make the issue happen

Appendix B: Settings Quick Reference

Appendix C: Stream URL Formats

Common RTSP URLs

Common HTTP MJPEG URLs

Appendix A: Configuration File (INI File)

The CCR application stores all its settings in a configuration file called an INI file. This file contains every configurable option for the application and is automatically created when you first save your settings.

INI File Location and Naming

The configuration file is located in the same directory as the CCR application executable. The file naming convention depends on the application instance:

{instance_id}.ini

INI File Structure

The INI file is a text-based configuration format organized into sections and key-value pairs. Here is an example of what an INI file looks like:

[General]
; This is a comment
setting_name=value

[Input Stream]
input_stream_type=1
input_stream_address=rtsp://192.168.1.100:554/stream1
input_stream_tcp_port=554
input_stream_username=admin
input_stream_password=secret123
input_stream_fps_limit=30
input_stream_resx=1280
input_stream_resy=720

[Companion Stream]
companion_stream_type=0
companion_stream_address=
companion_stream_tcp_port=80

[Detection Window]
input_stream_window_active=false
input_stream_window_origx=100
input_stream_window_origy=100
input_stream_window_resx=100
input_stream_window_resy=100

[Live View]
live_view_active=true
live_view_url=http://localhost/io/ccr/live_view.php

[Reporting]
reporting_url=http://localhost/io/ccr/reporting_event.php
check_action_url=http://localhost/io/ccr/check_action_event.php
check_action_send_trigger_address=
check_action_send_trigger_udp_port=3500
reporting_check_action_id=0
reporting_check_action_authkey=

[Plates]
plate_min_length=5
plate_max_length=10
same_plate_delay=30
single_plate_mode=false

[Vehicle Settings]
cars_direction=0
cars_event_type=1

[Barrier Control]
open_barrier_url=
close_barrier_url=
open_close_barrier_delay=10
open_barrier2_url=
close_barrier2_url=
open_close_barrier2_delay=10

[External Trigger]
external_trigger_type=0
external_trigger_seconds=1

[Engine Settings]
lpr_engine_working_mode=0

[Hardware Integration]
weight_scale_type=0
weight_scale_address=
weight_scale_tcp_port=10001
radar_type=0
radar_address=
radar_tcp_port=10001

[Advanced Settings]
rtsp_stream_latency=100
rtsp_stream_protocols=tcp

Complete Settings Reference

The following table lists all settings that can be stored in the INI file, organized by category:

Input Stream Settings

Companion Stream Settings

Detection Window Settings

Live View Settings

Reporting Settings

Plate Recognition Settings

Vehicle Settings

Barrier Control Settings

External Trigger Settings

Engine Settings

Hardware Integration Settings

Advanced RTSP Settings

Stream Type Values Reference

The following table shows the numeric values for stream types:

Trigger Type Values Reference

Weight Scale Type Values

Radar Type Values

Backing Up Configuration

It's good practice to backup your configuration file:

• Make a copy before making major changes
• Backup before software updates
• Save different configurations for different scenarios
• Store backups in a safe location

Resetting to Defaults

To reset all settings to default values:

1. Close the CCR application
2. Delete or rename the INI file (e.g., rename 0.ini to 0.ini.backup)
3. Restart the CCR application
4. A new INI file will be created with default settings

Multiple Instances

When running multiple instances of the CCR application, each instance has its own INI file:

ccr -app_id 0    ; Uses 0.ini
ccr -app_id 1    ; Uses 1.ini
ccr -app_id 2    ; Uses 2.ini

This allows you to have different configurations for different cameras or locations on the same computer.

Appendix D: Glossary