Skip to the content
6 layers50 × 81.3 mmBRS HW v1, the printed circuit board in 3D

Basic Rocket System

Size
50 × 81.3 mm
Copper layers
6
Thickness
1.6 mm
Parts
129
Nets
117
Pads
439
Tracks, vias
427, 31
Pours
5
Routed
Yes
KiCad
KiCad 8.0 (file 20240108)
Created
30 Jan 2025
Updated
18 Jun 2025

Overview

BRS HW v1 is an open-source printed circuit board by lucasnoce, from the lucasnoce/BRS_v1 repository on GitHub, published under the MIT licence. It is a 6-layer board of 50 × 81.3 mm with 129 parts on 117 nets, routed with 427 tracks and 31 vias.

It is built around the BMP280, TCA9534PW and W25Q128JVSIQ, with the AMS1117-3.3, CAT811TTBI-GT3 and MPU-6000 among its other parts. Its parts include 34 resistors, 32 capacitors, 13 diodes, 10 connectors and 8 ICs. It belongs with the STM32 boards of this library.

Main components

10

README

README.md

Basic Rocketry System

This repo will be used to develop a basic system for rocketry avionics. Development is still in initial phase, as described below, and will most definetly go under many changes and tweeks as the project evolves.

For updated project information, please refer to the General Requirements document. The images and descriptions in this README may be out of date.

Rocketry Overview

My Background

I am a recently graduated Electronics Engineer and a space/rocketry enthusiast. For 3 years during graduation, I participated on a student rocketry team (at the time called Beyond Rocket Design, now Beyond Aerospace Department) where I helped to design and build model rockets for competitions like LASC, FBMF and so many others.

The problem is I knew nothing about rocketry back then (I still don't for the most part but hey, at least I have some xp now) and I was just starting to learn electronics, so although I knew how to code a little bit, I had never even heard of things like RTOS, threads, drivers and many many other things. Back then we used to program on Arduino IDE and created some really basic pcbs with ATmega328 and, later, ESP32 DevKit. Nothing wrong with that, we were able get somethings working, but of course my imagination never stops thinking about how much faster, reliable and efficient I could make those systems had I implemented them with some fancier techniques.

So, this is my main motivation for this project. I will be trying to implement an avionics system that does the basic but does it well. And obviously, if it works I will also try to convince the current team members to let me fly this thing on one of their rockets.

Flight Behavior

Suborbital model rockets tend to (although, more often than desired, they don't) go through these 6 main stages during flight:

  • Lift off
  • Powered Ascent
  • Coasting / Unpowered Ascent
  • Parachute / Recovery system deployment
  • Slow Descent
  • Landing


Flight Stages
Flight Stages (NASA)
Source: NASA's Beginners Guide to Aeronautics


Flight Stages: force analysis
Flight Stages Resultant Analysis
Source: Image created by the author

Notice that the most important events that happen during a flight - as far as software development goes - are the transitions between stages:

  • Launch: transition from being still and moving, hopefully, upwards
  • Main Engine Cut-Off (MECO): transition from Powered to Unpowered Ascent
  • Apogee: transition from moving upwards to downwards
  • Parachute: transition from descending almost on free fall to descending slowly
  • Landing: transition from descending to - we expect - softly stopping on the ground

Consider that the avionics system will have some kind of IMU (Inertial Measurement Unit), which basically tells us the instantaneous acceleration along its 3 axes. It will also feature a barometric sensor to measure the air pressure during flight. Now, let's imagine a rocket flying without any rotation, so that the Z-axis is always pointing up (this will never actually happen, but it's good for demonstration purposes). We can plot a graph with the approximate resultant acceleration (in red) and the corresponding velocity (in green) during this flight.


Flight Behavior: acceleration (red) and velocity (green)
Flight Behavior
Source: Image created by the author

As we can see in this simplified example, the resultant acceleration starts at 0g (1g = 9.8 m/s^2). It rises up to about 5g and then falls back down to 0g. This period where the acceleration is positive corresponds to the powered ascent, as illustrated on the previous image. Note that the rocket hits its maximum velocity when the acceleration is 0 (of course, since a=dv/dt). Then, the vehicle experiences free fall for some time (a = -1g) until the parachutes are deployed, at around T+28 seconds. From this point, the rocket falls at a constant speed only to hit the ground at T+41 seconds.

Just to be very clear, this example is absolutely, completely inaccurate and overly simplified. In practice, the acceleration curve of the motor during powered ascent stage is much steeper and shorter and the free fall period should be significantly smaller. Also, this example ignores any kind of air resistance, which is definetely not a great idea when studying rockets. However, I hope the example helps us understand the overall behavior of a model rocket during flight.

Project Requirements and definitions

For updated project information, please refer to the General Requirements document. The images and descriptions in this README may be out of date.

Hardware

The main objective with this project is to develop the device firmware, so hardware requirements are being defined based on components I have easy access to, mainly some off-the-shelf modules. If everything goes well after prototyping, I might review the project and design some proper hardware for it, but for now it is what it is.

Firmware

First of all, I defined a State Machine to control the system behavior based on rockect flight phases. For this project, I considered that the parachute shall be deployed on apogee detection in order to simplify things a little. This machine will be managed by the Flight Control thread, shown in the Architecture structure below.


FW State Machine
FW State Machine
Source: Image created by the author

Basically, the system is initialized on the first state and, if everything is working properly, moves to S1 where the operation mode is selected based on a mechanical switch state. There are only 2 modes: UART mode is used to select secondary opModes (such as reading post-flight data and configuring the system) and Flight mode is where the magic happens.

A flight only starts after the Remove Before Flight tag is detected as removed. This has many reasons, in this case the most important being reliability, since this helps prevent a false flight start, as well as saving battery power. After that, the system has 4 detection states, one for each flight stage transition. For example, S3 keeps trying to detect lift off stage by analyzing IMU and barometric sensor data. Another example is S4, which tries to detect MECO by also analysing data from IMU and barometric sensor, or (for redundancy) can move forward after a certain timeout.

After landing has been detected (and if the rocket is still a rocket) the system tries to backup the data from internal flash to a secondary storage unit, which may be a microSD card or another flash chip (still to be defined). Finally, the system goes to S8, a state designed to facilitate rocket recovery (sometimes, they really like hiding underground) while also saving battery power. In this state, the system stays on a cycle of sleeping and waking up to beep/blink the buzzer/LEDs until the battery is critically low.

All of this is operation is illustrated in the following Flowchart (also under development).


FW Flowchart
FW Flowchart
Source: Image created by the author

Lastly, the system will be organized according to the following Architecture (yes, you guessed it, this is also not the final version).


FW Architecture
FW Architecture
Source: Image created by the author

Tests and Validation

Untested rocket code is bad rocket code. So, I need a good way of testing this firmware to validate individual blocks and also the complete system working together. Of course, the biggest issue here is that I don't have multiple rockets to fire up and watch what happens. I am still not sure how to do this (if you have any ideas or advices, please tell me), but I fell like what I need is a combination of these 2 things:

  1. Simulated flight data: a piece of code that simulates a flight by generating coherent sensor data and feeds it into the system firmware as inputs.
  2. Small scale test flight: some sort of physical structure tied to my device/pdb that allows me to through it up the air and control the descent phase so that it doesn't crash onto the ground.

First method is clearly safer, but doesn't provide a "real world" condition. Second method allows me to test things in conditions closer to a real flight, but may lead to a lot of frustration, electronic waste and emptiness in my wallet. For now though, I will focus on developing the main firmware and some sort of flight simulation function.

Parts

129
QtyValueFootprintReferences
71k2Resistor_SMD:R_0603_1608MetricR1, R22, R23, R24, R25, R26, R27
7Jumper_2_Small_OpenBRS_Footprints:SMD_SolderJumper_SmallJP2, JP6, JP7, JP8, JP9, JP10, JP11
6100nFCapacitor_SMD:C_0402_1005MetricC7, C8, C9, C10, C28, C29
610kResistor_SMD:R_0603_1608MetricR2, R5, R6, R11, R12, R33
610nFCapacitor_SMD:C_0603_1608MetricC16, C17, C18, C19, C24, C32
5100nFCapacitor_SMD:C_0603_1608MetricC21, C23, C25, C26, C31
4100kResistor_SMD:R_0603_1608MetricR13, R28, R29, R31
4BLUELED_SMD:LED_0603_1608MetricD6, D7, D8, D9
4SupPCBMountingHole:MountingHole_2.2mm_M2_DIN965H1, H3, H5, H7
351kResistor_SMD:R_0603_1608MetricR14, R15, R16
3BC848Package_TO_SOT_SMD:SOT-23Q5, Q6, Q7
3ToolingHoleTFG_Footprints:JLCPCB_Tooling_HoleH2, H4, H6
2100nCapacitor_SMD:C_0603_1608MetricC4, C5
210uFCapacitor_SMD:C_0603_1608MetricC20, C22
2120RResistor_SMD:R_0603_1608MetricR18, R19
212pFCapacitor_SMD:C_0402_1005MetricC14, C15
21N4148Diode_SMD:D_SOD-123D12, D13
21kResistor_SMD:R_0603_1608MetricR4, R34
220kResistor_SMD:R_0603_1608MetricR20, R21
22kResistor_SMD:R_0402_1005MetricR7, R8
2AO3401APackage_TO_SOT_SMD:SOT-23Q3, Q4
2GREENLED_SMD:LED_0603_1608MetricD10, D11
2PMOSPackage_TO_SOT_SMD:SOT-23Q1, Q2
2TBDCapacitor_SMD:C_0603_1608MetricC1, C2
2TBDDiode_SMD:D_SOD-123D1, D2
10RResistor_SMD:R_0603_1608MetricR17
110nFCapacitor_SMD:C_0402_1005MetricC13
110uCapacitor_SMD:C_0603_1608MetricC3
116MHzCrystal:Crystal_SMD_Abracon_ABM8G-4Pin_3.2x2.5mmY1
11uFCapacitor_SMD:C_0402_1005MetricC12
11uFCapacitor_SMD:C_0603_1608MetricC30
12.2nFCapacitor_SMD:C_0603_1608MetricC27
1220kResistor_SMD:R_0603_1608MetricR10
139nHInductor_SMD:L_0603_1608MetricL1
14.7uFCapacitor_SMD:C_0603_1608MetricC6
14.7uF/1RCapacitor_SMD:C_0603_1608MetricC11
147RResistor_SMD:R_0402_1005MetricR3
15kResistor_SMD:R_0603_1608MetricR30
1620kResistor_SMD:R_0603_1608MetricR9
1AMS1117-3.3Package_TO_SOT_SMD:SOT-223-3_TabPin2U1
1AO3400APackage_TO_SOT_SMD:SOT-23Q8
1BATTERYConnector_Molex:Molex_Micro-Fit_3.0_43045-0412_2x02_P3.00mm_VerticalJ1
1BMP280Package_LGA:Bosch_LGA-8_2x2.5mm_P0.65mm_ClockwisePinNumberingU7
1BuzzerBuzzer_Beeper:PUIAudio_SMT_0825_S_4_RBZ1
1CAT811TTBI-GT3Package_TO_SOT_SMD:SOT-143U4
1EXT_GPIOSConnector_PinHeader_2.54mm:PinHeader_1x05_P2.54mm_VerticalJ4
1GNDConnector_PinHeader_2.54mm:PinHeader_1x03_P2.54mm_VerticalJ8
1JP_MCU_BOOT0BRS_Footprints:SMD_SolderJumper_Triple_SmallJP3
1JP_MCU_BOOT1BRS_Footprints:SMD_SolderJumper_Triple_SmallJP4
1MPU-6000Sensor_Motion:InvenSense_QFN-24_4x4mm_P0.5mmU6
1Micro_SD_CardConnector_Card:microSD_HC_Wuerth_693072010801J5
1ON/OFF MECHButton_Switch_THT:SW_DIP_SPSTx03_Slide_6.7x9.18mm_W7.62mm_P2.54mm_LowProfileSW1
1RBF_SYSBRS_Footprints:AudioJack_VerticalJ7
1RCV_SYSConnector_Molex:Molex_Micro-Fit_3.0_43045-0412_2x02_P3.00mm_VerticalJ6
1REDLED_SMD:LED_0603_1608MetricD3
1RED 2V/20mALED_SMD:LED_0805_2012MetricD5
1STM32F411CEUxPackage_DFN_QFN:QFN-48-1EP_7x7mm_P0.5mm_EP5.6x5.6mmU3
1SWD/ExtTrigConnector_PinHeader_2.54mm:PinHeader_1x05_P2.54mm_VerticalJ3
1SW_MCU_NRSTTFG_Footprints:SW_TS-1187A-B-A-BSW2
1TBDResistor_SMD:R_0603_1608MetricR32
1TCA9534Package_SO:TSSOP-16_4.4x5mm_P0.65mmU8
1TestPoint_SmallTestPoint:TestPoint_Pad_D1.5mmTP1
1USBLC6-2Package_TO_SOT_SMD:SOT-23-6U2
1USB_C_Receptacle_USB2.0_14PConnector_USB:USB_C_Receptacle_GCT_USB4105-xx-A_16P_TopMnt_HorizontalJ2
1USB_PWR_JPJumper:SolderJumper-2_P1.3mm_Open_RoundedPad1.0x1.5mmJP1
1VCCConnector_PinHeader_2.54mm:PinHeader_1x03_P2.54mm_VerticalJ10
1VDDConnector_PinHeader_2.54mm:PinHeader_1x03_P2.54mm_VerticalJ9
1W25Q128JVSPackage_SO:SOIC-8_5.23x5.23mm_P1.27mmU5
1WP_JPConnector_PinHeader_2.54mm:PinHeader_1x02_P2.54mm_VerticalJP5
1YL 2V/20mALED_SMD:LED_0805_2012MetricD4

Similar boards

  • 2 layers191.5 × 76 mmPcb project, the printed circuit board in 3D

    Pcb project

    CrashOverride85/zc95

    4 channel EStim box inspired by the mk312bt, with Lua scripting support

    337 parts117GPL-3.0
  • 4 layers29.5 × 29.5 mmEW281C FC, the printed circuit board in 3D

    EW281C FC

    jpwolfe9912/EW281C_FC

    Flight Controller for EW281C

    82 parts
  • 6 layers29.5 × 29.5 mmF722-FC Mini V2, the printed circuit board in 3D

    F722-FC Mini V2

    jpwolfe9912/F722-FC-Mini-V2

    113 parts
  • 6 layers70 × 27 mmUSB Dongle KiCad, the printed circuit board in 3D

    USB Dongle KiCad

    The810man/cross_pcb

    KiCad project to create a custom USB-C key with mass storage and a microSD connector. Find all the KiCad schematics and layout files.

    58 parts
  • 4 layers41 × 61.6 mmWhitefox, the printed circuit board in 3D

    Whitefox

    nxrmqlly/whitefox

    A devboard based on the Raspberry Pi RP2350B, with 47 GPIO, and microSD support

    80 parts1CERN-OHL-S-2.0
  • 2 layers37 × 70.9 mmOpendiag, the printed circuit board in 3D

    Opendiag

    maximus64/opendiag-hardware

    OpenDIAG - Open Source OBD2 Interface (Hardware)

    148 parts5CERN-OHL-S-2.0
  • 4 layers80 × 80 mmObc, the printed circuit board in 3D

    Obc

    OSUSat/cubesat

    Open Source Earth Imaging Satellite Hardware + Firmware

    151 parts8MIT

Questions

How big is the BRS HW v1 PCB?

It measures 50 × 81.3 mm and has 6 copper layers, 1.6 mm thick.

What parts does the BRS HW v1 use?

129 parts, built around the BMP280, TCA9534PW, W25Q128JVSIQ and AMS1117-3.3. The full list of its parts is on this page, with links to each part's symbol and footprint where PCBKit's library has them.

Where can I download the BRS HW v1 KiCad files?

From the lucasnoce/BRS_v1 repository on GitHub, at the commit this page was made from: the board is Hardware/BRS_HW_v1.kicad_pcb and its schematic Hardware/BAR.kicad_sch. PCBKit opens the board in the browser, with nothing to install.

Can I use the BRS HW v1 design in my own project?

Its repository publishes it under the MIT licence: you may reuse it on that licence's terms (keep the author's notice, and for a copyleft licence share your changes alike).