Change Description
ICARUS
Defined Icarus Airside Power Architecture
Description of Change
Specifically how each device is being powered needs to be properly documented in the system architecture. Currently all that is written is a 12S power architecture and vague power rails for different devices.
Implementation
Detailed power architecture has been documented in a table here: Power Distribution Architecture. There are a few things that are up in the air:
How video system is being powered. Solutions presented are directly from the PDB, a separate 3S battery if we want a cleaner rail, or using another COTS PDB for a cleaner 12V rail
How LED strip is being powered. I have been told from Daniel that we have an LED strip in the bay. I need to document the part number and figure out how we want to actually want to control it. Current solution is to drive the gate of a MOSFET from a GPIO from the Pixhawk. This point could/should also have its own RFC.
Data filled out for airside components. Groundside components will have a separate RFC.
Reason for Change
Members working on Icarus need to know where/how devices are being wired.
Priority
⬆️ High
Impact of Not Responding to Change
Team will not know how devices are being powered which will delay harnessing for Icarus.
What Groups, People, Sub-teams Need to be Notified?
Anthony Luo
Nathan Green
Hamza Ali
Aidan Bowers/Sysint
EE (Daniel, Michael, Farris, Rayyan, Nolan)
Megan Spee
Conall Kingshott
Change Impact
Additional Parts/Resources Required and Costs
None as of now.
Impact on deadlines
Less than a week to implement this change.
Alternatives and Recommendations
No alternatives for this RFC. Need to clearly define specific power architecture.
Comments
N/A
Change Request Sign Off <System Integration>
Status
✅ Accepted / ⏸️ On Hold / ❌ Rejected / 
More info Requested