UaiSat: distinguish a signal from an environmental event

UaiSat was part of the MGSAT-1 mission, developed through UFSJ’s space-systems work with industrial participation including Uai Soluções e Integração. IFMG’s prelaunch account describes three intended uses: agricultural data collection, lightning and storm research with INPE, and validation of hardware and software in space. The spacecraft was among the passengers lost in the PSLV-C62 failure on January 12, 2026. Its objectives must therefore be taught as intended experiments, not returned orbital results.

The preparation record describes assembly followed by radio checks, qualification and integration for launch. These steps exercise different risks. A mechanical test can investigate whether an assembly tolerates a specified load, while a communications test checks whether the intended equipment exchanges information. Neither alone evaluates the scientific interpretation of an environmental signal. A mission carrying several experiments needs both common platform verification and tests specific to each measurement.

In an original design exercise, a farm sensor reports soil moisture every hour. Its record includes location, sampling depth, time, units and calibration — open definition information. A number taken near the surface after a brief shower may not describe moisture around deeper roots. Repeating that number through a satellite does not broaden the sensor’s physical sampling volume. Useful agricultural information depends on matching the measurement to the decision and the field conditions.

Suppose one device sends a normalized value of 0.3 while another sends 30 percent. They might express the same quantity, or they might use different definitions and calibrations. The receiver should consult the data definition rather than infer equivalence from familiar-looking numbers. A shared packet format is helpful only when the participating teams agree what each field means and how missing or invalid measurements are represented.

Trace a signal back to its cause

A lightning experiment faces a related interpretation problem: detecting a candidate signal is not automatically identifying a lightning event. Instrument noise, electrical activity aboard the spacecraft and external radio transmissions can complicate a measurement. Designers can characterize the instrument on the ground, record operating modes and compare candidate events with independent observations where suitable. The lesson’s reasoning is general; it does not assign an unverified instrument frequency or flight result to UaiSat.

Imagine that a detector reports a pulse every time the fictional spacecraft transmitter turns on, including during controlled tests with no simulated lightning. That correlation is a reason to investigate interference, not proof of a newly discovered storm pattern. Repeat the test with controlled equipment states and documented timing. UaiSat’s combined objectives make a useful systems lesson: the platform that powers and communicates an experiment can also influence what the experiment records, so engineers must test those interactions deliberately.