August 31th, 2022 - Electrical Task Sync Up
Attendants
Austin
Logan
Chan
Ari
Agenda
Review and discuss status of ongoing projects
Plan out and scope future EE tasks for end of comp
Ongoing Projects
Science board
Was assembled a while ago, need a status update on the firmware testing for the board
All board tests that could be completed without firmware have been completed
If firmware is completed, next test is to determine if rails are pulling correct voltages when receiving commands or signals (i.e. if its pulling enough voltage when powering a motor)
SPI LVDS
Either peripheral or host board is complete, however one is not complete yet
Taylor was previous contributor, may continue project, nobody actively working on it as its low priority
SPI LVDS
confirms SPI to longform signals, plan to use them on wrist and gripper joints as they are further away from odrives
not high priority as we can do joint by joint testing without converting to longform signals (just connect the odrive closer)
delegate tasks for receiving status updates
PDB
schematic is done and reviewed, layout in progress
layout will likely be done soon, however need to circle back to get a status update
parts have not been ordered yet
BMS
similar state to pdb, schematic close to competition, yet to be reviewed
parts have not been ordered yet - potentially part of the BOM
Multiphase buck
layout has been posted for review
ordering parts for the board soon
RS422 breakout board
RS422 breakout boards are completed and already mounted on the odrives
need to circle back with jason to see if there are any planned / future changes for the board
need to confirm current qty and how many we have working - will probably want to order more
M1 task to get full status update - see if they work, current quantities and design status
BLDC Motor Controller
it is likely no progress has been made for this yet; this would be a p1 task at best. very low priority at the moment
Future EE Tasks
Comms
M1 - need to find someone to work, learn about and right a nice operational confluence page on comms
M2 - latency and range testing after getting a core understanding of our comms system
M1 - confirm which antennae in the bay are being mounted on the drivetrain and where they are located
for M1 focus on picking anything that works then worry about improvements for M2
M2 - if there are any required changes to the base station, this needs to be determined (definitely more of a mechanical task)
P1 - if there is interest and manpower figure out how to make a battery
look for cost estimate, manufacturing process information
first need to refine power budget calculations through M1 testing before selecting cells
M2 - new members to get involved with testing and debugging for all M1 systems
PM Tool
https://docs.google.com/spreadsheets/d/1imf_OKjGeVF7BAd0x7Hlz-e45I1U33sTOc7G1meOANw/edit?usp=sharing
PM emails for edit access
This tool will be managed by team leads to track every active task the team is working on
With proper implementation, PM timeline would dictate task assignment and work distribution for each week (offload from subteam leads at weekly leads meetings)
For more clarification, we are aiming to get all subsystems to an M1 build minimum by end of term
Team leads to meet with subteam leads individually to discuss sheet before term starts
Feedback open and appreciated