KNACKSAT: university satellites become shared laboratories

King Mongkut’s University of Technology North Bangkok developed KNACKSAT as a university satellite project. The first KNACKSAT launched in December 2018. Its successor, KNACKSAT-2, used a different route: JAXA records its release from the International Space Station on February 3, 2026. The second spacecraft was developed through collaboration involving the university, NBSPACE and Japan’s Kyushu Institute of Technology.

KNACKSAT-2 is a three-unit CubeSat designed to host ten payloads. JAXA lists communications, imaging and radiation-related experiments among its objectives. A shared platform lets several teams test equipment without each building an entire spacecraft. That opportunity also creates a coordination problem: experiments must share power, onboard time, storage and downlink capacity within a small vehicle.

Imagine a fictional platform with twelve watts available for experiments after essential spacecraft functions are supplied. One experiment needs eight watts and another needs six. Running both together would require fourteen watts, exceeding the assumed allowance by two. A schedule that runs them at different times may help, but the team must also account for startup behavior, heat and the time required to collect useful data.

This example is not KNACKSAT-2’s power specification. It illustrates why a hosted-payload mission needs interface agreements and operating rules. The clean-room photograph shows KNACKSAT-2 during preparation in October 2023. It documents hardware at a particular stage; neither the photograph nor the number of payloads proves that every later experiment worked as intended. Results require measurements and a clear success criterion.

Shared resources need a plan

JAXA identifies KNACKSAT-2’s deployment under J-CUBE, an arrangement involving JAXA and the University Space Engineering Consortium. Other satellites in the same release campaign used different frameworks, including KiboCUBE. Sharing a day or deployment mechanism does not make the programs identical. A useful history preserves the actual partner arrangement instead of assigning every small satellite to the most familiar program name.

Successful separation from the station establishes an important flight event. Subsequent contact, commissioning and experiment results answer different questions. A camera returning one image may demonstrate part of its function without proving long-duration reliability; another payload can succeed or fail independently. Reporting the evidence experiment by experiment makes the university program more informative and helps later teams understand exactly what experience is available to reuse.