Skip to content

Add QFE reference elevation message to telemetry system - #145

Open
ETSells wants to merge 1 commit into
integration/state-estims-telemetryfrom
ES/QFE
Open

Add QFE reference elevation message to telemetry system#145
ETSells wants to merge 1 commit into
integration/state-estims-telemetryfrom
ES/QFE

Conversation

@ETSells

@ETSells ETSells commented Aug 20, 2026

Copy link
Copy Markdown
Member

Description

Simple change: Adds a message with calibration offsets to the telemetry system for use on the frontend.

Issue Link

Closes #137

Parent: SunDevilRocketry/SDEC-API#24

Testing

  • Passes existing automated tests
  • Automated tests modified
  • Manual test performed

https://discord.com/channels/1533570052677304420/1533588614301220884/1540196574372827146

AI Disclosure (Required)

  • Was an AI agent used to synthesize a significant portion of the submitted code?
  • Do you understand that you are responsible for your contributions, regardless of whether they are generated or hand-written?

Scope of AI assistance:

N/A

Please consider disclosing the specific tools you used (this part is optional):

  • Model: N/A
    • Thinking Level (if applicable):
    • Context Size (if applicable):
  • Harness: N/A

Other

N/A

Reviewer Checklist

Standards

  • Follows FCF Architectural Standards
  • Follows SDR Coding Standards
  • Code complexity/function Size is minimized
  • Code is testable
  • Code is readable and commented properly
  • License terms are respected

Accuracy

  • Code implements the correct requirement (a.k.a. does the right thing)
  • Code is logically correct (a.k.a. does the thing right)

Error Handling

  • Potentially unsafe functions return a status code
  • Error returns properly handled
  • Fail-fast errors are only thrown when unsafe to continue software execution
  • Debug errors are thrown for exceptions where execution should still continue (to be noticed during development)

Memory

  • Stack allocated memory is scoped correctly
  • Heap allocated memory is not used
  • Statically/Globally allocated memory is minimized except when necessary
  • Pointers are used correctly
  • Concurrent access has been considered (especially by/from interrupt service routines)

Performance

  • Rate limiters are respected
  • Busy waiting is avoided in performance sensitive code
  • "Delay" calls are not used in performance sensitive code
  • If performance is negatively impacted, a justification is provided and the impact is quantified

@ETSells
ETSells marked this pull request as draft August 20, 2026 18:58
@ETSells
ETSells marked this pull request as ready for review August 21, 2026 03:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Telemetry: Implement a message to give the baro offsets to the dashboard

1 participant