Connect the platform and payload

Amazonia-1 reached orbit on 28 February 2021 aboard India’s PSLV. INPE designed, integrated, tested and operates this Brazilian Earth-observation satellite. Its mission combines environmental imaging with a second goal: proving the Plataforma Multimissão, or PMM, as a reusable service platform. Brazilian spacecraft development and an Indian launch service are complementary roles in the same mission.

The service module supplies common spacecraft functions, while the payload module carries imaging, recording and image-transmission equipment. Consider the distinction as a design question. A camera needs electrical power, a stable viewing direction and an acceptable temperature before its measurements can be useful. Those services matter even if the next mission carries a different camera. Reusing a platform can preserve engineering knowledge, but does not make every instrument an automatic fit.

INPE describes the wide-field camera’s heritage in the CBERS program. A DC/DC converter adapts the power arrangement for its remote telemetry unit because the two spacecraft families have different electrical architectures. Hardware with flight experience can still require new interface engineering. Reuse is a starting point for qualification, not permission to skip it.

Try an original power-budget exercise. A fictional payload needs 120 watts, while its converter is 80 percent efficient. The input must supply 120 ÷ 0.8 = 150 watts, leaving 30 watts as conversion loss. These are teaching values, not Amazonia specifications. A team budgeting only the camera’s demand would omit a load on both the electrical and thermal systems. The interface affects more than the shape of a connector.

An interface changes the power and heat budget

Amazonia-1’s recorder holds images when no receiving station is visible and can send stored data during later contact. Observing and downlinking therefore need not occur at the same instant. Storage makes geographically distant observations possible, but it remains finite. The schedule must account for both acquiring data and clearing space for later acquisitions.

Imagine a fictional recorder with 12 units of free capacity. One observing period adds seven units and a later period adds six before any downlink. Thirteen units would exceed the available capacity by one. A planner could reduce acquisition, move a downlink earlier or change priorities. Merely having a radio does not remove a storage bottleneck. Keep the time of observation attached to a file even when its delivery happens much later.