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 29 Next »

Competition

2023-2024 Aerial Evolution of Canada Student Competition

Team

Waterloo Aerial Robotics Group

Technical Director

Anthony Luo

Version

Document Version V. 028 created on . See changelog below for details.

On this page

This page describes the top-level view of the 2024 competition airframe, and contains references to sub-pages with implementation specific details. This page will be finalized as of Nov 6, 2024. Any changes after that point must follow the formal RFC process. Ping Anni for more details.

Please make your RFC using the following link: tbd

Supporting Documents

🗂 References and documentation

 References
  • [Acronyms] Glossary

  • [2024 Competition Requirements]

🖇️ WARG Standards

To future users: Please try and include a VERSION of a document (e.g. “CAD Guidelines V. 17”)

 Mechanical Standards

List of mechanical-maintained standards:

 Electrical Standards

List of electrical-maintained standards:

 Software Standards

List of embedded flight software and autonomy maintained standards:

 External Standards

Standards that are not internal to WARG. Our internally standards always take precedence over this list unless explicitly stated. These standards include:

📐 Architecture


This is the top-level document for the 2023-2024 AEAC competition aircraft “Pegasus”. These documents describe the purpose, function, and decisions made relevant to the design and use of the remotely piloted aircraft. It has been divided into sub-sections (in no particular order) which hope to offer a global overview of the design and implementation of all systems, as well as how they interface with each other.

If you are editing this document, please do your best to add in the changes made into the changelog and ID the version that you are on.

BOM

This lists all of the components that constitute the configuration of a drone that we wish to fly at competition in May 2024. Some parts may be listed as “Optional” (🔍), in which case they will bethey are not strictly necessary for flight but may be useful in improving system performance.

Here, “Quantity” refers to the number which is needed for a functional drone.

Airframe

Part Function

Manufacturer

Part Name & Link

Qty

Notes

Propulsion

Part Function

Manufacturer

Part Name & Link

Qty

Notes

Propellers

T-Motor

MF2211

4 Indiv

2 CW

2 CCW

 Alternatives

May be reasonable replaced with other props of similar size/pitch

Motors

T-Motor

Antigravity MN6007II

4 Indiv

See Motor Selection Subpage

ESC

Advanced Power Drives [APD]

120F3[X]v2

4

 Alternatives

This can reasonably be replaced by any 12S capable ESC that is able to support BI-directional dshot and > 50A continuous

Power Distribution

Part Function

Manufacturer

Part Name & Link

Qty

Notes

Batteries

Turnigy

Heavy Duty 5000mAh 6s 60C LiPo Pack w/XT90

4-6

 Alternatives

Could be reasonably replaced with Li-Ion packs which are properly specced or with similar sized Li-Po packs.

PDB

Advanced Power Drives [APD]

PDB500[X]

1

 Alternatives

Could reasonably be replaced with any 12S capable PDB, or with a wire harness.

Power Monitor

Holybro

Holybro PM02D High Voltage

1

BEC

Mateksys

BEC12s-Pro

1-2

 Optional

The number of BEC uses depends on the number of subsystems that need voltage isolation which are present

Flight Control System

Part Function

Manufacturer

Part Name & Link

Qty

Notes

Autopilot

Holybro

Pixhawk 5/6x + SD Card (logging)

1

 Which one?

The autopilot standard gets revised every so often. The 6x is significantly improved from the 5x, and we recommend it for the competition drone.

 Onboard Sensors

Note that the “Cube” standard has multiple internal sensors, some of which we may list externally for redundancy or performance reasons!

GPS

Holybro

Holybro M9/10N GPS

1 Prim

1 Sec

 Which one?

The M10 is newer & cheaper. We have a lot of M9’s but again, newer GPS’s are better.

 Primary vs Secondary

You’ll notice that you have an option for “Primary” and “Secondary” on the GPS’s. This refers to the wiring of the “Switch” on the gps and the termination of the GPS. With the pixhawk baseboard standard, most systems accept 1 primary GPS and 1 secondary GPS.

Unknown

Future RTK system

 How does RTK Help?

RTK gives more precision, which is always useful when we’re trying to have very precise position hold

Rangefinder 🔍

Benewake

TFMINI-S Micro LIDAR Module I2C

1+

 Semi-Optional

Using a rangefinder is not strictly necessary for any flight mode but greatly improves the accuracy of auto-landing and stability of the drone when hovering close to ground level.

 Quantity

Using (1) rangefinder is the minimum for the system to function, but it is possible to use multiple rangefinders to get better data or to offer horizontal or vertical object detection.

 Alternatives

There are many different rangefinders available. Lidar typically reports least noise and is more accurate over a wider range of circumstances

Optical Flow Sensor (OFS) 🔍

CubePilot

HereFlow

1

 Semi-Optional

The drone will fly in all modes without the OFS, but it greatly improves position hold at altitude.

 Alternatives

ATM, there are multiple supported alternatives but please ensure they function at the same range

Compass 📉

Barometer 📉

Jetson TX2

Fully documented with system requirements in Jetson

Raspberry Pi

RF + Peripherals (grouped because it’s small bits of things)

Part Function

Manufacturer

Part Name & Link

Qty

Notes

Control Link

TBD

ELRS Diversity RX

1

1 of either

WARG

ELRS Gemini

1

Telemetry Link

1

1 of Either

Potentially double up 4 redundancy

Abra Electronics

LTE Hat

RF Design

RFD900x

Video Transmitter

Mateksys

VTX 1G3SE

1 of either

 DISCONTINUED

Most 1.3GHz VTX’s are no longer available due to current political conflicts.

Foxeer

1.2G 5W (Enhanced) 4ch

FPV Cameras

Caddx

Baby Ratel 2

2

OSD

Holybro

Holybro Micro OSD V2

1

 HARD TO FIND

Please be careful

Video Mux

Lumenier

3-Way Multi Camera Video Switcher Board

1

Lighting 🔍

-

-

NAVLights

-

-

Landing Lights

CV Camera

Hupuu

200$ CV Camera

$200 CV Camera

Groundside

Part Function

Manufacturer

Part Name & Link

Qty

Notes

Groundstation Laptop

Lenovo

Thinkpad T490?

1

1.3G Video RX

ReadyMade RC

900-1.3 GHz Receiver w/Tuner

1

5.8G Video TX

AKK

TS832 5.8 GHz VTX

1

RC Control Link

WARG

ELRS Gemini

1

PREF GEMINI WHEN POSSIBLE

RadioMaster

RadioMaster Ranger FCC

1

Telemetry Link

WARG

ELRS Gemini

1

RFDesign

RFD900x

1

LTE Hotspot

1

No manufacturer

Telemetry Relay

Xbee

XBEE Pro 5.8

2

ELRS

ELRS Airport

FPV Goggles

-

Pilot Preference

RC Controller

RadioMaster

TX16s MkII ELRS Mode 2 HALL

2

 Modifications

The blue controller has an INTERNAL elrs rx hooked up to aux trainer so that wireless trainer may be used.

Video Monitor

-

Generic 5.8 GHz Receiver

List of user manuals & references

We maintain an active list of PDF revisions of user manuals, datasheets, and spec reference parts in the event that an externally hosted server goes down or a manufacturer discontinues a part.

Anni still needs to do this!

 Propulsion System
  • Motors - view page 7 (# 187)

etc….

Pegasus Overview

Pegasus is a “heavy-lift” quadcopter designed to serve as a generic quad-rotor platform for AEAC 2024 as well as future competitions. It features standard mounting grids across the entire frame, as well as modular landing gear and easy disassembly of all components for transport or repair.

Below is a summary of system characteristics which are expected of Pegasus

Min

Recc/Avg

Max

Propeller Diameter (in)

20

22

24

Battery Voltage (v)

36

-

50.4

Takeoff Weight

4.5

<

8

Thrust (kg)

~16

Flight time (min)

30

TBD (40?)

Wind Lim. (kt)

< 20

TBD (< 60)

Altitude (m)

< 120

200

Horizontal Pos Accuracy (cm)

+/- 2

+/-30

+/- 200

Vertical Pos Accuracy (cm)

+/- 2

+/- 15

+/- 30

Usable Range (km)

1

10

inf w/LTE

Airframe


Pegasus is an X-frame configuration and motor arms attached directly to a straight aluminum block. Here are some of the key notes:

  • 30x30mm mounting grid for peripheral and accessory mounting

  • Xmm thick mainplates

  • Xmm distance between mainplates

  • Xcm distance motor to motor

  • Xcm dimensions with props on

  • Xmm high spacer for the autopilot

Mech should probably fill this out a bit more

<pegasus rendering>

< more information & dimensioning if necessary >

Top & Bottom Plates

Mech should probably fill this out a bit more

Featuring 30x30 mm blocks, these plates provide torsional rigidity and protection for batteries within the drone. They are < more information here >. These are Xmm thick, and made with <material>. FILES.

Center Block & Inner area

Mech should probably fill this out a bit more

The center block is where all 4 arms connect, and how the arms remain rigid and centered on the drone frame. It is made of <material> and uses <screws> to disconnect. Shoulder bolts are used <somewhere> to improve <something>. It is designed for easy removal of the arms for transport, if necessary.

< Link to supporting documentation/CAD>

Interfacing

The center block and arms are designed to allow 3-phase motor wires to run through the arms and exit out the cube below the pixhawk or otherwise <drawings here would help>.

MT30’s are designed to fit within the cube and arms for quick-disconnect of the 3-phase leads. See connector standardization for more information.

Removing the arms

Instructions for how to remove the arms, diagrams if possible.

Arms & Landing gear

Mech should probably fill this out a bit more

The arms mount to the airframe at the center block, and also through the spacers located at each corner of the frame. The landing gear mounts directly to the arms.

Payload attachment points

Inofrmation about how exposed slots in the frame allows for payload attachment points and best practices for that

Motor Mounting

Mech should probably fill this out a bit more

Motors are mounted on 3d printed mounts with a <pattern> (insert a photo if you can).

Propulsion


Pegasus uses 4 T-Motor Antigravity MN6007II kv160 motors. These motors are designed to run on 12s voltage and are wired to APD 120F3[x] v2 ESCs. The ESC’s are significantly overspecced and are designed to allow for continuous operation in high ambient heat environments and minimal passive cooling, although this is not a recommended mode of operation.

Motors

There are multiple alternative motors which we may use, and these interface to the carbon-fiber arms using 3d printed parts. The motor specifications change a bit depending on the propeller that we’re using. Review the following charts:

 MN6007II KV160 Charts

From that data, we can synthesize the fol

Recommended/Target

Maximum

Takeoff Weight / Motor [kg]

2

6* (depends on prop)

Current Draw (hover) [A]

3

25

Operating Temp

< 70 C

90 C

Interface

The motors mount to a 3d printed block which attaches to the ends of the arms. Multiple propeller mounting options are available!

Propellers

The current propellers are T-Motor MF2211 props. These do not follow typical propeller naming convention. They are 22” in diameter, but 8” in pitch (not 11). The 11 at the end of the name refers to the maximum thrust which the prop may provide.

Mounting

These propellers do not need a prop-washer to be mounted, the following infographic from the T-Motor website explains proper mounting solution:

Vibration

With folding props, it is possible to have vibrations and harmonics. It is important to look at motor data from telemetry logs, as well as listen to pilot and operator feedback gained from visual and audio cues, especially if there is significant turbulent air or pressure differentials across the path of the propeller.

Balancing

Our props come balanced from T-motor, and may need to be balanced if they acquire nicks, scratches, chips, or other deformities.

Safety & Storage

Polymer-carbon propellers are suspect to shattering under load, even with tiny surface scratches or nicks. Unless absolutely necessary it is not recommended to fly in marked or scuffed propellers.

Props should be stored in a low humidity and cool environment to prevent damage and aging to the propellers.

Electronic Speed Controllers

For the most part, the choice of electronic speed controllers is fairly relaxed as there are many commercial and off-the-shelf hobby components that may do the job. Keep in mind when choosing your speed controllers the software, protocols, and current/volage ratings that it may have.

Interfacing

Our speed controllers often have through-hole solder pads and castellated pads. Refer to EE guidelines on how these should be soldered. The holes are not mounting holes, and the ESC’s are interfaced to the 30x30 mounting grid through the use of 3D-printed cases.

The cases may be made of any material, but general guidelines are that they should be made of non-conductive and thermally resistant materials. 3D-printed TPU is often a good choice.

Heatsinks + Cases

ESC’s generate a lot of heat, and are prone to foreign objects shorting terminals or interfering with operation. ESC’s should be mounted in a way such that the possibility of foreign objects are minimized

Change Log

 V.029 -- 2023-09-19 -- Daniel Puratich --
  • Added a header for formatting improvements

 V. 028 --- 2023-09-19 --- Anthony (anni) Luo ---
  • Separated References and documentation

  • Added enviro limits (or at least started them)

    • This will need to be cleaned up as we test more but should be a baseline of when we can or cannot fly and with what configs. I’m working on how to present this cleanly (think like charts / spreadsheets for determining whether or not you can fly in a commercial airline)

  • Added templates for mechanical (airframe) section

  • Added information under propulsion section about motors/props

 V. 026 -- 2023-09-19 -- Daniel Puratich --
  • Updated Anthony’s role to be technical director to mitigate confusion of having a single position with multiple names. For details please see Technical Director .

  • Updated how we are tracking the changelog and version in the header

 V. 024 -- 2023-09-18 -- Daniel Puratich --
  • Updating terminology section moving things to our glossary

  • Created new specification for electrical glossary

  • Updated the electrical standards with context

 V. 022 --- 2023-09-17 --- Anthony (anni) Luo ---
  • Nuked entire previous/existing arch doc (copied from 2023 arch doc). Started (basically) from scratch.

  • Added section to store PDF files for spec parts.

    • PDF currently not filled in

  • Added in components table with links & more descriptions, as well an notes and extra information.

  • Re-organized document to include references and standards at the top of the page in “expands”

    • Hopefully this is a good idea.

Todo:

  • Flush out the rest of the document.

    • Pegasus overview, operating limits chart

    • Subsystems Explanations, Interfaces, Operation, etc.

Version Date Comment
Current Version (v. 29) 2023-09-20 03:27 Daniel Puratich
v. 57 2024-01-24 13:58 Anthony Luo
v. 56 2024-01-24 13:56 Anthony Luo
v. 55 2024-01-23 14:53 Anthony Luo
Addresses 2024-01-22 RFC's
v. 54 2023-10-15 22:58 Conall Kingshott
v. 53 2023-10-09 03:37 R D
v. 52 2023-10-09 03:34 R D
v. 51 2023-10-09 02:53 Anthony Luo
Small updates for correctness.
v. 50 2023-10-08 19:37 Mihir Gupta
v. 49 2023-10-07 17:11 Daniel Puratich
v. 48 2023-10-06 02:08 Conall Kingshott
v. 47 2023-10-05 17:49 Alison Thompson
Preliminary Cabin + Cargo section has been added
v. 46 2023-09-30 17:30 Daniel Puratich
v. 45 2023-09-30 17:16 Daniel Puratich
v. 44 2023-09-30 14:55 Daniel Puratich
v. 43 2023-09-26 03:23 Conall Kingshott
v. 42 2023-09-26 03:20 Conall Kingshott
v. 41 2023-09-25 00:12 Megan Spee
v. 40 2023-09-24 00:38 Anthony Luo
Added output configuration information to "Flight Control System > Wiring & Outputs" section
v. 39 2023-09-23 07:14 Daniel Puratich
v. 38 2023-09-23 02:20 Anthony Luo
v. 37 2023-09-21 03:59 Michael Botros
v. 36 2023-09-21 03:59 Michael Botros
v. 35 2023-09-21 03:58 Michael Botros
v. 34 2023-09-21 02:12 Daniel Puratich
v. 33 2023-09-21 00:21 Anthony Luo
Updates to better represent the nature of the document (as a reference manual)
v. 32 2023-09-20 04:39 Anthony Luo
V.032: Added burner/starter information for power distribution (HV & LV), as well as templates for FCS/RF/Periph information. formatting mid but will work on it slowly.
v. 31 2023-09-20 03:52 Anthony Luo
v. 30 2023-09-20 03:27 Daniel Puratich
v. 29 2023-09-20 03:27 Daniel Puratich
v. 28 2023-09-20 03:02 Daniel Puratich
v. 27 2023-09-19 16:23 Mena Azab
v. 26 2023-09-19 14:47 Daniel Puratich
v. 25 2023-09-19 14:36 Daniel Puratich
v. 24 2023-09-19 01:01 Daniel Puratich
v. 23 2023-09-19 00:35 Daniel Puratich
v. 22 2023-09-17 20:38 Anthony Luo
v. 21 2023-09-17 20:38 Anthony Luo
V.018
v. 20 2023-09-17 20:37 Anthony Luo
v. 19 2023-09-17 20:36 Anthony Luo
v. 18 2023-09-17 18:03 Anthony Luo
v. 17 2023-09-13 23:39 Anthony Luo
v. 16 2023-09-12 19:34 Daniel Puratich
v. 15 2023-09-09 20:12 Daniel Puratich
v. 14 2023-09-09 20:09 Daniel Puratich
v. 13 2023-09-04 16:22 Daniel Puratich
v. 12 2023-07-13 02:43 Daniel Puratich
v. 11 2023-07-13 02:40 Daniel Puratich
v. 10 2023-07-10 20:26 Michael Botros
v. 9 2023-07-04 21:03 Michael Botros
v. 8 2023-07-04 20:05 Anthony Luo
v. 7 2023-07-04 20:03 Megan Spee
v. 6 2023-06-14 12:43 Nathan Green
v. 5 2023-06-08 01:59 Anthony Luo
v. 4 2023-06-08 01:58 Anthony Luo
v. 3 2023-06-05 21:52 Anthony Luo
v. 2 2023-06-02 00:14 Anthony Luo
v. 1 2023-06-02 00:14 Anthony Luo

  • No labels