Quote:
Originally Posted by ThomasClark
Is it a seconds second latency, or is it only getting one frame every two seconds?
Also, are you running on the RIO, or another processor?
I think this is actually a good way to track the targets. Using the target positions directly as the input to a feedback loop will result in a lot of overshooting, since reading gyro values has a lot less lag than real-time computer vision. Maybe you can just make the process more automated, so the driver can hit a single button and set the whole thing off?
|
What is a seconds second latency? It gets anywhere from 13-29 fps.
We are running it on the roboRIO.
How would we adjust for overshooting? We had it working pretty well but it would always end up past the point where we want it and it wouldn't be very accurate.