The Electronics team is responsible for the design, development, and integration of the rocket’s electronic systems. This includes the complete flight computer, consisting of the hardware (including PCB), firmware, and application software responsible for monitoring (and long term controlling) the rocket during flight. The team is also responsible for the ground station, including its firmware, desktop application, and possibly PCB, which provides communication, telemetry, monitoring, and control capabilities during testing and launch operations. Additionally, the team manages the electrical interfaces between the various rocket subsystems, ensuring reliable power distribution, communication, sensor integration, and data acquisition. The team is responsible for the testing, validation, and integration of all electronic systems, as well as ensuring that the electronics operate reliably throughout ground testing, launch, and flight.
As for the specifics, Phobos is our current project, which includes two flight computers (FCs), one designed and assembled by us, and one bought as commercial off-the-shelf (COTS). See the following pages for further information. Note, this may contain some deprecated information.
We mainly use teams for communication and storing relevant documents and various other stuff.
We mostly work by writing code, and to allow multiple people working on the same project we use Git. We put our code base, along with other helpful features in our GitHub page CAESAR-Chalmers.
These are the repositories that you will need to work with in electronics for the Phobos project:
The tasks we need to perform to build our FC is organized with GitHub projects and is done so here Phobos tasks. These tasks are beinged worked on and will continously be worked on as we discover new features we need or bugs that needs to be taken care of.