/
2023-12-02 Flight Tests

2023-12-02 Flight Tests

Owned by Yuchen Lin
Last updated: 2023-12-25 by Daniel Puratich
12 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

Requested By

@Yuchen Lin

Sub-Team Review

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

Mechanical
Electrical
EFS
Autonomy
Operations

Date of Request

Nov 28, 2023

Goal Summary

Pegasus AutoTune

Status?

APPROVED

Desired Airframe

Pegasus

Desired Date(s)

Dec 2nd in Cornfield

Testplan - to be filled out by requesting team

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

Prerequisite

Objective

Knock off Criteria

  • Initial Frame paramaters set on Pegasus

  • using Alt-A utility tool

  • Familiarize pilots with system response of untuned drone.

  • Airframe unstable

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

  • Flight Time > 20 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: Pegasus Autotune, Pitch

Prerequisite

Objective

Knock off Criteria

  • Autotune research done.

  • 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 < 19.8 v overall, < 3.3v/cell

  • Flight Time > 20 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: Pegasus Autotune, YAW

Prerequisite

Objective

Knock off Criteria

  • Autotune research done.

  • 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 < 19.8v overall, < 3.3v/cell

  • Flight Time > 20 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: Pegasus Autotune, Roll

Prerequisite

Objective

Knock off Criteria

  • Autotune research done.

  • 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 < 19.8v overall, < 3.3v/cell

  • Flight Time > 20 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: Pegasus 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 < 19.8v overall, < 3.3v/cell

  • Flight Time > 20 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

Necessary Preparation

Necessary Preparation

Necessary items:

  • Ground test complete

  • LTE configured properly

Flight characteristics needed:

  • Require long flight endurance (needs more batteries)

Comms / Support needed:

  • TBD

Mandatory Attendees

Name

Phone #

Sub-team

Role

Name

Phone #

Sub-team

Role

 @Hardy Yu

 

 

 GSO

@Nathan Green

 

 

PIC Driver

@Yuchen Lin

 

 

FTC

@Daniel Puratich

 

 

Director

@Georgia Westerlund

 

 

Media rep

@Conall Kingshott

 

 

Mech rep

@Alison Thompson

 

 

Mech rep

Flightline Team

Name

Phone #

Role

Reason

Name

Phone #

Role

Reason

  @Nathan Green @Alison Thompson

 

 Driver / Pilot

 

@Daniel Puratich

 

FTL

 

@Conall Kingshott

 

Mech rep

 

Pre-Flight Preparation

Checklists

Raspberry Pi can collect images with the $200 CV Camera
Test the imaging repository with the Raspberry Pi and confirm images are taken and stored on the SD card
Edit the rc.local and ensure that image collection code runs on Raspberry Pi startup
Raspberry Pi can be powered onboard the drone. Need help from the Electrical team.
Raspberry Pi and $200 CV Camera are mounted onto Houston. The $200 CV Camera needs to be pointing in the downards direction.. Need help from the Mechanical team.
Flight test location booked
Drone Registration -
Houston
Tubie
Pegasus → flying on vanny registration
Ensure we have good props for Pegasus after last tests crash
Telemetry Verified Functional - @Nathan Green to verify with new LTE connectors
@Nolan Haines Schematic for and delegating manufacturing of anti-spark connector configuration
@Daniel Puratich to update template with all the new things he added to this template this time
@Nathan Green add to Onedrive logs from last time
@Georgia Westerlund uploading past test images to onedrive media
@Conall Kingshott potentially slop on landing gear
@Hardy Yu purchase request for more crossfire Rxs
Pilot scheduled - @Daniel Puratich
Test Plan - @Daniel Puratich
Initial frame parameters set - @Nathan Green
Verify we have wrestrc card
Systems test - @Daniel Puratich
Check flight controller orientation - @Nathan Green
Check motor spin & rotation direction - @Nathan Green
Check DSHOT configuration (DS300, bidir?)
Motors plugged into correct pins on pixhawk
Verify motors 1,2,3,4 in motor test go in the correct order
Verify motors in a,b,c,d configuration is correct order
verify rotational response of motors is correct (with more than just audio), move the drone around and check each motors reponse individually
Check transmitter mappings
Verify communication links
VTX/RX - no video on any of these aircrafts
Controller
Groundstation
Ammeter working - @Nathan Green
Verify data logging - @Nathan Green checked SD card, its working
Transportation logistics finalized
Booking SDC vehicles - @Hardy Yu to decide, @Daniel Puratich
Assigning drivers - @Daniel Puratich Done see above.
Renting any needed equipment (trailer? generator? etc.) - @Daniel Puratich not needed.
Setting Failsafes, @Nathan Green
normal failsafe set to land
disabled battery failsafe, dont want it to randomly land
GCS failsafe set to always land after 5 seconds of no GCS
Confirm the Raspberry Pi is securely attached to the drone.
Confirm the image collection software runs when the Raspberris powered on.
@Nathan Green configuring the GPS so both GPS’s are used
@Nathan Green Setting the controller profile on the radio master
SDC Vehicle key collected → machine shop is closed, we will not be able to grab the key @Hardy Yu
Batteries Planned for (DON'T LEAVE CHARGING OVERNIGHT)
Drone batteries & spares - 2 sets for pegasus, 3 houston batteries
Transmitter batteries - 70% on transmitter
Battery tester/indicator
On-site kit together - @Daniel Puratich announcing checklist
First Aid Kit
Ground station if applicable
Laptop
Antenna / Receivers
Transmitter
Extra Water
Power cords / Extension cables
Wrenches - none needed
Allen keys (metric ones) - three sets
Knives
Tape
Rope/string - not needed
Zip ties
Velcro
Radios
Safety goggles - not needed
Fire extinguisher - we dont have one, theyre out of our budget gg
Spare foam - not needed
hot glue gun w/ hot glue stick - not bringing that
harnesses
ratchet set
battery removed for velcro (thin 3d printed thing) for pegasus
Wrestrc
Airfame assembled
ESCs/flight controller wired
Radio equipment tested
Channel mappings
Flight modes
Motors tested
Check DSHOT configuration (DS300, bidir?)
Motors plugged into correct pins on pixhawk
Verify motors 1,2,3,4 in motor test go in the correct order
Verify motors in a,b,c,d configuration is correct order
verify rotational response of motors is correct (with more than just audio), move the drone around and check each motors response individually
Wiring secured (Harnessing)
End-to-end test (neglecting props)
Props require a little gold ring which we did not use during the strap down test, may have caused extra vibrations.
Check the center of gravity - CG is off quite a bit but because only running two batteries and much less hardware then anticipated it will be reasonable for this test
All components not on the airframe that are required should be in the flight box (e.g. props & prop nuts)
Airframe payload - Raspberry Pi + $200 Camera
Mount to airframe pointing downwards (exact angle doesn’t really matter)
Spare parts
Props
Houston props
Peggy props
Airframe components (landing struts, arms, etc)
wings nuts - n/a
prop nuts
any detached components such as angle mount - none needed
Hardware to assemble these components
Spare Electronics - we dont have much
ESCs
Motors
Flight controllers
Receiver
Ground station Software updated

Incident Procedures

Flight Test Timeline

Date/Time

Action

Notes

Date/Time

Action

Notes

 

Date/Time

Action

Notes

Date/Time

Action

Notes

1:00 pm

arrive bay and do pre-flight checklist

 

2:00 pm

Briefing @ WARG Bay

 

2:20 pm

Arrival at Flight Test Location

 

 

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

 

 

Flight Test Card #2

 

 

Flight Test Card #…….N

 

 

 

 

 

 

 

DEBRIEF

To-do

 

Debrief

Related content

2023-11-11 Flight Tests
2023-11-11 Flight Tests
Flight Tests
More like this
2023-10-28 Flight Test
2023-10-28 Flight Test
Flight Tests
Read with this
2024-04-06 Pegasus CS2
2024-04-06 Pegasus CS2
Flight Tests
More like this
July 16, 2023 Flight Test
July 16, 2023 Flight Test
Flight Tests
Read with this
2024-03-30 Pegasus E2E
2024-03-30 Pegasus E2E
Flight Tests
More like this
2023-11-19 Flight Tests
2023-11-19 Flight Tests
Flight Tests
Read with this