Cross Functional Goals:
FW thinks that the cross functional goals were a good idea
Cross Functional Goal 1: Flying ZP on airframe: Tentative February 8th with initial flight
This weekend we want to have motor controller and have am restructure ready for testing, the idea is that we can test both pieces on hardware.
Tests: Try spinning drone motors and ensure they’re running at correct speeds.
After that copy in PID values on board
EE still needs to solder the board with peripherals which will be done over the coming week once these goals are met.
Cross Functional Goal: Firmware-CV Comms: Tentative February 10th15th
We’ve got a UART driver that can send the FOJI and FIJO structs back and forth.
We need CV to rework the comms module to use byte arrays, not too hard
Jetson is in the bay, we need a USB-TTL breakout board to test this as well, confirm with Ryan about power supply.
Cross Functional Goal: Firmware-Ground Comms: First test February 3rd10th
Aadi will have a PR up within the next few days, review should be completed in 2 days, so firmware-ground
Receive should have initial code ready by tomorrow on the ground, send logic will take end of the week.
Unsure if XBees are hooked onto ground station, follow up with Aadi and others on that to get hardware ready on ground and air. Big Concern
Cross Functional Goal: Gimbal Tentative February 1st
EE will solder on arduino nano onto gimbal PCB by end of week
Confirm with Sahil but the code in kitchen-sinks is likely sufficient to load onto the ardunio and test
Gimbal prototype has servos on it and we can just hook our board onto it and run our tests. Gimbal prototype is on a shelf in the bay
Currently printing another gimbal prototype with a new printer
Flight Tests w/ Mech
Mech will have grabber mounted within next 2 weeks and we’ll do an indoor flight test with that
WrestRC flight tests still need some time for grabber and landing gear to be complete, follow up with Brielle for timeline
List of who’s going to competition
...