2023-10-28 Flight Test

Owned by Amy Hu, created
Last updated: 2023-10-28 by Mena Azab
5 min read

 

 

FTC: Make sure to update the Title following the format “2020-01-30 Flight Test”

 Flight Preparation

Requested by:

Required Sub-team integration efforts

Mech
Electrical
EFS
CV
Operation
Sys-Int

Date of Request

Oct 25, 2023

Location and Time

 

Goal Summary

Landing pad images collection with Houston for software settings finalization.

Approved?

Yes / Pending / No

 Mandatory Attendees

Name

Phone #

Role

Reason

Name

Phone #

Role

Reason

 

 

Flight Test Director

  • Creating documentation

  • Booking the test flight

  • Creating a thread in #flight-staging

  • Responsible for coordinating operations from start of brief to end of de-brief

 @Hardy Yu

 

 

Ground Station Operator

  • Aircraft preparation

  • Filling out documentation

  • Operation of aircraft

  • Coordination between mission plans

 

 

Safety

  • Making sure everyone is safe

  • Bringing Med kit

  • Incident procedure

@Amy Hu

 

Autonomy representative

  • Review landing pad images and update camera settings.

@Mihir Gupta

 

Autonomy representative

  • Review landing pad images and update camera settings

 Auxilliary Attendees

Name

Role

Name

Role

Daniel Puratich

Electrical Support

Flight Test Logistics/Director Support

Tc basic

Availability: morning only until 11:30am.

David Wu

AUTO-ML team member

Saturday Morning until 12 pm

@Rosanne Zhu

AUTO-ML team member

@Vibhinn Gautam

AUTO-ML team member

Drivers & Seat Arrangement

We took public transit to get to the flight test location.

Driver

Vehicle Type

Passenger

Driver

Vehicle Type

Passenger

 

 

 

 

 

 

 

 

 

Goals/Objectives

Objective

Priority

Owner(s)

Objective

Priority

Owner(s)

Test raspberry pi 3 on Houston

 

Autonomy

Collect landing pad images and update camera settings

 

Autonomy

Flight Test Timeline

Date/Time

Action

Date/Time

Action

10:30

Member arrive @ WARG Bay

10:50

Briefing @ WARG Bay

11:30

Arrival at Flight Test Location

12:00

Flight Test Operation #1: Tested houston auto mission, RPi not plugged into drone

  • We didn’t connect RPi since we wanted to first ensure that Houston was successfully able to run an auto mission and see where it went so we can position landing pads accordingly.

12:45

Flight Test Operation #2: Ran Houston with auto mission, RPi plugged in and used camera settings in run.sh scripts. Collected and saved images.

  • We powered the RPi and started to collect images while the drone is in flight. Noticed that the images were very purple.

1:30

Flight Test Operation #3: Ran Houston with auto mission, RPi plugged in and used default camera settings. Did not save images @Amy Hu do you know the reason why.

  • Powered the RPi and collected images but noticed that it didn’t collect images.

2:00

Flight Test Operation #4: Ran Houston with auto mission, RPi plugged in and used default camera settings. Collected and saved images.

  • Powered the RPi and collected images. Noticed that images looked more normal.

2:30

Flight Test Operation #5: Ran Houston with auto mission, RPi plugged in and used new camera settings. Collected and saved images.

  • Powered the RPi and collected images. Noticed that images were more purple with the new settings.

3:30

Debrief

 

 

 

 

Incident Procedures

Incident

Location

Procedure

Incident

Location

Procedure

Crash

WRESTRC

  • Identify last known location & flight path of the aircraft

  • Divide into teams of 3 and decide on communication protocol

< otherwise >

 

Flyaway

 

Outline the procedure for flyaways. List relevant contact information for local authorities and plans of action to recover control of the aircraft

Fire

WRESTRC

  • Designate 911 contact

  • Describe incident (Drone crashed, contains LiPo batteries)

  • Give location of team (Skid pad at the Waterloo Region Emergency Services Training Center)

  • Give best approximation of the location of the drone

< otherwise >

 

Injury

 

  • Apply first aid as required.

Property Damage

 

 

Week-Before To-Do List

Raspberry Pi 3 can collect images with the $200 CV Camera
Test the imaging repository with the Raspberry Pi and confirm images are taken and stored on the SD card with a SD card reader
Edit the rc.local and ensure that image collection code runs on Raspberry Pi startup
Raspberry Pi can be powered onboard the drone. Need help from the Electrical team.
Raspberry Pi and $200 CV Camera are mounted onto Houston. The $200 CV Camera needs to be pointing in the downwards direction.. Need help from the Mechanical team.
Drone Registration

Drone Registration Number:

Flight test location booked
Pilot scheduled
Test Plan (What we are testing)
Subteam action items (for flight readiness)
Transportation logistics finalized

Day-Before To-Do List

Pre-Departure Checklist

Pre-flight Safety Checklist

Post-Flight Checklist

Item

Owner

Item

Owner

ALL MEMBERS PRESENT

 

 

Flight Test Debrief

Flight Test Timeline

Analytics (hopefully applicable)

Flight Test Post Mortem // Final Thoughts // Condensed Summary

  • Houston successfully flew with automission to complete the camera video logging

  • Multiple camera logging were collected with different filter

  • We didn’t crash

  • image rep worked, tested different functions

  • We did a lot of automissions

  •  

  • uploading the waypoints should be done wirelessly

  • battery failsafe after takeoff for unknown reason, might be hardware issue

  • plugging usb devices to rpi is a hassel, might need mechneism to help on this process

  • failed takeoff for multiple times because of missing the waypoints information, tho the waypoints upload was done

  • the weather is cold, wear warm

  • we could coordinate ppl better so extra ppl can has something to do instead of being bored

RCA for Red Items

Create a RCA and keep it as a child page.

 

Action Items

Other Resources

Booking WRESTRC Field

WRESTRC