User's Manual
Table Of Contents
- 1 General
- 2 Introduction
- 3 System Description
- 4 Hardware
- 5 Installation
- 6 Coordinate System
- 7 Commissioning
- 7.1 Check list installation and surveying
- 7.2 Editing of configuration files for the DSP
- 7.3 Upload of configuration files for the DSP
- 7.3.1 Connection with LPR mobile unit (type: compact) via TCP/IP
- 7.3.2 Connection with LPR mobile unit (type: compact) via RS232
- 7.3.3 Upload DSP configuration file for LPR mobile unit (base station)
- 7.3.4 Upload DSP configuration file for master transponder unit
- 7.3.5 Upload DSP configuration file for transponder unit
- 7.4 Editing of configuration files for Fusion Engine
- 7.5 Upload configuration files for FusionEngine
- 8 Symeo MAP
- 9 Network Settings
- 10 Symeo 2D Protocol
- 11 Appendix A: Agency certifications
Symeo LPR
®
-System
LPR
®
-2DB
Product Documentation
Introduction
Copyright © Symeo 2012
Page 13 of 132
the selected model, application and operation mode)
- symeo_map.ini
- symeo_2D.ini
All files are delivered in the structure shown in Figure 1 (“deliverables” and “symeoMap”).
Figure 1- folder structure
The folder “mobileUnits”
contains all files for the
vehicles. The folder
“staticCells” contains all files
for the LPR-2DB Integral
Station including the master
LPR-2DB Integral Station. The
folder name for all LPR stations
is named with the serial
number.
To allocate the stations for the customer, it makes sense to create a
text-file that describes the function of that LPR station, i.e.
“forklift_123_customer.txt”.
If it is later necessary to replace a LPR unit (e.g. due to a defect) you
can find easily the necessary configuration files for the appropriate
station.
Folder for the files of the
FusionEngine