CanSat Ireland: the satellite must survive the whole mission

Editorial overview

CanSat Ireland compresses a space mission into an object the size of a drinks can. Teams have to integrate power, sensors, communications and a recovery system, then operate the device during a launch and descent. The required measurements of air pressure and temperature provide a common technical baseline, while the secondary mission gives each team room to choose a more ambitious question or capability.

That structure is what makes the competition valuable. A sensor that works on a classroom desk is not enough if the radio link fails, the enclosure breaks, the parachute behaves unpredictably or the team cannot turn transmitted readings into a defensible analysis. ESERO Ireland supports participating schools with a starter kit, introductory training, mentoring and access to partner colleges, but students still need to make the systems work together.

CompeteMap sees CanSat as a strong choice for TY and Senior Cycle students who want engineering to feel consequential. It suits mixed teams because mechanical design, coding, electronics, scientific analysis, documentation and presentation all matter. The main trade-off is commitment: this is not a one-afternoon build. A good team needs repeated integration tests and must be willing to treat failures as mission data rather than as embarrassment.

Quick Facts

For current dates, eligibility and registration details, see the CanSat competition page.

What the mission actually asks

The primary mission requires measurements of air pressure and air temperature during descent, transmission to a ground station and analysis after recovery. The secondary mission is the team's opportunity to differentiate its design. ESERO gives examples such as GPS, radiation measurements, telecommand functions or a controlled landing system, but the best choice is the one the team can test properly.

Start by writing interfaces, not shopping lists. Decide how the sensors connect to the processor, how often data will be sampled, what will be transmitted, what happens when packets are lost and how the structure protects the electronics. A modest secondary mission with reliable evidence is more persuasive than several unfinished features.

Build around integration tests

Test subsystems separately, then combine them early. A useful sequence is sensor calibration, radio range, power endurance, data logging, drop testing and full mission rehearsal. Keep a configuration record so that the team knows which software version, battery, parachute and enclosure produced each result.

The presentation should explain decisions as clearly as the hardware demonstrates them. Graphs need units, axes and an account of uncertainty. If a subsystem failed, show how the team diagnosed it and what changed. That is often stronger engineering evidence than pretending the mission proceeded perfectly.

Key Takeaways

• Treat CanSat as one connected mission, not separate coding and construction tasks.
• Choose a secondary mission that can be tested repeatedly with the available time and equipment.
• Reserve time for full rehearsals, data analysis and presentation, not only assembly.
• Use the CompeteMap page and official ESERO Ireland page for the latest season information.

Sources checked

• https://esero.ie/projects/cansat/
• https://cansat.esa.int/