Versions Compared

Key

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

Attendees

Agenda

  1. Reviewing requirements, points breakdowns, and assembling the list of questions

  2. Determining Strategy

  3. Setting timelines and integration milestones

Table of Contents

Brief Points breakdown


Phase #1 Scoring Criteria

Points

% of max

Expected?

Quality

15

15%

System Capabilities

50

50%

Technical Innovation & Novelty

25

25%

Project Management

10

10%

Total

100

80

Info

We are looking to absolutely demolish phase #1 paper here.

Phase #2 Scoring Criteria

Points

% of max

Expected?

Presentation

40

12.5%

Prototype Realism Review

40

12.5%

Task #1

100

32%

Task #2

100 + bonus

32%+bonus

Flight preparation

30

9.375%

Report

10

3.125

Total

320+bonus

=360

~260

Info

What score are we looking for here?

Requirements Review + Questions assembly


Expand
titleEXAMPLE REQUIREMENT

< rule / point distribution / importance >

< explanation >

Hard Requirements

Non-negotiable “we must have these if we want to meet our target”

Expand
titleDrone can fly

In progress, not done flight test yet. bench power on successful

must be able to fly up to 200m

must be electric propulsion

Expand
title< 15 kg

On track. Limited to <7kg with motor/prop combo

Expand
titleSeats
  • at least 4 seats

Expand
titleCargo
  • up to 4 5x5x10(cm) cargo blocks up to 500g total

Expand
titleLanding gear
  • yup

Expand
titleVisible Sponsor Logos
  • Internal warg requirement

Expand
titleKillswitch
  • Must have way to descend at 2m/s

Expand
titleElectrical/Mechanical motor lockout
  • Motors can’t run when someone is working on the drone

Expand
titleWe need to know position of the drone
  • rpas + autonomous nav

Expand
titleCompetition GPS mount
Expand
titleMust maintain RC or Telem link with drone
  • must killswitch otherwise (cannot fly gg)

  • must be able to communicate up to 200m height

Expand
titleReady button
Expand
titleAdvanced RPAS licence
  • For the pilot/gso

Expand
titleHAM Licence
  • needs to exist

“Soft” Requirements

negotiable “we can add these in and it will increase our performance if it’s possible. May revisit these as we talk about strategy”

Expand
titleSeats
  • Cushiony

  • restrain passengers properly

Expand
titleCabin stuff
  • Windows

  • Nice looking interior

  • separate cargo/passenger cabin

  • WARG Logo on drone

  • stairs / way to get barbies in to drone

  • way to secure cargo

  • comfortable

  • safety measures

  • no exposed wires

  • Accessibility?

Scoring metrics

  • Table 3 & Table 4

  • ~ 30 points (rough estimate)

WARG Internal

  • easy to remove/swap (two airframes)

  • Weight limit

Expand
titleAirframe
  • Aerodynamic (or at least aerodynamic looking)

  • Fly for a long time (30 or 45 minutes)

    • Window depending // assigned day of

    • allowed to swap batteries through task #2

  • Light

    • lightest drone gets most points

  • Sponsor logos

  • Weatherproofed/proof-able

    • not hard requirement, can scramble it.

Scoring Metrics

Expand
titleAutonomous flight

Task #1 flying laps autonomously [20 pt total]

  • could modify pathing repository?

  • able to upload waypoints

    • fly within 10m of first waypoint,

    • subsequent laps no altitude restriction and must not cut through waypoints.

Task #2 [20]

  • Ability to detect & land on landing pads

    • only needs to land in the landing zone?

      • rotors stopped for 15 seconds

  • fly within 5m of waypoints/approach centerline (incl altitude).

Expand
titleSensors
  • Accurate position/alt data

  • FPV cameras (for pilot/monitoring)

  • don’t hit things while flying / landing

  • 200$ cv camera (obj detection)

Expand
titleFlightline
  • Checklists

  • organization

Open Questions / Clarifying questions

Expand
titleX (size) of LZ
  • We do not know them gg

Expand
titleTask #1: What constitutes a lap
  • how far around each waypoint, etc

Expand
titleFRR: Is realism a scale or can multiple max out the points there
  • How hard do we need to try?

Expand
titleATC Interaction: Are there points for doing that autonomously, or done through human interaction?
  • title

Question: In 18.c., is the vehicle allowed to cross the centreline between the 2 waypoints?

Question: In 18.c., does “outside the waypoints” mean past a line perpendicular to the line segment connecting the 2 waypoints?

Question: In 18.d., how close to the takeoff point does the vehicle need to land (i.e. what is the acceptance radius)?

Question: In 18.d., is it correct to assume that once the vehicle is landed, the lap count is final (i.e. cannot land at takeoff point, then take off again)?

Question: In 18.f., what is the maximum height of the obstacles from the ground (i.e. building and containers)?

Question: In 21.f., which side of the landing pad will be facing upwards (i.e. blue only, orange only, or possibly both)? Are the landing pads the same from the 2023 Student UAS Competition?

Question: In 21.a., will we be able to synchronize our clock with the official clock?

Question: In 21.a., is the vehicle allowed to finish the approach early and hover over a landing pad until the start of the landing time window?

Question: In 21.g., how close to the landing pad does the vehicle need to land (i.e. what is the acceptance radius)?

Question: In 21.g., does crash landing onto the landing pad count as landing (e.g. vehicle hits a wall and then crashes)?

Question: In 21.g., when is the vehicle landing time taken? For example:

  • The moment it touches down (confirmed when the rotors are stopped for 15 seconds).

  • 15 seconds after the rotors stop (so the vehicle should touch down at least 15 seconds before the end of the landing time window).

  • Landing completed reported to ATC (confirmed by judges to have actually landed).

  • Something else?

Question: In Table 6, under Time, are the deductions for discrete increments of 30 seconds or continuous (e.g. 0.2 point deduction for 3 seconds)?

Question: Are we allowed to survey the landing areas prior to the competition?

  • We would be looking for if we could update our satelite imagery.

Strategy


Task #2

Criteria

MAX

Expected

Approach

20

20

Autonomy

  • 5pt takeoff

  • 5pt waypoints

  • 10 pt landing

20

10 (drop landing if it fails?)

Landing

  • Null = 0

  • A = 30

  • B = 45

  • C = 70

70

70?

Landing time window

20

20

Communication

10

10

Sum

140

130?

  • Takeoff

  • Approach is known

    • Need to report to ATC what you are doing

  • Landing

    • LZ C is behind shipping containers.

      • pretty confident that 800mW will go through?

        • background noise not the same as what exists at the airport

    • will need video & sensor transmission through that.

      • LTE should work?

      • could possibly use rangefinders which give distance buffer

    • 2023-09-24

      • attempt sending video over LTE.

      • rm jetson from airside (weight saving).

      • integrate code from task #1 to give instr. from groundside.

    • Attempt LZ C. half time autonomously. pilot takeover on back half

  • Communication

    • flight dir to call out.

Task #1

Criteria

MAX

Expected

Time

15

7.5?

Distance

30

15?

Empty Weight

10

??

Autonomy

  • Takeoff: 5

  • Waypoints: 10

  • Landing: 5

20

20

Landing

5

5

Passenger & Cargo Security

  • Passengers in place: 10

  • Cargo in place: 10

20

20

Total

100

45?

  • Takeoff

    • Waypoint #1 @ 200m height

  • Distance

    • Lots of system characterization & determining a glide slope//descent slope?

    • Flying forward a lot…

    • Likely want to run motors near peak efficiency (pinning it likely not to be best case)

      • depends on how long we expect battery to last. Needs lots of flight testing

    • Total dist. for a lap is 3km

    • potentially fly some radius around the waypoint

  • Empty Weight

  • Autonomy

    • very doable should get max points

    • Time / voltage based?

  • Landing

  • Passenger & Cargo security

    • Cannot be shifted

Notes:

  • no points for passenger comfort

    • keep in mind “would you get in this” (might be pre-flight only)

Action items

  • Anni to look at rangefinder support + weight options

Mechanical

  • Cabin development

  • Slowly reduce weight of 3d printed stuff

Electrical

  • Look at custom power distrib pcb (instead of thick wires)

  • Evaluate use of xt90’s / connector usage

  • Shorten cable runs?

EFS

  • meet with anni to see what we can do

Autonomy

  • RM Jetson

  • Inference on ground

  • Digi vid through rpi w/LTE telem.

    • breakout on ground to mp & inference.

  • Evaluate how to bring desktop & breakout video

    • CV camera for rpi

Flight Test

  • Determine how many batteries we’ll need for flight times

  • efficiency curves, etc.

  • Re-evaluate sensor stacking && what exactly we need.

    • rangefinder/proximity sensors

Change History