NuX-1: connect small messages from remote places

NuX-1, built by NuSpace, launched on Transporter-3 on January 13, 2022. Its LoRaWAN Internet of Things payload addressed connectivity beyond established ground networks. The spacecraft also hosted Aliena’s miniature Hall-effect thruster for technology validation. These were different tasks on one platform: collecting small messages and testing a propulsion device. The launch provider’s integration record identifies the payloads without proving every intended experiment succeeded.

The Internet of Things connects devices that measure or report conditions. A remote agricultural sensor might transmit a timestamp and soil measurement instead of a continuous video stream. That changes the communications problem. Short, occasional reports can be useful even when contact is intermittent. A spacecraft passing overhead can offer another route for data where a nearby terrestrial gateway is absent, provided the device and satellite can communicate reliably.

Consider a fictional sensor that records one measurement each hour. It creates six records before a useful satellite contact. Sending only the latest value gives the user one recent measurement; sending the stored sequence preserves changes across all six hours. Each record needs its own measurement time. The time a server receives a packet — open definition is not necessarily the time the physical condition was measured.

Now suppose the sensor sends all six records, but the receiving system acknowledges only five. A retry may restore the missing record, yet it may also repeat an already received one. Identifiers let the service distinguish a duplicate from a genuinely new measurement. Buffer size, battery use, retransmissions and delivery deadlines become parts of the design. The spacecraft is one link in that larger information system.

Keep the measurement with its history

A hosted thruster needs electrical power, commands and telemetry from its carrier. Its operations can also affect attitude or other activities. A mission team must define interfaces and schedule experiments so that one payload’s test does not unexpectedly prevent another from collecting data. The miniature size of the hardware does not remove the need for those agreements. Integration tests should exercise the combined system under representative conditions.

NuX-1 makes a useful distinction between demonstrating a component and supplying a dependable service. Reaching orbit confirms a launch milestone; a received sensor report confirms a particular communication event. A sustained connectivity claim needs records of availability, delivery delay and data completeness. The same discipline applies to the hosted propulsion experiment: its intended presence is documented, while claims about performance require the corresponding measurements rather than the launch announcement alone.