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 Card #1, #2, #3 (Tracking Antenna, Obstacle Avoidance)
đź“‹ 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-22 |
Goal Summary |
|
Status? | WAITING FOR SUB-TEAM REVIEW |
Desired Airframe | 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”.
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
- Cabin is mounted
- EFS to set the surface area in Ardupilot of the front of the drone - get surface area from Mech CAD
Electrical
- Pegasus cleared to fly (electrically)
- harnessing secure
Embedded Flight Software
- Pegasus Ardupilot Configuration ready
- Opflow → Offsets correct, usage correct ? (EKF3?)
- Lidar → Offsets correct, usage correct? Height limits set?
- set the surface area in Ardupilot of the front of the drone - get surface area from Mech CAD
- Test area SME available
- Test procedure is clear → Houston & Pegasus
- Possible deviations from test understood and considered → Houston & Pegasus
- Software ground tested
- Ground tests complete on all airframes (on battery over telemetry)
Tracking Antenna- Tested ? SME ready? ground test only not in the flight test
- ELRS / Radio management correct.
- ELRS rx’s on pegasus. → Clear unique models.
- RFD900x on Pegasus → Verify functioning
- Radio Management
- Flight mode channel configured as channel 12 on both radios.
- Arm/Disarm sequences checked & ready
- Updated to latest EdgeTX if possible?
- Radio models cleaned up // labels cleaned up.
- For the same drone, possible to have two models, but labelled differently for different pilots
- Ensure pitch/roll/yaw NOT reversed in-radio on any controller.
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 | FT director/pilot | ||
3-274 Caravan | ||||
3-196 Rav4 | ||||
Ops | ||||
Mech | ||||
EFS | ||||
EFS | ||||
EFS |
This section and remaining to be filled out by FTC and Flightline Team
Flightline Team
Name | Phone # | Role | Reason |
---|---|---|---|
Pilot | je suis | ||
GSO | |||
Pre-Flight Preparation
Checklists
Incident Procedures
⏲️ Flight Test Timeline
Date/Time | Action | Notes |
---|---|---|
7:30/8 | Start charging batteries 4x 6s 5000mah (pegasus) | |
9:30 | Briefing @ WARG Bay | |
9:50 | Final flight inspections | |
10:00 | Begin loading vehicles | |
10:30 | Arrival at Flight Test Location | |
10:50 | Flight Test Pegasus | |
12 | Packup | |
Lunch | ||
1:00 | Debrief | |
<> |
đź’» DEBRIEF
Timeline:
Leaving the bay: 10:16 AM
Arrived at flight test location: 10:35 AM
Take-off time (autotune 1): 10:41 AM
Take-off time (autotune 2): 10:46 AM
Take-off time (autotune 3): 10:58 AM
Take-off time (air speed 1): 11:09 AM
Take-off time (air speed 2): 11:18 AM
Take-off time (air speed 3): 11:23 AM
Take-off time (air speed 4): 11:26 AM
Take-off time (air speed 5): 11:28 AM
Take-off time (wind test): 11:39 AM
Drone is still intact
Specific LTE problem from last weekend was fixed (eliminated Zerotier)
Accomplished all tasks in the document
tuned with cabin
trialed airspeed
windspeed stage 1
We have sufficient battery
Role assignments worked
Pegasus can fly up to 18m/s
Good media collected from dji mini 3 pro 🔥
Wind direction identification - it was different at different elevations
Left slightly later than original plan
Procedure for flying an auto mission was not clear/defined
Arm/Disarm switch REALLY INCONSISTENT (worked enough of the time)
LTE telemetry lost at high speeds
Though this was sometimes regained when drone got slower
Analysis
Pegasus did not actually get up to speed on the 160-180 meter straight flight (during the 20 m/s test).
Fastest we can go (demonstrated here, at least:) is 18m/s, giving us 2.7778 minutes per lap at competition (3000 meter lap).
Batteries would die before this.
Theoretically, at 8 m/s, it can fly the entire 30 minute window, and complete 6.25 laps.
no point flying slower thana 8m/s in future tests - this is the lower bound for how much time we have
Seems to be more efficient when you go slower.
will need to test again on a longer flight path (500m) to see actual max speed given a 20 m/s command. At 20 m/s command speed this time, did not finish accelerating.
What we want to get from logs:
EK3_DRAG_MCOEF via https://ardupilot.org/copter/docs/airspeed-estimation.html
efficiency rating for each speed (mahperkm)
Nathan Green looking at getting this stat for each speed
can compare last week’s tune to this week’s tune
Also need to fix the LTE module connectivity issue.
Theories
LTE failure
interference from motors/ESCs
orientation of antenna
Nathan Green troubleshooting this by testing signal strength with different cables, etc