Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Tip

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

...

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

 

 

 

...

Date/Time

Action

10:30

Member arrive @ WARG Bay

10:50

Briefing @ WARG Bay

11:30

Arrival at Flight Test Location0X00

12:00

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

12:45

Flight Test Operation #1…… (eg: Capturing data, tuning, etc)

Flight Test Operation #2

Flight Test Operation #…….N

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

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.

2:00

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

2:30

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

3:30

Debrief

🧯 Incident Procedures

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

...

Expand
titlePre-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

...