Symeo LPR
®
-System
LPR
®
-2DB
Product Documentation
Symeo
2D Protocol
Copyright © Symeo 2012
Page 127 of 132
once per second. But this can also happen if the line of sight between cell master and a
single transponder is broken (e.g. an obstacle between in the line of sight).
To detect a broken master, we count the number of IDLE messages of a single cell in the last
60 seconds. If we receive at least one IDLE message of at least two different transponders
during this time and received no valid transponder measurement during the observation
interval and the oldest IDLE message is at least 30 seconds old, we assume the cell master
is broken.
The error value contains the cell ID of the broken master.
10.6.2.2 0x02
– broken transponder
If a single transponder is broken, it is not measured by the base station, so the basestation
measures only the remaining transponders of a cell. But such failures can be position
dependent, so we have to check, if a transponder isn't measured at several positions of the
basestation.
To detect a broken transponder, we count the number of
“positions bins”, in which the other
transponders of a cell was measured. A
“position bin” is a square of 5x5 meter. If at least
50% of all cell transponders were successfully measured in at least 5 position bins (per
measured basestation antenna) and the observed transponder was not measured in any
position bin, we assume the transponder is broken.
The error value contains the LPR-B address (see chapter 10.6.3) of the broken transponder.
10.6.2.3 0x05
– broken LPR antenna
To detect a broken LPR antenna, we count the number of
“positions bins”, in which we
measured another LPR antenna. A
“position bin” is a square of 5x5 meter.
For the detection at least one LPR antenna must be measured at 10
“popular places” in the
last 10 minutes. A
“popular place” is a position bin, visited for at least 10 times. If the
observed LPR antenna was never measured at any popular place, we assume the antenna
is broken.
The error value contains the antenna port of the broken LPR antenna. If the mapping of
antenna ports is not configured, the error value is set to -1.
10.6.2.4 0x06
– broken hardware component
The software FusionEngine communicates with the attached hardware components (sensors
etc.) via different interfaces (e.g. RS-232, TCP sockets etc.). If an communication timeout
occurs at one of these interfaces, the respective hardware component is marked as failed.
This error code can also caused by wrong FusionEngine configuration.
The error value contains the index of the concerned FusionEngine node. To find out the
hardware component of a FusionEngine node, the FusionEngine logfile must be analyzed.
