Inex Solution for the Motorola PTL System

1. Background

RoadView is advanced ALPR software that reads license plates using sophisticated image recognition algorithms, and creates LPR Events. RoadView sends LPR Event data via HTTP or other protocols to other systems.

The PTL system records Events for vehicles that are in the lane, and compares them with a list of authorized vehicles (White List).

This document describes how to configure the Inex Motorola PTL system.

2. Configuring/Controlling Parameters via the GUI and API

RoadView can be configured using both a web-based GUI and an API. Some parameters can only be configured/controlled via the API, others only via the GUI, and some via both (see Table 1). See the API document for further details.

Table 1. GUI/API Parameter Control
Name Description API Cntrl GUI Cntrl Local Storage Notes

Site GUID

Unique GUID of the RoadView (RV) site

yes

no

RV config file

"enforceSite" in API

Motorola Server URL

Motorola Server URL

yes

yes

RV config file

"avivServiceAddress" in API. "Motorola URL" in GUI.

Motorola Server Username and Domain

Motorola Server username and domain

no

yes

RV config file

"Motorola Username" in GUI. Format: domain/username

Motorola Server Password

Motorola Server password

no

yes

RV config file

"Motorola Password" in GUI.

Time to Save Events

How long RV stores logs in a database and Events in an offline queue

yes

yes

RV config file

"time2SaveEvent" in API. "Log Store Days" in GUI.

Keep Alive Interval

How often RV sends Keep Alive messages to the Motorola Server. In seconds.

no

yes

RV config file

"Keep Alive Interval" in GUI.

Amazon Bucket Credentials

Credentials for access to the bucket where RoadView sends images and video.

yes

no

RV config file

"s3" in API

Activity Days

Default system activity ("enforcement") times, according to the day of the week.

yes

no

RV config file

"activityDays" in API.

Activity Times

Special activity times, according to specific dates. Enables "enforcement" (system activity) regardless of Activity Days settings.

yes

no

RV config file

"activityTimes" in API

Stop Enforce Now

When the value is 1, then immediately stop enforcement on the site.

yes

no

RV config file

"stopEnforceNow" in API

Start Enforce Now

When the value is 1, then immediately start enforcement on the site.

yes

no

RV config file

"startEnforceNow" in API

Stop Enforce Times

Scheduled days and times to stop enforcement for this site.

yes

no

RV config file

"stopEnforceTimes" in API

Send White List Events

When the value is 1, the system sends all Events, whether or not the vehicle is on the White List (of authorized vehicles). When the value is 0, then the system only sends Events for vehicles not on the White List (unauthorized vehicles).

yes

no

RV config file

"sendWhiteListEvents" in API

Camera Recording Time

How much time before and after the Event to record video

yes

yes

RV config file

"camerasRecLength"; "timeBeforeRec"; "timeAfterRec" in API. "Video Pre/Post Time" in GUI in Camera section.

White List

An array containing all the plate numbers belonging to the White List (of authorized vehicles)

yes

no

Separate encrypted file on disk

"updateWhiteList" POST message in API

3. Computer and Software Requirements

  • Computer running with Windows 10 or later

  • Chrome or Microsoft Edge browser

4. Use IZ Discovery

The factory default IP address of the IZIDPUGOX Data Processing Unit (DPU) is on the sticker on the device; typically 192.168.5.110. If needed, use IZ Discovery to change its IP address to one you have allocated in your network.

4.1. Installing and Using IZ Discovery

The IZ Discovery utility discovers all active devices connected to the network, and displays a list of their network parameters. These devices can include cameras and computers.

If any device on your network is connected via wireless, IZ Discovery will not recognize the device. In addition, if the computer running IZ Discovery is connected via wireless, you will not see any devices displayed.

  1. Download the IZ Discovery software (link)

  2. Run IZ Discovery

  3. When IZ Discovery first runs, you may see a Windows security warning. If so, click Run.

  4. If you see a message related to the Windows firewall, click Allow.

  5. IZ Discovery will start and display a list of devices on the network, according to their serial numbers (see Figure 1).

    1. Scroll down to find the device you are interested in. You can double-click to view/edit a specific device’s IP address parameters (see Section 4.2).

    2. Click Clear List to refresh the discovery process.

      IZ Disovery Main Screen
      Figure 1. IZ Discovery Utility

  6. If IZ Discovery does not recognize a device:

    • Press the device’s reset button (if available)

    • Reset the device by shutting off power/removing the LAN cable, waiting 5 seconds, and reapplying power

    • Check the LAN cable between your laptop and the network, and the LAN cable between the device and the LAN switch. Replace the cable(s) and run IZ Discovery again.

4.2. Changing a Device’s IP Address and Network Settings

IZ Discovery Network Setting Dialog
Figure 2. Changing the Device’s Network Settings

It is highly recommended to use a fixed IP address (not DHCP). A fixed IP address enables you to access the computer using the same URL every time, even after unexpected power outages.

A dynamic IP address may change upon device reboot. Before opening the web interface, you will have to find the current IP address of the device using IZ Discovery.

If you want to copy the IP address (for login to the device) you will need to uncheck the DHCP checkbox momentarily to make the address field accessible.

For devices using RoadView software, you can change the IP address using the RoadView Settings tab.

To change the device’s mode (fixed or dynamic [DHCP]), or IP address:

  1. Select the relevant line in the list of devices and double-click on it.

  2. The Network Settings window appears

  3. To change the mode:

    1. Check or uncheck the DHCP box

    2. Click Save

  4. To change the IP address:

    1. Verify that the address is not used by any other device on the network

    2. Be sure to uncheck the DHCP box

    3. Enter the network address parameters

    4. Write down the new IP Address and click Save

  5. The change should be reflected in the main dialog. This can take about a minute until the IP is obtained. If you do not see the change after this time, close IZ Discovery, and then reopen it.

  6. Verify that the IP address parameters have been changed to the ones you wanted. If not, you will have to log into the device (or RoadView) and change the IP address.

5. Prepare to Aim and Calibrate

Move a vehicle next to, and at the middle of the capture line. (This is the position at which the vehicle detector signals that the vehicle is present.) Ensure that the camera is aimed at the middle of the lane, and is at the required capture distance.

Alternatively, in a lab, position a license plate at the expected distance and height.

6. Log In to RoadView

6.1. Logging In

  1. Open a browser.

  2. Type in the IP address of the RoadView computer - the IZIDPUGOX.

    You must put "https://" before the IP address.

    For example:
    https://192.168.5.110

    If you see a browser security warning message:

    1. Click Advanced

    2. Click the "Continue" link

  3. You will see the login screen. Enter the default username and password (root, root):

    image
    Figure 3. Logging In to RoadView

  4. You should see the RoadView Live (Journal) tab (see Section 10).

6.2. Changing the Password (Multi-line Menu Icon)

  • Click on the multi-line menu icon at the upper right of the RoadView screen

  • Select "Change Password"

image
Figure 4. Change Password (Multi-line Menu)

  • Enter the new password and re-type it

image
Figure 5. Change Password Dialog

6.3. Logging Out (Multi-line Menu Icon)

  • Click on the multi-line menu icon at the upper right of the RoadView screen

  • Select "Logout"

image
Figure 6. Logout (Multi-line Menu)

7. Configure RoadView - Settings Tab

Use the Settings tab after the first installation or re-installation of the PTL system, or when some fundamental parameters need updating. For example, if the IZIDPUGOX was moved to a different location (time zone).

Configure the parameters in the order in this section of the document.

After clicking the Save button at the end of the Detector Configuration section, it will take several seconds before the Live tab can start displaying Events. Also, some defaults and/or available parameters may change, depending on the Detector Configuration "Mode" selected.

7.1. Software Version and DPU Information

The box at the upper right of the Settings screen shows:

  • The RoadView software version (verify that the version is correct)

  • The model, part number and serial number of the DPU that RoadView is communicating with:

image
Figure 7. Software Version and DPU Information Section

7.2. Network Settings

image
Figure 8. Network Settings Section

  • If needed, set the IZIDPUGOX IP address parameters.

  • Remember to click the Save button in this section; the change will be applied immediately.

The Network Settings refer to the IZIDPUGOX computer - NOT the computer on which the browser displaying the GUI is running.

It is highly recommended to use a fixed IP address (not DHCP). A fixed IP address enables you to access the DPU using the same URL every time, even after unexpected power outages.

7.3. Date and Time Settings

The Date and Time Settings refer to the location of the IZIDPUGOX computer - NOT the computer on which the browser displaying the GUI is running.

The Time Zone selections are organized by continent. For example, the "America/" prefix covers various cities and countries in North America (U.S. and Canada) and South America.
image
Figure 9. Date and Time Settings Section

Set Time (Automatically/Manually) - The preferred setting is "Set Time Automatically".

  • If Automatic, the date and time will be updated from a central NTP (Network Time) server; the server can be in the cloud or on a local NTP server. (The default is ntp.ubuntu.com.)

    • Enter the NTP server URL

    • Select the interval at which you want RoadView to poll for the date and time (selected from the Polling Interval dropdown).

    • Click the "Update Now" button to update the date and time immediately.

    • The icon (green check mark or red "x") indicates if the URL of the NTP server is correct, and if the connection to it was successful.

  • If an NTP server is not available, select Manual. Click in the Date and Time box to display a calendar/time popup.

  • Select a Time Zone; set it to the local time at the location in which the DPU is installed (not the UTC default).

  • Remember to click the Save button at the end of this section after making changes.

7.4. Web Protocols

image
Figure 10. Web Protocols Section

  • The parameters should already have been set for you; verify the settings look as they appear here.

  • If you need to change the settings, remember to click the Save button at the end of this section.

7.5. HTTP Integrations Security

image
Figure 11. HTTP Integrations Security Section

  • The parameters should already have been set for you; verify the settings look as they appear here.

  • If you need to change the settings, remember to click the Save button at the end of the Detector Configuration section.

7.6. Lanes

Use this section to add and configure Lanes.

image
Figure 12. Lanes Section

  • Edit - edit the Lane’s parameters

  • Delete - delete the Lane (a warning will be displayed)

  • Trigger - send a software trigger immediately to RoadView

    Each Lane number must be unique in the overall ALPR system.

    The images from all cameras capturing the same physical lane will be combined into a single Event.

    Each "Lane" is actually a virtual Lane. For example, if you have two cameras capturing the same physical lane, you will need to create two different "Lanes", and associate each camera with a different "Lane".
    image
    Figure 13. Add/Edit Lane Dialog

  • ID (required) - The identification number of the lane to be captured by the cameras. This number will appear associated with Events in the Live tab.

  • Name (required) - The name of the Lane as it will appear throughout the user interface (GUI).

  • Location - Select one of the following options:

    • Unknown - the camera’s position relative to vehicles is unknown.

    • Front - the camera in this Lane is capturing images from the front of vehicles

    • Rear - the camera in this Lane is capturing images from the rear of vehicles

  • Passageway - Unused

  • Ignore Opposite Direction - Unused

7.7. Cameras

image
Figure 14. Cameras Section

  • Edit - edit the camera’s parameters (see Figure 15)

  • Delete - delete the camera (a warning will be displayed)

  • Camera table headers: Camera ID, Lane ID, Name, URL, Type (as configured when the camera was added)

  • Image - Thumbnail image from a recent camera image

    If you add a camera, or edit a camera’s parameters and click the Save button in this dialog (even if you did not change the URL), you may see a warning icon in the Image column. The reappearance of the image indicates that the core software has restarted, and Events will resume being captured and displayed in the Live tab, with the following changes:
    - The Event ID will continue to increase from the last Event ID.
    - The history of previous Events for that camera will be cleared

  • Add Camera (button at end of Cameras section):

    image
    Figure 15. Add/Edit Camera Dialog

  • Lane ID - The identification number of the lane being captured by the camera(s). Select a Lane number you defined (see Section 7.6). This number will appear associated with Events in the Live tab.

    The images from all cameras capturing the same physical lane will be combined into a single Event.

    Using the same Lane ID for different cameras will combine the reads into one Event (see Section 7.6).

    You can position multiple cameras to be in different positions for the same lane (front/rear).

  • Camera ID - For internal use; should be unique in the overall ALPR system

  • Name - Camera name for internal use; should be unique in the overall ALPR system

  • URL - RTSP URL

  • Type - Type of camera (View)

  • Video Recording Enabled - Check the box to enable video recording

  • Video Pre Time - How much time before the Event to record video; set as shown

  • Video Post Time - How much time after the Event to record video; set as shown

7.8. Motorola Integration

Enable Motorola Integration and set the parameters as follows. Remember to click the Save button at the end of the Detector Configuration section after making changes.

image
Figure 16. Motorola Integration Section

  • Motorola URL - URL of the Motorola server

  • Motorola User Name - domain and username (in the form domain/username) to access the Motorola server

  • Motorola Password - password to access the Motorola server

  • Camera Port - the HTTPS port on which RoadView listens for commands from the Motorola server

  • Log Store Days - how long Motorola logs are stored in the RoadView database; also defines how long Events are stored in the offline queue

  • Keep Alive Interval - how often RoadView sends a Keep Alive message to the Motorola server

  • Offline Enabled - enables the Offline Queue for Events sent to the Motorola server; should always be enabled

7.9. Journal

image
Figure 17. Journal Settings Section

  • Check the Enabled checkbox - should always be enabled

  • Remember to click the Save button at the end of the Detector Configuration section after making changes.

7.10. Detector Configuration

  • Set the parameters as shown here

  • Remember to click the Save button at the end of this section after changing these parameters.

image
Figure 18. Detector Configuration Section

Explanations of frequently used parameters:

  • Mode - Note that parameters may appear or be hidden, depending on the chosen Mode.

    • NonTriggered - Events are created and reported by LPR video analytics

  • Region - Region for which characters on the plate will be recognized. Select from the following options:

    • Israel

8. RoadView - System Info Tab

  • The software version and DPU information appear as shown here

image

9. Calibrating a Camera Using RoadView

image
Figure 19. Calibration Tab

  1. When you see a vehicle at a typical capture position on the video, click on the video to pause it.

  2. It is recommended to use the view called "Draw image by maintaining aspect ratio (two-headed arrow)". You select this view by clicking on the right-most button at the upper left of the screen: image

  3. Select a camera from the dropdown list

  4. The Frame Width (horizontal) and Frame Height (vertical) are displayed at the lower left, and are set automatically.

  5. The Frame Timestamp at the lower left displays the date and time that the image is being taken/was taken by the camera.

  6. Aim the camera using the mounting bracket’s adjustment hardware (see Figure 20).

    1. Pan: Adjust the Pan so that the image of the license plate is in the horizontal middle of the Field of View.

    2. Tilt: Adjust the Tilt so that the image of every expected plate position (depending on the vehicle type, such as passenger cars, jeeps, trucks, etc.) will be in the middle of the screen (from top to bottom).

    3. Roll: Adjust the Roll so the license plate’s image is horizontally straight, parallel to the ground (not tilted to one side).

      image
      Figure 20. Pan/Tilt/Roll (Angle) Adjustments

  7. When the correct position is achieved, make a preliminary tightening of the mounting screws.

  8. Define the Region of Interest (ROI) by dragging on the corners (vertices) of the trapezoidal region. For optimum recognition accuracy, the ROI should be large enough to capture the region where plates could be found in images.

    The following settings for the cameras are saved separately. For example, you may want a Region of Interest that is different for each camera.

  9. Define the Plate Width Min: Events will only be created for plate reads whose width is greater than or equal to this parameter. Enter the desired value in the Plate Width Min text box.
    This parameter can also be configured by dragging the small circle on the horizontal line on the Calibration tab (expressed in pixels).
    This parameter can be used to ignore small plate reads. For example, if the image was taken when a vehicle is too far away, the characters are too small to be read - even by a human.

  10. Define the Plate Width Max: Events will only be created for plate reads whose width is less than or equal to this parameter. Enter the desired value in the Plate Width Max text box.
    This parameter can also be configured by dragging the large circle on the horizontal line on the Calibration tab (expressed in pixels).
    This parameter can be used to prevent false reads, such as large numbers on trucks.

  11. Direction (red arrow on video): Not used

  12. When you have finished, click the Save button. Wait several seconds for the display to refresh automatically, which indicates that the RoadView recognition software is running again with the updated parameters.

  13. When the correct position is achieved, make a final tightening of the mounting hardware.

  14. Repeat these steps for other cameras.

10. Verify System Operation

  • Using a license plate mounted in a lab, or by driving a vehicle through the lane, verify that an Event is generated with the correct plate read, as recorded in the RoadView Live (Journal) tab.

image
Figure 21. Live (Journal) Tab

  • Once the lane is active, verify that Events are being generated for each vehicle passing each camera, and that the recognition has sufficient accuracy and confidence.

  • You can use the Search tab to find Event records stored in the RoadView database.

  • Note that you can add/remove different columns on the Live and Search tabs by selecting "Configure Journal" from the multi-line menu at the upper right of the screen (see Section 6.2).

image
Figure 22. Search Tab

  • Click on each thumbnail under the large Event image pane to see overview and plate images

  • To see the video clip used to create the Event, click on the Video link under the thumbnails

  • You can use the System Status tab to check the statuses of different system components

image
Figure 23. System Status Tab

11. RoadView Troubleshooting

Table 2. RoadView Troubleshooting
Symptom Possible Solution

Thumbnails in Settings tab, in the Camera section at bottom have been replaced by red exclamation points and/or
The Live tab and Search tab are empty (no Events are detected)

  • Verify that each camera’s IP address, and the RoadView computer’s IP address are all on the same subnet.

  • Verify that stable power at the correct level is being supplied to the cameras, even when under a heavy processing load.

  • Verify that the IP address(es) configured in RoadView match the IP addresses that you configured in the camera(s). See Section 7.7.

Recognition rates are low

  • On the Calibration tab, increase the size of the Region of Interest (ROI) - it may be too small to capture plates with high confidence

  • On the Calibration tab, try to reduce the Plate Width Min and increase the Plate Width Max

Examine the video from the Camera on the Calibration tab:

  • If all license plates are not fully visible, re-aim the camera so that the each camera’s field of view fully covers the capture zone. For a more precise adjustment, verify that the license plate’s images are as close to the middle of the video display as possible.

  • If the images are spotted, remove dirt and dust from the front window of the camera with a soft cloth and mild soap

12. Legal Notices

12.1. Notice

Inex Technologies reserves the right to improve and enhance its product offerings. Thus, the illustrations and descriptions presented in this manual may differ in some respect from the products you receive.

Technical specifications are subject to change without notice.

In addition, please note that some figures are not drawn to scale, in order to illustrate the addressed issue more effectively.

All third-party trademarks are the property of their respective owners.

Inex Technologies cannot be held liable for technical and editorial omissions or errors made in this document; nor for incidental or consequential damages resulting from the furnishing, performance or use of this document.

Actions or circumstances that void the warranty are improper usage, improper handling without adequate electrostatic discharge (ESD) protection, defects resulting from natural disaster (fire, flood etc.) and unauthorized modifications or repair.

Power undervoltage, overvoltage and/or incorrect polarity will damage the unit and will void the warranty.

It is your responsibility to ensure that all wires connected to Inex Technologies' products have appropriate surge protection. Any damage due to electrical spikes (for example, lightning) is not covered by the warranty.

No part of this document may be reproduced in any form without permission from Inex Technologies.

12.2. Software Precautions

  • The use of any Inex Technologies' software products or any other software product referred to in this document with internet access shall be used wholly at your own risk. Inex Technologies does not take any responsibility for abnormal operation, privacy leakage or any other damages resulting from cyber attack, hacker attack, virus infection or any other internet security risks.

  • Proper configuration of all passwords and other security settings is the responsibility of the installer and/or end-user.

12.3. Legal Disclaimer

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE PRODUCT DESCRIBED, WITH ITS HARDWARE, SOFTWARE AND FIRMWARE, IS PROVIDED "AS IS", WITH ALL FAULTS AND ERRORS, AND OUR COMPANY MAKES NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, MERCHANTABILITY, SATISFACTORY QUALITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT OF THIRD PARTY. IN NO EVENT WILL OUR COMPANY, ITS DIRECTORS, OFFICERS, EMPLOYEES, OR AGENTS BE LIABLE TO YOU FOR ANY SPECIAL, CONSEQUENTIAL, INCIDENTAL, OR INDIRECT DAMAGES, INCLUDING, AMONG OTHERS, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, OR LOSS OF DATA OR DOCUMENTATION, IN CONNECTION WITH THE USE OF THIS PRODUCT, EVEN IF OUR COMPANY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

THE USE OF ANY Inex Technologies' SOFTWARE PRODUCTS OR ANY OTHER SOFTWARE PRODUCTS REFERRED TO IN THIS DOCUMENT WITH INTERNET ACCESS SHALL BE USED WHOLLY AT YOUR OWN RISK. Inex Technologies DOES NOT TAKE ANY RESPONSIBILITY FOR ABNORMAL OPERATION, PRIVACY LEAKAGE OR ANY OTHER DAMAGES RESULTING FROM CYBER ATTACK, HACKER ATTACK, VIRUS INFECTION OR ANY OTHER INTERNET SECURITY RISKS.

For details, see the Inex Software End User License Agreement.

© Inex Technologies, LLC - All rights reserved.

Doc. No. PTL-MAN-002b Ver. 2024-07-01