Supporting Documents

🗂 References and documentation

🖇️ WARG Standards

📐 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.

Ultimately, this document serves as a “reference manual” for Pegasus, and should contain necessary information for the usage and support/maintenance of Pegasus. Engineering decisions and background knowledge should be provided as references, external links, or as subpages. We want to know how this drone works, and not necessarily why that decision was made.

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.

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.

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

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

<pegasus rendering>

< more information & dimensioning if necessary >

Top & Bottom Plates

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

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

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

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

Propulsion

< insert schematic here >

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

Interface

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

3.5mm male bullet connectors will exist on the motor leads, and these will plug into 3.5mm female bullet connectors on 3-phase wires which run through the carbon fiber arms.

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. See <prop balancing link> for more information.

Safety & Storage

T-Motor Polymer folding props require particular storage and upkeep.

Please refer to <general prop storage> for storage information, and please refer to T-Motor instructions on tuning the friction of the joints to ensure safe operation.

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

ESC’s will have 3.5mm female bullet connectors on 3-phase live side. This will attach to a short MT-30 extension, where the MT-30 on the block-side will be fe-male, while MT-30 on the arm-side will be male.

Our speed controllers often have through-hole solder pads and castellated pads. Refer to EE guidelines on how these should be soldered.

This is done so that there is a common ground reference point (star topology). There exist solder pads in between the voltage pads for ground, signal, and telemetry on all APD esc’s and PDB’s. These should be used, with M1-4 connections on the PDB being taken to the pixhawk.

ESC 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. The ESC cases must allow for the removal and replacement of ESC’s with only the disconnection of 3.5mm and xt60 connectors, and with no disruption to other parts of the drone. (I.e. ESC only replacement must be possible).

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 when in regular operations, and heatsinks shall be added as necessary to prevent thermal limiting or runaway.

Software Configuration

It is recommended to run the ESC’s using default firmware (BL_HELI, Bluejay, etc) at 48khz update loop. This offers the best blend of controllability and power efficiency.

Bidirectional dshot must be supported as this offers critical logging and flight performance data, as well as advanced filtering options for the autopilot. On Pegasus, it is recommended to run DShot 300, as 600 may introduce significant signal integrity issues, and DShot 150 may be too slow for accurate bidirectional data transfer.

Telemetry wires shall be connected to a uart port, in the case of a bidirectional dshot failure. This is significantly slower than bidirectional dshot but offers us a failsafe and backup.

Power Distribution

On Pegasus, “power distribution” refers to all elements that affect and interact with power before it is distributed to individual components. Typically, this includes:

• Power distribution boards for ESC voltage

• 12v and 5v LV supply for peripherals

• Power monitoring & Power backups for the flight control system

All power on pegasus runs to a common source (the PDB), with the exception of the pixhawk system power delivery which will be provided by the power monitor + BEC backup.

Battery Voltage

Below shows the two different battery configurations we can fly. Pairs of 6S battery cells are connected in series and terminated with an XT90. The harnesses below show how the batteries are attached and how removing harness 3 and the cells with it bring the drone into its 4 cell configuration.

Battery voltage is around 50 volts for pegasus. All high voltage systems follow <EE to insert spec here>.

Interfacing

There exists 30x30mm mounting holes on the PDB. These may be used directly on the 30x30mm mounting holes on the drone. Electrical isolation must be provided between the contacts of the PDB and the carbon fiber, as voltage may arc across the carbon fiber starting (at worst) fires.

<photo>

A case shall be provided for the PDB that covers the terminals, but leaves sections exposed such that it is possible to attach wires to the LV and motor busses.

<EE to attach photo>

• XT90’s will be used between battery and PDB

• XT60’s will be used between PDB and ESC

Batteries & Harnessing

Pegasus officially supports 4, and 6 battery configurations. Physically 8 batteries will fit with a light enough payload.

These batteries are cross-connected from each other, meaning that the only difference between a 4 and 6 battery connection is the NC of one pair. These should be labelled or colour coded

Below shows the two different battery configurations we can fly. Pairs of 6S battery cells are connected in series and terminated with an XT90. The harnesses below show how the batteries are attached and how removing harness 3 and the cells with it bring the drone into its 4 cell configuration.

XT90 standard across the board, but the maximum peak current draw from all 4 motors is anticipated to be around 90Amps. Any individual motor will not draw more than 23 amps at a time, not including the path.

Errata

On certain long voltage runs, it may be necessary to “double up” on decoupling capacitors. <ee to fill in more>.

Low Voltage

< Insert schematic here >

Low voltage systems on Pegasus run at either 5 or 12v. Below are the voltage and current draws of each (potential) Noteworthy peripheral. Please refer to individual documentation for more information

• Jetson: 12v 4A

• Raspberry Pi + LTE: 12V 2A

• RFD900: 5V 1.5A

• Pixhawk: 5V 3A

• 800mW vtx: 12V 1A

• 5W vtx: 12V 5A?

• Gemini: ???

• I may be missing multiple items. EE leads please double check from prev. years and compare

Power Monitoring

We use powering monitoring from a Holybro PM02D HV module. This uses I2C to communicate with our autopilot, meaning that we don’t need to do analog voltage or current calibration.

This is used in isolation, with no backup. There is only 1.5A continuous draw available ee leads fact check me, and this power monitor will continue to update current and voltage measurements even after LDO failure.

LDO failure should be mitigated by providing the pixhawk with a BEC that is capable of up to 5A continuous draw. fact check me 5 or 3a.

Pixhawk Errata

Note that the pixhawk telemetry ports only support 0.5A current; with the exception being “Telem1” which supports up to 3A.

The pixhawk also supports two concurrent power monitors. We are using 1 power monitor and 1 BEC with NC’s on the remaining pins for better redundancy under thermal limit.

Flight Control System

Pegasus will operate using an ardupilot software stack. As of Fall 2023 Pegasus runs software revision 4.4.0, as this brings necessary changes for digital power monitoring and bidirectional dshot.

Software Configuration

Sensors

Please refer to each sensors page under our operating manuals space in sysint.

Pegasus will use the following external sensors:

• Two M9 or M10 sensors, using GPS blending for position; or 2 RTK sensors being blended.

  • one of these will be the “primary” gps, and must have an accessible safety switch.

• 1 Optical flow sensor, facing downwards and aligned with the drone

• 1 Lidar rangefinder, facing downwards

Anni to make mounting requirements pages for all of these (see sysint space most likely).

Particular Mounting constraints

When using blended GPS sensors, these shall be placed as far apart as possible, with no wiring nearby and with the sensors elevated above the plane of the drone.

A word about calibration

It is not necessary to re-calibrate the compass every time you fly, but it is strongly recommended to do so if you have moved more than 40km from your original location as you may have different magnetic interference.

Accelerometer calibration does not need to be done more than the first time you did setup, or if there is significant concern about the health of the system.

RF + Peripherals

There are a number of external devices on the drone. Autonomy is largely responsible for additional compute, while Electrical is largely responsible for RF

Frequency Distribution

Pegasus will support 2.4+900+433 interchangeable control links, as well as LTE+piggybacked telemetry, and dedicated 2.4 or 900 telemetry systems.

Pegasus will use 1.3 ghz as the primary airside video frequency.

Antenna Choice

2.4ghz antennas will be regular dipoles, potentially folded dipoles. Refer to https://docs.google.com/spreadsheets/d/1G2Ue9xrBFwbJbkzpw3Gx3-eZ3x3dWSVjVrP4fPepvcg/edit#gid=0 for the best selection.

1.3ghz antennas will be circularly polarized antennas provided by TrueRC. Airside antennas will be Singularity 1280’s.

900 MHz antennas tbd

433 MHz antennas tbd.

Antenna Placement

< EE TO ENTER MORE INFORMATION ABOUT RF STUFF >

Control Link

GEMINI GO BRR

Telemetry Link

GEMINI GO BRRR LTE GO BRRR

Video Link

1.3 go brrr. System unchanged from previous year: 1 forward facing camera and 1 downward facing camera

PIKACHU OBLIGATORY PIKACHU

ok thank you for listening

Change Log