Flexreader™ 6.1 includes the following known limitations.
| Issue | Description |
|---|---|
| 1538479 | When plate reading is activated by a capture trigger, it can take few seconds before the Flexreader™ plugin begins processing plate reads. During this delay, a Connecting to camera… warning is generated. To minimize this delay, refer to the Best practices for Flexreader™ camera configuration. |
| 1392596 | When you delete the Flexreader™
plugin from Security Center, the system
gives you the option to delete the associated cameras from Security Center. Selecting this option does not
delete the cameras from Security Center and
the system displays the warning: m_sourceAppNotificationLookups has fallen
out-of-sync with the main m_tableEntityState dictionary. Workaround: Delete all cameras from the plugin before deleting the plugin. |
| 1290205 | If you delete a camera from the Flexreader™ plugin and then re-add the same
camera, it behaves normally and the video stream continues to be sent to the
Archiver. However, if you delete the camera from the Archiver and then re-add the
same camera, the plugin stops processing plate reads. Workaround: If you delete a camera from the Archiver and then re-add it, you must also delete the camera from the Flexreader™ plugin and then re-add it to the plugin. |
| 1285220 | When using a separate camera for context images in the Flexreader™ plugin, the license plate event can display the image of the ALPR camera instead. |
| 261595 | When the number of cameras connected to an instance of the Flexreader™ plugin exceeds the limits of the
hardware, the system can stop capturing reads from some cameras. Workaround:
|