Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

FSM: Add additional states & transitions around parachute deployment

未关闭
#364 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 4 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
c
领域
embedded-iot

调研方向

Start by locating the top-level flight computer FSM and its state transition logic; the issue gives the current enum and describes the desired states, deployment triggers, and transition criteria. Read the dual deploy EPIC referenced in the issue for related context. Done when the FSM handles drogue deployment, main deployment, descent, and the terminal LANDED state as specified.

由索引模型根据 Issue 内容生成。

描述

advanced enhancement

Version: v2.8.0

Describe the feature you'd like
Currently, our top-level FSM uses the following states:

typedef enum __attribute__((packed)) _FLIGHT_COMP_STATE 
	{
	FC_STATE_INIT = 0, // startup
	FC_STATE_IDLE = 1, // terminal
	FC_STATE_CALIB = 2, // calibration
	FC_STATE_LAUNCH_DETECT = 3, // wait for launch
	FC_STATE_ASCENT = 4, // powered ascent
    FC_STATE_COAST = 5, // unpowered ascent
	FC_STATE_APOGEE = 6, // runs once at apogee (FC_STATE_DEPLOY_MAIN) -- should change to wait for drogue deployment accel spike OR main if single deploy rocket
	FC_STATE_DESCENT = 7, // parachute descent
    FC_STATE_LANDED = 8 // on ground; currently unused
	} FLIGHT_COMP_STATE_TYPE;
	_Static_assert( sizeof(FLIGHT_COMP_STATE_TYPE) == sizeof(uint8_t), "FLIGHT_COMP_STATE_TYPE size invalid.");

We should update the latter half of this FSM such that
APOGEE -> normal FC state that triggers drogue deployment (if configured) and transitions out once drogue is deployed (even if by external avionics)
DESCENT -> DROGUE_DESCENT (no other change except state transition becomes main deployment criteria)
after DESCENT, insert MAIN_DEPLOY (trigger main (if configured) and transition out once main is deployed. the transition out of MAIN_DEPLOY should also be allowed for DROGUE_DESCENT if main deployment not configured).
after MAIN_DEPLOY, insert MAIN_DESCENT (same as drogue descent except state transition becomes ground hit criteria)
Implement LANDED state (no transitions out)

Describe alternatives you've considered
N/A

Additional context
Should theoretically be worked in tandem with dual deploy EPIC.

Points of Contact
FC Rev. 2 Project Lead, Flight Logic SME: @NArmistead
Flight Logic & State Transitions SME: @ETSells

主要语言
C
星标
8
派生
6
平均合并
6 天 21 小时
30 天内合并 PR
9

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

SunDevilRocketry/Flight-Computer-Firmware 的其他 Issue

查看 SunDevilRocketry/Flight-Computer-Firmware 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。