OCCRA
Go to Post I don't think Dean Kamen ever recieved a real degree. That doesn't make him any less of an engineer.:) - Adam Y. [more]
Home
Go Back   Chief Delphi > Technical > Programming
CD-Events   CD-Media   CD-Spy   FRC-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
Closed Thread
Thread Tools Rate Thread Display Modes
  #61   Spotlight this post!  
Unread 05-03-2008, 12:07 AM
chaoticprout's Avatar
chaoticprout chaoticprout is offline
can't wait for next years VRC
AKA: Michael Montazeri
FRC #1138 (Eagle Engineering)
Team Role: Alumni
 
Join Date: Nov 2004
Rookie Year: 2005
Location: West Hills, CA
Posts: 265
chaoticprout has a brilliant futurechaoticprout has a brilliant futurechaoticprout has a brilliant futurechaoticprout has a brilliant futurechaoticprout has a brilliant futurechaoticprout has a brilliant futurechaoticprout has a brilliant futurechaoticprout has a brilliant futurechaoticprout has a brilliant futurechaoticprout has a brilliant futurechaoticprout has a brilliant future
Send a message via AIM to chaoticprout Send a message via MSN to chaoticprout
Re: Silly Programming screw ups (funny)

Quote:
Originally Posted by EricH View Post
Are you keeping that "bug"?
Haha I was reffing and saw this, apparently he just shortened the time that the motors run, but the look on the drive teams faces as the bot accidently scored 6 balls was AMAZING.
__________________
2009 Los Angeles Regional - Chairman's Award
2009 Granite State Regional - Engineering Inspiration Award
2007 Los Angeles Regional - Engineering Inspiration Award
2006 Southern California Regional - Regional Champions
  #62   Spotlight this post!  
Unread 05-03-2008, 12:11 AM
Eric24's Avatar
Eric24 Eric24 is offline
Registered User
FRC #1138 (Eagle Engineering)
Team Role: Programmer
 
Join Date: Mar 2008
Rookie Year: 2007
Location: Northridge, CA
Posts: 30
Eric24 is an unknown quantity at this point
Send a message via AIM to Eric24
Re: Silly Programming screw ups (funny)

I modified the "bug" slightly so that the arm didn't go quite as far to prevent damage to the robot, but it was very convent since thats what I was going to work on next.
__________________

  #63   Spotlight this post!  
Unread 05-07-2008, 05:25 PM
slavik262's Avatar
slavik262 slavik262 is offline
We do what we must because we can.
AKA: Matt Kline
FRC #0537 (Charger Robotics)
Team Role: Alumni
 
Join Date: Jan 2007
Rookie Year: 2007
Location: Sussex, WI
Posts: 310
slavik262 is a splendid one to beholdslavik262 is a splendid one to beholdslavik262 is a splendid one to beholdslavik262 is a splendid one to beholdslavik262 is a splendid one to beholdslavik262 is a splendid one to beholdslavik262 is a splendid one to behold
Send a message via AIM to slavik262
Re: Silly Programming screw ups (funny)

At the Milwaukee competition, the programming port broke on our controller and we were forced to replace it with the previous year's controller. After re-wiring everything autonomous turns refused to work, yet teleoperated turning was fine. This problem wasn't solved until our next regional (Michigan), when I noticed that the wires for the drive train motors had been switched. The teleoperated code hadn't presented a problem because I had accidentall switched the inputs in the arcade-style drive code.
__________________
  #64   Spotlight this post!  
Unread 05-07-2008, 09:55 PM
Andrew141WOBOT's Avatar
Andrew141WOBOT Andrew141WOBOT is offline
WOBOT for Life
AKA: Andrew
FRC #0141 (WOBOT)
Team Role: College Student
 
Join Date: Apr 2008
Rookie Year: 2003
Location: Holland
Posts: 52
Andrew141WOBOT is an unknown quantity at this point
Re: Silly Programming screw ups (funny)

With our team, if there's a problem, the builders say its a programming problem. The programmers always think it's an electrical problem. What a suprise...
  #65   Spotlight this post!  
Unread 05-10-2008, 05:24 PM
slavik262's Avatar
slavik262 slavik262 is offline
We do what we must because we can.
AKA: Matt Kline
FRC #0537 (Charger Robotics)
Team Role: Alumni
 
Join Date: Jan 2007
Rookie Year: 2007
Location: Sussex, WI
Posts: 310
slavik262 is a splendid one to beholdslavik262 is a splendid one to beholdslavik262 is a splendid one to beholdslavik262 is a splendid one to beholdslavik262 is a splendid one to beholdslavik262 is a splendid one to beholdslavik262 is a splendid one to behold
Send a message via AIM to slavik262
Re: Silly Programming screw ups (funny)

On our team, even the electrical guys think it's a code problem. But the programmers know it's an electrical problem.
__________________
  #66   Spotlight this post!  
Unread 05-10-2008, 06:25 PM
ComradeNikolai ComradeNikolai is offline
Registered User
AKA: Nicholas
FRC #2603 (Team Hornet)
Team Role: Mentor
 
Join Date: Feb 2008
Rookie Year: 2008
Location: Medina, Ohio
Posts: 203
ComradeNikolai is a splendid one to beholdComradeNikolai is a splendid one to beholdComradeNikolai is a splendid one to beholdComradeNikolai is a splendid one to beholdComradeNikolai is a splendid one to beholdComradeNikolai is a splendid one to beholdComradeNikolai is a splendid one to behold
Re: Silly Programming screw ups (funny)

Yeah, I had that problem, too; our IR board didn't work, I was told to make it, despite it being wired wrong... that was fun. Then, once the wiring was fixed, it worked for a while. When it stopped, I was asked to fix my code (yet the code didn't change!)... ah, the joys of programming. Next year, I'm going to blame everything on the electrical team.
__________________
I cut myself shaving with Occam's razor.

  #67   Spotlight this post!  
Unread 05-10-2008, 06:30 PM
slavik262's Avatar
slavik262 slavik262 is offline
We do what we must because we can.
AKA: Matt Kline
FRC #0537 (Charger Robotics)
Team Role: Alumni
 
Join Date: Jan 2007
Rookie Year: 2007
Location: Sussex, WI
Posts: 310
slavik262 is a splendid one to beholdslavik262 is a splendid one to beholdslavik262 is a splendid one to beholdslavik262 is a splendid one to beholdslavik262 is a splendid one to beholdslavik262 is a splendid one to beholdslavik262 is a splendid one to behold
Send a message via AIM to slavik262
Re: Silly Programming screw ups (funny)

I tried that this year and it worked suprisingly well.

The thing I love the most about these accusations is that the code hasn't change since before the code "broke it."
__________________
  #68   Spotlight this post!  
Unread 05-10-2008, 06:44 PM
ComradeNikolai ComradeNikolai is offline
Registered User
AKA: Nicholas
FRC #2603 (Team Hornet)
Team Role: Mentor
 
Join Date: Feb 2008
Rookie Year: 2008
Location: Medina, Ohio
Posts: 203
ComradeNikolai is a splendid one to beholdComradeNikolai is a splendid one to beholdComradeNikolai is a splendid one to beholdComradeNikolai is a splendid one to beholdComradeNikolai is a splendid one to beholdComradeNikolai is a splendid one to beholdComradeNikolai is a splendid one to behold
Re: Silly Programming screw ups (funny)

Yep, and you'd think our coach would know that, as he teaches programming (thus why the core of our team had all taken Programming I and II.) However, with most of our team graduating, blaming everyone else will work VERY nicely, as we'll have a completely new electrical team and mostly new mechanical people.
__________________
I cut myself shaving with Occam's razor.

  #69   Spotlight this post!  
Unread 05-11-2008, 12:13 AM
Alan Anderson's Avatar
Alan Anderson Alan Anderson is offline
Software Architect
FRC #0045 (TechnoKats)
Team Role: Mentor
 
Join Date: Feb 2004
Rookie Year: 2004
Location: Kokomo, Indiana
Posts: 7,893
Alan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond repute
Send a message via AIM to Alan Anderson
Re: Silly Programming screw ups (funny)

Quote:
Originally Posted by slavik262 View Post
On our team, even the electrical guys think it's a code problem. But the programmers know it's an electrical problem.
I instituted a policy of "defensive programming" a couple of years ago. Simple, easy-to-understand subroutines that provided simple, easy-to-understand feedback to show the state of sensors and their desired operation. The electrical/mechanical group quickly comes to trust the software group when a wiring problem can be identified by the lack of a light or a non-incrementing number.
  #70   Spotlight this post!  
Unread 05-11-2008, 12:18 AM
tdlrali tdlrali is offline
Registered User
FRC #0469 (Las Guerrillas)
Team Role: Programmer
 
Join Date: Sep 2006
Rookie Year: 2006
Location: MI
Posts: 377
tdlrali has much to be proud oftdlrali has much to be proud oftdlrali has much to be proud oftdlrali has much to be proud oftdlrali has much to be proud oftdlrali has much to be proud oftdlrali has much to be proud oftdlrali has much to be proud of
Re: Silly Programming screw ups (funny)

Quote:
I instituted a policy of "defensive programming" a couple of years ago. Simple, easy-to-understand subroutines that provided simple, easy-to-understand feedback to show the state of sensors and their desired operation. The electrical/mechanical group quickly comes to trust the software group when a wiring problem can be identified by the lack of a light or a non-incrementing number.
Yeah, same here. Our terminal can display almost any input and output of the RC, so when they tell me that I need to fix something, I just show them that the input is not correct or that the output is correct.
  #71   Spotlight this post!  
Unread 05-11-2008, 12:31 AM
pjamma pjamma is offline
Registered User
AKA: Justin Chan
FRC #1732 (Hilltopper Robotics)
Team Role: Programmer
 
Join Date: Mar 2007
Rookie Year: 2007
Location: Wisconsin
Posts: 4
pjamma is an unknown quantity at this point
Send a message via AIM to pjamma
Talking Re: Silly Programming screw ups (funny)

There was one time at the Wisconsin Regional, where i was ready to download new code...
but for some strange reason the laptop that i was using really liked loading up our practice robot's code...
so without paying attention i downloaded the wrong code.
and when we turned on the robot the arm shot up
but luckily we had a limit switch which both of the robots used in the same input...

so when i checked what was wrong i noticed that i had downloaded the wrong hex file
(and then my mentor owed his wife 15 dollars... which they apparently bet that id make that mistake)

Oh and there was one time at the Great Lakes Regional,
Once the match started our arm decided to not go up
right as we came back everyone began to blame me (even my mentor had to "check what i had done")
but then one of our drivers said, before the match started the cowboy hat guy from IFI told them that there was something wrong with the controller but we didnt have to worry about it... and i guess the arm decided not to work
but luckily it worked the very next match (without me needing to change the code)
  #72   Spotlight this post!  
Unread 05-11-2008, 02:16 PM
slavik262's Avatar
slavik262 slavik262 is offline
We do what we must because we can.
AKA: Matt Kline
FRC #0537 (Charger Robotics)
Team Role: Alumni
 
Join Date: Jan 2007
Rookie Year: 2007
Location: Sussex, WI
Posts: 310
slavik262 is a splendid one to beholdslavik262 is a splendid one to beholdslavik262 is a splendid one to beholdslavik262 is a splendid one to beholdslavik262 is a splendid one to beholdslavik262 is a splendid one to beholdslavik262 is a splendid one to behold
Send a message via AIM to slavik262
Re: Silly Programming screw ups (funny)

Quote:
Originally Posted by tdlrali View Post
Yeah, same here. Our terminal can display almost any input and output of the RC, so when they tell me that I need to fix something, I just show them that the input is not correct or that the output is correct.
I did that as well. I basically created a bunch of preprocessor macros containing prints throughout my code, i.e.

Code:
#ifdef DEBUG_THIS
printf("The value of this is: %d\r", this);
#endif
I then created a file called Debug.h containing commented out #defines. Whever I wanted to check a specific system on the robot, I just uncommented the #define that correlated to the system I wanted to check.

This strategy helped us constantly, and even let us track down a loose wire connected to the compressor's pressure switch (even though when electrical blamed me I told them that I hadn't touched compressor code since before we shipped ).
__________________
  #73   Spotlight this post!  
Unread 05-11-2008, 07:02 PM
usbcd36's Avatar
usbcd36 usbcd36 is offline
Registered User
AKA: "DOS"
FRC #2399 (The Fighting Unicorns)
Team Role: Mentor
 
Join Date: Jan 2007
Rookie Year: 2006
Location: Solon, OH
Posts: 150
usbcd36 is a jewel in the roughusbcd36 is a jewel in the roughusbcd36 is a jewel in the rough
Re: Silly Programming screw ups (funny)

So…

I've been working on the electrical, programming AND drivetrain for the past two years. If something goes wrong with any of those, it's simply MY problem.

2007

I wasn't programming for the first time, but I was programming for the first time that season, and I wrote the code like so:

Code:
pwm01 = p1_y/2
pwm02 = p2_y/2
Oh, and neither wheel was reversed.

Needless to say, it didn't work as I'd planned. Right after I plugged in the OI, the robot spun around really fast and whacked one of our members in the ankle. He jumped around shouting "AARGH! The robot just tried to kill me!", and the mistake was forever named, "The Kill Rimon Program."

Also, in an attempt to slow the robot down a bit, we'd implemented a better, but not completely correct algorithm. The only problem is that when the joysticks were moved forwards past a certain point or backwards at all, the chars overflowed and the robot shot ahead at full speed. Very confusing for our driver, though it didn't cause any crashes.


2008

I had originally written the code to actuate our hoop and trackball puncher (both of which used pneumatic cylinders) to use two buttons each: one to extend, and the other to retract. While this was a very simple solution, the button to retract the lifter was hard-to-reach (p2_sw_top on the left joystick ends up right between your thumb and pointer), so I decided to re-write the program to toggle the cylinder position instead (and therefore only use two buttons). After downloading the code and driving the robot back out to the middle of the room, I realized that something was wrong. Upon pressing either button, nothing would happen, and upon the release, there was a 50% chance that the manipulator assigned to that button would move to its other position. When I stepped up to investigate, I noticed that when a button was pressed, the solenoid it corresponded to switched back and forth rapidly, and upon release, it stopped. At that point, the hoop hit me in the head. I had failed to realize that no one is going to press a button for one cycle of the main loop, so the toggling feature formed a simple oscillator instead.

Another time, I was working on a simple autonomous program that would drive the robot forwards a certain amount, then stop and extend the trackball lifter. I wisely (or so I thought) left it on the cart for its first run, so it couldn't go around terrorizing the school if something went wrong. The wheels ran at a reasonable speed in the correct direction, but the combined height of the cart and fully-extended lifter were enough to dislodge the cover of a nearby fluorescent light, which nearly fell on me. The danger gone, I started trying to figure out how to replace the cover. I thought about it for a moment, then re-hooked the hinges on one side and used the same lifter to push the other side into place.

There was also one time where the left and right encoders were plugged into the opposite digital inputs. Wasted a LOT of time diagnosing that one…

Fortunately, most of our crazy robot stories from this year were actually stupid operator stories, and were able to be stopped by simply letting go of the controls.
  #74   Spotlight this post!  
Unread 05-11-2008, 07:23 PM
RMS11's Avatar
RMS11 RMS11 is offline
Safety!!!!
AKA: Rick
FRC #2415 (WiredCats)
Team Role: Driver
 
Join Date: Feb 2008
Rookie Year: 2008
Location: Atlanta
Posts: 263
RMS11 is a splendid one to beholdRMS11 is a splendid one to beholdRMS11 is a splendid one to beholdRMS11 is a splendid one to beholdRMS11 is a splendid one to beholdRMS11 is a splendid one to behold
Send a message via AIM to RMS11
Re: Silly Programming screw ups (funny)

This year during a practice match our coder forgot to comment out some autonomous he was testing some code and didn't comment it out and our robot hit one of those boards supporting the overpass and our robot flipped. Quite scary but very funny since nothing was hurt.
__________________

2009 Peachtree Regional Champs
2009 Palmetto Regional Champs
2008 Peachtree Rookie All Star and Rookie Highest Seed
  #75   Spotlight this post!  
Unread 05-13-2008, 05:09 PM
JMB226's Avatar
JMB226 JMB226 is offline
Registered User
AKA: Joe
FRC #0379 (Robocats)
Team Role: Alumni
 
Join Date: Apr 2007
Rookie Year: 2006
Location: Girard, Ohio
Posts: 12
JMB226 is a jewel in the roughJMB226 is a jewel in the roughJMB226 is a jewel in the rough
Send a message via AIM to JMB226 Send a message via MSN to JMB226 Send a message via Yahoo to JMB226
Re: Silly Programming screw ups (funny)

Mine would be this year, before the Buckeye Regional when trying out autonomous code back at the school. We didn't have the robot, so I downloaded the code to our motorized cart. And some how, no matter what the dongle was set to, it would always be in auto mode.
A few days later when I fixed that, I was experimenting w/ joy stick control. Ended up giving it an emergency stop. where you had to hold down the trigger button in order to move. While it was a good idea so accidental movement didn't happen, it wasn't practical.
The 'funnest' was when the 'testing' auto. code kicked in randomly when moving the cart. While packing stuff on, it bumped the switch and that was that.
__________________


Closed Thread


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
pic: I Love UPS! dubious elise Extra Discussion 15 05-05-2006 04:43 PM
pic: UPS with UPS Kevin Kolodziej Extra Discussion 10 05-04-2005 12:57 PM
I am silly. FotoPlasma Chit-Chat 15 01-07-2003 09:55 AM
silly fun Mark Hamilton Chit-Chat 8 10-29-2002 01:56 PM


All times are GMT -5. The time now is 12:41 PM.

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


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