FIRST Robotics Competition Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

Intermittent camera connection, with error

On our practice robot (before we started building the actual 2011 robot) we were using the veteran Axis camera with 2011 code. It would intermittenly lose connection or not connect at all when we cycled power to the robot. There would be an error in the Diagnostics driver station tab. I don't have the actuall wording, but I think it related to setting up the IP address or network settings of the camera as the robot was booting up. I remember that it said we were using an un-allowable name or character and it listed the characters that were allowed. We thought this might from the Begin VI, but we did not change the default IP constant or anything else, except the frame rate and compression constants. We think it might be that our crossover ethernet cable wiggles in just the right way to loose connection, since this has clearly caused problems before. But then why the unique error?

Thanks in advance for your help!! We meet again this Monday, so I will check back again then. We do have another cRIO connected to last year's robot that we could use to test any solutions out with. Our current robot is being built and can't be used yet.

0 Kudos
Message 1 of 4
(4,719 Views)

Several teams have had problems in the past with intermittant power connections to the camera, or with mounting methods that will sometimes press the reset button. Could either of those cause your problem?

0 Kudos
Message 2 of 4
(3,209 Views)

I don't think so, especially because we got a unique error, not just a "lost connection to camera" error. But it still is a possibility. This thread on Chief Delphi is releated, we will check this out too.

http://www.chiefdelphi.com/forums/showthread.php?p=1022485#post1022485

0 Kudos
Message 3 of 4
(3,209 Views)

I stumbled across a thread on Chief Delphi that gave the exact error we got and explained it as happening when the camera isn't booted up yet and the cRIO tries to talk to it. This seems to explain our scenario quite well, so I am taking this to be a non-issue. We also got our robot up and running a couple of days ago for the first time (a little late huh? ) and we weren't having major problems with the camera on this issue.

0 Kudos
Message 4 of 4
(3,209 Views)