Can you look at the .dat file in the viewer?
Any idea why this happens regularly and what can I do about it?Yeah, the logs on CPAI are not useful (unless you are seeing red, which means the module probably has to be restarted).
.DAT file is where all of the answers are. My guess is that it was canceled well before all of your images were sent.
I'll investigate further. It's just puzzling that so many cars are read perfectly and then randomly this occurs. My pre-trigger images was set to 4. I'll see what happens when I drop it down to 2. Thanks!Look at the other plate misses, if it's all the same pattern, where it would miss the plate if it wasn't found in the pre-trigger images (where the T values are negative) and a few in post, then you can try lowering the pre-trigger images to a smaller number (like 2) and see if that helps.
I agree with Mike, rather than triggering just on motion, setup a zone on the left of the screen and the other zone for the right of the screen. Then trigger based on crossing from one to the other. Now the plate should be close to the middle of the screen (or at least fully visible) and AI should see the plate.
I'm now at 2 pre trigger and 10 post trigger analyzing at 100msHow many post trigger images are you set to? You could try increasing that. If you don't have a lot of traffic-- make it seconds worth of data.
Did you add the zones and get it so it triggers when the vehicles are in the middle of the frame? With 12 frames, you've only got 1.2 seconds of footage to find an image with a plate. Plus your processing time is about 5000ms (5 seconds) so it's going queue them up and take about a minute to process that with your CPU.I'm now at 2 pre trigger and 10 post trigger analyzing at 100ms