EE W24 Projects

Harnessing - comp drone

• All the wiring for the drone

• Current Status: Pegasus 1.0 wired with core control system.

• Missing parts:

  • LED Controllers

  • Gemini

  • VTX 12v rail to be connected (exists)

• End goal: Competition ready harness

  • Going to keep current harness until comp, making new harness loses out on testing that’s been done (trial through flight test).

• Will support second drone once completed.

  • will be building a new harness → better idea of the layout.

Flight test requirements:

• ATP for new harnesses may take too long (time crunch), people may not follow closely.

Gemini

• handed over to EFS

  • 3 boards assembled, handed over to EFS, X boards worth of parts able to be assembled. (estimating 5 more)

End goal:

• Be ready to bring up 1 or 2 more boards once EFS acceptance testing done

LED board - comp drone

Current State:

• Finished first rev. of PCB, comments to be addressed & reviewed.

End goal:

• LED Board flying @ comp.

• Latest deadline to be integ’d by Pegasus 2.0 all systems up

Testing reqs:

Timeline:

• aiming for completion by early february (ordered before feb 1st)

• Testing done by Mar 1st.

Tracking antenna

Current State:

• Board close to done, in routing stage.

End goal:

• done & tested.

Timeline restrictions:

• COTS solutions to be impl. at some point this term if not fully validated E2E (incl. software).

High current power module

Current State:

End goal:

• board wants to be assembled & tested.

• Ready 2 fly.

Timeline:

• no timeline

  • get them assembled & brought up in the winter term.

• Ground testing + bringup validation to be considered in the summer term.

Additional Projects

ZP3 interface

• new member, timeline hard to give.

Servo motor power management / supply

• Likely to be done before february! (ordered before february 1st).

PDB (Power Distribution Board)

• Daniel puratich. Tom working on them, more time this term (on co-op)

12S ESC

• Ethan working on 12s esc.

• Likely target to finish by EOT.

6s ESC

• new member, timeline hard to give.

• Low priority.

CAN Sensor Board - pending kickoff

• Waiting on if people finish current boards.

Megans questions

• AEAC syncs: We ran them throughout summer & fall, for those that attended the meeting what are your thoughts on how the meeting was structured and how the meeting took place? Were there too many details, was it too long, was it useful?

  • When first joined AEAC sync, lots of terminologies from other subteams that were hard to understand. Would be nice to have an introductory document to bring everyone into the loop.

    • arch doc was not helpful introduction to everything that was going on (too long)

    • after more meetings, get a handle of what is going on. Joining flight test also helps a lot.

  • Things get lost in the document // action items aren’t stressed enough. Lots of team members giving updates, important actions will come up and it doesn’t get emphasized enough or delegated.

    • Would be good to emphasize action items at the end of meeting or end of the document.

    • Action items section at start of the meeting not useful because things will come up during the meeting (gets filtered out or forgotten)

• AEAC syncs: Was it too technical? Updates and discussion

  • Meetings are better now, right amount of technical but not detail. Gives everyone an opportunity to ask questions and give their thoughts.

  • Never felt like the meeting was going off track, every discussion has felt important and was being had at the right place / time as opposed to another meeting.

  • Structure as is is good, but information and action items tends to get lost because so many things are brought up (positive), but need a way to emphasize the takeaway

• Leads meetings:

  • Feels like reading the meeting minutes is enough and you don’t actually have to attend

  • leads meetings feel very short - not a lot of discussion. sometimes however gets into a tangent

leads+aeac sync combination?

• no - reduce frequency of leads meeting instead, actually

  • leads meeting last term was policy updates

  • this may not be the case this term !

Director oversight/support!

• bit of guidance/mentorship for leading meetings would be good

• integration help from @Anthony Luo - EFS ++ EE

  • ideally this integration can be transferred to AEAC syncs entirely

• directors would be happy to support you running in-person socials!

Asana

• too much documentation, already have confluence

• from @Anthony Luo : it’s good for cross subteam interfacing

  • tracking tasks

  • tracking blockages

  • EFS asana: tracks multiple projects - other teams have large todo lists. depends on the team

  • useful for visualizing blockers, etc, on a big team scale. subteam level not as important.

•