Capturing Model Rocket Telemetry Using a Raspberry Pi Zero (Part 1)

Written by someone who has watched "Apollo 13" more times than he'd like to admit.

October 3, 2020

Q&A on Hacker News about this project

The Rocket!

It seems like everyone's getting back into old hobbies in the time of COVID-19. For me, that's come as model rocketry, something I spent quite a bit of time doing growing up in the Appalachian Mountains of Pennsylvania. On a whim, I bought a model rocket a few weeks back, built it, and launched it while visiting home in PA. Armed with excitement from this rediscovered hobby – along with the admiration of two young nieces who were sure the rocket was going to the moon – I decided it was time to kick things up a notch and custom build a rocket and telemetry module.

Hardware Selection

Basing this entire project around a Raspberry Pi Zero was an obvious choice to me because of its light weight and excellent ecosystem of easily-programmed sensors available. From there, it was a matter of selecting the types of sensors and other hardware I'd need to build into this project. I came up with the following:



Telemetry Transmission/Reception

With all of these components chosen, I wired them up to a Raspberry Pi Zero. (First via breadboard for testing then soldered for final assembly.) For more on the wiring, see the appendix.


The air hardware is wired to the following Raspberry Pi pins:

  • PowerBoost 500 Basic:

    • 5v -> Pi 5V
    • Ground -> Pi Ground
  • BMP388 (SPI 0)

    • VIN -> Pi 3V
    • GND -> Pi GND
    • SCK -> Pi SCLK
    • SDI -> Pi MOSI
    • SDO -> Pi MISO
    • CS -> D5
  • LSM303 (I2C)

    • VIN -> Pi 3V
    • GND -> Pi GND
    • SCL -> Pi SCL
    • SDA -> Pi SDA
  • Camera

    • Pi Camera ribbon connection
  • RFM95W (SPI 1)

    • VIN -> Pi 3V
    • GND -> Pi GND
    • SCK -> Pi SPI1 SCLK
    • SDI -> Pi SPI1 MOSI
    • SDO -> Pi SPI1 MISO
    • CS -> Pi D24
    • RST -> CE0

The ground hardware, much more simply, is wired to the following Raspberry Pi pins:

  • RFM95W (SPI 1)

    • VIN -> Pi 3V
    • GND -> Pi GND
    • SCK -> Pi SCLK
    • SDI -> Pi MOSI
    • SDO -> Pi MISO
    • CS -> Pi CE1
    • RST -> Pi D25

Software Development

Before building the rocket and housings for the hardware, I needed to test the electronics and architect a software solution that would optimize for a high data sample rate. With that goal in mind, I devised the following:

Software Design Graphic

To see the source, check out the GitHub Project. I've named the software White Vest after the iconic white vest that flight director Gene Kranz wore during Apollo 13.


In the sensor reading thread, I access two devices, the BMP388 and LSM303. Those values for pressure, temperature, acceleration, and magnetic orientation get added to a thread-safe queue and a thread-safe single value holder. This thread is able to capture about 4 sets of sensor readings per second. (Unfortunately the BMP388 reads out data quite slowly.)

A separate thread reads the thread-safe queue and logs that data to a CSV file on the device. Further, an additional thread reads that thread-safe single value and transmits that data via the RFM95W as floats packed into a byte array. (I only transmit the most-recently-read data rather than everything from the queue because I want the ground receiver to have near-realtime data.)

Finally a third thread records video from the camera. All data recording terminates 30 minutes after program start, but it will continue to transmit telemetry.


On the ground, the RFM95W receives those transmitted byte arrays,unpacks them to floats, and puts the data into a thread-safe queue. Another thread reads from that thread-safe queue, logs that data to a CSV file, and appends the data to a thread-safe data buffer.

A third thread acts as a webserver to serve the dashboard web app, and a final thread listens for websocket connections to stream the contents of the data buffer as data becomes available.

Hardware Assembly

With the electronics tested and operational, I designed a set of 3D printable components to mount the telemetry module in a rocket. Based on the Estes builders' kit I was using, I knew 4cm across was the widest body I could support. Therefore I designed a mounting system to support a tube of that width.

After a few iterations, I ultimately designed the following parts for printing:

Designed Hardware

Those pieces, when assembled with the electronics, look like this:

Assembled Hardware

Rocket Design

The rocket has two main components: The booster section, which is the bottom half of the rocket, and contains the motor, fins, and recovery parachute. That section is joined via a coupler (one of the 3D-printed parts) to the upper-half of the rocket, which is the payload section containing the telemetry module.

After the main launch motor burns out, the engine fires an ejection charge up into the rocket. That force pushes the parachute up and blows out the coupler, forcing the two sections to separate and the parachute to deploy. (Both sections are attached to the parachute via shock cord.)

Rocket Design Graphic

The graphic above is from my design in OpenRocket, which is an open source tool for designing and testing model rockets. To learn more about the principles of model rocket design, I suggest the classic book, Handbook of Model Rocketry, which is considered a go-to resource for the hobby.

Based on this design, using an Estes D12-5 motor, I could expect this rocket to top out at around 90 meters, or about 295 feet. There are more powerful motors available, but those require more sophisticated launch controllers and this was just first test.

Once assembled, the rocket looked like this:

Assembled Rocket Graphic

To see the results of launching this, check out Part 2