Team Status Report for 10/25

This week, the main thing we did as a team was place our first set of orders. We ordered all the parts necessary for the main launch mechanism , which we plan to have done by the interim demo. We already started building it this weekend and so far it is going smoothly. On top of that, we all individually worked on our sections of the project and the Ethics Assignment.

As usual, we still believe that the launcher mechanism is the biggest risk of our project, but we are doing our best to get that part done as soon as possible to mitigate this risk. If we are confident in this by/before the interim demo, we will have confidence that everything else can come together as well.

The only changes made to the existing design of the system is that the CV, depth AI, and target coordination will all be done on the Oak-D Pro camera’s processor rather than the Raspberry Pi, which is just as capable and there will be less back and forth between the components. However, there is no change in costs and the overall project design is still the same as before.

Andrew’s Status Report for 10/25/2025

This week, I completed the individual as well as the team portions of the Ethics Assignment.  I helped Miles put in the orders from our BoM and I have just started the initial building process of the actual launcher mechanism (integrating the wheels, bike motors, tennis balls, and battery together). I also helped John with the CV program, depth AI, and targeting coordinates that will be completely done on the Oak-D Pro camera’s processor rather than the Raspberry Pi, which is just as capable and seems more of a practical approach and less interfacing involved. Finally, I helped Miles submit the order for the 3D printing of the base of the launcher, which will house the motors that control the X-Axis rotation and the Raspberry Pi.

My progress is currently on schedule, especially since I am starting to build the launcher mechanism this weekend and should be able to test if my physics hand calculations are correct soon.

Next week, I hope to continue building on the launcher mechanism and have it mostly working, while also assisting my teammates with the CV program and interfacings between the camera, Raspberry Pi, and motors.

John’s Status Report for 10/25/25

This week, I worked on the ethics assignment and put in all of our orders, and we are starting to build our launcher. We are also starting to interface our Pi with our Camera and attempting to decide on how we want to approach our sensing. We decided that the CV will be done on the Oak-D Pro Camera’s Processor, and that it is going to send out coordinates to our Pi. The Pi will then have code that will determine launch speed and base rotation based on the coordinates that it receives from our Camera. We decided this as the latency involved with sending a full image or depth map to the processor can be bypassed by simply doing our CV on the Oak-D Pro.

We fell a little bit behind schedule as we wait for our orders to come in, but if we can finish the launcher build by next week, we should be back on schedule.

Miles’ Status Report for 10/25

This week as a team we put in some of our orders for parts that will hopefully arrive within this week so we can begin working  on assembling our launcher. Throughout this week I have also been working on polishing our cad model to be ready for printing. I plan to put in the 3d print request tomorrow so that it should also be ready by the time our other parts also arrive.

For next week, once the motors arrive I plan to start the motor control code for the launcher, as we hope to have the main launch mechanism done by the interim demo.

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.