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)
This should also include the flight path where applicable
Subteam action items (for flight readiness)
Transportation logistics finalized
Booking SDC vehicles
Assigning drivers
Renting any needed equipment (trailer? generator? etc.)

Day-Before To-Do List

SDC Vehicle key collected (if required)
Batteries Planned for (DON'T LEAVE CHARGING OVERNIGHT)
Drone batteries & spares
Transmitter batteries
Battery tester/indicator
On-site kit together
First Aid Kit
Ground station / Laptop
Antenna / Receivers
Transmitter
Extra Water
Power cords / Extension cables
Wrenches
Allen keys
Knives
Tape
Rope/string
Zip/Velcro ties
Radios
Safety goggles
Fire extinguisher
Spare foam
hot glue gun w/ hot glue stick
harnesses
Airfame assembled
ESCs/flight controller wired
Radio equipment tested
Channel mappings
Flight modes
Motors tested
Wiring secured (Harnessing)
End-to-end test (neglecting props)
Check the center of gravity
All components not on the airframe that are required should be in the flight box (e.g. props & prop nuts)
Airframe payload
Spare parts
Props
Airframe components (landing struts, arms, etc)
wings nuts
prop nuts
any detached components such as angle mount
props for other aircrafts such as Houston
Hardware to assemble these components
Electronics
ESCs
Motors
Flight controllers
Receiver
Flight Code Flashed
Ground station Software updated

Pre-Departure Checklist

Confirm the Raspberry Pi is securely attached to the drone.
Confirm the image collection software runs when the Raspberris powered on.
Take the WARG laptop, CamLink, HTMI cable, key board and mouse.
Take the WREST RC entrance card
Grab Pre-departure Items
Battery charger and associated cables(30tx to 60tx)
Check battery status
Charge if required, otherwise place into flight box
Systems test
Check flight controller orientation
Check motor spin & rotation direction
Check transmitter mappings
Verify communication links (VTX/RX, Controller, Groundstation)
Verify the mission planner is logging data
Only attach props directly before flight (keep off at all other times)
Get snacks
Mission Briefing
Read the flight plan to the team (that was made a week ago)
Purpose of flight
Plan of action
Success criteria
Delegate and brief on flight line roles
Safety Briefing
Key flight characteristics to observe
Key system characteristics to observe
Measurements to be made

Pre-flight Safety Checklist

Air Frame
Check all antennas, ensuring they are secure and in good condition
Check the battery emplacement and secure attachment and ensure there are no cracks
Check that all lights are operating normally
Check that all sensors are secured and clear of any obstructions
Check that the GPS is receiving satellites and providing a navigation solution
For fixed wing aircraft, Check:
Wings, ensuring they are securely attached to fuselage
Wing leading edge surfaces
Top and bottom of wing surfaces
Wing tip surfaces
Read of wing and all flight control surfaces for freedom of movement, security and any skin damage
For rotary aircraft:
Inspect top and bottom of air frame arms for cracks, loose parts, or signs of damage
Check fluid levels and ensure no leaks if applicable
Control Surfaces
Ensure Elevator moves correctly
Ensure Ailerons move correctly
Ensure Rudder moves correctly
Landing Gear
Check landing gear is secure
Inspect skids or wheels, especially attachment points
Power plant
Cowling or motor casing
Security of engine mounts
Presence of any cracks
All wiring and connectors, ensure no cracks, loose connectors, or chaffing
Propellers / Rotors
Ensure propeller is secured
Check for nicks, chips or cracks
Ensure prop direction is correct
Batteries
Inspect to ensure there is no signs of swelling, external leaking or other defects
Battery wiring and connectors from the battery are connected securely
Batteries (and spares) are adequately charged
Wires are not pinched
Control Station / Receivers / Transmitter
The battery and spare batteries if required are adequately charged
Control Station device and cables are properly connected and functioning
All flight interfaces are functioning normally
Safety
Good visibility and safe wind speed
Surrounding is free of obstacles
Crew far from drone
General Site Survey
Are there other people on the property
Ground Recording / drone footage on
Autopilot
Control surfaces respond to autopilot in the correct manner
Transitions between flight modes have expected effect
Return-to-home systems, if present, have been configured

Post-Flight Checklist

Item

Owner

Item

Owner

Use Flight-Post Mortem to Debrief

ALL MEMBERS PRESENT

Discard of damaged batteries

 

Discharge used batteries for better longevity

 

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

  • ,

  • the place we are flight test has dangerous young driver that almost killed us jk

  •  

RCA for Red Items

Create a RCA and keep it as a child page.

 

Action Items

Other Resources

Booking WRESTRC Field

WRESTRC