Hey !
i was just woundering why our camera is acting weird… we got really bad frame rate… is there any way to imrove this ?
and we also got a very bad delay problam too.
Bad frame rate on your driver station? Generally you run the frame rate lower in the programming to make sure the image processing can keep up. If I remember correctly we run it around 13fps.
If the delay is noticeably bad(talking like .5-1second delay) then there might be something wrong, but I’m not sure were you would start trouble shooting for it.
It takes about 2-3 seconds from the moment I move the camera to the moment I get it on the driver station it self…
And I dont really know how to check exactly how much FPS I get but its not that good.
Another thing is the focus- why there is no auto focus or something? its kinda stupid that it can only focus on objects that are far away or really really close…
What language and computer?
The focus is something you will have to set by rotating the lens. Why no autofocus? Cost and design.
As for the frame rate, perhaps you can describe the settings of the camera?
Greg McKaskle
what settings are there ???
If you use C++, there is a member function for the AxisCamera class called writeCompression. You might want to try to increase the compression. This could yield faster refresh rates. We see the same slow rates and large delay times and plan on trying this tonight.
- Bryce
Off the top of my head, the camera has a setting for image resolution which will have the largest effect on speed. It has a setting for compression which affects the amount of data being transmitted, but didn’t have enough effect to be worth worrying about – but be careful of very low and very high numbers. The other settings are exposure, exposure priority, and brightness. Then there is one for sharpness and one for color saturation.
Greg McKaskle
With the new 2010 Vision API, is framerate not configurable?
We noticed the framerates we get at the DS are pretty atrocious with a large delay - more than 1 second. However the cRIO itselfs seems to be able to process Ellipses at around 5 fps based on our tests at 160x240 resolution.
Does the API try and set the camera to 30fps by default?
the API tries for 15fps but that dosen’t mean it achieves it.
Using LabVIEW slightly modified default code, we can get a good framerate on the dashboard, enough to aim well manually. I have tried local and remote dashboards. The delay is generally around 1 second.
There are three available resolutions - we are using the medium one (default).
The camera setup has a configurable FPS, but setting it higher than the crio can actually process obviously isn’t going to produce a higher framerate.
If you double click the find circle sub vi you can find a timer in ms of the processing time. Ours today was running anywhere from 25ms at lower resolutions to 40 ms with tight tolerances. In FPS terms, that’s 40 fps at the high end and 25 at the low. I’m not sure if I quite believe that or not… last year we were only seeing in the range of 10 fps.
The new camera software processes an 8-bit greyscale image, the old camera software processed a 32-bit RGB image. That saves alot of processing. Thus, it should go 4x as fast. It won’t go 4x as fast, but it will still go faster.