...
| Expand | ||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||
| Expand | |||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||
Necessary Preparation
Explain what capacity you need, what needs to be mounted, etc.
Necessary items:
JetsonRPI
CV camera
< rfd900 >
etc
Lidar
Flight characteristics needed:
Flight speed
flight distance
max altitude
< etc >stability
Comms / Support needed:
...
Autonomous/repeatable missions
...
ability to hold location within +/- X meters
...
...
etc….
🫂 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 |
|---|---|---|---|
8076320853 | Mech | ||
206-247-2823 | Mech | ||
6474256385 | |||
5195898378 | Auto | ||
2896985018 | EFS | ||
6473836886 | Auto | Testing obstacle avoidance | |
2897729826 | Auto | ||
5195917981 | Mech |
...
Flightline Team
Name | Phone # | Role | Reason |
|---|---|---|---|
|
|
| |
...
| Expand | ||
|---|---|---|
| ||
Total 5 main system checked:
|
⏲️ Flight Test Timeline
...
Date/Time | Action | Notes | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
lunch time ish | Briefing @ WARG Bay |
| Arrival at Flight Test Location |
| Experiment with tracking antenna |
| ||||
| Bring equipment to flightline |
| Test1 card 1 | Hardy Yu manually track the drone RTL because RC failsafe | Configure direct binding phrase to use normal controller elrs instead of gemini | |||||
| Test 1 card 1 | Test 2 card 1 practice #1 | ||||||||
| Test 2 card 1 practice #2 | |||||||||
| switch battery |
| ||||||||
Test 2 card 1 practice #3 | Test 2 card 1 practice #4 | Test 2 card 1 practice #5 | Presentation Photos | Start 4:30pm | Debrief10:00 | arrive bay | ||||
12:30 | setup test and get ready to go | |||||||||
12:40 ~1:10 | wait for the weather | |||||||||
1:10 | first take off | |||||||||
1:20 | second takeoff | |||||||||
1:30 | Fixed the prop | |||||||||
1:40 | return to service flight | |||||||||
...
💻 DEBRIEF
Flight test debrief report
Before Card 1:
Before departure
Yuchen Lin didn’t logistic going to flight test → next time book the car beforehand + long weekend machine shop does not open
Yuchen Lin Hardy Yu Testing with huston → connected to mission planner and able to forward the message(test 2 times)
first one does not flash the latest code
second one see tracking antenna working as expected
After departure
pre-flight tracking antenna testing: (no code change)
Keep rotating without stop and does not work
After adjust to the north keep rotating clockwise
does not help after adding delay
Please upload the picture to media digest!!!
updated thanks a lot
Weather is a huge thing
Glad doesn’t risk and fly in heavy rain
Next time plan ahead of time
A prop just break during transportation
suspect overtighten issue
replace one props
Card 1 Test 1
| Info |
|---|
Flight planning
|
Flight test card requirements/objectives Performance
Comp sim
| Panel | ||
|---|---|---|
| ||
Control performance & payload situation
|
| Note |
|---|
Identified issue
|
| Warning |
|---|
Issue need to be RCA
|
Card 1 Test 1 retry 12
| Info |
|---|
Flight planning
|
Flight test card requirements/objectives Performance
Check tuning in all three mode and compass variable at full throttle.
| Panel | ||
|---|---|---|
| ||
Control performance & payload situation
|
| Note |
|---|
Identified issue
|
| Warning |
|---|
Issue need to be RCA |
Card 2 Test 1
return to service
| Info |
|---|
Flight planning
|
Flight test card requirements/objectives Performance
During flight time upload the mission to pixhawk
Arm in auto and complete the mission
Pilot navigate through and land on the pad with fpv goggle
| Panel | ||
|---|---|---|
| ||
Control performance & payload situation
|
| Note |
|---|
Identified issue
|
|
| Note |
|---|
Identified issue
|
| Warning |
|---|
Issue need to be RCA |
Overall performance and Lessons learned
Outcomes
confident in flight characteristics of the drone and electrical robsutness
spline waypoints looked good during flight but looks poor on mission plannre
low confidence in custom rf links and tracking antenna
not using tracking antenna for comp → cc Daniel Puratich to bringup at AEAC
Gemini board was low link quality
try another gemini board and see if it works
Nathan Green apply new mag fit data based on today’s data
Check weather before comp.
Flightline tasks:
bring vtx tower, drone(path uploaded, battery in , shourds on), controller and the monitor
Before takeoff
Daniel Puratich conduct the pre takeoff checklist
manually toggle safety switch
confirm take off flight mode
arm in auto
| Tip |
|---|
Did not risk any valuable component and don’t have any issue with the rest of the system none of the other system got damaged |
| Warning |
|---|
Haven’t finish any objective for the day need seperate session for pilot training flying props are dangerous Need to respec the props |
Evan Janakievski will be available on 27th → next pilot training session time
Update on July 12th:
Smile Khatri Point out during July 6th flight test, The propeller normally come with a black ring at the bottom of the prop. The reason for the prop failure is that the ring was not installed, and when the motor spins, stress accumulates across the injection moulding edge. [need mech clarification]
Smile Khatri Can you add a photo of the black ring? thanks
The second lesson we learned is that Loctile is not suitable for a prop and might damage the prop. Also, it takes a long time to solidify, so if we use Loctile during flight test, it does not have any effect.