Vega - User Manual 6.47 - Eng

VEGA User Guide
Embedded System for Automatic Number Plate

Recognition
Software Programming and User Guide
Version 6.47
Il contenuto di questo documento di propriet della TATTILE srl. Non consentito riprodurre totalmente o parzialmente questo documento, n
divulgare informazioni in esso contenute, ne mettere in atto metodi, processi, o prove in esso descritti senza autorizzazione rilasciata dalla TATTILE
S.r.l., Mairano (Brescia)
The subject of this document is a TATTILE srl property. This document or any part of it must not be reproduced in any form, nor information therein
contained disclosed to third parties, nor methods, procedures or tests described, performed without the authorisation of TATTILE S.r.l. , Mairano
(Brescia), Italy..
1-128
VEGA User Guide
Table of contents
Table of contents ....................................................................................................................................... 2
1 Conventions used in this document ......................................................................................................... 4
2 Document revisions .............................................................................................................................. 5
3 Vega features....................................................................................................................................... 7
4 Vega unit configuration ......................................................................................................................... 8
4.1 Web server ..................................................................................................................................... 8
4.2 VRC server...................................................................................................................................... 8
4.3 Receiving data from Vega unit ........................................................................................................... 8
5 Using the web server .......................................................................................................................... 10
5.1 Tattile Device Discovery and manuals downloads ............................................................................... 10
5.2 Using Tattile Device Discovery ......................................................................................................... 10
5.3 Web browser access and user authentication..................................................................................... 11
5.4 Access levels ................................................................................................................................. 13
6 Main web page ................................................................................................................................... 14
7 Events and actions.............................................................................................................................. 17
7.1 Save image to FTP server ............................................................................................................... 20
7.2 Saving text messages to FTP server ................................................................................................. 23
7.3 Send alarm to Gate Master (GM alarm) ............................................................................................ 25
7.4 Pulse out ...................................................................................................................................... 27
7.5 Send messages to RS 232 and RS 485 serial ports ............................................................................. 28
7.5.1 Configuration of the RS232 and RS485 serial ports ....................................................................... 28
7.5.2 Output date format ................................................................................................................... 30
7.5.3 Format protocol PROTOCOLLED................................................................................................ 30
7.6 Sending messages to TCP-IP socket (TCP Message) ........................................................................... 31
7.6.1 STANDARD protocol .................................................................................................................. 33
7.6.2 String format ........................................................................................................................... 34
7.6.3 XML format .............................................................................................................................. 34
7.6.4 Custom protocol ....................................................................................................................... 35
7.7 Data storage on Secure Digital memory............................................................................................ 45
7.8 Saving text messages to Secure Digital ............................................................................................ 46
7.9 Shared configuration ...................................................................................................................... 47
7.9.1 JPEG header............................................................................................................................. 47
7.9.2 Default DB fields configuration ................................................................................................... 47
7.10 Conditional execution ..................................................................................................................... 47
8 Digital signature on JPEG images .......................................................................................................... 48
8.1 Standard FIPS-186-2 ..................................................................................................................... 48
8.2 Digital signature on Tattile JPEG images ........................................................................................... 49
8.3 Digital signature verification ............................................................................................................ 51
9 Image encryption ............................................................................................................................... 52
9.1 ZIP encryption............................................................................................................................... 52
9.2 AES encryption .............................................................................................................................. 52
9.2.1 How to generate crypt_key.dat ................................................................................................ 52
9.2.2 How to decrypt image buffers..................................................................................................... 53
10 System enabling and disabling and General Setting ................................................................................ 54
10.1 Operating modes ........................................................................................................................... 55
10.1.1 Free Run mode ......................................................................................................................... 56
10.1.2 Trigger from digital inputs mode ................................................................................................. 56
10.1.3 Trigger Ethernet mode .............................................................................................................. 58
11 Image grabbing .................................................................................................................................. 60
12 OCR configuration ............................................................................................................................... 64
12.1 Configuring the OCR parameters ..................................................................................................... 64
12.2 Lane Config................................................................................................................................... 70
12.3 Last transit image .......................................................................................................................... 74
13 OCR reading text results ...................................................................................................................... 76
14 OCR reading statistics ......................................................................................................................... 77
15 Using car plate lists............................................................................................................................. 78
16 Color context camera .......................................................................................................................... 81
16.1 Double heads camera (2H) ............................................................................................................. 81
16.2 External context camera ................................................................................................................. 84
17 GPS .................................................................................................................................................. 86
18 Secure digital memory ........................................................................................................................ 88
19 Network interface configuration ............................................................................................................ 90
19.1 Check syncronization ..................................................................................................................... 92
(Brescia), Italy..
2-128
VEGA User Guide

19.2 Activating a time server on Windows PC ........................................................................................... 93
20 Managing web server users .................................................................................................................. 94
21 Trace and Log messages ..................................................................................................................... 96
22 Firmware update ................................................................................................................................ 97
23 Installation layout and diagnostic configuration .................................................................................... 100
24 Device information and diagnostic ...................................................................................................... 102
24.1 Information................................................................................................................................. 102
24.2 Diagnostic................................................................................................................................... 102
25 Digital inputs and outputs .................................................................................................................. 104
25.1 ID management .......................................................................................................................... 104
25.1.1 Example of time evaluation for IDs ........................................................................................... 105
25.2 External strobe signal................................................................................................................... 105
26 System statistics .............................................................................................................................. 106
27 RTP streaming .................................................................................................................................. 107
27.1 Vega 2HD streaming .................................................................................................................... 107
27.2 Vega 2H streaming ...................................................................................................................... 109
27.2.1 Encoder configuration.............................................................................................................. 110
27.2.2 Device configuration................................................................................................................ 112
28 Appendix A: Extraction of timestamp from IDR (H264) or I (MPEG4)....................................................... 113
28.1 Frame IDR H264 .......................................................................................................................... 113
28.2 Frame I (MPEG4) ......................................................................................................................... 113
28.3 Content of field user data ........................................................................................................... 114
28.4 Example ..................................................................................................................................... 114
29 Appendix B: examples of system architectures ..................................................................................... 115
30 Appendix C: available TAGs ............................................................................................................... 116
30.1 Example: Building a file name string. ............................................................................................. 116
30.2 Example: Building path name. ....................................................................................................... 116
30.3 List of available TAGs ................................................................................................................... 117
30.4 Jpeg header data ......................................................................................................................... 122
30.4.1 Web page .............................................................................................................................. 122
30.4.2 Header decoding..................................................................................................................... 122
30.5 TCP message data types ............................................................................................................... 124
30.5.1 Type STRING ......................................................................................................................... 124
30.5.2 Type LONG ............................................................................................................................ 125
30.5.3 Type BUFFER.......................................................................................................................... 125
30.6 List of available enumerators ........................................................................................................ 125
30.6.1 TAG CLASS and CLASS_STRING .......................................................................................... 125
30.6.2 TAG VEHICLE_TYPE .............................................................................................................. 125
31 Appendix D: List of supported countries .............................................................................................. 126
31.1 Country code .............................................................................................................................. 126
31.2 Supported countries ..................................................................................................................... 126
31.3 Special plates .............................................................................................................................. 127
(Brescia), Italy..
3-128
VEGA User Guide
1 Conventions used in this document

Generic Note: generic information on how to use the system
Warning: specific suggestions that may as well refer to security matters
(Brescia), Italy..
4-128
VEGA User Guide
2 Document revisions
Document revisions
Ver.
Date
4.29
5.00
5.01
5.02
17 August, 2007
1 October, 2007
29 January, 2008
30 January, 2008
5.03
25 November, 2008
5.04
5.05
20 December, 2008
13 January, 2009
Author
5.08
5.09
02 December, 2010
6.06
6.07
6.08
6.09
6.10
6.11
6.12
6.13
6.14
6.15
6.16
6.17
07 August, 2012
11 September, 2012
8 October, 2012
30 October, 2012
04 February, 2013
20 February, 2013
28 February, 2013
10 April 2013
19 April, 2013
06 May, 2013
26 June, 2013
30/07/2013
6.18
16/09/2013
6.19
18/09/2013
6.20
04/10/2013
6.21
15/10/2013
6.22
30/10/2013
6.23
27/01/2014
6.24
13/02/2014
6.25
14/02/2014
6.26
04/03/2014
Comment
compatibility
with Vega
version
Aligned with firmware version 4.29

Updated page on Live video with 4 working points.
Added info on Ethernet trigger.
Aligned with firmware version 5.22
Added documentation on VRC server TCP
message.
Remove notes
Fixed VRC protocol documentation (Grab image
and Trigger Ethernet).
Added command to get TCP error counter
Fixed Country codes.
Added OCRSCORE in TCP Message buffer
Added possibility of a char separator between group
of characters into plate string
Added possibility to put TCP message after FTP
actions
Fixed a bug on grab image protocol: datasize on
data buffer was wrong
As for Italian version 6.04.
Added description for TAG CAM_SIGN
Added parameters in PLATE_READER page
Added parameter for TCP Message
Added TAG descriptions and diagnostic information
Changed first page
Added jpeg header example in appendix
Modified TAGs table
Full manual review
Added details
Added details about Milestone integration
Added TAG descriptions DIRECTION
Added Overlay TCP Message TEXT OPTION,
TEXT VALUE
- Added TAG_GRAB_MODE
- Modified description in context camera
Added description of new parameters in Plate
Reader page
- Added encryption information
- Added distinct configuration of jpeg quality for BW
and CTX
Added XML message format in TCP Message
section
Added explanation of Previous & Post ZEAG
Trigger Parameters
Added notes on TAGs VEHICLE_TYPE_NUM,
FIAG_MASK
Added PLATE_HASH tag
Added YEAR, MONTH, DAY, HOUR, MIN, SEC
tags
Added section on digital inputs and outputs
Vega 10.8
Vega 10.8
Vega 10.57
Vega 10.60
Vega 10.63
Vega 10.63
Vega 11.2
Vega 11.10
Vega 11.14
Vega 11.15
Vega 11.19
(Brescia), Italy..
5-128
VEGA User Guide

6.27
18/03/2014
B. Galvani
6.28
6.29
6.30
6.31
6.32
04/04/2014
14/04/2014
27/05/2014
19/06/2014
24/06/2014
L. Bonisoli
L. Bonisoli
L. Bonisoli
L. Bonisoli
L. Bonisoli
6.33
30/06/2014
L. Bonisoli
6.34
22/09/2014
L. Bonisoli
6.35
6.36
08/10/2014
08/10/2014
L. Bonisoli
A. Dondi
6.37
13/10/2014
F.Conti
6.38
24/10/2014
A. Dondi
6.39
30/10/2014
F.Conti
6.40
21/11/2014
A. Dondi
6.41
26/11/2014
F.Conti
6.42
04/02/2015
F.Conti
6.43
04/02/2015
F.Conti
6.44
16/02/2015
F.Conti
6.45
11/03/2015
F.Conti
6.46
27/03/2015
L.Bonisoli
6.47
21/05/2015
Fabio Conti
Updated description of Save DB page. Added CRLF

and LF tags
Added PLATE_PROVINCE tag
Added chapter on GPS
Added description of Save DB on SD page
Specified vehicle speed format
Added vehicle classes enum
- Added TAG PLATE_REGION, PLATE_PREFIX
- More details in TCP Message format
- Added TAG PLATE_STRING, PLATE_COUNTRY
for jpeg header
- Removed maximum string limit for PLATE_* tags
- Description of date/time format (local time)
Added description for jpeg output colorspace
Added TAG PLATE_CENTROIDS
Update Screen-shot Trigger Settings web page and
added meaning of Previous Image ms parameter
Added VRC message receiver description
-Removed limit of 200Kb for files list
-Updated parameters Diag_String word Tags
-Expanded explanation for the TCP / IP Milestome
Protocol.
- Added TAGs UTC_DATE and UTC_TIME
- Added diagnostic description
-Updated Screenshot of NETWORK web page
-Updated Explanation of the "Protocol" Time
Server section:
a) SNTP synchronization via NTP server.
b) PTP: synchronization via IEEE1588 protocol v1.
c) GPS: synchronization via GPS module.
- Update screenshot "System" "Configuration"
- Renamed field "Alarm repeat time (min)" in
"Message repeat time [min]".
- Expanded description of the field "Manage
configuration status".
- Add a description of the new field "Generate
periodic message:".
Add description "lane config" web page.
Added description of the LANE_ID TAG
Explanation Minimum values for Shutter and gain in OCR
page.
Added XML support for PLATE_ADR, PLATE_STD,
PLATE_TRL
Configuration lane Advanced feature is not for Vega
Access.
Vega 11.22
Vega 11.25
Vega 11.27
Vega 11.31
Vega 11.40
Vega 11.41
Vega 11.52
Vega 11.53
Vega 11.53
Vega 11.53
Vega 11.53
Vega 11.56
Vega 11.55
Vega 11.63
Vega 11.63
Vega 11.63
Vega 11.63
Vega 11.67
Vega 11.67
(Brescia), Italy..
6-128
VEGA User Guide
3 Vega features
Vega outlines a family of cameras produced by Tattile for automatic car plate reading.
Vega is suitable for parking lots, limited traffic areas surveillance, traffic monitoring and free
traffic statistics.
The system is highly integrated and contains the following components in a single casing:
Black and white camera for car plate number reading
Color Camera (*)
Processing board for real time OCR reading, service and user interface management
Infrared illuminator (IR)
Secure digital memory (*)
Digital input and outputs
Ethernet interface
RS-232 e RS-485 serial ports
Dedicated processor for MPEG4/H264 color streaming video (ONLY for Vega 2H)
GPS unit (*)
(*) Only on the devices which support it
For a detailed description of each product specifications and available optional features, please
see the Installation Guide.
Illuminator IR
Serial Ports
Digital IO
Camera BW for
OCR
Ethernet
100Mbit
Color Camera (*)

Main Board
Secur Digital (*)
Power 24VDC
Loop Detector(*)
Loop Detector (*)

Ethernet
100Mbit
Encoder
MPEG4/H.264 (*)
Main Board
(Brescia), Italy..
7-128
VEGA User Guide
4 Vega unit configuration

Vega system configuration is set using the Ethernet interface. Two modes are available:
Vega embedded web server
Vega embedded VRC, server
VEGA Number Plate Reader
WEB Server
WEB
Browser
Network
VRC Server
VRC Client
Application
4.1 Web server

If configuring the Vega system using the web server, a web browser (such as Internet Explorer,
Google Chrome or Mozilla Firefox) is required to access the unit.
This Guide describes all features available from Vega web server.
4.2 VRC server

When working with complex systems with automated device supervision, a VRC (Vega Remote
Control Server) is used in order to integrate and control the Vega unit. This server provides for
several services that can be accessed through a TCP-IP socket connection. For details please
consult the specific guide of VRC protocol.
4.3 Receiving data from Vega unit

Vega operates as Client unit. Upon detecting an event, it sends data to a remote server.
Several operating modes are available, which can operate simultaneously as well:
Ethernet network: Vega operates as FTP client (up to 2 different FTP server can be
set)
Ethernet network: Vega operates as client using Tattile protocol on IP socket (up to 2
different TCP server can be set)
Ethernet network: messages to specific software for access control named Gate
Master.
Serial ports: messages are sent to serial ports.
(Brescia), Italy..
8-128
VEGA User Guide

In FTP mode, the user must have an FTP server where Vega will send data and/or images. For
further details, please refer to relevant section in this Guide where events/actions available on
Vega systems are presented.
In TCP-Message mode, the user must develop a server capable of receiving data to TCP-IP
socket. For details on data format and how to use this feature, please see Send Messages to
TCP-IP socket section in this Guide.
In both modes, the data to be sent, the name to be assigned to images, the path for saving etc.
are all configurable using Vega web interface.
The chart below shows the available modes for data exchange:
VEGA Number Plate Reader
FTP Client
FTP
Server
TCP
Message
Client
TCP
Message
Server
Network
GM
Message
Serial Port
Client
GM server
Serial Connection
Serial Port
Server
Some models of the Vega family come with embedded secure digital (SD) memory. If data
sending is not possible, for instances when network communication is not available, data are
automatically archived to SD. Data are then automatically retrieved from SD and sent once the
connection has resumed.
In some models there are 2 SD, in this case the second one could be used as local storage for
images.
For details, please refer the section describing SD management. For Vega models with
embedded SD memory please refer to the Installation Guide.
(Brescia), Italy..
9-128
VEGA User Guide
5 Using the web server

Vega IP address must be known in order to access its web server. Tattile developed the
TATTILE DEVICE DISCOVERY (TDD) software. TDD allows searching the LAN network for
Vega machines that are connected and active.
This search does not depend on the network configuration of the PC where the TDD is being
carried out. This means it is not necessary to define any network settings for the PC since the
program operates in broadcast mode.
Please check your firewall settings! Broadcasts are usually blocked by it, so you need to
disable firewall.
The TDD allows setting the IP address, Netmask and NetBiosName of each machine.
5.1 Tattile Device Discovery and manuals downloads

The TDD application, as documents and other utilities, are downloadable from the Download
Area at following link:
Server: ftp://support.tattile.com
Username: read2traffic
Password: reda998
5.2 Using Tattile Device Discovery

Click on Search all devices to retrieve the list of available devices on the local network.
Double click on the device entry to modify the device parameters.
Click on Update device parameters to save the configuration on the device.
If the PC has 2 or more network cards, please choose the right one with the PC IP Selection
button.
(Brescia), Italy..
10-128
VEGA User Guide
5.3 Web browser access and user authentication

Prior to accessing the number plate reading unit using a Browser, make sure the PC network
configuration is coherent with the IP address of the device to access. For example: if the Vega
(Brescia), Italy..
11-128
VEGA User Guide

machine IP address is 192.168.0.100, the PC in use should be temporarily assigned an IP
address belonging to the same class (e.g. 192.168.0.200). Alternatively, use the TDD to modify
Vega IP address.
Once the static IP address of the Vega unit has been retrieved, type the numeric sequence in
the navigation address bar of the browser in use and either press Enter from the keyboard.
The Login Window appears where the user is asked to type in his/her Username and
Password.
Note: factory assigned user name and password are as follow:

User name: superuser
Password: superuser
Warning: for best access security, once the device has been installed, please
change the factory-assigned username and password (see HTTP Users Settings).
(Brescia), Italy..
12-128
VEGA User Guide
5.4 Access levels

Three user categories are available:
Superuser
Administrator
Guest
These three User Levels differ in such that: the Superuser is allowed to access all systemenabled features, modify operational parameters (set-up) and assign access rights to other
Vega users.
The Administrator user, unlike the Superuser, has no right to modify the user settings, and is
therefore not allowed to access the HTTP users page (described later in this document).
The Guest user is only allowed to view the system parameters, HTTP users page not included.
(Brescia), Italy..
13-128
VEGA User Guide
6 Main web page

If login was successful, the User is now able to access the program main menu screen.
The main page shows two sections: Plate Reader and System (link in the left side of the page).
The icons vary according to the Vega model in use while the software is the same for all
devices of the Vega family. The software can detect its hardware platform and thus dynamically
generate its web interface.
Figure 1: Page "Plate Reader"
Figure 2: Page "System"
Plate Reader contains the following features:

General: Vega general settings: operating mode, general settings, enabling and stand-by
mode selection.
(Brescia), Italy..
14-128
VEGA User Guide

Camera Ocr: this page relates to the black/white image camera used for car plate
reading. In this page it is possible to view a live video and its image grabbing
parameters, and to save and export the displayed image.
Camera Context: this page displays the color image-grabbing camera used for shooting
context images. This icon only appears in the web interface of Vega models with
Context Camera feature. The overview camera could be integrated in the same device
(a single device with 2 channels), or external. In this case standard IP camera are
supported, providing the accept a call to a http request for retrieving the images (ie:
Sony, Axis).
Plate Reader: this page contains the settings of plate recognition parameters (minimum
and maximum character size, plate searching area, time integration i.e. the duration of a
vehicle transit, image selecting mode, etc).
Lane Config: Page in where you can configure the lanes and assigning to each transit
the correct identification of the lane. Also useful to know in which lane was generated
the transit (acquisition mode TRIGGER_INTERNAL).
Digital Trigger: this page contains the settings of the digital inputs for external trigger
interfacing (such as passing-by vehicle magnetic loop detectors, photo sensors, etc...).
Check List: the settings of the lists of vehicles that are authorized/not authorized to pass
through the gate monitored by the unit. Two lists are available, which can be used as
generally as possible. Typically, the first list would include authorized vehicles. The
second list may include those vehicles that require a different event management, such
as an alarm generation.
Events Actions: the settings for actions the camera executes when an event is raised.
For example: send image to an FTP server when the plate number was recognized, or
activate a digital output when the recognized plate number belongs to either one of the
plate list in use, ect
Image Results: this page displays the last selected image of a vehicle transit. Helpful
when monitoring the system real time performance.
Text Results: this page displays the last results from a vehicle transit.
Statistics: this page displays the statistics of the Vega car plate reading machine (the
statistics refer to the last 24 hours of operating).
RTP: only for specific cameras is possible to enable a colour streaming video MPEG4 or
H264 during the normal working of the camera.
System contains the following features:
Network: the settings of Network configuration and Time synchronization through Time
Server (SNTP and PTP Protocol) or GPS module (It depends on Vega System).
HTTP users: the configuration settings for users who use a browser to access the
machine.
(Brescia), Italy..
15-128
VEGA User Guide

Log Files: the settings for generating log files on a remote ftp server or in a local device.
Serial Ports: the settings of the serial ports (COM) of the machine: through such ports
the Vega car plate reader sends transit data and plate readings to an external unit.
These parameters relate to baud rate, stop bits, etc
Firmware: this page displays the commands for updating the machine to the latest
software release and extracting the configuration to be automatically copied to another
unit.
Device Info: this page displays info about the system hardware, configuration and
firmware versions.
Digital IO: direct read of the digital input status, and set of the outputs.
Sys Statistics: statistics on transfer pass bands to remote servers and statistics on
synchronicity of SNTP time synchronization.
Secure Digital: secure digital partitions status. The Buffering partition is used by the
device for temporary storing data to be sent if the first attempt fails. The Storage
partition is for storing data for remote access via ftp.
Protocols: configuration page for various protocols used by the camera.
Diagnostic: configuration page for diagnostic limits, alarms.
Apply button: to apply the changes you must click on Apply button at the
bottom of most pages. In some cases the device will warn you for a reset needed.
Reset button: to undo changes in the page, you can click on the Reset button
at the bottom of most pages.
(Brescia), Italy..
16-128
VEGA User Guide
7 Events and actions

Vega engine software generates a series of events. It is possible to associate one or more
actions to each event.
Using WEB pages
A graphic matrix in the web interface is used to plan the actions required for handling the
generated kind of events.
The icon of access to the configuration matrix is shown below here:
The configuration matrix of the actions is shown below here:
(Brescia), Italy..
17-128
VEGA User Guide

The left column contains the list of events the system generates:
OCR Read: this is the car plate that has been read
OCR Not Read: this is a car plate that has been partially read. By partially read we mean
that groups of character were read that do not comply with any syntax supported by
OCR libraries of the version in use. Typically, an OCR Not Read event is generated
when the detected car plate does not belong to any Country of Origin the firmware
version can actually read or when the car plate cant be properly read due to dirt or
damage.
OCR No Plate: this is an image containing no plate number. This kind of event is
generated in trigger mode only. For a more detailed description of the various
available operating modes, please see the next paragraphs in this Guide.
Match on List A: this is a car plate number that has been read and recognized as
belonging to list A.
No Match on List A: this is a car plate number that has been read and has no match on
list A.
Match on List B: this is a car plate number that has been read and recognized as
belonging to list B.
No Match on List B: this is a car plate number that has been read and has no match on
list B.
Start Trigger: this is the Start Trigger event (either a digital or Ethernet I/O trigger).
Stop Trigger: this is the Stop Trigger event (either a digital or Ethernet I/O trigger).
System Alarm: this is the diagnostic notification. It is triggered by a change of state
variables checked by the internal diagnostic service. See chapters 23 and 0.
Changed ID: this is the ID changed notification. It is triggered by a change of the state of
a watched ID. (See chapter 25, this feature is available only for Vega HD familys
camera)
This matrix may contain the following symbols:
It indicates that when dealing with a certain event, the corresponding action
is enabled.
It indicates that the action was deactivated.
In case the event/action pair is not possible, the matrix will show no symbol.
In order to enable, disable or configure an event action, it is sufficient to click the box
corresponding to the check or uncheck symbols, as shown above. This will access the User to
the Configuration page that contains all action parameters and allows enabling/disabling the
action itself.
(Brescia), Italy..
18-128
VEGA User Guide
The Configuration page allows setting each action parameters using configuration TAGs. The
TAGs is strings starting with a % symbol. Click the context HELP buttons in each web page to
view the available TAGs (in appendix 30 complete list of TAGs with descriptions).
Vega firmware understands the TAGs and translates them to their corresponding value. For
instance: lets think of how to form the name of the file to which the image will be saved. If the
file name was set to %PLATE and the car plate is HG542ER and it is Italian then the file name
is HG542ER-ITA.JPG (if image is saved to JPG format).
%PLATE HG542ER-ITA.JPG
When using TAGs not provided by the software, they are not translated and are left unchanged.
For example, the %TEST TAG is not supported, so that:
%TEST%PLATE TESTHG542ER-ITA.JPG
Separators, such as the _ character, are handled as unknown TAGs so it is possible to use
them to separate file name components.
%TEST%_%PLATE TEST_HG542ER-ITA.JPG
Joining of special plates: trailers and/or ADR (dangerous goods)
In case the firmware is enabled is possible to join in the same result the reading of two plates if
one of them is a Trailer (TRL) plate or a Dangerous Good (ADR) plate.
Reading of standard Italian plate and Trailer plate
%PLATE HG542ER-ITA&AB12345-TRL.JPG
Reading of standard Italian plate and Dangerous Good plate
%PLATE HG542ER-ITA&331088-ADR.JPG
Shared Configuration
This feature allows to create a sequence of TAG words (defined as default) which can be used
in an immediate way in the various fields of the matrix events.
Is also possible to perform a real-time event monitoring.
The available actions and their detailed descriptions are shown below.
(Brescia), Italy..
19-128
VEGA User Guide
7.1 Save image to FTP server

This action corresponds to the Save Image FTP and Save Image FTP 2 columns. If enabled,
this function allows saving to a remote FTP server the images of vehicle transits detected by
the car plate reader. When the context camera is provided for and is enabled, two images per
transit are saved. The context image file name has a distinctive _CTX suffix. This does not
depend on whether the Vega unit has a context camera or whether you are using an external
context camera synchronized with Vega through the network (Vega Network Context).
Using the WEB pages
Enable: this parameter takes two possible values: YES or NO. If enabled (YES), this feature
allows saving the image of the event.
Encryption: allows to enable encryption of images. Options available:
1) No encryption
2) ZIP encryption. OBSOLETE. Do not use.
3) AES encryption
Please refer to Image encryption chapter for further details.
(Brescia), Italy..
20-128
VEGA User Guide

Jpeg Quality: the values may range from 1 to 100 where 1 is the maximum compression level
(lowest quality) and 100 is the minimum compression level (highest image quality). Suggested
values from 50 to 90.
Example of high quality (90) JPG image
Example of low quality(5) JPG image

Crop Image: this setting allows sending to an FTP server a crop of the full image. Such crop is
cut around the car plate. Available sizes: 320x240, 640x480, 800x600, 1024x768 or
PLATE_ONLY where the cutting is made just around the plate.
Sending an image crop instead of the full image saves space on the storage server and cuts
down on transmission time on the network (this is useful when working with low pass band
networks).
Path Name: it allows specifying the folder name where the car transit image is saved.
It is possible to use appropriate TAGs or arbitrary string to indicate this folder name.
Each % is a separator for creating folders. In case the specified directory path does not exist
on the FTP server, the Vega unit automatically creates it.
(Brescia), Italy..
21-128
VEGA User Guide

Example 1: In case the path name is %DATE%HOUR, when the date changes the Vega
system dynamically creates a new folder tree corresponding to the current date and hour (ie:
2013-05-17/08 for 8AM 17 May 2013).
Example 2: To join two or more TAGs without creating a new folder, you can use the &
symbol: %DATE%_%HOUR (ie: 2013-05-17_08).
Example 3: Each sequence of chars not recognized is treated as generic string (ie:
%DATE&_CUSTOM_STRING%HOUR will create: 2013-05-17_CUSTOM_STRING/08).
File Name: it allows specifying the name to assign to the vehicle transit image to save.
It is necessary to use appropriate TAGs to indicate this file name.
For example, use the %PLATE TAG in order to insert the read car plate in the name
Ctx Enable: enables the sending overview camera images.
Ctx Jpeg Quality: the values may range from 1 to 100 where 1 is the maximum compression
level (lowest quality) and 100 is the minimum compression level (highest image quality).
Suggested values from 50 to 90.
Ctx File Name: overview camera filename.
Text Position: it allows specifying the position of a text window inside the saved image. This
window contains the information entered in Text Value. The allowed values are: TOP_LEFT,
TOP_RIGHT, BOTTOM_LEFT, BOTTOM_RIGHT and DISABLED.
Text Options: it allows to enable the option NOT_OVER_PLATE. This option move
automatically the text window when positioned over the plate, in order to not cover the plate.
Text Value: it allows specifying information to be included in the image, whose position is
indicated in Text Position. It is necessary to use appropriate TAGs to provide this information.
Available TAGs are made up by the character % followed by a string. For example, use the
%PLATE%DATE%TIME TAGs in order to save the image containing the plate, acquisition
date and time.
Upon inserting any TAGs, a new caption is added above the image, as shown in the image
below:
(Brescia), Italy..
22-128
VEGA User Guide
FTP IP: the IP address of the FTP server.

FTP Username: the username of the FTP server.
FTP Password: the password of the FTP server.
FTP Port: the port of the FTP server.
FTP Passive Mode: it allows to enable (YES) the passive modality (PASV) for data
transferring.
Conditional execution: See chapter 7.9.
Buffering on SD: when it is present the Secure Digital memory. In case of network failure and
Buffering SD enabled, the camera is able to save automatically all data regarding the actions to
perform over the network. The saving is based over a circular buffer, in case of full memory the
camera will overwrite oldest data. When the network is newly available the camera will manage
automatically all data stored, freeing the memory.
FTP LINK: by clicking on the blue hypertext, it is possible to directly access the address of the
Server where images are saved. This hypertext automatically shows the parameters entered in
the FTP IP, Username, Password and Port fields. This link is useful to check whether the FTP
server is operating properly.
7.2 Saving text messages to FTP server

This action corresponds to the Save DB and Save DB 2 columns of the matrix. If enabled, this
feature allows creating and automatically updating on a remote FTP site a text file in CSV
(Brescia), Italy..
23-128
VEGA User Guide

format (CSV Comma Separated Values) containing information about every vehicle transit
detected by the Vega plate reader.
Using the WEB pages
Encryption: allows to enable encryption of images. Options available:
1) No encryption
2) AES encryption
Path Name: it allows specifying the folder name where the database is saved. It is necessary
to use appropriate TAGs to indicate this folder name. For example, when using %DATE, a
new folder is created each day.
File Name: it allows specifying the name of the database to be updated with the data about
vehicle transit. For example when using %DATE a new file is generated each day. The file
name is the date on that day e.g.: 2008-10-28.
File Extension: specifies the extension of the generated file. For example, if File Name field
contains %DATE and File Extension contains CSV, the resulting file name will be similar to
2008-10-28.CSV. The File Extension field can be left empty.
Fields: it allows specifying the database fields.
Example:
(Brescia), Italy..
24-128
VEGA User Guide

String on web interface:
%DATE%;%TIME%;%PLATE%;%IMAGENAME
CSV file on FTP server:
DATE;TIME;PLATE;IMAGENAME
2007-10-03;09-14-50-222;SA249BH-ITA;SA249BH-ITA_2007-10-03_09-14-50-222.jpg
2007-10-03;09-15-00-569;CH123BV-ITA; CH123BV-ITA_2007-10-03_09-15-00-569.jpg
2007-10-03;09-18-07-234;AF234SV-ITA; AF234SV-ITA_2007-10-03_09-18-07-234.jpg
Save Headers: when this field is set to YES, the system inserts a row containing the list of
fields at the beginning of the file.
FTP IP: the IP address of the FTP server.

FTP Password: the password of the FTP server.
FTP Passive Mode: it allows to enable (YES) the passive modality (PASV) for data
transferring.
FTP LINK: by clicking on the blue hypertext, it is possible to directly access the address of the
Server where images are saved. This hypertext automatically shows the parameters entered in
the FTP IP, Username, Password and Port fields. This link is useful to check whether the FTP
server is operating properly.
7.3 Send alarm to Gate Master (GM alarm)

This action corresponds to the GM Alarm column of the matrix. Gate Master (GM) is Tattile
software product for managing park lots and monitoring plates.
Gate Master includes a service for receiving messages from systems of the Vega family.
Using the WEB pages

(Brescia), Italy..
25-128
VEGA User Guide
Send Jpeg Image: it takes two possible values: YES or NO. If enabled (YES), this feature
attaches to the message an image of the transit event (in JPEG format).
GM Server IP: the IP address of the PC to which the alarm message will be sent.
GM Server Port: the port to which the GM server will receive messages. Its default value is
35.000.
date and time.
Upon inserting any TAGs, a new caption is added above the image.
(Brescia), Italy..
26-128
VEGA User Guide

7.4 Pulse out

This action corresponds to the Pulse Out column of the matrix. It allows activating any of Vega
digital outputs over a specified period of time. For electric specifications of the digital inputs and
outputs of the various Vega models, please refer to the Installation Guide.
Note: Vega machines are equipped with an internal I/O circuit with control outputs
for direct management of electrical devices (such as LEDs, sound alarms,
blinking, display) or electromechanical devices (such as electrical locks,
motorized barriers, traffic bollards, motorized gates) associated with systemgenerated events.
Using the WEB pages
Enable: it takes two possible values YES or NO.

Output Number: number of the digital output to be activated by the value shown in Pulse Time
ms.
Delay Time ms: delay to be applied prior to actual activation of the digital output on the car
plate reader. This value is expressed in milliseconds.
Pulse Time ms: the time period (in milliseconds) during which the output is high.
(Brescia), Italy..
27-128
VEGA User Guide
7.5 Send messages to RS 232 and RS 485 serial ports

This action corresponds to the COM 232 Message and COM 485 Message columns of the
matrix. It is possible to send messages to 232 and 485 serial ports. TAGs are used to define
the content of the message sent. The configuration form of a message to port 232 is shown
below. The configuration for messages to port 485 is identical.
Using the WEB pages
Enable: it takes two possible values YES or NO.

Message: this field allows specifying the syntax of the message to be transferred through the
serial port.
7.5.1
Configuration of the RS232 and RS485 serial ports
Before using the serial ports, it is necessary to configure them in a web page found in the
system section.
This configuration page is accessed via the icon shown below:
Using the WEB pages
(Brescia), Italy..
28-128
VEGA User Guide
Settings for both port 232 and 485 are equal.
Enable: it allows enabling or disabling communication through the serial port.
Baud Rate: it allows specifying the serial port communication speed. The allowed values
are: 2.400, 4.800, 9.600, 19.200, 38.400, 115.200 Kbps.
Parity: it allows specifying the congruence check of data, performed on the parity bit.
The allowed values are: NONE, EVEN and ODD.
Data Bit: default setting 8.
Stop Bit: it allows specifying the stop bit value. The allowed values are 1 (one) or 2
(two).
Message: it allows specifying the message protocol. The available options are: RAW or
PROTOCOLLED.
Wait ACK: it allows enabling/disabling the confirmation signal sent by the external unit
upon data receiving. The available options are: YES and NO (only when in Protocolled
mode).
Timeout ms: it allows specifying the time (in milliseconds) of waiting for an answer from
the external unit (only when in Protocolled mode).
Retry Number: it allows specifying the number of times the Vega machine will try to resend the
message to the external receiving unit (only when in Protocolled mode).
(Brescia), Italy..
29-128
VEGA User Guide
7.5.2
Output date format
Two format is disabled: RAW and PROTOCOLLED.

RAW format allows for full message setting using Vega web interface. Using the
PROTOCOLLED format involves a super structure and an acknowledge packet, if received.
When in this mode, everything works exactly like when in RAW mode but in addition, the Vega
firmware inserts a header and footer at the beginning and at the end of the message,
respectively. The header contains an open message code, an ID and the message size. The
footer contains a xor byte and a close message code.
When building the data packet to be sent, it is possible to use a TAG that inserts bytes using
hexadecimal decoding. This makes data packet building more flexible than when using
alphanumeric characters only.
For example: in order to send the car plate number string followed by the two bytes sequence
CR (carrier return) and LF (line feed) as terminators, the message field is to be set as follows:
%PLATE%0x0D%0x0A
where 0x0D and 0x0A are the hexadecimal codes of CR and LF, respectively.
7.5.3
Format protocol PROTOCOLLED
Protocol definition is as follows:

Protocolled data packet sent by the Vega unit
Number of bytes
Value
0x89
Open Message Code - byte 0
Description
0XAB
0xCD
0xEF
ID
DataLen
Message Progressive ID
Data Size in Bytes
Data Packet
DataLen
1
XOR
Xor byte of all previous bytes (DataLen+4+4+1+1+1+1)
0x12
Close Message Code - byte 0
0x34
0x56
0x78
A progressive integer number starting from 1 gives ID value. Such value is augmented at each
message sending. The 4 bytes in DataLen are sent starting from the most relevant byte.
It is possible to specify or not (using the web interface) whether an acknowledge packet should
be waited for.
The packet structure is as follows:
Acknowledge Packet
Number of bytes
1
4
1
Value
0xA5
ID
0x5E
Description
Open ACK Message Code
Message ID
Close ACK message Code
The ID in the ACK message must be the same as the ID of the received message.
(Brescia), Italy..
30-128
VEGA User Guide
7.6 Sending messages to TCP-IP socket (TCP Message)

This action corresponds to the TCP Message and TCP Message 2 columns of the matrix.
TAGs are used to define the data to insert in the packet to send. Such TAGs are entered in the
Message field of the web configuration form. It is possible to insert in the packet either data
(such as car plate number, date and time) or the JPEG image of the vehicle: %IMAGE_BW for
the B/W image used for car plate reading and %IMAGE_COL for the color image available with
systems having an embedded context camera or systems associated with a Vega Network
Context camera.
Using the WEB pages
Enable: it takes two possible values YES or NO. It allows to send data over socket TCP-IP.
YES means function enabled.
Message: see description for each available message format. Please note that each TAG or
generic text written in this field must start with a %.
Message format: it allows to choose the type of message to send. For example:
STANDARD: message is formatted through the using of all TAGs, but you can not
place arbitrary fields (see TAGs List).
STRING: The message string is formatted either using the only string TAGs or using
arbitrary strings (therefore images are not included).
XML: the message is a XML document.
ZEAG: the message is ZEAG compliant (it is possible to modify only Jpeg Quality and
Crop Image).
MILESTONE: data are sent as Analytics Event to the Xprotect server.
(Brescia), Italy..
31-128
VEGA User Guide
Image Encryption: allows to enable encryption of images, available only in STANDARD

message format. Options available:
1) No encryption
2) AES encryption
Message: it allows to specify which data to send over the socket TCP-IP. The HELP button
specify which TAGs use. It is possible to send also the images. Maximum length: 255 bytes.
Crop Image: This option is available from version 10.57. This setting allows sending to TCP-IP
server a crop of the full image. Such crop is cut around the car plate. Available sizes: 320x240,
640x480, 800x600, 1024x768 or PLATE where the cutting is made just around the plate.
networks).
date and time.
Upon inserting any TAGs, a new caption is added above the image.
Server IP: IP address of the destination server.
Server Port: port of the destination server.
Reuse Connection: two modes are available for handling the TCP-IP connection:
Open and close connection at each message sending.

Open connection upon sending the first message and keep the connection active.
(Brescia), Italy..
32-128
VEGA User Guide

Regardless of mode configuration, Vega will close and open a new TCP connection if problems
occurred while sending data. This means the receiver must be steadily ready to accept new
TCP connections.
When in keep connection open mode, the connection is automatically shut if unused for 15
minutes.
Jpeg header: configuration of TAGs inserted in the jpeg header. See Chapter 30.4 Jpeg
header data for further information.
7.6.1
STANDARD protocol
The protocol allows to send data in machine readable format.

Each field inserted in the Message field must be an available TAG. Unknown TAGs will be
discarded.
This protocol is described in chapter 30.5 TCP message data types.
7.6.1.1 Sample software

A server in Windows .NET Framework was developed that makes application testing and
developing easier. Such server allows opening a single TCP listen connection to display data
and images received from a Vega system.
In order to receive a new connection from Vega, the server should always have an open listen
connection. This operational mode is compulsory in case of errors in Vega client as they may
cause the connection to close and automatically to reopen.
In our example, the server uses port 32000.
Tattile provides for the source code of this project. The source code uses Windows the Tattiles
NTCPSDK dlls.
The image below shows the program dialogue window. The message receiver is a feature of
the sample application called VRC Client. Into the VRC window the two top panel display the
black and white image and the color image, if available. The bottom panel shows all data in the
received message.
The Decoder option allows to specify how to decode the message fields, in case of non ASCII
plate strings as UTF8.
In order to receive the sample application and its source code please contact traffic@tattile.com
(Brescia), Italy..
33-128
VEGA User Guide
7.6.2
String format
Output is generated using a syntax where each transit is represented by a string composed by
all fields specified in the Message field. The Message field can contain TAGs and generic
text. Each unknown TAG will be considered as string.
For example, these message TAGs:
%PLATE%_%DATE% %TIME%_TEST_SITE
Generate the following string output:
369AXJ-CANSK_2014-06-24 18-18-17-125_TEST_SITE
7.6.3
XML format
Output is generated using a XML syntax where each transit is represented by a root node and
every TAG specified by the user in the Message field is represented by a child node.
For example, these message TAGs:
%PLATE%DATE%TIME%GAIN%SHUTTER%STROBO%IMAGE_BW
Generate the following XML output:
<?xml version='1.0' encoding='UTF-8' standalone='no'?>
<root>
<PLATE>AA555AA-ITA</PLATE>
<DATE>2013-10-30</DATE>
<TIME>17-08-55-808</TIME>
<GAIN>256</GAIN>
(Brescia), Italy..
34-128
VEGA User Guide

<SHUTTER>20000</SHUTTER>
<STROBO>1000</STROBO>
<IMAGE_BW> (BASE64-encoded image) </IMAGE_BW>
</root>
7.6.4
Custom protocol
Custom protocol are available only for new products Vega Access, Vega III and Vega 2HD.
Before using the custom protocols, it is necessary to configure them in Protocols web page
found in the System section.
Using the WEB pages
7.6.4.1 ZEAG protocol

The configuration page is shown below:
Fields available:
Basic Settings:
- ZEAG Enable: this parameter takes two possible values: YES or NO. If enabled (YES),
this feature allows the communication with the protocol ZEAG.
(Brescia), Italy..
35-128
VEGA User Guide

- Server port: server port dedicated to receive ZAEG messages.
- Keep alive timeout: keep-alive timeout for maintaining open the communication.
Trigger Settings:
These parameters are managed only by ZEAG application that support communication
protocol 2.0. In addition, the camera must be configured in advance in
"TRIGGER_ETHERNET" mode.
- Previous Trigger (ms): This parameter describes how many milliseconds before the
Ethernet trigger event are dedicated to image processing.
- Post Trigger (ms): This parameter describes how many milliseconds after the Ethernet
trigger event are dedicated to image processing.
In Zeag protocol the full resolution image is always sent, while the cropped image is sent only if
the specific field is enabled.
(Brescia), Italy..
36-128
VEGA User Guide
7.6.4.2 Milestone protocol

The configuration page is shown below:
- Milestone Enable: this parameter takes two possible values: YES or NO. If enabled
(YES), this feature allows the communication with the Milestone Xprotect server.
- Server IP: server IP dedicated to receive analytics events.
- Server port: server port dedicated to receive analytics events.
- Event Name: Name of the analytics event
The Milestone integration uses the Analytics Event of the Xprotect server. In order to manage
this kind of messages you must enable the Analytics Event Server and create a new
Analytics event named Event Name by using server management application.
You can set up the event in Milestone as following:
1) Open XProtect Corporate Management Client.
2) Go to Tools->Options->Analytics Events Settings
3) Click on the Option drop-down menu of Milestone application, after that click on Option
item. Check the checkbox Analytics events to enable receiving events. Choose the
port (ie: 9090). And click on OK to close the window. This is the same port you must
set in Vega configuration.
(Brescia), Italy..
37-128
VEGA User Guide
4) On the main interface, create a new Analytics Events with name VegaEvent.
Therefore, click on the Analytics Events item of the left treeview control by the right
button of the mouse.
This is the same name you have written in the Vega configuration.
(Brescia), Italy..
38-128
VEGA User Guide
5) After creating the analytic event, there is the necessity to create an hardware object
associated with a generic driver Universal Driver (1 channel). You can manage to it
either manually or automatically.
Click on the Hardware Devices item of the left treeview control by the right button of
the mouse.
Its possible manage to it either manually or automatically. (manually)
(Brescia), Italy..
39-128
VEGA User Guide

Its necessary to insert the following parameters:
IP Address
Port (80 as default value)
User Name (superuser as default value)
Password (superuser as default value)
Driver (Universal 1 channel driver as default value)
6) Consequently there will be showed in the Hardware summary section your new Vega
device.
(Brescia), Italy..
40-128
VEGA User Guide
7) In order that Server send to Client information to be displayed is necessary, though,

setting alarm definitions. Click on the Alarm Definitions item of the left treeview control
by the right button of the mouse.
8) Fill in the following parameter:

Enable :
checked.
Name :
Alarm Definition.
Trigger Event : Type Analytic Events, and immediately below Vega Events
(Brescia), Italy..
41-128
VEGA User Guide
9) Press the button Sources and select as a source the hardware you have defined
previously.
10) Finally you have to define the Alarm Data settings. In this section you define what kind
of data will be sent to the client. Click on the Alarm Data settings item of the left
treeview control and move to Alarm List Configuration tabulation page.
(Brescia), Italy..
42-128
VEGA User Guide

11) Select the Available data from the right to left column on the Alarm list Configuration
tabulation page.
12) The XProtect Smart Client can now receive events.

The received event in the Smart Client will appear as in the following mage:
Please note that:

All received data are stored in Milestone database in the format of TCP
Message. Available tags are described in chapter 28.
System integrator is in charge to develop the plugin to extract further data (ie:
image, etc).
(Brescia), Italy..
43-128
VEGA User Guide
You can configure Milestone actions to be executed in case of receiving

VegaEvent.
(Brescia), Italy..
44-128
VEGA User Guide
7.7 Data storage on Secure Digital memory

This action corresponds to the SD Saving column of the matrix. The column is available only if
the Storage SD is detected inside the camera.
Using the WEB pages
Enable: it allows to store data over SD memory. YES means function enabled.
Image Encryption: allows to enable encryption of images. Options available:
1) No encryption
2) AES encryption
Jpeg Quality: specify the image quality to save in the SD memory. The values may range from
1 to 100 where 1 is the maximum compression level (lowest quality) and 100 is the minimum
compression level (highest image quality). Suggested values from 50 to 90.
Crop Image: this setting allows sending to a SD a crop of the full image. Such crop is cut
around the car plate. Available sizes: 320x240, 640x480, 800x600, 1024x768 or PLATE_ONLY
where the cutting is made just around the plate.
networks).
Path Name: It allows to specify the path over the SD where to save data. The first part of the
path is mandatory Date\Hour.
(Brescia), Italy..
45-128
VEGA User Guide

File Name: it allows specifying the name to assign to the vehicle transit image to save.
It is necessary to use appropriate TAGs to indicate this file name.
For example, use the %PLATE TAG in order to insert the read car plate in the name.
date and time.
7.8 Saving text messages to Secure Digital

This action corresponds to the Save DB SD column of the matrix. If enabled, this feature allows
creating and automatically updating a text file on Secure Digital (only on devices which support
it) in CSV format (Comma Separated Values) containing information about every vehicle transit
detected by the Vega plate reader.
Web page:
Path Name: it allows specifying the folder name where the database is saved. It is necessary
to use appropriate TAGs to indicate this folder name. For example, when using %DATE, a
new folder is created each day.
(Brescia), Italy..
46-128
VEGA User Guide

File Name: it allows specifying the name of the database to be updated with the data about
vehicle transit. For example when using %DATE a new file is generated each day. The file
name is the date on that day e.g.: 2008-10-28.
File Extension: specifies the extension of the generated file. For example, if File Name field
contains %DATE and File Extension contains CSV, the resulting file name will be similar to
2008-10-28.CSV. The File Extension field can be left empty.
Fields: it allows specifying the database fields.
Example:
String on web interface:
%DATE%;%TIME%;%PLATE%;%IMAGENAME
CSV file on FTP server:
DATE;TIME;PLATE;IMAGENAME
2007-10-03;09-14-50-222;SA249BH-ITA;SA249BH-ITA_2007-10-03_09-14-50-222.jpg
2007-10-03;09-15-00-569;CH123BV-ITA; CH123BV-ITA_2007-10-03_09-15-00-569.jpg
2007-10-03;09-18-07-234;AF234SV-ITA; AF234SV-ITA_2007-10-03_09-18-07-234.jpg
Save Headers: when this field is set to YES, the system inserts a row containing the list of
fields at the beginning of the file.
7.9 Shared configuration

7.9.1
JPEG header
Configuration of TAGs inserted in the jpeg header. See Chapter 30.4 Jpeg header data for
further information
7.9.2
Default DB fields configuration
Configuration of TAGs that can be applied to the save DB actions. See Chapter 30.3 List of
available TAGs for further information
7.10 Conditional execution

Some actions provide the Conditional execution option. The conditional execution is used by
the camera to execute actions if and only if is verified a specific condition. Following the
conditions available:
ALWAYS: The action is always executed.
BASED_ON_ID: The action is executed if at least one ID logical status is one of the ID
logical status of interest. (See chapter 25, this feature is available only for Vega HD
familys camera)
(Brescia), Italy..
47-128
VEGA User Guide
8 Digital signature on JPEG images

As of firmware version 4.71 included, all JPEG images generated by Vega systems are signed,
both the images saved to FTP and the images sent to TCP-IP socket.
The signature process is meant to embed a digital signature into JPEG images generated by
Tattile machines. Digital signatures allow:
Verifying that an image comes from a Tattile system.
Verifying whether an image has been edited - if so, the authentication process will
fail.
A third party cannot produce correctly signed images even if it knows the procedure for
authenticity verification.
The digital signature is inserted inside the JPEG image header. The digital signature is built
using whole JPEG image processing, header included. The signature algorithm uses an
asymmetric key ciphering. The ciphering key is private, secret and embedded in Vega systems.
To check the authenticity of the signature, a public key is used.
8.1 Standard FIPS-186-2

In order to create a digital signature, several hash and encryption/decryption algorithms are
available. FIPS 186-2 algorithm was used here. For complete specs, please see the fips186-2change1.pdf file - downloadable at:
http://csrc.nist.gov/publications/PubsFIPS.html.
FIPS is the acronym for Federal Information Processing Standard:
http://csrc.nist.gov/publications/fips/index.html.
In this standard, the SHA-1 hash algorithm is used while the encryption algorithm is the DSA
(Digital Sign Algorithm).
Please see: http://en.wikipedia.org/wiki/Digital_Signature_Algorithm for further details on DSA.
(Brescia), Italy..
48-128
VEGA User Guide
8.2 Digital signature on Tattile JPEG images

Digital signature is inserted into JPEG image headers as a string. When opening the JPEG
image in a text editor, it is possible to view the signature string. See red line in the window
below.
S_NETBIOSNAME=_VEGA_8MEGA
I_SN=101777
I_BOARD_FPGA_VER=21
I_BOARD_CODE=243
I_BOARD_REV=3
S_DATE=2008-03-18
S_TIME=09-51-29-471
S_PLATE=SA249BH-ITA
I_NREAD=27
I_JPEG_QUALITY=95
I_GAIN=200
I_SHUTTER=4000
I_STROBO=200
I_SPEED=NA
S_CLASS_STRING=CAR
I_QUALIF_0=NA
I_QUALIF_1=NA
I_OCCUPANCY_TIME=NA
I_GAP_TIME=NA
S_DIRECTION=UNKNOW
S_OCR_CFG=Win:(0,0) (1023,767) Ch:8x15 25x40 Sens:4 SelMode:BEST_LUMINANCE
NumJolly:0 MaxTime:2000
I_PLATE_MIN_X=752
I_PLATE_MIN_Y=433
I_PLATE_MAX_X=877
I_PLATE_MAX_Y=459
S_NET_TRIG_ID=
S_IMAGE_SIGN=302D02141EC0A396910402B4730AEDEB9E0409981BAB0A81021500A9013C58C836
145EF6CFD08126AFF4C99306FDA3
SHA-1 produces a 160-bits digest message that goes through the DSA algorithm and produces
a signature between 46 and 48 bytes long. Such variability is brought about by a random
component entered by the signature algorithm.
Assuming the same image and private signature key are being used, the produced signature
always differs by this random component introduced by the DSA algorithm.
The buffer produced by the DSA algorithm is then translated into an HEX string and inserted in
the JPEG image header, after the red-highlighted S_IMAGE_SIGN TAG, in the window shown
above.
The translation of the signature into an HEX string allows using printable alphanumeric
characters instead of a binary data buffer.
The public key of verification is made available to whoever wants to verify the signature
authenticity.
SHA-1 hash procedure used for digital signature generation includes the image entire JPEG
header, so that any tampering with the JPEG header or image will automatically determine the
signature authentication process failure.
The JPEG image header contains the serial number of the card used to generate the image
(TAG I_SN at the header top). This means the system stems from the hardware whose serial
number is shown in I_SN.
Image signature procedure with Vega systems is as follows:
(Brescia), Italy..
49-128
VEGA User Guide
All space characters, where the signature strings is to be entered, are inserted in the
JPEG image header.
On the entire image, JPEG header included, the digest is calculated.
The signature is calculated over the digest.
The signature is entered in the JPEG header.
(Brescia), Italy..
50-128
VEGA User Guide
8.3 Digital signature verification

To ease the verification of digital signatures, Tattile provides a DSA_VERIFY.dll to use for
signature verification in JPEG images. The private verification key is embedded in the DLL. The
DSA_VERIFY_CONSOLLE.exe describes how this DLL can be used for digital signature
verification purposes.
(Brescia), Italy..
51-128
VEGA User Guide
9 Image encryption
Actions on event allows to encrypt images for better security.
The available methods are the following:
1) Encrypted ZIP file. OBSOLETE.
2) AES128 binary file.
9.1 ZIP encryption

This method is obsolete due to low performances. You could have loss of detections if used.
9.2 AES encryption

If enabled, the generated image buffer is encrypted as following. If saved (via FTP or SD
storage), the file will have the extension aes added. In any case, the received buffer is directly
the output of the encryption procedure, without any extra header.
The AES 128 symmetric key (16byte) is stored encrypted (with Tattile RSA public key) on the
device file system in a file called crypt_key.dat.
The crypt_key.dat buffer can be sent to the camera in one of the following ways:
1) By writing the file crypt_key.dat with VRC command 26002
2) By the write configuration command (VRC 25216)
The RSA Tattile public key is reported here and you can find it on the device by reading the file
tat_pub.pem using the read file VRC command.
-----BEGIN PUBLIC KEY----MIIBIDANBgkqhkiG9w0BAQEFAAOCAQ0AMIIBCAKCAQEAz9o1uEeAFJQh/WDKi+Vj
jW8Cusd/48In1ejK4kRm7l8TL+2pWcp/8maCudGUUPB4SGEjO/KoUfPkaQW1hHlJ
2iZ3hD0RAM0R8wgwQw77tkBYLFLBMsAW+gFar3+waLYqU0CvwSfo/5JXgiYhU9Cq
DB9+JZKqf4GmyFfSBVMX0J8nJV3wPoe+J7NkIzdU/6NGQK5F2ydiV5qcWqpsLywf
pXAJ70fuV42/0IAju6qDDHKbQlVWuNw+5cauELkphbM7e8P3M/tvVsKpnTxZKi05
yv46cEZ4eweuTPL6DWMW1vV00bVHEziracO0tl2Xdllb1aD3rxY48yEBwr1qICFQ
4wIBAw==
-----END PUBLIC KEY-----
9.2.1
How to generate crypt_key.dat
You can generate a custom suitable crypt_key.dat b fllowing the steps below:
1) Get the Tattile RSA public key; bu either doing a VRC read file command (read the file
tat_pub.pem) or using the previously reported public key.
2) Choose a AES key with length of 16bytes (128 bit).
3) Crypt the 16bytes previously chosen with the RSA Tattile public key.
4) Send the binary buffer obtained to the camera by writing it as a file (VRC write file with
name crypt_key.dat), or using the field available in the command VRC 25216.
5) If you uploaded the key by using the file write command, you must reboot the device to
apply the new key. In case of key sent via VRC command 25216, the new key is applied
on the fly.
Example of crypting AES key vith OpenSSL:
openssl rsautl -encrypt -inkey pub_tat.pem -in plainaes.bin -out crypt_key.dat -oaep pubin
Where:
- pub_tat.pem is the RSA Tattile public key.
(Brescia), Italy..
52-128
VEGA User Guide

- plainaes.bin is the input file that contains the 16bytes of the AES key chosen by the
user.
- crypt_key.dat is the newly generated file containing the RSA encrypted AES key. You
must send this file via VRC write file or via VRC write configuration commands.
9.2.2
How to decrypt image buffers
Each image is encrypted with the AES128 key provided by the customer, or if the customer
didnt set any key, the default AES key is the following:
0x00, 0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07,
0x08, 0x09, 0x00, 0x01, 0x02, 0x03, 0x04, 0x05
Please note that the trivial key is available only for demonstration. You should generate one by
your own and upload it to the camera.
The custome should decrypt each image in the following way:
1) AES configuration: AES128 CTR
2) Initialization Vector: all zeros.
Example of decrypting an image sing OpenSSL:
#!/bin/bash
key128="00010203040506070809000102030405"
iv="00000000000000000000000000000000"
openssl enc -d -aes-128-ctr -in AB123CD.jpg.aes -out AB123CD.jpg -K $key128 -iv $iv
(Brescia), Italy..
53-128
VEGA User Guide
10 System enabling and disabling and General Setting

Using the web interface you can disable the system so that no unauthorized operation.
Using the WEB pages
Enable Engine: this parameter takes two possible values: YES or NO. It allows
enabling/disabling the processing of the images grabbed by Vega.
If set to NO, the device is on sort of stand-by and its infrared illuminator is disabled, which
means that any commands from external triggers are ignored.
The infrared illuminator is momentarily enabled only if the OCR Camera page is being
accessed.
Acquisition Mode: it allows selecting the system operating mode. The following values are
selectable:
FREE_RUN
TRIGGER_START_STOP
TRIGGER_START_TIME
TRIGGER_START_FREE_RUN_STOP
(Brescia), Italy..
54-128
VEGA User Guide

TRIGGER_ETHERNET
The acquisition mode will be described in detail in section 10.1.
Warning: Changing the Acquisition Mode parameters causes the machine to
reset. The browser connection will be interrupted.
Site Address: this field can contain an alphanumeric string, such as the address of a system
location. This string is available as %SITE_ADDRESS TAG and can be sued in the Text Value
field of the Save Image action.
TCP message after FTP Actions: with this parameter you can enable (YES) TCP send
message after every FTP actions enabled (FTP save image and FTP save DB).
Maximum fps: the field sets the maximum grabbing frame rate. Use 0 for no limitation.
Enable GPS: Enables the optional GPS connected to the device. It allows to use it for time
synchronization and position detection.
Filter static plates: the field allow to avoid sending transtis if the same plate is detected
multiple times, in example when a vehicle stops in the camera field of view. Please use this
option with care.
TCP timeout (ms): Change this field only if requested by the Tattile support team. Default
value is 10000.
Jpeg Output Colorspace: Allows to choose the OCR image colorspace. Change this field only
if needed. Default value is: 8bpp:
- 8bpp: the output image is encoded as 8bpp jpeg.
- 24bpp: the output image is encoded as 24bpp even if grayscale.
10.1 Operating modes

Prior to describing the different operating modes (Acquisition Mode field of the General
Settings options), lets elaborate briefly on the concept of TRANSIT itself. By transit we mean
that any of the three OCR_READ, OCR_NOT_READ and OCR_NO_PLATE events is being
generated.
A transit event is given by the processing of multiple images of the same vehicle. To execute
the actions described in the Events/Actions page (Save Image to FTP, Send to PNS etc.), a
single image will be used.
Such image is selected based on the criterion defined in the Temporal Integration section in
PlateReader page.
Vega systems can operate in two different modes:
(Brescia), Italy..
55-128
VEGA User Guide
FREE RUN mode

TRIGGER mode
When in FREE RUN mode, Vega freely grabs and processes images. The software
automatically detects the presence of a car plate in the image and thus generates an event. In
FREE RUN mode, the system may generate the following events:
OCR READ
OCR NOT READ
Several TRIGGER modes are available, but the basic principle they work on is similar.
The Vega system receives a start trigger.
Following the start trigger, image grabbing and processing begins.
The Vega system receives a stop trigger and the internal system generated an event.
In TRIGGER mode, the system may generate the following events:
OCR READ
OCR NOT READ
OCR NO PLATE
The NO PLATE event can occur only while in TRIGGER mode since in FREE RUN mode, the
event is generated based on whether a car plate is detected inside the image. In FREE RUN
mode, vehicle not having a car plate generate no event therefore, it is necessary to use either
one of the TRIGGER modes in order to grab images of any vehicle no carrying a car plate.
The time interval between a start and a stop trigger is called Gate Time.
10.1.1 Free Run mode

When in FREE_RUN mode, the unit freely grabs images and non-stop OCR processes them.
The software automatically detects a vehicle transit and generates a transit event for each
vehicle.
10.1.2 Trigger from digital inputs mode

There are three trigger from digital inputs modes:
TRIGGER START STOP
TRIGGER START TIME
TRIGGER START FREE RUN STOP
The digital inputs are defined via the Digital Trigger web page.
When the machine is in Free Run mode, parameters set in the Digital Trigger page are ignored.
Using the WEB pages
(Brescia), Italy..
56-128
VEGA User Guide
The Digital Trigger page contains the following fields:

Enable Median Filter: it allows to enable the median filter on the trigger signal; this function
should be disabled if the camera must catch signal trigger very short and fast (example
vehicles at high speed), instead should enabled for slow and noisy signal trigger (access
control, photocell).
Previous Image ms: allows you to define the time of image processing for a maximum time of
one second before occurring of the Start trigger signal.
Gate Time Max ms: it allows setting the value, in milliseconds, of the maximum period
between start and stop of the trigger. The Gate Time Max value is not relevant when the
machine is in Free Run mode (free grabbing). Its values may range from 40 to 30.000
(equivalent to 30 seconds).
Trigger Time Shift ms: it allows you to set a delay time that is applied to the events of START
and STOP TRIGGER. It may be useful to introduce a delay between the detection of the trigger
event and the beginning of the acquisition and image processing.
Input Num.: it allows setting the number of the digital input associated with the system start
trigger.
(Brescia), Italy..
57-128
VEGA User Guide

Input Edge: it allows setting the signal edge to use as a trigger to start (or stop) (RISE
indicates the rising edge ; FALL indicates the falling edge).
Inactivity Time ms: it outlines the minimum time between two consecutive triggers. If a trigger
is received before this time is expired it will be discarded.
Median Filter size: it allows to set the window size over which the median filter is calcualted.
Can be set from 3 to 91. Default value is 13.
When in TRIGGER_START_STOP mode, the unit grabs and processes the images in the time
period between the start trigger and the stop trigger. Typically, this mode is associated with 2
external sensors that are connected to the Vega system (e.g. photocells, magnetic loops etc.),
which determine the grabbing start and stop mode, respectively. In case the stop trigger is not
being activated within the Gate TimeMax. ms interval, the system firmware automatically
generates the stop trigger when such interval expires. Any stop trigger received prior to a start
trigger will be ignored. Any start trigger received after a start trigger makes the firmware
automatically generate a virtual-stop trigger and initialize a new transit event.
When in TRIGGER_START_TIME mode, the unit starts image grabbing when the start trigger
is activated and stops image grabbing after a time interval that was previously defined in
DIGITAL TRIGGER page, in Gate Time Max. ms (the value is in milliseconds). Once GateTime
has expired, a transit event is generated. If the system receives a start trigger during GateTime
period, it immediately generates a transit event and starts again image processing of the new
transit.
When in TRIGGER_START_FREE_RUN_STOP mode, the unit starts image grabbing when
the start TRIGGER is activated and then starts grabbing and reading car plates in FREE RUN
mode. The system may generate multiple transit events during the interval between start trigger
and stop trigger.
It is possible to use the same digital input as start trigger and stop trigger,
provided that rise and fall edges have different values.
10.1.3 Trigger Ethernet mode

In this mode the unit starts grabbing images upon receiving the start TRIGGER message from
the Ethernet network.
The VRC protocol describes how the trigger command must be formatted.
The start trigger message contains a precise time in milliseconds that expresses the GateTime
during which the machine is to grab images. When GateTime expires or upon receiving a stop
trigger message, the machine stops image grabbing.
The trigger message also contains a generic string (TriggerIdString) the system uses to
generate trigger messages where info may be inserted. Such string will later made available on
(Brescia), Italy..
58-128
VEGA User Guide

the web interface using the %NET_TRIG_ID TAG. This makes it possible to associate to any
transit data and images other info about the specific trigger message from which they were
originated.
Trigger messages are relevant when the machine is in TRIGGER_ETHERNET mode. If these
messages are sent when the Vega machine is in other operating mode, VRC server answers
with an error. For more details please refer to the VRC protocol description.
(Brescia), Italy..
59-128
VEGA User Guide
11 Image grabbing
The live image page shows the image captured from the sensor. If the web page is open, the
system will not trigger any vehicle and it will not generate actions.
After 120 the live image will automatically stop.
Using the WEB pages
The left side area of this page displays live video images generated by the Vega machine
(see figure).
(Brescia), Italy..
60-128
VEGA User Guide

The red rectangle on the image border represents the search plate window. It is possible to set
size and position of this window in PlateReader page, section PlateLocator".
The right side area contains the following fields:
General:
Grab Mode: in this section, it is possible to set the image-grabbing mode: AUTOIRIS,
SINGLE_POINT or MULTI_POINT.
Info Position: in this section it is possible to specify, inside the live image, the position of the
OCR reading results and the units work parameters.
The allowed values are: TOP_LEFT, TOP_RIGHT, BOTTOM_LEFT_BOTTOM_RIGHT and
DISABLED.
Image Mode: in this section it possible to see an enlargement of the central area of the image.
The allowed values are: NORMAL and CENTRED ZOOM.
Autoiris:
The Autoiris mode allow the camera to automatically calculate and set the best acquisition
parameters (shutter time, strobo time, gain).
Autoiris mode allows the automatic adaptive grabbing parameters to be set during the whole
day. This is the preferred working mode that should give the best performances.
The following configurable parameters are available. Please be careful when changing these
parameters.
Iris level: desired brightness level (values 0-100). Advised 25.
Min Shutter us: Minimum electronic exposure time. The minimum value permitted is
3uS.
Max Shutter us: Maximum electronic exposure time (maximum is 10000uS). If this value
is high, the grabbing frame rate of the device decreases. Advised 1000uS.
Min Gain: minimum gain. The minimum value is 3.
Max Gain: maximum gain (max 512). High gain values lead to high noise images.
Single Point:
In this section it is possible to set the parameters to use in SINGLE_POINT grabbing mode.
In this mode all the images are captured using the parameters:
Gain: it indicates the gain of the video signal.
Shutter us: it indicates the exposure time in microseconds.
Strobo us: activation time of the infrared illuminator.
(Brescia), Italy..
61-128
VEGA User Guide

This mode is used for system testing purposes and should not be used for standard operating.
Multi point:
In this section, it is possible to set the parameters to use in the MULTI_POINT grabbing mode.
Image-grabbing cyclically uses the following:
Gain0-Shutter0
Gain1-Shutter1
Gain2-Shutter2
Gain3-Shutter3
This mode is recommended for all installations with firmware version lower than 4.79.
The Save Image button allows saving an image for each work point. It is very useful for
evaluating the system work points.
The first work point Gain0-Shutter0 and the last one Gain3-Shutter3 are dynamically included
and excluded using a software command that works based on current light variances. This
allows for system optimization because info less images (i.e. images either too dark or
saturated) will not be processed.
Set values must be steady crescent which means that the Gain3>Gain2>Gain1>Gain0 and
Shutter3> Shutter 2> Shutter 1> Shutter 0 criterion must be always met. The commands in the
web page do not allow entering values that do not comply with such requirement.
In the page bottom, the following function buttons are available:
Focus:
Focus: this field enables the focus tool. You can use this tool while setting the camera focus.
Management page buttons:
Start Live: it allows starting live video

Stop Live: it allows stopping live video
(Brescia), Italy..
62-128
VEGA User Guide

Reset: press this button to cancel values that have been already typed in but not confirmed yet
using the Apply button.
Apply: use this button to implement the changes entered in this page.
Save image:
The Save Image button allows saving (Jpeg format) the image currently
displayed. The image is saved with the natural resolution of the image sensor.
Warning: engine is stopped if live video images are displayed in the OCR Camera
page and this means no event is available. Processing is automatically reactivated
upon exit from the OCR Camera page.
(Brescia), Italy..
63-128
VEGA User Guide
12 OCR configuration
The Vega system is capable of real time OCR processing grabbed images. Up to 32 countries
car plates can be simultaneously read.
It is necessary to update the Vega software if the user wants to change the countries the Vega
system has to read.
To view the countries the Vega system is capable of reading, please access the web server
and click the DeviceInfo icon: go to the line that shows the firmware version.
Example 1:
Firmware version
= VEGA LPR 4.97 ITA
Example 2:
Firmware version
= VEGA ACCESS 8.131.5 ITA-EU
Different installing pack are created directly by Tattile under request from customers. For
instance, for Europe is created an install pack where all 27 EU countries are included, but with
different priority levels:
For example an installation in Italy:
HIGH PRIORITY: ITA (country where the camera is installed)
MEDIUM PRIORITY: FRA, DEU, CHE, SVN, AUT (border countries)
LOW PRIORITY: all other EU countries.
12.1 Configuring the OCR parameters

This page allows to configure the Plate Reader paramters.
Using the WEB pages
(Brescia), Italy..
64-128
VEGA User Guide
Plate Locator:
Sensitivity: the allowed values are NORMAL, HIGH, AUTO. The higher the Sensitivity the
higher the sensitivity of the car plate search algorithm. Please dont modify these parameter
unless explicitly told by a Tattile operator.
It is recommended to avoid higher sensitivity values unless these are absolutely necessary:
high values may cause longer calculations with an overall lower system performance.
The default value is NORMAL.
Char Size Pixel:

These parameters represent the size of the plate characters the OCR video camera is to
recognize.
(Brescia), Italy..
65-128
VEGA User Guide

The minimum value represents the minimal threshold for recognition. Below this
threshold, OCR will NOT recognize the characters found as valid. The maximum
value represents the maximal threshold for recognition. Above this threshold,
OCR will NOT recognize the characters found as valid
These maximum and minimum character sizes should be empirically set upon installation, in
order to check whether the OCR recognizes the car plate characters.
Min Width: this is the plate character minimum width, in pixels.
Max Width: this is the plate character maximum width, in pixels.
Min Height: this is the plate character minimum height, in pixels.
Max Height: this is the plate character maximum height, in pixels.
Plate Format:
Max Jolly Char: this feature allows setting the maximum number of plate characters the Vega
machine OCR is allowed not to recognize within the car plate. If set to 0 (zero), the reading is
valid only if the Vega machine recognizes every character of the number plate. If set 1 or 2
(maximum value), the Vega machine will take as valid the reading obtained and the result will
include one or two Jolly characters represented by the # symbol placed instead of the
unrecognized characters. Car plate reading with jolly characters generates an OCR_READ
event.
Plate With Separator: allows to enable (YES) inserting a character _ between group of
character found by OCR into plate string. If enabled it will be put _ between group of char only
for German plates (DEU).
Enable UTF8 Encode: it allows to decode the string of characters using UTF8 coding. Without
this function enabled the string is coded as ASCII (8 bit).
Example: UTF8 allows to shows Arabic characters and umlaut characters (, , ).
UTF8 is present in following data:
File name and directory over FTP saving
File name ,directory and content of CSV file saved in FTP
Data over Serial ports RS232 - 485
TCP Message
UTF8 is not present in the web pages data like as Camera OCR, Image Result and in SD data
saving.
Temporal Integration:
(Brescia), Italy..
66-128
VEGA User Guide

The Vega system processes multiple images for each vehicle, which allows for higher OCR
reading effectiveness and reliability. Section Temporal Integration contains the parameters for
managing the whole packet of processed images for each single transit event.
Max Time Transit ms: this parameter is relevant only in FREE-RUN mode. This is the
maximum time period allowed for any transit. Lets suppose this parameter is set to 1000ms. If
the Vega system reads the car plate once, it still waits 1000ms before generating a transit
event. During such time, the system keeps grabbing and processing images of the same
vehicle whose car plate was read. This allows for a highly reliable car plate reading process.
During this same interval, the system may detect a vehicle with a different car plate number:
such new transit event is immediately generated (no waiting for the 1000ms interval to expire)
and the images subsequently acquired and processed must be related to as belonging to the
new transit event.
Setting a too low MaxTimeTransit value means less images are processed for the same
vehicle, which leads to lower reliability in OCR reading.
Therefore, MaxTimeTransit value should be set to the highest possible value while of course
complying with the specific installation requirements.
The Min Time Same Plate ms and Enable Multi Out Same Plate function fields are strictly
related.
Min Time Same Plate ms: it indicates two different things, depending on the value of the
Enable Multi Out Same Plate parameter.
Meanings:
1) Enable Multi Out Same Plate is set to 0 (zero):
It represents the minimum length of time during which the camera will not create a transit event
even if the number plate has been already recognized. In other words, for this length of time a
previously recognized plate does not need be in the Vega field of action in order to generate
another transit event. If the vehicle remains in the Vega field of action, the same plate
recognition event is generated only once.
This configuration is useful when monitoring traffic along free-circulation roads: in

case of queue, a single image for each vehicle is grabbed
2) Enable Multi Out Same Plate is set to 1 (one):

It represents the length of time that must elapse for generating a new transit event associated
with a plate already recognized in the previous transit.
In this case, a vehicle that remains within the camera field of action will generate a transit event
every Min Time Same Plate.
Time is expressed in milliseconds. Typical values are: a few minutes in the first case described
(120000 ms) and a few seconds for motorized barrier configurations (5000 ms).
(Brescia), Italy..
67-128
VEGA User Guide
Enabling this parameter may be helpful with motorized barrier gates as the transit event is likely
to be periodically sent when a vehicle is standing in front of the barrier while waiting.
For example, in LTZ implementations this parameter should be disabled, so that any vehicle
parked inside the camera frame view does not continuously generates a transit event.
Max Plates In Image: it specifies the maximum number of plates to be recognized in an image.
Use a value greater than 1 in case of a two lanes installation layout (Vega HD, 2HD).
Image Selection Mode: it indicates the selection mode of the image containing the recognized
plate associated with the transit. The possible values are:
BEST_LUMINANCE: best average luminance in the car plate area. This is the default mode
for transit image selection.
CENTERED POSITION: the selected image is the one with the plate as close as possible to
the image center.
HIGHEST POSITON: the selected image is the one with the plate as close as possible to
the top of image.
LOWEST POSITON: the selected image is the one with the plate as close as possible to the
bottom of image.
LOWEST POSITION_BEST_ILLUMINANCE: the selected image is the one with the plate
as close as possible to the bottom of image, but with the highest luminance.
LOWEST ILLUMINANCE: the selected image is the one with the lowest luminance.
Min Num Plate Read: minimum number of read images to validate a transit. Its applied to
READ and NOT READ. The allowed values are 1 to 3 and is used only in FREE RUN mode.
This filter is useful for avoiding false readings caused b patterns that may confuse the camera.
Apply Min Num Read To: the type of transit that the Min num plate read is applied to.
Min Plate Score for Num Read=1: minimum recognition score which prevents the filtering of
the transits with a number of reads less than Min Num Read.
Advanced features:
Enable Kemler Codes (ADR) Recognition: enables the recognition of the ADR Kemler codes.
This parameter can be set only if the OCR library for ADR is loaded on the camera.
Join Special Plates in a Single Result: enables the association of the standard plates and
special plates (ADR, trailer plates) into a single result. For example, when a truck with a
standard plate and a trailer plate is detected by the system, only a single event with the two
(Brescia), Italy..
68-128
VEGA User Guide

plates will be generated. Otherwise, if the association is disabled, two events with the two
plates are generated.
Enable Vehicle Classification: enables the vehicle classification based on the analysis of the
reflective panels on the vehicle. This is a more complete classification for trucks or buses
based also on other elements than the plate.
Warning: enabling this functionality could slow down the system. Use only
if needed.
(Brescia), Italy..
69-128
VEGA User Guide
12.2 Lane Config

The icon to access this configuration page is as follows:
The configuration of the lanes is used to assign the correct identification at each transit lane.
This assignment is useful in the case in which there are external detectors speed which assign
speed and / or class of the vehicle in transit and also to know which lane has generated transit
in the case of the acquisition mode has been set to TRIGGER_INTERNAL.
The following position Fields are expressed in percentage of the width / height of the image,
and you can set positive and negative values in order to align the lane lines to the current
configuration of the road.
Using WEB Page (Normal):
(Brescia), Italy..
70-128
VEGA User Guide

This section specifies the coordinates of the search area of the plate within the image. The
search area is displayed with a red rectangle on the image of the live video page Ocr Camera.
The possibility to set the search area allows to exclude from some parts of the image. This can
be useful to exclude areas of the image where there can never be a license plate or to exclude
areas in which the reading of the plate should not be performed and in this way speed up the
image processing.
Win MinX Pixel: Represents the X coordinate of the upper-left corner of the search area of
the plate within the image (see figure)
Win MinY Pixel: Represents the Y coordinate of the upper-left corner of the search area of
the plate within the image (see figure)
Win MaxX Pixel: Represents the X coordinate of the lower-right corner of the search area
of the plate within the image (see figure)
Win MaxY Pixel: Represents the Y coordinate of the lower-right corner of the search area
of the plate within the image (see figure)
(Brescia), Italy..
71-128
VEGA User Guide
Using WEB Page (Advanced):

This feature is not implemented on Vega Access models.
Vertical limits:
Upper and lower limits of the license plate search:
Top line: upper limit (In the top line red).
Bottom line: lower limit (In the lower line red).
Lanes:
Configurable number of lanes. Currently are managed as two lanes.
Lane 1 (Green):
Configuring the lane 1, in the image corresponds to the green lane.
Top left: Top left corner of the lane
Top right: The upper right corner of the lane
Bottom left: Lower-left corner of the lane
Bottom right: Lower right corner of the lane
(Brescia), Italy..
72-128
VEGA User Guide
Lane 2 (Blue):
Configuring the lane 2, in the image corresponds to the blue lane. For a description of the fields
used in this section refer to the equivalent fields described in the section on lane 1.
(Brescia), Italy..
73-128
VEGA User Guide
12.3 Last transit image

It is possible to show the image the last detected vehicle.
This page displays image and grabbing data of the last detected vehicle transit. The page is
automatically and periodically reloaded so it is possible to keep open and view in real time the
system results. Since the page is periodically being reloaded, it might happen that not all
system-detected vehicle transits are displayed. So it happens that with heavy traffic, the refresh
period is not capable of showing vehicles that actually transited.
Using the WEB pages
The page contains the image and grabbing data of the last detected vehicle transit.
Next to the image of the transit, the following data are displayed:
PLATE: car plate associated with the transit event.
COUNTRY: three-character string indicating the plate country of origin.
N. READ: number of images containing the read plate.
(Brescia), Italy..
74-128
VEGA User Guide

SCORE: reading confidence.
CHAR WIDTH: the width of the character, in pixels.
CHAR HEIGHT: the height of the character, in pixels.
SHUTTER: the exposure time, in microseconds, used for image grabbing.
STROBO: the time period of activity, in microseconds, of the infrared illuminator during
image grabbing.
GAIN: the gain used for image grabbing.
AI LEVEL: average luminance in the image.
TIME: the image grabbing time.
DATE: the image grabbing date.
Keep visualization of: the user can specify the image to be displayed in the window. The
available options are: READ (plates that were read) and NOTREAD_NOPLATE (plates that
have not been read or images containing no plate).
(Brescia), Italy..
75-128
VEGA User Guide
13 OCR reading text results

This page shows the last 20 transits detected.
Using the WEB pages
The last row in the text page reads as follows:

08/05/2012
Date (DD/MM/YYYY)
19:26:27:887
Hour (hh:mm:ss:mmm)
DL477JB
Vehicle Car Plate Number
ITA
Car plate Country of Origin
(5)
Number of lectures
Acq()
Acquisition parameters (shutter, strobo, gain, grab point, iris level)
(Brescia), Italy..
76-128
VEGA User Guide
14 OCR reading statistics

The page shows the plate reading statistics in the last 24 hours.
Using the WEB pages
These values are useful when installing and optimizing the Vega machine.
The upper part of the OCR Statistics image contains the percentage of the transits that have been
recognized as READ, NOT READ or NO PLATE.
The lower part, Frame Grabber Point Statistics, contains the percentage of readings for the 3
different points of image grabbing.
This allows viewing, at any time of the day, how many transits have been detected as well as what
grabbing points were used in order to save the images.
Using this information, the User can evaluate whether the grabbing settings used are correct and
consistent and calculate the transit recognition rate.
(Brescia), Italy..
77-128
VEGA User Guide
15 Using car plate lists

The page allows to configure the white/black lists.
Using the WEB pages
Select either Check List A or Check List B.

List A and List B setups are identical. For practical reasons, the description that follows relates
to List A only. The Check List A page contains the following fields:
Using the WEB pages
The car plate checklist can be stored either on the Flash memory of the Vega machine or on a
remote FTP server.
The checklist is loaded to the Vega unit RAM memory:
upon system startup
pressing the Reload List button (after the new list is changed)
(Brescia), Italy..
78-128
VEGA User Guide

enabling auto-reload periodic of period Reload period (s)
It is possible to modify and update in real time the car plate lists located in the FTP server or in
the Flash memory of the Vega unit.
The file that contains the car plate lists (List A and List B) must comply with the following
syntax:
Vehicle car plate; Country of origin; Comment string
The system will ignore any irrelevant spaces.

The ; (semi-colon) sign must be used to separate fields
To represent the Country of Origin three CAPITAL LETTERS must be used or three ###
can be used to mean any country. The standard used for the country is ISO 3166-1
alpha-3.
Example:
AB134HK;ITA; Test
BS46588;###; Substitute car
RS054HG;ITA; Presidents car
N.B.: in order for the last row of the file to be loaded too, a carriage return key must be
typed at the end of the line!
The comment string maximum length is 64 characters. Longer comment strings will be
truncated.
The maximum list files size is not defined. This size varies depending on car plate/comments
length.
Please refer to 31 Appendix D: for list of countries.
General FTP Server:

Enable: it enables the use of the checklist.
List Location: it allows setting the position of the lists in the available memories (internal or
external). When in FTP mode, the Vega unit is to refer to a plate list residing on an external
server. When in FFS (Flash File System) mode, the plate list is to be loaded into the Vega
Flash memory.
Auto reload: it allows to reload automatically the list; the period is indicated in Reload period.
Reload period (s): period in second for reloading the list automatically.
(Brescia), Italy..
79-128
VEGA User Guide

File Name: it allows setting the name of the first list of car plates. The file name and its
extension must correspond to the file name residing on the server.
FTP IP: the FTP server IP address.
FTP Password: the password of the FTP server user.
FFS (Camera Flash File System):

Upload List: the Upload List feature allows sending to the Vega unit the car list previously
selected using the Choose file button.
Download List: the Download List feature allows downloading from the Vega machine the
car plate list (as .TXT file). Such list is read by Vega RAM memory.
(Brescia), Italy..
80-128
VEGA User Guide
16 Color context camera

The page allows to configure the overview camera. Supported cameras:
Integrated (second color channel) in Tattile device
External device (Tattile or other vendors)
16.1 Double heads camera (2H)

With the Vega 2H double heads camera is possible to set some parameters about the
grabbing.
Using the WEB pages
This page is available only on Vega number plate readers. For a description of models with
embedded context camera, please refer to the Installation guide.
(Brescia), Italy..
81-128
VEGA User Guide

The context camera is used to grab a color image that matches the black/white image taken by
the machine head used for reading the car plate. When the context camera is active (Enable
Engine: YES), upon car transit the corresponding color image is automatically saved to the FTP
server (see paragraph Save Image to FTP server) and add the color image to the data packet
sent to TCP/IP socket (see paragraph Send Message to TCP/IP Socket).
The color context image name differs from the car plate b/w image name by the _CTX
character sequence at the end of the file name.
Below the description of the parameters available on web page.
General:
Enable Engine: Its possible values are either YES or NO. It enables or disables the processing
of images grabbed by the context camera. When set to NO, the context camera is disabled and
images are not available for system actions/events.
Grab Mode: in this section it is possible to set the image-grabbing mode. The available modes
are: SINGLE_POINT or AUTOIRIS.
The context camera operating mode should be Autoiris. The single-point mode is
available for setting up the Autoiris mode parameters purposes.
Info Position: in this section it is possible to specify inside the live image, where the overlay of
the grabbing parameters (gain and exposure time) will be positioned.
Histogram stretch: histogram stretching.
Binning: Allows to reduce image resolution for increasing brightness. In automatic mode, the
camera will decide by itself how much binning to use.
Image Mode: Allows zoom 1:1 centered on image center. Useful for focusing camera.
White Balance: white balance control.
Max Color Gain: the maximum gain of the color.
Single Point:
In this section, it is possible to set the parameters to use in SINGLE_POINT grabbing mode.
When using this mode, each image grabbing uses the following parameters:
Gain: it indicates the gain.
(Brescia), Italy..
82-128
VEGA User Guide
Shutter us: it indicates the exposure time in microseconds.
Autoiris:
When in Autoiris mode, the system automatically adjusts the grabbing parameters based on
external lighting condition so as to keep a stable image luminance.
The following fields are available for managing these parameter variance limits:
Iris level: it indicates the level of image brightness. The allowed values range from 1 to
100. Set a higher value to brighten the image or a lower value to make it darker.
Min Gain: it indicates the minimum gain value allowed to use in the Autoiris algorithm.
Max Gain: it indicates the maximum gain value allowed to use in the Autoiris algorithm.
Min Shutter us: it indicates the minimum shutter value allowed to use in the Autoiris
algorithm.
Max Shutter us: it indicates the maximum shutter value allowed to use in the Autoiris
algorithm.
In the page bottom, the following function buttons are available:
Focus:
Focus: allow to enter the focusing mode in the selected region.
Management page buttons:
Start Live: it allows starting live video

Stop Live: it allows stopping live video
Reset: press this button to cancel values that have been already typed in but not confirmed yet
using the Apply button.
Apply: use this button to implement the changes entered in this page.
Save image:
(Brescia), Italy..
83-128
VEGA User Guide
The Save Image button allows saving (Jpeg format) the image currently displayed. The image
is saved with the natural resolution of the image sensor.
Warning: engine is stopped if live video images are displayed on the Context
Camera page and this means no event is available. Processing is automatically
reactivated upon exit from the Context camera page.
16.2 External context camera

External context camera can be a Tattile camera or a standard IP camera which supports an
images request by http commands. (Some external context camera tested are by Axis or
Sony).
Enabling the context camera function give as result a context image associated to the BW
image of the plate read.
Please remember that external camera could decrease performances due to the
delays related to request and image management. This could lead to transit lost
or missing overview images.
The configuration web page is always Camera Context.
Using the WEB pages
Enable: it allows to enable the request to external context IP camera

(Brescia), Italy..
84-128
VEGA User Guide

IP Address: Vega Network Context IP
Protocol:
- STANDARD means that the external camera is a Tattile camera (Vega Network Context);
- HTTP means that the external camera is a generic IP camera.
Packet Timeout (ms): timeout in receiving data packets over the network. Dont modify this
parameter unless explicitly requested by Tattile operator.
Request mode: specifies when the overview image must be requested by the device in
reationship with the vehicle transit detection.
- TRANSIT END: overview image request at end of transit. The overview image is
requested to the remote device only if the transit will be generated. In this case the
image is requested at the end of the vehicle transit management.
- TRANSIT START: overview image is requested whenever a new transit is detected. This
mean that the image will be closer to the start of vehicle transit in the field of view. In
case of false or wrong detection, this working mode could lead to high camera load and
could decread performances.
HTTP String: must be filled with the http command used to get the image from the external
camera.
HTTP Authorization: enable, if needed, the access to web of external camera by
authorization.
HTTP Username: username (only if HTTP Authorization is enabled).
HTTP Password: password (only if HTTP Authorization is enabled).
(Brescia), Italy..
85-128
VEGA User Guide
17 GPS
The GPS unit can be enabled setting the field Enable GPS to YES in the General settings
page. Changes to this value require a reboot of the camera.
After setting the value to YES, its possible to display the data detected by the GPS unit in the
GPS page, which shows the geographic coordinates, date, time, and the number of visible
satellites. In addition, the page allows to turn off and on the GPS using the GPS OFF and GPS
ON buttons.
Note:
- The GPS unit is available only on models which support it.
(Brescia), Italy..
86-128
VEGA User Guide
(Brescia), Italy..
87-128
VEGA User Guide
18 Secure digital memory

Some Vega family models come with optional Secure Digital (SD) memory. Please refer to the
product Installation Guide to check for which models this support is available
SD memory management is entirely automatic and transparent by the Vega firmware, apart
manual formatting allowed in this page.
Using the WEB pages
In this page is possible to:

Check how many queued events needs to be sent due to failure in sending. This is the so
called Buffering partition.
Check which is the oldest and the newest inserted event.
Format the partitions. You cannot modify partitions size.
Change the ftp parameters to access the Storage partition.
(Brescia), Italy..
88-128
VEGA User Guide

Event buffering (in the Buffering partition) is performed only when the first attempt to send the
event fails and the action is configured to use buffering. The buffered actions are those that
must be sent via Ethernet (TCP message, FTP send, Gate Master event).
Before sending the image, the event/action matrix is checked. If the action is enabled, the
image will be sent while if disabled, the image will be deleted. In general, whenever actionrelated data are retrieved from the SD memory, the relevant action parameters that were set
via web page are always checked first so that the action is executed according to these setting.
NOTE: Lets assume for example that when saving the image to SD, the FTP server IP is
192.168.0.100. If upon reading the image from SD the server IP is 192.168.0.200, then the
image will be sent to this IP address.
(Brescia), Italy..
89-128
VEGA User Guide
19 Network interface configuration

This web page allows to set the network configuration and date-time, with the possibility of time
synchronization via time server (SNTP, PTP) or GPS module (it depends on the Vega System).
By default, the camera works with local time. The dates contained in all fields of action are
expressed in local time.
If you need to operate in UTC time you can turn off options "GMT Offset min" and "Adjust clock
for daylight saving changes".
Please note that the TAGs UTC_DATE and UTC_TIME always contains GMT time.
Warning: changing any parameter in Network Setting page causes the machine
to reset. The browser connection will be interrupted.
Using the WEB page
(Brescia), Italy..
90-128
VEGA User Guide
Network:
NetBiosName: it allows setting the name of the Vega machine. It is possible to enter
alphanumeric values in this field. Spaces must be represented by _ (underscore).
Ip Address: it allows setting the IP address of the Vega machine.
NetMask: it allows setting the network netmask.
Gateway: it allows setting the gateway IP address.
DNS server: it allows setting the IP address of the DNS.
DhcpEnable: it allows enabling/disabling automatic acquisition of IP addresses.
Time Server:
In the Time Server section of Vega device there are three ways of time synchronization:
a. SNTP synchronization via NTP server.
b. PTP: synchronization via IEEE1588 protocol v1.
c. GPS: synchronization via GPS module.
Synchronize: this feature enables/disables the synchronization to an external timeserver. Its

possible values are either YES or NO.
Protocol: This field can get the following options:
a) SNTP: synchronization via NTP server.
Vega Device uses SNTP (Simple Network Time Protocol) for synchronization with a
remote time server. To configure the Server / PC that serves as a reference clock, see
section "19.2 Activating a time server on a Windows PC".
b) PTP: synchronization via IEEE1588 protocol v1.
The "Precision Time Protocol" allows a continuous synchronization and better precision
compared with SNTP.
Please note that PTP on Vega devices is not based on dedicated hardware.
c) GPS: synchronization via GPS module.
This option is valid only if the GPS module is present and enabled on the device. If this
module is not present the system indicates that it is not possible to synchronize the
time with the message "Status Time Synchro = NOT READY" on the Web page "Device
Informations".
(Brescia), Italy..
91-128
VEGA User Guide

Ip Address: it indicates the IP address of the Time Server or PTP master unit that the Vega
machine uses as reference when synchronizing its internal clock.
GMT Offset min: it indicates the minutes to be added to the time received from the server, in
order to offset between Greenwich Mean Time (prime meridian) and local time. This value is
expressed in minutes and can be negative.
See http://www.greenwichmeantime.com for further details on time zones for different
countries around the world.
Automatically adjust clock for daylight saving changes: allows the daylight saving time
management. If enabled, the device will automatically switch between daylight saving time on
and off when needed.
Manual set of date and time:
In case is not possible to keep synchronized the camera with NTP protocol, is possible to set
manually the date and time. The system will work with the internal clock.
Read date: reads the current date and time from the device.
19.1 Check syncronization

The Sys Statistics page contains statistics about synchronization with the SNTP server.
=================================================
TIME SERVER SYNCRO
=================================================
Time Difference
= -438.0 / -59.8 / 85.0 (stdDev: 191.0) ms
Syncro Update type = Trimmer: 5 Set: 0 Errors: 0
(Brescia), Italy..
92-128
VEGA User Guide

Last Clock Offset
= 12.0ms
The reported information allows to detect if there were synchronization errors, minimum /
average / maximum error, and the last synchronization offset.
19.2 Activating a time server on Windows PC

For activating NTP server service on Windows Computers follow the instruction below:
Windows XP:
Open Service windows (Control Panel\Administration tools\Services).
Stop the service Windows Time if it is running.
From editor register (REGEDIT) go to path
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\W32Time\Time
Providers\NtpServer.
Set parameter Enabled to value 1.
Enable again the service Windows Time.
Verify that firewall do not block packet towards port UDP 123.
Windows 7:
Open Service windows (Control Panel\Administration tools\Services)
Stop the service Windows Time if it is running.
From editor register (REGEDIT) go to path
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\W32Time.
Go to Config and set AnnounceFlags = 5.
Go to \TimeProviders\NtpServer.
Set parameter Enabled to value 1.
Enable again the service Windows Time.
Verify that firewall do not block packet towards port UDP 123.
(Brescia), Italy..
93-128
VEGA User Guide
20 Managing web server users

The HTTP Users page contains the configuration settings of the users who access the unit via
a browser. In this section, the User is allowed to enter and update the Username and Password
codes of the Super user, Administrator and Operator categories.
Using the WEB pages
Access to HTTP Users page is granted to the Super User only, who is allowed to enable,
disable or delete users or to assign new passwords.
Server Port: porta su cui viene aperto il server http. Il valore di default 80.
The Super User has the rights to modify any Vega operational parameters.
The Administrator user has the rights to modify any Vega operational parameters but is not
allowed to access the HTTP Users page.
(Brescia), Italy..
94-128
VEGA User Guide
The Guest is only allowed to view the system parameters, except for the HTTP Users page.
The system can be assigned up to 10 Administrator / Guest users and one only Super user.
(Brescia), Italy..
95-128
VEGA User Guide
21 Trace and Log messages

It is possible to save to FTP Vega internal temperature and traces/errors generated during
operating.
Log files can slow down the normal operation of the system.
Please avoid to use them when not needed!
It is possible to set 3 different levels of log (Log level):
ERR: only errors are traced

WARN: it traces error and warnings
INFO: it traces error, warnings and useful info

Logs can be stored on local SD, if the device supports it, and sent via FTP.
Using the WEB pages
(Brescia), Italy..
96-128
VEGA User Guide
22 Firmware update
The page allows to upgrade the whole system:
- Firmware
- Fpga
- Web pages
- Configuration files
To upgrade the firmware you need the installpack file released by Tattile.
Each installpack may contain the fpga.
Please be careful when upgrading firmware!

Wrong firmware or a power loss may result in a device unrecoverable
error.
There are 3 types of firmware installpack:
- Vega old series (Vega 2, Vega Plus, Vega 2H)
- Vega Access, Vega III
- Vega HD, Vega 2HD
Each type is identified by the name of the installpack:
Vega old series
2012-05-10_VegaLprEngine_v8.132.3_ITA-EU.bin
Vega Access/Vega III
2012-05-10_VegaImx51LprEngine_v8.132.3_ITA-EU.bin
Vega HD/Vega 2HD
2012-05-10_VegaHdLprEngine_v8.132.3_ITA-EU.bin
2012-05-10_VegaHdLprEngine_v8.132.3_ITA-EU_fpga23.bin
In case of upgrading from old Vega firmwares (before version 7), you should
use the Neutral installpack. This installpack is available in the download
area of tattile FTP support.
Using the WEB pages

(Brescia), Italy..
97-128
VEGA User Guide
Four updating methods are available:

Upgrade firmware keeping current settings: in this section, the update is carried out without
changing the previously configured parameters.
Press the Browse button and select the update file from the PC file list. Once this file has been
selected, press the Upload button and confirm the operation. When update completes, the
User is asked to reboot the Vega machine by pressing the Reset button displayed on screen.
Upgrade firmware with default settings: in this section, the upgrade is carried out by deleting
all user-defined parameters and reloading the default settings of the new .BIN file just loaded
using the Browse and Upload command sequence. This procedure is the same as the one
previously described.
Upgrade FPGA and firmware keeping current settings: only for cameras with FPGA, this
mode it allows to upgrade FPGA version and firmware, maintaining the current settings.
Upgrade FPGA and firmware with default settings: only for cameras with FPGA, this mode
it allows to upgrade FPGA version and firmware, with the default settings of the machine.
We recommend using the Internet Explorer or Google Chrome browsers when
updating the software. Using other browsers, the updating procedure does not
work and causes problems with Vega software.
(Brescia), Italy..
98-128
VEGA User Guide

During update it is very important to make sure the camera is not powered off.
Please do NOT close the http connection until the download operation is
completed.
The software update never changes the Network Interface Settings.
Download firmware and settings procedure: press the download button to save to PC a .bin
file containing the Vega firmware and all its user-defined parameters.
This feature is very useful when duplicating the same configuration onto another device or
keeping the file for backup purposes. The .bin file can be directly loaded to a Vega system,
using either of the available upgrade options.
(Brescia), Italy..
99-128
VEGA User Guide
23 Installation layout and diagnostic configuration

The diagnostic configuration page allows to set working limits on Vega Access, Vega III, Vega
HD / 2HD. State variables you can configure are the following:
Camera tilt and roll
Temperature and humidity range
Current absorption
The values stored in this page are used for generating diagnostic alarms.
Using the WEB pages
(Brescia), Italy..
100-128
VEGA User Guide

Installation parameters
These configuration will be used by the diagnostic procedure in order to send information about
malfunction or warning situation. These information are also used to evaluate the speed of a
detected vehicle if this feature is available on board this device.
If the layout configuration is not available for a device a Not supported message will be
displayed on the web page.
Working limits
These configuration will be used by the diagnostic procedure in order to send information about
malfunction or warning situation.
Diagnostic message handling
In this section is possible to configure the behaviour of the diagnostic messages that can be
enabled using the event action configuration web page. (See chapter 24 for further information
about the diagnostics status).
Message repeat time (min): Delay in minutes between a diagnostic status not OK
message and the next one. (If 0 will be sent just the first diagnostic message)
Generate warning messages: Enable also the diagnostic WARNING messages.
Generate end of alarm messages: Enable the diagnostic messages sent from the
camera once the diagnostic status goes back to OK.
Generate period message: It allows periodically the "system diagnostic" action in any
device status. In this way it is possible to generate a periodic action of keeplive period
which is configurable through the field "Message repeat time [min]".
Manage configuration status: Enable the diagnostic status CONFIG.
It enables the status notification "CONFIG" of the camera. the camera goes to
"CONFIG" status when making act of configuration via web interface or command VRC.
The camera remains in this state for the next 2 minutes after the last configuration
command received.
(Brescia), Italy..
101-128
VEGA User Guide
24 Device information and diagnostic

The device info web page contains information related to hardware, software and diagnostic
status.
Using the WEB pages
24.1 Information
Depending on the system, some capabilities could be shown as disabled or not shown at all.
24.2 Diagnostic
Status: describes the summary of device status:
OK: system is working fine.
Warning: the device detected something wrong in the system variables. The device may still
work but with poor performances.
Alarm: the device detected severe malfunctioning. It should not work in this status.
Config: the device is in configuration from a web browser or using the VRC commands.
(This status is available if and only if the option is enabled on the configuration web page,
see 23 Installation layout and diagnostic configuration.)
(Brescia), Italy..
102-128
VEGA User Guide
Internal parameters: reserved.

Last check time / Boot time: date of the last diagnostic check and boot time (GMT time).
Please note that if the device starts with a wrong date or time, these values ma be invalid.
Diagnostic parameters:
Description
Temperature
Humidity
Secure Digital
Type
Malfunction
Malfunction
Malfunction
Current
Camera tilt/roll
Malfunction
Malfunction
RAM memory
Alarm
Processes and threads
Alarm
Type server sync
Malfunction
Acquisition on OCR
channel
Acquisition on color
channel
Plate reader status
Alarm
Encryption key status
Malfunction
Malfunction
Alarm
Note
System can not store data for buffering or

storage functions.
System is working out of the configured
angles. This could affect performances on
plate reading.
System fault. The device will restart in 3
minutes.
System fault. The device will restart in 3
minutes.
System cannot synchronize date and time with
the time server. Date and time could be
imprecise or wrong. Malfunctioning alarmi s
sent after 3 hours of failed sync.
System fault. The device cannot capture
images for plate reading.
Malfunction: the device cannot capture context
color images.
System fault. System cannot load all required
OCR learns or plate reader cannot be correctly
initialized.
The device detected an invalid key. The device
will not encrypt images.
(Brescia), Italy..
103-128
VEGA User Guide
25 Digital inputs and outputs

This page allows to monitor the state of the video camera digital inputs and controlling the
digital outputs. Depending on the device type, some features may not be available.
This configuration page is accessed through the icon shown below:
Using the WEB pages
Vega systems have embedded digital inputs and outputs. Outputs are used for controlling
external devices; inputs can be used as trigger sources. It is possible to check and modify the
status of digital outputs. This feature is useful when checking the cabling upon installation.
A green input icon indicates that the input is high and a red output icon indicates that the output
is low. The digital output state can be changed by clicking on the output icon. The Refresh
Status updates the input and output logical status.
25.1 ID management
In devices of the Vega HD family this web page is also used for checking the ID logical state
and configure the ID behavior.
(Brescia), Italy..
104-128
VEGA User Guide

As for the digital inputs the ID icon will be green if the ID logical state is high (closed contact);
otherwise the ID icon will be green if the ID logical state is low (open contact).
Event trigger on ID change: it is possible to configure which condition generates the
Changed ID event (See chapter 7). The possible configurations are:
NONE: The event Changed ID is never raised.
RISE: The event Changed ID is raised when ID logical state becomes high.
FALL: The event Changed ID is raised when ID logical state becomes low.
BOTH: The event Changed ID is raised when ID logical state changes.
ID state for time evaluation: It is possible to measure how long an ID has been in a given
logical state. Available configurations are:
NONE: The time is never measured.
HIGH: The system measures how long the ID remains in high state.
LOW: The system measures how long the ID remains in low state.
25.1.1 Example of time evaluation for IDs

T1
T0
[1]
Ta
[2]
[3]
Tb
The picture represents an hypothetical ID0s trend. Assuming that ID 0 logic is HIGH, there
will be the following behavior:
1. During period [1] every actions tag called ID0_LOGIC_DELTA_MS will contain the time
in millisecond since T0.
2. During period [2] every actions tag called ID0_LOGIC_DELTA_MS will contain Ta.
3. During period [1] every actions tag called ID0_LOGIC_DELTA_MS will contain the time
in millisecond since T0.
Otherwise, if the ID 0 logic is LOW the behavior will be inverted.
25.2 External strobe signal

The device can drive an external strobe light. The driving signal can be configured as:
- Normal
- Inverted
For dual head cameras (Vega 2HD) you can also configure the synchronization channel:
- Channel 0: OCR channel
- Channel 1: Color camera
(Brescia), Italy..
105-128
VEGA User Guide
26 System statistics
The page contains statistics about triggers and events.
The info in this page is very useful upon installation as they help check the available pass
bands from Vega to the data receiving servers.
In addition to this info, the page displays the statistics about synchronization with the SNTP
server. These statistics are updated when synchronization with time server is enabled (Network
Settings page).
Using the WEB pages
(Brescia), Italy..
106-128
VEGA User Guide
27 RTP streaming
Devices such Vega 2HD, Vega 2H can be configured to generate a RTP streaming (H264 or
Mpeg4) from the color channel.
27.1 Vega 2HD streaming

Using the WEB pages
The configuration page RTP is divided into two sections: RTP Streamingand SDP File:
RTP Streaming:
Enable: it allows to enable (YES) the sending of video streaming.
Stream Format: it is possible to choose between MPEG4 and H264.
Dest. IP (uni/multi cast): IP address of streaming video destination.

(Brescia), Italy..
107-128
VEGA User Guide
Dest. Port: destination port.
Bandwidth Control: type of bandwidth control, CONSTANT_BITRATE orqualit

CONSTANT_QUALITY.
Bandwidth [Kbit/sec] (*): if Bandwidth Control is enable this value define the limit of the
bandwidth.
Quality % (**): defines the quality of the streaming video, ONLY if Bandwidth Control is
disabled.
GOP (Group Of Picture): define the distance between frame I (intraframe), default 20 frames.
Frame rate: streaming video frame rate. The allowed values are: 1, 3, 7, 10, 15 and MAX.
Timestamp in IDR header: if enabled (YES), it allows to have the timestamp coded in the
Userdata field of video stream. Please see appendix for further information.
Overlay Time: it allows to write the timestamp in overlay on the video.
SDP File:
SDP Notify Mode: SDP file destination:
REMOTE_FTP: remote FTP.
LOCAL_FFS: local memory (SD).
BOTH: both.
FTP Notify: enables the sdp file to be sent to a FTP server.
FTP Server IP: IP address of FTP server where to send the SD file.
(Brescia), Italy..
108-128
VEGA User Guide

FTP Server Username: username to write the file in the FTP folder.
FTP Server Password: password for the FTP server.
FTP Server Port: porta for the FTP server.
FTP Server Path: destination path of the sdp file on the ftp server.
SDP File Name: sdp filename.
Use streaming server: it allows (YES) to send video towards a Streaming Video Server (for
example Darwin Streaming Server).
Connection server IP: IP address of the streaming server.

The Send SDP button force the sending of sdp file.
27.2 Vega 2H streaming

A specific module in the Vega 2H is in charge to produce the stp stream. It can be accessed via
web page to a specified IP address. Use Tattile Device Discovery to configure its IP.
The device name is H264 ENCODER .
(Brescia), Italy..
109-128
VEGA User Guide

The web page allow two main sections:
Encoder: RTP stream configuration
System: system configuration (IP, etc), similar to Vega web interface.
27.2.1 Encoder configuration
The encoder menu includes the RTP configuration page..
(Brescia), Italy..
110-128
VEGA User Guide
RTP Streaming:
Send: it allows to enable (YES) the sending of the video streaming.
Stream Format: it is possible to choose between MPEG4 and H264.
Dest. IP: IP address of streaming video destination.
Dest. Port: destination port.
Bandwidth Control: enable the bandwidth control.
Bandwidth [Kbit/sec]: if Bandwidth Control is enable this value define the limit of the
bandwidth.
Quality %: defines the quality of the streaming video, ONLY if Bandwidth Control is disabled.
GOP (Group Of Picture): define the distance between frame I (intraframe), default 20 frames.
Fps decimation ratio: frame decimation factor; default value is 1, it matches a 30fps.
Streaming server: it allows (YES) to send video towards a Streaming Video Server (for
example Darwin Streaming Server).
Streaming Server Conn. IP: IP address of streaming server.
Overlay Date and Time: it allows to write the timestamp in overlay on the video.
SDP File:
FTP Notify: sends the sdp file to a ftp server.
FTP Server IP: IP address of FTP server where to send the SDP file.
FTP Server Username: username to write the file in the FTP folder.
FTP Server Password: password for the FTP server.
FTP Server Port: FTP port.
FTP Server Path: destination sdp file path.
(Brescia), Italy..
111-128
VEGA User Guide
27.2.2 Device configuration
The page contains the following features:
Network: the settings of Network configuration and Time synchronization through Time
Server (SNTP Protocol).
HTTP users: the configuration settings for users who use a browser to access the machine.
Log Files: configure log file status.
Firmware: this page displays the commands for updating the machine to the latest software
release and extracting the configuration to be automatically copied to another unit.
Device Info: this page displays info about the system hardware, configuration and firmware
versions.
(Brescia), Italy..
112-128
VEGA User Guide
28 Appendix A: Extraction of timestamp from IDR (H264) or I

(MPEG4)
Inside the field userdata belonging to IDR header (H264) or I frame (Mpeg4) is
present the timestamp of the image sent.
Here after is described the way to extract it., using an example frame.
28.1 Frame IDR H264

This is a payload UDP of a frame IDR H264, sending from the camera:
00
00
00
00
00
00
00
00
00
00
10
20
30
40
50
60
70
80
1c
00
00
03
00
76
34
7b
72
80
01
0c
00
63
bf
4d
c9
c1
00 00
68 ce
00 00
00 00
7a 1a
ee 61
f0 ff
b6 0d
04...
00
38
00
01
80
ef
90
c8
01
80
04
41
00
f5
11
6e
67
00
02
88
84
60
1a
d5
42
00
db
c4
b9
79
f3
1f
00
00
07
15
fb
f7
2b
d5
14
01
08
c4
93
36
a9
f0
a6
26
00
80
ca
b5
8c
80
81
05
2c
44
0c
f6
07
17
41
14
00
60
74
a6
bb
1f
f9
fa
1e
cd
b4
d0
39
b8
00
2e
00
31
21
f6
7e
61
00
00
96
6f
1b
76
ea
eb
Inside the stream is possible to search for the sequnce of byte underlined (in HEX:
00 00 00 01 26 05), which is followed by 1 byte indicating the quantity of user
bytes that follow:
Header Supplement Enhancement Info: 6 bytes

0x00 0x00 0x00 0x01 0x26 0x05
Payload size: 1 byte
0x14 (variable depending on how many data are inserted by the user)
28.2 Frame I (MPEG4)

This is a payload UDP of a frame I MPEG4, sending from the camera:
00
00
00
00
00
10
20
30
00
00
b5
50
00
04
91
a0
01
02
81
41
b0
db
00
e1
02
07
00
41
00
0d
01
03
00
00
00
00
01
33
00
00
b2
00
00
01
fa
36
01
b6
2e
00
20
28
00
cb
00
60
00
03
c8
59
0c
00
88
41
00
00
80
09
00
01
05
9f
(Brescia), Italy..
113-128
VEGA User Guide

00 40 3d fd 77 bb 55 35 4a 90 f6 9a 23 68 16 e4 1a d9
00 50 d3 73 63 17 be d2 88 ef e5 bf 02 97 6d 44 b1 ff
00 60 e5 bd 51 7b 01 db 6d 22 50 be f8 42 65 26 ee e1
0070 2d b0 b7 01 e3 3f f9 cf c0 9e 76 df 76 c2 74 95
0080 b4 39 6a
Inside the stream is possible to search for the sequence of byte underlined (in
HEX: 00 00 01 B2), which is followed by 1 byte indicating the quantity of user
bytes that follow:
Header User Data: 4 bytes
0x00 0x00 0x01 0xB2
28.3 Content of field user data

The user data field contains data encoded using the SC Tattile protocol, as following:
[data code][len][user data]
data code: integer which identify the type of data contained in the block (ex:
12026: date-time, 12010: shutter, etc...).
len: integer that contains the number of useful bytes contained in the [user data] block.
user data: the data. The length of the field must always be multiple of 4 bytes.
In the following example is present only one block of data corresponding to [data
code]=12026 which means timestamp.
28.4 Example
Consider the following field of user data present in the stream H264 or MPEG4:
0010
fa 2e 00
0020 00 0c 00 00 00 04 02 db 07 08 00 2c 00 1e 00 96
0030 03
The decode result is:

Code: 4 bytes (integer little endian)
0x00 0x00 0x2E 0xFA (12026)
Size: 4 bytes (integer little endian)
0x00 0x00 0x00 0x0C (12)
User data: 12 bytes (little endian)
0x04 0x02 0xDB 0x07 0x08 0x00 0x2C 0x00 0x1E 0x00 0x96 0x03
Then:
0x04 (04) 0x02 (February) 0x07DB (2011)
0x0008 (ore 8) 0x002C (44 min) 0x001E (30 s) 0x0396 (918 ms)
Hence: 04/02/2011 08:44:30,918.
(Brescia), Italy..
114-128
VEGA User Guide
29 Appendix B: examples of system architectures

Free run and trigger mode examples.
FREE-RUN
FTP Server
and/or VRC
Server
VEGA
LAN/WAN
TRIGGER ethernet
FTP Server
and/or VRC
Server
VEGA
Trigger Message
with unique ID
LAN/WAN
Data and/or Images
Trigger Source:
Loop system,
Optic Barriers,
(Brescia), Italy..
115-128
VEGA User Guide
30 Appendix C: available TAGs

It is possible to use the TAGs for:
- Fill the jpeg header of the image.
- Create the path name and file name for storing image via FTP.
- Create the data to be sent via TCP Message.
- Create the data to be sent as a CSV file via FTP (DB).
- Path name and file name of the locally saved jpeg image.
- Data field for RS485 and RS232 data.
- Overlay message on the jpeg image.
- Custom protocols data (if available).
Depending on the firmware version and on the device type, some TAGs may be
not available.
Some TAGs could be available only in some fields (in example: path name may
allow different TAGs than CSV file).
Please refer to the website help on the camera to list the available TAGs.
30.1 Example: Building a file name string.

Use the % to distinguish between TAGs:
example: %DATE%_%PLATE generates a file named: 2010-12-14_CG281SV-ITA.jpg
30.2 Example: Building path name.

Use the % and & to distinguish between TAGs:
When you use %, different TAGs will generate a directory.
When you use &, different TAGs will concatenate the strings.
Example: %TLC%DATE&_&HOUR%MIN creates the following directory tree:
TLC/2010-12-14_22/55, where:
- TLC: is not a recognized file so it will be used as string.
- 2010-12-14_22: date and current hour.
- 55: current minute.
(Brescia), Italy..
116-128
VEGA User Guide
30.3 List of available TAGs

TAG value
Description
JPG
TCP
File
name
File
path
Image
overlay
DB
Standard
XML
Data code
Data size
(maximum)
Date type
ACQUSITION_MODE
Acquisition mode (FREE RUN, TRIGGER,...)
14025
32
STRING
DATE
Current local date with format YYYY-MM-DD
14000
12
STRING
TIME
Current local time with format HH-MM-SS-mmm (mmm are milliseconds)
14001
16
STRING
UTC_DATE
Current UTC date with format YYYY-MM-DD (local time)
14093
STRING
UTC_TIME
Current UTC time with format HH-MM-SS-mmm (mmm are milliseconds)

(local time)
14094
STRING
YEAR
Current local year with format YYYY
14066
LONG
MONTH
Current local month with format MM
14067
LONG
DAY
Current local day with format DD
14068
LONG
HOUR
Current local hour with format HH
14069
LONG
MIN
Current local minutes with format MM
14070
LONG
SEC
Current local seconds with format SS
14071
LONG
Current local milliseconds with format mmm
14072
LONG
14003
14073
MILLISEC
PLATE
PLATE_HASH
Plate number and 3 chars for the country (Example: AA182NN-ITA)
SHA-1 hash of plate (plate number and 3 chars for the country)
STRING
44
STRING
Plate number for plate not read (Example: AA182NN-NRD).

PLATE_NOT_READ
In case of READ result, the TAG will contain the value READ.
14040
STRING
Plate string (Example: AA182NN)
14004
STRING
PLATE_COUNTRY
Plate country (Example: ITA)
14005
STRING
PLATE_PROVINCE
Plate province, if available
14081
STRING
PLATE_REGION
Plate region (Example: QC)

See ISO 3166-1 local ISO codes.
14088
STRING
PLATE_PREFIX
Plate prefix (valid only for ARE countries).
14089
STRING
14022
LONG
14002
32
STRING
14007
128
STRING
In case of NOPLATE result, the TAG will contain the value NOPLATE
PLATE_STRING
OCRSCORE
NETBIOSNAME
IMAGENAME
Score of the OCR process

Netbiosname of the camera
Ftp image name
Il contenuto di questo documento di propriet della TATTILE srl. Non consentito riprodurre totalmente o parzialmente questo documento, n divulgare informazioni in esso contenute, ne mettere in atto metodi, processi, o prove in
esso descritti senza autorizzazione rilasciata dalla TATTILE S.r.l., Mairano (Brescia)
The subject of this document is a TATTILE srl property. This document or any part of it must not be reproduced in any form, nor information therein contained disclosed to third parties, nor methods, procedures or tests described,
performed without the authorisation of TATTILE S.r.l. , Mairano (Brescia), Italy..
117-128
VEGA User Guide

TAG value
IMAGEPATH
NREAD
Description
JPG
File
name
File
path
Image
overlay
Ftp image path

Number of images with a read plate in the transit
Standard
XML
Data code
Data size
(maximum)
Date type
14008
128
STRING
14006
LONG
Acquisition shutter time (in microseconds) of the image
14029
LONG
Acquisition gain of the image
14030
LONG
STROBO
Acquisition strobo time (in microseconds) of the image
14031
LONG
AI_LEVEL
AutoIris level
PLATE_MIN_X
X top left corner of the plate in the image
14010
LONG
PLATE_MIN_Y
Y top left corner of the plate in the image
14011
LONG
PLATE_MAX_X
X bottom right corner of the plate in the image
14012
LONG
PLATE_MAX_Y
Y bottom right corner of the plate in the image
14013
LONG
Transit counter (from the boot of the device)
14009
LONG
PLATE_DESC_A
Plate description (only for Match on list A action)
14023
128
STRING
PLATE_DESC_B
Plate description (only for Match on list B action)
14024
128
STRING
14014
LONG
14015
LONG
14016
32
STRING
14032
32
STRING
SHUTTER
GAIN
TRANSIT_ID
SPEED
CLASS
CLASS_STRING
VEHICLE_TYPE
VEHICLE_TYPE_NUM
Vehicle speed km/h * 100.

Example: 2345 means: 23,45Km/h
Class of the vehicle (class id):
See chapter: 30.6 List of available enumerators
Class of the vehicle (string description):
Type of the vehicle (string description) based on the plate format:
TCP
DB
RESERVED
QUALIF_0
Qualifier Byte 0
QUALIF_1
Qualifier Byte 1
Vehicle loop occupancy time (ms)
GAP_TIME
Vehicle gap time (ms)
DIRECTION
Vehicle direction
14018
12
STRING
Device Serial Number
14017
LONG
14019
32
STRING
OCCUPANCY_TIME
SN
NET_TRIG_ID
Network Trigger ID string
118-128
VEGA User Guide

TCP
JPG
File
name
File
path
Image
overlay
DB
Site Address name specified in General Settings page
Acquisition binning value
Plate color description
Plate color hue
GAIN_RED
Acquisition red gain of the image
GAIN_BLUE
Acquisition blue gain of the image
PLATE_STD
Standard plate only when joined
14026
STRING
PLATE_TRL
Trailer plate only when joined
14027
STRING
PLATE_ADR
ADR plate only when joined
14028
IMAGE_BW
Ocr camera image
14020
IMG_BW_DIM
BUFFER
IMAGE_COL
Context camera image
14021
IMG_COL_DIM
BUFFER
TAG value
SITE_ADDRESS
BINNING
PLATE_COLOR_STRING
PLATE_COLOR_HUE
Description
Standard
XML
Data code
Data size
(maximum)
Date type
14039
128
STRING
'-'
Separator '-'
'_'
Separator '_'
','
Separator ','
';'
Separator ';'
''
Separator ' '
0xAB
Two digit hex number
CRLF
Newline (Windows)
LF
PLATE_COLOR_WIN
X
X
X
VEHICLE_BRAND_STRING Brand string of the vehicle
Image signature, header included
Device firmware version
Device FPGA version
Device board code
Device board revision
Device boot version
FFS_SIZE_KB
Device FFS size
SD_SIZE_MB
Device SD size
FIRMWARE_VER
BOARD_FPGA_VER
BOARD_CODE
BOARD_REV
BOOT_VER
STRING
VEHICLE_COLOR_STRING Color string of the vehicle
IMAGE_SIGN
Newline (Unix)
Plate position in color image
119-128
VEGA User Guide

TAG value
JPEG_QUALITY
MAX_GATE_TIME
OCR_CFG
Description
JPG
JPG quality
Maximum gate time
Plate reader configuration
File
name
File
path
Image
overlay
TCP
DB
Standard
XML
Data code
Data size
(maximum)
Date type
Diagnostic status:
DIAG_STATUS
DIAG_NONE: No alarms
DIAG_WARNING: Warning status
14037
257
STRING
14038
257
STRING
12518
256
STRING
DIAG_ALARM: Alarm status

Diagnostic status string
Detailed diagnostic.
Each entry is divided by a _ character. Each elementi s composed by 3
chars (analysis type) followed by a number (analysis status).
Available values for analysis status:
DIAG_STRING
0: Invalid / non-controlled on / off

1: No alarm
2: Warning
3: Alarm
The tests available and their codes are listed below:
"DAT": Date and Time
"THE" Temperature, humidity
"DSS" SD Storage Device
"CVM" Current Consumption
"TLR" tilt camera
"MEM" Status Memory
"PRO" Processes in execution
"TSY" Time Synchronization
"COA" BW Camera
"CCA" Color Camera
"PRA" Plate Reader
"CRY" encryption keys images
example:
"DAT1_TEH0_SDD1_CVM0_TLR0_MEM1_PRO1_TSY2_COA1_CCA0_
PRA1"
DIAG_MASK
RESERVED
CAM_SIGN
Camera Signature
OCR_SCORE
DIRECTION
Score given the degree of goodness on the process of reading license

plates.
0 <= value <= 100
The Tag DIRECTION supports the following parameters:
"Approach": The Plate is going towards the camera, this means that the
plate moves from top to bottom in the image;
"GO_AWAY": The Plate moves away from the camera, this means that
X
X
14022
LONG
14018
STRING
120-128
VEGA User Guide

TAG value
Description
JPG
File
name
File
path
TCP
Image
overlay
DB
Data size
(maximum)
Standard
XML
Data code
Date type
14056
STRING
Index of the ID that raised the event Changed ID
14059
LONG
Delay in millisecond form the last change of the ID_INDEX ID
14060
STRING
Event description:
- RISE
- FALL
14061
LONG
the plate moves from the bottom to the top in the image;
"UNKNOW": It is not possible to detect the direction of motion of the
plate, perhaps because the plate is locked in a position in the image..
GRAB_MODE
ID_INDEX
ID_CHANGE_TIME_MS
ID_EVENT
Grab parameters selection mode.

- Single point: contains gain, shutter (us) and strobo (us) values.
Example: SINGLE_POINT-G512-Sh10000-Sb200
- Multipoint: contains shutter and gain values for the 4 working points
Example: MULTI_POINT-P0-G200-Sh200-P1-G350-Sh350-P2-G400Sh400-P3-G500-Sh5500
- Autoiris: contains speed, level, min and max shutter (us) and gain, gain
color (if color camera), and autoiris window. Example: AUTOIRISSpd90-Lv50-ShMin2-ShMax12000-Gmin78-Gmax450-GColmax256Elem100-Win(0-0)(1280-960)
ID0_STATUS
ID0 logical state
14062
LONG
ID1_STATUS
ID1 logical state
14063
LONG
ID2_STATUS
ID2 logical state
14064
LONG
ID3 logical state
14065
LONG
ID0_LOGIC_DELTA_MS
Time spent by the ID0 in the logical state of interest.

See digital I/O management
14074
LONG
ID1_LOGIC_DELTA_MS
14075
LONG
ID2_LOGIC_DELTA_MS
14076
LONG
ID3_LOGIC_DELTA_MS
14077
LONG
14092
STRING
14086
LONG
ID3_STATUS
PLATE_CENTROIDS
LANE_ID
Plate centroids in transit images: (X, Y,delta from transit timestamp)

Example: (1358,1587,-76)(1362,1560,-50)(1366,1532,-25)(1373,1505,0)
If the management lanes has been enabled, the related tag can
assume the following values
0: not determined
1: transit detected on lane 1
2: transit detected on lane 2
121-128
VEGA User Guide
30.4 Jpeg header data

Each Jpeg generated in a configured action has a header containing configurable data.
Data are configurable by accessing the link available in the Events Action configuration pages.
Please note that the JPEG header configuration is the same for all actions.
30.4.1 Web page

The web page is built as following:
Header Type: type of jpeg header.
Added by default: list of non-removable fields.
Other custom TAGS: configurable TAGs. Click on HELP link to list all available tags.
Default TAGS: list of TAGs added by default. This is useful to restore default
configuration by copy-paste from the Default TAG textbox to the Custom TAG
textbox.
Using the WEB pages
30.4.2 Header decoding

Jpeg header data are inserted in the JFIF field named APP 0. Its code is 0xFFE0. The following
2 bytes contains the length of the field in bytes, including the 2 bytes of the size field itself.
Example:
- 0xFFD8: Start of Image.
- 0xFFE0: APP0.
- 0x037C (892): size of the user data field, including 2 bytes of this field.
(Brescia), Italy..
122-128
VEGA User Guide

- User date: 890 bytes of date.
- Jpeg stream.
Data types in the jpeg header are identified by the starting chars:
- S_: string value
- I_: integer value
- F_: float value
Each field is separated by a CR+LF, and the separation between TAG and the field value is the
symbol =.
Fields could appear in different order depending on the firmware version and on the user
configuration. Please use the TAG name for searching the fields inside the header buffer.
Here an example of the jpeg stream containing the header, in hex format and in text format.
Please note that each entry is in a separate line.
FF
5F
36
63
32
45
36
46
41
.
30
49
00
D8
56
38
20
34
3D
34
50
52
FF
45
20
31
0D
52
37
47
44
E0
52
49
33
0A
4F
30
41
5F
03
3D
54
20
53
54
34
5F
43
7C
56
41
32
5F
4F
31
56
4F
53
45
2D
30
4E
4E
0D
45
44
5F
47
45
31
45
44
0A
52
45
46
41
55
31
54
41
49
3D
3D
49
20
2D
20
42
0D
5F
30
36
52
49
49
30
49
0A
42
0D
34
4D
49
53
39
4F
49
4F
0A
30
57
49
54
3A
53
5F
41
49
0D
41
20
20
33
4E
53
52
5F
0A
52
38
44
31
41
4E
44
42
49
45
2E
65
3A
4D
3D
5F
4F
5F
.|S_FIRMWARE
_VER=VEGA III 8.
68 ITA-EU-IST De
c 13 2011 09:31:
24..S_NETBIOSNAM
E=ROTONDA..I_SN=
647041..I_BOARD_
FPGA_VER=0..I_BO
ARD_CODE=640..I_
2C 20 31 2C 20 30 0D 0A 53 5F 43 41 4D 5F 53
47 4E 3D 0D 0A FF E9 00 04 00 00 FF DD 00 04
3C FF DB 00 84 00 13 0C 0C 0C 10 0C 13 10 10
S_FIRMWARE_VER=VEGA III 8.68 ITA-EU-IST Dec 13 2011 09:31:24

S_NETBIOSNAME=ROTONDA
I_SN=647041
I_BOARD_CODE=640
I_BOARD_REV=4
S_BOOT_VER=3.0
S_DATE=2012-02-21
S_TIME=14-00-26-787
S_PLATE=DN866PW-ITA
I_NREAD=12
F_OCRSCORE=072
I_JPEG_QUALITY=75
I_GAIN=200
I_SHUTTER=200
I_STROBO=200
I_AI_LEVEL=50
I_SPEED=NA
S_CLASS_STRING=CAR
S_DIRECTION=GOAWAY
I_PLATE_MIN_X=261
I_PLATE_MIN_Y=255
I_PLATE_MAX_X=380
I_PLATE_MAX_Y=286
(Brescia), Italy..
123-128
VEGA User Guide
S_NET_TRIG_ID=
30.5 TCP message data types

The TCP Message in the STANDARD mode is built as following.
N. bytes
4
4
4
4
Field name
Header Size
Command Code
Not used
Not used
Error
Payload size
MSG_SIZE
Message to send
Client-server generic command

Description
Value
Size in bytes of the header. It is always set to 24.

Identification code of the sent message
Not Used
Not Used
If sending was faultless, Vega sets this field to 0. Otherwise, this
field shows the error code, if any.
Size in bytes, 32-bit aligned, of the data to be sent after the
header (header size is not included).
Custom data specified in the web page.
24
40000
0
0
0
MSG_SIZE
The firsts 24 bytes are called Command Header. The optional following bytes are the
Payload. The Payload length must be always multiple of 4 bytes. If the data contained in the
payload arent multiple, zero padding is required.
Each field contained in the payload must be formatted as in the following table.
N. bytes
4
4
ALIGN_LONG(DATA_SIZE)
Message Generic Data Block

Description
DataCode
DataSize
DataBuffer
Value
DATA_SIZE
The table shows the first 8 bytes (the Data Header) that contains the Data Code, a number
that identifies the content of the field, and the Data Size, a number that specifies the useful
length of the Data Buffer.
After the Data Header, the Data Buffer is the actual payload. It must be always a multiple of
4 bytes. Padding required if needed.
In the same message may be present a variable number of these data blocks. The Data Size
field of each block allows to jump through each one and to scan the whole message. Receiving
application must be able to search for the required Data Code inside the message regardless
of the data block order.
In example if you receive a field with Data Size value is 18, you must expect an actual Data
Buffer length of 20 bytes (20 is the highest near multiple of 4). So the application knows that its
payload will contain 18 useful bytes, but the application will need 20 bytes offset (plus the 8
bytes of the header) for jumping at the following data block.
The web page allows to configure the fields the message will contain as payload. In example, if
you specify %PLATE%DATE%TIME, the message payload will contain the data codes as
specified in the appendix.
30.5.1 Type STRING

- All strings are null-terminated.
(Brescia), Italy..
124-128
VEGA User Guide

- Unused bytes are set to 0, or the string inserted in the field is at least strlen(string)+1.
- All strings are UTF-8 encoded.
Example 1:
The TAG %CAM_SIGN contains the string AEF23AC012 which is 10bytes long. Including the
\0 null terminator, there are 11bytes needed. Aligned to the 4byte, the total field len that must
be senti s equal to 12 bytes.
So the payload field will contain 12 bytes, whose the last 2 are set to 0.
The data_size variable will contain the number 11 meaning that the useful bytes in the
payload are only the first 11.
30.5.2 Type LONG

- 32-bit integer.
- The format is little endian
30.5.3 Type BUFFER

- The value of DATA_DIM is not necessarily multiple of 4 bytes, but the occupied buffer
space is always a multiple of 4 bytes, to keep structure alignment (padding if needed).
Example 1:
consider IMG_BW_DIM and suppose this is a 34231 bytes image. This means that
DATA_DIM=34231. But data buffer sent from Vega is larger (so as to keep 4 bytes-alignment)
and the result is a 34232 bytes image.
When using the DATA_DIM value to skip to next datum of the message, this should not be
overlooked.
30.6 List of available enumerators

Available tags could have both numerical and string format.
30.6.1 TAG CLASS and CLASS_STRING

If available, vehicle class is reported in TAG as string and as number.
Number
Tag: CLASS
0
1
2
3
4
5
6
String
Tag: CLASS_STRING
CAR
CAR WITH TRAILER
LORRY
LORRY WITH TRAILER
BUS
MOTORCYCLE-MOTORBYKE
UNKNOWN
7
8
9
MOTORCYCLE
MOTORBYKE
CAR
10
OTHERS
Note
Car
Car with trailer
Lorry
Lorry with trailer
Bus
Motorcycle or motorbike
Depending on classificator:
Identifies any unclassified vehicle
Motorcycle
Motorbike
Identifies any vehicle that is not a motorbike or a
motorcycle
Identifies any unclassified vehicle
30.6.2 TAG VEHICLE_TYPE

If available, vehicle type is reported in TAG as string. Please note that not all countries have the
whole set of categories.
(Brescia), Italy..
125-128
VEGA User Guide
String
Tag: VEHICLE_TYPE
UNKNOWN
PASS
PASS_NEW
PASS_OLD
PRIV_TR
PRIV_TR_NEW
PRIV_TR_OLD
TAXI
TAXI_NEW
TAXI_OLD
MOTO
MOTO_NEW
MOTO_OLD
MOPED
MOPED_NEW
MOPED_OLD
PUBL_TR
PUBL_TR_NEW
PUBL_TR_OLD
EXPORT
EXPORT_NEW
EXPORT_OLD
DIPLOMATIC
DIPLOMATIC_NEW
DIPLOMATIC_OLD
TRAILER
TRAILER_NEW
TRAILER_OLD
DEALER
DEALER_NEW
DEALER_OLD
IMPORT
IMPORT_NEW
IMPORT_OLD
Note
Passenger
Private transport
Taxi
Heavy motorcycle
Light motorcycle
Public transport
Export
Diplomatic
Trailer
Dealer
Imported vehicles
31 Appendix D: List of supported countries

31.1 Country code
Standard Country codes: ISO 3166-1 alpha-3 (http://it.wikipedia.org/wiki/ISO_3166-1_alpha-3).
Standard Region codes: ISO 3166-1 (http://it.wikipedia.org/wiki/ISO_3166-1).
In example: if the TAG PLATE reports: 345JKL-CANQC, that means:
- 345JKL: Plate number
- CAN: Country code - Canada
- QC: Region - Quebec
31.2 Supported countries

Supported countries:
http://www.tattile.com/vision-systems/traffic-division/where-we-are/
(Brescia), Italy..
126-128
VEGA User Guide
31.3 Special plates

The table shows additional custom country codes for special plates supported by Tattile
devices.
Code
Country
ADR
Dangerous goods
CON
Container
TRL
Trailers
(Brescia), Italy..
127-128
VEGA User Guide
Tattile srl 2014 All rights reserved.

Tattile is a proprietary registered mark of Tattile srl
(Brescia), Italy..
128-128

Vega - User Manual 6.47 - Eng

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Vega - User Manual 6.47 - Eng

Uploaded by

Copyright:

Available Formats

VEGA User Guide

Embedded System for Automatic Number Plate

VEGA User Guide

VEGA User Guide

VEGA User Guide

1 Conventions used in this document

Warning: specific suggestions that may as well refer to security matters

VEGA User Guide

Aligned with firmware version 4.29

VEGA User Guide

Updated description of Save DB page. Added CRLF

VEGA User Guide

Color Camera (*)

Loop Detector (*)

VEGA User Guide

4 Vega unit configuration

VEGA Number Plate Reader

4.1 Web server

4.2 VRC server

4.3 Receiving data from Vega unit

VEGA User Guide

VEGA Number Plate Reader

VEGA User Guide

5 Using the web server

5.1 Tattile Device Discovery and manuals downloads

5.2 Using Tattile Device Discovery

VEGA User Guide

5.3 Web browser access and user authentication

VEGA User Guide

Note: factory assigned user name and password are as follow:

VEGA User Guide

5.4 Access levels

VEGA User Guide

6 Main web page

Figure 1: Page "Plate Reader"

Figure 2: Page "System"

Plate Reader contains the following features:

VEGA User Guide

VEGA User Guide

VEGA User Guide

7 Events and actions

The icon of access to the configuration matrix is shown below here:

The configuration matrix of the actions is shown below here:

VEGA User Guide

VEGA User Guide

VEGA User Guide

7.1 Save image to FTP server

VEGA User Guide

Example of high quality (90) JPG image

Example of low quality(5) JPG image

VEGA User Guide

VEGA User Guide

FTP IP: the IP address of the FTP server.

7.2 Saving text messages to FTP server

VEGA User Guide

VEGA User Guide

FTP IP: the IP address of the FTP server.

7.3 Send alarm to Gate Master (GM alarm)

Using the WEB pages

VEGA User Guide

VEGA User Guide

7.4 Pulse out

Using the WEB pages