Ignition: Implement proper parachute deployment logic

Open
#266 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
c
Domain
embedded-iot

Research direction

Begin by locating the current ignition logic that deploys the drogue and main chutes back to back at apogee, then inspect the PRESET_DATA struct. Confirm the deployment sequence and timing through the proposed design discussion. Done means the drogue deploys at apogee and the main chute deploys later using an agreed design.

Written by the indexing model from the issue text.

Description

enhancement postponed

Requester: @NArmistead

Describe the solution you'd like
Right now, we simply try to deploy the drogue chute then the main chute back to back at apogee. We should be deploying the drogue chute at apogee and the main chute later. A proper design discussion about this during a meeting would probably be a good idea.

This also might require modifications to the PRESET_DATA struct if we add something like a deployment altitude.

Describe alternatives you've considered
Uhhh... a very long recovery walk

Additional context
N/A

Points of Contact
FC Rev 2 lead - @NArmistead

Dominant language
C
Stars
8
Forks
6
Avg merge
6d 15h
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SunDevilRocketry/Flight-Computer-Firmware

All issues in SunDevilRocketry/Flight-Computer-Firmware

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.