2023-09-24 EFS : Director Sync

Lots of bootcampers. Some people missed sections but its on them for not reading. New members are eager to take tasks. Bootcampers dont have exp and are interested. Theres not a lot of work to give to new members. Considering restricting bootcamper number? They had a lot at start of Fall, but it should flatten out? A chunk of bootcampers also get bored. Therr’s a backlog of tasks, there’s always something, but its hard to assign things. Dont want to turn anyone away.

Gagan MIA, Ayoung has dmed, busy on study term. Kinda ghosted team. Ayoung taking over project. He was main dev for system manager. Milestone 1 is mostly integration.

Milestone 1, basic system manager, ayoung has taken over frkm gagan. People are working on future milestones. Milestone 1 needs to be tested then we can flight t3st it. Need to clarify Hardy’s plans.milestone 2 integrates attitude manager and basic telemetry manager, same control algo as milestone 1, acro mode. Milestone 3 is porting in new control algo and more sensor drivers integrated. We have lots of drivers already that need validation and integration. Rangefinder, crsf, OFS, awaitting. M1 and M2 this term are realistic, depends on priorities. Plan is to fly on tubes which we have and we can make. Plan is to fly on zp3. Locking connectors on interface would be nice but not required. More zp boards wouls help for dev but we have two that are good now.

If electrical has big ideas they have that need firmware. These ideas are good for new projects. Cc @Michael Botros on can interface board or poc board.

Aidan carrying AM. Possibly have Aidan start bringing up a projrct manager.

Telem manager stalled bc Yuchen busy, focusing more on tracking antenna. Qould be good to find someone else to takeover telem manager. Mavlink interface lives in Tm.

Path manager is very far in the future. Van taking over from Neha on this, Neha super busy. Low priority. Need to get to milestone 5 before this is implemented.

Cots stuff is starting, sync coming up. 4 devs assigned to that, Anni helping. Derek will manage. Tuesday. Need to flesh out requirements. Can pull deadlines from Anni. We really onky want to do things that will fly. Dont make false promises. In the past there was a simple system manager deadline of make this work and well fly it then they got it done and we deided not to fly it, its rlly depressing to not be able 5o fly it.

Simualtor is kind of overlooked as far as pressure on deadlines. Theyre also doing something pre unique. Taim is on every subteam, need to clarify what he wants to do. People working on it now have experience. Purpose of this is that once zp code is ready we wsnt to be able to run it on computer. Simulator simulates thr drone environment and mock sesor data. Possibly it needs rearchitecting? One problem at a time, let this idle for a bit? It seems to be going somewhwre but leads are handoff on it. Project manager should have a sync meeting for this.

Focus shifting to comp stuff: cots and tracking antenna.

Tracking antenna is gated by driver. Stuff is written fot algorithm but needs to be tested, but integration. Mavlink passthrough is working, fully tested on drone, neo m8 has lots of testing. Bmx160 driver is the last driver. Pid was copied from ardupilot implementation. After bmxq60 driver can be tested.

Goal on efs is to minimize refactoring things in the future. Efs is up for anything Anni approves electrically. For the past three years we’ve spent a lot of time rrfsctoring. Goal is dont rewrite anything.

Saying things are comp critical it seems most members are willing ti gk fkr it. Zeropilot has no time deadlines but it is a lot of fun!

New bay increases visibility. People randomly wander in and we tell them to do the bootcamp. Most pekple found us from the sdc event!

Zp is kinda EFSs own thing. They wanna do more stuff with other subteams. Aadi doesnt believe zp will ever fly at comp sadge.