Attendance:
Electrical:
Embedded Flight Software:
Ayush Ganguly
Autonomy:
Operations:
Directors:
Agenda:
| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
1. Changes to AEAC Sync Structure
Meeting minutes still avail. 1 week before. This gives teams time to fill out blockers, decision documentation, etc, before the meeting.
Goal is to bring updates and then next steps, ideally we explain decision documentation, but we try and have decisions made async, with documentation on the decision ready to present!!
Trying to be respectful of time and people who may not be a part of each project!
Good to bring forward global knowledge, but highly technical discussion maybe …. maybe not! Feel free to mention open invites to decision meetings (maybe just put them before AEAC sync idk).
Project based updates. Projects sub-divided as found on 2023-2024 Program Outline
(Hopefully) increasing cross-talk between subteams on specific projects.
(Hopefully) allows members to be engaged during their related project, instead of having to piece through multiple sub-teams updates
(potentially) allows us to schedule 15 minute blocks for each subsystem across an hour
Video System
Command + Telem
Airframe + Propulsion + Sensing
General Updates + FT
Understood that this may require a bit more overhead from subteams in meeting prep. Happy to work with subteams on weekends to ensure meeting goes well.
Global action items / system architecture updates to go at the end of the meeting in a dedicated section.
Allows for team-wide recap of the meeting at the very end.
Leaves more time for discussion about architecture + integration instead of taking up critical meeting time early on in the meeting.
Project-based action items to go at the start of each project section. (so as to be easily findable)
(hopefully) allows subteams to call out blockers
Allows team-members on each project to quickly and easily find project-specific action items.
2. W24 AEAC Sync meeting time(s)
We are looking to find a time for W24 AEAC Sync meetings. Talked with subteam leads during Subteam : Director syncs about stacking the meeting before leads meetings:
Good things:
Fewer days to travel to campus.
Potentially more stayover from AEAC syncs so general members may stay through leads more.
Bad things:
Some subteam leads aren’t available all of Monday.
Potentially two back to back draining meetings.
Decision: [tbd]→ fill out lettucemeet
3. Competition Timeline Review
Jan 15th (Today): Competition Phase #1 Paper Due
Feb 17-25: Reading Week
Apr April 8: Classes End
April 11: Exams begin
April 11: Proof of flight
April 12: Team list submission
April 21: End of final exams
May 6: Classes begin
May 24-26: Phase #2 (competition)
4. Flight Test Timeline Review
Aiming to fly at least two competition simulations (end to end, fully integrated).
May not (necessarily) be flown with flight test team. TBD
Aiming to finish flight testing near the end of classes (no flights through exams planned - may use as spillover dates)
Aiming to schedule 1 key downtime period +/- 1 week around reading week for overall system updates and return to service ground tests.
Following ground test → Houston → Pegasus for all new hardware + systems.
Done to ensure overall safety of our airfrmes.
Please coordinate with Anthony Luo to order any necessary components. Currently tracking
diversity RX’s
houston props
vtx systems
Over to asana!
flight test this weekend -
4v6 batt config - https://uwarg-docs.atlassian.net/wiki/spaces/FT/pages/edit-v2/2391113782?draftShareId=95aa7b5b-1eeb-4c72-90e7-63ef08b70a09&createdWithTemplate=true
Attendance
Mechanical:
Electrical:
Embedded Flight Software:
Autonomy:
Operations:
Directors:
Agenda
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Propulsion + Control
Action items / blockers:
EFS looking for <team> to integrate <bidir dshot generic item> on <some date>
Updates:
< Decision documentation >
Mech | < motor mounts > | < some update > make sure to check motor direction |
EE | harnessing | the harnessing will allow 4 or 6 batteries otherwise, no news |
EFS | esc | make sure you have ESC telemetry check all current items: notch filtering, etc |
Auto |
Sensing
Action items / blockers:
360 Lidar mounting - Houston
Updates:
Aiming to FT 360 lidar soon
Mech | sensing mounts | 360 lidar not on monster mount monster mount is done, though Houston has a 360 lidar mount. This has all hardware and software prepped. (maybe not harnessing)
|
EE | sensor mount harnessing | “looks done” - flow sensor is tested CV camera + lidar also tested |
conformal coating | no plans as of right now to conformal coat any of the sensor mount components figure out which components need extra help when conformal coating keep in mind we have SDC thermal camera - if you need access ping @director or (Megan Spee - I will ask in slack) | |
EFS | configuration | configure for ardupilot with the objective of carrying this over to zeropilot |
Auto |
Video System
Action items / blockers:
EFS looking for <team> to integrate <bidir dshot generic item> on <some date>
Updates:
< Decision documentation >
Mech | mounting | |
EE | harnessing, power delivery | haven’t looked into it yet - depends on RX/TX we buy |
EFS | configuration | configure the video MUX |
Auto | LTE | |
groundside | geolocation not ready yet |
Telemetry
Action items / blockers:
EFS looking for <team> to integrate <bidir dshot generic item> on <some date>
Updates:
< Decision documentation >
Mech | airside | Gemini airside mounting - proposed solution is double sided tape? |
groundside | Tracking antenna not looked at yet | |
EE | nucleo shield still in progress RPi airside is USB C connected to ->> BEC pro boards | |
EFS | TX/RX | flashing diversity onto receiver + look at multi receiver support make sure gemini FW works relay working, still need to test. After this, check out receiver on drone to check 3 wire/ 4 wire compatibility. |
tracking antenna | ~~ maybe progress on GPS/IMU integration | |
Auto | LTE telem | Task 1 almost ready to fly, task 2 getting worked on |
need to integrate autolanding infrastructure |
General Updates
phase #1 paper submitted!
Flight test schedule
Next ft; blah
requires: blah blah blah