[Design Review] [Payload]: Payload v2r1 Firmware and Integration

[FerretCode]

Subsystem

Payload

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 and test v2 software functionality, create v2 hardware mocks, test on real hardware, and integrate into the system.

Which requirement(s) does this satisfy?

Payload Subsystem Info - Next Steps (v2r1): Create hardware mocks, Implement and test software, Test on real hardware, Integrate into system.

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

How do we synchronize dual cameras for simultaneous image acquisition?