PROGRAMMING MANUALUSER MANUAL - Quercusdownloads.quercus.biz/speed/latest/manual/SmartLPR... · Software version 3.5. x Firmware version 3.5. x PROGRAMMING MANUALUSER MANUAL

Software version 3.5. xFirmware version 3.5. x

www.quercus.biz

www.quercus-technologies.com

www.quercus.com.br

PROGRAMMING MANUALUSER MANUAL

SmartLPR® Speed User Manual (v 3.5.x)

January 2014

© 2014 Quercus Technologies. All rights reserved.

This manual, including the information of the system described within the manual, is provided under a license and can

be solely used for the purposes described in the license. The contents of this manual are provided for information

purposes only and can be modified with no prior warning. The manual can not be fully or partially reproduced, placed

in a distribution system or released to third parties without the express permission of Quercus Technologies.

Safety Precautions

LED RADIATION

DON'T LOOK DIRECTLY USING OPTICAL INSTRUMENTS (MAGNIFYING GLASSES,

LENS OR MICROSCOPES)

LED PRODUCT RISK GROUP 1

● * MAXIMUM OPTICAL POWER OUTPUT: 29W

● * AVERAGE OPTICAL POWER: 0.9W

● PULSE DURATION: 1 ms pulses with regular inactivity intervals of 15ms.

● * WAVE LENGHT: 850 nm

● LED PRODUCT CLASS 1M, as to UNE-EN 62471:2009 standard

Don't look directly at the light source of the unit from a short distance (20 cm) for

more than 30 seconds in a row. The light source emits infra-red light unnoticeable to

the human eye but which can damage the retina in case of long exposures.

If you think that the light source is not working properly and you want to check it, use the

diagnostic tool that comes with the unit, set Live Camera on and point the light source to a

reflective object. Another easy method to see the light source working is by setting the Live

Camera on and facing the light source with a digital camera (for instance, any mobile

integrated camera). On the digital camera you will be able to see the led shinning (due to the

fact that digital cameras are infra-red sensitive).

Table of contents

Basic Concepts...............................................................................................................8

1. Introduction...........................................................................................................9

1.1. What SmartLPR® Speed is................................................................................9

1.2. System description...........................................................................................9

1.3. Operating Modes..............................................................................................9

1.4. Available models............................................................................................10

1.5. Optional parts................................................................................................10

1.6. Integration....................................................................................................11

1.6.1. Development Alternatives.........................................................................11

1.6.2. Communication Alternatives.....................................................................12

1.6.2.1. Single Central system and UDP..........................................................12

1.6.2.2. One central system per lane and UDP..................................................12

1.6.2.3. One central system per lane and RS-232.............................................13

1.7. Updates and compatibility...............................................................................13

1.7.1. Version numbers.....................................................................................14

1.7.2. Version compatibility................................................................................14

2. Before installation.................................................................................................15

2.1. Design and execution of civil works..................................................................15

2.2. Wiring..........................................................................................................18

3. Supplied material..................................................................................................19

3.1. List of materials.............................................................................................19

3.2. Optional parts................................................................................................20

Software.....................................................................................................................21

4. Introduction.........................................................................................................22

5. Client Software Installation....................................................................................23

5.1. Windows Installation......................................................................................23

5.2. GNU/Linux Installation....................................................................................23

5.2.1. Dependencies.........................................................................................23

5.3. Installed files.................................................................................................23

6. Central System Setup............................................................................................26

6.1. Section [Global].............................................................................................26

6.2. Section [Network]..........................................................................................26

6.3. Section [RemoteSystems]...............................................................................27

6.4. Section [RemoteSystemX]...............................................................................27

6.5. Section [LaneY].............................................................................................27

7. Diagnosis tool.......................................................................................................29

7.1. Status bar.....................................................................................................29

7.2. Button Bar....................................................................................................30

7.3. Main Zone.....................................................................................................32

7.3.1. Status....................................................................................................32

7.3.2. Events...................................................................................................33

7.3.3. History...................................................................................................35

7.3.4. Live Camera...........................................................................................36

7.3.4.1. Numerical/graphical focus..................................................................38

7.3.5. Statistics................................................................................................38

7.3.6. Configuration..........................................................................................40

7.3.7. FTP........................................................................................................40

Hardware....................................................................................................................43

8. Equipment description...........................................................................................44

8.1. Pinouts.........................................................................................................44

8.1.1. Ethernet.................................................................................................44

8.1.2. Serial.....................................................................................................45

8.1.3. I/O........................................................................................................45

8.2. Serial communication properties......................................................................45

8.3. Input/Output system characteristics ................................................................45

8.3.1. Inputs....................................................................................................45

8.3.2. Outputs..................................................................................................46

8.4. Temperature control.......................................................................................46

9. Firmware.............................................................................................................48

9.1. Main system configuration...............................................................................50

9.1.1. Variables................................................................................................51

9.1.1.1. Communications...............................................................................51

9.1.1.2. Engine.............................................................................................52

9.1.1.3. Global.............................................................................................52

9.1.1.4. I/O.................................................................................................53

9.1.1.5. OSD................................................................................................53

9.1.1.6. PPU.................................................................................................54

9.1.1.7. Recognizer.......................................................................................55

9.1.1.8. Serial..............................................................................................56

9.2. Import configuration with FTP..........................................................................57

9.3. Export configuration with FTP..........................................................................57

9.4. Change configuration system password.............................................................57

9.5. Apply changes and reboot...............................................................................57

9.6. Discard changes.............................................................................................57

9.7. System information........................................................................................57

9.8. Recognizer log...............................................................................................58

9.9. Serial adapter log...........................................................................................58

9.10. File system log.............................................................................................58

9.11. Configuration Log ........................................................................................58

9.12. View recent recognitions...............................................................................58

9.13. View last captured images.............................................................................59

9.14. Export system status to FTP..........................................................................59

9.15. Contact info.................................................................................................59

9.16. Adjust the date and time...............................................................................59

9.17. Synchronize time with server.........................................................................59

9.18. Firmware update..........................................................................................59

9.18.1. Steps required before updating...............................................................60

9.18.2. Update.................................................................................................60

9.19. Restore original firmware..............................................................................61

9.20. Format data disk..........................................................................................61

9.21. Restoring configuration parameters................................................................62

9.22. Firmware emergency restore.........................................................................63

10. Step by step installation.......................................................................................64

10.1. Wall installation............................................................................................64

10.2. Ceiling installation........................................................................................64

10.3. Vertical mast installation...............................................................................65

10.4. Common Procedures.....................................................................................66

10.5. Optical adjustment.......................................................................................68

10.6. Basic firmware configuration..........................................................................70

10.7. Closing the unit............................................................................................70

Annexes......................................................................................................................71

11. Annex A: SmartLPR® Power Process Unit..............................................................72

11.1. Introduction.................................................................................................72

11.1.1. What SmartLPR® Power Process Unit is...................................................72

11.1.2. Compatibility.........................................................................................72

11.1.3. Capacity...............................................................................................72

11.1.4. Integration...........................................................................................72

11.2. Equipment description..................................................................................73

11.2.1. Components..........................................................................................73

11.2.2. Electrical installation..............................................................................73

11.2.3. Wiring..................................................................................................73

11.3. Firmware.....................................................................................................73

11.3.1. Settings................................................................................................74

11.3.1.1. Communications.............................................................................74

11.3.1.2. Engine...........................................................................................74

11.3.1.3. Global...........................................................................................74

11.4. Step by step installation................................................................................75

11.4.1. Hardware installation.............................................................................75

11.4.2. Client software update...........................................................................75

11.4.3. Setting up SmartLPR® Power Process Unit...............................................75

11.4.4. Setting up SmartLPR® unit ....................................................................76

11.5. Technical specifications.................................................................................77

12. Annex B: Technical specifications..........................................................................78

12.1. DC powered models......................................................................................78

12.2. AC powered models......................................................................................80

13. Annex C: CE Certificates......................................................................................81

14. Annex D: FCC Certificate......................................................................................84

15. Annex E: In case of malfunctioning.......................................................................88

16. Annex F: Support................................................................................................89

17. Annex G: [Global] TimeZone values......................................................................90

SmartLPR® Speed User Manual Basic concepts

Basic Concepts

This section provides a basic summary of the characteristics of a SmartLPR® Speed system. It

includes the basic operation of the system, models available, the different alternatives of

development and communications, as well as the previous steps required before installing the

equipment.

Quercus Technologies 8


1. Introduction

1.1. What SmartLPR® Speed is

SmartLPR® Speed is an LPR system which has been specially designed to be used in open

traffic lanes (without a barrier), where vehicles can travel at high speed1.

SmartLPR® Speed is based on All-In-One concept, which embeds in a single equipment all the

operations needed for license plate recognition (image acquisition and further processing), so

that installation becomes much easier compared to systems using different capture and

process units.

1.2. System description

SmartLPR® Speed is composed of a single set of hardware that must be installed in each lane

to be controlled.

The equipment integrates all elements required for I/O signals, communications, lighting of a

specific area, image capture and processing.

1.3. Operating Modes

The main purpose of SmartLPR® Speed is to provide the license number of vehicles in

controlled lanes to the client application, regardless of its nature.

The system has three operating modes:

● Continuous: SmartLPR® Speed captures and process images in a continuous and

indefinite way. The best recognition result for each vehicle is notified to the client

application.

● Software Trigger: the client application notifies SmartLPR® Speed of the presence of a

vehicle. The vehicle image is automatically captured and processed. The results

obtained are sent back to the client application.

● Hardware Trigger: SmartLPR® Speed itself directly receives the information about

the presence of a vehicle from a sensor installed in the lane. The client application is

immediately notified about it. Then, the vehicle image is captured and processed. The

results obtained are sent back to the client application. When the vehicle leaves the

lane, the client application is once again notified.

1 Recognition rate is not affected for speed up to 200 km/h. At higher speed, this rate can decrease.



1.4. Available models

There are various unit models of SmartLPR® Access that allow to satisfy different

requirements. According to the criteria, the models are the following:

Number of simultaneous countries

● SmartLPR® Speed: limited to simultaneously recognize license plates from 5

countries.

● SmartLPR® Speed Plus: no limits of simultaneous countries.2

Power

● Alternate current: works from 110VAC to 240VAC and 50 Hz to 60Hz.

● Direct current: requires power from an external 12VDC network.

Temperature control

● Without temperature control module: does not provide protection against extreme

temperatures.

● With temperature control module: provides protection against extreme

temperatures and increases its working range.

All models are absolutely compatible (at a software level) amongst them and can be combined

in the same installation without any problem. Check the lists at the end of this manual to know

the references and technical specifications of each model.

1.5. Optional parts

The following parts are available for case housing models:

● Wall mount: with rotating and tilting head, that allows to fix the unit on any wall and

position it properly.

● Celling support: with rotating and tilting head, that allows to fix the unit on any wall

and position it properly.

● Tube adapter: to be used together with a wall mount or a ceiling support, it allows to

fix the unit in any horizontal or vertical mast.

2 It is not recommended to enable the simultaneous recognition for more countries than the ones strictly necessary, as the system performance could decrease.



1.6. Integration

SmartLPR® Speed communicates with the client application using the protocol described in the

SmartLPR® Programming Manual. The same protocol is used for communications using RS-232

and UDP/Ethernet.

1.6.1. Development Alternatives

In the case of UDP/Ethernet communications, the protocol is embedded in C and C++ libraries

which are compatible with Microsoft Windows and GNU/Linux. These libraries simplify the

communications between the client application and various SmartLPR® Speed units and add

specific functionalities, such as log register.

The advantages and disadvantages of each integration method are described next:

● Class library in C++: dynamically linked library for Windows and GNU/Linux that

provides an object oriented vision of the system. The source code of a proxy in a fully

portable C++ language is provided with the dynamically linked library, which can be

used with any C++ compiling program. The library manages the simultaneous and

transparent communications with various lanes. It implements a high level interface

which facilitates the programming tasks in C++. Available for Windows or GNU/Linux

systems.

● Function library in C: dynamically linked library for Windows and GNU/Linux that

provides a function oriented vision of the system.

As in the case of the C++ library, the source code of a proxy in a fully portable C

language is provided with the library, which can be used with any C compiling program.

It also manages the simultaneous and transparent communications with various lanes.

Allows to program in C while keeping the high level vision provided by the C++ library.

It can be used with both C and C++ languages. Available for Windows or GNU/Linux

systems.

● Through UDP or serial protocols of SmartLPR® Speed: The definitions of the

protocol used for the communication activities are provided in a header file (SA.h)

including examples of use, programmed in ANSI C. In addition, the basic routines for

UDP communications are also provided in UDPTools.c and UDPTools.h files. With these

files, any client application that interacts with SmartLPR® Speed can be programmed

from any device with network or serial transmission capabilities.



1.6.2. Communication Alternatives

SmartLPR® Speed units communicate with the client application (which is referred to as the

“Central System” in SmartLPR® Speed) in two different ways:

● Using the UDP protocol: use of a standard 10/100 Mb Ethernet network.

● Using RS-232 serial communication: the SmartLPR® Speed setup system can be

used to select the speed, parity, etc. of the serial communications. (for more

information see the “Setup” chapter)

The different communication methods along with the possibility of having a different central

system for each lane or a central system for all lanes generate the following configurations:

1.6.2.1. Single Central system and UDP

Typical configuration of a central machine where a control application runs, which is, in turn, in

charge of the registration of movements and the management of all communications with the

lane equipment.

1.6.2.2. One central system per lane and UDP


Ethernet

SmartLPR unit

SmartLPR unit

SmartLPR unit

Central system

Lane equipment

Lane equipment

Lane equipment


This is the most common setup used when each SmartLPR® Speed lane has to directly

communicate with the equipment of its associated lane. Each device acts as the central system

of the unit on each lane.

1.6.2.3. One central system per lane and RS-232

Similar to the previous one, this configuration is used in lanes where the equipment does not

have a network card.

1.7. Updates and compatibility

The software delivered with the unit is valid for every license plate recognition products of

SmartLPR® family.

SmartLPR® family of license plate recognition units have a firmware (internal execution

software) which can be updated.


SmartLPR unit

SmartLPR unit

SmartLPR unit Lane equipment

Lane equipment

Lane equipmentEthernet

Ethernet

Ethernet

SmartLPR unit

SmartLPR unit

SmartLPR unit Lane equipment

Lane equipment

Lane equipmentRS-232

RS-232

RS-232


1.7.1. Version numbers

Each version number of software/firmware is composed of three numbers (for example 2.4.5):

● The first number (named “major”) shows the main software/firmware version. It

indicates how many times important external/internal changes have been made.

● The second number (named “minor”) indicates how many times new functionalities

have been added to the major version.

● The third (named “revision”) indicates how many times errors have been fixed in the

“major.minor” version.

The initial version of every SmartLPR® product is 1.1.0.

1.7.2. Version compatibility

Client software is always backwards compatible, so you can control all SmartLPR® versions by

using the latest one.

In order to know if a firmware update is compatible with your unit, the current version must be

checked and compared with the update version.

Version Compatible Firmware Update Required

Different first number No3 X

Same first numberDifferent second number

Yes Yes

Same first and second numbersDifferent third number

Yes No

3 Compatibility is not excluded. It is just not guaranteed. Contact with Quercus Technologies Support Department.



2. Before installation

2.1. Design and execution of civil works

SmartLPR® Speed units can be installed in two different ways:

● Front installation: the unit is able to work under the three available methods, which

are hardware trigger, software trigger and continuous.

● Rear installation: possible but not recommended. Lots of vehicles (lorries, 4x4, etc.)

have their plate in a position impossible to be completely visualized from a high point

(hidden by the trailer if the vehicle is a lorry or by the spare wheel in case of a 4x4

vehicle, etc.). This renders a non-optimal result when reading rear license plates.

Several parameters will depend on the installation height and the maximum lane width (image

bottom) to be captured. The following diagrams show the different system parameters:


SmartLPR S

peed units

Sensors

Image capture

SmartLPR S

peed units

Sensors

Image capture


Camera installation possibilities are all detailed in the table below:


General view

Sensors

SmartLPR S

peed

Image capture zone (L2)

Distance (L1)

Hei

gh

t (h

)

Side view

Camera angle (β)

Image capture zone (L2)

Distance (L1)

Hei

gh

t (h

)

Aerial view

A2 A1


h A1 L1 A2 L2 β Zoom Max. Speed

4.0 1.8 8.5 2.5 3.7 21.7 25.1 200

4.0 2.0 7.25 2.8 3.7 14.5 19.9 200

4.0 2.2 6 3.2 3.7 28.1 15.7 200

4.5 1.8 9.75 2.4 3.6 21.7 28.6 200

4.5 2.0 8.25 2.7 3.6 24.7 22.5 200

4.5 2.2 7.75 3.0 3.9 25.6 19.5 200

5.0 1.8 11 2.3 3.5 21.7 32.2 200

5.0 2.0 9.5 2.6 3.6 24.3 25.8 200

5.0 2.2 8.5 2.9 3.7 26.4 21.5 200

5.5 1.8 12.5 2.2 3.5 21.3 36.4 200

5.5 2.0 10.75 2.5 3.6 24.0 29.0 200

5.5 2.2 9.5 2.8 3.6 26.4 24.0 200

6.0 1.8 14 2.2 3.6 21.0 39.0 200

6.0 2.0 12 2.5 3.5 23.8 32.2 200

6.0 2.2 10.5 2.8 3.6 26.4 26.4 200

6.5 1.8 15.5 2.2 3.6 20.8 -- 200

6.5 2.0 13.25 2.4 3.5 23.6 35.4 200

6.5 2.2 11.5 2.7 3.5 26.4 28.8 200

7.0 1.8 15.5 2.1 3.3 22.4 -- 185

7.0 2.0 14.75 2.4 3.6 23.1 39.0 200

7.0 2.2 12.75 2.7 3.6 26.0 31.7 200

7.5 1.8 15.5 2.1 3 24.0 -- 173

7.5 2.0 15.5 2.4 3.5 23.7 -- 200

7.5 2.2 14 2.6 3.6 25.6 34.6 200

8.0 1.8 15.5 2.0 2.9 25.4 -- 162

8.0 2.0 15.5 2.3 3.3 25.2 --- 183

8.0 2.2 15 2.6 3.5 25.7 37.1 200

Where:

● h: Camera height (meters).

● A1: Image bottom width (meters).

● L1: Horizontal distance between the camera and the image bottom (meters).

● A2: Image top width (meters).

● L2: Image depth (meters).

● β: Angle camera-ground (degrees).

● Zoom: Camera zoom (focal distance in mm).



● Max Speed: Maximum speed allowed for vehicle capture (km/h).

In general, recognition rate increases as lane width is smaller because the images captured of

the plates will be bigger. However, width decrease can also produce a loss on the maximum

speed that vehicles can reach while being captured from the highest points.

To work in “Trigger Hardware”, sensors must provide a signal with a time duration of more

than 25 ms for each vehicle detection.

The correct operation of any LPR system depends on several external factors. Most of these

factors can be optimized if considered during sensor and camera location design. Quercus

Technologies can only guarantee an optimum performance of the SmartLPR® Speed

system if the design of the different parts of the system is carried out observing the

guidelines described above. If there are any unavoidable, physical limitations, which do not

allow you to follow the indicated procedures, it is important to install the capture units with the

assistance of Quercus Technologies Support department.

2.2. Wiring

Each SmartLPR® Speed recognition unit must have the following cables:

Power

● shielded power cable: 3x1.5mm² or 2x2.5mm² cross-section (direct current) or

● shielded power cable: 3x1.5mm² cross-section (alternate current)

Networking

● Shielded Network cable: UTP cable, category 5 (ethernet networking) or

● 3-wire serial shielded cable (RS-232 serial port communication).

I/O (optional)

● 12-pin shielded cable (if 2 inputs and 8 outputs are required) with a 0.22mm2 cross-

section.

3. Supplied material

3.1. List of materials



1. Recognition unit.

2. Optical lens.

3.2. Optional parts

1. Wall support.

2. Ceiling support.

3. Tube adapter.

4. Flat adapter (to be used with ceiling support).


1 2 3 4

SmartLPR® Speed User Manual Software

Software

This section describes the client software available on the CD-ROM, as well as the installation

procedures and its configuration process.

No physical units of SmartLPR® Speed are required to follow the steps described in this

section, since only the client software is installed, which is the software used to communicate

and interact with one or more units.



4. IntroductionTo better understand this section, we must incorporate a series of concepts that will repeat in

the description of the SmartLPR® Speed software (in the diagnostic tool, setup phase, etc.).

In a SmartLPR® Speed client application (programmed using Quercus Technologies

development libraries), the units are grouped by means of logical process in “remote

systems”. A remote system is described as a group of SmartLPR® Speed units on which certain

actions can be applied at the same time (restart and obtain the status, among others). The

number of remote systems in a SmartLPR® Speed application and the number of units in a

remote system are unlimited.

The purpose of grouping units in remote systems is to provide a common link for each group of

units. For example, in case of installing a SmartLPR® Speed system in a parking with two

groups of lanes which are far apart from each other (let's call them “north” and “south”), when

we have the units divided into two remote systems (one for “north” lanes and another one for

“south” lanes), the parking operators will be able to easily identify the parking area affected in

the case of, for example, a communication breakdown.

The following diagram shows an example of the application with five SmartLPR® Speed units

divided into two remote systems with three and two units, respectively.


SmartLPR

Remote systemSmartLPR

Remote systemSmartLPR

SmartLPR unitSmartLPR unitSmartLPR unitSmartLPR unitSmartLPR unit

North lanes South lanes


5. Client Software InstallationDownload the latest software version to be found at the following web page:

http://downloads.quercus.biz/

As this software is always backwards compatible, the latest version can be used with all units

unless the opposite is explicitly agreed.

5.1. Windows Installation

Run the installation program “setup .exe” and follow the installation steps here.

If the system has already installed an older version of this software, and the newer release

only differs in revision number ( for example the installed version is 2.2.3, and the new version

is 2.2.5), the software will be installed in the same folder overwriting only the necessary files,

and leaving one uninstall menu entry.

5.2. GNU/Linux Installation

Run the installation program you have downloaded and follow the installation steps.

5.2.1. Dependencies

The executable files for GNU/Linux are dynamically linked, thus the following components must

be installed. All those components are installed (or available for their installation) in any

modern Linux distribution.

To develop and run the programs without a graphic interface:

● glibc v2.3.2: http://www.gnu.org/software/libc/libc.html

To run the programs with a graphic interface you will also need:

● XFree86-libs v4.3.0: http://ftp.xfree86.org/pub/XFree86/

5.3. Installed files

The following sub-folders are found in the installation folder:

● Bin: Executable files and libraries. Includes the following files:

● SLPRDiag(.exe): diagnostic tool. Allows to check the operation of different units,

from a central system.

● AccessSimu(.exe): SmartLPR® Access unit simulator (text mode) used to


http://downloads.quercus.biz/

http://ftp.xfree86.org/pub/XFree86/

http://www.gnu.org/software/libc/libc.html


develop client applications for SmartLPR® Access without the need of a physical

unit. For more information, see the SmartLPR® Programming Manual .

● AccessSimuGui(.exe): SmartLPR® Access unit simulator (graphic mode) used to

develop client applications for SmartLPR® Access without the need of a physical


● SpeedSimu(.exe): SmartLPR® Speed unit simulator (text mode) used to develop

client applications for SmartLPR® Speed without the need of a physical unit. For

more information, see the SmartLPR® Programming Manual .

● SpeedSimuGui(.exe): SmartLPR® Speed unit simulator (graphic mode) used to

develop client applications for SmartLPR® Speed without the need of a physical


● ComBridge(.exe): Serial adapter, transforms UDP frames into serial frames.

Used to simulate a unit with serial communications.

● ComBridgeGui(.exe): Serial adapter (graphic mode), transforms UDP frames into

serial frames. Used to simulate a unit with serial communications.

● SA.dll (Windows) or libSA.so (Linux): Dynamically linked library required to run

client applications in C/C++.

● SLPRDiag.bin (Linux): Diagnostic tool binary file, Not to be used directly, as it is

used by SLPRDiag.

● AccessSimuGui.bin (Linux): binary file of SmartLPR® Access Simulator (graphic

mode). It must not be directly called, as it is used by AccessSimuGui.

● SpeedSimuGui.bin (Linux): binary file of SmartLPR® Speed Simulator (graphics

mode). It must not be directly called, as it is used by SpeedSimuGui.

● ComBridgeGui.bin (Linux): binary file of serial adapter (graphics mode). It must

not be directly called, as it is used by ComBridgeGui.

● lib*.so (only in GNU/Linux): all libSA.so dependencies (except glibc y Xfree86).

● /libs (only in GNU/Linux): All the executables dependencies (except glibc and

Xfree86).

● Data: Setup data and files which are required by the diagnostic tool and the simulator

for their correct operation.

● Doc: contains this manual, the SmartLPR® Access manual and SmartLPR® Programming

manual.

● Include: Contains the C/C++ header files required to develop using either the libraries

of these languages or the type library (TLB). It contains the definition of the protocol

frames in a C structure.

● Log: Folder where the records of different programs will be stored, as well as the

history of all the movements.



● Redist(Windows): Visual C++ run-time libraries.

● Samples: Programming samples using the different alternatives: C, C++, and protocol.

See the “Readme.txt” file in the folder for more information.

● Simulations: Simulations of the operating mode of SmartLPR® Access and SmartLPR®

Speed units. Each simulation contains a .bat file or a script, which is required in order

to properly execute them. For further information refer to the "Readme.txt" file from

the mentioned folder and to the SmartLPR® Programming manual.

● Src: C/C++ source code files required in order to use a library in C++, as well as a

group of help functions for the management of UDP communications.



6. Central System SetupThe central system will be set up by means of a text file. The client application must use this

setup file to initialize the development library of SmartLPR® Speed (be it C or C++).

The setup file can have any name and it can be stored anywhere in the client machine.

However, if you are going to use it from the “SLPRDiag” diagnostic tool (see the 7 Diagnostic

tool section for more information) it must be stored in the “Data” folder of the installation

directory and it must be called “Central.ini” since that is what SLPRDiag expects to find.

The file is divided into sections, and each section has a series of variables of the

“Variable=Value” type. Spaces can be left before and after the “=” symbol, since they will be

ignored.

6.1. Section [Global]

Includes the general system parameters.

● LogLevel: Level of information shown in the records. Possible values:

● 1: Message: all messages will be displayed.

● 2: Warning: Only warning or error messages will be displayed.

● 3: Error: only error messages will be displayed.

● HistoricSize: Number of movements stored per detection unit. The movements are

stored in the folder where the log file is located (<installation folder>/Default Log)

RemoteX/LaneY” where “X” and “Y” represent remote system and lane index,

respectively. Each movement involves the storage of two files, one with the movement

data (license number, time, etc.) and a jpeg image with the photograph of the vehicle.

Therefore, limitations on the number of files contained in one folder must be taken into

account when setting this value.

6.2. Section [Network]

Contains general network parameters.

● ConfigPort: UDP port which will receive answer messages from the unit configuration

system. The default value is 7040.

● ListeningPort: UDP port which will receive unit messages. The default port used to

receive messages is 7050, so we recommend using this value.

● Password: encryption password. Please consult the SmartLPR® Programming manual.

● Timeout: Time to wait, in milliseconds, from the moment of sending a message to a



unit until it is considered that the message has not reached its destination and it has to

be resent (or canceled if the number of retires has been exceeded). The recommended

value ranges between 300 and 1000 (if the network of the units has heavy traffic, this

value may be slightly higher).

● Retries: number of retries to send a message before considering it could not be sent.

The recommended values are 2 to 3 retries.

6.3. Section [RemoteSystems]

Contains the information applicable to all remote systems.

● MonitoringPeriod: Seconds between checks on the unit status. The recommended value

is between 10 and 30 seconds.

● RSNumber: number of remote systems in which the system is divided. There has to be

as many RemoteSystemX sections as indicated here and they must be numbered from

1 to X. The remote systems will appear in the collection of remote system lanes

accessible from the development libraries (as well as from the diagnostic tool) in the

order declared here.

6.4. Section [RemoteSystemX]

Contains the “X” remote system parameters.

● RSLanes: comma-separated list, containing the units grouped under this remote

system. The grouped units will appear in the collection of remote system lanes

accessible from the development libraries (as well as from the diagnostic tool) in the

order declared here.

6.5. Section [LaneY]

Contains the “Y” lane (or unit) parameters.

● ConfigPort: UDP port where the unit will wait for configuration messages from the

Central System. The default setup is 7039, thus this is the recommended value.

● Host: IP address of the unit. Names can be used instead of the IP Address, in which

case access must be configured to a DNS server which will translate the names into IP

addresses.

● Port: UDP port where the unit will wait the messages from the central system. The

default setup is 7051, thus this is the recommended value.



Example of a setup file

[Global]LogLevel=2HistoricSize=100

[Network]ListeningPort=7050Timeout=300Retries=2ConfigPort=7040Password=

[RemoteSystems]MonitoringPeriod=10RSNumber=2

[RemoteSystem1]RSLanes=1,2

[RemoteSystem2]RSLanes=3

[Lane1]Host=192.168.1.201Port=7051ConfigPort=7041





7. Diagnostic toolThe SLPRDiag diagnostic tool can be used by the operator to check the capture units operation

from the central system.

To use the diagnostic tool, shut down the client application (if running), since both use the

same UDP port to receive messages from units, and they cannot be operating at the same

time.

The program can be run with or without arguments. If it is not executed with arguments, the

program will look for the setup file in “<SLPRDiag folder>/../Data/Central.ini” and the log file

will be stored in “<SLPRDiag folder>/../Log/Central.log”. However, if it is executed with

arguments, the first argument must be the path of the setup file and the second one the path

of the log file. Example: SLPRDiag Central2.ini Central2.log.

The application is divided into three zones:

● Button Bar.

● Main zone.

● Status bar.

7.1. Status bar

It is located at the bottom part of the screen. Shows additional information depending on


Button Bar

Main Zone

Status bar


which tab is active in the main zone.

7.2. Button Bar

The Button bar occupies the upper part of the screen. The buttons are grouped by

functionality: some of the buttons are applicable only under specific circumstances and with a

certain tab activated; on the other hand, some are applicable independent of the active tab.

The groups of buttons available are:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18

Main Buttons

They run the most basic actions of the application:

1. Exit: Quits application.

2. RemoteSystem/Lane selection: The first box (2) selects the remote system and the

second (3) the lane inside the remote system. If “All” is selected in the remote system

box, all actions will have effect on all remote systems; if a remote system is selected,

and “All” in the lane box, actions will have effect on all lanes of the selected remote

system; if a remote system and a lane are selected, actions will have effect only on the

selected lane. Depending on the selection made in these two boxes, some of the tabs

may have more or less available functionalities.

3. See 2.

Action Buttons

They enable actions onto the selected tab. Some of the buttons will only be available for

certain combinations of remote system/lane and/or specific tabs:

4. Exposure time selection: (see below the description of the tabs, 7.3.Main Zone).

5. Start: (see below the description of the tabs).

6. Stop: (see below the description of the tabs).

7. Clear/Restart: (see below the description of the tabs).

8. First: (see below the description of the tabs).

9. Previous: (see below the description of the tabs).

10.Next: (see below the description of the tabs).

11. Last: (see below the description of the tabs).

Function Buttons

Functions independent of the selected tab:



12.Send Trigger: Available only when there is a selected lane; it sends a “trigger” signal

(capture and recognition of the license plate) to the lane. The trigger identifier starts

with “1” when the application starts, and increases by 1 unit each time the button is

pressed. Lanes not configured in software mode will return error.

13.Reboot selected lane: Always available, allows to reboot the selected lane (or lanes).

The application will ask for confirmation before sending the order to the unit/s.

14.Enable Output:: Available only when there is a selected lane; it is used to activate or

deactivate one bit of the Input/Output unit board.

Once pressed, the following window will appear: Here you must choose the bit and the

duration (or set “Always On”), and then click “Activate” button to send the order to the

unit. To deactivate a previously activated bit, set a time of zero for that bit and click

“Activate”.

15. (De)Activate Lane: Available only when there is a selected lane; makes the unit answer

or not to external events (triggers, changes in I/O board, etc.). The application will ask

for confirmation before sending the order to the unit.

Help Buttons

Manuals and other help resources.

16.SmartLPR® Access Manual: shows the SmartLPR® Access User Manual in Pdf. You need

to have a PDF viewer associated to this type of files (you will find Acrobat Reader in the

installation CD of SmartLPR®).

17.SmartLPR® Speed Manual: shows the SmartLPR® Speed user manual in Pdf. You need

to have a PDF viewer associated to this type of files (you will find Acrobat Reader in the

installation CD of SmartLPR®).



18.About: shows information about Quercus Technologies.

7.3. Main Zone

The main zone is divided into tabs. The combination of remote system/ selected lane in the

button bar changes the behavior of the tabs.

7.3.1. Status

Indicates the status and notifications of the element selected in the button bar (All/one remote

system/Lane). Divided into two parts: The upper part shows the status of the element

selected, and the lower part the notifications associated to it.

Status will show the following data:

● With the entire system selected:

● Status: General status of the system. It will show correct only when the status

of all the lanes of all the remote systems are correct.

● With a remote system selected:

● Id: Remote system identifier.

● Status: Remote system status. It will show correct only when the status of all



the lanes in the remote system are correct.

● Networking status: networking status of the remote system. It will be correct

only when the networking status of all lanes in the remote system is correct.

● With a selected lane:

● Id: Lane identifier.

● Networking status: networking status of a lane. If this field shows error, the rest

of fields will not show any data.

● I/O board status: Shows the lane I/O board status. As this board is optional, if it

is not present, the field will show correct.

● Camera status: Status of the camera unit.

● Active: Shows if the unit is active (answers to external events as messages, I/O

changes, etc. ) or not. In that case the unit will not react to external events. To

activate or deactivate the unit use the button for this purpose from the button

bar.

● Firmware version: Shows the SmartLPR® Speed firmware version running in the

unit.

The notifications will show the following information:

● Time: Date and time when the notification arrived, in a year-month-day hour-minute-

second format .

● Remote system: Remote system where the notification came from.

● Lane: Lane that sent the notification.

● Description: Description of the generated notification.

Active Buttons

● Clear/Restart: Empties the notification list.

7.3.2. Events

Shows the events produced in the selected item (All/remote system/lane). The events shown

are changes in the I/O board, arrivals or departures of vehicles, or, mainly, license plate

recognitions. The main actions done by the user, are also printed in this tab.



The window is divided into 4 parts:

● Image: Image of the last recognition made. Located in the upper part of the window.

The license plate will be framed if it has been recognized and it is compliant with the

grammar of any configured country.

● License plate information: License plate data of the last recognition made. Data shown

is:

● Lane: Remote system and lane identifier where the recognition was made (comma

separated).

● License plate: recognized license plate.

● Time: Date and Time of the recognition ( year-month-day hour:minute:second format).

● Quality: Average quality of the characters recognized and, between brackets, minimum

quality found.

● Vehicle Id: vehicle identifier.

● Trigger: identifier of the trigger event.

● Country: Country or countries that matched the license plate.

● Roi: Rectangle where the license plate was found.

● Brightness: Allows to adjust the brightness of the images at the screen. It is located at

the bottom left part of the window.



If the “Active” box is checked, the application will try to automatically decrease or

increase the brightness of the image so that all license plates appear with a similar

brightness. To manually adjust the brightness, the “Auto” check box must be

unchecked and adjusted as desired with the control placed for that purpose. Once the

brightness is manually set, the value will remain the same even for new recognitions.

Warning: This control only modifies the way the application shows the images to the

user. It does not modify the brightness of the pictures stored in the disk history.

● Events list: List of generated events. It shows date and time, remote system and lane,

and a short description of the event.

Active Buttons

● Clear/Restart: Empties the notification list.

7.3.3. History

Shows recognition data stored in the disk history.

This tab will only display data if the active item in the button bar is a lane; the window will

appear empty if the active item is a remote system or the whole system.




● Image: Stored image for the recognition. It is located in the upper part of the window.

The license plate will be framed if it has been recognized and it is compliant with the

grammar of any configured country.

● License plate information: License plate data of the last recognition. Data shown is:

● Lane: Remote system and lane identifier where the recognition was made

(comma separated).

● License plate: recognized license plate.

● Time: Date and Time of the recognition ( year-month-day hour:minute:second

format).

● Quality: Average quality of the characters recognized and, between brackets,

minimum quality found.

● Vehicle Id: vehicle identifier.

● Trigger: identifier of the trigger event.

● Country: Country or countries that matched the license plate.

● Roi: Rectangle where the license plate was found.

● Brightness: Allows to adjust the brightness of the images at the screen. It is

located at the bottom left part of the window.

If the “Active” box is checked, the application will try to automatically decrease

or increase the brightness of the image so that all license plates appear with a

similar brightness. To manually adjust the brightness, the “Auto” check box

must be unchecked and adjusted as desired with the control placed for that

purpose. Once the brightness is set manually, the value will remain even for new

recognition.

Warning: This control only modifies the way the application shows the images

to the user. It does not modify the brightness of the pictures stored in the disk

history.

Active Buttons

● First: Shows data of the first recognition in the history.

● Previous: Shows data of the recognition previous to the one currently shown.

● Next: Shows data of the recognition following the one currently shown.

● Last: Shows data of the last recognition in the history.

7.3.4. Live Camera

Allows to view the images the camera is currently capturing. Its main function is to properly

adjust the lens.



This tab will only show data if the active item in the button bar is a lane; the window will


Live Camera feature must only be used for lens adjusting purposes, as it negatively

affects the recognition system in a way that it could prevent the unit from recognizing

license plates while it is enabled.


● Image: image currently being received from the camera. Located in the upper part of

the window.

● The Numerical focus allows to adjust the camera lens without having to trust the

human eye for small variations in image clarity.

● Graphical focus: Similar to the previous one, but with a visual representation of the

information.

Active Buttons

● Exposure time: Allows to set the exposure time (in μs) the images will be captured in.

● Start: Start receiving live images.

● Stop: Stop receiving live images.

● Clear/Restart: Refresh numerical and graphical focus data.

● Previous: decrease by 20 % of the exposure time.

● Next: increase by 20 % of the exposure time.



7.3.4.1. Numerical/graphical focus

The Numerical/graphical focus allows to adjust the camera lens without having to trust the

human eye for small variations in image clarity.

To make a good use of the numerical focus, follow the steps below:

1. Start Live Camera.

2. Place the red rectangle that appears printed on the image on the zone you wish to get

the maximum image clarity. In order to do so, mark with a mouse click a corner of the

rectangle you want to draw; a little red cross will appear on the marked point. Mark

with another mouse click the opposite corner, and the new rectangle will appear red

bounded.

3. Click the “Clear/Restart” button to initialize focus data.

4. Make a very slow “scan” with the focus ring of the camera lens, from the initial position

to the end. Then, “Max” field value will show the maximum focus value reached.

5. Adjust the focus ring of the lens until the value of the field “Focus” is equal to the value

of the filed “Max” .

The graphical focus provides the same data as the numerical focus but with an easier

representation. X axis represents the time and Y axis represents the focus value. The higher

the value appears at any given time, the better is the image focused. The vertical line sets the

current point in the graphic and the horizontal line the current focus value. When the two lines

appear red, the focus value reached maximum; when the current value is below maximum, the

lines appear gray.

7.3.5. Statistics

It allows to make an objective evaluation of the adjustments of the camera. Therefore, the

system must be left running for at least 24 hours (to be able to evaluate all light conditions)

and until hundreds of vehicles have been recorded. The application should be running and

correctly configured to be able to store the necessary number of vehicles in history, and also in

order to have a clean history.





To see the statistics, click the "Start” button and the application will calculate the data

(depending on the number of vehicles, results may take a few seconds to appear). The values

shown have the following meaning:

● ROI average location: Map of license appearing frequencies in the images. The zones

where more licenses have appeared are colored brighter. Useful to know if the camera

is centered in the lane.

● Total Captures: Number of vehicles processed.

● With license: Total number and percentage of captures for which the license plate

number was found .

● Empty: Total number and percentage of captures for which a license plate number was

not found.

● Grammar ok: Total number and percentage related to captures with license where the

plate number matches any of the country grammars configured. This parameter is very

useful for lanes configured in trigger mode: For instance, a value between 90% and

95% will indicate that the lane is properly adjusted.

● Grammar failed: Total number and percentage related to captures with license where

its plate number does not match any of the country grammars configured.

● Unknown characters: Number of unknown characters for each thousand licenses.



● Average quality: Average of the average quality parameter of all the captures with

license.

● Average minimum quality: Average of the average minimum quality parameter of all

the captures with license.

● From: Date and time of the first capture.

● To: Date and time of the last capture.

Active Buttons

● Start: Starts to calculate the statistics.

7.3.6. Configuration

Allows to access the configuration system of the unit by means of a embedded web server.



Note that you can access the system configuration through this tab or through a web browser,

getting the same result. See paragraph 9.1 Main system configuration to find out more

information about the unit configuration system.

Active Buttons

● Start: Reconnects to the configuration system of the unit. Useful when the unit has

been rebooted.

● Clear/ Restart: refreshes current configuration page.

7.3.7. FTP

Allows to access the FTP server of the unit by means of an embedded FTP client.



Note: if you use protocol encryption option, it will not be possible to access to the stored

recognitions through FTP; refer to SmartLPR® Programming Manual for more information.



The window is divided into three parts:

● Local files: The left part of the window shows drive, folder and file list in the local

drives.

● Remote files: The right part of the window shows folder and file list of the selected unit.

● Progress bar: Shows the percentage of the transferred files (when there is a transfer in

progress).

Operation

The operation is symmetrical on both sides. A double-click on a folder or drive makes it active

and shows its content.

To select more than one file or folder to transfer, use the [control] key to add one by one files

or folders, or use [shift] to add all files or folders since the last selected.

Once the file list is selected, drag-and-drop it to the other window and the transfer will start in

the indicated way.

Active Buttons

● Clear/Restart: Reconnects to the FTP server and refresh both file lists content. Useful



for instance when the unit has been rebooted, as the FTP server content is lost every

time the unit reboots.


SmartLPR® Speed User Manual Hardware

Hardware

This section describes the steps required for the installation of a SmartLPR® Speed unit, from

the unpacking procedure to the full operation of the system, which includes the physical

installation of the unit and its correct setup (including its focus).

However, this section does not describe the processes that do not deal with the unit itself,

such as the installation and setup of the client software installed in the unit (see the

“Software” section).



8. Equipment descriptionThe unit is built in a high strength housing. Inside the housing there are the light, capturing

and image processing systems. The equipment is composed of the following parts:

Externally

1. Removable housing.

2. Housing screws.

3. Sun visor.

4. Viewing window.

Internally

1. Optical lens.

2. Light source (its aspect may vary)

3. Power strip.

4. Cable input holes.

5. OCR Unit.

8.1. Pinouts

8.1.1. Ethernet

J1 connector

Pin MeaningTX+ TX+ (pin 1 RJ-45)

TX- TX- (pin 2 RJ-45)

RX+ RX+ (pin 3 RJ-45)

RX- RX- (pin 6 RJ-45)


1

2

34

3

51

24


8.1.2. Serial

J2 Connector

Pin MeaningRS232_RX RX of RS-232

RS232_TX TX of RS-232

GND Ground of RS-232

8.1.3. I/O

J3 et J4 Connectors

Pin MeaningIN1 (J3) Input 1

IN2 (J3) Input 2

GND (J3) Inputs ground

+12VDC (J3) Power for the outputs

+12VDC (J3) Power for the outputs

OUT1 (J4) Output 1

OUT2 (J4) Output 2

OUT3 (J4) Output 3

OUT4 (J4) Output 4

OUT5 (J4) Output 5

OUT6 (J4) Output 6

OUT7 (J4) Output 7

OUT8 (J4) Output 8

8.2. Serial communication properties.

Serial communications have the following characteristics:

● 1 Stop bit.

● No parity.

● No flow control.

8.3. Input/Output system characteristics

8.3.1. Inputs

Inputs are “dry-contact” type, and have two possible states: open circuit and ground short



circuit. The following drawing shows an example of how to connect the inputs:

Inputs that are not going to be used can be left unplugged.

8.3.2. Outputs

Outputs provide an open circuit or a ground short circuit.

Each of the outputs can provide power up to 200mA. Note that the sum of the current intensity

of these 8 outputs cannot be higher than 200 mA. To control power loads through these

outputs an external relay is needed, connected as shown:

To feed relay coils, never use any other external power than the provided in the output

connector strip, otherwise the circuit could result damaged.

8.4. Temperature control

There are models with a control module that permits to preserve the temperature of the unit in


NO

NC

Common

RelayInputs

Ground

Input n

SignalExternal

Outputs

+12VDC

+12VDC

Output n

NC

NO

Common

Relay


case of extreme cold. A heater is activated when the inside temperature falls and it stops when

it reaches a comfortable working temperature.



9. FirmwareWe call “firmware” the software that runs internally in the unit.

Each unit has a default setup with IP address 192.168.1.2xy, where “xy” represents the last

two figures of the serial number of the unit. For example, a unit with serial number

04420120711002 will have IP address 192.168.1.202.

The serial number can be found on a label inside the unit.

To gain access to the configuration system, just choose the corresponding lane in

the diagnostic tool and then select the “Configuration” tab (also can be accessed via a web

browser at the URL http://<ip of the unit> ).

Once connected, a window asking for password will appear. The default password is “quercus2”

; it can be changed later, if necessary, through the configuration options.

The same window will show a list of languages from which the user can select the language of

the system.

When clicking the “Validation”, you will gain access to the configuration system window, which

is divided into 2 parts: on the left, the menu with the configuration options; on the right, the

specific screen of the option chosen.

The options are divided into the following sections:

● Configuration: Allows to make configuration changes editing the variables that rule the

behavior of the unit . Also allows to import or export all configuration settings and apply

changes or discard them.

● Main system Configuration: You can adjust the setup using variables, recognition

system parameters (exposure times, inputs and outputs, etc.) or general system

parameters (IP address, time zone, etc.).

● Import configuration from FTP: Allows to import the settings from an externally

generated file.


10W12V ---

SmartLPR® SpeedRef.: 07000063S/N: 04420130701001


● Export configuration from FTP: Allows to export the settings from an externally

generated file.

● Change management password: Allows to set a new password to login to

management system.

● Apply changes and reboot: Applies changes made in “Main system configuration”

section (or after importing the configuration) and reboots the unit.

● Discard changes: discards changes made in “Main system configuration” section.

● Information: Allows to check information about the unit such as recognition logs,

firmware version, etc.

● System information: shows system information (serial number, firmware

version,etc.).

● Plate recognizer log: Shows logs generated by plate recognizer system while its

running.

● Serial adapter log: Shows logs generated by serial communication system. The

file will only exist if serial networking is enabled in the unit.

● File system log: shows the information generated after the file system check,

where recognitions are stored. The check is performed when the unit boots.

● Configuration Log: Shows logs generated by the configuration system of the

unit.

● View recent recognitions: Allows to view the images and recognition data of the

last 3 vehicles.

● View last images captured: shows the images captured of the last 3 vehicles

processed. Depending on the system configuration, it shows all the images

captured, not only the ones sent as recognition data.

● Export System Status to FTP: Used to generate a system status report of the

unit for the Quercus Technologies technical service, in order to detect possible

errors in the unit.

● Contact information: Shows necessary information to contact Quercus

Technologies support team.

● Date and time configuration: Allows to set the date and time of the unit.

● Adjust date and time: Allows to set current date and time.

● Synchronize time with time server: Synchronizes the time of the unit with a

previously configured time server.

● Firmware: Allows to update the unit firmware or to restore its original one. The main

menu of the unit firmware gives access to its different functions:

● Update firmware: Allows to update the unit firmware

● Restore original firmware: Allows to restore the firmware to factory version.



● Format data disk: Allows to format the data disk, where recognitions are stored.

9.1. Main system configuration

The main system configuration is done by editing specific variables that set its behavior.

If you wish to restore the default value of the variable, leave the box empty. Changes will not

be applied until the option “Apply changes and reboot” is selected.

To obtain a description of the meaning of a variable, leave the mouse pointer on the variable

name for a few seconds and a small pop-up window with the information will appear.

When you finish editing the variables, do not forget to “Save Changes”.

9.1.1. Variables

9.1.1.1. Communications

● CentralSystemHost: IP address of the central system.

● CentralSystemHost2: IP address of the second central system.



● CentralSystemPort: port where the central system will receive messages from units.

● CentralSystemPort2: port where the second central system will receive messages from

units.

● CompressionQuality: compression used to send images in JPEG format (1 to 100); the

higher the number, the higher the quality, although with a bigger size.

● ConfigurationServerPort: port where the unit configuration server will wait for

configuration protocol messages.

● DateProtocol: protocol used in date and time synchronization. Possible values are

“TIME” and “NTP”. If set to “TIME”, the protocol used will be the one specified in “ARPA

Internet RFC 868” document; if set to “NTP”, the protocol used will be Network Time

Protocol.

● DateServer: date and time server that will synchronize the unit once a day.

● Gateway: gateway to Internet access. Used when the central system is out of the local

network of the unit, otherwise it can be left pointing to “127.0.0.1”.

● HostName: name of the unit. Used in case you wish to give each unit a different name.

● IP: IP address of the unit.

● ListeningPort: port where the unit expects to receive messages.

● MaxMsgVersion: the messages that the unit will generate will not be of a version higher

than the one indicated. It allows the client applications that implement an older version

of the protocol to communicate with new units, without having to wait for the protocol

negotiation mechanism to be done.

● NameServer1(2,3,4): DNS servers. Used when the addresses are specified as names

instead of Ips (for example, “example1.quercus.biz”). If you do not wish to use names

in the unit setup, leave them as “127.0.0.1”.

● Netmask: network mask of the unit.

● ObserversDefaultPort: default port where the message will be sent to the observers. For

more information, please refer to the SmartLPR® Programming Manual.

● ObserversList: list of IP addresses and Ports of the observers. The list must be comma-

separated "," where each item has the following format <ip_address>[:port] . If port is

omitted, the port used will be the one set in ObserversDefaultPort. Example:

“192.168.1.3:4444, 192.168.1.4”. For more information, please refer to the SmartLPR®

Programming Manual.

● Password: protocol encryption password. For more information, please refer to the

SmartLPR® Programming Manual.

● Protocol: communications protocol used. Possible values: UDP and Serial.

● Retries: number of retries for sending messages in case of failed deliveries.

● Timeout: time in milliseconds during which the system will wait for a response to a



message before it is considered as not answered.

9.1.1.2. Engine

They are internal parameters used by the license plate recognition system. Modifying them, a

better performance rate can be achieved in very special circumstances. Never modify any of

these parameters except at Quercus Technologies support department request. The only

parameter to take into account is:

● EnableSquarePlates: when the value is 0, recognition for “Square” plates ( plates with 2

lines of characters) is disabled. When the value is 1, “Square” plates recognition is

enabled,provided that the grammar of the enabled regions allows it. This parameter

permits to recognize “square” rear plates of certain vehicles such as 4x4 models. Do not

enable it unless it is absolutely necessary, as system performance might decrease.

9.1.1.3. Global

● DiskHistoricSize: storage space (in Mb) reserved to save recognitions in the unit. If its

value is -1, the behavior is compatible with version 3.3.x or older; and value 0 indicates

that the history is not used (although it always saves the last recognition).

● LogFilter: text string which will be established as a filter of messages that you want to

include in the log file. The filter allows you to use “*” as the pattern to indicate any text

string. For example, if the filter is established as *Photo* only the messages with the

Photo string will be displayed. The default value of the filter is “*”, in other words, all

messages are displayed.





● SystemId: Identifier of the unit. Each unit in a SmartLPR® Speed system must have a

unique identifier.

● TimeZone: time zone of the machine. Used to ensure the date and time synchronize

synchronization will take time zone differences into account. Possible values are listed

in appendix B.

● Watchdog: activates a hardware part that reboots the unit in case of malfunctioning.

The possible values are: 1 active, 0 inactive.

● WorkingMode: the operation mode of the unit. Possible values:

● Software: The unit does not detect vehicle movements and it is the central

system which determines when a detection should take place.



● Hardware: The unit detects vehicle movements and it determines when the

detection should take place (every time a new vehicle arrives).

● Continuous: The unit is constantly capturing and processing images. When a

license plate is detected it is immediately sent to the central system.

● WorkingDirection: operation direction. Possible values: Front, the unit is set to capture

front plates. Rear, the unit is set to capture rear plates. See the variable called

“Engine/EnableSquarePlates” for more information about rear captures.

9.1.1.4. I/O

● SensorChannel: bit of the I/O card used as sensor. Possible values: 0 to 1 or –1 if the

sensor is not going to be used.

● SensorFilterTime: time (in ms) of the digital inputs filter against signal bouncing.

● UsedInputs: Comma separated list of inputs which must notify the change of status to

the central system. The possible values are 0 and 1.

9.1.1.5. OSD

Parameters that allow to choose and configure the information which should be printed as text

onto the picture itself.

● Active: sets the OSD system active or not: 1 enables it, 0 disables it.

● Position: image position where the text should be displayed. The possible values are:

● LeftTop: text is displayed in the upper

left part, left aligned.

● RightTop: text is displayed in the

upper right part, right aligned.

● LeftBottom: text is displayed in the

lower left part, left aligned.

● RightBottom: text is displayed in the

lower right part, right aligned.

Each data item that can be superimposed on the image is defined by two variables:

● LabelXXX: sets the text that must be displayed before the value of variable XXX. For

example, if LabelCarId is set to “Vehicle identifier” and vehicle 3 arrives, the text

displayed will be “Vehicle Identifier 3”. If LabelXXX is empty, no text will be displayed

before the value.

● OrderXXX: sets the order which the item XXX will be displayed, if the value is -1, the

item will not be displayed. For example, if OrderCarId is 3, OrderLicense is 2, and


Image

LeftTop

LeftBottom RightBottom

RightTop


OrderMinQuality is 1, MinQuality will be displayed first, then License, and last CarId.

The data items available are the following:

● AvgQuality: average quality of the recognized license plate (from 0 to 1).

● CarId: vehicle identifier.

● Chars: recognized license without blanks, hyphens or any additional decoration.

● Country: character or characters identifying the country of the recognized license.

● GrammarOk: shows if the license matches any known grammar: 1 matches, 0 doesn't

match.

● LaneId: identifier of the lane where the image comes from.

● License: recognized license with the corresponding additional decoration (blanks,

hyphens, etc.). If the license doesn't match with any known grammar, this item will not

contain any decoration.

● MinQuality: quality of the character worst recognized (from 0 to 1).

● NumberOfUnknownChars: number of unknown chars (displayed as question mark in the

license).

● Qualities: individual character qualities (from 0 to 1, comma separated).

● Roi: rectangle inside the image where the license was found, formatted as

“(<left>,<up>)-(<right>,<down>)”. If the license doesn't match with any grammar, or

it is empty, the value of this field will be the image dimensions.

● Timestamp: date and time of the recognition formatted as “year-month-day

hour:minute:second”.

● TriggerId: identifier of the trigger event.

9.1.1.6. PPU

● Host: IP address of the SmartLPR® Power Process Unit that the unit will communicate

with.

● Port: port where the module will receive the messages of the units.

● Reserved1: reserved. Do not modify unless Quercus Technologies support department

explicitly indicates you to do so.

See 11 Annex A: SmartLPR® Power Process Unit for more information.

9.1.1.7. Recognizer

● DelayTime: can have three different uses:

● Sensor delay: Negative DelayTime. Sets the time in milliseconds for the the



image to be taken from the moment when a vehicle actives the sensor (or, in

the case of units configured in software mode, when a "trigger" message is

received). It is mainly used when the sensor introduces a known constant delay

in the detection of a vehicle. For example, if the detection sensor has a relay

which takes 50 ms to activate, this variable should be set to “DelayTime= -50”.

● Sensor between the visual field and the camera: Negative DelayTime. It is used

in situations when, due to physical reasons,

the sensor had to be installed in a position

more advanced than the optimum one. The

attached figure shows the time that a

vehicle takes to run the space represented

by the red arrows. This solution is not advisable because the time a

vehicle will take to do it depends on its speed.

● Sensor in the visual field of the camera: Positive DelayTime. Sets the time in

milliseconds while the image capture will

intentionally be delayed from the moment when a

vehicle actives the sensor (or, in the case of units

configured in software mode, when a "trigger"

message is received). It is used in situations when,

due to physical reasons, the sensor had to be installed in a position behind the optimum

one.

The attached figure shows the time that a vehicle takes to run the space represented by

the red arrows. This solution is inadvisable also because the time a vehicle will

take to do it depends on its speed.

● EmptyLicenseOnGrammarFailed: the license is returned if grammar is not correct.

Possible values: 0 (license plate without changes), 1 (license plate with question marks)

and 2 (empty license plate).

● ExposureTimes: list of exposure times, in microseconds, used to capture images. There

are 7 exposure times defined.

● ImagesToSave: indicates that the unit will temporarily store the captured images. The

possible values are: “None”, where no images are stored. “Best”, stores the image with

the best quality for each vehicle. “All”, stores all images of each vehicle. If you select

any value different to “None”, a folder called “LastImages” will appear in the FTP server

of the unit, where the images will be stored in BMP format. The images of the last three

vehicles will be stored. In continuous mode "All" is the same as "Best".


Visual field

Detector

Unit

Visual field

Detector

Unit


● MaxNumberOfUnknownChars: maximum number of unknown characters (or with a

quality too low) that will be accepted on a license plate in order to consider it valid

(only used in Continuous mode).

● MinAvgQuality: the minimum average quality a license plate should have to be

considered valid (only used in Continuous mode). Possible values: from 80 to 100.

● Regions/Spain, Regions/Denmark, etc.: countries for which the license plate recognition

is needed. To enable the recognition of a country, a value higher then zero must be set.

This value will also set the priority order (ascending order) that this country will have in

the list of enabled countries. When the recognition engine has doubts about a license, it

will try to match it with the grammars of higher priority countries.

It must be taken into account that the more enabled countries you have, less

recognition reliability and longer response time you will get.

To disable a country, the value to be set is “-1” .

● Reserved1,2,3,4: reserved parameters. Do not modify them unless Quercus

Technologies support department explicitly indicates you to do so.

● SendRepeatedLicenses: indicates, in case of finding a repeated license, if it must be

sent (1) or not (0). (only used in Continuous mode).

● SendRepeatedLicensesTimeout: minimum time in milliseconds that will elapse between

sending two identical licenses when the variable 'SendRepeatedLicenses' is equal to 1.

(only used in Continuous mode).

Example:

If the variable 'SendRepeatedLicensesTimeout'=10000 and the license is recognized,

this same license will never be recognized and sent again after the 10 seconds pass.

9.1.1.8. Serial

● Baudrate: serial port transmission speed (only needs to be configured if you have

selected the serial communications option). Possible values: 57600, 19200, 9600,

4800, 2400, 1200, 600 and 300.

9.2. Import configuration with FTP

Used to upload an externally predefined configuration(by Quercus Technologies technical

service) to the unit. To achieve this, you will have to first upload (using FTP) the file

“Config.dat” that Quercus Technologies support department has provided. Then, you are

ready to use this option. Take into account that any changes made to the unit configuration

will be lost. Changes will not be applied until the option “Apply changes and reboot” is



selected.

9.3. Export configuration with FTP

Its main purpose is to provide the current configuration to Quercus Technologies technical

service, so that they can help you to set up the unit or to make a configuration settings

backup. If this option is selected, a file named “Config.dat” will be generated in the FTP server.

It will contain the current settings of the unit. You will only need to copy the file from the FTP

server or using the link provided by the configuration system.

9.4. Change configuration system password

Allows to enter a new password to login to the configuration system. You must enter the

current password, and the new one twice (to avoid mistakes while typing that could end up in

entering a wrong password). The new password will be valid from the moment it is entered.

9.5. Apply changes and reboot

This option saves all changes made in “Main system configuration”, and reboots the unit with

its new configuration. It must also be used after importing configuration with FTP.

9.6. Discard changes

This option discards all changes made in “Main system configuration”.

9.7. System information

This option shows the serial number, the production date of the unit, product version and other

data that Quercus Technologies support department might need in order to help if you have

doubts about the configuration, updates, etc.

9.8. Recognizer log

Shows the log generated by the plate recognition system while running. Each line in the log is

divided into parts separated by the symbol “|”. The first part corresponds to date and time

(formatted as “Year-Month-Day Hour:Minute:Second”). The second part indicates the severity

level of the messages, that can be:

● “Message”: informative messages.

● "Warning": Alerts that might not correspond to any problem but they must be taken



into account because they could be caused by a configuration error.

● "Error": Errors, which could mean configuration or hardware errors.

The fourth part is the message body.

In case of unit malfunctioning, check this log as it will probably give you information

on the error.

The whole log file can be downloaded using the link from the upper part of the window.

9.9. Serial adapter log

Shows logs generated by serial communication system. The file will only exist if serial

networking is enabled in the unit. It has the same format as the recognizer log.

9.10. File system log

Shows the report generated after checking the system disk, where recognitions are stored. The

report is generated during boot process and informs about disk status. If errors are

encountered, the report describes steps to try to solve them.

9.11. Configuration Log

Shows logs generated by the configuration system of the unit.

9.12. View recent recognitions

Shows the images of the last 10 vehicles recognized. Clicking on one image, the image at its

actual size will be shown together with the recognition data stored in the XML file (See

SmartLPR® programming manual for more information).

9.13. View last captured images

Shows an image mosaic with the images of the last 3 vehicles processed.

To get these images generated, the variable “Recognizer->ImagesToSave” must be set to

“Best” or “All” (to store only the best image or one for each exposure time used, respectively)

To view an image at actual size, just click on it.

Viewing these images can be very useful to determine if the camera is properly adjusted, as a

sequence of images of each vehicle can be seen instead of only one image, as it happens



during the normal operation of the unit.

9.14. Export system status to FTP

It is used to generate a system status report of the unit for the Quercus Technologies technical

service, in order to detect possible errors in the unit. If this option is selected a file called

“SystemStatus.dat” that contains the report will be generated. You will only need to copy the

file from the FTP server or using the link provided by the configuration system.

9.15. Contact info

Provides the necessary information to contact with the Quercus Technologies technical service

(email, phone, etc.)

9.16. Adjust the date and time

Allows to manually set the internal date and time of the unit. The new date and time will be

effective from the moment is entered (no need to reboot the unit).

9.17. Synchronize time with server

Used to synchronize the time with the time server previously configured at the variable

“Communications -> DateServer”. Time is synchronized once a day, but it can be forced to do

it at any time using this option.

9.18. Firmware update

The firmware update is used to add newer versions of the Quercus Technologies recognition

system, either to repair detected bugs or to add new features.

9.18.1. Steps required before updating

Before installing updates, you must follow a series of steps so that the update would become

available. Follow these steps:

1. Get the firmware update file from Quercus Technologies (files with extension .upd).

WARNING: NEVER install an update that does not come directly from the technical

service of Quercus Technologies since you can seriously damage the firmware of the

unit. If fraudulent manipulation of the firmware installed is detected, the product

guarantee will be cancelled immediately.



2. Use the diagnostic tool to transfer the file to the unit via FTP or open an FTP connection

to the unit (address ftp://<unit_IP_address>). The identification and password are the

same as those used in the setup process (default user “admin”, password “quercus2”).

You can access it directly from Microsoft Internet Explorer using the address

ftp://admin@<unit_IP_address> and entering the password when asked.

3. Upload the update file to the FTP server.

4. Close the FTP connection.

Please note that the data uploaded in the FTP server will not be permanently stored (it will be

deleted when the unit is rebooted) so upload the file when you actually plan for the update to

take place.

9.18.2. Update

When the file has been uploaded to the FTP server you can update the system. To do that,

select “Update Firmware” option on the menu.

If there are update files available in the server, the system will ask you which file you wish to

use; select the right file (normally there will be only one available). If you select this option, a

window describing the actions to be taken will appear: If you agree, click the “Update” button.

Once the update has finished, a window with the result of the update will appear, and the unit

will reboot, now using the new firmware.

Updating the unit firmware is a delicate operation. If you are not sure about the steps that

must be followed, please contact the support department of Quercus Technologies; our staff

will guide you through to safely update the system. In addition, take the following aspects into

account:

● The firmware update does not modify the current setup of the unit. However,

the new firmware might require the configuration of additional parameters

(initially found at their default value). See the documents attached to the

update to understand the steps to follow after the process.

● Do not update the system if there is a high probability of power outages. Although

every effort has been made to make the update process as reliable as possible, there is

always the possibility, as remote as it is, to cause irreversible damage to the unit

firmware.

● This process involves stopping the recognition system during the operation. Do not

update the system if you need the unit to remain operational.

● Make sure the update has been carried out successfully by checking the version

displayed by the unit before and after the process, using the diagnostic tool, for



instance.

9.19. Restore original firmware

This option allows you to restore the original factory firmware of the unit (and configuration).

If you select this option, a window describing the actions to be taken appears: If you agree,

click the “Restore” button. Once the restoration is finished, a window with the result will be

shown, and the unit will reboot using the original firmware.

Restoring the firmware of the unit is also a delicate operation. Take into account the following:

● Restoring the firmware generates the total loss of the current setup and restores the

original factory settings. The unit will have the same IP address it originally had.

● Do not restore the system if there is a high probability of power outages. Although

every effort has been made to make the update process as reliable as possible, there is

always the possibility, as remote as it is, of causing irreversible damage in the unit

firmware.

● This process involves stopping the recognition system during the operation. Do not

restore the system if you need the unit to be operating.

● Make sure the restoration was successful by checking the version displayed by the unit

before and after the process (any development library of SmartLPR® Speed will let you

check the unit version).

If you encounter any problems during the restoration process, see 9.22 Firmware emergency

restore which explains an alternative method to restore the original firmware.

9.20. Format data disk

This option allows you to format the data disk of the unit, where recognitions are stored. You

can use this option to remove all the recognitions stored in the unit or whenever “Filesystem

Log” indicates it must be formatted. If you select this option, a window describing the actions

to be taken appears: If you agree, click the “Format” button. Once the process is finished, a

report will be shown; you must read the full report and check if any error occurred during the

format process. If the process successfully finished, you must reboot the unit to start working

with the formatted data disk. Otherwise contact Quercus Technologies support department.

Formatting the data disk is also a delicate operation. Take into account the following:

● The formatting involves the total loss of stored recognitions, as well as any

other file uploaded through FTP.

● Do not format the disk if there is a high probability of power outages. Although every



effort has been made to make the update process as reliable as possible, there is

always the remote possibility to cause irreversible damage to the firmware.

● This process involves stopping the system and FTP/SFTP service. Do not format the

system if you need the unit to be operating.

● Check if the format process was successful. Read carefully the final report.

● Note that the format process may take several minutes while the unit must not be

stopped or rebooted.

9.21. Restoring configuration parameters

The configuration restore system allows to restore the original configuration parameters of the

unit regardless of the configuration system (using a button).

Warning: The configuration parameters restore system must only be used when is not

possible to restore the firmware using the usual method (configuration system). It could be

used, for example, to recover the factory IP address of a unit when the current one is

unknown.

To restore the factory configuration values using this method follow these steps:

1. Press and hold the button.

2. You will hear a sequence of beeps will followed by a longer one.

3. The unit will reboot. If you only wanted to reboot the unit, you can release the button.

4. If you keep the button pressed, 50 seconds later a sequence of beeps will sound

becoming shorter in duration, followed by a longer one.

5. Release the button before the next sequence of beep sounds to be over.

Warning: Warning: if the button is not released before the next series of beeps to be

over, firmware emergency restore will start (see 9.22 Firmware emergency restore ).

6. The unit will restore the firmware (and configuration) and will reboot with the new

settings.

7. Once you hear the usual start beep, the unit is already working with factory default

settings.

8. Some of the factory parameters will not be effective until you select "Apply changes

and reboot" (see 9.5 Apply changes and reboot ).

The beep sounds of "Restore configuration parameters" and those of "Reset" differ because the

last ones are constant whereas the fist ones increase their frequency.

9.22. Firmware emergency restore

The emergency restore system allows to restore the original firmware of the unit



independently of configuration system (using a button).

Warning: The emergency restore system must only be used when is not possible to restore

the firmware using the usual method (configuration system). It can be used, for example,

if there has been a power cut while the unit’s firmware was being updated, leaving it damaged.

To restore the firmware using this method follow these steps:

1. Press and hold the button.

2. You will hear a sequence of beeps followed by a longer one.

3. The unit will reboot. If you only wanted to reboot the unit, you can release the button.

4. If you keep the button pressed, 50 seconds later a sequence of beeps will sound

becoming shorter in duration, followed by a longer one.

5. You will hear again the same sequence of beeps becoming shorter in duration, followed

by a longer one.

6. Release the button.

7. The unit will restore the firmware (and configuration) and will reboot with the new

settings.

8. Once you hear the usual start beep, the unit is already working with its factory default

settings.

The beep sounds of "Emergency restore" and those of "Reset" are different because the last

ones are constant while the fist ones increase their frequency.



10. Step by step installationCase housing units are designed to be installed, with the corresponding optional components,

in the following configurations:

● Wall. Using wall support.

● Ceiling. Using ceiling support.

● Vertical Cylindrical Mast. Using the tube adapter + the wall support.

Each configuration installation is detailed next.

10.1. Wall installation

Fix the wall support to the wall

Face the support to the wall, leaving cables inside the

support and mark the holes to drill.

Remove the support and drill the holes.

Put the anchors into the holes.

Place the support in its position, and pass the cables through

the opening for that purpose, until they come out from the

other end.

Fix the support firmly using the screws.

Fix the support to the unit.

Place the unit onto the head tilt, and fix it through the 2 holes

using the M5 screws supplied. Do not ever use longer screws than

the ones supplied, they could damage the unit. Fix it with the allen

screw of the head tilt oriented to the right (view from behind).



10.2. Ceiling installation

Fix the support to the ceiling

Face the support to the ceiling, leaving cable exit inside the support and mark

the holes to drill.

Remove the support and drill the holes.

Put the anchors into the ceiling holes.

Place the support to its position, and pass the cables through the opening for

that purpose, until they come out from the other end.


Fix the flat adapter to the support

Place it at the right side of the unit (view from behind).


Place the unit onto the support platform, and fix it through the

slot of it using the M5 screws supplied. Don't ever use longer

screws than the ones supplied, they could damage the unit.



10.3. Vertical mast installation

Fix the wall support to the tube adapter


Place the tube adapter

Fix the tube adapter firmly using the provided studs and its

corresponding nuts.


Place the unit on the head tilt, and fix it through the 2 holes using

the M5 screws supplied. Don't ever use longer screws than the

ones supplied, they could damage the unit.



10.4. Common Procedures

This section describes the Common Procedures to all installation options for case housing

models (ceiling, wall, vertical mast, floor).

Open the unit

Remove the screws from the unit locks.

Lift up the upper part of the housing.

Pass the cables inside the unit

Use the three cable glands on the back of the unit to

move the cables (power supply, network/serial and I/O)

inside the unit.

Connect the network cable

Use the detachable strip J1. Connection layout is described

in 8.1 Pinouts section.



Connect the RS-232 serial cable

Necessary only if the communication protocol going to be

used is RS-232. Use the detachable strip J2. Connection

layout is described in 8.1 Pinouts section.

Connect digital Inputs and Outputs

Only necessary if digital Inputs or Outputs are going to

be used. Use the detachable strips J3 and J4. Connection

layout is described in 8.1 Pinouts section.

For more details about the layout and operation of the I/O system, see section 8.3

Input/Output system characteristics

Connect the power supply cable

In the case of the DC powered model connect the power supply

cable to the power strip, at the back part of the unit.

In the case of the AC powered model, connect the Line wire to

the terminal (L),

Neutral wire to (N)

and Ground to (PE). Keep the transparent cap to

its original position at the power supply

terminals. Avoid direct contact between cable

mesh and any metallic part.

10.5. Optical adjustment

For a more comfortable adjustment, use a laptop computer with the SLPRDiag diagnostic tool

installed and a crossed network cable.


L N PE

PE + -


All units are configured to reach the central system at 192.168.1.199 address, so you should

configure this address on the laptop you are going to use. See chapter 9 Firmware to find out

how to get the default IP address of each unit.

To adjust the camera the following steps must be taken:

1. Find in the table from 2.1 Design and execution of civil works chapter, the line

corresponding to the lane location: Height of installation and maximum width on image

bottom.

2. Set the unit at the inclination obtained from the table (β). An inclinometer could make it

easier. Obviously, the angle must be referenced to the ground. Therefore, if the road is

on a slope, you should add it to or subtract it from that inclination to maintain the

indicated angle with the road.

3. Set the lens zoom (central ring) to the value obtained in the table (chapter 2.1 Design

and execution of civil works) for the Zoom field.

4. If it is possible to stop car traffic while doing the setup of the lane, two cones should be

placed on both limits of the visual field. Every distance can be obtained from the table

(A1,L1,A2 y L2).

5. Connect the crossover cable to the unit and the laptop.

6. Start the laptop and the diagnostic tool.

7. Power up the unit.

8. Set the lens to the F 1.4 position.

9. Select, from the button bar, the remote system and the corresponding unit.

10.Click on the “Live camera” tab.

11.Select an exposure time to view the images clearly. Values between 100 and 1000 are

considered are the usual values, 100 for very bright areas (outdoors with sunlight) and

1000 for dark areas (inside parking lots, for example). Click the “Start” button to view


Se

nso

r


the images of the camera. If the exposure time has to be modified, click the “Stop”

button, modify the time and click the “Start” button again or use next/previous arrows

to increase/decrease by 20% the exposure time.

12. If the traffic cones are correctly placed, make sure that each of them appears at the

limit of the visual field of the 2 corners of the image. If not, set up the zoom/inclination

again, until both are at the limit.

13.Set up the focus so that the images are clearly displayed along the whole visual field.

You can use the diagnostic tool to obtain an exact setting.

14.Once a clear image is obtained, restore the lens to F4 position.

15.Tighten the ring nuts of the lens, to avoid future variations in focus.

10.6. Basic firmware configuration

If you are going to use the serial networking unit (and you don't want to install the network

cable), all configuration must be done with the unit door open, in this case have a look at

section 9 Firmware to know all configuration parameters. On the other hand, if UDP networking

is going to be used, you will only need to change the IP address of the unit and its identifier,

as the rest of configuration can be done from any computer connected to the LAN.

Take the following steps:

1. From the laptop, using the diagnostic tool or the web browser, access the unit

configuration system.

2. Type the password (the default one is “quercus2”) and the main menu will appear.

3. Click on “Main configuration system” option.

4. In the “Communications/CentralSystemHost” variable, enter the IP address of the

computer(the one running the client software) that will communicate with the unit .

This step is not required if you use serial networking instead.

5. In the “Communications/IP” variable, enter the IP address of the unit. If the central

system and the unit belong to different networks, you will also have to modify

“Communications/Gateway” and “Communications/Netmask” variables.

6. In the “Global/SystemId” variable, enter a single numerical value as identifier, unique

in all SmartLPR® system. For example, if you have three units, identify them as 1, 2

and 3, respectively.

7. Click on “Apply changes” button.

8. In the main menu, select “Apply changes and reboot” option. You will be asked for

confirmation and the unit will reboot. Click on the “Apply” button and the unit will

reboot with the new configuration.



10.7. Closing the unit

Once the basic configuration has been set, follow these steps:

1. Remove the crossed network cable of the laptop.

2. Place the network cable to be used.

3. Place the upper housing in place, fix the locks and its screws.


SmartLPR® Speed User Manual Annexes

Annexes

71


11. Annex A: SmartLPR® Power Process Unit

11.1. Introduction

11.1.1. What SmartLPR® Power Process Unit is

SmartLPR® Power Process Unit is an external module that provides additional features to

SmartLPR® family. With that module running and properly configured, the units acquire the

capacity of recognizing license plates with non-Latin characters.

NOTE: SmartLPR® Power Process Unit module cannot be used in SmartLPR® Speed

units configured in Continuous working mode. See 9.1.1.3 Global.

11.1.2. Compatibility

SmartLPR® Power Process Unit is compatible with the following products:

Product Version

SmartLPR Access 3.x.x

SmartLPR Speed 3.x.x

11.1.3. Capacity

Each SmartLPR® Power Process Unit can supply up to 20 units. This number may be reduced

depending on the type of installation and performance needs of the system. In case of doubt,

check with Quercus Technologies support department.

11.1.4. Integration

The SmartLPR® Power Process Unit communicates with the configured units by TCP/IP.

72


11.2. Equipment description

11.2.1. Components

SmartLPR® Power Process Unit consists of a single compact module which includes the

following items:

1. Power switch.

2. Power

3. Ethernet connection.

4. Anchors.

5. Power cable:

11.2.2. Electrical installation

Voltage Consumption

Alternate Current (AC) 220V 70W

11.2.3. Wiring

Each SmartLPR® Power Process Unit must have the following cables:

● Power cable: 2x2.5mm2 cross-section.

● Network cable: category 5 UTP cable with RJ-45 plug.

11.3. Firmware

The software running internally in the module is usually known as “firmware”.

Each module has a default setup with the IP address set as 192.168.1.19x, where “x”

represents the last figure of the serial number of the unit. For example, a unit with the serial

number 08220100718001 will have the IP address 192.168.1.191.

73

41

2

3

4


The serial number can be found on a label on the module housing.

To access to the configuration system, just set your web browser address bar to

http://<module_ip_address>. The operation is similar to SmartLPR® units, therefore this

manual will only describe configuration settings. If in doubt, check any manual of SmartLPR®

product family.

11.3.1. Settings

11.3.1.1. Communications

● ClientIP 1..20: IP address of each SmartLPR® units that will communicate with the

module. Each module allows up to 20 units. If you are not using all of them, let the

remaining fields blank.

● Gateway: gateway to Internet access. Used when one or more units are out of the local

network where the module is located, otherwise it can be left as “127.0.0.1”.

● HostName: name of the module, if you want to give a different name to each of them.

● ListeningPort: port where the unit expects to receive messages.

● IP: IP address of the module

● NameServer1(2,3,4): DNS servers. Used when the addresses are specified as names

instead of IPs (for example, “example1.quercus.biz”). If you do not wish to use names

in the setup, leave them as “127.0.0.1”.

● NetMask: Network mask of the module.

11.3.1.2. Engine

They are internal parameters used by the license plate recognition system. By modifying them,

a better performance rate can be achieved under very special circumstances. Never modify

any of these parameters except at Quercus Technologies support department request.

11.3.1.3. Global

● LogFilter: text string which will be established as a message filter for the messages you

want to be included in the log file. The filter allows you to use “*” as the pattern to

indicate any text string. For example, if the filter is established as *Unit* only the

messages with the Unit string will be displayed. The default value of the filter is “*”, in

other words, all messages are displayed.



74




11.4. Step by step installation

11.4.1. Hardware installation

Fix the module to the wall

Fix it using the side anchor holes.

Connect power and network cables

Connect the network cable and the

power cable supplied to the

corresponding sockets at the back of

the module.

11.4.2. Client software update

This step is required if the integration of the units with the client software is done using the

software library provided by Quercus Technologies and the installed version is lower than

3.2.0.

● Windows: Replace the file <install_folder>binSA.dll by the file SA.dll provided by

Quercus Technologies support department.

● Linux: Replace the file <install_folder>/bin/libSA.so by the file libSA.so provided by

Quercus Technologies support department.

11.4.3. Setting up SmartLPR® Power Process Unit

1. Power up the module using the rear switch.

2. From another computer, log into the web configuration system of the module, from

75


a web browser at the address http://<module_ip_address>. Once connected, a

window asking for a password will appear.

3. Type the password (the default one is “quercus2”) and the main menu will appear.

4. Click on “Main configuration system” option.

5. For the variable “Communications/IP” enter the desired IP address of the module. If

the module and any of the units are in different networks, the variables

“Communications/Gateway” and “Communications/Netmask” must also be

accordingly modified.

6. Enter in the fields “Communications/ClientIPx” the IP address of each SmartLPR®

unit that the module will communicate with.



confirmation to reboot; click on “Apply” to accept it and the unit will reboot with the

new configuration.

11.4.4. Setting up SmartLPR® unit

The following steps must be applied to each one of the SmartLPR® units that will

communicate with the module.

1. If the unit version is lower than 3.2.0, update its firmware using the LPR320.upd file

provided by Quercus Technologies support department. You must follow the steps

shown in the section 9.18 Firmware update of the unit manual.

2. Modify the new variables displayed in the main configuration system.

1. PPU/Host: IP address of the SmartLPR® Power Process Unit that will

communicate will the unit.

2. PPU/Port: port where the module will receive the messages of the units.

3. PPU/Reserved1: reserved. Do not modify unless Quercus Technologies support

department explicitly indicates you to do so.

4. Recognizer/UsePPU: “1” to enable the use of SmartLPR® Power Process Unit in

current unit; “0” to disable it (traditional operation).

3. Assign a value between 1500 and 2500 to the Recognizer/MaxRecognizerTime

variable. Note that, although this step is not essential, it is recommended for a

better performance.



confirmation to reboot; click on “Apply” to accept it and the unit will reboot with the

76


new configuration.

11.5. Technical specifications

Product SmartLPR® Power Process Unit

Reference 07000200

Dimensions

Height 65 mm

Width 320 mm

Depth 200 mm

Weight 4800 g

Power

Input Voltage 240V AC

Consumption 70 W

Environmental operating conditions

Temperature range 0 - 40 ºC

Humidity range 0 - 80% non-condensing

Maximum vibration 0.5 G, 5~500 Hz

Impact 15 G at 11 m/s

77

12. Annex B: Technical specifications

Technical specifications of SmartLPR® Speed y SmartLPR® Speed Plus are identical except that SmartLPR® Speed model has a limit of 5 simultaneous

countries, while SmartLPR® Speed Plus does not have this limitation. Therefore, they appear together at the tables.

Power Unrestrictedrecognition

Temperaturecontrol

Name Reference

AC DC

● SmartLPR Speed DC 07000063

● ● SmartLPR Speed Plus DC 07000065

● ● SmartLPR Speed DC CT 07000064

● ● ● SmartLPR Speed Plus DC CT 07000066

● SmartLPR Speed AC 07000068

● ● SmartLPR Speed Plus AC 07000069

For the electrical installations of the units we recommend calculating the consumption above the values indicated in the technical data sheets to prevent

peaks that might exceed these values.

12.1. DC powered models

Product SmartLPR® Speed DC

SmartLPR® Speed Plus DC

SmartLPR® Speed DC CT

SmartLPR® Speed Plus DC CT

Reference 07000063 / 07000065 07000064 / 07000066

Dimensions

Height 190 mm

Width 195 mm

Depth 350 mm

Power

Input Voltage 12V DC

Consumption 12 W 52 W

Certifications

CE: EMC Radio Disturbance EN 55022:2006+A1:2007

CE: EMC Immunity EN 55024:1998+A1:2001+A2:2003

FCC Class A digital devices / FCC rules: 47CFR (parts 2 and 15)

Connectivity

Communication ports Ethernet 100Mbps, RS-232

Inputs 2 dry contact

Outputs 8 for power

Voltage provided at outputs 12 V DC

Maximum current per output 200 mA

Image

Resolution 752x480

Focus

Classification according UNE-EN

62471:2009

Risk Group 1

Temperature

Working temperature -25ºC - 60ºC -40ºC - 60ºC

Housing

International Protection Code IP67

Color RAL 9002

12.2. AC powered models

Product SmartLPR® Speed AC

SmartLPR® Speed Plus AC

Reference 07000068 / 07000069

Dimensions

Height 190 mm

Width 195 mm

Depth 350 mm

Power

Input Voltage 85 – 264 V AC (47-63 Hz)

Consumption 15 W

Certifications

CE: EMC Radio Disturbance EN 55022:2006+A1:2007

CE: EMC Immunity EN 55024:1998+A1:2001+A2:2003

FCC Class A digital devices / FCC rules: 47CFR (parts 2 and 15)

Connectivity

Communication ports Ethernet 100Mbps, RS-232

Inputs 2 dry contact

Outputs 8 for power

Voltage provided at outputs 12 V Dc

Maximum current per output 200 mA

Image

Resolution 752x480

Focus

Classification according UNE-EN 62471:2009 Risk Group 1

Temperature

Working temperature -25ºC - 60ºC

Housing

International Protection Code IP67

Color RAL 9002


13. Annex C: CE CertificatesProducts with CE Certificate (see section 12 Annex B: Technical specifications) have Class A

category. In a domestic environment this product may cause radio interference, in which case

the user has to take adequate actions.

81


82


83


14. Annex D: FCC Certificate

These equipments (see section 12 Annex B: Technical specifications)have been tested and

found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC

Rules. These limits are designed to provide reasonable protection against harmful

interference when the equipment is operated in a commercial environment.

This equipment generates, uses, and can radiate radio frequency energy and, if not installed

and used in accordance with the instruction manual, may cause harmful interference to radio

communications. Operation of this equipment in a residential area is likely to cause

harmful interference in which case the user will be required to correct the interference at his

own expense.

84


85


86


15. Annex E: In case of malfunctioningContact with Quercus Technologies support department, who will verify if it really is a unit

malfunction or not (could be a bad adjustment, wrong setting, etc.). In case the

malfunctioning is confirmed, the procedure is the following:

1. Verify, together with Quercus Technologies support department, the unit malfunction.

2. Replace the faulty parts by the spare ones. We recommend to have a minimum of one

spare part for each component of the unit.

3. Contact with Quercus Technologies sales department to get the faulty parts replaced if

the unit is under warranty. If the warranty of the unit expired, Quercus Technologies

sales department will prepare a purchase offer with the cost of the components to

replace or repair.

87


16. Annex F: SupportIf you have any doubts about configuration or use of SmartLPR® Speed, don't hesitate to

contact our technical support department:

● USA: +1 201 227 2020

● Brazil and Latin America: +55 (11) 2614 3006 (Extension 21)

● EMEA & Asia : +34 977 300 377

Or by email at: [email protected]

You can also contact us through our web pages:

● www.quercus.biz

● www.quercus-technologies.com

● www.quercus.com.br

88

http://quercus.com.br/

http://quercus-technologies.com/

http://quercus.biz/


17. Annex G: [Global] TimeZone valuesAfrica/BamakoAfrica/BanguiAfrica/BanjulAfrica/LomeAfrica/AsmeraAfrica/BissauAfrica/AlgiersAfrica/JohannesburgAfrica/DoualaAfrica/NdjamenaAfrica/HarareAfrica/KinshasaAfrica/AccraAfrica/CairoAfrica/CeutaAfrica/DakarAfrica/LagosAfrica/TunisAfrica/LubumbashiAfrica/KigaliAfrica/MalaboAfrica/MaputoAfrica/MaseruAfrica/Porto-NovoAfrica/MonroviaAfrica/LuandaAfrica/LusakaAfrica/NiameyAfrica/FreetownAfrica/WindhoekAfrica/KampalaAfrica/GaboroneAfrica/ConakryAfrica/MogadishuAfrica/BrazzavilleAfrica/TimbuktuAfrica/Addis_AbabaAfrica/BujumburaAfrica/NouakchottAfrica/CasablancaAfrica/MbabaneAfrica/El_AaiunAfrica/LibrevilleAfrica/Dar_es_SalaamAfrica/OuagadougouAfrica/KhartoumAfrica/NairobiAfrica/Sao_TomeAfrica/TripoliAfrica/AbidjanAfrica/DjiboutiAfrica/BlantyreAmerica/Mexico_CityAmerica/AdakAmerica/AtkaAmerica/BelizeAmerica/LimaAmerica/NomeAmerica/CancunAmerica/CaymanAmerica/BogotaAmerica/DawsonAmerica/DenverAmerica/CuiabaAmerica/Antigua

America/HavanaAmerica/BelemAmerica/ArubaAmerica/BoiseAmerica/Thunder_BayAmerica/GuatemalaAmerica/GuyanaAmerica/JujuyAmerica/InuvikAmerica/ThuleAmerica/Rankin_InletAmerica/JuneauAmerica/La_PazAmerica/MaceioAmerica/ManausAmerica/MeridaAmerica/GuayaquilAmerica/MontrealAmerica/NassauAmerica/Cambridge_BayAmerica/PhoenixAmerica/PanamaAmerica/Puerto_RicoAmerica/CaracasAmerica/CayenneAmerica/JamaicaAmerica/Porto_AcreAmerica/RecifeAmerica/ReginaAmerica/Indiana/KnoxAmerica/Indiana/VevayAmerica/Indiana/MarengoAmerica/Indiana/IndianapolisAmerica/Buenos_AiresAmerica/DanmarkshavnAmerica/MazatlanAmerica/IqaluitAmerica/Boa_VistaAmerica/VirginAmerica/ChicagoAmerica/EnsenadaAmerica/CatamarcaAmerica/Costa_RicaAmerica/FortalezaAmerica/St_JohnsAmerica/St_KittsAmerica/MiquelonAmerica/St_LuciaAmerica/Port-au-PrinceAmerica/VancouverAmerica/Porto_VelhoAmerica/WinnipegAmerica/MartiniqueAmerica/CordobaAmerica/WhitehorseAmerica/New_YorkAmerica/Glace_BayAmerica/YakutatAmerica/DetroitAmerica/LouisvilleAmerica/Grand_TurkAmerica/Fort_WayneAmerica/Goose_BayAmerica/YellowknifeAmerica/Curacao

America/HermosilloAmerica/TegucigalpaAmerica/ParamariboAmerica/ScoresbysundAmerica/Swift_CurrentAmerica/Kentucky/LouisvilleAmerica/Kentucky/MonticelloAmerica/Knox_INAmerica/AnchorageAmerica/EirunepeAmerica/RosarioAmerica/BarbadosAmerica/Dawson_CreekAmerica/ManaguaAmerica/PangnirtungAmerica/AsuncionAmerica/MenomineeAmerica/St_ThomasAmerica/Sao_PauloAmerica/MendozaAmerica/GuadeloupeAmerica/MonterreyAmerica/North_Dakota/CenterAmerica/AraguainaAmerica/Port_of_SpainAmerica/ShiprockAmerica/AnguillaAmerica/DominicaAmerica/EdmontonAmerica/Rio_BrancoAmerica/TijuanaAmerica/MontevideoAmerica/SantiagoAmerica/TortolaAmerica/Los_AngelesAmerica/NipigonAmerica/Rainy_RiverAmerica/El_SalvadorAmerica/HalifaxAmerica/Santo_DomingoAmerica/St_VincentAmerica/IndianapolisAmerica/GodthabAmerica/MontserratAmerica/ChihuahuaAmerica/NoronhaAmerica/GrenadaAntarctica/CaseyAntarctica/DavisAntarctica/SyowaAntarctica/MawsonAntarctica/PalmerAntarctica/VostokAntarctica/RotheraAntarctica/DumontDUrvilleAntarctica/McMurdoAntarctica/South_PoleArctic/LongyearbyenAsia/AlmatyAsia/AnadyrAsia/AdenAsia/BakuAsia/DiliAsia/BeirutAsia/Gaza

89


Asia/HovdAsia/OmskAsia/OralAsia/AqtobeAsia/BruneiAsia/BaghdadAsia/BahrainAsia/BangkokAsia/MakassarAsia/VladivostokAsia/HarbinAsia/AmmanAsia/AqtauAsia/DaccaAsia/DhakaAsia/DubaiAsia/YekaterinburgAsia/KabulAsia/MacaoAsia/MacauAsia/CalcuttaAsia/QatarAsia/SeoulAsia/TokyoAsia/KuwaitAsia/ManilaAsia/BishkekAsia/MuscatAsia/JakartaAsia/RiyadhAsia/SaigonAsia/TaipeiAsia/TehranAsia/ThimbuAsia/ChoibalsanAsia/UrumqiAsia/IrkutskAsia/KarachiAsia/KashgarAsia/Ulan_BatorAsia/ColomboAsia/RangoonAsia/KrasnoyarskAsia/AshkhabadAsia/YakutskAsia/IstanbulAsia/TashkentAsia/SingaporeAsia/YerevanAsia/JayapuraAsia/SamarkandAsia/AshgabatAsia/Riyadh87Asia/Riyadh88Asia/Riyadh89Asia/PontianakAsia/KuchingAsia/MagadanAsia/ShanghaiAsia/PyongyangAsia/JerusalemAsia/Kuala_LumpurAsia/TbilisiAsia/Hong_KongAsia/DushanbeAsia/DamascusAsia/SakhalinAsia/Thimphu

Asia/ChungkingAsia/KamchatkaAsia/NicosiaAsia/Ujung_PandangAsia/ChongqingAsia/Tel_AvivAsia/NovosibirskAsia/VientianeAsia/QyzylordaAsia/Phnom_PenhAsia/UlaanbaatarAsia/KatmanduAtlantic/CanaryAtlantic/AzoresAtlantic/FaeroeAtlantic/BermudaAtlantic/ReykjavikAtlantic/Jan_MayenAtlantic/Cape_VerdeAtlantic/St_HelenaAtlantic/MadeiraAtlantic/StanleyAtlantic/South_GeorgiaAustralia/ACTAustralia/LHIAustralia/NSWAustralia/WestAustralia/DarwinAustralia/HobartAustralia/NorthAustralia/PerthAustralia/SouthAustralia/CanberraAustralia/MelbourneAustralia/SydneyAustralia/AdelaideAustralia/TasmaniaAustralia/Broken_HillAustralia/Lord_HoweAustralia/YancowinnaAustralia/VictoriaAustralia/LindemanAustralia/QueenslandAustralia/BrisbaneBrazil/AcreBrazil/EastBrazil/WestBrazil/DeNoronhaCanada/PacificCanada/YukonCanada/MountainCanada/CentralCanada/EasternCanada/NewfoundlandCanada/East-SaskatchewanCanada/AtlanticCanada/SaskatchewanChile/EasterIslandChile/ContinentalEtc/GMTEtc/UCTEtc/UTCEtc/GMT0Etc/ZuluEtc/GMT+10Etc/GMT+11Etc/GMT+12Etc/GMT-10

Etc/GMT-11Etc/GMT-12Etc/GMT-13Etc/GMT-14Etc/UniversalEtc/GMT+0Etc/GMT+1Etc/GMT+2Etc/GMT+3Etc/GMT+4Etc/GMT+5Etc/GMT+6Etc/GMT+7Etc/GMT+8Etc/GMT+9Etc/GMT-0Etc/GMT-1Etc/GMT-2Etc/GMT-3Etc/GMT-4Etc/GMT-5Etc/GMT-6Etc/GMT-7Etc/GMT-8Etc/GMT-9Etc/GreenwichEurope/San_MarinoEurope/KievEurope/BerlinEurope/OsloEurope/RigaEurope/RomeEurope/AthensEurope/LuxembourgEurope/DublinEurope/AndorraEurope/VilniusEurope/BelgradeEurope/BelfastEurope/ChisinauEurope/MaltaEurope/MinskEurope/ParisEurope/SofiaEurope/VaduzEurope/BrusselsEurope/LisbonEurope/MadridEurope/BratislavaEurope/LondonEurope/KaliningradEurope/MonacoEurope/MoscowEurope/PragueEurope/StockholmEurope/SamaraEurope/SkopjeEurope/TiraneEurope/ViennaEurope/WarsawEurope/BudapestEurope/SimferopolEurope/ZagrebEurope/ZurichEurope/BucharestEurope/IstanbulEurope/AmsterdamEurope/Copenhagen

90


Europe/UzhgorodEurope/TiraspolEurope/TallinnEurope/HelsinkiEurope/SarajevoEurope/ZaporozhyeEurope/NicosiaEurope/GibraltarEurope/LjubljanaEurope/VaticanIndian/MaheIndian/ChagosIndian/ComoroIndian/KerguelenIndian/MaldivesIndian/CocosIndian/ChristmasIndian/MauritiusIndian/ReunionIndian/AntananarivoIndian/MayotteMexico/BajaSurMexico/BajaNorteMexico/GeneralMideast/Riyadh87Mideast/Riyadh88Mideast/Riyadh89

Pacific/YapPacific/ApiaPacific/FijiPacific/GuamPacific/NiuePacific/TrukPacific/WakePacific/EasterPacific/Pago_PagoPacific/EfatePacific/NauruPacific/PalauPacific/SamoaPacific/KosraePacific/MajuroPacific/MidwayPacific/HonoluluPacific/GuadalcanalPacific/NoumeaPacific/PonapePacific/SaipanPacific/PitcairnPacific/TahitiPacific/TarawaPacific/ChathamPacific/JohnstonPacific/Wallis

Pacific/GalapagosPacific/KwajaleinPacific/TongatapuPacific/FakaofoPacific/AucklandPacific/GambierPacific/RarotongaPacific/FunafutiPacific/Port_MoresbyPacific/MarquesasPacific/EnderburyPacific/KiritimatiPacific/NorfolkUS/AlaskaUS/PacificUS/HawaiiUS/SamoaUS/MichiganUS/ArizonaUS/MountainUS/CentralUS/East-IndianaUS/AleutianUS/EasternUS/Indiana-Starke

91

Documents

PROGRAMMING MANUALUSER MANUAL - Quercusdownloads.quercus.biz/speed/latest/manual/SmartLPR... · Software version 3.5. x Firmware version 3.5. x PROGRAMMING MANUALUSER MANUAL