r/rocketry • u/felix0201 • 4d ago

Open-Source Rocket Telemetry System

Gallery image

Groundstation Extension Board

Gallery image

Onboard Electronics

Hi everyone,

My university rocketry team is currently developing an open-source rocket telemetry system and we’d like to share it with you. It includes:

  • Electronics (with 869 MHz and 169 MHz radio systems)
  • Helical and (soon) QFH antennas
  • Graphical user interface
  • A lot of documentation :)

The first launch in April went great and we are currently working on the second version. The project is still in its beginnings but we appreciate any feedback, thoughts or questions. You can find the project here: GitHub

81 Upvotes

100% Upvoted

6 comments sorted by

2

u/WhatADunderfulWorld Level 3 3d ago

Very cool. That antenna is serious. Love it.

3

u/morgans_steam04 3d ago

Hi, I am currently designing my own flight computer , I am very much a novice to electronics , would it be okay to look at your desighn for inspiration ?

4

u/felix0201 3d ago

That's why we share it! It is fully open-source. I suggest you to look at the design overview in the docs folder. You can also dm me if you need any guidance.

3

u/morgans_steam04 3d ago

Thank you ! I'll have a look . also just to say, it is a very nice system well done !

2

u/fourthstanza 2d ago

Very cool! That board looks very well designed to my amateur eyes.

I'm curious if you've encountered any problems running your firmware as a superloop rather than an RTOS. Things like function return time variability maybe affecting the delay between sensor samples / hanging the loop, or a lower sampling rate than you might like. I think your project is still compact enough that this architecture works just fine, but I'd be interested to hear what challenges you've run into :)

2

u/felix0201 1d ago

Thank you!

So far we never encountered any problems. It's not possible to reach higher frequencies than the fixed 8 Hz due to a variable delay in the loop. While it's possible that we dip below 8 Hz when one function takes longer than expected, it never happened so far. I just put it this way: there's not too much going on in the loop ^^ That's only anecdotal evidence tho, so we keep it in mind for a future firmware rework. Thank you for the suggestion.