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 9 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 Card #1, #2, #3 (Opflow, Tracking Antenna, Obstacle Avoidance)

📋 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

Anthony Luo

Sub-Team Review

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

  • Mechanical
  • Electrical
  • EFS
  • Autonomy
  • Operations

Date of Request

Jan 16, 2024

Goal Summary

  • Pegasus Opflow calibration

  • Pegasus MAGFit check

  • Tracking antenna algorithm check

  • Houston Obstacle avoidance functionality check

Status?

WAITING FOR SUB-TEAM REVIEW

Desired Airframe

Houston / Pegasus

Location + Time

WrestRC 1300-1800

☀️ Wx

https://www.windy.com/station/ad-cykf?42.541,-80.379,8 Waterloo Weather Station

image-20240125-155541.png

🥅 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 OpFlow + Lidar Calibration

Test #1: Opflow calibration

Procedure

Goals / Objectives

Knockoff criteria

  1. Hover altitude <x>

  • Obtain images of <x>

  • Verify colour calibration

  • < anything else you’re evaluating >

< list of reasons why you would want to stop the test >

  1. Begin opflow calibration

  • < Should get some message >

< etc >

  1. Check lidar calibration?

  1. Review test data?

 Card 2: Tracking Antenna Validation

Test #1: straight passes

Procedure

Goals / Objectives

Knockoff criteria

  1. Hover altitude <x>

  • Verify antenna is able to point towards the drone

< list of reasons why you would want to stop the test >

  1. Translation motion:

Move in <pattern>

  • Ensure that the tracking antenna remains pointed at the drone

< etc >

 Card 3: Houston obstacle avoidance

Test #1: ???

Procedure

Goals / Objectives

Knockoff criteria

  1. Hover altitude <x>

< list of reasons why you would want to stop the test >

  1. Translational movement @ slow speed towards vertical wall

  • Ensure that the drone stops at specified distance before the wal

< etc >

  1. Maintain desired movement towards the wall while spinning heading vector 360

  • Ensure that obstacle avoidance continues to track at all angles

  1. Approaches from front/side/rear ascending & descending

  • Basic characterization of obstacle avoidance properties.

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.

Embedded Flight Software

  • Pegasus Ardupilot Configuration ready
    • Opflow → Offsets correct, usage correct ? (EKF3?)
    • Lidar → Offsets correct, usage correct? Height limits set?
  • Houston Ardupilot Configuration ready
    • Failsafes configured (Radio, GCS, Battery, ETC?)
    • 360 Lidar → Configured, ground tested. Distances set properly?
  • Test area SME available
    • Test procedure is clear → Houston & Pegasus
    • Possible deviations from test understood and considered → Houston & Pegasus
  • Software ground tested
    • Ground tests complete on all airframes (on battery over telemetry)
  • Tracking Antenna
    • Tested ? SME ready?
  • ELRS / Radio management correct.
    • ELRS rx’s on houston & pegasus. → Clear unique models.
    • ELRS Airport on houston → Verify functioning.
    • RFD900x on Pegasus → Verify functioning
    • ELRS Trainer → Verify functioning

Autonomy

  • LTE telemetry ready (question)

🫂 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)

 Vehicle Bookings
image-20240125-155241.pngimage-20240125-155246.png

Name

Phone # (opt)

Sub-team

Driving (question)

Role

Anthony Luo

Director

Y - 5pass SUV

Megan Spee

Director

5-person liftback

Nathan Green

Mechanical

Ryan Chan

Mechanical

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

Flightline Team

Name

Phone #

Role

Reason

Megan Spee

Pilot

;/

Anthony Luo

Pilot

Pre-Flight Preparation

Checklists

Incident Procedures

⏲️ Flight Test Timeline

Date/Time

Action

Notes

0700

Start charging batteries

4x 6s 5000mah (pegasus)

3x 3s 4000mah (houston)

0800

Begin checklists

0900

Briefing @ WARG Bay

0930

Begin loading vehicles

1000

Arrival at Flight Test Location

1030

Flight Test Card #1 + 2: Opflow calib.

1030

Flight Test Card #3: Houston obstacle avoidance

1200

Packup

1230

Lunch

1300

Debrief

<>

💻 DEBRIEF

  • No labels