[Design Review] [OBC]: OBC Software Test Harness and Mocking Framework

[FerretCode]

Subsystem

OBC

Type of work

New firmware service

Target start date

2026-07-15

Reviewer(s) requested

@OSUSat/osusat-reviewers

What you're about to build

Create a testable software framework without hardware by mocking other subsystem communications, allowing the OBC code to run in a dummy mode for testing.

Which requirement(s) does this satisfy?

OBC Subsystem Info - Next steps (v1r1): Create testable framework without hardware while it's being designed.

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

What communication mocks are needed (EPS, Payload, Comms)?