Limitations are software or hardware issues that cannot be fixed. For certain limitations, workarounds are documented.
AutoVu™ Genetec Patroller™ 6.5 includes the following known limitations:
|1190417||Two Patroller vehicles cannot monitor the same long-term overtime zone using Plate link. Plate reads are kept for a limited time.|
|472102||In SharpX mobile installations where the SharpXS LPR Processing Unit includes the Navigation option, the LPR Processing unit must not be installed with the face plate pointing down or up. For more information on hardware orientation, refer to the AutoVu Hardware Guide for SharpX Mobile Installation.|
|296429||Time limited parking: If the configured "Duplicate hit delay" period is greater
than the Overtime rule, duplicate hits are raised during that period.
Workaround: Always configure the Overtime rule to be longer than the duplicate hit delay period.
|227487||To use overtime enforcement over a period of 24 hours or more, the Overtime rule regulation Applicable hours must be set to All Day. If Applicable hours is set to a time range, then an overtime hit is not raised on the second day. For example, if you have a 1 hour overtime rule that is configured with a specific time of day of 8:00-18:00 and is applicable all week long, a plate read on Monday at 17:00 will not raise a hit on Tuesday if it is read at any time between 8:00-18:00.|
|225947||When creating a New Wanted without entering an expiry date, the entry will expire based on the Store Hits setting (default is 120 hours). You can edit the expiry date but once it is edited, you cannot edit it again to set the value back to undefined.|
|213853||When using the Plate Copy plugin with Copy plate number to Windows clipboard setting enabled, the plate number copied to the XML file does not correspond to the plate number that was selected in Genetec Patroller™ for overtime and shared permit hits.|
|134674||If multiple plates have the same plate number but different issuing states,
provinces, or countries (for example, ABC123 from NY and ABC123 from NJ), hotlist or
permit list changes transferred to Genetec
may not be accurate.
NOTE: This issue occurs with live hotlist or permit list transfers only; USB transfer is not affected.
Workaround: To avoid this issue, make sure you are running the latest versions of both Security Center and Genetec Patroller™.
|100763||Windows 7: If you install Microsoft update KB2670838, context images of license
plate reads might not appear in Genetec
Workaround: Install update KB2836502. For more information, see https://support.microsoft.com/en-us/kb/2836502.
Patroller™ raises permit and shared
permit hits for the same vehicles that already have similar hits pending
acknowledgment. For example, if Genetec
raises a permit hit for license plate ABC123, it should not raise another permit hit
for that plate (for the same violation) until you either accept or reject the first
Workaround: Whenever possible, accept or reject hits as they occur. Try not to leave many hits pending.
|59320||After you acknowledge (accept or reject) a hit in Genetec
Patroller™, the hit icon on the map turns grey, which
is the same color as a read. As a result, you cannot differentiate between reads and
acknowledged hits by looking at the map. This applies to all types of hits (hotlists,
permits, overtime, etc).
Workaround: To view acknowledged hits in Genetec Patroller™, tap Hits, and then tap Review.
Patroller™ switches from live reading to
the list of unacknowledged hits, even when new hits are automatically rejected. For
example, when you set an acknowledgment buffer, you specify a limit to how many hits
can remain unacknowledged before Genetec
rejects all subsequent hits. After this limit is reached, a hit causes Genetec
Patroller™ to switch from live plate reading to the
list of unacknowledged hits, even though the new hit is automatically rejected and
does not require user interaction.
Workaround: You need to switch back to live reading every time you receive a new hit, or clear the list of unacknowledged hits.