Introduction

A CubeSat is a miniature satellite that is classified with sizes of U (1U = ~10 cm). A 1U CubeSat has dimensions of 1U by 1U by 1U; or 10 cm by 10 cm by 10 cm. CubeSats nowadays range from sizes of 1U up to 12U. Our project team will be focusing on sizes of 3U or below. If you would like to read more about CubeSats, please read chapter 1 of the NASA101 paper linked here.

CubeSats are traditionally launched through the NASA CubeSat Launch Initiative (CSLI), also known as an ELaNa Paper. Our CubeSat will be launched by applying to the CSLI through an Announcement of Partnership Opportunity (AoPO). Usually an AoPO opens in early August and closes around 4 months after it is announced, usually in mid-November. If you would like to read more about the application and design process please read chapter 2 of the NASA 101 paper linked here.

CubeSats can have a variety of payloads, with the team deciding on the chosen payload at the beginning of the project. Our project is to classify unclassified space debris in orbit using images and artificial intelligence to optimize the data sent to the ground station. You can read more about the payload in the “Experiment/Payload” section of this document.

Team Structure

The overall CubeSat team is organized into various subteams, each with their own expertise and focus. This has been modeled after the standard systems and components of a CubeSat. Although this organizational framework is very helpful, please note that these are not strict cut-offs. You may work on different aspects of different subteams, work with and alongside other subteams, etc. As such, subteam leads are chosen to oversee a subteam and deliver the expected components with their teams by the deadline.

There is no limit to how many subteams a single individual can join and be a part of, but be aware that the time commitment to each subteam may be quite high. And that it may not be feasible to participate fully in more than one subteam.

Subteams

Attitude Determination Control Systems (ADCS)

Technical Skills

To excel in the ADCS subteam, you should possess or be willing to develop skills in the following areas:

Mathematics and Control Theory: A solid understanding of mathematics, especially linear algebra and control theory, is essential for designing and implementing control algorithms.
Programming: Proficiency in programming languages like C/C++ and experience with software tools for simulations and control system development.
Sensor Integration: Familiarity with sensors commonly used in CubeSat ADCS, such as gyroscopes, magnetometers, and sun sensors, as well as the ability to integrate these sensors into the system.
Simulation Tools: Knowledge of software tools like MATLAB, Simulink, or Python for simulating and testing control algorithms.
Hardware Integration: Understanding of hardware components like reaction wheels, magnetic torquers, and power management systems used in CubeSat ADCS.

Team Collaboration

The ADCS subteam collaborates closely with other subteams, specifically the Payload team and the Command and Data Handling team, to ensure that our CubeSat's orientation is optimized for data collection and communication with Earth. Effective communication and teamwork are essential for the success of our mission.