![]() |
Name of camera task
Hi. Got the camera to the dashboard to work this weekend. Woohoo!
It has around a 2.5 second lag, is this normal, good or bad. I set it to 160 x 120 and tried setting max frames per second to 15. Setting FPS didn't seem to change the lag. I noticed that if you kill the robot code, the camera still appears on the dashboard because there is a separte camera task for it. What is this task called? It seems that when a new program is run (in memory for fast debugging) and the camera task is already running, then it won't reinitialize the camera, plus it sometimes dies with a kernal exemption. Is there a way to stop the camera task from code? Thanks, Brian |
Re: Name of camera task
At the moment, no. You will need to modify WPIlib: (From AxisCamera.cpp)
Code:
// TODO: Keep track of this so it can be shut down!2.5 seconds is bad, did you update the driverstation to 1.1, cRIO to v20 and WPILib to 4.3? |
Re: Name of camera task
I believe there is something to the effect of a DeleteInstance() function in wpi lib i'm not completely sure of its effects though. I do know that stoping cameras with it didn't seem to work out too well, and without source infront of me i can't say much else on it.
as for lag, try decreasing color depth or setting a moderate amount of compression (we use 50). are you running any image processing? it can slow things down quite a bit. let us know how it goes |
Re: Name of camera task
Quote:
|
Re: Name of camera task
Quote:
|
| All times are GMT -5. The time now is 13:46. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi