On Saturday, September 28th our team competed in the Minnesota Robotics Invitational (MRI) in Roseville, MN. All members were given a chance to explore different roles in the drive team and alternate between each match.
Our main goal this year during the pre-season is to give all our team members experience and preparations for competitions in EVERY aspect of Robotics. We want all of our members to be capable of driving a robot, understanding how its coded, being a human player, scouting, answering questions, planning strategies and more. To do that, we are competing in 3 pre-season competitions before official seasons start.
We want to start the 2025 season strong with our best abilities. These competitions give us the opportunities to learn without the same stress and risk of larger competitions. We also get to introduce our new members to the FIRST environment!
Today ,June 13th, our team participated in Fridley’s 49er’s Day Parade!! We showed off our 2016 robot for a bit, handed out candy, we even got to answer questions and encourage other students to join robotics! We had a blast, enjoyed the weather and had our fair share of technical issues along with overcoming said issues.
Today we had 7 of our sponsors show up to our sponsor appreciation night! Sponsors graciously offered us a tour of the Nation Tool and Machinery facility and 3 people from Cummins, who took time out of their day, came to stop by. Our wonderful sponsors got to ask questions, talk to our mentors and students, and even play around with this seasons robot Princess Scene Queen! Thank you to everyone who came! <3
On May 7th, our team organized a staff appreciation night for Fridley teachers and staff members, due to it being teacher appreciation week. Individuals who attended were invited to come for refreshments, checking how our robot works, ask team members questions, take a look at our processes for an off-season robot, and even try their hand at driving this seasons robot. We had around twenty or more teachers, administrators, and school board members attend, and we are all so glad that they were able to make it! We love our staff members and appreciate everything they do for our school and community!
Throughout the night, we made sure to take pictures to show you just how much fun it was!
Today our drive team presented at the middle school assembly, to grades 5-8.
At this assembly we showed off our robots abilities, talked about what we do in robotics, invited 8th graders to inquire and potentially even join our team as they transition into high school. We hope to have left an impact on these younger students, here are some pictures to show how it went!
On April 16th, we presented to our School Board. Our slide show discussed FIRST: what it is, how it works, and core values. We also talked about what our team needs, wants, and is thankful for (a designated room and closet). Remi, ThuyVi, and Coral did a great job of preparing, answering questions, and keeping their composure when our video had no sound. This is our first step in what we hope will be the start of a successful outreach program with our school and our city.
Our main focus between competitions were major improvements to code, the addition of cameras, improving our autonomous driving, creating a method for keeping game pieces from getting stuck, and improving our intake. We went through many designs for our note-blocker, which would prevent notes getting stuck near our battery during matches, but in the end determined that more refined driving strategies would work best at competition. Our intake was improved, however, by adding a polycarbonate sheet and some bolts to the top of it to prevent notes from being pulled in too far.
Competitionday by day
Day 1
We had a few team members stay and set up the pits while everybody else brought their luggage to the hotel and settled in. Assembling the pit went well, and they later joined us at the hotel. Several other teams stayed at the same hotel as us, allowing us to make friends. This made the hotel stay and competition much more fun, since we danced, swam, and played games together.
Day 2
We played several practice matches and began scouting in order to get information about other teams and their robots. We also spent time connecting and building relationships with other teams. We had some issues with the robot’s controls behaving unpredictably in matches, but other than that our practice matches went smoothly.
Day 3
On day three we started to play qualification matches. We had some rough matches, but our drive team could improvise on the field for the best outcome. The robot took some damage on its intake, with the mechanism getting bent in addition to a motor breaking. In another match, the climber got caught on the stage in the center of the field and became severely damaged. Finally, we had a loss of electronic communication to the motor controllers, finding that some of the wires were pinched in the robot frame. However, thanks to our troubleshooting skills, (and a little help from another team), we were able to fix the pinched wire in time for our match.
Day 4
On the final day of the Granite City Regional, we played our last two qualification matches and got ready for awards and finals. While we didn’t rank in the top eight teams (which are the teams that get to pick alliances for finals) nor were selected for an alliance, we cheered on other teams and joined in on lots of spontaneous dancing.
Plan for the postseason (and summer)
In our remaining time, we plan to expand our fundraising efforts and better network with our sponsors. We have a few fundraisers planned for the postseason, including working closer with a few local businesses. To better support our goal of gaining more sustainable funding, we are also working on building a booster club. We plan on having build specific meetings during the summer to help us learn and improve skills.
First off, thank you sponsors for your generous support of our team! We really appreciate your continued support for the Tigers and wanted to take a moment to update on what we’ve been up to this season.
After learning this year’s challenge, we started off the season figuring out the priorities of our robot using elements of Design For Six Sigma (DFSS). We weren’t able to achieve all of the game’s scoring methods for the robot, but due to our design process, we were able to consider what was lower priority.
We had a larger build team this year, which allowed for easier assembly of the robot once we fabricated the required pieces. Thankfully there weren’t many mishaps during construction. Build speed picked up closer to when we were going to the Northern Lights Regional, which allowed us us to have time to practice driving before the competition.
The code team was led through the efforts of one dedicated student, though other students took an interest and helped from time to time, allowing us to get the code we needed done. This is our first year with swerve drive, which was a complicated system. We did not have any preexisting code to use as a base which led to issues, such as initial lack of an electrical output limiter, and had to be added at competition.
Our robot uses motors and chains to move our intake system, which has an arm and a wrist. The wrist moves to score in multiple spots, pick up notes, and feed notes into the note launcher. Our note launcher is fed by our intake system, and uses motors and wheels spinning at high speeds to launch the notes to score. Our climber system has two hooks that move with motors and ropes to lift our robot onto the chain. We got a lot of things done on our robot, and are proud of what we managed to do. We think that we did fairly well on robot construction, it turned out meeting our design goals.
The competition consists of robots competing in teams of three to outscore their opponents in each match. Winning matches and completing specific tasks during the match give ranking points allowing teams to continue through the group and place them favorably for the elimination portion of the tournament. There are multiple ways to score points, like launching orange rings (“notes”), into a high up area (The “speaker”). You can also put notes into a lower, vertical, opening (“amp”) that scores points and can increase the points of the speaker. At the end of a game, you can have your robot climb up on a chain (“Onstage”), and put notes into a trapdoor (“Trap”) for extra points.
First day – Load In:
When we got to Duluth, we started off with setting up our pit area. We had our pit built for repairs on our robot, for teams to know who we are, for giving out our pins, and for robot repairs. We had some of us setting up in our pit and others getting set up in their rooms. We were also getting ready for the start of practice matches.
Second day – Practice:
Thursday was our first full day at the competition, and we spent it participating in practice matches. This let our drive team get a feel for how the game played on a regulation field, as well as letting us see what fine tuning may have needed to be done before qualification matches began the next day. Some of our members also went to talk to other teams’ pits to learn about their robots and start networking.
Third day – Qualification Matches:
We began playing in qualification matches on Friday, and made it through six of our nine total matches for the competition. We won a couple of matches, but also lost some. On the bright side, we found areas on our robot that needed improvements, including our autonomous modes and our controls.
Fourth day – Qualifications end and Eliminations:
On our last day of the competition, we finished up with the rest of our matches. We had three matches left and ended up with one more win and two more losses. After we completed our matches, we unfortunately did not get picked for the elimination rounds, so packed up our pit and moved our equipment to our trailer. Then, we went back into the stands to watch the rest of the competition.
In the competition, most of our problems could be fixed right away. For some things, we had to work on them after the competition ended. A few of the challenging issues that had to overcome were things like our drive system, our controllers, and stress about performance. Later on, when the competition continued, we improved our uneasiness about performing on the field, and figuring out what the problem was in our drive system. We made solid plans and strategies to help our robot, and drive team, do well.
We worked closely with our mentors to double check that our controllers worked fine and were responding quickly and correctly to our robot, along with verifying the robot was receiving the correct driver station commands. We also tried reserving practice matches when possible, to test, and be ready for the match.
With many new members on the team, it had shown that we weren’t experienced and needed to improve our communication to work well with other teams. As we finished more matches, we started to understand how to work in the arena. Our strategies improved, and we found greater success in our matches.
We are most proud of our communication skills for scouting, judging, and strategy planning that we were able to develop at the competition. We are also proud that all of our team members were acting with gracious professionalism and how well we did with a new drive team. Even through all the challenges we faced while building our robot and the exhausting pace of competition, we all had fun while being professional.
In the time we have between competitions, we plan to fix up the robot, improve our intake, and program more procedures for our robot to follow autonomously.
Our next competition is the Granite City Regional in Saint Cloud, MN from April 4th to April 7th. Our goals for this competition are to get the highest placement we can, while maintaining a positive impact on the culture of the competition. We would love to see you there!
