Quote:
|
Originally Posted by Danny Diaz
Sounds like a classic problem of the backup battery being too low - we've seen issues just like this that have been solved by replacing with a FRESH battery. Obviously if your CMUCam2 is able to talk to LabVIEW then you don't have a traditional "communication problem", but your battery doesn't seem to have enough juice to sustain the communications (or there's an intermediate short, very likely with PWM cables from IFI - several our PWM cables were bad). If you do something in-between grabbing frames, it would appear to me that would give the battery a [small] chance to recover.
-Danny
|
Our team also continually sees the problem that the original poster is talking about.
We have used two different backup batteries, both fully charged. The problem was still observed.
Note that when I say "continually", I mean that we consistently get the problem on an inconsistent basis. Sometimes we get it immediately at the start of the work session and it lasts through several restarts of LabView and RC/Camera power cyclings. Other times, things work for a little while (we can grab 2-3 frames), but then we get the OP's problem of LabView not responding to input, not getting the frame that was asked for, and the frame grab progress bar continually filling up and starting over. This persists until we restart the LabView CMUCam GUI application. After restarting, it might or might not occur again immediately. It is consistently inconsistent as to when it works.
If it is really thought to be a power supply issue, then I will try to make an effort to rig up a non-battery supply and run the camera off that. Maybe the OP or someone else having the same problem can do the same (just use any standard DC power supply that fits the specs outlined in the CMU Cam docs).
Hope this helps to diagnose the problem.