During our week 1 event, we tried using the microsoft webcams found in first choice as a driver feed to find balls behind the hub, but even after dropping the resolution to 160p, the latency was several second and the fps was about 5 making it unusable?
Does anybody know of a fix for this issue either in software or a better camera?
There could be a lot of issues that you may be seeing. High CPU usage on either the roboRIO or your driverstation laptop could cause low FPS, high bandwidth usage by higher priority data, among other issues that don’t spring to my mind immediately. I think that camera stream data is among the lowest priority data coming from the robot, I might check for errant print statements to console that run every iteration.
A good place to start may be to look at driver station logs for anything that looks irregular: Driver Station Log File Viewer — FIRST Robotics Competition documentation
That might be the cause. We have some suffleboard logging for some things we used during testing and that could be the cause.
If it is only a couple things, I doubt it is the root cause. I’m talking 12+mbps of text that is getting in the way of the camera
How did you drop the resolution?
I think the programmers used the dropdown menu in dashboard but I am not sure exactly how that works.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.