Temuulel: turn experience abroad into a domestic engineering process

The Temuulel project began in 2019 with a goal distinct from Mazaalai’s first international training mission: develop a small satellite inside Mongolia. The team’s 2022 conference abstract describes a one-unit CubeSat with imaging, remote data collection and technology experiments. It also includes a launch forecast; that forecast is not treated here as evidence that the spacecraft flew.

Domestic development involves more than selecting a national name. A team needs to make design decisions, document interfaces, assemble and test the hardware, and retain the knowledge required to operate or improve it. Purchasing a component can be entirely compatible with local engineering. The important question is which decisions, procedures and capabilities the project enables the local team to carry forward.

An imaging goal depends on power, pointing, storage and communications. A camera may produce useful pictures on a bench yet fail to fit the satellite’s operating plan. The team must specify when the instrument can run, how the spacecraft is oriented and what happens to its output while no ground station is available. One working subsystem is not the same as an integrated mission.

Consider an invented storage budget: eight images of 750 kilobytes each require six megabytes when decimal units are used. If two megabytes are reserved for logs and software in an eight-megabyte usable store, the images fill the remaining allowance. That leaves no extra margin for unexpected files or retransmission copies. These numbers illustrate planning; they are not Temuulel hardware specifications.

A storage budget needs room for the whole mission

Interface — open definition documentation gives cooperating teams a shared description of power, data and mechanical connections. A change to an interface can affect several subsystems even if the changed board works alone. A useful review asks whether the new configuration still meets requirements and whether the test evidence actually covers that configuration.

Temuulel’s published objectives include experiments involving onboard electronics and software. Such experiments require a way to recognize success, preserve diagnostic information and recover from a failed test where the design permits it. A student team should be able to explain what it expects to observe and how that observation differs from a misleading symptom. A development report can demonstrate this reasoning before flight; an orbital result needs a later operational record.