2220 Blue Twilight | 2024 Build Thread

Blue Twilight is excited to be doing our first build thread during our 17th season! This year we have 56 students and 8 mentors, most of these students being new to the program.

We’ve been working hard recently on a project designed to further the skills of everyone on our team. This elevator style robot is designed to play the Charged Up game. It will be used at demonstrations for corporate sponsors and community events.

We’re currently preparing to compete in the Minne Mini regional on November 18th.

Team Links:

16 Likes

MMR

On November 18th, 2023, several of our students and mentors attended the Minne Mini Regional Event, which is an off-season FRC competition hosted by FRC Team 2169 KING TeC at Prior Lake High School. The experience was a blast for our team; this was one of the first off-season events our team has attended in a while, and was certainly a great experience for all of the students and mentors that attended. We thank KING TeC, Prior Lake HS, FIRST in Upper Midwest, other teams, and any other organizations or contributors who made this event possible. Listed below are several key points relevant to the team regarding the event and our experience at it that are worth mentioning:

Orientation for New Members

Several new members from the team who had attended the onboarding nights our team hosted during the training season also attended this event. This was so that new students could get first-hand experience of how an FRC competition typically runs, and what responsibilities students typically engage in. With the help of older, more experienced team members/leads, many of our new team members got to engage in working on preparing the robot for its matches, talking to other teams about our robot, and overall just having fun experiencing what a robotics competition is all about. Some team members who had filled out a driver off-season interest form also got to experience being a technician, human player, and manipulator driver for the robot for at least one match each. The manipulator driver was paired up with one of our experienced drivers, Sean, throughout all of the matches. Lastly, many of our new students attended the various seminars hosted by other teams in the morning. Overall, the competition was a great training tool in preparing new students for the build and competition season.

Seminars

Team 2220 also hosted four thirty-minute sessions throughout the morning, prior to the qualification matches. For both of the morning sessions, two of our students presented on the Impact Award, which went over the requirements for the award and provided tips for other teams on approaching their Impact award submissions. For the first morning session, one of our mentors also presented on the 3D printing process, which covered numerous aspects of 3D printing from CAD, to slicing, to print orientation, etc. so that other teams could make the appropriate choices for the strength and appearance of their parts. Finally, our safety captain gave a safety presentation during the second morning session. The session covered multiple important aspects of safety, including shop safety, why a safety captain is a very important and necessary role for a team, identifying hazards within a team’s workshop, team safety training, how to keep your team safe, safety documentation, and why you can be the reason your team thrives or folds.

Robot/Programming Issues

During the regional, we ran into numerous issues with our robot’s arm and wrist needing to be re-zeroed and arm and wrist positional presets not working properly. As such, we couldn’t set our arm or wrist to certain positions autonomously, meaning that for all of our matches we could only earn the mobility bonus during the autonomous period of the match. In other words, we couldn’t move our arm or wrist to pick up game pieces during the autonomous period of the match, and during the teleoperated period of the match we had to manually adjust the position of the arm and wrist to grab and score game pieces. Additionally, we had trouble connecting with the LimeLight cameras on the robot, and thus needed to disconnect them throughout our matches. Lastly, our MaxPlanetary Gearbox (with a 90 degree output) on our wrist had to be replaced after the teeth on the bevel gear teeth (within the gearbox) became chipped.

FLL

Alongside the Minne Mini regional, there was also an FLL tournament going on. Team 2220 mentored two teams who attended this official competition: Team Spoon and Team Lucky Lego Lemons. Both teams had a blast talking to judges about their robots and did fairly well at the competition.

3 Likes

We have been using your battery spill cleanup video for years, excited to see what comes out here!

3 Likes

Kickoff

We started kickoff like our previous years, where we all gathered in the school’s cafeteria to watch the stream live. Following the stream, everyone went into rigorous study sessions, with everyone reading the game manual thoroughly, the intent that everyone could have a thorough understanding of the game and essentially become “rule experts.” A couple hours following the kickoff, we all took Citrus Circuits’ game quiz, along with a safety quiz that was made by our safety captain. The requirement for our team was that everyone had to pass both of these quizzes. We then tried something new. We split into three groups: a human game group, an XRC simulator group, and a standard strategy discussion group. We then presented our findings to each other. The human game group discovered that having one robot designated to charge the amp, while the other two robots designated to score in the speaker was the most effective strategy. The XRC simulator group similarly discovered that constant scoring into the speaker was the fastest and most effective way to get points. The brief strategy discussion group just went over ideal autos, along with questions that the entire team would want to be asking during Sunday’s strategy meeting.

Following Meetings

The next day we all came together and did more strategy. We determined what would be the most important actions we could take and what wouldn’t be needed to be successful this season and did some rough sketches for the individual subsystems on the robots. We also went right into some very sketchy prototypes of the main three subsystems, like two shafts with wheels on the ends of drills for the intake. The day after that we started testing how our off season demo bot would hang off of a chain simulation and programming tried to use WPILiB swerve drive code on last year’s robot. There was also a bunny :slight_smile:

Strategy Sunday

We discussed several major topics on Sunday:

  • Under the bumper intake vs over the bumper
    • We decided that an over the bumper intake was more important than under the bumper for a few key reasons. One, we figured that it would have been just more complex to build and CAD and under the bumper intake, especially since we’ve never done one before. With the game pieces being on the other side of the field, we figured that aligning up with the pieces on the ground would be easier with an over the bumper intake. Three, the swerve modules and their chassis/wheel heights meant that even if we raised our bumpers as high as we possibly could, we would still run over the game pieces.
  • Ground pickup vs source
    • We decided to prioritize a ground pickup intake for a few reasons. One, We felt like lining up with the substation perfectly would be difficult with it being across the field and in front of obstacles. Two, with a total of eight game pieces on the ground accessible to an alliance during autonomous, having a ground intake could play a significant advantage in being able to score those speaker points when they are worth a lot. Three, missed game pieces could easily be picked up and scored, rather than having to go back to the source and get a new game piece. Four, the ability to pile up game pieces in preparation for an amplification period could possibly serve as an advantage in scoring three to four game pieces during amplification.
  • Is the trap a trap?
    • We kind of put a hold on this question and are awaiting further prototyping and what the infrastructure of our robot is going to look like before fully deciding whether to commit to scoring in a trap or not. We do believe that its 5 point margin is very valuable, especially for getting the ensemble bonus, but that it may or may not be too high of a metric to achieve.
  • Should we be able to go under the stage?
    • We think that this question is not super crucial, as one can always just go around the stage, even during autonomous. At the end of the day, it is a nice feature to have, but we didn’t want to sacrifice the functionality of our robot for this.
3 Likes

UTB Intake

We reconsidered our decision of an over the bumper intake after seeing a post by team 95, The Grasshoppers. We are now prototyping and designing a full width under the bumper intake, as shown below.

Launcher Prototyping

Several launcher designs are being prototyped, experimenting with compressions and spin.
Video

Drivebase Build

We have completed our Mk4i prototype drivebase and handed it off to programming while we continue our work on the intake, shoulder, and elevator.
Video

Other Projects

  • Battery Testing

    • After receiving 2 new CBA battery testers, we crimped connectors and prepared cables to connect these testers to our new 2024 batteries.
  • Week Zero Scoring System

    • Work was started on a new scoring system for our week zero event. This is written in python, and will run on a Raspberry Pi 3B+ located inside the amp. All scoring during matches is reported by a human scorekeeper during the match, and sent to Cheesy Arena via a websocket connection. GitHub - Team2220/weekzerofield
  • Parts Organizer Spreadsheet

    • To keep parts more organized during the season, one of our mechanical leads created a Parts and Manufacturing Organizer. This organizer tracks part numbers, subsystems, and manufacturing status.
5 Likes

Hello all,

It’s been a minute since our last update, but boy do we have a lot to share.

First up, our 2024 CAD:

This has been public for a while, our apologies that it never made it into the OP. Please let us know if you have any troubles with access or export. It is our intention that the entire robot and all parts are available to anyone who wants them.

With the most important part out of the way, lets take a spin through the design as it gets today. Keep in mind that we do not view this robot as “finished” in any sense-- we expect there will be additional revisions in particular to the conveyor, shooter, and intake at a minimum.

Drive Base

We liked our 2023 drive base so much we decided to use it again! Core electronics are all present in a belly pan along with the robot battery. This is a 26x26 frame, though the frame perimeter of the robot is larger due to the under-the bumper intake. We are additionally using our configurable top cover and corner covers, which are available here (with logo-less variants!) for your enjoyment: Onshape

The frame is entirely 2x1 MaxTube, with crush prevention blocks at each corner and where the center rails connect. We’ve found that even using the MaxTube with scribe lines (which is all we have in the shop) this gave us sufficient durability for all of last season.

Arm

The arm is a critical part of our overall architecture. A lot of thought went into the dimensions of this, as it affects several critical parts of our strategy. In particular, the following were considerations for our arm geometry:

  • Having a very low stowed position for general driving
  • Having a stowed position that was entirely within bumpers and ideally fully inside frame perimeter (no hanging outside, we expect this game to be extremely rough)
  • Being able to hit angles between 15 degrees and 60 degrees on one side for autonomous purposes
  • Being able to hit 45-60 degrees at a high angle for less blockable shots near the subwoofer
  • Having a solid quick climb geometry
  • Being able to score in the AMP (this was not a key design driver)
  • Having a somewhat plausible geometry for scoring in the TRAP (this was not a key design driver)
  • Having a plausible SOURCE loading position (this was not a key design driver)

As you can see, we largely hit our goals with this overall design. One of the key parts to this was borrowing a trick from 2910 and offsetting the arm down such that the arm is very low while stowed and gains height when rotated.

You’ll also notice that the CAD model currently has a gas shock in it. We got really excited when we saw 3005’s design from last year (such a cool robot!) and wanted to try it out on this robot. So far it… has not gone particularly well. We’re having some trouble safely compressing a shock with similar force characteristics on this robot. Additionally, on some reflection, this is exactly the opposite of what we really want when we talk about climbing in the end game. So, the gas shock is likely going to go away at least for the near future.

In terms of specs, this is a 60:1 MaxPlanetary gearbox into a 58:18 #35 chain reduction, powered by a single Falcon 500. We have some plans to potentially drive this on both sides, but currently it is on a single side.

Intake

Like Sean mentioned above, we fell in love with the 95 intake the moment we saw it a few weeks ago and have continued to develop it since then. The current iteration uses 2" compliant wheels, with the outside 4" or so on each side taken up by some VexPro 2" mecanum wheels that we happened to still have lying around, and a low-friction PLA roller on the inside axle. We have not yet done a powered test with this arrangement, and I wouldn’t recommend anyone copy it right now-- we still have a lot of work left to do on our centering, where we’ve also experimented with static blocks in a few ways.

Shooter

Currently our shooter compresses the discs to 12" and fires them using 3" wheels on one side. Based on what we’ve seen from other OA teams we’re excited to give this a more in depth try. The shooter/ejection mechanism is where we expect to do quite a bit more iteration-- this version was designed prior to some of the prototyping work that we and other OA teams have done, but we’re compromising perfect for the sake of getting a full robot to programming quicker.

Conveyor

The conveyor uses ThriftyBot dead axle rollers, polybelt, and polybelt covers. So far we’ve been extremely happy playing with this, but it does have some additional things we’d like to tweak-- an interference issue below and being a little higher compression than we expected it to be.

Robot Pictures

Finally, some pictures of the robot as it exists now:





As you can see, we’re rapidly approaching “robot aliveness”-- we have a couple of wires left to make for the robot and are hoping to be driving tomorrow night! From there we expect to continue to iterate on some of the core problems remaining on the robot.

You’ll also notice some differences in materials. In general we try to cut 1/4" aluminum parts out of plastics before we commit to machining them out of aluminum. Ultimately a lot of the shoulder will likely be replaced over the next few weeks.

16 Likes

Controls! Robot wiring is not easy to get right. All of our problems with wiring were ultimately caused by a lack of supervision and training by experienced students.

So what did we do wrong?


Here we have a CAN bus wire that was not tested in the full range of motion of our arm, the XT-30 is getting pulled out and the wire is taut. We will remake an extension cable of the correct length, and strain relief this wire.


These wires are too loose, and are likely going to get caught in something. We try to avoid exposed wiring as much as possible, especially smaller wires as shown here. That PWM cable is for a proximity sensor, and it is spliced into the black cable shown. That bend radius also scares me a little bit, but the worse part is that it can just be pulled out. This will al be run inside corrugated tubing.


This wiring is not very protected at all and is even touching the chain above it. This part wasn’t super concerning, but It could be done better. The mounting of this spark max hides our logo, and makes the encoder harder to access if we need to service it. Also the port on top should be covered. We will remount this motor controller better, strain relief the wires, and route everything through corrugated tubing.


This one isn’t so bad. This is 22awg wire taken out of a 4 conductor cable. We will be rewiring this inside the tube, and leaving the jacket on the cable, as it adds extra protection.


These wires will interfere with our bumper mounting. Also no strain relief, and wire bundles that can get caught in things. Will be rerun and strain relieved.


These wires are hanging out in the intake, not strain relieved, and not bundled. These will be secured down and strain relieved.


Remember that prox sensor cable from earlier? This is the same one. It was run with the wires below it, but didn’t actually go through any of the cable ties. Like all of our wiring, we will run this inside corrugated tubing, and strain relief it.


If this bundle of CAN wire were to get caught and pulled, it would tighten on itself and cause even more problems for us. We’ll be bundling this properly, inside some corrugated tubing or somewhere more protected.


These 12awg bonded wires were run out the end of a tube (good!) with no grommet protecting them (bad). This is an example of somewhere where we were on the right track, but better supervision from myself and our leads would have prevented these issues. Also while it is run in front of our radio, we will be remounting the radio elsewhere.


An unmounted pigeon? Not only will that get caught in something, but it won’t work if it’s moving around as CTRE has yet to implement magic in their products. This is an example of poor training. A student was instructed to do something, without understanding what they were doing and why.


Just generally messy. We’ll be cleaning all of this up.


That explains our radio issues. Like CTRE, REV also unfortunately has not implemented magic. You can also see some exposed wire behind some of the heatshrink on those connectors.


We’ll be replacing all of our 6awg with 4awg so this isn’t a huge concern, but it’s still good to be mindful of bend radii.


Not all of the strands made it into this ferrule.


Wire stripped too long, exposing the conductors.


A broken XT-30.


Missing strain relief, and exposed wiring. This is bound to get caught on something.


Oh boy.

Overall, this will be a learning experience for everybody. This was a failure of our team leadership. Students were not properly trained or supervised to wire a robot. These are the things we need to remember for next time:

  1. Protect everything
  2. Strain relief everything
  3. Do things right, the first time (no shortcuts!)

I hope this will be helpful to someone else, and I want to emphasize that nobody who worked on this wiring is at fault here. There are things about wiring that you can only learn from having to fix broken wiring at a competition after it got chewed up in a pulley or caught in a drive wheel.

5 Likes

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.