Ignition: Add non-blocking parachute deployment check

Open
#37 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
c
Domain
embedded-iot

Research direction

Start by reading the ignition driver and the flight-loop entry point, then compare the alternative implementation in mod issue 133. Trace how parachute deployment currently asserts and deasserts, and define the state-machine transitions needed for synchronous updates. Done means deployment checks no longer block for roughly 100 ms and assertion and deassertion occur through the flight loop.

Written by the indexing model from the issue text.

Description

enhancement

**Requester: @ETSells **

Describe the solution you'd like
Our current parachute deployment logic is blocking for upwards of 100ms, which is unacceptable in flight. We should alter the ignition driver to be able to assert and deassert based on a state machine that is updated synchronously by the flight loop.

Describe alternatives you've considered
The alternative implementation of this issue is https://github.com/SunDevilRocketry/mod/issues/133.

Additional context
N/A

Points of Contact
FC Rev. 2 Project Lead: @NArmistead
Driver maintainer: @ETSells

Dominant language
C
Stars
2
Forks
0
No merged PRs in 30d

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/driver

All issues in SunDevilRocketry/driver

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.