/
2023-11-18 Flight Tests

2023-11-18 Flight Tests

Owned by Hardy Yu
Last updated: 2024-06-08 by Daniel Puratich
7 min read

 

Sections for requesting team to fill out:

  • Admin preparation

  • Test Cards / Test Plan

  • Mandatory Attendees

Sections for flight test coordinator to fill out:

  • Flightline team

  • Location

  • Status

  • Drone

Sections for flightline team to fill out:

 

Admin Preparation

Your status should read “submitted” when you submit the FTR to our Flight Test Coordinator.

Once the coordinator approves, and a date/location/drone has been assigned, the status will change to “waiting for sub team review”. Once all sub-teams have reviewed and signed off, the status will change to “approved”

Requested By

@Hardy Yu

Sub-Team Review

(To be checked once reviewed by sub-team representative)

Mechanical
Electrical
EFS
Autonomy
Operations

Date of Request

Oct 25, 2023

Goal Summary

Houston AutoTune / Pilot Training w/ Houston

Status?

status:APPROVED

Desired Airframe

Houston / Pegasus / Tubie

Desired Date(s)

Approx Date range for help out with FTC Scheduling

Testplan - to be filled out by requesting team

Create ONE table per test-item. Eg: “Landing pad images over asphalt”, “landing pad images over grass”, “landing pad images over grass, high” should all be unique tables.

Use each expand to capture one series of tests, eg “Landing pad detection” or “Auto-tuning”.

Card 1, Test #1: Houston un-tuned parameter check

Prerequisite

Objective

Knock off Criteria

  • Initial Frame paramaters set on Houston

  • using Alt-A utility tool

  • Familiarize pilots with system response of untuned drone.

  • Airframe unstable

  • Battery < 10.1v overall, < 3.3v/cell

  • Flight Time > 10 minutes

Procedure

Outcome

  1. Switch into Attitude/Stabilize mode using FM1 button

  • Drone beep,

  • Mission planner shows “STAB” or “Stabilize”

  1. Takeoff in Attitude mode, control check in each direction.

    1. Full stick deflection on each axis

    2. Full stick deflection “rocking” on each axis

  • Watch for drone response, how “long” it takes to get to the setpoint.

  1. Switch to Loiter mode, using FM3 button

  • Drone beep

  • Mission planner shows “LOIT” or “Loiter”

  • Drone holds position

  1. Full stick deflection, same as (2)

  • Watch for drone response

  • Watch for drone stability

  1. Land

  • Don't crash

Card 2, Test #1: Houston Autotune, Pitch

Prerequisite

Objective

Knock off Criteria

  • Autotune research done.

  • Rpi, Camera removed.

  • Aircraft solid, screws tightened, etc.

  • ATUN_Axis set to pitch

  • get pilots/GSO familiar with the procedure of how to autotune

  • Autotune houston in pitch axis

  • autotune complete

  • Airframe unstable

  • Battery < 10.1v overall, < 3.3v/cell

  • Flight Time > 15 minutes

  • Nearby obstacles distance < 30m

Procedure

Outcome

  1. Switch into Loiter using FM3 button on tx16.

  • Drone beep,

  • Mission planner shows “LOIT” or “Loiter”

  1. Takeoff in Loiter, fly to a safe distance and around 8 -12 m altitude

  • Watch for drone stability, ensure systems OK.

  1. Switch into Autotune by using FM5 button on TX16.

  • Drone beep

  • Mission planner shows “ATUN” or “Autotune” in HUD

  1. Wait for Autotune to complete

  • Pilot: Watch for drone stability and clear of objects. Do not touch sticks unless necessary

    • (still have control ability when nearby object become close)

  • GSO: Watch for autotune messages, make sure no failures. Enusre order of messages correct.

  1. Autotune complete message received

  • Crosscheck atune complete

    • GSO:

       

    • Pilot: observe drone not significant movement

  1. Switch into Loiter, fly back to a closer distance

  • This will revert to old tune.

  • Ensure system OK, sensors OK

  1. Switch into autotune, land, disarm, power and power cycle + battery check

  • This will apply new tunes and then save them.

  • We will do a 3-axis controls check once all autotune is complete.

Card 2, Test #2: Houston Autotune, YAW

Prerequisite

Objective

Knock off Criteria

  • Autotune research done.

  • Rpi, Camera removed.

  • Aircraft solid, screws tightened, etc.

  • ATUN_Axis set to YAW

  • get pilots/GSO familiar with the procedure of how to autotune

  • Autotune houston in pitch axis

  • autotune complete

  • Airframe unstable

  • Battery < 10.1v overall, < 3.3v/cell

  • Flight Time > 10 minutes

  • Nearby obstacles distance < 30m

Procedure

Outcome

  1. Switch into Loiter using FM3 button on tx16.

  • Drone beep,

  • Mission planner shows “LOIT” or “Loiter”

  1. Takeoff in Loiter, fly to a safe distance and around 8-12 m altitude

  • Watch for drone stability, ensure systems OK.

  1. Switch into Autotune by using FM5 button on TX16.

  • Drone beep

  • Mission planner shows “ATUN” or “Autotune” In HUD

  1. Wait for Autotune to complete

  • Pilot: Watch for drone stability and clear of objects. Do not touch sticks unless necessary

  • GSO: Watch for autotune messages, make sure no failures. Enusre order of messages correct.

  1. Autotune complete message received

  • Crosscheck atune complete

    • GSO:

       

    • Pilot: observe drone not significant movement

  1. Switch into Loiter, fly back to a closer distance

  • This will revert to old tune.

  • Ensure system OK, sensors OK

  1. Switch into autotune, land, disarm.

  • This will apply new tunes and then save them.

  • We will do a 3-axis controls check once all autotune is complete.

Card 2, Test #3: Houston Autotune, Roll

Prerequisite

Objective

Knock off Criteria

  • Autotune research done.

  • Rpi, Camera removed.

  • Aircraft solid, screws tightened, etc.

  • ATUN_Axis set to roll

  • get pilots/GSO familiar with the procedure of how to autotune

  • Autotune houston in pitch axis

  • autotune complete

  • Airframe unstable

  • Battery < 10.1v overall, < 3.3v/cell

  • Flight Time > 10 minutes

Procedure

Outcome

  1. Switch into Loiter using FM3 button on tx16.

  • Drone beep,

  • Mission planner shows “LOIT” or “Loiter”

  1. Takeoff in Loiter, fly to a safe distance and around 8-12 m altitude

  • Watch for drone stability, ensure systems OK.

  1. Switch into Autotune by using FM5 button on TX16.

  • Drone beep

  • Mission planner shows “ATUN” or “Autotune” in HUD

  1. Wait for Autotune to complete

  • Pilot: Watch for drone stability and clear of objects. Do not touch sticks unless necessary

  • GSO: Watch for autotune messages, make sure no failures. Enusre order of messages correct.

  1. Autotune complete message received

  • Crosscheck atune complete

    • GSO:

       

    • Pilot: observe drone not significant movement

  1. Switch into Loiter, fly back to a closer distance

  • This will revert to old tune.

  • Ensure system OK, sensors OK

  1. Switch into autotune, land, disarm.

  • This will apply new tunes and then save them.

  • We will do a 3-axis controls check once all autotune is complete.

 

Card 3, Test #1: Houston tuned parameter check

Prerequisite

Objective

Knock off Criteria

  • Autotune card 2 Test 1-3 complete.

  • Characterize tuned system response

  • Compare against un-tuned system response.

  • Airframe unstable

  • Battery < 10.1v overall, < 3.3v/cell

  • Flight Time > 10 minutes

Procedure

Outcome

  1. Switch into Attitude/Stabilize mode using FM1 button

  • Drone beep,

  • Mission planner shows “STAB” or “Stabilize”

  1. Takeoff in Attitude mode, control check in each direction.

    1. Full stick deflection on each axis

    2. Full stick deflection “rocking” on each axis

  • Watch for drone response, how “long” it takes to get to the setpoint.

  1. Switch to Loiter mode, using FM3 button

  • Drone beep

  • Mission planner shows “LOIT” or “Loiter”

  • Drone holds position

  1. Full stick deflection, same as (2)

  • Watch for drone response

  • Watch for drone stability

  1. Land

  • Don't crash

Test #1: Pilot Training - @Yuchen Lin

Prerequisite

Objective

Knock off Criteria

  • aircraft ready

  • stabilze mode quad drone control tranining

  • runout of batteries

  • crash

  • tried

Procedure

 

 

 

Test #2: Pilot Training - @Hardy Yu

Prerequisite

Objective

Knock off Criteria

  • aircraft ready

  • stabilze mode quad drone control tranining

  • runout of batteries

  • crash

  • tried

Procedure

 

 

 

Necessary Preparation

Necessary Preparation

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

Necessary items:

  • N/A

Flight characteristics needed:

  • Require long flight endurance (needs more batteries)

Comms / Support needed:

  • TBD

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

 @Hardy Yu

 

 

 GSO

@Yuchen Lin

 

 

PIC FTC

This section and remaining to be filled out by FTC and Flightline Team

Flightline Team

Name

Phone #

Role

Reason

Name

Phone #

Role

Reason

 

 

 Driver / Helper

 

@Daniel Puratich

 

FTL

 

Pre-Flight Preparation

Checklists

 

Incident Procedures

Flight Test Timeline

Date/Time

Action

Notes

Date/Time

Action

Notes

Date/Time

Action

Notes

Date/Time

Action

Notes

12:00 pm

Briefing @ WARG Bay

 

12:20 pm

Arrival at Flight Test Location

 

 

Flight Test Card #1…… (eg: Capturing data, tuning, etc)

 

 

Flight Test Card #2

 

 

Flight Test Card #…….N

 

0X00

Debrief

 

 

 

 

 

 

 

DEBRIEF

To-do

 

Debrief

 

https://drive.google.com/drive/folders/1U0YxCWHETwVbdSjnfKc9icndyzbdJmyX

  • we didn’t damage the huston

  • parallel 3s extend flight time

  • keep the logs

  • finish the flight objective

  • @Yuchen Lin @Hardy Yu lot’s of pilot training with 8 battaries

  • prototype a battery heater

  • didn’t disarm when it hit the ground

  • start yaw and yaw e at once only finish one of it

  • unsure yaw and yaw e what it’s testing

All of these major issues should be addressed via Root Cause Analysis Forms:

 

Related content