FSM: Add additional states & transitions around parachute deployment

Abierto
  • ¿Algo no está bien?
#364 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 3 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
c
Área
embedded-iot

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
C
Estrellas
8
Forks
6
Merge medio
6 d 20 h
PR fusionados (30 d)
9

Preparar el entorno

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de SunDevilRocketry/Flight-Computer-Firmware

Todos los issues de SunDevilRocketry/Flight-Computer-Firmware

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.