3588 the Talon - 2023 Build Thread


Happy Kickoff! Our team has been working hard over the weekend coming up with ideas of how our team can tackle this year’s challenge. Right now, we are developing prototypes of the ideas we came up with, but here’s a brief overview of how we got here:

Game Animation

Right after watching the game animation, we looked at the rulebook and answered the following questions:

  • How can our robot move?
  • How can we interact with game pieces?
  • How can we interact with the arena?
  • How can we interact with other robots?

And using those questions, we went into making a priority list of what we wanted OUR robot to do.

Mechanism Brainstorming

Once we have our priority list, we start thinking of HOW to do those actions. We took our priority list and figured out what we would need to have in order to do what we want it to do (ex: Claw, lift, arm). Some of the ideas we tested out by grabbing some scrap pieces and using people to act as the “mechanism”, which we used to eliminate or further understand some of the mechanism concepts we came up with. The biggest things we learned from this were:

  • One axis arms were more complex than we originally thought
  • A flat claw makes it hard to pick up cones
  • Center of Gravity is very important and heavily impacted by any lifting mechanism


Now we have reached our prototyping phase, where we took the ideas from our brainstorming and made them more accurate. We have started prototyping four different types of claws (Flat, curved, roller, and passive/reverse piston). We have yet to test any lifts or arms.

1 Like

Week 1

So far, our team has successfully prototyped several claw designs, held both an open and team-only PDR, finalized our overall robot concept, finished the master sketch, and began assembling the full robot 3D model.


For prototyping, we settled on replicating four “unique” claw designs, and one extra claw design similar to one we were already working on.

Roller Claw: Similar to 2018, our roller claw uses wheels to pull both cubes and cones in and “hug” them by pulling the arms together passively. After testing, we realized this design was extremely heavy, did not work very well when picking up cones, and was more complex than our other designs.

Round Claw: The concept of our round claw was to create a curved grip with arms/pinchers that rotate around an axis to better grip cones, but also pick up cubes. Testing revealed that this design would take some trial and error to figure out the best curve or curve+flat combo to pick up both game pieces, but it could be made light and with few materials.

Flat Claw: Our flat claw’s concept was to use a flat gripping surface with two arms, with one arm fixed and the other arm free to slide, to pick up both cones and cubes while being actuated with a piston. We were unable to successfully prototype with truly “flat” claws, and we had to add lumps to the claw to grip the cone. Further testing showed the claw was no more effective than the Round Claw and was more vulnerable to damage.

Reverse Piston w/ Rotating Grips: Based on a design from a Ri3D, our reverse piston design uses arms with wheels or hubs on a freely rotating axis to grab a cone or cube and orient cubes upright when grabbed+lifted. Our testing proved this design was very effective, however, it would require more weight than the Curved design while achieving the same goal (pick up from shelf, dropped cones aren’t a priority)

Scissor Claw: Essentially a different version of our Flat Claw, the Scissor Claw would rotate two flat arms around an axis like scissors to grab both cones and cubes. After adding pool noodles and grippy tread to the arms, the arms were able to pick up both game pieces, however the grip was not all that strong.


Although our open PDR may not have had as many attendees as last year, we received quite a lot of good input. After presenting our overall game strategies and robot concepts, we received the following from our audience:

  • Using pistons for all of our designs would be more efficient and weigh less
  • Motors are more reliable than pistons when it comes to claws
  • Use bungines with motors to reduce stress
  • Keep efficiency and cycle time in mind for overall strategy and replacements

While this is not all we received, these were the most relevant pieces of criticism and advice we received.

Team Only PDR

During our team only PDR, we went into more detail on the criticisms and advice we received during our open PDR. We then used that feedback to decide on our overall strategy and robot concept. In terms of strategy, we thought through the most efficient way to earn points and the best way to avoid being defended against, as well as the best way to defend, which landed us on two drivetrain concepts:

  1. Mecanum Drive: Pros are that it can move side to side, which would help us align. Cons are that we are easy to defend against, and won’t have much grip on the charging station.
  2. Tank/Drop Center: Pros are that it is not easily moved, and has more grip and “tilt” for getting onto the charge station. Cons are that it isn’t as maneuverable and could make our robot too big to fit three robots on the charging station.

Considering all of these pros and cons, we ended up settling on Tank/Drop Center because it provided the ideal balance of speed to defense that we were looking for.

We also went over our lift mechanisms, which after PDR were:

  • Elevator+Telescoping Arm: This combo makes scoring fast and adjustable for the driver, but is also heavier and more complex than-
  • Rotating Arm: Which essentially uses a single arm with an axis above the robot that allows the arm to rotate back and forth over the robot to grab game pieces. While this would allow us to grab from the ground and would make our lift mechanism more simple, it would also create a large torque issue on that single axis that we would have to deal with.

With that being said, we ended up going with the Elevator+Telescoping Arm. The team decided that the elevator and arm would cover a wider range of possible points we would need to reach, as well as be quicker overall (plus it looked kinda cool).

Finally, our team discussed which claw mechanism would fit us best, and after some tips from our mentors we discovered that:

  • Scissor arm and Flat claw are the same, just rotating on a different axis
  • Rotating vs. Sliding doesn’t matter because as the claw gets closer to grabbing the game pieces they are moving in the same direction, the only thing that would affect is spacing and implementation.
  • Pistons would allow us to put less weight onto the telescoping arm
  • A rotating grip wouldn’t benefit us because we plan to grab from the shelf, where all of the pieces are already oriented correctly.

Taking that into consideration, we decided that the best design for us would be our Curved Claw design with a Piston to actuate the motion. This would allow for quick pickup of both game pieces as well as easy replaceability if the claws were to ever break.

Thank you all for reading over our post, and unfortunately, the post was a bit delayed. Nevertheless, we’re heading into our 3rd week of the build season with a plan of action. We’ll make sure to keep this thread updated with significant developments in the coming weeks. The week two recap will be posted early next week, so be on the lookout!


Week 2 of the Build Season

This week, our team focused on assembling the Kit of Parts (KOP) to have a working robot for our drive team applicants to drive in the weeks leading up to their driver test. For some, this is their first-ever driver test, so we also plan on finishing bumpers as quickly as possible so that we don’t do too much damage.

First things first when you’re building the robot chassis is you must have a CAD. Luckily for us, with a pre-CAD for Kit of Parts, most of the back-breaking work was done — except that we now had to integrate an elevator pre-CAD and telescoping tubes into our design.

Our CAD team being the total chads they are, were able to integrate all the various pre-CADs, created superstructures, drafted the electrical board and electrical components, and even started a CLAW prototype CAD. And so, by Friday, we fully assembled our robot’s KOP chassis.

Now that’s what I call progress!

Programming also made some significant progress during week 2. Namely, upon receiving our new programming laptops, the programmers completed the code for the chassis to drive — granted, the laptops were preloaded with Windows 11 ); — and calibrated our SPARKMAX motor controllers. It was an exciting rush of adrenaline and euphoria when the robot started driving Saturday morning. Of course, though, the robot rammed straight into a table, but I still see a driving robot as an absolute win.

Most of this week has been spent on working on CAD, but with the progress we’ve made with a drivable robot, we expect to get in a lot of driver practice and a lot of fabrication done in the following week.

Feel free to check out our Onshape CAD and our Github with comments, questions, and critiques:

  1. Onshape
  2. Lindbergh Robotics - Team 3588 · GitHub
1 Like

I’m pretty concerned about the split upper crossbar as you have it designed.

This is a pretty critical structural piece. Splitting the middle opens you up to two problems:

  1. The crossbar is carrying the load of lifting the carriage, via the cascade rope (orange arrows). When you lift the elevator, the rope pulls vertically on the clamp plates. With a split in the middle that vertical force is reacted as a torque at the blue standoffs, which are very poorly positioned to resist that torque. I’d be extremely worried about those just bending, especially if it’s the thin wall MAXtube.

  2. The crossbar is the structure that keeps the top elevator bearings pressed up against the middle stage tubes and prevents them from spreading apart (blue arrows). With the split crossbar, the only thing resisting this is where the vertical and diagonal static tubes connect to the bottom, which is probably not strong/stiff enough to keep the top together.

I understand the need for the gap in the crossbar to let your telescoping extension pass through. You might be able to add some additional bracing or gussets to help keep it stiff. I’m not sure if it’ll be enough, but I’m pretty sure if you leave it as is you’re going to have a bad time.


Thanks for the advice! A lot of these changes would be perfect for structural support, but the main issue is that it’s hard to connect since it is tilted. Also, would the top support put more pressure on the elevator support?

  • Logan (Team 3588 CAD Lead)

Week 3 of the Build Season

Week 3 of our build season saw some finalized changes with our team’s CAD, progress with elevator, autonomous, and PID code from programming, and a basic layout of our team’s electrical board. Most prominently, CAD experienced Dante’s Nine Circles of Hell but, in the end, pulled through in the end. That is, most of the week was CAD dealing with connectivity issues between telescoping tubes and the clamp as well as the elevator with supports, resulting in a slightly off-centered elevator with various sizing issues. Although hectic, part of our CAD team ventured into exploring claw prototype designs; here’s an example of a design we came up with: Current Claw Design

Additionally, with our team’s CDR on Saturday, we identified risks in our current design choice that would prevent us from achieving the goals we established during kickoff:

At the start of the CDR, we first evaluated our robot’s design in comparison to the following questions:

  1. Will our robot conform to all the robot rules?
  2. What prevents our robot from being reliable?
  3. Will we be able to dock on the charging station?
  4. Will we be able to score on all three levels?
  5. What roles can our robot play? In other words, is our robot flexible enough to play offense or defense when need be?
  6. What are some challenges we may face in the future with regards to maneuverability around the game field?
  7. Is there anything left we can improve upon to lower cycle times?
  8. How can we make our electrical components more accessible?
  9. Are motors still a less preferable choice compared to pistons as the actuation device for claw?
  10. Last year, a lot of the robot’s mechanisms broke down during competition and it proved difficult to get the robot back up and running again. With this in mind, what can we do to make our robot more reliable on the field?

After about an hour of deliberation, we identified the following risks (some are solved while others aren’t; bolded text = currently unsolved or is solved but may go wrong):

  1. When elevator is fully extended, our robot will be outside the frame perimeter
  2. The telescoping tube is too long in the back
  3. The Electrical board does not have the holes on the CAD yet
    4. Claw: 1) Every claw design thus far has been outside of extension limit, 2) We still don’t have a finalized claw design
  4. With our current design, it’s hard to secure the telescoping tube
  5. The current brackets to support the elevator aren’t very secure
    7. The telescoping arm, upon extension, can possibly break
  6. Our elevator can twist when turning
  7. Cutting angled tubing proves difficult for fabrication (specifically for the super structure)
  8. Tubing for our claw’s piston would be sketchy
  9. The gearbox of the telescoping arm may possibly crash into the electrical board and battery
    12. Our robot currently has weird elevator plates with the platform

Similarly related, most of our CDR was spent working with our robot’s CAD before we started cutting metal to ultimately start building the rest of the robot and its mechanisms. In particular, there were issues with twisting from the elevator, but we put a cross bar to prevent said issues. CAD also started working on drawings to give to fabrication, and began drafting possible claw designs with our mentors. We’re currently settling on a curved claw design. After evaluating the curved claw with mentors and students, we found out that while great for grabbing cubes, our claw design falls short when it comes to cones.

What’s more, because we’re using pistons for our claw, there might be some possible issues with popping. Our current curved claw design features an overlapping design that is more effective at grabbing cones, but when picking up cubes, there’s 6 inches extra of length that can exert too much pressure on the cube, popping it. As mentioned in our possible risks earlier, we’ve also encountered problems with support. For one, we had issues directly connecting the telescoping tube to a clamp, had weird sizing issues for our elevator, and the elevator couldn’t couldn’t connect cleanly with the supports, leading to the elevator being off-centered.

We’ve also encountered a recent issue with our robot driving… The other day, we tested the endurance of our motors, but upon actually driving the robot on the floor, our robot would lose communications when we push the joystick on our controller all the way when the voltage drops below 10 volts. Today, we tried switching out different radios, PoE injectors, batteries, and other ways to control the power output of the robot. To no avail, nothing worked. If you have any ideas on how we can proceed, feel free to reply to this thread!

Also, check out our new kickoff video our Outreach team has been working on for the past week in a half here: https://www.youtube.com/watch?v=MeEeVC_6gY0. Make sure to like, subscribe, and turn on the bell notifications! While you’re at it, feel free to also donate to our Patreon (there’s no Patreon)!

That’s all for week 3! Stay tuned next week for week 4, and also feel free to leave any advice, tips, or resources in our weekly updates!

1 Like

Week 4 of the Build Season!

With CAD finishing the main CAD for this year’s bot, most of week 4’s focus for the robot was on fabrication, electrical, and programming. In terms of electrical progress, our team has been working extensively on figuring out how to best integrate REV components into the current electrical board/schematics. Electrical has also been planning out the placement of the electrical board on our robot and the placement of the electrical components while helping programming with troubleshooting elevator code. Here’s a picture of our current board setup below:

Seeing as this is our first time switching over to using REV components, we’d appreciate any general tips or any resources that may help us during our competition season! Electrical also plans on mounting pneumatics all around the robot for ease of access. As learned from last year’s competition, accessibility to the robot’s electrical board, especially with regard to pneumatic systems, is vital.

Programming has also been working on developing elevator and autonomous code. Unfortunately, we’re still encountering issues with driver code, so our team is currently looking more into using REV components as a compromise in the meantime. With the majority of the week being spent on autonomous code, programming is currently trying to work on our robot’s auto alignment code for Kit of Parts. While elevator code is going quite well, our programming team is having some trouble with auto alignment code. Seeing as this is our first year working with Kit of Parts and taking time to work considerably with autonomous code since Infinite Recharge, any tips and resources for auto alignment, especially with Kit of Parts, would help out a lot!

A lot of progress has been made by fabrication this week! In particular, during our Saturday meeting, we finished assembling our 3 stage telescoping arm and even simulated weight at one end of the arm upon extension. Here’s a recording of just that:


Fabrication during week 4, what’s more, made supporting tubing for our robot’s chassis elevator, and made the plate for our telescoping tubing. We’re currently missing our gearbox for our telescoping arm, but we’ve completed as much as we can with the parts we have nonetheless. That being the case, we’re currently waiting on elevator parts and REV ion tubing before moving forward with fabrication. In the meantime, fabrication is working more on assembling field elements while we wait on our REV ion tubing and additional elevator parts.

There’s also been developments with our claw prototype. After going through 7 iterations of claw designs, we’ve now settled on the claw design mentioned in the previous week’s post.

Compared to last year, our team has been on schedule with deadlines. As a project manager, I’ve been switching our team over to Notion for deadlines. Is this the right approach? Unfortunately, we don’t have a lot to work with in terms of in-person workflow visualization tools like Kanban, so what would be a more efficient way of communicating deadlines? The Notion is currently set up for project managers to be organized, but is there an effective way to set up a Notion for subteam leads to check daily? Does anyone use Notion for their project management? Any suggestions would be helpful!

That’s all for week 4, and our team is ready to head into week 5 head on! We’re currently waiting a little bit on some parts to come in for our elevator, but afterwards, we’ll be set to make even more progress on this year’s bot! Stay tuned early next week for our week 5 post, and as always, feel free to leave comments, resources, and suggestions on these posts! See you then.

1 Like

Week 5 of the Build Season

Although week 5 wasn’t as hectic as the previous weeks, we did make some more progress with our robot this week. Because Fabrication was waiting on gearboxes to arrive, a neo converter (that we had to 3D print due to time restraints), rope for our telescoping arm, and a plate for the gearboxes, most of the week was spent, well, fabricating without said parts. Even so, fabrication did manage to complete the telescoping tubing while waiting for these parts. Fabrication and CAD also worked together on creating field elements this week.

With an overall plan of where to place the electrical board and where to mount electrical components with the help of CAD, Electrical has been working extensively on integrating REV components with the current electrical board. At the end of the week, working with the REV components was a success. Our team now has a basic electrical board. CAD mainly spent the week refining the structural support of the bot, making drawings for fabrication while adding carriage support (connecting on the top) and the crossbar with gussets and tubing.

A common pattern seen this week was that our progress came to a slight halt while waiting on certain parts to ship. This wasn’t a pattern only for fabrication, but also for programming. While waiting for gyroscopes to arrive, programming had to wait around a week before testing their autonomous code. Because of this, programming learned too late that their autonomous code wasn’t working properly. Especially because programming was working on elevator and arm code at the same time, the autonomous code going wrong subsequently delayed programming finishing their elevator and arm code. With help from one of our mentors, however, programming seemed to be getting back on track.

Outreach also posted 2 new posts tracking our progress throughout the weeks. Make sure to give them a like on Instagram! Our Outreach team also submitted awards for this year! Namely, we nominated one of our advisors, Mr. Lowrey, for the Woodie Flowers award and our Shop Master and Project Manager, Reuel Fernandez, and our Fabrication lead, Jasmine Aninion, for Dean’s List! We’re so proud of them and nominating them for awards this year was well deserved! All of them did so much to actively promote FIRST and Stem in our high school and the PNW community.

We’re now approaching the final official week of our build season! Overall, I’d say our team has improved a lot from last year, especially after the pandemic. With that being said, stay tuned for our final Chief Delphi post for week 6!

Week 6 of the Build Season

This is it! It’s week 6 of our build season. And seeing as it’s our final official week of the build season, we finished strong. Although, our team will meet the week following mid-winter break for additional testing of our robot before drive practice and our field test for our potential drive team.

With a basic electrical board completed, electrical’s main goal for the week was finishing the placement of electrical components and mounting the polycarb to our bot. And so, electrical has been working on getting the board set up this week. More specifically, electrical has also been working on setting up some of the new batteries this year. In terms of highlights this week for electrical, there were no major struggles as compared to the previous weeks other than having to wait for fabrication to get the ball rolling with assembly. Electrical also successfully figured out the communication issue, and is now waiting on fabrication to assemble the final parts of the robot so they can begin wiring.

Around the middle of the week, fabrication finally received their gearbox parts, telescoping arm rope, and gearbox-specific plate to begin fabricating the rest of the robot. At the start of the week, basically everything was already fabricated and ready to go, so fabrication has been working heavily on assembly. Although we initially planned to have an elevator with the gearbox assembled by Thursday and Friday of week 6, fabrication experienced some minor delays due to one of our parts shipping being delayed. Even so, fabrication has been hard at work on assembling the elevator and putting everything all together so programming can test and electrical can begin wiring the robot. After that point, our robot will be entirely assembled and we can start planning for field testing for our drive team and scheduling opportunities for drive practice. We originally planned on heading over to Tahoma’s practice field for drive practice, but due to programming needing more time to test because of the delay of assembly, we had to skip out. Although this being the case, our team still plans on heading over to Blue Origin for drive practice!

Speaking of programming, programming has been hard at work again with autonomous, elevator, and arm code. Getting into specifics, programming encountered issues with april tags and testing elevator code. Namely, programming has been spending the majority of the week dealing with making progress in one of their alignment methods and getting the robot to properly, accurately, and consistently align with the april tags. What’s more, programming has been working on testing their elevator code and setting up PID for the elevator with regards to taking in weight and the robot’s center of gravity. Programming is now waiting on a fully assembled bot along with electrical so both subteams can work together on testing code and the electrical components.

CAD mainly spent the week refining the structural support of the bot, making drawings for fabrication while adding carriage support (connecting on the top) and the crossbar with gussets and tubing.

This week, Outreach has mainly been working on planning for this year’s robot reveal video. We haven’t done a robot reveal in years, so we’re excited about releasing one this year! A script has been made, and let’s just say there’s much to look forward to! With the season coming to a close, our Outreach team has also been working on photoshoots for our students and mentors.

One thing our team has been keeping a secret for a while now is our new merch for this year… Thanks to our Outreach member, Jada Rivera, our team now has redesigns for our hoodies, t-shirts, and mentor polos this year, which can be seen below:

Gotta say these new merch designs are pretty snazzy. I’m especially proud that our mentors will get in on the action with these clean black polos. During our testing week after mid-winter break, our Outreach team will begin shooting footage for our robot reveal video as well as a build season recap interview where PMs, leads, and members will reflect on the season this year and what they look forward to gaining from competition. After our build season, Outreach plans on updating our website with the new team roster and planning out Outreach events in the PNW community as fostering a sense of community is at the heart of our team’s mission.

Weeks 7 + Week 8

While weeks 1 - 6 highlighted our team’s progress as we built our bot, weeks 7 and 8 highlighted our team’s progress with finalizing drivers, getting more driver practice in, and otherwise spending more time testing our robot and prepping for week 3 of competition.

As per usual, all of our subteams were hard at work; however, the formatting of this Chief Delphi post will focus more on programming and electrical efforts toward troubleshooting and configuring the bot while getting some driver practice in.

To start off with a general summary of what CAD, Fabrication, and Outreach got done, CAD focused their time on helping fabrication, practicing CADs, and spending more time training and passing down CAD knowledge to this year’s rookies who will return next season as a returning CAD member or even as a potential CAD lead! Lots of great potential for next year’s leadership team! Fabrication, after finalizing assembling the elevator, have been split off into two main teams: 1) A team assisting in any potential fabrication issues that programming and electrical picks up on while testing and troubleshooting and 2) A team working on bumpers and spare parts. In light of recent testing, however, fabrication has also been hard at work on making blocks to help support the tubing of the robot’s elevator, which will require them to make and mount RLS-brackets and blocks on the arm of the elevator.

Outreach, meanwhile, has been working extensively on prepping for competition by making all of our shirts, mentor polos, and hoodies for competition season. While we won’t be able to rock our hoodies in the first week, our team will be wearing our newly-designed t-shirts as seen in last week’s post in our week 3 competition. In addition to the shirt and hoodie merchandise being almost done, Outreach has also been working on filming and editing this year’s bot reveal video as well as working with branding for our post-competition season projects as well as next year’s competition season. Specifically, Outreach has recently been working on different graphics for potential posts during our week 3 competition in Bonney Lake and our week 5 competition in Auburn.

Now, I will be detailing what programming, electrical, and our project managers have been working with regards to competition preparation as well as finalizing our drive team and troubleshooting our robot. First, our team has been struggling a lot with getting drive practice in. Particularly, even though our project management team practically swore to dedicate 3 weeks to straight driver practice and testing, every little setback has made us resort to cutting into this 3 week period. Primarily with getting in driver practice in, we’ve been struggling with getting access to a practice field due to struggles with scheduling rides. Short term gain for long term loss. Granted, going with a Kit of Parts robot chassis this year and a Thrifty Elevator Stage Kit helped a lot in accelerating our progress with regards to being on and sometimes ahead of schedule. Even so, from a project management standpoint, we’ve still been struggling with efficiently and effectively dealing with setbacks that have prevented us from moving further along with our robot. For example, figuring out that fabrication has to spend time with the robot ultimately sets back programming’s and electrical’s time to test with the robot. Although obvious, I feel like part of the reason why we struggle with bouncing back from setbacks has to do with our lack of discussion and planning as to what got done on a particular day and what needs to be accounted for. Shipping and tracking of items we order online, especially for fabrication, has been the subject of many of our setbacks in the past, including last year.

Do any mentors or project managers know how to deal with this effectively? I’ve found that Notion helps a lot not only with tracking the overall timeline of the robot, but to also address action items and potential setbacks that may cost us a few days or a week in build time.

Anyhow… as discussed in the previous post, electrical spent the beginning of week 7 finishing wiring the entire electrical board, particularly with electronics. And… surprise, surprise! With some testing driving our robot, we discovered the cause of our robot’s communication issues. One of our fabrication members (not gonna name who, lol) drilled over the electrical board without covering it, resulting in a bunch of metal shavings in the roboRIO of our robot and the short circuiting that resulted in the communication with our roboRIO suddenly turning off while driving. Well, at least we can say we solved the issue…

Electrical has also been working on wiring pneumatics for programming to test the robot’s arm. In light of testing alongside programming, Electrical has noticed a recurring problem with our robot’s motors. Namely, our neo motors have a tendency to smoke, possibly due to the strain of programming’s PID code. Although, we’re not exactly sure on what is causing this year’s neos to smoke under relatively normal strain as well as what had caused last year’s neos to smoke during competition. If you have any insights, please let us know.

Partners in crime, Programming has also been working commodiously with Electrical on troubleshooting and testing the robot. Generally, programming has noticed errors in the electrical board and CAN Spark Max tuning along with electrical and fabrication errors while testing, further delaying programming’s period to test. Also, programming has been struggling with setting up autonomous for this year’s game, possibly resorting to scrapping it entirely in favor of doing a timed autonomous mode instead of creating various autonomous modes for docking/engaging with their alliance community’s charge station. However, it’s a decision that programming is still looking into. Struggle with getting access to a practice field due to struggles with scheduling rides.

Before ending this post, I’d like to announce a special surprise for our Chief Delphi readers… No, our robot reveal is not done yet, but it will be soon (and there’s much to look forward to!) Granted, the intimacy of these posts indicate that y’all might already have a good impression of our robot… In either case, seeing a robot doing some action is part of the fun, right!?

Anyways… we held a special ceremony on the 10th of March for our bot… Solemnly swearing and pledging their “claw” to the Talon’s liege, to defend and obey us until we depart our demesnes (our shops) or death (running out of food), our robot promises to uphold the honor of knighthood… And so, we dubbed our robot “Orion!” Why Orion, you may ask? Well, we held a bracket tournament to ultimately decide on the name for this year’s robot and ran into a stalemate, so one of our project managers, Reuel Fernandez, utilized the intellectual prowess of ChatGPT to generate a name for this year’s bot. And, you know what, Orion fits! Our running contender was Jörmungandr, but our team was split on naming our bot after something that would probably be difficult to pronounce and spell.

With that being said, that’s all for weeks 7 and 8 of our build season. In our next posts, I will highlight our team’s scouting strategies and experiences during our first competition at Bonney Lake!

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