Open ivogeorg opened 2 years ago
Have to design the WiFi streaming for the demo @NotfatPrince @Christopher-Dauchter
@PaulAJanes This should give some more context of what you are doing...
The Flight Executive (FE) is:
telemetry
, camera
, and rockblock
being packages it imports. The structure should be like this (with any other necessary sub-packages):
balloonsat/
|--executive.py
|--telemetry/
|---__init__.py
|---telemetry.py
|--camera/
|---__init__.py
|---camera.py
|--rockblock/
|---__init__.py
|---rockblock.py
enum
class. This is a tentative list of the states: POWER_ON, STARTUP, PREFLIGHT_CHECK, MISSION, POSTFLIGHT
. The transitions between states are strictly identifiable functions.Major FS design points:
There should be a way to start and stop the FE without Ctrl+c. This is potentially just as damaging as hard shutdown of the RPi (from the perspective of the fexecutive.py
process, it's the same thing).
Potential solutions:
fexecutive.py
code, there can be a time interval argument for the flight loop to stop when the time since the start has elapsed.
Description
Main flight loop has to be stable and easy to recover. Preferably, multi-threaded (RPi 4 has a quad-core processor). It should integrate all components (see Deliverables for details).
Knowledge
multiprocessing
orconcurrent.futures.ProcessPoolExecutor
should be used.Deliverables
A main program that manages the following tasks:
Time estimate
12 man-hours