Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Sections for requesting team to fill out:

  • Admin preparation

  • Test Cards / Test Plan

  • Mandatory Attendees

Sections for flight test coordinator to fill out:

  • Flightline team

  • Location

  • Status

  • Drone

Sections for flightline team to fill out:

  • EFS to fill out flight test cards

đź“‹ Admin Preparation

Your status should read “submitted” when you submit the FTR to our Flight Test Coordinator.

Once the coordinator approves, and a date/location/drone has been assigned, the status will change to “waiting for sub team review”. Once all sub-teams have reviewed and signed off, the status will change to “approved”

Requested By

Megan Spee

Sub-Team Review

(To be checked once reviewed by sub-team representative)

  • Mechanical
  • Electrical
  • EFS
  • Autonomy
  • Operations

Date of Request

2024-03-16

Goal Summary

  • Pegasus Video transmission with different antenna placements, using 5.8GHz

  • OSD configured and MUX functional for front and downwards cameras

  • OFS configured correctly

  • Autolanding on houston functional

Status?

WAITING FOR SUB-TEAM REVIEW

Desired Airframe

Pegasus
Houston

Location + Time

WrestRC

🥅 Testplan - to be filled out by requesting team

Create ONE table per test-item. Eg: “Landing pad images over asphalt”, “landing pad images over grass”, “landing pad images over grass, high” should all be unique tables.

Use each expand to capture one series of tests, eg “Landing pad detection” or “Auto-tuning”.

 Card 1: Pegasus VTX testing

Video muxing w/ at least 2 cameras. Ideally 3: 1 front, 1 bottom (monster mount), 1 bottom (cabin)

Test #1: Pegasus VTX, LOS low speed & hover performance

Procedure

Goals / Objectives

Failure criteria

  1. Takeoff manually in Loiter, verify that video is stable during takeoff.

  • Ensure that video signal is maintained during close-range takeoffs.

  • Ensure hover doesn’t negatively impact video switching

  • Ensure OSD elements are correct

Loss of Video Transmission

  • Stop drone movement, attempt to re-establish video link.

Loss of Control

  • Land the drone as soon as possible

Loss of Orientation

  • RTL

Battery

  • Land, RTL if possible.

  1. Attempt switching video sources

  1. IF CONFIGURED: attempt switching OSD screens.

  1. Fly slow passes at varying altitudes / distances (pilot discretion) from the ground station

  • Ensure that video signal is maintained during different maneuvers

  • Ensure that different video sources are functional during different passes

  1. Land normally

 Card 3: Houston obstacle avoidance

Test #1: Auto Mission

Procedure

Goals / Objectives

Failure criteria

Necessary Preparation

Explain what capacity you need, what needs to be mounted, etc.

Mechanical

  • Pegasus cleared to fly (mechanically)
    • sensor mount ready
    • Motors + frame rigid
  • Houston cleared to fly (mechanically)
    • sensor mount attached
    • arms + plates rigid

Electrical

  • Pegasus cleared to fly (electrically)
    • harnessing secure
  • Houston cleared to fly
    • Harnessing secure
    • ELRS RX’s secure.
  • Video System harnessed & Checked

Embedded Flight Software

  • Pegasus Ardupilot Configuration complete
    • VTX Mux configured (even if NC’d)
    • Ardupilot OSD connected & Functional
  • OFS configured
  • Mission objectives clear
    • Ground following clear
    • Understanding of how to tune obstacle avoidance systems
  • Arduino tracking antenna tested

Autonomy

  • Test Pathing code on Pegasus (because Pegasus has LTE HAT)
  • Test auto landing on Houston

đź«‚ 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 # (opt)

Sub-team

Driving (question)

Role

Megan Spee

Director

toyota prius

Nathan Green

Amy Hu

Autonomy


This section and remaining to be filled out by FTC and Flightline Team

Flightline Team

Name

Phone #

Role

Reason

Pre-Flight Preparation

Checklists

 Week-Before & Day-Before checklist
  • Motors Tested (directions)

  • Propellers Checked

  • VTX System E2E Checked on Pegasus

    • VTX system works

    • Camera switching works

    • Ground station relay works

    • All monitors & Goggles Work

  • OSD config’d

  • OFS config’d

Incident Procedures

Weather

⏲️ Flight Test Timeline

Date/Time

Action

Notes

730

Start charging batteries

4x 6s 5000mah (pegasus)

900

Final flight inspections

930

Briefing @ WARG Bay

945

Begin loading vehicles

1015

Arrival at Flight Test Location


đź’» DEBRIEF

Logs: https://uofwaterloo-my.sharepoint.com/:f:/g/personal/uwarg_uwaterloo_ca/EprwSfOtGeZOom-fAK63e0gBZ2c94HDJ8xIIYBWXcJXheg?e=hJEmC2

Media Ingest: https://uofwaterloo-my.sharepoint.com/:f:/g/personal/uwarg_uwaterloo_ca/EqjTFLI7eSZHil5CgZ13PYMBk9KPlNMFPESkOseTALivzg?e=tapYW3

Action items

  • No labels