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
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 |
---|---|---|---|
@Smile Khatri | 8076320853 | Mech |
|
@Yuchen Lin | 6474256385 |
|
|
@Hardy Yu |
|
|
|
@Manasva Katyal |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Flightline Team
Name | Phone # | Role | Reason |
---|---|---|---|
@Smile Khatri |
| Mech lead/Pilot |
|
@Yuchen Lin |
| FTC/GSO |
|
@Ben Lovegrove |
| Mech/Observer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Pre-Flight Checklists
Flight Test Timeline
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