View Single Post
  #7   Spotlight this post!  
Unread 01-04-2003, 04:02
DougHogg DougHogg is offline
Robot-A-Holic
FRC #0980 (The ThunderBots)
Team Role: Coach
 
Join Date: Jan 2002
Rookie Year: 2002
Location: S. California
Posts: 324
DougHogg has much to be proud ofDougHogg has much to be proud ofDougHogg has much to be proud ofDougHogg has much to be proud ofDougHogg has much to be proud ofDougHogg has much to be proud ofDougHogg has much to be proud ofDougHogg has much to be proud of
Re: Failure of Robot Interface

Quote:
Originally posted by Matt McNelley
Anyone who saw our first round of the finals at the Midwest Regional knows that we didn't function at all after sustaining an impact from another robot. It was thought at first that it was a battery problem, and that is what you heard from the announcer if you watched the webcast, or were there. Well, the problem was not a battery connection, or any other kind of external connection for that matter. Immediately following the round, we gave all the connections a thorough inspection, and could find nothing wrong with the robot. We were still getting power, but we had no radio communication. Well, one of the engineers gave the console a couple of taps and it came back to life. Something inside of the actual component of the radio equipment must have broken. Whatever it was, it definitely didn't help us out any.

Has anyone else had problems of this sort?
We had some similar and very weird problems last year where we would suddenly loose connection while at our school. Once we changed a fuse near the modem port and the problem went away, so we thought we had solved it.

Then just prior to the Summer Classic last summer, we had the same problem again and changing the fuse did nothing.

We then did a major rewire job with a different circuit breaker panel, and once again all went well.

Later, we had the same problem again. An additional symptom that appeared and seemed related was that our robot sometimes did strange random things, motors twitched off and on, the light went on and off, and these things occurred repeatedly and together. More than once, we had a cyclical connecting/ disconnecting occurring with the light going off and then on again every second or two, while the motors activated and deactivated. We also had the no data light turning on. It seemed like our robot was betwitched.

We tried a lot of different things to try to handle it. Finally we changed out the radio on the operator interface and since then no problem. This time, the solution seemed to be clear in our case, in that the problem kept occurring and then the second the radio was changed, it was gone and never came back. (We had tried tightening the connections from the radio to the operator interface and changing the radio wire, with no success.)

Hope the data helps in some way.

Good luck guys. I know it is not fun, especially during the finals of a competition.
__________________
FIRST Team 980, The ThunderBots
2002: S. California Rookie All Stars
2004: S. California: Regional Champion,
Championship Event: Galileo 2nd seed,
IRI: Competition Winner, Cal Games: Competition Winner
2005: Arizona: 1st seed
Silicon Valley: Regional Champion (Thanks Teams 254 and 22)
S. California: Regional Runners Up (Thanks Teams 22 and 968)