|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#1
|
|||||
|
|||||
|
pic: FRC488 - Overview
Last edited by Madison : 30-01-2006 at 18:26. |
|
#2
|
|||||
|
|||||
|
Re: pic: FRC488 - Overview
I Like, Very Elegant. just looking . seems like you drop the hopper down to drop balls into the collector feed to launch. Beautifully skeleton look and the adjustable chassis for chain tension, Id love to see how that works out.
|
|
#3
|
|||||
|
|||||
|
Re: pic: FRC488 - Overview
Quote:
![]() The chassis isn't adjustable for chain tension in a specific sense, but rather, is completely modular. The modules that hold the transmissions, motors, wheels, chain and sprockets are self-contained and can be removed from the robot after removing four bolts from each side. I'll see if I can't find a picture of the unassembled chassis to show what I mean. |
|
#4
|
|||
|
|||
|
Re: pic: FRC488 - Overview
Cool. So, if you don't mind my asking, what are you using for belts?
|
|
#5
|
||||
|
||||
|
Re: pic: FRC488 - Overview
I am not trying to nitpick the rules here but rather gain a better understanding of how to interpret them. It is my understanding that the pictured design would not pass rule R4:
<R04> "Wedge” robots are not allowed. Robots must be designed so that interaction with other robots results in pushing rather than tipping or lifting. Neither offensive nor defensive wedges are allowed. All parts of a robot between 0 and 8.5 inches from the ground (the top of the bumper zone – see Rule <R35>) that might push against another robot must be within 10 degrees of vertical. Devices deployed outside the robot's footprint should be designed to avoid wedging. If a mechanism or an appendage (a ball harvester, for example) becomes a wedge that interferes with other robots, penalties, disabling, or disqualification can occur depending on the severity of the infraction. We were originally thinking of having a "door" that opened to allow balls to exit into the lower goal but have since changed our design specifically because of this rule. While neither your design nor our original design were designed to intentionally flip another robot they both appear to violate this rule. There are parts of the robot between 0 and 8.5 inches from the floor that are not within 10 degrees of vertical and can come into contact with other robots. Your design has a inverted wedge but the rule doesn't specify the direction of any wedges. In your case you are more likely to flip yourself than the other bot but I think FIRST would also frown upon bots driving up on other bots. Please, please, please don't take this as a slam of your bot design. I personally think it is a wonderful design. I am just unclear as to how the inspectors will rule on it. I am intending this to spark a discussion of how strict the R4 rule will be enforced and what is and isn't allowed. By a strict definition of the rule I don't think your design would pass but by a common sense definition I think it is great. I am wondering what other teams are thinking and how they are designing around this R4 rule. Are ALL the bots going to be square boxes from 0 to 8.5" up??? |
|
#6
|
|||||
|
|||||
|
Re: pic: FRC488 - Overview
Quote:
![]() Quote:
I'm not certain, even now, that such a ramp would be prohibited by this rule. The last sentence reads, "If a mechanism or an appendage (a ball harvester, for example) becomes a wedge that interferes with other robots, penalties, disabling, or disqualification can occur depending on the severity of the infraction," suggesting that a functional mechanism outside the initial constraints is not considered a wedge (if more than 10 degrees off vertical) by default. Instead, they've used the word "becomes," which implies that it would be okay to use for its intended purpose alone. I'm interested to read some others' interpretation of how we may be affected by that rule -- particularly anyone who will be an inspector or referee in Portland. ![]() Last edited by Madison : 30-01-2006 at 16:01. |
|
#7
|
|||
|
|||
|
Re: pic: FRC488 - Overview
Quote:
Last edited by Rick TYler : 30-01-2006 at 16:33. |
|
#8
|
|||||
|
|||||
|
Re: pic: FRC488 - Overview
[quote=Rick TYler]
Quote:
|
|
#9
|
||||
|
||||
|
Re: pic: FRC488 - Overview
I like Ms.Krass it's very nice, simple and eloquent echoing Dan Quiggle's words. I think our team has a lot of the saem thought process you described about teams not being able to shoot as well as they want to. We too hold a far amunt of balls and from what I can tell are going to proficient about getting rid of them but anyways. Sweet work I really like it looks amazing very beautiful bot seems like it could be a winner.
Good luckwith it, Drew |
|
#10
|
||||
|
||||
|
Re: pic: FRC488 - Overview
Quote:
![]() One question, how do you go from the wide collecting base to the shooter wheels? Last edited by Alekat : 31-01-2006 at 00:50. |
|
#11
|
|||||
|
|||||
|
Re: pic: FRC488 - Overview
Quote:
Beautiful design. How are you aiming the shooter? (If that's not giving too much away) |
|
#12
|
|||||
|
|||||
|
Bravo!
The design looks great, and I share the same belief on your strategy. I mostly want to applaud you on posting a full drawing with no strings attached. I believe this is the true spirit of first and it does not diminish the competitiveness of the competition one bit. Is there really anyone this late in the build season that is going to see someone else's design and change their own to "steal" some other team's idea? Doubtful. Way to be a leader in doing this and having a team that understands these views without questioning it.
|
|
#13
|
|||||
|
|||||
|
Re: pic: FRC488 - Overview
Quote:
I'm not so certain it'll work. In fact, I know it won't work as shown because the two center rails are missing an endpiece that would keep balls from falling into the gap. I suspect we'll need some larger funnel walls on the sides to coax the balls over to where they need to be. We're also considering running the conveyor belting on one side on a slightly different pulley size so as to make its speed a bit different. We hope that will aid in relieving any congestion between balls on the way up. Quote:
Thanks, everyone, for the continued compliments. I've grown tired of teasers that aren't that engaging, interesting or revolutionary and am trying to encourage full disclosure in its place. We've had enough trouble trying to design and build in isolation in just six weeks, so I too can't imagine that many teams have the resources or desire to alter their own plans to either copy or make obsolete a strategy or design they see here. Last edited by Madison : 31-01-2006 at 13:36. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| pic: River Rage 9 pic | JohnBoucher | Extra Discussion | 2 | 30-10-2005 14:43 |
| Using a computer to control the pic | mikesown | Programming | 6 | 13-09-2005 19:13 |
| Linux and new microcontollers. | djcapelis | Programming | 48 | 29-01-2005 00:26 |
| Survivor All-Stars | EddieMcD | Chit-Chat | 10 | 01-04-2004 19:50 |