Join Us

The Power subsystem is responsible for the design, analysis, and implementation of the power system of the satellite. This will involve both systems-level design and analysis (electrical interfaces, system power and data requirements) and subsystem-level design and testing.

The Communication subsystem works to ensure a proper system from the ground station radio to the flight radio. This will include the design and testing of antennas, radios and testing along with flight software. UBNL has developed its own open-source radio for flight, the Little Free Radio (LFR) (lfradio.space)

Every satellite needs a robot brain - and this is the group that programs it! We write C/C++ code which runs on embedded systems which manage the automatic behavior of the satellites (pointing, navigation, etc.), collecting and parsing telemetry, and then on-board processing of any scientific data. Focus on high reliability software systems.

The Mission Control Software subsystem is responsible for writing code that supports the satellite on the ground. Create a GUI that a ground operator can use to view telemetry, log data, and control the mission. You will use program languages such as Ruby and mission control software such as Ball Aerospace COSMOS.

The Command and Data Handling subsystem designs and assists in testing the of the flight computer and peripheral systems, such as storage, sensors, and actuators. You will learn about the design, programming, testing, and troubleshooting of embedded systems, analog and digital circuits, and PCBs.

The Structures subsystem is responsible for the structural design, implementation, and analysis. This will entail work at the systems level (working with other subsystems and program management to define interfaces and requirements) and at the detailed design level (creating models and drawings of the spacecraft, running structural and thermal analyses, machining or purchasing structural components).

The thermal subsystem uses different analysis techniques to find the projected temperature of the satellite while in flight. The development of the satellite design revolves around ensuring that the satellite remains within operational temperatures.

Almost every satellite mission will require knowledge of where the satellite is and where it's pointed at all times. The Guidance, Navigation and Control (GNC) subsystem is responsible for designing the satellite's Attitude Determination and Control Systems (ADCS) with various cubesat-viable sensors and actuators, such as sun sensors, MEMS gyroscopes and magnetic torquers, so that we can meet that requirement and carry out the mission.

Mission Operations is the team that prepares and executes all in-flight operations for the satellites. If you decide to join Mission Operations, you might be involved in design of the Concept of Operations, Exception development and handling procedures, fault tree development, and, of course, performance of in-flight operations through mission control software after launch. Mission Operations is a truly interdisciplinary team as you must learn about every subsystem. All majors are welcome and no previous experience is necessary.

The Integration members are responsible for soldering circuit boards, assembling spacecraft and components, and fabrication of wire harnessing. Most hands on of all positions. The Testing members will help develop, document, execute, and analyze tests of various hardware for our satellites. The components and systems under test will encompass all those on the satellite including electronics, sensors and actuators, and communication systems. The tests performed will be vital in meeting system level testing deliverables for upcoming reviews for each satellite. The subsystems provide training and the only pre-requisite is motivation.