Limitations are software or hardware issues that cannot be fixed. For certain limitations, workarounds are documented.
AutoVu™ SharpOS 12.7 GA includes the following limitations:
|2149700||Using the Optimize for static image background feature is not recommended if only a small part of the image background is static, for example, if many moving trees are visible. This is less likely to happen in installations where the camera is tilted downwards. It is not recommended to use this feature in conjunction with Virtual Loop when vehicles are traveling at speed above 50 km/h (30 MPH).|
|2148472||When updating the SharpV using Internet Explorer, the upgrade might fail if the Windows feature Enable 64-bit processes for Enhanced Protected Mode is not enabled.|
|2139127||It is not recommended to use Virtual loop in conjunction with the Optimize for fixed installation feature when vehicles are traveling faster than 50 km/h (30 MPH).|
|2136538||Following an upgrade to SharpOS 12.7 or higher, the browser is refreshed and points to https://<SharpV IP address>:443. If the network topology uses a NAT, the browser will not be redirected to the Sharp Portal unless port forwarding has been configured for access to the Sharp Portal.|
|2135241||When recording video from a SharpV from the Dashboard > Camera feeds page of the Sharp Portal, after clicking Cancel, the record button still shows "Stop recording".|
|2030186||When a SharpV is enrolled under the LPR
Manager using the LPM protocol, if you then modify the configuration to use the
Center (legacy) extension, a second
SharpV entity is added to the LPR Manager.
Workaround: To ensure that the reads that were made using the LPM protocol are still accessible, merge the reads from the two entities using the Unit replacement tool in Config Tool.
|2025741||When a SharpV is configured to use the Security Center (legacy) extension with the This unit manages the connection to Security Center feature enabled, if the main server fails, the unit cannot connect to the failover server.|
|1959475||After upgrading a SharpV to use the LPM protocol, the auto-generated self-signed certificate that is included with the SharpV is not automatically installed on the server machine.|
|1951944||If a SharpV is added to the LPR Manager using the LPM protocol and the extension is then changed to Security Center (legacy), a duplicate offline SharpV is added to the LPR manager so that locally-stored plate reads can be retrieved.|
|945150||When configuring the virtual loop, the zoom level of the LPR and context cameras must be adjusted so that the context camera field of view is more than double the width of the LPR camera field of view.|
|944854||The Speed estimation feature uses the width of the license plate to calculate the vehicle's speed. When this feature is used in regions where there are multiple license plate widths, for example, if trucks use different sized plates than cars, speed estimation can be inaccurate.|
|942672||The speed estimation feature is less accurate in countries where the license plate dimensions are not uniform. Speed estimation is also less accurate because some plate features (for example, logos) can make the plate appear smaller than it is.|
|900724||If the LPR camera fails to capture a vehicle’s license plate and the vehicle is then detected by the virtual loop, a NOPLATE event is only generated when the vehicle leaves the camera's field of view. In the case where the vehicle is still within the field of view when it exits the parking lot, the parking attendant is not notified of the NOPLATE event until after the vehicle has left the parking lot.|
|781714||When using the Optimize for static image background feature, the system can sometimes read plates in the image background after a vehicle or pedestrian passes in front of the camera.|
|741365||When updating a SharpV from the SharpV
Portal using the Web Updater tool, the upload files might fail if you are using
Internet Explorer 11.
Workaround: Close the Internet Explorer task from your Task Manager, and then start a new Internet Explorer session to the SharpV Portal. Perform the update again.