This past weekend was a blast at the Gitchi Gummi Get Together hosted by the Duluth East Daredevils (2512). This was our first pre-season event with incoming rookies who were ready to get involved and helped them start to figure out what they want to do on the team. This event offered everyone on the team the opportunity to drive the robot and work in the pit. Some matches went well and others not so well and things broke but it gave the incoming rookies a look at what could happen during a regional with little time between matches.
On the second day, we were picked by fourth seed alliance captain, Rock Solid Robotics (4656), and assisted them alongside the Granite City Gear Heads (3244). We won our first semi-finals match against the first seed alliance and lost the second one. We went into the third match and had to replay it because one of the defenses got knocked out of place. After restarting it, a defense got knocked out of place again. In the final replay, we ended up losing the match. We then played one last match to decide who would be third place. Our alliance ended up winning the match and placed third.
Overall, the event was fun and a great opportunity for everyone on the team and a huge shoutout to the Daredevils for hosting the event for the third time. Now, we have time to prepare and fix the things needed for upcoming events like Woodbury Days and the Minnesota Robotics Invitational.
Today was a very busy day with lots of manufacturing of final parts for the competition robot. We made a spare intake arm and another shooter. The coders worked on writing more tests to prevent possible future code issues as we continue to improve our code in the weeks before competition. Stay tuned for our updates as we get closer to the Iowa regional!
Today we spent most of the time preparing the practice robot and the competition robot for tomorrow’s week 0 event at Centennial High School. We hope to find any possible issues that arise from extensive testing at the event. The marketing team spent time getting sponsor logos ready to go on the competition robot.
The CADers were using finite element analysis in Solidworks to test the 3D model of the robot out to make sure it can stand the tests of this years challenge. The code team have been writing more unit tests to help reduce the amount of errors in the code. With 4 days left in the build season, as each day goes by, each minute becomes more and more precious.
Today we made great progress on optimizing and finalizing many subsystems on the prototype robot. The remaining machined parts have arrived from our gracious sponsors which some of
them have been assembled with the rest of the competition robot parts.
The Electronics team have been hard at work finalizing their wire runs for the final robot. The Build team have been testing the prototype robot for possible improvements and have been building the competition robot. The coders have been working on autonomous routines and on new drivetrain gear shifters. We are five days out from bag day, so it has been nothing but hard work!
Today the prototype robot was driving around which was a great milestone in the build season. We were able to test all the defenses which went very well, there are some minor adjustments that have to be made. Testing of the subsystems mounted onto the prototype were also tested for consistency and other possible issues. The coders spent the day writing tests that point out errors in our code, and the CADers sent out the final parts order for the competition robot.
While all these other exciting things are going on, people have been hard at work machining parts in house for the competition robot. We hope to have all the parts for the final robot by next Wednesday.
After yesterdays successful meeting, we continued working on the prototype robot. We attached the wheels to the drive train after the hub caps arrived from our gracious machining sponsor, Harvey Vogel.
One of our coders finished setting up Jenkins. Jenkins is a CI (continuous integration) server, whenever someone on the code team pushes new code to GitHub, a web based source code management for programmers, Jenkins downloads the code and compiles it to see if there are any errors or issues with the new code.