|
Re: Finding problems too late
Quote:
Originally Posted by pfreivald
Oddly enough, we had exactly that problem with mecanum wheels this year. They were all labeled properly, but somehow someone had managed to switch them around. It was a frustrating programming switcharoo obnoxious time trying to debug the code and figure out why nothing was quite working right and then it was 'oh, change those out' and everything worked fine.
Remember how this works:
Mechanical blames electrical.
Electrical blames programming.
Programming blames mechanical.

|
On our team:
Mechanical blames programming.
Programming blames electrical.
Electrical blames the newbies.
Yeah.
Yesterday at our last qualification match at Silicon Valley the robot wouldn't respond at all and just sat there all match. Afterward we powered it on in the pit and everything worked. We'll never know for sure what went wrong, but the most likely explanation seems to be that we didn't plug in the ethernet cable to the radio.
It didn't help either that in our second to last match we were flipped during autonomous and were upside down for the rest of the match. Not really an impressive show for the top 8 to want to pick us. Heh...
__________________
cout << "Hello, robotics. Goodbye, world." << endl;
"The two-axis accelerometer provided in the kit of parts (shown in the picture below) is a two-axis accelerometer." - WPILib User's Guide
Last edited by Al3+ : 21-03-2010 at 15:24.
|