Building a satellite is a big adventure for students like us! Even so this enterprise could seem demanding and perhaps even intimidating, we have to manage this just as any other project. And it starts with defining what are the system functionalities.
Actually, there are a few standard core functionalities in the world of nanosatellites:
As suggested just before, the satellite needs to communicate with Earth as well. What would be the point of a – more or less – expensive space program if our device were not able to transmit us its mission results? That’s precisely the role of the Telecommunication system (TCS). Its antenna sends data from the satellite to a station based on Earth (called the Ground Station or GS). Data can also be sent from the Ground Station to the satellite’s TCS to transmit orders.
Finally, we often name On Board Computer (OBC) the entity dedicated to the whole satellite management. OBC is in charge of other modules’ supervision; it is our CubeSat’s brain!
Here is a short video about these entities:
And what now? Well, that depends on the mission’s goals! Here at ECEĀ³Sat, our payload is a deorbiting system.
These entities constitute a logical software architecture, but does not necessarily reflect the final hardware distribution. Several functionalities can be handled by the same microcontroller; conversely one functionality can be implemented with several pieces of hardware according to its needs. Gathering or splitting entities among different boards, and communication between these boards, are a serious strategic concern. An article dedicated to this architecture design will be released soon, stay tuned!