Session
Weekday Session 8: Recent Launches
Location
Utah State University, Logan, UT
Abstract
OPS-SAT is a 3U CubeSat launched by the European Space Agency (ESA) on December 18, 2019. It is the first nanosatellite to be directly owned and operated by ESA. The spacecraft is a flying platform that is easily accessible to European industry, institutions, and individuals, enabling rapid prototyping, testing, and validation of their software and firmware experiments in space at no cost and no bureaucracy. The spacecraft is equipped with a full set of sensors and actuators including a camera, GNSS, star tracker, reaction wheels, high speed X band and S band communication, laser receiver, software defined radio receiver, and a 800 MHz processor with a reconfigurable FPGA at its heart. Conceived to break the “has not flown, will not fly” cycle, OPS-SAT has spearheaded many firsts. One of the reasons for the success of CubeSats is that they have changed the rules on who can access space; opening a world that used to belong to a few governmental and commercial players to smaller and newer ones. This is also true within space agencies as well as outside them. It would have been unthinkable just a few years ago for an ESA center, whose prime job is to control ESA satellites, to specify, design and launch a mission with the sole aim of improving mission operations. However, it was never going to be easy. This paper describes the events of the OPS-SAT mission starting from a few weeks before launch, when some last-minute non-compliances almost stopped the mission, through the LEOP and to the end of commissioning. During the whole process many challenges had to be overcome and it took ten months to complete commissioning compared to the initially planned three months. Problems started in the first pass, no UHF packets were received from the spacecraft and bad communications plagued the mission for many months. However, during this time a great deal of progress had already been made thanks to the ingenuity of the Flight Control Team (FCT) and the supporting industry. Given the unpredictable and short uplink possibilities a framework evolved whereby commissioning of the payload was done using the experimenter infrastructure rather than the flight control infrastructure.
OPS-SAT LEOP and Commissioning: Running a Nanosatellite Project in a Space Agency Context
Utah State University, Logan, UT
OPS-SAT is a 3U CubeSat launched by the European Space Agency (ESA) on December 18, 2019. It is the first nanosatellite to be directly owned and operated by ESA. The spacecraft is a flying platform that is easily accessible to European industry, institutions, and individuals, enabling rapid prototyping, testing, and validation of their software and firmware experiments in space at no cost and no bureaucracy. The spacecraft is equipped with a full set of sensors and actuators including a camera, GNSS, star tracker, reaction wheels, high speed X band and S band communication, laser receiver, software defined radio receiver, and a 800 MHz processor with a reconfigurable FPGA at its heart. Conceived to break the “has not flown, will not fly” cycle, OPS-SAT has spearheaded many firsts. One of the reasons for the success of CubeSats is that they have changed the rules on who can access space; opening a world that used to belong to a few governmental and commercial players to smaller and newer ones. This is also true within space agencies as well as outside them. It would have been unthinkable just a few years ago for an ESA center, whose prime job is to control ESA satellites, to specify, design and launch a mission with the sole aim of improving mission operations. However, it was never going to be easy. This paper describes the events of the OPS-SAT mission starting from a few weeks before launch, when some last-minute non-compliances almost stopped the mission, through the LEOP and to the end of commissioning. During the whole process many challenges had to be overcome and it took ten months to complete commissioning compared to the initially planned three months. Problems started in the first pass, no UHF packets were received from the spacecraft and bad communications plagued the mission for many months. However, during this time a great deal of progress had already been made thanks to the ingenuity of the Flight Control Team (FCT) and the supporting industry. Given the unpredictable and short uplink possibilities a framework evolved whereby commissioning of the payload was done using the experimenter infrastructure rather than the flight control infrastructure.
