Rev 031109
43
•
Added support for the
LogViewMaxRows
and
LogExportMaxRows
configuration
properties in the
c:\uvss\blogic.ini
file to control the maximum number of events that can
be displayed in the GUI event table and exported to CSV files, respectively. The
properties can be optionally specified as part of the
[GUI]
category, as in the following
example:
[GUI]
LogViewMaxRows=1000
LogExportMaxRows=5000
•
Added support for the
MOTION_COUNT_FILTER
and
MOTION_RANGE_FILTER
configuration properties in the
c:\uvss\blogic.ini
file to
fine-tune the algorithm used to filter out false alarms.
a.) If MOTION_COUNT_FILTER is an integer greater than 1 (default value is 2),
then the server will wait for a consecutive number of motion events before generating
an alarm. This prevents alarms from being generated for spurious motion events.
b.)
If MOTION_RANGE_FILTER is a decimal value greater than zero (default
value is 0), then the difference between the first motion event range and last motion
event range (as determined by the MOTION_COUNT_FILTER) must be greater than
or equal to the MOTION_RANGE_FILTER value (specified in feet) in order for an
alarm to be generated. This prevents alarms from being generated unless two or more
consecutive motion events occur with a “decreasing” range (i.e., target moving
towards the sensor).
- For example, suppose MOTION_COUNT_FILTER is specified as 2 and the
MOTION_RANGE_FILTER is specified as 0.5 feet.
- If the first motion event occurred at a range of 10 feet and the second
consecutive motion event occurred at a range of 9 feet, then an alarm would be
generated.
- If the second consecutive motion event occurred at a range of 9.6 feet, then an
alarm would not be generated at that time. However, if the 3
rd
consecutive motion
event occurred at a range of 9.2 feet, then the alarm would be generated.
•
Added support for the
INCIDENT_DEBUG
configuration variable which allows
technical support staff to log incident processing information for a given sensor. For
example, if the INCIDENT_DEBUG variable is set to “3”, then only the incident
processing information for Sensor 3 will be output to the server log. The amount of
debug information generated could be quite large, so this configuration variable should
be used only when actively trouble-shooting event filtering problems.
•
All server logs have been moved from the
c:\uvss
directory to the
c:\uvss\logs
directory
to better organize the server runtime directory.
•
Created a new daily maintenance log in
c:\uvss\logs
to assist with trouble-shooting
maintenance issues.
