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:
EFS to fill out flight test cards
đ 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 | |
|---|---|
Sub-Team Review (To be checked once reviewed by sub-team representative) |
|
Date of Request | 2024-01-30 |
Goal Summary |
|
Status? | WAITING FOR SUB-TEAM REVIEW |
Desired Airframe | Houston / Pegasus |
Location + Time | WrestRC |
đ„ 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â.
Note: This flight test can be Gemini + OA at the same time.
General Gemini Procedure:
Enable logging on TX16.
Preface: https://ardupilot.org/copter/docs/parameters.html#avoid-parameters , we want to determine if:
Avoid backup_spd
Avoid accel_max
Avoid backup_dz
Has impacts on handling âpredictabilityâ near obstacles.
Test #1: Default OA setting characteristic handling | ||
Procedure | Goals / Objectives | Knockoff criteria |
AVOID_MARGIN = 2m AVOID_ACCEL_MAX = default AVOID_BACKUP_DZ = default AVOID_BACKUP_SPD = default |
|
|
|
| Impact w/obstacle
Loss of orientation
Loss of control
OA failure
|
| ||
Test #2: Modified OA Setting handling | ||
Procedure | Goals / Objectives | Knockoff criteria |
|
| Impact w/obstacle
Loss of orientation
Loss of control
OA failure
|
| ||
Necessary Preparation
Explain what capacity you need, what needs to be mounted, etc.
Mechanical
- Pegasus cleared to fly (mechanically)
- sensor mount ready
- Motors + frame rigid
- Houston cleared to fly (mechanically)
- sensor mount attached
- arms + plates rigid
Electrical
- Pegasus cleared to fly (electrically)
- harnessing secure
- Houston cleared to fly
- Harnessing secure
- ELRS RXâs secure.
- Video System harnessed & Checked
Embedded Flight Software
- Pegasus Ardupilot Configuration complete
- VTX Mux configured (even if NCâd)
- Ardupilot OSD connected & Functional
- Mission objectives clear
- Ground following clear
- Understanding of how to tune obstacle avoidance systems
- Arduino tracking antenna tested
Autonomy
- LTE telemetry ready
đ« 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 # (opt) | Sub-team | Driving | Role | |
|---|---|---|---|---|---|
Director | toyota prius | ||||
Director | 5-pass sedan (smol) | ||||
Mech | Caravan | ||||
6472074122 | electrical | checking harness & debug Gemini if needed | |||
EFS | flight test coord | ||||
EFS | |||||
EFS | Testing OSD and VTX |
This section and remaining to be filled out by FTC and Flightline Team
Flightline Team
Name | Phone # | Role | Reason |
|---|---|---|---|
Pre-Flight Preparation
Checklists
Incident Procedures
Weather
Light chance of rain, sunny, and above 0.
Potential chance of steady wind & gusts up to 30+km/h.
âČïž Flight Test Timeline
Date/Time | Action | Notes |
|---|---|---|
0700 | Start charging batteries 4x 6s 5000mah (pegasus) 3x 3s 4000mah (houston) | |
0930 | Final flight inspections | |
1000 | Briefing @ WARG Bay | |
1015 | Begin loading vehicles | |
1030 | Arrival at Flight Test Location | |
Card 1-1 | ||
Card 1-2 | ||
Card 1-3 | ||
Card 1-4 | ||
Card 2-1 | ||
Card 3-1 | ||
Card 3-2 | ||
Packup | ||
Debrief | ||
0200 | We outta here bois | |
11:40 | Flight test plan (Pegasus) Misson 2 - Arm & take off time | |
11:43 | landing | |
11:48 | Mission 3: arm and take off | |
11:52 | disarm and land | |
12:09 | Mission 4 (Test VTX and OSD): arm and take off | |
12:11 | disarm and land | |
12:19 | Houston flight test mission 1: arm and take off | |
12:21 | disarm and land | |
12:22 | Mission 2: Testing with box obstruction: arm and take off | |
12:22 | disarm and land | |
12:23 | Mission 3: arm and take off | |
12:25 | crashed into obstacle and disarm | |
12:28 | Mission 4 (increased distance) : arm and take off | |
12:29 | disarm and land | |
đ» DEBRIEF
LTE issue from last weekend (noise??) fixed! - flying very fast did not cause dropout. LTE antenna on leg of peggy.
VTX and OSD function
Pink controller arm switch working
Flight line communication good
Tested gemini on houston (worked) (but no link stats)
Obstacle avoidance on houston worked but not great
once it clipped the bins
Forgetting parts at the bay: VTX antenna & connectors
ardupilot configs not set beforehand
for RFDs
for OSD
for removal of OFS on Pegasus
VTX harness was scuffed
used breadboard jumper wires and electrical tape: loose
Houston would tip and propstrike the ground on several landings
360 lidar was late to prepare, was being screwed on morning of test
Particular RPM causes drone to shake pretty hard, not very detrimental, it just has to be throttled past in order to avoid.
Possible chance of power line clipping - we were 50 meters up and nearly BVLOS, not sure if we were going to clip trees or power lines in the distance
LTE dropouts on pegasus again
suffers when 1.3 GHz video transmitter is on.
either separate the antennas, use different freq, or find another video solution.
mount on opposite sides of the drone? or try 5.8 GHz video
Houston difficult controls.
tipped, shook, ran into bins,
drifts in a large radius in loiter
had a medium hard landings a couple times
landing houston in wind was very hard: needed to angle very hard, risk of propstrike and tipping very high
hit angle limit on pegasus (30 deg) so never hit the top speeds
Did not mount VTX on drone for flight test
Tracking antenna did not work
Action items
Get the max weight of houston to mechanical for new landing gear design
more stable to avoid tipping
Update angle limit and re-run max speed
try landing on landing pads with current FPV setup: need mux harness and second camera harness prior
VTX range test
configure OSD better
change from icarus config
fix the âturning on and off in the airâ problem
get link stats between gemini and the drone forwarded to logs somewhere
buying pre crimped wires to build a proper VTX harness
Weathervaning
figure out obstacle avoidance parameters/setup on houston
get new batteries
hit 70 amp current draw at one point
indicates battery health bad
document OA parameters and how it translates to behavior. Anthony Luo to look at this
clean up harnessing on pegasus:
shorten all the cross wires
clean up all little wires too
Analysis
logs are uploaded, donât need much analysis on them
Vibe
Pegasus generally shows good vibration means, near 10 in all axis. (where 10 is essentially perfect). Comparing against vanguard shows worse vibe performance in some instances, but not to a significant degree.
Houston showed incredibly bad vibration, likely due to chipped propellers.
Attitude Control
Wind was estimated to be around 20-40km/h, the highest winds weâve flown Pegasus in to-date. Attitude control performance on roll and pitch axis are excellent, even given the higher vibe.
Current Draw
During card 2 - 1, multiple missions were run. On average, when flying at full speed forward, we were limited by our MAX_LEAN_ANGLE of 30 degrees. At this angle, our average current draw is visually observed to be around 80Amps.
Efficiency
Snipping from sections where Pegasus was at maximum or near-maximum forward velocity, we are able to calculate efficiency in mah/km using the following formula:
BAT.Curr[A] * 1000. [mA/A] / GPS.Spd [m/s] * (3600[s/h] / 1000 [m/km] ) --> Eff[mAh/km]
Average efficiency at high-speed shows somewhere between 700-1000 mah/km
Assuming battery capacity of 4*6000 = 24000 mah, this means we expect to be able to run 24km at 15m/s = 55km/h, giving us ~ 8 laps in ~26minutes. This is perfect assuming we get a 30 minute flight windowâŠ.