Why does an XProtect match-list alarm fail after the plate is recognized?
Answered by ANPR AI·Sourced
Short answer
A list match needs an associated event to trigger the intended workflow.
Explanation
Successful OCR does not by itself configure an alarm action.
Things to check
- Plate entry
- Events triggered by list match
- Downstream rule
What to do
Select the required event in the match list and verify the rule action with a fresh recognition.
Was this answer helpful?
Your vote decides which questions we answer next.
Cloud API
Test plate and vehicle recognition on your own images.
Send a photo or camera frame to our API and get the plate, country, make and model back as JSON. Start free, or run the same models on your own servers.
- 100 free credits every month, no card
- Plates for Saudi Arabia, Qatar, Kuwait, Bahrain and Oman
- Cloud API or on-premise deployment
What to read next
ProductCloud ANPR APISelf-serve plate and vehicle recognition API with a free tier, or run it on-premise.Read GuideConnect an IP camera to ANPRStep-by-step: RTSP streams and snapshots from the cameras you already have, sent to the API.Read ComparisonANPR camera alternativeWhat a dedicated ANPR camera costs against a standard IP camera plus plate-recognition software.Read
Related questions
Why is my Milestone XProtect LPR server CPU usage hitting 100%?Why does XProtect LPR ignore plates that look readable on screen?Why does XProtect recognize only fragments of a number plate?Why does XProtect LPR reject a foreign plate but read local plates?
Browse all ANPR questions
Comments
Add a comment
Share what worked for you, or ask about a detail in this answer.