|
Re: Axis - Image Lag
The dashboard and cRIO have largely independent sessions to the camera. I suspect that there are settings which are shared between them, but I think I've also seen that the robot can request one image size and the dashboard another, and the camera gives everyone what they ask for.
I do not believe that setting the camera setting on the cRIO to 640x480 is a good move. It takes about 100ms to decode that image, and I don't see how it will improve the framerate to the dashboard.
If you are working on a good framerate to the dashboard, you can open the source to it and change the settings in the sample code. It uses the default cluster of 30,30,320x240 -- 30fps, 30% compression, and 320x240 pixels in size. Create the cluster constant if you want to make changes.
Before doing that, I'd add a loop timing to see how often it runs and see if you can determine the cause. One thing to watch for is low lighting. The camera will lengthen the exposure if the light levels are too low. This is unlikely to happen at competitions, but could easily happen in a practice or shop environment.
Greg McKaskle
|