Backplane Meeting - 9/14/22

Attendees:

@Will Merges (RIT Student)

@Mary Dertinger (RIT Student)

@Louis Fleisher (RIT Student)

@Nate Lloyd (RIT Student)

@Aaron Chan (RIT Student)

@Jim Heaney (RIT Student)

@Chloe Clark (RIT Student)

@Yevgeniy Gorbachev (RIT Student)

@zackary wake

@Dante Sivo (RIT Student)

@John Ye (RIT Student)

@Billy Siegener (RIT Student) (Deactivated)

@michael

Item	Notes

Item	Notes
Backplane	SwitchBlox microswitch going forward Connector not selected until specific power/IO Added GPIO block to diagram found memo that says no need for magnetics? one reason for magnetics is to support high current + high voltage AC through any port (part of IEEE 802.3) Everyone get maximum GPIO pin count they need so we can decide on a module ↔ backplane connector Probably driven by autopilot Power req not sent Every module sends a heartbeat to GPIO for blinky blinky
Power Module	James not here Updates made to block diagram / other comments from last meeting Still need power, voltage, & current requirements from each module and the backplane
Autopilot Module	Ben not here Idea: add ability for servo control
Sensor Module	Sensors selected This rocket might exceed 20g 56 mg resolution on high-g is not that bad Starting schematic capture
Radio Module	Currently planning on using an XBee (not pro due to availability) Pushing power until after link budget is satisfied
Flight Computer Name?	Connected Loads On Will's Network, contained by a Connector of Independent Redundant CompUterS

Action Items

@Billy Siegener (RIT Student) (Deactivated) send power requirements to James for power module
@Dante Sivo (RIT Student) select radio module, do link budget, if meets requirements send James power requirement
@Mary Dertinger (RIT Student) @Louis Fleisher (RIT Student) send power requirements to James
@Mary Dertinger (RIT Student) @Louis Fleisher (RIT Student) Populate RMS noise values
Everyone should think about better names