Team Status Report for 10/18/2025

The most significant risk that could jeopardize the success of the project is still the same, which is having the launching mechanism work. With the Design Report and all the physics calculations done, now we have to build the launching mechanism to see if the math follows following fall break. To mitigate the risk, we have purchased have a bike motor that significantly overshoots all of our finalized specifications to ensure we have room to make adjustments in case there were unexpected physical constraints. Furthermore, the Design Report has a section on Design Trade Studies, where there are other approaches to the launching mechanism discussed. If the spinning wheels do not work as intended no matter what we adjust, our contingency plan is to use a spring system that contains guaranteed energy.

No changes were made to the existing design of the system. We are also currently on schedule, so there are no updates to report. Following fall break, we will have our focus entirely on building the launching mechanism, figuring out CV, and working with our motor control board, so we are confident in our current progress.

Part A was written by Miles: Our project can affect many people outside of Pittsburgh and across the world, as throwing and catching a ball is one of the most universal pastimes. Furthermore, many sports (like soccer for example) are very popular in many countries and tennis balls are most commonly used to enhance training and hand-eye coordination. Anyone across the globe who regularly catches, whether for fun or training for a sport, can gain value from our product. Since our product automatically targets a person and shoots the tennis ball when ready, this launcher is feasible to use for those who are familiar or not used to technology. As a result, anyone who wants to catch a ball on their own can have a need for this product, regardless of where they are from.

Part B was written by Andrew: Our project could affect the culture surrounding sports and how people practice them. Typically, practice always involves multiple people and even some personnel used, like coaches or teammates, for menial actions such as throwing a ball, but our project could potentially change this norm. Entire franchises and organizations could potentially switch their traditional practice methods to using our product, allowing coaches to be put in more critical roles such as analyzing player performance. Additionally, our launcher allows all athletes on a team to receive proper training instead of being stuck on passing duty or having inconsistent balls thrown at them. This could also majorly change the traditions of a variety of groups, like sports teams or even recreational leagues, who may not have enough players.

Part C was written by John: From our perspective, our project does not have an appreciable environmental impact. The original problem itself had little to no effect on any environment or surrounding ecosystems, and our solution will also have no additional environmental consequences. As a result, we do not anticipate any positive or negative environmental effects from our project. Perhaps there is an off chance that by having the machine take up the duties of a ball thrower, like a quarterback, more people could practice sports outdoors anytime without needing to coordinate with a large group. To elaborate, normally if a dedicated ball thrower is not available, practice as a group would be difficult, but our product removes this barrier. This would mean greater physical activity instead of having people remaining indoors using electricity. However, since the launcher itself requires power, the overall environmental difference is small.

 

John’s Status Report for 10/18

This week, I worked on the Design Report and got started on the CV and depth AI code.  For our design report, I did the introduction, use case requirements, and the Test, Verification, and Validation section. I also worked on parts of the design trade studies centered around our use of CV and the OakD pro camera.  This took a long time; however, over break, I was able to get started on the code for our CV.

Since I didn’t have the Camera with me, I could not actually test any code that I wrote; however, I was able to figure out how DepthAI worked, specifically that DepthAI is run by the camera and simply will output the information it finds to our microcontroller. I found it is possible to get coordinates from depth AI running their general-purpose (mobilenet-ssd) model and using it for person detection, and sending coordinates and depth information. Because of this, I made a first attempt and wrote out our depthAI code that finds coordinates, horizontal displacement, depth, and height, which is to be run on the OakDPro Camera; however, I also wrote simple, incomplete CV code to use on our Pi just in case.  Both of these are simply a start and are unfinished and untested.

Our main goal last week was to complete all the deliverables needed for the report, which we were able to do. The goal for this upcoming week will be to get all of our parts ordered and to start our 3d print so that we can begin assembling and testing our ability to launch as soon as possible. We are a little behind progress with our physical build; however, I am currently still on schedule with the CV portion of the project

Miles’ Status Report for 10/18

In the week of 10/4-10/11, we were mostly working on the Design Report as a team. Personally, I mostly worked on the system implementation section, as well as some of the smaller ending sections like the scheduling and summary. This took the majority of the week, as we tried to be as detailed and thorough as possible in our report.

Our main goal last week was to complete all the deliverables needed for the report, which we did complete. Our goal for this upcoming week will be to get all of our parts ordered now that we have our BOM and start our 3d print so we can begin assembling and testing our project as soon as possible.

Andrew’s Status Report for 10/18/2025

This week, I primarily worked on the Design Report. Since I am in charge of all of the physics and hand calculations, I put most of my focus on the Design Requirements and Design Trade Studies. The Design Requirements was fairly straightforward in terms of outlining the formulas and calculations I did for the exit speed, RPM, kinetic energy, torque, and power. I also described how the weight of the launcher will be supported, the necessary depth perception and processing speed of our camera, the necessary electronic components of a microcontroller to process CV and perform my projectile motion calculations, and the need for a big motor like a bike motor. The Design Trade Studies on the other hand was more challenging than expected, which is where I spent most of my time. Since this section called for explaining the other approaches our team thought of implementing but abandoned, I walked through all the logic and reasoning behind the physics calculations and how to balance between all considered fields to ensure the DC motors controlling the spinning wheels are not overstressed in one area over the other. I talked about our final decisions for specific wheel size, exit speed, energy, RPM, torque, power, microcontroller, camera/CV, launching mechanism, and DC motors. I also helped John and Miles write and proofread the other sections of the Design Report. The design report is under the “Design Review” menu of the website.

My progress is on schedule. Since all of the design requirements and the design trade studies are now clear, my main focus is to assist John and Miles with working on the CV and motor control to physically see if my math is correct.

Following fall break, I hope to start building the launching mechanism. I want to first attach the wheels to the DC motors and have them spinning to ensure it is stabilized and see if it can actually shoot a tennis ball around 20+ feet. Once that is completed, I will help work on the CV with Miles and John to start tracking a target and controlling the motor control board that helps rotate the base and spins the wheels.

John’s Status Report for 10/04/2025

This week, I prepared and gave the design presentation. I also reviewed our design to make some changes before the presentation. Specifically, I planned out the removal of the tilting function after determining that the design we had in place wouldn’t function, exploring other designs, and determining that there was no solution where we either got a series of motors that would push our budget, or compromise the predictability of the flight of the ball post launch. Since tilting was not necessary and would strain our budget, we decided to remove it.  For the design Report, I started finalizing the solution approach and have added and expanded upon the tests and testing metrics.

I have not made much progress with the CV, other than deciding to use a HOG(Histogram of Oriented Gradients) and SVM (Support Vector Machine) in order to identify a person, and using depthAI (the depth perception library that pairs with the OAKD camera) for our depth perception. I have a few decisions to make about my code. The algorithm I plan on using normally suggests a resize for faster processing; however, I am hesitant to do so, as I am unaware of how I’m meant to draw depth information out of the depthAI. My concern is being unable to locate where exactly a person is on a depth map, since the image being processed by my CV would not be the same. Because of this, I had to put a pause on my CV code until I figure out how the OpenCV and DepthAI libraries will interact.

Andrew’s Status Report for 10/04/2025

There were a few components accomplished this week on the project. For the first half of the week, John, Miles, and I spent time reviewing the design presentation slides. Due to the extensive amount of content to be presented, going over them together helped John prepare exactly what to say on Wednesday given the time limit. For the second half of the week, I started working on the Design Report. I have been working on the Introduction, Use Case Requirements, some Architecture, and mostly Design Requirements. From the calculations I derived last week for the design presentation, these sections seemed the most feasible to work on first. Since I am in charge of deriving the physics of the system, I have started working on the Design Trade Studies to analyze the trade-offs and constraints of Passing Partner primarily through equations right now.

My progress right now is on schedule, so there are no changes at the moment.

Next week, I will be working with my group to finalize the Design Report. Since the Design Report will involve a lot of calculations to complete certain sections, this is where most of my focus will be. I also hope that with the Design Report coming together, I can potentially add new certain motors, wheels, etc. to the finalized Bill of Materials.

 

Team Status Report for 10/4

As a team earlier this week, we mainly worked on the design presentation. Since there was a lot of material to cover about Passing Partner, going through the slides together helped John prepare what to say within the time limit. After we went through our design change last week by having the vertical tilt function static at 45º, our biggest risk that could jeopardize our success is still likely the wheel launching mechanism. We have been mitigating this risk as much as we can by thoroughly outlining calculations and selecting parts that overshoot our quantitative specifications to have room for flexibility.

We are currently on schedule, so there are no updates to report. Besides the change made last week to implement a 45º vertical angle instead, we have not had any other significant changes to the existing design of the system. We have shifted our focus entirely to the design report for next week, which is our main deliverable.

Miles’ Status Report for 10/4

At the start of this week the team spent a lot of time collaborating on the design presentation. Towards the middle of this week we also began working on the design report. I have mostly been working on the architecture and system implementation sections.

In addition to the report, I have been continuing to research the other motors, as well as prepping the cad model to be printed. I was hoping to get it printed this week, but there were some tweaks I wanted to make to the model, and I’d rather only print it once than have to reprint it multiple times and waste money, especially when we are still working out our final bill of materials. Our main deliverable for next week will be the design report, which will also have out completed bill of materials and our finalized cad model.

Miles’ Status Report for 9/27

This past week, I have mostly focused on researching materials and working on our CAD model of the launcher. I have been spending a lot of time researching the DC motors we’re going to use to launch, since that is the crux of our project. I’ve been trying to find a balance between getting something powerful enough, but also at a reasonable price and footprint. We also have been working together on the design presentation.

I believe we are still on schedule, and I finished the CAD model like I had planned last week. For next week, I’d like to at least get the motors ordered and have a few pieces 3d printed.

Team Status Report for 9/27

As a team we have spent a lot of this week collaborating on the Design Review Presentation and searching for essential components (Oak-D Camera, motor board, Raspberry Pi) for our launcher. Our biggest risk we think this week after more design is the tilt adjustment. We realized that adjusting the vertical angles ties to our stretch goals of launching different curves/launches. To mitigate this, the vertical tilting is now a stretch goal and the launcher will stay at a constant 45 degree angle for now. To adjust distance we will instead adjust the power, RPM, and torque of the motor. Because 45º is the optimal angle, at max motor power, it will get us our max distance, and if we want to shoot closer we can decrease the parameters of the motors. This overall is a minimal design change, and if anything it simplifies our design. If we in the future want to add the tilt back in, it will not be a major change: just implementing a rack and pinion mechanism.

We are still on track with our schedule, so no changes have occurred.

Below is a still WIP but more complete CAD diagram of what our launcher is now like. Some of the parts are to scale placeholders for our actual parts(motors, rollers, etc.)