To say the road traveled in this class was a difficult one would be an understatement. Between mismatched schedules, components and modules not working as intended, and nearly missed deadlines, it was beginning to seem that our project was the embodiment of Murphy’s Law, “Anything that can go wrong, will go wrong.” However, it was not all doom and gloom in the end. Through hard work and perseverance, we were able to step up to every challenge put in our way and produce a machine that was simple, effective, and most importantly, able to perform how it was designed to function.
Even though I would have to say that this has been the most stressful and time intensive classes I have ever taken, the end result has made it more than worth it. The experience I gained in the ME shop has been more than invaluable. Though I would have to admit that I made my fair share of mistakes during manufacturing, I was able to learn from these mistakes and make a better product as time went on. Before this class I could say that I had basic knowledge about the mill and lathe. Now, I can confidently say I can use these machines along with other tools in the shop to produce very precise custom components, a skill I will take with me for the rest of my engineering career.
As my other group members have pointed out, time management and communication played a big part of how our machine came together and it’s pace. Unfortunately, our group quickly learned that our schedules didn’t exactly match, and unforeseen circumstances prevented our team from being able to make vital decisions and produce critical parts as a whole. During these critical times, with group members missing, exams looming, and deadlines coming closer with each passing second, a great deal of frustration set in. It came to the point where I was probably pushing myself too hard trying to get everything I could for this project.
But out of the need to get things done and my frustration, I did my best to enact minor design changes to streamline manufacturing and ensure a working product. Though some of these changes were considered temporary by the rest of my team at first, the ideas behind most of them were implemented, or even adopted outright with minor changes. Everyone in our group had great ideas, and the machine really is the culmination of all of our thoughts put together, but stubbornness in taking criticism and adopting each other’s ideas hampered the early design process. It wasn’t until we started putting components and modules together did we start to see what parts of the design were working and what was not meeting expectations. It was at this point that everyone was able to get on the same page and start working toward the same goal on our final product. If we had a bit better time management and group dynamic, our design would have been optimized to its greatest potential, but the end result was more than satisfactory.
We may have had many issues along the way in getting our machine done, and it may not finally come together until the final days before seeding and competition, but seeing our final design in action was more than a rewarding experience. After a couple minor design tweaks, we were able to create a machine that during seeding was able to push all but two ping pong balls and all the squash balls over the divider. And seeing that our machine was seeded 4th, I would say that our design met the expectations that were given to us. Just witnessing our design going up against others in competition and succeeding made me forget of all the hardship and be proud of the fact that I made this thing.
But I have to say, if I were taking this class again, I would really hope that a few things were changed about it. As a member of a FIRST Robotics team in high school, I was excited to hear that we were being given the opportunity to compete. Unfortunately, unlike in FIRST, we weren’t given any details on kit parts, control systems, or the rules until after we started our group designs. I personally feel that many designs would have been better thought out if we had been given all of this information from the get go. It was more than frustrating trying to think of a design when I didn’t even know if it was feasible or not. Also, especially during build time, it seemed like many of the later milestones were not finalized until last minute. MS7 particularly stuck in my mind, as we weren’t given details on when to sign up to show our parts until the day before. Seeing as this was during an exam week, and everyone in our group had at least two exams, it did not seem fair to give us such late notice. The beginning of the class was also a bit rough in terms of scheduling. Three homework assignments a week put its toll on me, as this class provided about half my total homework for all my classes.
Other than these criticisms, I would say that the class gave me valuable engineering experience. We can learn all we want in books, but this, practical engineering experience, is how engineers really learn. Being able to physically touch a part you just made, seeing how a module really moves, and seeing an overall design come to life is more rewarding than doing calculations all day. Our robotics mentor in high school used to always say, “design is an iterative process.” This class and this project showed me that this saying is very much true.