Go to Post FIRST, an american revolution. - paulcd2000 [more]
Home
Go Back   Chief Delphi > Competition > Rules/Strategy
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
Closed Thread
Thread Tools Rate Thread Display Modes
  #16   Spotlight this post!  
Unread 13-01-2008, 12:24
keen101's Avatar
keen101 keen101 is offline
Ubuntu Linux User
no team
Team Role: College Student
 
Join Date: Dec 2007
Rookie Year: 2005
Location: Loveland, CO
Posts: 228
keen101 is a jewel in the roughkeen101 is a jewel in the roughkeen101 is a jewel in the roughkeen101 is a jewel in the rough
Re: Intentionally tipping and disabling your own robot FTW...

Quote:
Originally Posted by ida_noeman View Post
How does the ref know exactly when you hit the emergency stop button?

The judges have a little panel that tells them everything. It also has disable buttons for them to use.

Last year, the judges claimed our robot's power momentarily spiked, so they disabled it. We were out an entire match. We never did figure out what went wrong. Our robot worked fine after too.
  #17   Spotlight this post!  
Unread 13-01-2008, 12:27
Glooper's Avatar
Glooper Glooper is offline
Annoying Blob of Goo
AKA: Alec
FRC #1719 (Umbrella Corporation)
Team Role: Engineer
 
Join Date: Jan 2008
Rookie Year: 2008
Location: The PA-MD border
Posts: 5
Glooper is an unknown quantity at this point
Re: Intentionally tipping and disabling your own robot FTW...

Quote:
Originally Posted by keen101 View Post
The judges have a little panel that tells them everything. It also has disable buttons for them to use.

Last year, the judges claimed our robot's power momentarily spiked, so they disabled it. We were out an entire match. We never did figure out what went wrong. Our robot worked fine after too.
Wait, the Judges can tell how much power is going through your robot? 0.0
__________________
Blood rains from above
A wave of death consumes all
Sadness is but life
  #18   Spotlight this post!  
Unread 13-01-2008, 12:48
IbleedPink233's Avatar
IbleedPink233 IbleedPink233 is offline
Registered User
FRC #0233 (The Pink Team)
Team Role: Alumni
 
Join Date: Dec 2007
Rookie Year: 2003
Location: Florida
Posts: 133
IbleedPink233 is a splendid one to beholdIbleedPink233 is a splendid one to beholdIbleedPink233 is a splendid one to beholdIbleedPink233 is a splendid one to beholdIbleedPink233 is a splendid one to beholdIbleedPink233 is a splendid one to behold
Re: Intentionally tipping and disabling your own robot FTW...

Well, to block an entire lane, you don't need a thirteen foot robot. All you need to do is make a 9 foot robot - if it lies in the center, then there will only be 2 ft of clearance on either side. 2 ft will not let the average 28in wide + bumpers robot through. 9 ft is reasonable for scoing over the Overpass - especially if you have a 40 inch manipulator. 9 ft is also easily obtained by a 2 section tower/elevator or a rotating arm. Since most robots will have almost no ground clearance, they won't be able to climb over the bot (and will probably earn themselves a penalty if they tried). A Trackball might be able to get through, but could be easily blocked by another alliance member.
However, even though it is "possible," I hope that no one is seriously considering this strategy. It would definitely make the game mind-numbingly boring - 15 seconds of play and 1 minute and 45 seconds of robots doing donuts in their little quadrants. FRC is not boring, so making the game boring would not be in the spirit of FIRST.
Not to mention that the strategy would reduce your engineers and student designers and their work to making a roadblock instead of a game-playing robot.
I am more worried about a robot that is less likely to incur penalties, but still effectively bolck scoring: one that can go up to their opponents' Overpass and fold out a huge shield that prevents all but the highest-thrown Trackballs from hurdling. In theory, it is perfectly legal, as long as the robot doesn't grapple anything and moves out of the way when someone signals to pass. Excellent defense, but once again, makes the game more dry and frustrating, not fun.
  #19   Spotlight this post!  
Unread 13-01-2008, 13:07
Libby K's Avatar
Libby K Libby K is offline
Always a MidKnight Inventor.
FRC #1923 (The MidKnight Inventors)
Team Role: Mentor
 
Join Date: Mar 2006
Rookie Year: 1992
Location: West Windsor, NJ
Posts: 1,584
Libby K has a reputation beyond reputeLibby K has a reputation beyond reputeLibby K has a reputation beyond reputeLibby K has a reputation beyond reputeLibby K has a reputation beyond reputeLibby K has a reputation beyond reputeLibby K has a reputation beyond reputeLibby K has a reputation beyond reputeLibby K has a reputation beyond reputeLibby K has a reputation beyond reputeLibby K has a reputation beyond repute
Re: Intentionally tipping and disabling your own robot FTW...

Emphasis mine...

Quote:
Originally Posted by eagle33199 View Post
I would hope the judges would treat such a blatant disregard for gracious professionalism rather severely.
Quote:
Originally Posted by keen101 View Post
The judges have a little panel that tells them everything. It also has disable buttons for them to use.

Last year, the judges claimed our robot's power momentarily spiked, so they disabled it. We were out an entire match. We never did figure out what went wrong. Our robot worked fine after too.
Quote:
Originally Posted by Glooper View Post
Wait, the Judges can tell how much power is going through your robot? 0.0
I know this is a really unrelated side note, but reading this thread, I've noticed so many people saying "Judges". Please remember the difference between a Judge and a Referee.

Many judges (blue shirts) don't actually SEE matches until all their decisions are done. They're on the field for opening ceremonies each day, may watch a few matches, and then retreat back to the Judges' room to debate who gets which award.

The referees (zebras) are the ones on the field, watching every match and every team to make sure gameplay is fair and the spirit of FIRST competition is maintained.

It's a minute note, but it does make a difference. However, if teams do something really, really against the spirit of FIRST and Gracious Professionalism, rest assured that the judges DO find out about it and consider it in their decisions.

Sorry for the tangent, but that's about it.

$0.02 -- given.
__________________
Libby Kamen
Team 1923: The MidKnight Inventors
2006-2009: Founder, Captain, Operator, Regional Champion.
2010-Always: Proud Alumni, Mentor & Drive Coach. 2015 Woodie Flowers Finalist Award.

-
229: Division By Zero / 4124: Integration by Parts
2010-2013: Clarkson University Mentor for FLL, FTC & FRC

-
FIRST Partner Associate, United Therapeutics
#TeamUnither | facebook, twitter & instagram | @unitherFIRST

-
questions? comments? concerns? | twitter: @libbyk | about.me/libbykamen
  #20   Spotlight this post!  
Unread 13-01-2008, 13:52
Tristan Lall's Avatar
Tristan Lall Tristan Lall is offline
Registered User
FRC #0188 (Woburn Robotics)
 
Join Date: Aug 2001
Rookie Year: 1999
Location: Toronto, ON
Posts: 2,484
Tristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond repute
Re: Intentionally tipping and disabling your own robot FTW...

Quote:
Originally Posted by dlavery View Post
Notice that the (revised) rule indicates that a disabled Robot will not receive any additional PENALTIES. It does not say anything about being immune from receiving a RED CARD (note that in the formal definitions, they are not the same thing).
There's a practical problem with that, though: you can't directly get a red card for egregious behaviour, only a yellow card (according to <T05>), unless the red card results from two yellow cards in two separate matches (due to <T07>). Also, <T09> tells us that red cards can be recieved directly, for disqualifications that don't result from yellow cards—but then the grounds for disqualification need to be something else. That brings us back to the subject of the thread: there doesn't seem to be a sanction with immediate punitive results, unless the behaviour is repeated in more than one match (in which case another yellow card will quickly deal with the offender).

While the referees will obviously hand out a yellow card every time this happens, that does give a team a theoretical opportunity to use this strategy once in the qualifying rounds and once in the elimination rounds, without being disqualified.
  #21   Spotlight this post!  
Unread 13-01-2008, 14:00
EricH's Avatar
EricH EricH is offline
New year, new team
FRC #1197 (Torbots)
Team Role: Engineer
 
Join Date: Jan 2005
Rookie Year: 2003
Location: SoCal
Posts: 19,817
EricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond repute
Re: Intentionally tipping and disabling your own robot FTW...

Quote:
Originally Posted by Tristan Lall View Post
There's a practical problem with that, though: you can't directly get a red card for egregious behaviour, only a yellow card (according to <T05>), unless the red card results from two yellow cards in two separate matches (due to <T07>). Also, <T09> tells us that red cards can be recieved directly, for disqualifications that don't result from yellow cards—but then the grounds for disqualification need to be something else. That brings us back to the subject of the thread: there doesn't seem to be a sanction with immediate punitive results, unless the behaviour is repeated in more than one match (in which case another yellow card will quickly deal with the offender).

While the referees will obviously hand out a yellow card every time this happens, that does give a team a theoretical opportunity to use this strategy once in the qualifying rounds and once in the elimination rounds, without being disqualified.
Hmmm. Tristan, didn't you ref at one point? If so, would you consider a 9-13 foot tall robot falling towards either the robots or the refs/scorers/judges as a safety hazard? And, if a robot is deemed a safety hazard, it can be DQ'd, right? Not only that, but if it is routinely a safety hazard, the refs can refuse to allow it to compete until it is no longer a hazard, if I read the rules correctly.

I may be lawyering the rules a bit much, but I think this is the easy way to discourage this/allow red cards. Also, this effectively disables other robots (even more of a stretch).
__________________
Past teams:
2003-2007: FRC0330 BeachBots
2008: FRC1135 Shmoebotics
2012: FRC4046 Schroedinger's Dragons

"Rockets are tricky..."--Elon Musk

  #22   Spotlight this post!  
Unread 13-01-2008, 14:21
IbleedPink233's Avatar
IbleedPink233 IbleedPink233 is offline
Registered User
FRC #0233 (The Pink Team)
Team Role: Alumni
 
Join Date: Dec 2007
Rookie Year: 2003
Location: Florida
Posts: 133
IbleedPink233 is a splendid one to beholdIbleedPink233 is a splendid one to beholdIbleedPink233 is a splendid one to beholdIbleedPink233 is a splendid one to beholdIbleedPink233 is a splendid one to beholdIbleedPink233 is a splendid one to behold
Re: Intentionally tipping and disabling your own robot FTW...

Quote:
Originally Posted by Tristan Lall View Post
There's a practical problem with that, though: you can't directly get a red card for egregious behaviour, only a yellow card (according to <T05>), unless the red card results from two yellow cards in two separate matches (due to <T07>). Also, <T09> tells us that red cards can be recieved directly, for disqualifications that don't result from yellow cards—but then the grounds for disqualification need to be something else. That brings us back to the subject of the thread: there doesn't seem to be a sanction with immediate punitive results, unless the behaviour is repeated in more than one match (in which case another yellow card will quickly deal with the offender).

While the referees will obviously hand out a yellow card every time this happens, that does give a team a theoretical opportunity to use this strategy once in the qualifying rounds and once in the elimination rounds, without being disqualified.
Ummm, as a general rule, you don't want to nitpick the words of someone on the GDC! When they deal with the intent or organization of the rules, especially, they know more about it than any of us!

Also, why would you build a robot that is designed to fall once during an entire regional? That means that you either have to waste the resources to actuate something strong enough to tip over your bot and make the entire robot durable enough to withstand the impact (ie lots of weight and engineering time) for such a tiny gain OR you have to risk the safety of your robot to tip it over when it is not designed to do that. Either way, you are hurting yourself in the long run, if not the short run, as well.
  #23   Spotlight this post!  
Unread 13-01-2008, 14:22
Koko Ed's Avatar
Koko Ed Koko Ed is offline
Serial Volunteer
AKA: Ed Patterson
FRC #0191 (X-Cats)
Team Role: Mentor
 
Join Date: Mar 2002
Rookie Year: 2002
Location: Rochester,NY
Posts: 22,945
Koko Ed has a reputation beyond reputeKoko Ed has a reputation beyond reputeKoko Ed has a reputation beyond reputeKoko Ed has a reputation beyond reputeKoko Ed has a reputation beyond reputeKoko Ed has a reputation beyond reputeKoko Ed has a reputation beyond reputeKoko Ed has a reputation beyond reputeKoko Ed has a reputation beyond reputeKoko Ed has a reputation beyond reputeKoko Ed has a reputation beyond repute
Re: Intentionally tipping and disabling your own robot FTW...

Unless your robot is completely offensively inept I cannot see any reason to purposely disabling it. And considering that any robot that can move can score this strategy shouldn't be given any consideration unless you are completely insane.
__________________
  #24   Spotlight this post!  
Unread 13-01-2008, 15:08
Tristan Lall's Avatar
Tristan Lall Tristan Lall is offline
Registered User
FRC #0188 (Woburn Robotics)
 
Join Date: Aug 2001
Rookie Year: 1999
Location: Toronto, ON
Posts: 2,484
Tristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond repute
Re: Intentionally tipping and disabling your own robot FTW...

Quote:
Originally Posted by EricH View Post
Hmmm. Tristan, didn't you ref at one point? If so, would you consider a 9-13 foot tall robot falling towards either the robots or the refs/scorers/judges as a safety hazard? And, if a robot is deemed a safety hazard, it can be DQ'd, right? Not only that, but if it is routinely a safety hazard, the refs can refuse to allow it to compete until it is no longer a hazard, if I read the rules correctly.

I may be lawyering the rules a bit much, but I think this is the easy way to discourage this/allow red cards. Also, this effectively disables other robots (even more of a stretch).
I was actually considering posting exactly that, but decided against it. I figured that if the team is smart (and crazy) enough to plan out a strategy using this technique, they'll also be smart enough to fall toward the centre divider.
  #25   Spotlight this post!  
Unread 13-01-2008, 15:14
EricH's Avatar
EricH EricH is offline
New year, new team
FRC #1197 (Torbots)
Team Role: Engineer
 
Join Date: Jan 2005
Rookie Year: 2003
Location: SoCal
Posts: 19,817
EricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond repute
Re: Intentionally tipping and disabling your own robot FTW...

Quote:
Originally Posted by Tristan Lall View Post
I was actually considering posting exactly that, but decided against it. I figured that if the team is smart (and crazy) enough to plan out a strategy using this technique, they'll also be smart enough to fall toward the centre divider.
Yeah, but the best-laid plans...

The main thing is that this can effectively disable other robots. Call me a lawyer if you will, but that is explicitly prohibited and is a cardable offense, up to a Red Card for the first attempt/success and at minimum a penalty at first.

And the GDC will probably take measures as soon as someone tries this. (And, if the refs are smart, as soon as the robot starts going over, they will start pulling out flags for impeding/80" violation.)
__________________
Past teams:
2003-2007: FRC0330 BeachBots
2008: FRC1135 Shmoebotics
2012: FRC4046 Schroedinger's Dragons

"Rockets are tricky..."--Elon Musk

  #26   Spotlight this post!  
Unread 13-01-2008, 15:51
Compnerd's Avatar
Compnerd Compnerd is offline
Self-Proclaimed Nerd
AKA: James H
FRC #1444 (Lightning Lancers)
Team Role: Webmaster
 
Join Date: Jan 2007
Rookie Year: 2006
Location: St. Louis
Posts: 180
Compnerd has a spectacular aura aboutCompnerd has a spectacular aura about
Exclamation Re: Intentionally tipping and disabling your own robot FTW...

Has anyone considered that if your robot is tipped and is laying down, and robots are running into it, my bet is that your going to have some serious damage to your bot... Penalties would be the least of my worries in this situation, as this could potentially take you out of the entire competion depending on the severity of the damages..
__________________
James H. - Webmaster - Team 1444
http://www.first1444.com

If you need any website help send me a PM
  #27   Spotlight this post!  
Unread 13-01-2008, 16:57
Mr. Lim Mr. Lim is offline
Registered User
AKA: Mr. Lim
no team
Team Role: Leadership
 
Join Date: Jan 2004
Rookie Year: 1998
Location: Toronto, Ontario
Posts: 1,125
Mr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond repute
Re: Intentionally tipping and disabling your own robot FTW...

A couple people have posted responses as to why a team would even consider a strategy like this. Why waste your engineering resources on this type of mechanism, etc. Why not try and score instead?

Consider a few things:

1) What does your perfect alliance consist of? Mine is 2 extremely effective hurdlers, and one other robot. There are only two alliance trackballs, and assuming your 2 hurdlers can maintain possession of the ball throughout most of the match, your 3rd robot should never interact with a trackball. There is no "viable" defensive strategy, so what is your ideal 3rd robot supposed to do?

DRIVE REALLY FAST, make 10 laps, and score 20 points right? THAT, in my opinion, is waste of engineering resources. Most every FIRST team probably feels they are capable of doing much more, and I predict most will! But a 3rd robot that can herd or hurdle is no better than one that can't. It should never touch a ball, so why bother having the capability of herding or hurdling?

I'm looking for a 3rd robot that doesn't need to herd or hurdle, but can still change the outcome of a match. Wouldn't a robot like this fit the bill?

If you're an alliance captain making your last pick, and you have a field of mediocre herders and hurdlers, or a speedster that can spontaneously decide to be "tippy, disably, and extendy" at the perfect moment, who are you going to pick?

If your team consistantly qualifies 16 or lower at an event, will be fighting for a 3rd robot spot in the eliminations, and you are seriously thinking about WINNING an event (remember, it's not everything, but it IS important to many), these are viable strategy decisions.

2) Over the years, the serpentine draft has added some interesting complexion to 3rd robot picks. No doubt, this "tippy, disably, and extendy" speedster will be offensively weak. During qualifications, I would expect it to do very poorly, and rank at or near the bottom, which is actually a very good thing for the team. Most "terrible" robots that rank dead last with no discernable scoring capabilities tend to not be picked.

The caveat is that during the last round of picks, generally, the last to pick, higher ranked teams have more scouting and strategy experience. They would be the most likely to recognize that your "tippy, disably, and extendy" speedster is actually an EXCELLENT 3rd robot.

From this standpoint, strategy decisions like this can vault your team from the bottom of the rankings, to regional winners before you even cut your first piece of metal.

I personally don't think it would be so strange for a team to consider doing something like this.

It would kill me though if I ever saw it done on purpose.
  #28   Spotlight this post!  
Unread 13-01-2008, 17:14
IbleedPink233's Avatar
IbleedPink233 IbleedPink233 is offline
Registered User
FRC #0233 (The Pink Team)
Team Role: Alumni
 
Join Date: Dec 2007
Rookie Year: 2003
Location: Florida
Posts: 133
IbleedPink233 is a splendid one to beholdIbleedPink233 is a splendid one to beholdIbleedPink233 is a splendid one to beholdIbleedPink233 is a splendid one to beholdIbleedPink233 is a splendid one to beholdIbleedPink233 is a splendid one to behold
Re: Intentionally tipping and disabling your own robot FTW...

Quote:
Originally Posted by SlimBoJones View Post
A couple people have posted responses as to why a team would even consider a strategy like this. Why waste your engineering resources on this type of mechanism, etc. Why not try and score instead?

Consider a few things:

1) What does your perfect alliance consist of? Mine is 2 extremely effective hurdlers, and one other robot. There are only two alliance trackballs, and assuming your 2 hurdlers can maintain possession of the ball throughout most of the match, your 3rd robot should never interact with a trackball. There is no "viable" defensive strategy, so what is your ideal 3rd robot supposed to do?

DRIVE REALLY FAST, make 10 laps, and score 20 points right? THAT, in my opinion, is waste of engineering resources. Most every FIRST team probably feels they are capable of doing much more, and I predict most will! But a 3rd robot that can herd or hurdle is no better than one that can't. It should never touch a ball, so why bother having the capability of herding or hurdling?

I'm looking for a 3rd robot that doesn't need to herd or hurdle, but can still change the outcome of a match. Wouldn't a robot like this fit the bill?

If you're an alliance captain making your last pick, and you have a field of mediocre herders and hurdlers, or a speedster that can spontaneously decide to be "tippy, disably, and extendy" at the perfect moment, who are you going to pick?

If your team consistantly qualifies 16 or lower at an event, will be fighting for a 3rd robot spot in the eliminations, and you are seriously thinking about WINNING an event (remember, it's not everything, but it IS important to many), these are viable strategy decisions.

2) Over the years, the serpentine draft has added some interesting complexion to 3rd robot picks. No doubt, this "tippy, disably, and extendy" speedster will be offensively weak. During qualifications, I would expect it to do very poorly, and rank at or near the bottom, which is actually a very good thing for the team. Most "terrible" robots that rank dead last with no discernable scoring capabilities tend to not be picked.

The caveat is that during the last round of picks, generally, the last to pick, higher ranked teams have more scouting and strategy experience. They would be the most likely to recognize that your "tippy, disably, and extendy" speedster is actually an EXCELLENT 3rd robot.

From this standpoint, strategy decisions like this can vault your team from the bottom of the rankings, to regional winners before you even cut your first piece of metal.

I personally don't think it would be so strange for a team to consider doing something like this.

It would kill me though if I ever saw it done on purpose.
You are very much limiting the strategies that a team can use - even to the point of being unrealistic. I can almost guarantee that there will be no robot that will be able to perfectly keep control of their ball for an entire match while Hurdling - the rules appear to be designed to prevent that. Also, a robot without a Trackball is still able to do things such as: play defense (which there are plenty of "viable" ways to do, just poke around the forums), herd opponents' balls, etc. Limiting them to doing laps and the freak chance that tipping over can help you win one match is making that robot a very inflexible robot, and thus, a poor pick for any alliance. Even ignoring any possible penalties, I know that my team - with a great scouting and intelligence system that I am a part of - would only pick that robot over another that could only go around the Track 9 times, they are by no means an "EXCELLENT" pick.
Not to mention - if you are going to be 9 ft tall anyway, why not try to score? Why would you design a bot that had a tower that would only be used once per regional?

Last edited by IbleedPink233 : 13-01-2008 at 17:18.
  #29   Spotlight this post!  
Unread 13-01-2008, 17:46
ALIBI's Avatar
ALIBI ALIBI is offline
Registered User
FRC #0141
Team Role: Parent
 
Join Date: Feb 2007
Rookie Year: 2004
Location: Michigan
Posts: 271
ALIBI is a name known to allALIBI is a name known to allALIBI is a name known to allALIBI is a name known to allALIBI is a name known to allALIBI is a name known to all
Re: Intentionally tipping and disabling your own robot FTW...

Quote:
Originally Posted by SlimBoJones View Post
Team Update #2 had an excellent resolution to some questions posed in the Q & A. This change made me wonder about an interesting strategy:



DISCLAIMER: I in no way support this strategy. Please don't misinterpret this post as intent to use this strategy myself or for my team. This question is asked as a result of investigating "game-breaking" strategies, which is something we do as part of our game analysis.

Suppose you built a robot that extended upwards, that if tipped, would block an entire lane of traffic, such that no other robot could pass. Attempting to push this robot out of the way would also be futile.

If at any time during the match, your alliance gained a lead (i.e. maybe 12 to 8 after hybrid mode), if your robot were to tip and be e-stopped, effectively blocking all traffic, would that not prevent scoring for the remainder of the match, thus securing the win?
Simply can not be done:

If you had a mechanism that purposely tipped over the entire robot, that would also be a mechanism that articulated the standard bumpers outside the bumper zone and it would not pass inspecition. The key here is to get the E-stop for tipping. You can not just raise something up ten feet or so, hit the E-stop as it is falling and then say you tipped to avoid further penalties.

EDIT: I could see a mechaism getting past the inspectors, however, after the first time it was used on the field I could see a Head Ref. sending it back for inspection and not allowing it back on the track until the design has been corrected (S01). Anything 10-12 feet tall that that could tip where the guardrail is only 20 inches high should be considered unsafe.

Last edited by ALIBI : 13-01-2008 at 17:54.
  #30   Spotlight this post!  
Unread 14-01-2008, 13:24
JesseK's Avatar
JesseK JesseK is offline
Expert Flybot Crasher
FRC #1885 (ILITE)
Team Role: Mentor
 
Join Date: Mar 2007
Rookie Year: 2005
Location: Reston, VA
Posts: 3,708
JesseK has a reputation beyond reputeJesseK has a reputation beyond reputeJesseK has a reputation beyond reputeJesseK has a reputation beyond reputeJesseK has a reputation beyond reputeJesseK has a reputation beyond reputeJesseK has a reputation beyond reputeJesseK has a reputation beyond reputeJesseK has a reputation beyond reputeJesseK has a reputation beyond reputeJesseK has a reputation beyond repute
Re: Intentionally tipping and disabling your own robot FTW...

Quote:
Disabled ROBOTS
may be pushed out of the path of travel without PENALTY.
You better believe that if you try this strategy against our team (or even if you're on our alliance?!) we will use all of our 105-constant-amp drive train to move you out of the way without any detriment to our own robot
__________________

Drive Coach, 1885 (2007-present)
CAD Library Updated 5/1/16 - 2016 Curie/Carver Industrial Design Winner
GitHub
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
Ramp and Tipping Nitroxextreme Rules/Strategy 10 10-02-2006 15:01
See ISS and Space Shuttle Discovery With Your Own Eyes! geo Chit-Chat 3 05-08-2005 15:09
Disabling the robot in autonomous? IMDWalrus Programming 10 18-01-2005 16:52
Ruling in Robot Tipping A.J. P Rules/Strategy 10 04-01-2003 17:50
Build Your Own Robot Kit Rich Wong Robotics Education and Curriculum 2 30-12-2002 20:50


All times are GMT -5. The time now is 01:03.

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