Drone project finale

Vincent Zhao 2/10/2025

Abstract

One last time, we look back at the initial problem statement.

We set out to design a human operable vehicle, capable of traversing a 10 kilometer round trip through titan.


The hover drone prototype is designed to test the feasibility of aerial mobility relevant to Titan-like conditions. Specifically, this prototype shall be used to evaluate a drone’s efficient lift-off, sustaining controlled flight, and making a 10 km round trip, bound to constraints similar to the low gravity and dense atmosphere of Titan. It shall also assess stability in simulated wind conditions and energy efficiency for longer distance travel.


This test was designed to evaluate the energy efficiency of our prototype drone during two types of flight paths: a straight-line path and a path with multiple turns simulating navigation over Titan’s rugged and mountainy terrain. These tests aim to provide insights into how our full-scale vehicle might perform under similar conditions. For more details on the design and concept, refer to the planning post.

Final solution

Our testing process was significantly compromised due to physical errors in building our drone. Initially, we had a well-structured plan: we would individually purchase drone parts, 3D print the frame of a CAD-designed FPV drone, and solder/glue the everything to the frame. However, before winter break, we realized that the printed frame was too small and incompatible with our motor parts. Additionally, our limited experience with soldering and circuitry made the assembly process far more difficult than anticipated.

To address this, our building leader, Joe, took the drone home over the break to work on it. Unfortunately, one of the circuits got fried during the process, leading him to reconstruct the frame using hot-glued popsicle sticks as a last-minute solution. Despite our best efforts, upon returning from break, we continued to face technical difficulties. The motors never fully calibrated, causing severe imbalance, and the drone was ultimately unable to achieve stable flight. After numerous failed attempts, we made the difficult decision to scrap our original drone and instead conduct tests using a fellow robotics teacher’s working drone with a similar weight. The measuring was made even easier as he had DJI drone goggles, which allowed us to actively see the voltage per cell in the display.

Procedure

Materials

  • Small drone (250 g).
  • DJI goggles
  • Pre-measured field (100 m).
  • Drone controller.

Preparation

  1. Drone Setup:
    • After getting these materials, we read the initial voltage and record the value
  2. Mark Testing Area:
    • We decided to fly the drone length-wise across the main senior school field, which is around 100m.

Test 1: Straight Flight Path

  1. Use the drone controller to fly the drone in a straight line along the path and back
  2. Maintain a steady height and as straight a flight as possible.
  3. Land the drone at the endpoint and measure the remaining battery voltage.
  4. Initial voltage, and final voltage.

Test 2: Maneuverable Flight Path

  1. Guide the drone along a random maneuverable flight path, with multiple zig zags and turns with two AA batteries strapped onto the top to simulate realistic conditions
  2. Land the drone at the endpoint and measure the remaining battery voltage.

Data Collection

For our data collection, we focused on measuring voltage per cell (V/PC) for battery use. We conducted two types of tests:

  1. NL (No Load) Straight Flight: The drone was flown in a straight line without additional weight, simulating a simple, controlled flight.
  2. L Zag (Loaded Zigzag) Flight: To better simulate real conditions on Titan, we taped on two extra 31g batteries to simulate the weight of a human passenger and flew the drone in a zigzag pattern to try and replicate the need to navigate around potential obstacles in Titan’s unknown and mountain filled terrain.

The following table presents the recorded voltage per cell at the start and end of each test, along with the overall voltage drop:

Test typeV/PC at startV/PC at endVoltage Decrease
NL Straight4.163.910.25
NL Straight4.083.860.22
NL Straight3.783.70.08
L Zag3.913.60.31
L Zag3.653.450.2
L Zag3.553.370.18

The test itself preformed as we intended it to. Although we changed up the procedure during the day of the test due to unexpected setbacks and using an external prototype, there was still an ample amount of data gathered for evaluation. The only issue is that there was not enough proper coordination for us to have specific control variables. For example we only had a No load straight and Load zigzag tests, when we could have included no load zigzag and load straight. However, we were on time constraints and the two tests we conducted are enough to simulate a control variable, and a realistic flight conditions variable as we flew the drone there and back three times for each test.

Data Analysis

For the six individual tests we flew, we recorded the starting and final values before and after the round trip. Our data shows that the battery voltage drop per cell (V/PC) decreases slightly from one test to the next. This trend might be due to the fact that in each test the drone begins its flight from a resting position on the field. Because the drone is initially landed, the energy consumed to lift off.

Defining Efficiency

In our tests, we define the energy efficiency of the drone in terms of the battery’s voltage drop per cell per meter flown. We assumed that the voltage drop (ΔV) is a direct indicator of the energy consumed by the drone during the test. Therefore, efficiency is expressed as:

equation

Where ΔV is the Voltage Per Cell (volts), and D is the total flight distance in meters

This allows us to measure volts per meter. A lower value indicates more effieicncy

Calculating Voltage drop

We conducted two sets of tests:

  1. No Load (NL) Straight Flight:
    The voltage per cell (V/PC) was measured before and after flying a 110 m straight-line course.
    The recorded voltage drops were:
    • Test 1: 4.16 V−3.91 V=0.25
    • Test 2: 4.08 V−3.86 V=0.22
    • Test 3: 3.78 V−3.70 V=0.08

The average voltage drop for the NL straight flight tests come out to be 0.1833 V

  1. Loaded Zigzag (L Zag) Flight:
    Here, the drone flew a maneuverable zigzag path with additional weight (two extra 31 g batteries) to simulate a human passenger. The recorded voltage drops were:
    • Test 1: 3.91 V−3.60 V=0.31 
    • Test 2: 3.65 V−3.45 V=0.20
    • Test 3: 3.55 V−3.37 V=0.18

The average voltage drop for theses is 0.23 V

How we got efficiency

Given that the total flight distance for each test was 110 m (length of our rugby field), we calculate the efficiency for each test type:

NL STRAIGHT:

equation

L ZIGZAG:

equation

 The higher voltage drop per meter in the L Zag test shows that maneuvering through turns and obstacles increases energy consumption.

Scaling the conditions to Titan’s Conditions

Titan’s environmental conditions – a gravity of approximately 1/7 of Earth’s and an atmosphere that is about 50% (or 1.5 times) denser – affect energy consumption for flight. These factors improve lift efficiency and reduce energy requirements.

Together, these factors reduce the energy required for lift. We combine these effects with a reduction factor that can most likely be:

equation

From here, adjust for the full scale efficiency values to simulate Titan’s conditions:

equation

While there isn’t a standard “volts per meter” benchmark for full-scale vehicles, our scaled values indicate that under Titan’s conditions, the energy required per meter would be significantly lower than on Earth. The improvements by a factor of approximately 10.5 imply that our design is solid for a Titan environment.

Summary

Our testing and data analysis highligted that our drone’s energy efficiency, in V/PC per meter, differs between a straight line, and a maneuverable zigzag flight. In our NL straight flight test, the drone experienced an average voltage drop of approximately 0.1833 V over a 110-meter flight for an efficiency of 0.001667 V/m. In contrast, the loaded zigzag (L Zag) test – where we added extra batteries to – yielded an average voltage drop of roughly 0.23 V and efficiency of 0.002091 V/m. These values show that a more realistic path, uses around 25% more energy per meter compared to a straightforward flight. Furthermore, our design basically rested upon the air density and lower gravity considerations, which allow for less energy use by what we assume would be 10.5x.

Our initial design was too complex. We tried to use an overly advanced CAD frame that was ultimately incompatible with our motor parts due to size, and, at the time, we all lacked experience with soldering and circuitry. We did gain experience in these skills; however, focusing on functionality will likely result in a more successful prototype next time.

Another issue was our lack of communication and coordination. Our main builder, Joe, had to work on the drone independently over winter break, and was unfortunately forced to replace the frame due to wiring issues. Personally, while I regularly chcked in and helped with soldering, much of the critical work fell to one team member. I believe that if we established goals and all collaborated in design, it would help avoid wasted time. Although our initial plan was quite solid, the end result was us having to use a fellow robotics teacher’s working drone rather than our own prototype. Although his drone allowed for an easier way to measure the data we needed for our tests, it would have been the best to see our own creation succeed.

Overall, this process of designing and ideating for our own vehicles was quite fun, and we learnt many things about the process of a design cycle that can help improve for if another similar experiment happens. Even though we faced challenges, a 5 kilometer round trip on Titan has been simulated to be possible and efficient with our proposed design.

AI TRANSPARENCY DOCUMENT (CLICK)


Comments

4 Responses to “Drone project finale”

  1. mcrompton Avatar
    mcrompton

    Good report, Vincent. You have been thorough in your description of your work. I like the honesty with which you approach the challenges you faced and what you learned from them. I do have a few questions that I’d like you to answer.

    1. Your straight and zigzag tests were measured by travelling the full distance of the field as measured by the lines on that field, correct? It is reasonable to assume that you are covering 110m of horizontal (straight line) distance in both tests. Because your zigzag test is also covering distance across the width of the field (not a straight line) aren you not covering more distance if you go the full length of the field? The zigzag nature of the flight adds distance. Or maybe you accommodated for that and travelled a shorted length of the field to make up for the additional width distances?

    2. Were you able to fly the drone at a consistent height? You say that your voltage measurements were recorded prior to lift off and after landing. I assume that if the height is the same, you are still measuring the same distance flown. Otherwise, the variance in voltage drop might be due to variance in the height of the climb and landing distance.

    3. I like your thinking around having additional tests (NL zigzag and L straight) to truly be able to identify the factors that determined differences in efficiency. It is essential that in any test, you are clear about what exactly your variables are. (this is more of a statement than a question, but if you want to comment you may).

    4. Thank you for the transcript of the AI exchange. I’m curious about how you found your use of that information. Did you use AI to get answers? Or did you use it to go deeper with your thinking? Did you always think that the AI was “right”? Did you understand the AI’s answers thoroughly? If you didn’t, what did you to clarify it’s statements and fact check them?

    Please reply in the comments below.

    1. 1.Test Distance
      Yes, for our straight-line test we used the 110 m field as measured by the field lines. For the zigzag test, we recognized that the side to side movements inherently add extra distance overall, because even though the goal was to cover the same horizontal distance, the turns and zigzags force the drone to travel a bit more than 110 m. We adjusted our flight path as best as we could to approximate 110 m total, but that the added distance from the turns is a factor that may slightly affect our efficiency readings.

      2. Consistent Height During Flight
      We made every effort to fly the drone at a consistent height in both tests by using stable control inputs and visual markers. In both the straight and zigzag tests, we climbed up to the horizontal bar of the rugby pole to make sure that the energy consumption due to climbing or descending was consistent.

      4. Ai use
      I used AI as a brainstorming tool, especially to help guide me on the efficiency scale calculations since we initially were confused of how to calculate efficiency with the variables. I did not assume the AI was always “right” and only used it for guidance on those specific aspects. For researchable questions, we relied on our own research

      1. mcrompton Avatar
        mcrompton

        Thanks for the clarification, Vincent.

  2. I’ll echo the same thing as Mr. Crompton about the distances involved. The first time you mention distance, you say “around 100 m” but use 110. Then he is very right that the zig zag path would be longer…. so how do you account for that?

    Since efficiency does have that output / input feel, or actual / ideal, I wonder how you might use your V/m calculations to come up with some kind of statement about efficiency. I like that you explicitly point out that a lower value of V/m corresponds to a more effective use of energy, but is it actually efficiency?

    How can you justify that scaling idea as just multiplying the factors? How do we know it would be linear? How do we know that they would compound independently?

    Finally, I wonder about the design implications for shifting over to Titan.

Leave a Reply

Your email address will not be published. Required fields are marked *