Skip to content

Conversation

@Elan456
Copy link
Contributor

@Elan456 Elan456 commented Apr 29, 2025

Description

Adds April flights to the Avionics documentation

Summary of Changes

  • Adds 3 launches to the flight tests (AA-AA-04-13-2025-0, AA-MA-04-13-2025-0, L1-MA-04-12-2025-0)
  • Moves flight tests to a separate markdown file
  • Updates the README with the new data saver and state estimation tools.

Motivation

  • Important to keep our documentation up to date

Testing

Check all that apply:

  • I have added or modified tests to cover these changes.
  • I have manually tested the changes on the target device(s) or environment(s).
  • Existing tests were reviewed to ensure they still work as expected.
  • If tests were not added or modified, explain why:

    Only markdown files were changed


Building

  • This change successfully builds in at least one of the following environments:
    • Native repo
    • Target device(s) (e.g., MARTHA)
  • If the build fails in any environment, explain why:

    (Provide reasoning here)


Checklist

  • My code follows the style guidelines of this project.
  • I have performed a self-review of my own code.
  • I have commented my code where necessary for clarity.
  • I have made corresponding updates to documentation (if applicable).

@Elan456 Elan456 merged commit 05266cd into main May 1, 2025
Copy link
Contributor

@mcschoo mcschoo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nothing to add

## Flight Test History (most recent first)

- **AA-AA-2025-04-13-0 [Active Aero FC Apr 13th 2025 Active Aero Launch](https://github.com/CURocketEngineering/Active-Aero/releases/tag/1.0):**
Flew on the same flight as **AA-MA-04-13-2025-0** and was connected to the air brakes. It successfully detected launch, engine burnout, and apogee (based on post-fight data analysis). The brakes were accurately deployed at 1 second after engine burnout and retracted 3 seconds before apogee (according to the software). There is no way of knowing if the fins actually deployed and then retracted or never deployed in the first place. Utilized the [new SD card data saver](../include/data_handling/DataSaverBigSD.h) which worked well.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You could add the point of CommunicateVerification showing deployment on the pad, but that's a little niche, so up to you

@Elan456 Elan456 deleted the doc/april-flights branch May 13, 2025 16:26
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.

3 participants