We received our first finalist trophy at The Grauer School tournament! The whole team was very surprised - our robot was not exactly in the best shape during the qualifications. We tried taking our intake mechanism off, but that made our robot malfunction because the code didn’t correspond with what was attached to the robot. We were all very frustrated because our robot didn’t move for one whole round!
After many struggles - our dedicated members worked through lunch break to get our robot working - we decided to reattach the intake mechanism and borrow a weight from another team (Shockwave 3848)to apply more pressure on the center wheels. Fortunately, after lunch break we scored all the points possible in autonomous and it worked beautifully. Unfortunately, we got stuck on the crater wall couldn’t move for the rest of the round. At least we got partial parking points in endgame!
Although we didn’t have the best robot performance, we think that this was an opportunity to learn to be flexible and to overcome our emotions and compromise to get the robots working. We truly believe that this meet has strengthened our cooperation as a team, as many changes were made last minute and everyone had to be on the same page. We got chosen by the 4th alliance (Fast and Curious), and we beat the 1st Alliance in a huge underdog win, and only lost by 17 points in the final match! We were very happy that our autonomous worked perfectly both finals rounds and it was awesome to finally win a semifinal round. All in all, this has been a great experience and an opportunity to practice gracious professionalism. We still have a lot to work on!
Our original design for the robot; it's probably going to look completely different by competition 2...
We're currently trying to think up a team slogan - the best we could come up with was "We may be out of order, but our robot isn't! :):):):)::))):):)"
Needless to say, we would love suggestions!
FTC allows three methods of programming: OnBot Java, Blocks, and Android Studio. We tried all three this year and would like to share our experiences with them as well as pros and cons.
OnBot Java - A bare-bones programming tool great for teams with little or no experience programming
Blocks - A simple tool for teams who have younger members/have very little programming experience or a lack of a software mentor
As for us, we started out with Blocks for our first Tele-Op. Then, we started using OnBot Java which was sufficient for the early stages such as basic tele-op and autonomous. Once we were familiar with Java programming, we started to transition to Android Studio which has made coding much easier. However, we do not recommend it to most rookie teams unless they have a mentor with experience/advanced programmers, because it is very complicated in the beginning. At our first meet, Android Studio refused to run our program edits (it is useful to be able to change code during competition) because of a few updates it needed, and we did not have wifi to do so and hotspots are not allowed . However, we were able to copy and paste our code into OnBot Java and send it to the robot from there.
I hope this was an informative guide. Below is a link to tutorials for each programming tool made by FIRST and others.
Leave a comment if you have any questions or anything!
- Andrew G
We had a great time at our first ever competition! We placed 8th out of 14 teams and were chosen for an alliance by Retro Robotics 12666. Thank you! We were right next to ROH 4216 and got to see how their team runs so well.
What We Learned:
We didn't focus so much on scouting this time since we were not expecting to be a captain, but here is what we observed from the scouting we did do and the top teams did.
Feel free to comment below if you want to add anything!
See you guys next time!
- Andrew G