ZACUBE: connect student engineering to useful signals

Cape Peninsula University of Technology’s ZACUBE work connects postgraduate engineering with spacecraft development. ZACUBE-1, also called TshepisoSat, launched in November 2013 and included space-weather research and technology demonstration. ZACUBE-2 followed in December 2018 with maritime radio-reception experiments. Their shared institutional history does not mean the two spacecraft carried identical instruments or answered identical questions.

The CubeSat format helps teams arrange compact subsystems within a standardized physical envelope. It does not make a mission effortless. Power, antennas, software, thermal behavior and a usable ground link still have to work together. Student participation is especially valuable when learners follow that whole chain rather than treating assembly, launch and operations as unrelated classroom exercises.

ZACUBE-2’s stated objectives included reception of Automatic Identification System and VHF data-exchange messages. AIS is a cooperative maritime reporting system: equipped vessels broadcast information that can help observers understand traffic. Receiving a report is different from independently photographing a ship. The information must be associated with its sender and timestamp, and the receiving system must cope with missed or overlapping transmissions.

Imagine a teaching dashboard displaying a vessel report measured at 10:00. The satellite forwards it at 10:04, and processing finishes at 10:06. At the moment it appears, the observation is six minutes old. Those times are invented, not ZACUBE performance figures. A dashboard that labels only the display time could make an older position look current. The measurement time should remain attached to the message as it travels through the system.

Keep the observation timestamp

Suppose the same vessel sends another valid report at 10:07, but a receiving station does not obtain it until 10:12. The newer observation may still be more useful than the earlier one, yet neither supplies a continuous track between reports. A gap can arise from geometry, radio interference, scheduling or equipment behavior. Silence alone does not prove that a ship has disappeared or that a satellite has failed.

To evaluate this family, ask what each mission attempted, which tests produced usable data, and how the ground team interpreted the results. SANSA’s older mission page contains commissioning — open definition language from an earlier stage; it should not be read as a live status feed. The lasting lesson is about information quality: small satellites can contribute useful observations, but a trustworthy service preserves timestamps, identifies missing coverage and checks the entire route from transmitter to reader.