Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

System Tests [v2.7.0]: Re-execute flash extract integration test

Cerrado
  • ¿Algo no está bien?
#335 3 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 3 días

@NArmistead ya está trabajando en esto.

Desde el 29/9/2026.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
c
Área
embedded-iot, testing-qa

Línea de trabajo

Start with the linked to_upload_preset.json base configuration and follow Tests 1–5 in the issue, using the flight computer hardware and flash extract workflow. Upload the continuity and extracted data for each test, then verify the results against requirements 3.1–3.6, including configurable logging, launch detection, rate limiting, calibration, and SDEC communication.

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

Descripción

verification

Base config:
to_upload_preset.json

-------Test 1-------

Upload a preset
Download a preset
Run flash extract
Observe continuity between all configs, upload here

-------Test 2-------

Upload base config
Arm FC
Wait 25 seconds
Run flash extract and upload data

-------Test 3-------

Upload base config
Arm FC, shake to trigger launch detect
Wait for flash to fill (blue LED)
Run flash extract and upload data

-------Test 4-------

Upload base config with rate limit set to 100
Arm FC, shake to trigger launch detect
Run for a few seconds, then reset
Run flash extract and upload data

-------Test 5-------

Upload base config with only pre-converted data enabled
Arm FC, shake to trigger launch detect
Run for a few seconds, then reset
Run flash extract and upload data

This test verifies the following requirements:

3.1:	The system shall utilize the Sun Devil Rocketry “lib”, “mod”, and “driver” libraries to interface with flight computer hardware.
3.2:	The system shall have an option to log flight data.
	3.2.1:	The data that is logged shall be configurable.
3.2.2:	The data logging shall begin when launch has been detected and end when flash is full.
3.2.3:	The data logging shall have a method to reduce the sampling rate and extend the period that data is logged.
3.3:	The system shall have a methods to detect if launch has occurred, including:
	3.3.2:	A method based on acceleration.
3.4:	The system shall calibrate the IMU and barometer before launch.
3.5:	The system shall have an interface to communicate with SDEC.
3.6:	The system shall change modes from the SDEC interface to the pre-launch mode when the external switch is activated.
Lenguaje dominante
C
Estrellas
8
Forks
6
Merge medio
2 d 3 h
PR fusionados (30 d)
7

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.