Communications Module

Welcome to the 2nd edition of the NEUDOSE hardware series! This week’s hardware post is focusing on the communications module, which can be seen in images 1 and 2. Keep reading to learn more about this hardware! 

Q: What is the Communications Module?

A: The communications module is the radio onboard the NEUDOSE CubeSat mission. The module contains two independent radio systems; one for uplink (receiving commands on the satellite) and another for downlink (transmitting data out of the satellite). This module works in a full-duplex mode meaning we can transmit and receive information at the same time.

Q: What is the Communications Module used for?

A: The communications module is what allows us to talk with the NEUDOSE CubeSat while in orbit.  It has three key objectives during the mission:

  1. the reception of telecommands (i.e. operational commands) onboard the satellite as it travels 400km+ overhead,

  2. obtaining vital telemetry and subsystem health information to inform ground-based operators on the satellite status, and

  3. relaying the scientific data generated by the payload to the ground for further analysis.

Q: What are the improvements since the last version?

A: Since the last revision, the communications module has undergone a major design overhaul. Many aspects of the design required an upgrade or modification to meet the capabilities of the NEUDOSE mission. An upgrade to the radio frequency (RF) front-end has led to improved signal quality, strength and efficiency. The digital systems, such as the microcontroller and sensors, have been modified to handle mission tasks. This revision strikes a balance between performance and efficiency, and the ability to do more with less is at the heart of each design choice.

Q: What progress have we made during quarantine?

A: Since quarantine began, the team has fabricated and manufactured the latest revision (rev 3.0). The module is currently undergoing testing, software development, and fine-tuning to ensure each component works as intended. The lessons learned from rev 3.0 have allowed us to develop our next and hopefully final revision, rev 3.1. The next revision aims to improve the subsystem design flaws and manufacturability for flight-ready hardware.