First Robotics Competition: An International High-School Robotics Competition
firstinspires.org
firstinspires.org
I don't think anything else in school has prepared me for the real world more than my FIRST team. If I could tell my younger self one thing, it would be to join the team in my freshman year instead of senior year.
I was excited for him to get involved for many reasons but one of which I've been a pretty big fan of Dean Kamen (he co-founded First). However, over the past few years I've learned Dean is kind of a douche and the real star of First is (well, now was) Woody Flowers. He's a great example to all the kids and his philosophy of "graciousness professional" is no bullshit. It is a great way to roll out tech / STEM to kids.
When my kid first got into First I keep asking him about Dean (again, I was a fan) and he was like, "no one cares about him."
Woodie wasn't just the star of FIRST; competitive robotics based STEM education was basically his brainchild, building out from his work on the MIT 2.007 course. He really was the true ethos of the organization.
There are three major STEM promoters in the guise of a robotics competition: Offerings from FIRST, competitions sponsored by Vex, and KIPR BotBall. FIRST is the most well known at this point, thanks to excellent promotion by Dean Kamen. And Vex is great. But I think Botball has long thought been historically the best of the three, if the goal is to inspire, teach, and enable students who otherwise wouldn't have had an such opportunity.
BotBall is a shoestring nonprofit which was out very early doing competitions using Lego, motors and sensors, and MIT Handyboards: essentially a middle-school and high-school version of MIT's 6270 class. Botball competitions pit one robot against another and the robots are fully autonomous. Once the lights go on, the robots are completely on their own. Botball doesn't do teleoperation at all. This forces students to think of robots as complete systems of mechanical, electrical, sensory, and computational elements. I think this is good.
But BotBall has a critical additional big plus: it is very cheap. BotBall is a shoestring nonprofit and costs very little for schools to get started, and they work hard to allow schools to reuse most of their kits the next year even as the competition changes, so the rewnewal cost is extremely low. This means that BotBall is a very good choice for Title-1 and other disadvantaged schools, as well as non-school entities. One problem I've seen with some STEM ventures is their high cost, which is then offset by corporate sponsorship for schools. And there are a lot of problems with that model, often resulting in bias in selection of schools, or in kids' educational experience getting sidelined in the name of corporate success. BotBall is not only cheap for schools, but it's so cheap that corporate, private, or academic sponsors can jump in without a need to win at all costs. I myself have funded several Title-1 schools several times as a (mediocre) line item in NSF robotics and AI grants I've received, and highly recommend it.
I agree that having the competition rules change every year makes it harder for less well funded and backed schools to compete. Also, requiring specific hardware just to field a competition makes things much harder. NRL doesn't have that problem.
If you only build websites don't worry you'll find a place on a team. Don't sell yourself short, if you like kids and mentoring it's a great experience.
I went to the FIRST competition and it was fun. Maybe I'm wrong and those who participated got more out of it than I suspect.
edit: It some people got more out of than my friend indicated. Maybe better structured teams than his..
I lead the programmers but I don't do the work for them. If I do have to do work, I do it with them. It's very much their system and if they don't want to work on it then it'll be broken.
It depends on the team, the mentors, and the students. I'm sure other mentors and other teams do this, and I'm sure there are other teams and other mentors who help the students less and make them do more work.
With my former team software was always student-led. We had a mentor show us the ropes with git and and he'll work on helping people who are stuck. I think you can evaluate a team based off how they do at an event off the field. If they can still make changes to their codebase or robot then they're fine, but if they say "Mr./Ms. ____ isn't here so we can't deploy any changes" then that's really concerning.
On another note: the FIRST Robotics Competition’s official support library (WPILib) includes a number of advanced control features (trajectory generator, extended/unscented/“regular” Kalman filters, LQR) that were written almost entirely by students. I was one of the students involved in this work, and I can say with certainty that students can get a tremendous amount out of the program.
Would appreciate any recommendations.
[1]: https://www.curseforge.com/minecraft/mc-mods/opencomputers
Its an old site (java and .net), but it appears to still be going.
https://www.ibm.com/developerworks/library/j-robocode/index....
It includes both "hardware design" and programming. Hardware design in the form of balancing power usage vs capability. A big honking amount of solar panels is convenient, but then the mass of your grobot increases and you need a bigger more power hungry engine too. Software design in the form of a small but very capable stack based language.
One of the fun parts about grobots is you get more than one robot and cooperation between your robots is pretty important! There's a fair few published robots, ranging from simple algea-tactics (Just sit there and photosynthize) to bee-like swarms with workers and queens to stationary robots with big cannons that depend on a small and nimble scout to pick out targets at a distance.
But yeah, a match is 2.5 minutes; and only in the first 15 seconds is the robot is entirely autonomous, for the remainder of a match there's a 2-person drive team (plus maybe a coach standing behind them) operating it over WiFi, and also a human player that is able to interact with the field from the sidelines. Nevermind all the activity in the pits, repairing and adjusting the robot.
Not only would you have issues with remotely controlling the robots, as most of the competition isn't autonomous, but things are constantly breaking and need physical intervention. These aren't NASA rovers.
We need robotics competitions for 50+ year-old engineers.
Just sayin'. :)
https://www.servocity.com/actobotics
Granted, its not like Intel is allowing me to use there metal deposition printers, but there's a lot of good stuff there. I think they know me by name at this point.
Same with this place:
C++ was also always supported but from the one year we used that I can guarantee our team's dev speed was much less than LabVIEW. Something about the data-flow UI and live probing of values and VI controls view made it so much more intuitive to develop a robot with. We had a mecanum drive that we developed a dual layer PID system to control individual wheel power using a PID, but also a PID control on wheel rate. The effect was a super smooth but extremely fast control scheme that also had the effect of the robot pushing back if it were moved without user input. Great application in 2014 where the field was entirely open and physical defense was key, but I would have preferred to have normal wheels and all of the traction benefits that come with them that year instead.