Any idea on why the tracks stop? The config seems okay as I've verified the speed with a radar gun. #177
Comments
|
I've uploaded a video (too big for here sadly) That is about a minute long on imgur where you can see it's done it at the start and a couple more times throughout. |
|
Sorry, I can't help but since you have more or less an identical setup to me, I'd be interested in seeing your Would appreciate your help if you don't mind and sorry for the OT post! |
|
If you want to maybe message me on discord? I've made a channel https://discord.gg/8mfZGAaR - that way, hopefully the main GH issue stays true to it's intent. I notice I found it difficult to capture my car, but that was when I was INTENTIONALLY speeding through the target area. I've also now changed my calibration so that to the camera/code the line is straight, rather than a hill. I am hoping this means I can make the target area smaller. I'm not sure if having a very long target area (red box) is a good or a bad thing or a bad thing, I'm starting to think it's necessary to capture FAST cars as they're gone before the app can even get the number of suggested points in many cases. Did you try dropping down to the 480? I have a feeling that opencv has too much processing to do, if your target are is too big. I/you could always test this by running the code on my pc 13900k, etc and a RTSP camera. There'a an iPhone app I downloaded and experimented with for £2.99 it was called IP Camera Pro, it's a black camera with a white wifi type symbol in the logo which is on a black background https://apps.apple.com/gb/app/ip-camera-pro/id990605467 The weather sucks here today so I won't be going out, but I may edit the code and use my iPhone 15 pro as an RTSP camera and have a play about with the settings. |
I am using a RPI5 8GB with the Official Camera Module 3 Wide, which is static on a little tripod stand and the picam480 config. The only changes made were to bring the alignment down from where it was aimed and calibrate it at about 150px for the average car and UK cars are somewhere between 4400-4700mm in length.
The red car that was captured below was also verified at exactly 25mph using a radar gun, so in terms of overall speed tracking it seems okay but certain things it seems to start tracking and then give up on.
Running headless and just watching the logs via ssh. Nothing else, other than the web server are running.
Here is a snippet of some of the logs of my issue, it seems that fairly often, part of the way through the 6 tracks it'll just stop or lose track of the car? Then after some time (presumably when something else comes along) it'll start tracking that.
^^
Above is one of the captured images of where it has tracked and saved something over the 25mph limit I'd set.
The config is the picam480, with only the alignment area moved down as it was originally targeting the houses opposite.
Average sized car is about 150px and car sizes in the UK range from about 4400-4700mm roughly.
Then you have ones like this where the car is very likely to exceed my target.
2024-09-27 13:59:54 INFO speed_camera New - 0/6 xy(188,6) Start New Track
2024-09-27 13:59:54 INFO speed_camera Add - 1/6 xy(213,8) 24.55 mph D=25/30 C=5 46x25=1150 sqpx L2R
2024-09-27 13:59:54 INFO speed_camera Add - 2/6 xy(229,5) 20.08 mph D=16/30 C=6 47x30=1410 sqpx L2R
2024-09-27 13:59:54 INFO speed_camera Add - 3/6 xy(257,0) 24.55 mph D=28/30 C=8 41x22=902 sqpx L2R
2024-09-27 13:59:54 INFO speed_camera Add - 4/6 xy(281,0) 24.09 mph D=24/30 C=8 38x18=684 sqpx L2R
2024-09-27 14:00:58 INFO speed_camera Reset- event_timer 63.47>0.30 sec Exceeded
but it also happens on ones where it the car is much slower, as in this example.
It is the type of road where there can be a queue from the bottom which might enter the red area, but at this time of the day that isn't the case.
It either seems to go through all 6 adds smoothly or it does 2/3/4 and then pause, like this:
The text was updated successfully, but these errors were encountered: