pageauc
commented
3 years ago Run ./speed-cam.py in ssh or terminal session and view the logs. You should see what is causing the issue. I suspect you are getting a lot of track event timeouts. The default is 0.3 sec. Opencv just has to process too much data in a 720 image. You could try reducing the tracking window size by uncommenting the following config.py settings This will override the auto calculation of motion tracking window.
x_left = 50 # uncomment and change values to override auto
calculate
x_right = 300 # uncomment and change values to override auto
calculate
Allow user to customize the motion crop area (height) y values
If variables not found then values will be set automatically base on
image size.
y_upper = 60 # uncomment and change values to override auto
calculate y_lower = 150 # uncomment and change values to override auto calculate
then make sure following setting is set to True (default)
image_show_motion_area = True
720 resolution image is 1920 x 720 so start with a very small tracking window size. roughly equivalent to what you would get with the autocalculated 320x240 resolution. Numbers have been changed to position window near the center of the camera image. You can change these to suit.
x_left = 600
x_right = 850
y_upper = 300
y_lower = 390
You will need to repoint the camera to put the motion area in the tracking window. I sometimes move my hand in front to trigger motion tracking so I can see where the window is pointed Depending on what logs say you can tune other parameters per comments These will be in the Motion Tracking Settings section of the config.py file eg track_counter = 4
Make sure the camera is at least approx 50 ft away or more or you will have problems tracking since a objects will take up so much of the camera view.
Give these suggestions a try and let me know how you make out
Also see https://github.com/pageauc/speed-camera/wiki/How-to-Tune-Motion-Tracking-Settings
Regards Claude ...
On Sat, Jul 17, 2021 at 4:45 PM jameshfischer @.***> wrote:
using default low-rez 240p plugin, all is well, but changing to webcam720, and appropriately changing parameters within that file results in calibration mode that never see any motion at all.
Motion is certainly detected, but it does not result in a trigger.
What would be some "good guess" settings for detection box size with the webcam720 plugin?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/pageauc/speed-camera/issues/95, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABNPKZBMDNCXERJ74HKEKW3TYHTXBANCNFSM5ARM775Q .
-- YouTube Channel at https://www.youtube.com/user/pageaucp http://www.youtube.com/user/pageaucp GitHub Repository at https://github.com/pageauc
jameshfischer
bushibot
using default low-rez 240p plugin, all is well, but changing to webcam720, and appropriately changing parameters within that file results in calibration mode that never see any motion at all.
Motion is certainly detected, but it does not result in a trigger.
What would be some "good guess" settings for detection box size with the webcam720 plugin?