Go to Post Sustaining an FRC team is really hard! - Jared Russell [more]
Home
Go Back   Chief Delphi > FIRST > General Forum
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
Reply
Thread Tools Rate Thread Display Modes
  #16   Spotlight this post!  
Unread 21-03-2010, 22:09
Radical Pi Radical Pi is offline
Putting the Jumper in the Bumper
AKA: Ian Thompson
FRC #0639 (Code Red Robotics)
Team Role: Programmer
 
Join Date: Jan 2010
Rookie Year: 2010
Location: New York
Posts: 655
Radical Pi has a spectacular aura aboutRadical Pi has a spectacular aura aboutRadical Pi has a spectacular aura about
Re: Finding problems too late

Quote:
Originally Posted by pfreivald View Post
In all robot code -- not just ours, but all robots from the coolest of automobile assemblers to the humblest of photocopiers -- there is a subroutine that we call 'Secret Subroutine C'. You cannot delete it, and you cannot in any way remove it, even by reformatting everything and starting over. The best you can hope to do is minimize (not prevent) the chances of it executing, and minimize the damage caused when it executes. It reads only one line, and roughly translated from machine code into English, it reads:

"Run amok and destroy your masters."
Oh, that happened to us once . One of our matches we lost connection to the cypress. I switched the controls over to the compatible mode to show our drivers what they could do if the cypress board failed again, and then I switched it back into cypress mode. I didn't realize the last guy hadn't disabled the bot, and that when the cypress is gone all of the inputs go high, so when I switched it all of the controls defaulted to on and suddenly our kicker starts spinning at full speed, the winch starts running, and the pneumatics to raise our arm activate. I disable it before the arm actually gets enough pressure to raise (something that can be very dangerous if you've seen our bot), but the mentors are instantly questioning me about how it could all activate on it's own. It takes a while for me to explain how I know the exact reason for it.

Oh, also when we were queuing for a match one of our guys bled the air from the pneumatics (I have no idea why) and forgot to close the valve. We spent that match mostly crippled, since our arm needs pneumatics, our kicker needs pneumatics as well, and all we can do is drive around. We promptly put a nice big sign next to the valve that says "close me". Next match? We forget to unwind our winch before the match and our arm gets stuck.
__________________

"To have no errors would be life without meaning. No strugle, no joy"
"A network is only as strong as it's weakest linksys"
Reply With Quote
  #17   Spotlight this post!  
Unread 21-03-2010, 22:23
Jeff Pahl's Avatar
Jeff Pahl Jeff Pahl is offline
likes to look at shiny things...
FRC #5148 (New Berlin Blitz)
Team Role: Engineer
 
Join Date: Oct 2004
Rookie Year: 2004
Location: Waukesha, WI
Posts: 344
Jeff Pahl has a reputation beyond reputeJeff Pahl has a reputation beyond reputeJeff Pahl has a reputation beyond reputeJeff Pahl has a reputation beyond reputeJeff Pahl has a reputation beyond reputeJeff Pahl has a reputation beyond reputeJeff Pahl has a reputation beyond reputeJeff Pahl has a reputation beyond reputeJeff Pahl has a reputation beyond reputeJeff Pahl has a reputation beyond reputeJeff Pahl has a reputation beyond repute
Re: Finding problems too late

Quote:
Originally Posted by yoshibrock View Post
I was just wondering if anyone else has stories of discovering problems too late, because it's nice to share silly mistakes and to learn from them.
You mean like when we were sitting on the floor of the hotel hallway Friday night eating pizza, and we started giving the driver a hard time because the robot was moving like it was under the control of a drunk driver about half the time, and his response was "it would help if when I turned the joystick to the left, the robot turned to the left instead of the right..." (We were using a 3-axis joystick, and turning the stick was supposed to turn the robot). We all looked at the programmer, whose only response was "oops" and then he disapeared to his room to fix the code.
__________________
Team 5148 - 2014 Wisconsin Regional Rookie All-Stars!!

Mentor: 1379: 2004-2008 / 2530: 2008-2013 / 2861: 2009 / 5148: 2014-??
Lead Robot Inspector: 10,000 Lakes '09 - '11 / Lake Superior '11-'12 / Northern Lights '13, '15 - '16 / Championship '09 - '12, '14 - '15
Attending/Inspecting 2017: TBD, Wisconsin, STL Championship

"Sometimes the questions are complicated and the answers are simple" -Dr. Seuss
Reply With Quote
Reply


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Not Too Late For NURC falconmaster General Forum 10 07-04-2008 16:52
pic: Too bad it's too late.... Cody Carey Chit-Chat 20 31-05-2006 16:54
[FVG] Too late to join? Matt Krass FIRST-related Organizations 3 28-10-2004 21:36
Too late for 2004? nwagers Starting New Teams 16 30-09-2003 11:56
too late to register? RobDeCotiis Championship Event 8 09-04-2002 18:46


All times are GMT -5. The time now is 14:42.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi