Blog Posts

Preparing for QRB 1

The One For All team jumped in full speed to the start of the spring semester and has already made great progress. The Aerial Drone has successfully been connected to an access point which will drastically help latency issues. The PiCar controls and video were successfully integrated into the UI, as well as it having full network communications with the Tello Drone.

The team needs to move hastily into the next steps of the project. Now that the PiCar and Tello Drone are properly integrated and communicate with one another more UVs need to be purchased in order to see how many can properly be integrated.

The One For All team is excited to see the reception of their project plan and testing plans for this semester and sharing it with the liaison engineers of Northrop Grumman.

Starting Again in 2021

Team One For All is excited to get back to their project in the new year and has already made great progress. On the software side of the project the Base UI has been developed and includes the “Smart Screen” selection. The Aerial has also been completely integrated into the UI.

Next on the hardware side of the project the first PiCar has been completely assembled, it is pictured below.

The team is excited to integrate this into the UI and continue ordering more Unmanned Vehicles. Excited to see what is in store for the One For All team in 2021!

SLDR Peer Review

This week, we presented our SLDR presentation to our fellow peers in order to receive some feedback before our actual presentation for our Sponsors next week. As always, the One For All team was very excited for this event and the feedback that we were going to receive. The picture below is of our team presenting to our peers.

After this presentation, we had a lot of feedback that we needed to go over. The largest of which came from our coach, Dr. Latorre. When we were going over our presentation during our coach meeting, he suggested that we should be focusing more on the final product rather than what we have done. With this suggestion, the One For All team started to brainstorm some ideas on how we can demonstrate what we have envisioned for the final project.

We sure got our work cut out for us from now until this Tuesday. But we are always up for the task!

Prototype Inspection Day

This week, the One For All team presented our prototype at this year’s full online Prototype Inspection Day. We were really excited to get what we had as a prototype out there for the judges to see so that we can start getting feedback on what needs to be changed.

Over the course of the day, we received a bunch of feedback on our prototype UI, both positive and negative, which we are very thankful for. Some points that were made really caused us to stop and think about what we wanted to do moving forward. For instance, one piece of feedback was how we issued warnings on our prototype. At the time, we had popups showcasing warnings but due to some of the feedback that we received, we think we are going to proceed with a different solution that won’t distract the operator as much as the popups.

At the end of the day, the One For All team is very satisfied with how PID went. We looked forward to what we can accomplish before the SLDR and we will update you at a later date.


This week, the One For All team has started to turn our sights to Prototype Inspection Day (PID). One For All has had some ideas about what we want to do for our actual prototype and after today we have a concrete plan on what we would like to do for PID.

After talking it out and coming up with a plan, we decided to focus mainly on the software side for our PID presentation. We want to get as much feedback as we can from the judges on things like ease of use to how intuitive our UI is at this point in the project. But just because we are focus on the software side of our project doesn’t mean we can’t start working with the hardware.

Drone Picture Taken from Tello EDU

The picture above is after One For All met for the first time in person to work on the construction of the Sunfounder PiCars and was actually taken with our Tello Drone EDU. We know the kit was going to be a lot of building but there are SOOOO many screws and bolts that go into such a small thing. So far, we have constructed up until the point where we need the Raspberry Pi’s that we ordered to continue building.

Vehicle Selection

This past week, we have been working hard to finalize our vehicle choices that would work best with our project. We have chosen two different types of vehicles, one aerial vehicle and one ground vehicle. For the ground vehicle, we chose the SunFounder Smart Video Car Kit V2.0. This particular model is Raspberry Pi compatible, has a camera module, and can be coded using python. We felt like this was a good option for our ground vehicle as it would give our team a lot of freedom when coding.

As for our aerial vehicle, we went with the DJI Tello EDU drone. This model has a built-in 720p camera and can be configured to recognize objects. One For All felt like this was a good choice as it comes with an Software Development Kit (SDK) in python. This gives a lot of commands that were prebuilt for the drone already, along with us being able to use some of these commands to make our own.

For this upcoming week, the One For All team is starting to prototype our UI and we are excited to see where we can take this prototype before presentation day. The sky is the limit (and our coding ability).

PDR Presentation Week

This week the team held their Preliminary Design Report Presentation for Northrop Grumman. We spent days beforehand incorporating the feedback from our peers that we received from the peer review presentation. This involved redesigning slides, rehearsing, discussing and planning every detail of the presentation, from the order in which we would speak, to back-ups in case one of us experienced technical issues. Finally, we held our final practice on Tuesday night, and by the end of it, we were confident we had a solid presentation to show off our hard work to the engineers at Northrop Grumman.

The day finally came, and on Wednesday we gave the presentation itself. Everything went smoothly, and overall we felt that the engineers from Northrop Grumman were pleased with our design. We received some great pointers and advice from some of the engineers that were in attendance, which we believe will really help to focus our work moving forward. Now, as we look to start the process of building a functioning prototype, we can move forward with the assurance that our designs have been checked out by some of the most talented engineers in the country.

PDR Preparation and Peer Review

This past week and a half has sure felt like one ongoing assignment. From finishing the Minor Report to immediately working on the PDR presentation and report.

After compiling all of our work into the Minor Report and hashing out the formatting, the One For All team immediately started to work on our PDR presentation for our Peer Review.

We were all super excited to present to our peers as we wanted to know how well we could communicate our ideas to an audience as well as how they felt about the direction that we are taking this project in. Overall, the One For All team felt that the presentation we gave was very solid. We were able to give a very high-level description of our project allowing almost everyone to understand it while maintaining the technical aspects pertaining to our project.

With the PDR Peer Review in our rear view mirror and reviews in our back pocket, our sights are now set on our PDR Presentation and Report for Northrop Grumman. We are a little nervous due to us presenting to our client but we are excited just the same.

A Month into How Many Can You Handle?

This past month has sure been a busy one. From being assigned to a team to trying and research as much as we can about our respective problems, our work has been cut out for us.

Over this past month, the One For All team has put countless hours into researching, planning, and documenting all of our progress on this project. This past week, our liaisons presented us with a different way to approach our problem and in doing so, caused us to really look at how we previously thought of solving it. As we can not get into too much detail, we were focused on how we were going to give commands to the drones rather than how the drones should be receiving those commands.

With this new way of thinking, the One For All team is excited for this next month as we solidify the solution that we want to move forward with and we hope to do our best.

Research, Research, Research

This past week has been a busy one for sure. From meeting our liaisons, Mary Alice and Jessica, to starting out initial research, this week and the last has really thrown us into the ocean with us barely knowing how to swim.

After our liaison meeting, we really started to get down to business. Within our team, we started to cast a large net over the topics of multitasking and decided to look at both multitasking technologies as well as the principles behind it. With this goal in mind, we are exploring different avenues of research in hopes of finding the most efficient solution to the problem at hand.

This upcoming week, we will refine our research efforts even further to narrow down which solution we would like to implement. Along with a couple of assignments and reports, this week will be another busy one. But One For All is ready for yet another great week.