[Design Review] [EPS]: EPS v2 Firmware Implementation and Integration

[FerretCode]

Subsystem

EPS

Type of work

New firmware service

Target start date

2026-07-15

Reviewer(s) requested

@OSUSat/osusat-reviewers

What you're about to build

Implement the EPS v2 firmware functionality for controlling power rails and system power delivery, and integrate it with the rest of the CubeSat.

Which requirement(s) does this satisfy?

EPS Subsystem Info - Next steps (v2r1): Implement EPS firmware functionality, Integration.

Pre-work checklist

• Relevant subsystem information doc section (mission context, electrical requirements, part tradeoffs) exists and covers this work
• (Hardware) Relevant part(s) selected with a documented tradeoff, or reusing an already-approved part
• (Hardware) Derating requirements for any new part identified before layout begins
• (Hardware) If this touches envelope, mass, power architecture, RBF, deployment switches, or RF: CDS-compliance checklist reviewed
• (Firmware) Interface sketched out and classified into Question/Command/Loop per the event-driven refactor guideline
• (Firmware) Proposed event UID(s) checked against the existing UID registry for collisions
• Known open questions or risks are listed below

Open questions / risks

Are there any changes to the boot flow or rail sequencing?