2024-7-20 Houston 2 Autotune flight test

Admin Preparation

Requested By

@Yuchen Lin

Goal Summary

Houston 2 first-time Flight test

Status?

DRAFT / SUBMITTED / WAITING FOR SUB-TEAM REVIEW / APPROVED

Desired Airframe

Pegasus 1

Date(s)

20th July 2024

Testplan

Test 1: Prove basic Flight performance

Procedure

Goals / Objectives

Knockoff Criteria

  1. Battery plugged in

  • Mission planner no pre-arm warning

 

  1. Bring the drone to the flightline

  • toggle safety switch

 

  1. Enable logging

 

 

  1. Take off the drone in Stablize

  • verify drone flight performance

  • Drone unstable

  • unable to establish VLOS

  • Timer threshold:

    • flight time exceeded 5 min.

    VBatt below safety threshold: 10V

    • QLAND immediately, disarm when landed.

    • Recover drone & gather state of batteries

    Lost link

    • Follow lost link procedures. Maintain vlos if possible.

    • Contact necessary local authorities.

  1. Switch Flight mode to Alt Hold

  • verify drone flight performance

  • Drone unstable

  • unable to establish VLOS

  • Timer threshold:

    • flight time exceeded 5 min.

    VBatt below safety threshold: 10V

    • QLAND immediately, disarm when landed.

    • Recover drone & gather state of batteries

    Lost link

    • Follow lost link procedures. Maintain vlos if possible.

    • Contact necessary local authorities.

  1. Switch Flight mode to Loiter

  • verify drone flight performance

  • Drone unstable

  • unable to establish VLOS

  • Timer threshold:

    • flight time exceeded 5 min.

    VBatt below safety threshold: 10V

    • QLAND immediately, disarm when landed.

    • Recover drone & gather state of batteries

    Lost link

    • Follow lost link procedures. Maintain vlos if possible.

    • Contact necessary local authorities.

  1. land the drone

  • disarm the drone, Toggle safety switch

 

Test 1: Tuning

Procedure

Goals / Objectives

Knockoff Criteria

  1. Battery plugged in

  • Mission planner no pre-arm warning

  • make sure autotune is in one of the flight mode

 

  1. Bring the drone to the flightline

  • toggle safety switch

 

  1. Enable logging

 

 

  1. Take off the drone in Loiter

  • verify drone flight performance

  • Drone unstable

  • unable to establish VLOS

  • Timer threshold:

    • flight time exceeded 5 min.

    VBatt below safety threshold: 10V

    • QLAND immediately, disarm when landed.

    • Recover drone & gather state of batteries

    Lost link

    • Follow lost link procedures. Maintain vlos if possible.

    • Contact necessary local authorities.

  1. Engage Autotune

  • one axis at a time

  • Drone unstable

  • unable to establish VLOS

  • Timer threshold:

    • flight time exceeded 5 min.

    VBatt below safety threshold: 10V

    • QLAND immediately, disarm when landed.

    • Recover drone & gather state of batteries

    Lost link

    • Follow lost link procedures. Maintain vlos if possible.

    • Contact necessary local authorities.

  1. Switch Flight mode to Loiter to back to landing area

 

  • Drone unstable

  • unable to establish VLOS

  • Timer threshold:

    • flight time exceeded 5 min.

    VBatt below safety threshold: 10V

    • QLAND immediately, disarm when landed.

    • Recover drone & gather state of batteries

    Lost link

    • Follow lost link procedures. Maintain vlos if possible.

    • Contact necessary local authorities.

  1. Land the drone with autotune mode

  • to permanently save the PID value

  • Drone unstable

  • unable to establish VLOS

  • Timer threshold:

    • flight time exceeded 5 min.

    VBatt below safety threshold: 10V

    • QLAND immediately, disarm when landed.

    • Recover drone & gather state of batteries

    Lost link

    • Follow lost link procedures. Maintain vlos if possible.

    • Contact necessary local authorities.

  1. Disarm the drone

  • disarm the drone, Toggle safety switch

 

 

Necessary Preparation

Explain what capacity you need, what needs to be mounted, etc.

Necessary items:

  • RPI

  • Lidar

Flight characteristics needed:

  • Flight stability

Comms / Support needed:

  •  

Mandatory Attendees

This is a section for all attendees from your subteam which will be present for this flight test. (because they are testing their products, or otherwise)

Name

Phone #

Sub-team

Role

Name

Phone #

Sub-team

Role

@Smile Khatri

8076320853

Mech

 

@Yuchen Lin

6474256385

 

 

@Hardy Yu

 

 

 

@Manasva Katyal

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


Flightline Team

Name

Phone #

Role

Reason

Name

Phone #

Role

Reason

 @Smile Khatri

 

 Mech lead/Pilot

 

@Yuchen Lin

 

FTC/GSO

 

@Ben Lovegrove

 

Mech/Observer

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Pre-Flight Checklists

  • Software configuration correct

  • Compare against latest baselines and verify no params changed, or changes approved by comp-ft-team

  • LTE tested

  • Autopilot Orientation checked

  • Motors tested

  • Prop direction check

  • Sensors outputs healthy & within range

  • Controller input mappings correct

  • Controller input choices correct for pilot preferences

  • Wireless trainer tested & working per pilot preferences.

Hardware (wiring)

  • Wires are not too tight or too loose (comfortable, not strained, not flapping around)

    • No cut/exposed wires

    • Shrouding is neat + presentable

    • Solder joints look good

      • no cracks

      • no corrossion

      • no exposed contacts (unless expected)

    • Specific requirement from @Daniel Puratich

      • no exposed pad without solder on ESC caps

        • i did this on peggy 2

        • someone will need to do with peggy 1

      • ESCs all have a touch of hot glue to secure cap to board

    • Connectors fully plugged in

    • Connectors in good health

Hardware (airframe)

  • Bolts secure (nothing loose)

    • Carbon fiber not cracked

    • 3D prints not failing / crushed / cracked

    • No loose items

Hardware (groundstation)

  • ELRS Gemini tested & Working

    • Logging correct

    • Data looks correct

    • Control tower tested & working

  • Tracking antenna x2 (control + video) (mechanical)

    • Servos secure

    • Hardware (antennas) secure

    • No cracks/bends/chips in polycarb/aluminum

    • Gears / shafts look healthy

    • Grease if necessary

  • Tracking antenna x2 (control + video) (electrical)

    • Electrical components secure

    • Power delivery / signal wires secure, no cracks/corrosion/damage

  • Video System

    • goggles(?)

    • Monitors(?)

    • Video tower tested & working

  • Laptop w/mission planner configured correctly.

    • LTE Link tested working

Flightline Kit

  • Spare motors

  • Spare props

  • Spare tools

    • Metric allen keys

    • Socket set

    • Pliers (flatnose + needle nose)

  • USB-C cable (short & long)

  • Soldering iron + heat shrink + spare cables

  • Power supplies for ground station computer

  • Ground station computer

  • Spare bolts

  • Radio Controllers

  • Mission plan clear

  • flightline roles assigned

  • Communication hierarchy established

  • Incident procedures & roles in-place & briefed to all flightline team members

  • Timeline for day-of clear

  • Battery charging plan, equipment management plan clear.

  • Transportation clear

  • Batteries in safety bag

  • Equipment

    • Zip tie

    • duck tape

    • label maker

    • Type c cable

    • ELRS Gemini

    • Saleae Logic Analyzer

    • charged WARG laptop

    • spare bag for small electronics

    • controller box

      • two controller

      • battery tester

    • VTX box

  • execute

Total 5 main system checked:

  • Power system(battery and connection)

  • Propulsion system(motor and propeller)

  • Controller system(Control links and ground station system)

  • Sensory system(sensors)

  • Video system (VTX)


  • Debrief

  • clean / store equipment if necessary

Flight Test Timeline

 

Date/Time

Action

Notes

Date/Time

Action

Notes

9:30

Meet up at the Bay

 

10:20

Arrive at Cornfield

 

10:30

first take off in stabalize→ take off 2 more times in stabalize

 

10:44

take off in alt hold → hover → hot motor check

 

10:55

Althold take off → autotune pitch

 

11:20

No luck autotuning → take off in althold, reattempted in loiter but failed

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


DEBRIEF

Flight test debrief report

10:27 arrive at WRESTRC

-----Final mech inspection-----

first flight test:
stabilize take off and observe control performance

take off time: 10:30am

observation:

  • wrong setup which led to motor auto stop? @Yuchen Lin pls update this

    • Follow up: This does not. Originally I thought we could set the motor emergency stop/ arm. But later, it will not display any other pre-arm warning, so hot fix and solve the issue.

  • drifting a lot(wind)

  • altitude is changing a lot

  • this is an expected behavior in stabilize mode

actions:
Take off in stabilize 3 times
control performance check (little throttle input)

ends: 10:40

second flight test:
althold take off and hover and hot motor check

take off time: 10:44

observation:

  • Altitude is stable, lots of drifting7

    • Pilot @Smile Khatri tried to correct drifting but was giving too much throttle input correction which can be dangerous

      • This is a part of pilot training, letting the pilot control the drone smooth is a good practice. No direct impact on this.

actions:
first take off aborted (mag realign warning)
recalibrate the Compass and the accerlator
take off again
hover 30 secs no hot motor
land

ends: 10:50

third flight test:
althold and autotune pitch

take off time: 10:55

observation:
still yaw realign
vibe yellow observed
cpu red
Battery failsafe(land at 10.1v) {at the end observe lost throttle}

  • This is the battery labelled lost battery(Note: in previous autotune procedure we did mentioned autotune will take long so might need to use the full battery)

autotune does not complete
current draw 17 -> 19 A

  • Normal wind conditions (not full throttle just hover and loiter)

decide not to do autotune(not seeing the drone twitch)

roll and pitch

11:20 -11:22
new battery no luck stuck at 0 percent
second battery got drained very fast two flight <5 min each for 10.9v (aggressiveness reduce)

  • this I cannot confirm but it’s not a battery issue(the issue observed is houston is less efficient than the previous one, which leads to an overall reduce in flight time)

yaw tuning working but not close to complete

actions:
first takeoff abort autohold drift too much (will reattempt in loiter)

ends: 11:40