A huge thanks Karthik AND Ian. I read Ian’s strafing paper for an FTC prototype but for FRC we wanted to try a high speed shifter instead of omni drive train.
There are a lot of words in all of those documents that communicate the way I’ve been thinking for a while but have been unable to concisely put into words for the team I mentor. These documents will be a most invaluable resource for the rest of this year and all of next year. See you guys in Atlanta!
YES!!! Ohhhh how I miss Dunkies coffee!
And Cumberland Farms, and Hot Dog Charlie’s…
All I can say about 1114… awesome robot. Its going to take a powerhouse to beat them… I hope they team up with 1024 @ Big A cause them two playing against each other… whooooo what a battle!
Practice, practice, practice. I know of at least one team that wore the traction tread off its wheels at 1983’s practice field in Seattle. The team I’m thinking of had a fairly modest robot, but it worked as designed the full 140 seconds of every match, and had a very smooth, competent drive team. I’m starting to think that a full-sized practice field is one of the five or six things a team NEEDS to be successful.
I was just looking through the schedule for the FIRST Robotics Conference, and saw that Karthik is doing a presentation on Effective Strategies for FRC Robots on Wednesday night at 7:00. If this is the presentation (or close to) the presentation of his that I’ve seen, it’s possibly the best use of 45 minutes your team could ever spend. If you want an inside view into how 1114 functions, this is your chance.
Will this presentation be online in any format for those of us who can’t make it?
Practice is a great part of a successful run. We don’t have a carpet to
practice on so we have to run on linoleum at our school. Hard to tune
autonomous on that or do drive practice with all the slipping around.
We are hoping to do some practice on carpet this weekend at a
another elementary school.
Karthik’s team has it down. 2 hours of practice a day makes for good
teamwork. We owe a lot of this years success to having one of our
old drivers being a mentor now. He knows the ropes and helps not only our team
but at Cleveland he was jumping between teams on our finals. Coordination is key.
Nothing wrong with having a killer launcher like 1114 either though.
How does next thursday sound to you guys? I’m sure you and Paul could work something out. 
If you guys want to make the drive, we’ll open the doors for a good SimChicken practice session. Paul’s already been by once this year, I’m sure you can convince him to come again.
Having taken home half of the carpet from GTR, hopefully now 1075 can get some decent practice done in our facility, and should be able to avoid this year’s occurence of going to 188’s facility the week before ship, only to find that our gear ratio was too high, and we were killing batteries in LITERALLY seconds.
On a completely irrelevant note (
) how has 1114 been doing in terms of Vex this year? I kinda want to see that robot too while I’m in Atlanta. 
I have some pictures of 1114’s Vex 'bot that I’ll put up closer to the Championship (to respect their desire for secrecy).
Excellent job team 1114. Your papers are excellent. People tend to see the robot what they don’t see is the infrastructure behind it to make it successful.
Question, how do you tell which of the 6 spots to hit the balls in hybrid mode? We use the IR, how do you do it?
We also use the IR to inform the robot where the balls are in hybrid. The program assumes the balls are in the middle lanes and commands from the robocoach override this with different ball locations.
That is the way we do it. On each side if IR not pushed than it goes for that one by default. But your hybird mode is so much better, my hybrid hat is off to your team.
As promised, here are some photos of the 1114 Vex robot that I took at one of their practice sessions (before they got the pretty side panels on). Based on the way they dominated the Ontario FTC Championship, I would be surprised if they didn’t win a third consecutive world championship. :ahh: