6908 Infuzed | 2024 Build Thread | Open Alliance

Welcome to the 2024 Infuzed build thread! This is our first year as part of The Open Alliance and our fifth season in FRC. The goal of this thread is to be useful for your team, fostering creative discussions. We will also project our team to a wider audience in light of both good and bad moments.

FRC 6908 is a community team based in Raleigh, NC, and run by our parent 501(c)(3) nonprofit, InspireNC. For the upcoming year, we have 35 students from the local Research Triangle Park region. We have 9 primary mentors with expertise in the fields of programming and business. 2 of the mentors are also team alumni.

We will be participating in the FNC District Orange County and one of either the Mecklenburg or Wake Events in Week 1 and Week 4 respectively. Of our 5 seasons so far, we have had relative success winning 7 awards but have not won a blue banner yet. Infuzed has qualified for the District Championship once and made the playoffs. We hope to return to the NC championship this year.

Mini Logo 6908 PNG

What we do:

Infuzed was created with the mission of being a student-run, student-led team. We wanted to be a place for students to learn regardless of prior robotics experience. For this year, we want to continue our goal of spreading STEAM (Science, Technology, Engineering, Arts, and Math) education in our local community while also securing a long-term sponsor. Our non-profit organization, InspireNC, further exemplifies this goal with other programs focusing on student involvement as well as through outreach. The organization has reached over 5K people from across the world since its creation in 2017.

Open Alliance Updates

We will be updating the thread biweekly during the offseason and twice a week during the build season. During the offseason, we will be meeting once a week based on the schedule of upcoming offseason competitions and outreach events.

Team Links

We wish all of you the best next season and remember, Knock on Wood!

7 Likes

Looking forward to an amazing season from this team in 2024!! Can’t wait!!! :crossed_fingers:

1 Like

Biweekly Update 1: 11/4/23

In theory, this update was supposed to be last week, but time flies when planning for next season. This update is supposed to shed some light on what Infuzed is currently working toward regarding business, outreach, FRC, FTC, and more.

Some old robots!!

2023 Robot: Takeoff

2022 Robot: Klaw

2020 Robot: Cookie Monster

Offseason Update Part 1:

Going into this summer, our team had established key goals for the upcoming season in:

  1. FTC: Restarting our FIRST Tech Challenge Team: Insight after 2020
  2. Fundraising: Securing money both from membership dues or corporate donations
  3. Outreach: Planning more diverse outreach events relating to non-robotics events
  4. Member Recruitment: With only 10 new members after the 2023 season, we had to recruit heavily

This update will cover FTC and our fundraising plans.

FIRST Tech Challenge

Our nonprofit organization InspireNC, hosted and ran a FIRST Tech Challenge Team before the pandemic, not only to expand our programs as a younger age group but also to create a pipeline for students to grow through. After 2020 however, we did not have enough interested members or the space to host a program. This summer, our plan was to recruit team members for Team Insight and also to have mentors for this program. We asked returning members and also collaborated with our friends over at FRC 4828, the Roboeagles, to set up a mentorship program. The team now has 10 members and is currently planning and designing for its first competition.

Insight working on setting up an FTC field

Fundraising

Infuzed did not have enough money to participate in FRC for 2024 at the end of last season with less than 2K in the bank at the start of August. The main thing that we did to identify how much money we needed to raise was budget our expenses based on data from previous years. It has been linked below if any of you are interested in seeing our expenses.

Budget Information!

After this, we started applying for grants and have had mixed results so far. Last week, we secured $1500 from the Intuitive Foundation and $3000 from the ArgoSy Foundation which will both be put toward registration. We also gained access to NordVPN’s password manager and VPN for free, which is equivalent to almost 5000 dollars. Despite the amount received and another 4000 from membership dues, we still are short of our goal and hope to receive more grant results in the upcoming months. In the future, we hope to provide an Open Alliance update on solely business proceedings.

Meeting Updates

We are still hosting a general meeting every Saturday from 2:30 to 4:30. We anticipate these times to increase in the upcoming months as we ramp up toward the 2024 season. The FTC Team will soon start having midweek meetings while Infuzed will host upcoming workshops involving safety, grant-writing, CAD, and more.

Pics and Flicks!: Bonus points for thoughts on who looks the most scared in the last picture



That’s it for this update, but the next post will (hopefully) be in two weeks discussing our offseason competitions, recruitment, outreach activities, and our brand new scouting app.

5 Likes

Infuzed will be hosting robotics workshops throughout the next few months as a form of outreach but also to give back to the FIRST community. These are free and most will be streamed online. Check them out below!

Free Robotics Offseason Workshops

In side news, we also won a REV Robotics Sticker Giveaway for Thanksgiving!

We will be back later this week with a comprehensive update on team activities including our progress in building a drawing machine! Have a great Thanksgiving everyone. :turkey:

1 Like

Biweekly Update 2: 12/14/2023

Happy Thursday everyone! As build season approaches, Infuzed has been busy at work with Workshops, Outreach, and Scouting Progress.

Workshops (Community FIRST Outreach):

Infuzed over the past month has conducted several outreach activities via workshops as part of the Community FIRST initiative. This was run by FRC #2096 Roboactive!

  • Our captain, Kartik Nanduri, is hosting a series of CAD workshop over Twitch for rookie members. We planned many different methods to distribute these workshops online but went back to our personal favorite in Twitch. To stream OnShape, we used StreamLabs to be able to share a screen and present for free. This workshop included basics of part design, and usage of the Onshape interface. We have had gained interest from across the United States, Turkey, Mexico, and Israel.
  • One of our mentors, Mr. Alex, recently hosted a Git workshop for our members as well. Here he talked through the installation process, basics of version control, and basic commands you can use to update a git repository. He also talked about uploading your git repository to GitHub, which team Infuzed will be using for version control regarding our codebase.
  • Next week, our team will be hosting a “revamping a team” workshop. In this our team business and outreach leads will be presenting strategies that Infuzed used over the past summer to increase member involvement and sponsors. We will also be talking about leadership and the struggles that come from running a FRC team.

Outreach Activities:

  • InspireNC recently attended Artist’s Alley at Green Level High School. We planned to sell some Christmas decorations, such as 3D-printed christmas trees, laser etched christmas boards, and showcased some art as well. Through this event, we fulfilled one of our season goals of diversifying our outreach events. This was something that helps us better fulfill FIRST values, for our own team and the local community.

Scouting App:

  • A few of our members are reworking our scouting application from the ground up. We’re planning on adding new features, a proper database system, data visualization features, and potentially switching hosting services as well. We’re also hoping to have an automatic data-scraping system from TheBlueAlliance, which would eliminate the need to manually enter team names and numbers. All in all, we’re expecting a completely refreshed system, with our scouters’ ease of use in mind.

This was our submission for the 2024 Safety Design Animation Award! It showcases computer vision as a method to keep people safe and emphasizes fire safety in robotics.

Check it out below!

Safety Animation Video Submission: With Safety, Everything is Fine

Season Update 1: Kickoff

Only a week late this time 🫨

Kickoff Recap

Kickoff started a few days before we met to decide on a pre-season buying list. This consisted of discussing a few goals for the season and setting realistic expectations for the 2024 season.

Swerve or No-Swerve

This was one of the biggest debates we faced this season. On one hand, we had seen the effectiveness of swerve over the past season and its increased mobility. However, this would be our first year running Swerve, and wouldn’t have time to test our code and modules in actual competition.

It took us until December to make a final decision regarding Swerve (MK4i!), and decided against it in the end. We did make a parts list of things that we would need to buy as we plan to buy it during the offseason.

Build Season Schedule

A really useful app that we use to assign tasks and have a set schedule is ClickUp! It’s a pretty easy layout and has helped us map out our schedule over the next two months during the season. We would recommend it to any team looking to structure all their activities and is free of cost for all non-profit organizations.

Now…the actual event

We met at our workshop at SMILE around 10 AM on the day! We cleaned up our shop and then settled down with some pizza to watch the livestream. After the reveal video, we started off by reading through the game manual, rewatching the kickoff video, and making a scoring analysis.

This scoring analysis was crucial for how we planned to design the robot and told us what to prioritize. We split it up by the usual FRC game categories of autonomous, teleoperated, and endgame.

If anyone wants to take a look at it, it’s linked below!

https://docs.google.com/spreadsheets/d/1QTy5NDW3D4lNHs4ZElH9YiA5v4czjijhlNX7lk7itN0/edit?usp=sharing
After scoring analysis came a brief break and then all havoc broke out. We discussed some initial designs and also prototyped a bit. We also had some fun with the game piece!

Through all of this talk, we decided not to finalize a design so early into the season and set a hard timeline of the weekend after kickoff for this.

Tomorrow, we will cover our team updates after the first week of design and present a more comprehensive update on programming activities.

1 Like

Week 1 and 2 Update: We are up and running!

Business

We got some new sponsors! SendcutSend, an online laser cutting and waterjet cutting service was the latest company to support our program. We cold-emailed them about a potential offer regarding using their metal services this season and received this.

While on the topic of sponsors, here is our finalized list of sponsors (for now?) for the 2024 season. These are the list of companies that will be displayed on our website, t-shirts, and competition banners. We also described what the sponsor provided and how the money will be used.

InspireNC: Our parent organization, providing us with our tools and material resources

Argosy Foundation: Registration Sponsor, provided by FIRST North Carolina

GeneHaas Foundation: Money for FRC, FRC parts sponsor

Intuitive Foundation: Money for FRC, FRC parts sponsor

SMILE Camp: Shop Location, providing us with space to store our tools and meet regularly

Sheetz: Monetary Donation going toward general costs such as rent

IBM: Mentor-provided sponsor, going toward general costs

NordVPN: Non-Profit Discount, giving us free VPN and password manager applications

Limited Run Games: Transportation Sponsor, giving us their company van to take our robot and parts to in-state competitions.

Controls (Programming+Electrical)

2024 Code Repository: GitHub - frc6908/2024robot

The Controls team had 3 main objectives for the 23-24 Season:

  1. Use PhotonVision and AprilTags
  2. Educate new programming members on Command-Based Programming in C++
  3. Implement our Autonomous Mode using PathPlanner

Teaching New Members

One of the biggest challenges we had heading into this season was teaching interested rookies programming. With more than 10 new interested programmers, we started them off with the WPIlb documentation, walking them step-by-step through the basics of C++ and Electrical Hardware. Over the past two weeks, the rookies have worked on building a Kit of Parts chassis and programming it to move. While this chassis will not be used for actual competition, it was a hands-on way for them to experiment and learn.

One of the most significant objectives for our Controls team this year was to implement our code using PathPlanner correctly. This would be our first time implementing this software, and we started before using the software by going through our possible plans for autonomous in the upcoming season. Given that we spent over 4 hours on one day discussing, we got a bit hungry….and decided to name all our Autonomous Ideas based on the food we wanted at the moment :yum:

Week 1 Ideas

Idea 1: Diagonal Amp+ Rotate+Pickup/Shoot Wingstop (2-7 Points)

  • Mobility Achieved
  • Amp 1 (working toward Amplification/Coopertition)
  • Alignment on point for amp score
  • Not enough time for shoot potentially
  • Option for top Alliance

Idea 2: Center of speaker, 3 piece speaker (Taco Bell) (17 Points)

  • Mobility Achieved
  • Potentially not getting third piece scored
  • Far from human player station
  • Really good for week 1

Idea 3: Center of Speaker 2.5 Piece (Chicken Tender) (12 Points)

  • Preloaded game piece
  • close to human player station
  • unlikely to collide with other robots

Over week 3 and week 4, we hope to establish 1 consistent autonomous and 2 somewhat reliable autonomous modes before testing on the robot for most of February. Given the relatively low level of independent score that is average in North Carolina in week 1 competitions, we focused on 1 high scoring autonomous mode in Taco Bell, one standard auton that maximizes cycle time in Chicken Tender, and an independent that is not the highest score but the best for ranking points and amplification in Wingstop.

A Quick Simulation
ezgif.com-video-to-apng-converter

Mechanical

West-Coast Chassis

2024 is our second season of implementing a custom West Coast tank drive. In 2023, we learned a lot about the strength and endurance of rivets and gussets (specifically their bending due to stress), and this year, we tried implementing something new using REV MaxTube and REV Endcaps. While MaxTube and Endcaps are commonly used by teams who use Swerve, we took this as a sign of success regarding their long-term usage at the highest level.

Our finalized Chassis Dimensions are 28’’x30’’ without bumpers! We chose this chassis size so that any mechanisms we could build would be modular and transferred to the KitofParts Chassis in case of failure during build season or competition.

Design Talk

To get all of our members to collaborate and feel comfortable sharing their ideas, we decided to split up individually and make members share ideas on a slideshow. This would then be presented to mentors and other members the following Saturday meeting. We also encouraged members to post their thoughts from Ri3D designs. This led us to some interesting conclusions in terms of this approach.

Pros

  • Gets Parents and Students involved in the game design process
  • Keeps Ideas fresh and open to all
  • Allows the visualization of possible ideas in drawing/CAD form
  • Allows for the simplification of designs/elimination for overcomplicated ideas.

Cons

  • Newer Members might be more nervous to share ideas in terms of criticism
  • Short time span to think of a idea
  • Heavily Ri3D-based designs (Good or bad, depending on how you look at it)

In terms of the actual design ideas that were proposed, the slideshow that our members made has been attached.

https://docs.google.com/presentation/d/1lCmRZu3VaVj2D0DOQYOtcWh05hW0RKfSQQk0YZxjS4I/edit?usp=sharing

Feel free to ask questions about designs!

Favorite Ri3D Designs

These are some of our favorite robot in 3-days designs that influenced our thought process heading into the season.

During the past two weeks, while our design was being tested, we also prototyped different shooter options, including flywheels and stealth wheels, side-by-side and top-down.

We started by discussing possible ways to intake the game piece.

We then attached some motors and tried this version of the ground intake:

From this, we identified the main shortcomings: we needed to increase the intake angle between the top and bottom wheels. We also determined that compliance wheels were grippy enough to intake the game piece and keep it inside the mechanism to shoot.

We also tried several shooter concepts and determined that a top-down shooter was much better than a side-by-side shooter due to more area being covered over a more significant duration and the increased compression that it provided.

Our Robot Design will be released this weekend; until then, here’s a little teaser.

Awards

This was something that we didn’t mention in our previous open alliance update but 6908 is making steady progress towards our first ever FIRST Impact Award Submission. Our planning for this award starting way back as far as November. We initially started by working on the short answer questions, drawing heavy inspiration in terms of format from the Robolancer’s content from 2023. We also used FRC 1903’s award formatting content. After the Impact Award Submission deadline, we will send out a comprehensive list of resources that we used and drew inspiration from.

By the start of the season, we had finished most of our Impact Award Responses in terms of the supporting documentation, long essay, and short essay questions. We focused these on three main aspects regarding Infuzed.

  1. Inspiration Initative

  2. Umbrella Name for all of InspireNC (Our Parent Non-Profit) and Infuzed’s outreach focused on STEAM education

  3. Diverse Outreach

  4. As part of the Inspiration Initative, Infuzed focuses on a wide variety of outreach opportunities including our past experience at Artists Alley (Covered in the last off season post) and upcoming events at the NC STEM Expo in April, promoting the values of FIRST

  5. Student-Led

  6. Infuzed prides itself on being a student-led team in both good and bad times. This allows members to be involved outside of just the robotics team and into our parent non-profit. Ultimately, we (the teens) make all the decisions from what competitions we are going to, to what our finalized shirt design will be. (Possible Release next week???)

A few takeaways from our work so far on the Impact Award.

  1. Good Way to let members read about team history

  2. We gained a lot of new members with fresh ideas but not a lot of background knowledge regarding the team this year. The Impact Award turned out to be a really useful way for these rookies to learn about our vision and impact in the community!

  3. Starting early is Key

Since the start of build season, we have had less time to work on background organizational activities and awards as well. Starting early (like wayyyyyyyyyyy early- we started planning in October) made the deadlines not seem nearly as threatening even though we are less then a month away.

  1. Treat it as a way to learn about team shortcomings

  2. We really learned a lot about ways Infuzed could improve in terms of our outreach and business activities this year. Given that this was our year working toward Impact with a fleshed out schedule, there was a lot of reflection in terms of goals for upcoming years and the types of opportunities we should target.

This week, we started working on the Impact Video and presentation.

General Stuff :large_blue_circle:

Starting from next week, we will be posting on a bi-weekly basis that lets us not only update more regularly but also lets our own team see progress.

Our goals for the next week are to:

  • Finish Custom Chassis
  • Set up note recognition using Limelight
  • Run a basic autonomous mode on PathPlanner
  • Order mid-build season parts list

Snack of the week:

  • Basically the food that runs out the fastest at our workspace
  • This will be logged throughout the season
Date Snack Time to Empty
Week 1 Costco Cookies (24 Count) 3 Hours
Week 2 Costco Hard Cookies (24 Count) 1.5 Hours

Also a quick timelapse to finish off the week!

IMG_15531-ezgif.com-video-to-apng-converter

3 Likes

2024 Design Reveal

Infuzed is proud to present our 2024 Version 1 Robot, Kronos. This will be the design we work towards for our week 1 district competition. We still do not have an integrated trap mechanism but a working speaker, amp, and climb mechanism.

Our arm will be controlled by 2 NEO V1.1 Motors, with a through-bore encoder on the non-motor side of the arm. This is built off our REV-MaxTube-based, custom chassis, and the chassis will also use omni-wheels to counter the moving force of the arm’s mass. Our arm features a constantly working intake and kicker mechanism, both powered by a one-bag motor. We only have one motor on the actual part of the robot that can extend outside the frame perimeter to decrease the chance of electronic failure. Lastly, our drivetrain will also be powered by 4 NEO V1.1 Motors and shooters with 2 NEO V1.1 Motors.


A few of the custom parts that we will CNC include the arm mount, hex shaft mount, and the metal of the intake and shooter.

There are a few other exciting things to note: we transitioned away from the idea of Colson wheel shooters after registering the wheel’s impact on the Game Piece from a few different teams. Instead, we switched to stealth wheels. We were also heavily influenced by the Quokkas design and Penn State from RI3D regarding how the robot mechanisms will work.

With this and the use of PathPlanner, our fastest cycle time would be around 8 seconds from the human player station to speaker and 11 seconds to the amp.

5 Likes
2024 Impact Video Reveal

:person_raising_hand:

1 Like

So……it’s been a few weeks. We will try to make a post regarding what we changed on our actual robot between the last open alliance post and our week 1 competition. But this is the recap of the actual event, which definitely exceeded our expectations.

Before this….presenting our week 1 robot

Friday Goals
Upon load-in, we had five primary goals for the day:

  1. Making a suitable and neat pit setup
  2. Passing Robot Inspection
  3. Testing autons at the practice field
  4. Testing limelight functions
  5. Attaching a Climb Mechanism (Hooks Basically)

What actually happened?

  1. This was very successful for us; we finished setting up the pit by 7:30 and got 3 hours to work on the robot. This seems unusual given that pits are typically supposed to close at 10 PM but due to delays in setting up robot inspection stations and the practice field, every team given 30 minutes extra.

  2. We got through most of the inspection process, with the only things that we needed to fix being our arm being slightly out of frame perimeter (around ÂĽ extra) and fixing permanent bumper mountings

  3. We also needed to fix our bumpers because our iron on numbers started peeling off due to encountering rain when loading in

  4. We were unable to finish the inspection process however

  5. The practice field was not set up until Saturday morning so this meant we would just have to go with our mobility autonomous for Saturday’s qualification matches

  6. See above regarding the practice field

  7. We decided to hold off on actually attaching the mechanism despite cutting it at the machine shop because the robot would have to be reinspected after.

Qualification Matches

In our first qualification match, we encountered issues with wiring and connecting to FMS. This was a new issue to us as while we had to rush through wiring our robot due to some final arm adjustments, this had never been an issue before, even when we had tested at FRC 6004’s practice field. We realized the issue was because of a loose wire that connected the RoboRio to the robot radio and fixed this. The rest of the quals on Saturday went pretty much as we expected from a performance point of view. We finished the day in 18th with a record of 4-4-0 and being a pretty consistent amp cycler.

Sunday’s qualification matches were also similar with us winning 2 games and losing two as well. We rounded off qualification matches in 18th.

Mechanical Issues in Qualification Matches

Shooter/Intake Robustness

  • This was an issue that we expected but to the extent that it happened.
  • Our over-the–bumper intake would consistently be hit whether it be by other robots or the stage or parts of the field.
  • Our most frequent fixes in pit were often fixing the bent shooter/intake metal and just switching out bumpers
  • By the end of qualification matches on Sunday, our intake was so bent that the bearing holding the hex shaft rollers fell out and was essentially taped on

Modular Arm

  • One of our biggest design ideas for this year was to make our arm modular so that it could be switched between chassis if needed. However, making the arm modular did prove to have some interesting flaws through competition.
  • Pros:
    • The arm often just needed little fixes, we wouldn’t need to take the arm off the chassis to fix anything.
    • Quickly disassemblable: we discovered an issue with the Neo mount at the base of our arm and were completely able to take the arm off the chassis and fix this within the space of 1 hour.
  • Cons:
    • We faced issues with the actual mounting of the maxtube arm base onto the KoP chassis
    • We discovered that part of the MaxTube had been sheared off by the end of quals because of an unknown reason
    • (most likely because of the impact the arm had faced throughout the day)

Bumpers

  • Our bumpers took a hard hit during qualification matches, with half the numbers peeling off
  • We fixed this by asking Pit Admin for bumper number tape (FYI: totally recommend this, it is very useful and works pretty well)

Alliance Selections

Our team was fairly certain that we would not get picked for an alliance just because we had issues with our speaker shooting, and our arm had faced chain tensioning issues for all of Sunday.

However, we were the second pick of Alliance 2 which was led by captains 4829, the Titanium Tigers, and 900, the Zebracorns. Both of their robots were AMAZING and their respective robot reveal and build threads are linked below.

We finished the elimination bracket as finalists, losing 0-2-0 to the first-ranked alliance of alliance captains 7763, first pick 4795, and third pick 8757.

Strategy

The biggest strategy hack that we identified from this weekend was….Amp is really important. At the end of the day, we realized that this and driver practice were crucial to success, especially at early week 1/week 2 events. Amp specifically is a unique subset because we discovered around 8/10 robots we found could score speaker at our competition. We were one of the few robots that were more consistent with Amp scoring. This gave us an advantage as by the end of eliminations, our alliance’s plan was for us to score 2 amp cycles, then go play defense in front of the speaker. 900 and 4829 would alternate for the rest of the match. Through this, it was possible for each team to have a clean cycle path, especially with the source zone and also be able to keep scoring high while also providing sufficient defense.
During our initial strategy planning, we anticipated that our alliance would score around 64 points every game and this was what we achieved at the end of finals with our alliance reaching 63 points. This showed the strategy to be worthwhile.

On the topic of driver practice, we noticed this on the rewatch of our games. Both of our drivers are new this year and this severely limited our cycling especially at the start of qualifications even with a fully functioning robot. However, by the end of competition, we realized that our cycle time had improved not because of our robot performing better (it was slower if anything) but rather because the drivers had better chemistry.

Robot Redesign

Our main job within the alliance was to score amp nots but also to play defense. By the end of finals 2, we discovered that we had basically damaged our whole intake and shooter mechanism to the point where it could not work. We also changed our design intentions for week 4, beyond just adding a climbing mechanism to switching to an under-the-bumper intake system to prevent further arm damage.

Also a special mention to our alliance in 4829 Titanium Tigers and 900 Zebracorns!

3 Likes