6421 WarriorBots 2024 Build Thread | Open Alliance

Welcome to the WarriorBots 2024 Build Thread!

We are in our eighth year as a team, and we are based out of Muskego High School in Muskego, WI. This will be our second year participating in Open Alliance, and we are excited to continue sharing our design process throughout this season.

This year, we will be competing at 3 Regional Competitions:

At all of our competitions, we run the following initiatives to assist other teams and create an inclusive environment for everyone involved:

  • WarriorWATCH is our public scouting data and analysis system, available to all teams at our competitions. Teams will be able to scan a QR code to access raw scouting data and Google Sheets-based analysis tools. We are also working to make WarriorWATCH available at additional regionals through partnerships with other teams. We will share more updates on what data we are tracking and which regionals will have WarriorWATCH as we enter build season.
  • WarriorBots Helping Others (WHO) is a new initiative this year, but it builds on our efforts over the past few seasons to provide spare parts and direct assistance to other teams. Through WHO, we will be offering mechanical, electrical, and Java programming help, as well as a variety of tools and robot parts, to any teams that need them throughout the competition.
  • We hand out 3D printed awareness pins at all our competitions, supporting causes such as pride, cancer awareness, and more. We have distributed about 5,000 of these pins throughout the past two seasons, and we are excited to share them again this year. Be sure to stop by our pit to pick some up!

pride

Here are our important links for this build season:

11 Likes

2023 Off Season Recap

Throughout this off season, we competed in 4 off season competitions (Laser Lights, MROC, Rumble on the River, and TWIST). Overall, we had a lot of success throughout the off season, including giving many team members new experiences in the drive team and pit crew and receiving 4 different awards.

Laser Lights

  • Ranked 2nd
  • 2nd alliance captains
  • Event winners with our alliance partners 1732 and 1259
    • First event win with our 2023 robot, Chameleon

224x225,5%

Mukwonago Robotics Offseason Competition (MROC)

  • Entered 2 robots - our main robot, Chameleon, and a low/mid scoring cube robot, Gecko

1179.3333333333335x878.7565796561763

Gecko picking up a cube during auto

  • Chameleon ranked 7th, Gecko ranked 15th
  • Chameleon was selected as the first pick of the 4th alliance, Gecko was selected as the second pick of the 5th alliance
  • Chameleon and our alliance partners 2194 and 9991 (1732’s second robot) ended in 5th place, Gecko and our alliance partners 3197 and 93 ended in 3rd place
  • This was our first time entering 2 robots in an off season competition. We built Gecko in less than a week leading up to MROC. It had a couple matches where the battery came unplugged after a hard hit, but overall we were impressed by its ability to score quickly and run primarily a 3-piece autonomous during the event.

Rumble on the River

  • Ranked 1st
  • 1st alliance captains
  • Event winners with our alliance partners 7021 and 9992 (2977’s second robot)

281x134

  • Received the Innovation in Controls Award
  • Here’s one of our highlights from the competition:

flip6421

TWIST (Together, Women in STEM Thrive)

610x163

This was our first year hosting TWIST, an off season competition dedicated to providing an inclusive environment for female team members to try new roles and take their skills to the next level. To achieve this goal, the event requires all-girls drive teams. The event was a huge success, with 18 FRC robots/19 FRC teams attending (some teams formed partner teams to have enough students for a drive team), 2 FTC teams running a demo event, 8 FLL teams participating in a scrimmage, and an estimated 1200 attendees.

At the event, we were:

  • Ranked 1st
  • 1st alliance captains
  • Event finalists with our alliance partners 6574 and 5125

After TWIST, we began training new members in prototyping and pseudocode using our mock game, Allegro. The rest of our off season will be focused on running a mock kickoff event and setting our team goals to prepare for Crescendo.

3 Likes

Week 1 Overview - January 13th, 2024

Overview:

We’ve been enjoying some actual Midwestern weather lately, schools been in and out all week (not to mention our students have also had exams)

This week we spent time analyzing the new game and starting to get iterating on prototypes. These notes are mercifully easier to work with than last year’s cones.
We spent the first weekend of build season building a Kitbot on a swerve drive to see how the notes interact with it, and then began prototyping other mechanisms for our competition robot.

2024 Robot Goals:

After kickoff, the team met up and created a list of goals using the MSCW format.

Intake Team:

Our intake subteam started by researching whether an over the bumper or under the frame intake would be more effective.

Intake vid
IMG_9397-ezgif.com-video-to-gif-converter

An under-bumper intake with two sets of rollers was decided to be the ideal design. Different angles and dimensions were tested until we found the most effective organization.

Transfer vid
IMG_4968-ezgif.com-video-to-gif-converter

We then moved on to deciding how to go about transferring the game piece between intake and shooter, eventually landing on flat belting. We are currently deciding between one or two sides of belts.

Shooter Team:

During the first week of Build Season, the shooter subteam came up with two types of shooters: vertical and horizontal. The team has decided upon the vertical launcher for its height, consistency, distance, and ease of use over the horizontal launcher.

Shooter Testing Video 14 Feet at 29 Degrees
Untitledvideo-MadewithClipchamp-ezgif.com-video-to-gif-converter (1)

Programming:

The programming team has been testing commands to characterize our drivetrain and tune our feedforward and PID values. We began working with Kitbot to allow us to begin testing auto paths in the next week.

IMG_6799-ezgif.com-video-to-gif-converter

We started work on converting our swerve code to use Phoenix v6 to switch to running Krakens for our drive motors, and we finished code to allow our intake team to begin testing prototypes on an actual robot base. We’ve also started tuning our Limelight to detect notes for vision-assisted floor pickup, and we are investigating if we will need to use a neural network to distinguish the notes from other orange objects.

2 Likes

Meet Dolly, Dolly Parton

This is one of our test bases that we’re using to test how nicely our system play with each other

3 Likes

Week 2 Overview - January 22nd, 2024

Intake:

This week, our intake subsystem tested a variety of materials, angles, and distances for the wall behind the intake roller. Additionally, we tested different wheel types and wheel diameters for the intake itself. We developed a successful transition from the intake to the transition mechanism to transfer notes to the shooter.

Intake
IMG_2857-ezgif.com-video-to-gif-converter

Intake/Transition
-248056469060723556vid_117540814_190435_076-ezgif.com-video-to-gif-converter
At this point a lot of our testing is focusing on integration on Dolly our test base before moving on to driven floor interactions with our intake driven around on one of our swerve bases.

Shooter:

Our shooter subsystem upgraded from wood to prototyping in polycarb and metal to create a more realistic mechanism. We have been experimenting with how to give the ring spin to stabilize it as it flies. It got to a point where we were spending longer trying to keep our prototype functional than actually testing it.

IMG_87911-ezgif.com-video-to-gif-converter
Accuracy on that version got to be about as good as our football teams kicker :woman_facepalming:

Here’s the latest version of it getting mounted to Dolly, this new version is hooked up with Vortex motors instead of the CIM’s we were using for testing with significantly improved construction.


Dolly:

Dolly is our mock robot acting as a drive base and is what we are using to test all of our prototyped subsystems. Throughout the week we have been modifying Dolly to imitate what our drive train will look like potentially in season, so we can plan how our subsystems will fit together and so we can test them in unison. It has mainly been used to test our floor intake and note transfer, and we are working to integrate the latest version of the shooter and eventually the climber subsystems onto Dolly.


We :heart: Dolly

This is our first time building a full integrated bot prototype during season, we’ve been learning a ton from it.

Programming:

Our programming team has continued working on updating our swerve code to use Phoenix v6. We have gotten the robot to drive in straight lines, but we are still struggling with getting the robot to turn (see our other thread). Hopefully this issue can be resolved soon so we can finally get Kraken :eyes: :squid:

After testing our Limelight with different orange, red, and yellow objects, we determined that setting the Limelight to track the largest target was an effective way to filter out objects that are not notes. We have also been working on calibrating Arducam cameras running on Orange Pi 5s with Photon Vision for AprilTag detection. In the next week, we are hoping to start tuning autonomous paths, begin writing vision commands, and continue developing code to operate our mechanisms.

Wisconsin FLL State Championships

On a very different note, a number of our team members went up to Madison, Wisconsin yesterday to volunteer at the State tournament for FIRST Lego League. We are so excited to say that one of our local teams, Nuggets of Knowledge, placed 5th out of 306 teams in the state this year and have qualified for post season tournament opportunities. Congrats Nuggets! :baby_chick:


5 Likes

Week 3 Overview - January 27nd, 2024

Overview:

This week the V1 CAD design of the robot was finished and we’ve been mass manufacturing the entire robot. A big focus for this season has been to improve the quality of our processes and our manufacturing. Last season we removed all the hex shafts we had replaced on our intake to find them all within a 1/2in tolerance which might have contributed to some issues in the past. :eyes:


We’ve added a manufacturing tracker to our overall system documentation this year. We used this to keep track of parts being made during meetings, and it will also be used to track replacements as we get closer to competition. We’ll come back to this document once electrical has an update later this week.

Intake:

After finally getting all distances, measurements, and prototyping done, we have manufactured all necessary parts for both the intake and transition. After the manufacturing process, we were also able to construct the final V1 version of the intake and transition.

Shooter:

We finished the V1 shooter and tested its shooting against the subwoofer and ten feet away from the speaker. It proved successful and we moved on to our V1 final shooter which we are currently in the process of constructing.
IMG_8869-ezgif.com-optimize

Climber:

The climber is similar to our 2022 climbing mechanism. By using the bulb design, we’re able to bend a portion of surgical tubing around the pivot of one linkage for our climber. In 2022, we found that tubing just stretch around a joint would have trouble opening up initial due to the two arms being close to parallel. This is due to the spring force of the tubing not providing any force in the perpendicular direction. By adding a bulb with some standoffs, we are able to provide some perpendicular force to allow the joint to open before the horizontal force takes over and opens the joint completely to some built in hard stops. This allows our arms to spring out when needed. The arms are pulled back in with a cord linkage. When the hooks at the end of the arms are on the chain, the cord is wound back up, pulling our bot upwards.
IMG_6693-ezgif.com-video-to-gif-converter

Programming:

After facing some problems with our previous swerve code and Phoenix v6, we switched to using the Phoenix v6 generated swerve code and saw significantly better results. We slightly modified the code to incorporate a drive command and were able to begin driving the robot again today. We have also continued working on our vision. We had connection issues with the OrangePis, but we were able to resolve them by setting our RoboRio to a static IP address. Finally, we did a code review to ensure our initial code for mechanisms was organized.

Winterizer:

On Friday, our team ran our demo bot and STEM learning stations at a community event called the Winterizer! We were happy to be able to share robotics with over 120 students in our community.

First Full Assembly!

We stayed a bit late today to throw all of the mechanisms on the chassis to check for interferences. Fortunately they’re all minor. Waiting on some more flat belting stock to come in for the transition, along with a few other odds and ends to finish up the V1 build. Quick little shout out to @JamesCH95 and Team 95 for lending us a hand with picking out the paint job. First time we’ve ever decided to paint our bot, and we’re super pumped about how it’s looking. Seems like the team motto this year is ‘more red’ :heart:


IMG_9681-ezgif.com-video-to-gif-converter

4 Likes

Your build is looking great. We had a sketch similar to your setup that we really liked but decided to go with an elevator instead of an arm for the AmpTrap mechanism. I’m excited to see how this turns out.

4 Likes

That feeling when your first scrimmage is in 2 weeks



2 Likes

FIRST Wisconsin Advocacy Day - February 6th, 2024

This past Tuesday we had 8 of our team members attend FIRST Wisconsin Advocacy Day, speaking with our state representatives and senators to garner more support for government funding of FIRST Robotics. Currently the Wisconsin Department of Public Instruction provides $750k of matching funding for teams with students in grades 5-12 with a maximum per team of $6k. This grant started in 2015 and has tripled in amount since then. This season teams requested $992,000 of funding, so we’re excited for the work cut out for us during the 2025 budget cycle.




We have just started to get code working and tuned in, more in depth update coming this weekend after programmers get some time with the robot.

1 Like

It looks like its coming along nicely, I can’t wait to compete with you guys at Sussex!

1 Like

Week 4-5 Updates - 2/15/2024

Overview:

We’ve made a lot of progress in the past 2 weeks, including some iterations on our V1 robot build. Our programmers have begun working with the robot to tune all of our subsystems! Time is relative until you start counting days until our first competition, so let’s try and catch up a bit.

Wiring:

The big wire up was this week, only took about 9 hours of work for a robot with 17 motors and a bunch of other low power devices and sensors. We use these knockoff WAGO CAN connectors with Andymark ferrules on the ends for most of our CAN and Low Power applications. Big thing with these is to use a hexagonal ferrule crimper, they are so much more consistent than the cheapo square ones you find all over Amazon. We’re still using Anderson’s for our motor connections, we have some inline WAGO’s that Rev sells for some items and for emergencies, from testing we just prefer to take the time to use Andersons over them for general use. We’ve been using these two sets of connectors for years at this point and they work really well.



We’ve actually had to retackle wire management twice already to add more devices, definitely going to need a third after vision is added onboard later this week

We have developed this System Documentation sheet which originally was used just for electrical but we’ve expanded it since to be used for documenting part manufacturing and chain lengths. The electrical documentation works by making a large list of everything plugged in on the robot and assigning it to slots. We’re also pretty aggressive about labels this year which is awesome, but in general this helps keep everything straight between electrical and programming. We’ve been using this system the past few years and it has worked for us.

Please feel free to use and modify it to your team’s content if you’d like

Intake/Transition:

We’ve been debugging our intake and transition to the point where notes are getting picked up and ‘indexed’ pretty consistently which is awesome as that is usually our pain point. Note come up through our undertaker into the belted transition which has 2 TOF sensors on it from Playing with Fusion. These are used to tell where the note is exactly in the transition so it can be automatically adjusted with code. This was one of the earlier versions of that logic, its currently a lot less dramatic but this shows the process of centering pretty well.
20240214_185158-ezgif.com-video-to-gif-converter

Some things we’ve noticed are that notes get super stuck to polycarbonate, but slide really well against wood and nylon. We noticed this during prototyping, we even had some very classy wood veneer on our robot for a minute there before we realized nylon worked just as well. We’re still messing around with adding nylon centering fins so notes don’t get stuck on the NEO and various bolt heads, but minor tweaking at this point is a-ok with us.


Older version of it with the wood veneer peeking out

Shooter:

We started running our V1 shooter at an advocacy event and noticed the Vortex’s were getting super hot. Turns out we just had a ton of friction from the chains driving it, so we ended up making the call to just go hard into a V2. We should have that assembled today so we can show that off Saturday.

Climber:

We got off the ground for the first time this week! We are still in super early development on this setup, but because our climber arms have 2 sets of elastic, we can control which goes up/down first based off the amount of spring force each joint has. Less spring force, it moves first as the path of least resistance. We’re working on a number of big tweaks to this system right now to require less human babysitting, hoping to have it working well enough to try at our scrimmage on Sunday, but it is doing the things we hoped it would so we’re overall pretty happy with it right now.

IMG_9992-ezgif.com-video-to-gif-converter

Bumpers:

Normally bumpers are a 1 Saturday operation for us, this year it’s taken two whole weeks. We’ve been tweaking how we mount them to work with the floating mounting rail system we have (We’ve been loving the rails though, thanks for the idea 3847!). We’ve settled on these polycarb plates bolted to 4 independent bumpers that on 3 sides get bolted to the sides of our mounting rails, and the intake one just has some permanently mounted bolts that get a wing nut on the end similar to our previous bumper system. The intake side one is higher than the rest, trying to prevent notes from getting under us as we drive around.

We used a bit of extra heat transfer vinyl to mark which side is which, quality award here we come

Programming:

We were able to get our intake and transition working together to pick up notes off the ground.

WithCenteringPanel-ezgif.com-video-to-gif-converter

After getting our intake working, we also tuned our transition arm and were able to score for the first time in the amp!

IMG_9955-ezgif.com-video-to-gif-converter
We beefed up the arm joint after this as well, bit less floppy

We have been making steady progress on calibrating cameras, and have been able to reliably detect AprilTags from about 25 feet away. We have also started writing commands to automatically pick up notes and align to the speaker. To test our AprilTag localization, we are creating a custom field layout to fit our practice area.

Moving forward, we are going to begin tuning our shooter to set angles and velocities, then begin working with our climber and trap scoring. We are also looking forward to getting on a full field at the Sussex scrimmage to test our auto paths and vision.

Scrimmage This Sunday!

We’re looking forward to competing in our first formal scrimmage event this Sunday! At this point we know what needs to be fixed and are mostly just fighting the clock. Big focus this week has been keeping our priorities for what needs to be done by the scrimmage in mind. One shot location is fine, we can tune the shooter at home. Climbing on a full field? That we have far less access to so we’re trying to prioritize that more for this week.

On a personal note I think our team in general is being a bit hard on themselves when things don’t work immediately or as quickly as they hoped. The team is doing AMAZING right now and it’ll be exciting to see everyone’s hard work paying off as we get things moving. Going to need to do some accomplishment recognition on Saturday. We compete Week 1, clock’s ticking

5 Likes

It’s going to be super interesting seeing the robot on a full field this weekend. Here at 1259 were super excited to get onto the field and see how our robot works. We’re waiting to put our climb on till after Sussex though. It’ll be super interesting what each team brings! See you Sunday! :smile:

1 Like

Sussex Scrimmage - 2/18/2024

Overview

This past weekend we were able to compete at the Sussex scrimmage hosted by 537 Charger Robotics. First time we’ve been able to test our bot on a full field, so let’s get into what we learned

  • CAN Utilization - Right now our robot has 24 CAN devices, 15 of which are CTRE. We’ve started looking into the CAN utilization optimization available with Phoenix 6. We could add in a CANivore, but we’ve noticed a far greater amount of issues running our CANivore’s on the Rio 2 as opposed to the Rio 1 so we’re hoping to avoid that solution for now.
  • Connection to Driver Station - We had persistent issues across different laptops with losing connection to Driver Station. We have hopefully traced the issue back to our network switch, and we ordered a new one to test.
  • Amp Lineup - We had expected the amp to be a bit tricky to align given its similarity to the single substation in 2023 and that was definitely the case. We’re leaning into vision alignment hard this week.
  • Amp Scoring - We’re really happy with how our transition arm is able to score in the amp. Only tweak we might make is to have it lean a bit further away from the amp to avoid it being out of frame (and potentially making contact out of field perimeter)
  • Build Robustness - We’ve been focusing really hard this year on a robust robot design and that was on full display at this event. Last year we were having motors rip out of their mounts and elevators fall from their slides. This year we tightened up 1 bolt, and only needed to go through our spare parts to help out other teams. Very excited to see how it holds up in season
  • LED Feedback - We had a few instances when our driver couldn’t tell that we had a note in the robot, so one of our priorities has been fixing our LED code to allow us to set a color when the note is detected and for other signals throughout the match. We started with using a CANdle to control our LEDs, but we were having trouble with the software to use it. We are switching to use the WPILib Addressable LED class because it has been the most reliable in our previous seasons.

1000013822


IMG_0083_1-ezgif.com-video-to-gif-converter
IMG_0083-ezgif.com-video-to-gif-converter

3 Likes

Oh….oh heck

Thanks FUN!

Check out the Week 1 forecast here!

3 Likes

Just wanted to post some interesting pit data from Lake Superior. 55 bot field, 44 are swerve drive, 9 are tank, 2 are mechanum. 80% of the field is running swerve.

Lake Superior Regional - 3/5/24

Outcomes

  • Ranked 32/55 Teams
  • 2nd Pick of the 8th Alliance
  • 4th Place in Eliminations
  • Set event high score in playoff match 10
  • Ranked 13th in EPA at the event. Ranked 9th in Wisconsin and 277th in the World
  • Won the Judges Award, a new one for us
    • This event marks 8 regionals in a row of bring home an award (or 2)
  • Dean’s List Finalist for the second year in a row.

What Went Wrong

  • Went out for our first 2 practice matches and autos in both immediately went wrong. We believe this was from AprilTag based odometry issues. In the second match, the robot drove full speed into the corner of a stage truss, bending our bumper, front intake rail, first intake shaft and a transition shaft. We quickly assessed what we could change to prevent that from breaking in the future, as we would definitely encounter another collision like that in the future. We decided to change the front rail from a REV Ion 1x1 to a REV Ion 2x1 Grid Pattern tube. All other parts were easily replaced.
  • After this incident we removed AprilTag updates to our odometry for the remainder of the event. The functions we were using it for were not ironed out fully at this point anyway, so we made the decision to shelf it for now.
  • Climbing: We had tested climbing at home with a team-version of the stage and found it to be acceptable there. Once on a real field we found that what we had to do to line up was improbable for a driver to do properly. We decided that it would be better to focus on cycling more and not wasting time on failed climbs throughout the event.
  • Speaker: Due to removing our vision system at the beginning of the event, we had no way of lining up with the speaker at distance. We went with the backup of having 2 shot locations. One driving into the subwoofer and 1 that is about 1 robot length away from the subwoofer, in the case that a robot was already there. The latter ended up not being very useful and was removed before the end of the event.
  • Cancoders: We had an issue with our drive system that popped up in the last minute of our first quals match and was not found before the following match. One of the steer motors was not receiving any signal, but was also not giving any error lights. We thought we may have burned out that Kraken, but before going through replacing it entirely, we wired in a backup to make sure it would function. But after setting CAN ID’s and everything needed, the replacement acted the same. In the end, we found that the power wires to a CANcoder had been sliced. We didn’t catch it initially due to a mechanism that is mounted above the swerve pods. We had issues with the same CANcoder going out in our final Elims match, but instead of wires being sliced, the wire had snapped at the ferrule. This is prompting us to take some time before our next event to make our electrical system a little more robust.
  • Amplification: We did not make the best use of amplification throughout the event. In several matches we either scored in the amp during an amplification period, didn’t amplify the speaker before scoring and just in general missed opportunities to score more points.

What Went Right

  • Auto: We had a variety of autos that all drove to the correct points every single time. The biggest issue we had was final tuning of shooting angles and speeds. This is part not having vision for distance and differences between notes and the speaker at home vs at the competition. We ended up finding the correct speeds for a few locations, which allowed us to have a few effective autos.
  • I want to make a special note on this that we wrote a new auto just for eliminations that better complimented our partners. It included 1 note from the close line and 2 from the center line. This auto worked perfectly on only the second time we ran it, with the only issue the first time being the shooter angle was ¼ of a degree too high. We are very proud of all the work we put into tuning our system so that we can have high quality autos that always go to the correct locations, pending other systems functioning correctly with it.
  • Amp: With some of the other issues we had, we decided to dedicate ourselves to being primarily an Amp bot. Our driver was incredible in lining up quickly and scoring in the amp, only missing 1 or 2 notes the entire event. This paired with our ability to still score in the speaker when amplified or during the last 20 seconds made us a valuable alliance partner (at least we think so).
  • Pit Crew: Our pit crew was working better together than we ever had before. Every time we came off the field they were quick to make any fixes and followed procedures so we never missed anything before putting the robot on the field. I am incredibly proud of the work they did this weekend.
  • Scouting: We scouted with 3 other teams, 930, 6381 and 7915. We found our data to be very accurate and was useful during the whole event. We spent some time this season trying to make our analysis more user friendly and it paid off. We are happy with the metrics we decided to scout and found most of them very useful. We still have a little bit of tinkering to do before our next event, but we are overall happy with our system.

What we learned

  • Our Robot is certainly capable of competing at the level we set to at the beginning of the season.
  • We may not be at the point for a full AprilTag based odometry system to be reliable enough to use at competition.
  • This game isn’t won by having the most cycles, it is won by having the most effective cycles. Our scouting data shows that the best cycler at the event was not the one in 1st. It was the team that best utilized amplification periods.
  • This game is incredibly fun to play and watch and has an incredible amount of depth to its strategy. Both 2O 1D and 3O being effective alliances is very interesting. I’m very excited to see how the meta develops over the coming weeks.

Next Steps

  • In the next week and half we will be working on a number of improvements to get our robot to where we want it to be. Improvements include:
    • Get off the ground and be able to harmonize.
    • Better shooter consistency.
    • Vision aim assist for scoring in the speaker from distance.
    • More robust electrical system
    • Smarter use of amplification
    • Trap?

Overall, our team is happy with our performance at Lake Superior Regional this past weekend, and will be working hard to be even better at Wisconsin and Midwest.

Some other fun statistics that may upset Minnesota folk. Across both Duluth events, Wisconsin had 22 teams, or 20% of the teams overall. Wisconsin took 28% of all awards and 38% of all qualifying slots. I’m very proud of our state’s ability to be contenders outside of our own borders.

5 Likes

Wisconsin Regional - 3/26/2024

So what did we change between events?

Our programmers decided to print business cards for everyone after coming home from Duluth with the famous Karthik quote

The most important thing you can do between events is programming and practice.

If you have not watched his presentation from champs on Effective FIRST strategies I can’t recommend it enough.

We tried to take a balanced approach between mechanical upgrades/repairs and programming time, some things we changed were:

  • Threw our old climbing arms in the trash can and simplified them down (with a good bit of inspiration from 3940). While we’re still like 2 inches away from the trap, we all agreed this was a much better solution overall (we’ll come back to this after Wisco
  • Swap from 2 sides of Colson wheels to one side of 4" stealths. This improved our accuracy dramatically, especially from distance. Had to retune the shooter, but yknow how it goes
  • Adjusted our vision setup to align to certain tags instead of attempting full field odometry

Outcome of Wisconsin Regional:

  • Ranked 12/54 Teams
  • 1st Pick of the 2nd Alliance
  • Going into eliminations, the robot was out on the practice field and our amp arm suffered a catastrophic failure. The sprockets being used on the max spline had effectively worn themselves into sharp teeth that snapped the chains. We also had our gearbox for one of our motors shear through 3 bolts at once to rip itself free. While we were able to get it fixed during eliminations, we were just a bit too slow, and a backup bot was called in. We would like to thank our amazing alliance partners 93, 2062, and 3734, we most certainly have a bit of a fire under our rears going into Midwest.
    IMG_0804

On a more positive note…

Our good friends Walnuts and Bolts 6643 won their first award! We are so jazzed for y’all!
IMG_08501-ezgif.com-video-to-gif-converter

Tyler was kind enough to interview us for Behind the Bumpers! Learn more about our robot Frog (and our Off Season competition TWIST) over on FIRST Updates Now!

We volunteered to tear down the field this year and it was a lot of fun (and pretty informative for planning our off season event). We only got to keep 3/4 of the field carpet (seems like the previous event forgot to pack the practice field carpet :eyes:) but it should be more than sufficient for the new workspace we’re moving into in August (hopefully).


Random other photos, good energy, passion, and footwork across the board for this crew






Alright, what now?

So Wisconsin didn’t exactly go how we wanted, that’s okay, gearing up for Midwest we took the approach of getting little wins to make big differences

Problem 1: The robot goes to the right spots in auto, but will randomly kick pieces away, what’s going on?
Our programming squad figured out that sometimes the auto code will get a false positive on one of our TOF sensors, indicating that the robot already has a note, so don’t turn the intake on. We added in a bit of a delay to make sure we’re getting an accurate reading, and our autos have been rock solid ever since (yay)

Problem 2: Sometimes our shots seems to not be set to the right speeds, what gives?
The entire shooter structure of the robot moving doesn’t help when you’re trying to be accurate huh. We’ve reinforced the heck out of it, so far so good. Programming had to retune the shooter for like the third time, but it’s so freaking clean now, it’s awesome to watch
IMG_2916-Trim-ezgif.com-video-to-gif-converter

Problem 3: Why no uppies?
We’ve been struggling to get off the ground because we tried to use our trap sequence to climb, not time effective, not dialed in enough. For Midwest, we adapted those arms we made after Lake Superior to get us off the ground fast. We can get that melody RP, now let’s go for that Harmony one.


IMG_0938-ezgif.com-optimize
Improvise. Adapt. Overcome

Problem 4: We have no field, we work out of a hallway, how are we supposed to get our driver good practice cycling?
Fortunately our buddies over at 930 have been kind enough to let us live on their field on the weekends.

Problem 5: We love our pit layout this year, but the backdrop is kind of ugly
Nothing a trip to Walmart and 4 hours of vinyl cutting on our Cricut can’t fix.


Problem 6: WHY ARE OUR CANCODER WIRES SNAPPING???
Make sure you trust the wire you’re using, we’d been using these big donated spools of 22AWG that have very brittle strands inside, they were snapping off randomly and they just so happened to be on our cancoders. Frustrating problem, but we’re very glad we’ve gotten to the bottom of it.

We look forward to the insanity that will be Midwest 2024 :frog:

1 Like

Midwest Regional Recap!

We’ve had some time to rest and recover after our third and final regional, time to go over what we learned.

  • Our brand new cart did not enjoy the load in ramp at Midwest, it eventually got a very cool 2x4 pegleg for the entire competition so it didn’t completely topple over :woman_facepalming:

  • It climbs! We actually had a functional climber for an event, was very cool to finally see Frog get off the ground

  • We lost a few more matches than we should have and it took us a while to figure out why. One of the back panels on the amps had begun to bow out, which resulted in our amp pieces rebounding into us, rendering us a defense bot for the rest of the match. Big thanks to Greg from 930 for pointing this one out to us. We might look into better note protection for the off season, but mid event our human player just pushed on the amp to reduce the bowing which helped tremendously. The amps are preforming as expected
    *We had an absolute BLAST checking out all the diverse teams at this event. We got very good at Google Translate helping our wonderful Turkish neighbors find the tools they needed throughout the event.

  • We helped rebuild a few bots, and made some friends along the way


  • Our front rail took a few hits this event, managed to snap out 3/4" cabinet plywood and bend the solid 1/8th rail behind it a few times. Fortunately pit crew has gotten very experienced at this kind of repair




    clampclampclampclampclamp

  • We had an issue partway through the event where our network switch dipped out right near the end of a match. Despite the hot glue, the + terminal on our voltage regulator wore out and was loose. Ol’ Reliable decided it was no longer going to be reliable

  • We attended the team social which was a blast!

  • Frog vibes are good vibes, we went through SO many buttons and mini frogs at this event

In the end were were the 2nd pick of the 8th seed alliance. Big thanks to 112 Plus One and 2383 Ninjineers for being fantastic partners. We ended up placing 4th after just simply being outscored. Not a bad way to end a season

The curtain falls…or does it?

We are still meeting, we are already making plans for improvement over the summer to keep making the WarriorBots the best team we can be! Stay tuned for our Off Season thread…and speaking of off season

TWIST Registration is open now!
Learn more, volunteer and register your team today!