• Recruitment events

  Status
  colour Red title URGENT

• Leads meeting

  • to send lettucemeet after this meeting

• Gen meeting

  • to be scheduled after first onboarding meetings through mega poll

• subteam meetings

  • subteam leads to schedule

• SDC Showcase on Wed, Sept 6 (3-5 PM)

  • Automatic slideshow on TV (?)

  • Video compilation (?)

  • Small printouts presenting each drone (?) - related to ‘meet the fleet’ board.

    • talk of 3d models?? not for right now, just use the actual drones

    • Parts (PCB’s, nucleos, software, etc)

• New member info sessions (PICK DATES)Thursday (7) Saturday (9) Wednesday (13)?) 6pm weekend, 1pm saturday

  • New recruitment slides in progress

  • Each team to update their respective slides - subteam leads update this HERE

  • individual recruitment events? - not really

    • Up to subteam leads to schedule & book

Brough up re: mech stuff about starting an aero team. What is our approach to having different categories under a subteam? For ex:

• Mech & Aero

  • Simulation

  • Composites

  • Airframe/Structures

  • UX/or whatever mechies call “human interactivity scoring”

    • ergonomics?

• EE:

  • PCB design

  • RF engineering

  • Harnessing / Bringup / Integration

• EFS

  • Ardupilot

  • ZeroPilot

    • software (pm/am/tm/etc)

    • drivers

  • ELRS & RF

  • Ground station (Tracking antenna, data forwarding, OSD, etc).

• …etcAuth

  • … etc

• Paris wasn’t built on a D20, so we need to see to it…. or something

  • “rome wasn’t built in a day”

    • but it was burned down in a couple!

  • “The leaning tower of pizza 🍕 is …… <fill in the blank>”

• We’d like to come up with short-term goals for this competition season, as well as long term goals for the next few projects. This goes for all subteams, and we do not need all subteams working on the “same” projects/airframe, but we need to fit it all into a meta that allows us to perform well at AEAC and (hopefully) SUAS. This may involve cutting projects that aren’t directly relevant, and creating other projects to fill niches and voids. Having this plan will really allow us to go hard on marketing.

Mech

• composites work (good ways to make more composites)

• Fixed wings // plane design → VTOL

• Further effort/emphasis on simulation / optimization of different systems

EE

• Replacing OTS solutions with (superior) custom ones that

  • fit our mounting patterns, weight requirements, use cases better

  • Goes for sensors, RF devices, etc

  • Still same PCB design, but we want things more customized for our system

• More effort/emphasis on RF stuff ™️

  • We need to analyze antenna structures to some extent

  • Daniel Puratich Will be focusing on this when onsite

EFS

• Working with EE to provide support within ardu ecosystem for new sensors/devices

• Zp3?

Autonomy

• SUAS targets

• We schedule as needed!

  • Daniel Puratich Will get a better feel for this when I’m boots on the ground

  • Daniel Puratich to complete learn quiz for this

• Competition Roster Selection Guide

• Lots of good activity going on about this, we likely don’t need to announce this publicly until a bit later in the fall term when things are more settled down. (maybe after reading week -anni)

  • Keep the discussion coming! Feel free to comment on the confluence page.

• Hoodie run in the Fall (Post midterms, late October / early November)

  • poll for interest @ first gen meeting (end of september?)

  • interest form to include things like bucket hats, hoodie, jackets

• Jackets possibly moved to W24 along with all competition branded merch

• Patch designs?