July 23, 2023 Flight Test
- Hardy Yu
- Mark Do
- Arunav Munjal
Make sure to update the Title following the format “Jan 01, 2020 Flight Test”
Flight Preparation
Requested by: | |
|---|---|
Required Sub-teams | Mech Electrical EFS CV Operation Sys-Int |
Requested Date | Jan 25, 2023 |
Location and Time | @WRESTRC from 12 - 6 pm |
Summary & Goals | Test QR mission planner integration & autotune an pitch/roll & potentially first milestone of ZP3.5 |
Approved? | Yes / Pending / No |
Required Persons During Test
Name | Phone # | Role | Reason |
|---|---|---|---|
@Anthony Luo |
| Flight Test Lead |
|
@Anthony Luo @Megan Spee |
| Pilot in Command |
|
|
| Safety |
|
@Tong Zhang @Mark Do @Rosanne Zhu @Arunav Munjal |
| Autonomy Rep |
|
|
| EFS Rep |
|
@Nathan Green |
| Mech Rep |
|
|
| Ops Rep |
|
Other Attendees
Name | Role |
|---|---|
|
|
|
|
Drivers & Seat Arrangement
Driver | Vehicle Type | Passenger |
|---|---|---|
@Anthony Luo | SDC RAV4 |
|
@Megan Spee | 5 seat |
|
|
|
|
Success criteria
Tests | Success Criteria | Requirements | Outcome |
|---|---|---|---|
CV camera footage logging |
|
|
|
QR code mission planner integration |
|
|
|
Autotune on pitch/roll |
|
|
|
ZP3.5 first milestone check |
|
|
|
Testing Timeline
Date/Time | Action |
|---|---|
| Aircraft Assembly If aircraft assembly is complicated, outline dates of various milestones that should be met to ensure we don't rush to complete work at the last minute. |
| Pre-flight Preparation Feel free to not come at 9 if you don’t have a lot workload. During this time get snack if needed |
July 23, 10 am | Required persons for preflight preparation show up at bay Flight test lead breifly assign task for preparation work |
July 23, 11:30 am | Flight brief from flight test lead |
July 23, 12 pm | Loading onto the Car Take your water bottle with you. Go washroom before we leave! |
July 23, 1 pm | Drive to the test ground |
July 23, 1-2:45 pm | Flight Testing |
July 23, 3 pm | Debrief |
Aircraft Incident Procedures
Incident | Procedure |
|---|---|
Crash | Outline the procedure for who will go to handle the aircraft in the event of a crash, what should be done, were emergency equipment is, etc. |
Flyaway | Outline the procedure for flyaways. List relevant contact information for local authorities and plans of action to recover control of the aircraft |
Configuration Error | Outline steps to take in the event of a configuration issue with the aircraft |
Injury |
|
Property Damage |
|
Week-Before To-Do List
Day-Before To-Do List
Pre-Departure Checklist
Pre-flight Safety Checklist
Post-Flight Checklist
Item | Owner |
|---|---|
ALL MEMBERS PRESENT | |
| |
|
Flight Test Post Mortem
Required equipment to
WARG Laptop (w/ CAMLINK and OBS) or preferably a portable monitor
HDMI cable, USB Splitter, Mouse and Keyboard
Before 1st Test Flight:
Plugged in HDMI into Jetson from Laptop & used OBS to view jetson screen
This is harder to use than if a monitor was connected directly, since OBS had input delay & poor cropping / solution
Plugged in Mouse & Keyboard into Jetson to get to command line
Checked to make sure that run.sh was enabled
Checked to see that SD Card was being logged onto
Rebooted Jetson
1st Test Flight:
SD card did not store any footage
Between 1st and 2nd Test Flight:
Checking Jetson after 1st test flight found that run.sh execution on startup was disabled (even though this was specifically enabled before test flight #1
Re-enabled run.sh to run on startup
Rebooted Jetson
Checked the Jetson’s file system to see that SD started logging footage again, meaning run.sh successfully executed on startup after this most recent reboot
Left Jetson as is for the 2nd Test Flight
2nd Test Flight:
CV Camera successfully logged footage to SD card
Video more purple than previous flight test, which led to poor landing pad detection model performance
Video Logged Successfully
Need to re-tune the CV camera to remove the purple hue
RCA for Red Items
Create a RCA and keep it as a child page.
Action Items
Other Resources
Booking WRESTRC Field