View Single Post
  Spotlight this post!  
Unread 04-02-2006, 13:30
BradAMiller BradAMiller is offline
Registered User
AKA: Brad
#0190 ( Gompei and the Herd)
Team Role: Mentor
 
Join Date: Mar 2004
Location: Worcester, MA
Posts: 590
BradAMiller has a brilliant futureBradAMiller has a brilliant futureBradAMiller has a brilliant futureBradAMiller has a brilliant futureBradAMiller has a brilliant futureBradAMiller has a brilliant futureBradAMiller has a brilliant futureBradAMiller has a brilliant futureBradAMiller has a brilliant futureBradAMiller has a brilliant futureBradAMiller has a brilliant future
Re: CMU Camera kills robot controller if not found.

Quote:
Originally Posted by chakorules
We are thinking about the what ifs. What if our camera becomes damaged by a poof ball and doesn't work, the next time it powers up with a "Initialize Camera " function call, it's going to LOCK UP, and we are going to be a sitting DUCK.
Sorry I couldn't get to this sooner, but there is a new version of WPILib that you can try that has one second timeouts on receiving camera data. If no camera data has been received before the timeout, then zeros are returned for all values. So if your code starts seeing zeros coming back for everything, including confidence, servo values, etc. then you know that the camera is not working.

This only happens for the first time. After that, the camera will always return the last value it received.

This should be fixed in an upcoming release of EasyC, but to try it for now, you can download the library from my web site, unpack the .zip file and replace the copy of WPILIb.lib inside of the EasyC directory C:\Program Files\Intelitek\easyC for FRC\Frc\18F8722 with the copy of WPILib2k6.lib from the .zip file.

It has been tested, but bugs do happen, and I'd suggest keeping a copy of the old file that you are replacing.

Please post a message or send mail if you run into any problems.
__________________
Brad Miller
Robotics Resource Center
Worcester Polytechnic Institute