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.
We could not see ANY WAY to code around this. Can we check for the camera somehow and not execute the Initialize if we don't find the camera present so our robot will continue to initialize and execute the rest of our code?
|
One of the things that we would most certainly be doing is using a switch on the robot, and a switch on the OI, to control whether or not the any of the camera code is used. Using a switch on the OI would be a little trickier than one on the robot, in that you have to make sure that you get a packet through to read the switch before attempting any code related to the camera. This strategy is not quite automatic, but it can be used to get the job done and it is a good idea, in general, to place PID systems and such under conditional control in this manner.
I have not looked at the details of the camera initialization code yet, but it should be possible to run a simple handshake with the camera and detect that the handshake is taking too long. You can then set a variable indicating that the camera is off line.
Eugene