![]() |
Re: Midwest Regional
Who watched that? That was a really good regional!
|
Re: Midwest Regional
Quote:
|
Re: Midwest Regional
i have, it was awesome!
|
Re: Midwest Regional
Quote:
Joey |
Re: Midwest Regional
Quote:
My team has been in situations like you describe in Curie last year. My take is it's a 100% valid strategy. If you know that other people consider you a weaker team, and you have the first pick, you have to do what's best for you. What's best for you would be one of two things--the "powerhouse" teams accepting your invitation, and thus making your alliance better, or the powerhouse declining your invitation, and denying them the ability to be picked by another powerhouse, thus weakening all your opponents. It's been done to us, and if I were in the position of the team executing this strategy, I'd absolutely do it as well. It's all part of the game. |
Re: Midwest Regional
Quote:
|
Re: Midwest Regional
Woohoo, i picked the champs!
I had a feeling they were gonna take it. |
Re: Midwest Regional
Way to go McKenzie! Great way to represent Indianapolis! We are proud of you.
|
Re: Midwest Regional
Thanks to a few close calls our team had to stay around longer (2433 @ seed 9).
Congrats to team 1024 (The literally smoking robot). Their autonomous mode can score up to 20 points. (Talking about getting a head start) The robot was smoking after it was placed on the field during semi-final. The cause is unknown. (Our team was summoned to standby because of this.) Wildstang had to call a timeout to help get one of the other robots working within their alliance (We were called to standby for the final match). There was a 3 vs 1 match because of two reasons. 1. A competing team pulled their robot from the field 10 seconds before play. They should have stopped and brought in the standby team. Would have scored more points instead of being dominated. 2. A key robot to the team was on its side. Killer Bee's (Team 33) robot did a great job. Unfortunately it fell hard on its side in the beginning of its elimination match crippling the alliance's chance of scoring. This is the look on their faces when it fell :eek: 1114 has a unique method of cooling the motors / actuators for the arms. Too bad I didn't grab a photo of their cooling process: Blowing on the motor when they are not competing. Their preparation process before the match was perfect. They insured nothing would come lose and tested the motors and arm before the match. |
Re: Midwest Regional
Quote:
|
Re: Midwest Regional
Programmer/Driver here...
I am SOOOO TIRED but I couldn't help but see if anybody was saying anything on CD. Aparently so! Thank you for all of your kind complements. I'm sure I speak for our entire team when I say we've worked very hard this year to put forth a good bot. Still can't believe that shooting mechanism came from this prototype... 65_Xero_Huskie: Great prediction. Who would have thought? :D However, you're pick on closest match wasn't quite right. I don't know what alliance # they were, but the bomb squad alliance REALLY gave us a run for our money! IndySam: Thanks for your kind complements. Ninja: To clear up some smoke on the smoke, the smoke actually came from one of our ultrasonic sensors. Strangely enough, these sensors keep the robot from ramming (the robot decelerates (note decelerate not decrease power) just before a collision to keep from getting carded). So, are they safety sensors or un-safety sensors? :ahh: Our gyro now has gunk all over it and I think the fire (yes there wasn't just smoke) killed one of our encoder cables (hence the robot drifting into the wall in the final match). So, we're bringing a spare gyro and a spiffy new encoder cable to boilmaker and RALFF should be all ready to drive again. Some things are lucky like this, but I didnt even realized who's timeout we were on while fixing the wiring fault. Turns out WildStang called their timeout to fix one of their robots same time ours decided to start smoking all of a sudden. If you hadn't called the timeout... things may have been VERY different.................. hmm. Also, one last note. Remember the team numbers for our alliance? Look what's odd about them... 1+1+1+4 = 7 1+0+2+4 = 7 2+0+4+1 = 7 A match made in heaven? Perhaps. :ahh: 1024 is updating their travel schedule to include the Championship Event in Atlanta. 1114: I know we'll see you there. 2041: Don't remember if you're going or not, but hope you are! Thanks guys! See you all at Boilermaker next! -q p.s. Any feedback on the speedometer/debug display? |
Re: Midwest Regional
Quote:
And I have to add to everyone else that has already mentioned this, your auto is amazing!!! |
Re: Midwest Regional
Quote:
Also, we figured out what one of our problems was with the display being so, well, hard to read (getting dim quickly). Our main battery cable was barely hanging on... so whenever we gunned it (most the time) the battery voltage was very low. 1024 should be a little quicker at Boilermaker. The display is currently set to display ft/sec speed in competition mode (when in debug mode it can display a number of things from encoder counts to gyro angles). It reads out in fixed-point hundreths of a ft/sec. Example: "12.75" on display means the robot's forward velocity is 12.75ft/sec. If you see all the decimal points turn on (ex 1.2.7.5.), this means the robot is going backwards at the indicated speed. -q |
Re: Midwest Regional
Quote:
Even to just use it as a debug screen and not even have it on the 'bot for competition seems like it would be very helpful when programming auto. |
Re: Midwest Regional
Quote:
See you guys at BMR You guys rock!! |
| All times are GMT -5. The time now is 08:57. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi