@wittaj Did you try CP.AI Explorer UI to test LPR with image? Does that work?
It worked, but it must have been it was timed right when it started before it says Lost Contact.
@wittaj Did you try CP.AI Explorer UI to test LPR with image? Does that work?
Do you have Auto start/stop with Blue Iris checked? If so uncheck it.Anyone else seeing this. All of a sudden everything is coming back object not found and times were shooting to 30,000+ms.
This is what my display shows now - I tried stopping the service and restarting the computer and same problem persists of saying Lost Contact - it will make connection and then lose contact again.
View attachment 183729
I need to email Ken about the way he is pulling the Custom Model, I am see a lot of user having issues with this.Yep, it is unchecked.
I noticed the custom models were missing on that page, so I restarted yet again and finally it appears to be working. Go figure.
Getting the same issue. I'd have probably 900-1500 requests then lose connection and it'd restart.Anyone else seeing this. All of a sudden everything is coming back object not found and times were shooting to 30,000+ms.
This is what my display shows now - I tried stopping the service and restarting the computer and same problem persists of saying Lost Contact - it will make connection and then lose contact again.
View attachment 183729
I get this on every restart but it settles after a couple of minutes. Very high CPU and memory usage for the CPAI process while it happens (100% CPU and 2Gb+ memory usage for the process). Runs smoothly with GPU DirectML thereafter using 250Mb memory and less than 5% CPU. The 30 second duration is likely a timeout? I'm running 2.4.7 on an i7-11700:Anyone else seeing this. All of a sudden everything is coming back object not found and times were shooting to 30,000+ms.
This is what my display shows now - I tried stopping the service and restarting the computer and same problem persists of saying Lost Contact - it will make connection and then lose contact again.
View attachment 183729
The slowdown still exists. I have tried some fixes but no luck, I am still working on it.@MikeLud1. II the rockchip implementation stable now?
Is the slowdown problem still present?
Thanks.
If you’re still on 2.5.1 there’s an update to the yolov5.NET module (1.9.1) that should resolve this issue.Tried with 2.5.0 and New 2.5.1.
YOLOv5.NET 1.9.2 was just released to resolve the timeout issue.Well it fixed the "Lost contact" part, but still getting the 30 second timeout issue on yolov5.net 1.91
@ch3st3rk Given the details you shared, since you unticked main stream, BI5 should send substream image to CP.AI. Is substream configrued for that camera?
Also, please share screenshots for:
#1: AI tab for that camera
#2: The AI details for a triggered event.
Thanks I will have to take a look a little later, will using sub stream prevent the CPU spikes or is that quite normal when detection triggered to analyse AI object?@ch3st3rk If you don't have substream configured for camera, then BI5 has no choice but to use main stream image for CP.AI. Main stream image will take more CPU to do AI detect than substream image. Add substream to camera temporarily to see if it improves AI response time.
BTW, please send #2 requested screenshot, the AI analysis details for a triggered event. It looks like this:
View attachment 184884
To get this screen, when in BI5 console, on your left, hold down Ctrl key while double clicking on a triggered event thumbnail
Note the AI response time of <100ms in mine, and the image resolution in the upper right corner.
Ok thanks I will setup some sub streams and see how that goes and report back, thanks for your help!@ch3st3rk It's best practice to configure main+sub streams for every camera to reduce CPU load, especially if you have cameras with high resolution like 4k. You're not missing out, you still have access to the main streams for viewing.
In general, AI models are trained on lower resolution images so if your images are high-res like 4k, they will be downsized (takes time and CPU load) as part of AI detection.