GS Projects

Two main sites that we are working

• ARO - Amateur Radio Operator
  • Audience: Amateur radio operators
• MCC - Mission Control Center
  • Audience: Orbital Team (leads or operators, whoever is most qualified to operate)

Functionalities

MCC

• See telemetry to diagnose problems
• See graphs and visualization to, in real time, see what’s right and wrong with the satellite
• Send and receive commands to the satellite
• It needs to be an interface for the operators to do their work effectively

ARO

• Provide an interface for Amateur Radio Operators who have registered with goverment
  • They can make ARO requests
• They do not get access to commands, that is MCC only
• They do not get access to telemetry, except for satellite position and next session

Backend

[MCC Only] Command Flow (From frontend to backend)

1. Choose command as inputs
2. Sent as a post request to backend via API
3. The command fills a packet by assigning it and ID and putting it into packet (this step was updated this sync, previously commands would be added when there was enough to fill)
4. When the packet is filled with commands, it is stored
   1. Packets can have the following states (named command status): Pending, Sent, Scheduled, Cancelled, Failed, Complete
      1. Pending: The packet is not completely filled with commands yet
      2. Fill in rest