Quote:
Originally Posted by Steve Warner
This may seem like an odd question but does the size of the file change depending on the complexity of the image being processed. We had our C++ code running like it should, made a very simple change, like reading an analog value, and the processor suddenly slowed down. I was sending a printf to the console to check the analog value and I noticed it was slow and downloads started taking about 20 seconds instead of 4 or 5. I commented all of this out and it still runs slow. I remember when I first started last night the camera was pointed up toward the ceiling with very bright lights and a dark ceiling. A very simple image. At some point I moved the camera to look across the room which was a very busy image. Before I left last night I didn't think to aim it back at the ceiling to see if the system speeded up. I did check the camera config and it had not changed (160x120, 30 compression, 10 frames/sec). Is there another setting that I'm missing? Any ideas?
|
The image size definitely changes with image complexity, but I would guess that's not the source of the slowdown. Perhaps you are getting a lot of particle detections that all need to be analyzed. Also, you should have your vision processing in an independent task, so as not to affect your robot control rates.
When you were seeing slow downloads, do you mean downloads of images or of new robot programs or what? If it was slow to run your code, you probably have some task that is chewing up the CPU and need to reboot your cRIO.
Another common source of slow downs is camera exposure. If you are shining a light directly into the lens, the camera can run full speed. If it's a dim scene, it can make the image stream significantly slower.
-Joe