
Pcb project
CrashOverride85/zc95
4 channel EStim box inspired by the mk312bt, with Lua scripting support

Basic Rocket System
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.
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.
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.
Suborbital model rockets tend to (although, more often than desired, they don't) go through these 6 main stages during flight:
Flight Stages
Source: NASA's Beginners Guide to Aeronautics
Flight Stages: force 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:
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)
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.
For updated project information, please refer to the General Requirements document. The images and descriptions in this README may be out of date.
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.
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
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
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
Source: Image created by the author
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:
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.
| Qty | Value | Footprint | References |
|---|---|---|---|
| 7 | 1k2 | Resistor_SMD:R_0603_1608Metric | R1, R22, R23, R24, R25, R26, R27 |
| 7 | Jumper_2_Small_Open | BRS_Footprints:SMD_SolderJumper_Small | JP2, JP6, JP7, JP8, JP9, JP10, JP11 |
| 6 | 100nF | Capacitor_SMD:C_0402_1005Metric | C7, C8, C9, C10, C28, C29 |
| 6 | 10k | Resistor_SMD:R_0603_1608Metric | R2, R5, R6, R11, R12, R33 |
| 6 | 10nF | Capacitor_SMD:C_0603_1608Metric | C16, C17, C18, C19, C24, C32 |
| 5 | 100nF | Capacitor_SMD:C_0603_1608Metric | C21, C23, C25, C26, C31 |
| 4 | 100k | Resistor_SMD:R_0603_1608Metric | R13, R28, R29, R31 |
| 4 | BLUE | LED_SMD:LED_0603_1608Metric | D6, D7, D8, D9 |
| 4 | SupPCB | MountingHole:MountingHole_2.2mm_M2_DIN965 | H1, H3, H5, H7 |
| 3 | 51k | Resistor_SMD:R_0603_1608Metric | R14, R15, R16 |
| 3 | BC848 | Package_TO_SOT_SMD:SOT-23 | Q5, Q6, Q7 |
| 3 | ToolingHole | TFG_Footprints:JLCPCB_Tooling_Hole | H2, H4, H6 |
| 2 | 100n | Capacitor_SMD:C_0603_1608Metric | C4, C5 |
| 2 | 10uF | Capacitor_SMD:C_0603_1608Metric | C20, C22 |
| 2 | 120R | Resistor_SMD:R_0603_1608Metric | R18, R19 |
| 2 | 12pF | Capacitor_SMD:C_0402_1005Metric | C14, C15 |
| 2 | 1N4148 | Diode_SMD:D_SOD-123 | D12, D13 |
| 2 | 1k | Resistor_SMD:R_0603_1608Metric | R4, R34 |
| 2 | 20k | Resistor_SMD:R_0603_1608Metric | R20, R21 |
| 2 | 2k | Resistor_SMD:R_0402_1005Metric | R7, R8 |
| 2 | AO3401A | Package_TO_SOT_SMD:SOT-23 | Q3, Q4 |
| 2 | GREEN | LED_SMD:LED_0603_1608Metric | D10, D11 |
| 2 | PMOS | Package_TO_SOT_SMD:SOT-23 | Q1, Q2 |
| 2 | TBD | Capacitor_SMD:C_0603_1608Metric | C1, C2 |
| 2 | TBD | Diode_SMD:D_SOD-123 | D1, D2 |
| 1 | 0R | Resistor_SMD:R_0603_1608Metric | R17 |
| 1 | 10nF | Capacitor_SMD:C_0402_1005Metric | C13 |
| 1 | 10u | Capacitor_SMD:C_0603_1608Metric | C3 |
| 1 | 16MHz | Crystal:Crystal_SMD_Abracon_ABM8G-4Pin_3.2x2.5mm | Y1 |
| 1 | 1uF | Capacitor_SMD:C_0402_1005Metric | C12 |
| 1 | 1uF | Capacitor_SMD:C_0603_1608Metric | C30 |
| 1 | 2.2nF | Capacitor_SMD:C_0603_1608Metric | C27 |
| 1 | 220k | Resistor_SMD:R_0603_1608Metric | R10 |
| 1 | 39nH | Inductor_SMD:L_0603_1608Metric | L1 |
| 1 | 4.7uF | Capacitor_SMD:C_0603_1608Metric | C6 |
| 1 | 4.7uF/1R | Capacitor_SMD:C_0603_1608Metric | C11 |
| 1 | 47R | Resistor_SMD:R_0402_1005Metric | R3 |
| 1 | 5k | Resistor_SMD:R_0603_1608Metric | R30 |
| 1 | 620k | Resistor_SMD:R_0603_1608Metric | R9 |
| 1 | AMS1117-3.3 | Package_TO_SOT_SMD:SOT-223-3_TabPin2 | U1 |
| 1 | AO3400A | Package_TO_SOT_SMD:SOT-23 | Q8 |
| 1 | BATTERY | Connector_Molex:Molex_Micro-Fit_3.0_43045-0412_2x02_P3.00mm_Vertical | J1 |
| 1 | BMP280 | Package_LGA:Bosch_LGA-8_2x2.5mm_P0.65mm_ClockwisePinNumbering | U7 |
| 1 | Buzzer | Buzzer_Beeper:PUIAudio_SMT_0825_S_4_R | BZ1 |
| 1 | CAT811TTBI-GT3 | Package_TO_SOT_SMD:SOT-143 | U4 |
| 1 | EXT_GPIOS | Connector_PinHeader_2.54mm:PinHeader_1x05_P2.54mm_Vertical | J4 |
| 1 | GND | Connector_PinHeader_2.54mm:PinHeader_1x03_P2.54mm_Vertical | J8 |
| 1 | JP_MCU_BOOT0 | BRS_Footprints:SMD_SolderJumper_Triple_Small | JP3 |
| 1 | JP_MCU_BOOT1 | BRS_Footprints:SMD_SolderJumper_Triple_Small | JP4 |
| 1 | MPU-6000 | Sensor_Motion:InvenSense_QFN-24_4x4mm_P0.5mm | U6 |
| 1 | Micro_SD_Card | Connector_Card:microSD_HC_Wuerth_693072010801 | J5 |
| 1 | ON/OFF MECH | Button_Switch_THT:SW_DIP_SPSTx03_Slide_6.7x9.18mm_W7.62mm_P2.54mm_LowProfile | SW1 |
| 1 | RBF_SYS | BRS_Footprints:AudioJack_Vertical | J7 |
| 1 | RCV_SYS | Connector_Molex:Molex_Micro-Fit_3.0_43045-0412_2x02_P3.00mm_Vertical | J6 |
| 1 | RED | LED_SMD:LED_0603_1608Metric | D3 |
| 1 | RED 2V/20mA | LED_SMD:LED_0805_2012Metric | D5 |
| 1 | STM32F411CEUx | Package_DFN_QFN:QFN-48-1EP_7x7mm_P0.5mm_EP5.6x5.6mm | U3 |
| 1 | SWD/ExtTrig | Connector_PinHeader_2.54mm:PinHeader_1x05_P2.54mm_Vertical | J3 |
| 1 | SW_MCU_NRST | TFG_Footprints:SW_TS-1187A-B-A-B | SW2 |
| 1 | TBD | Resistor_SMD:R_0603_1608Metric | R32 |
| 1 | TCA9534 | Package_SO:TSSOP-16_4.4x5mm_P0.65mm | U8 |
| 1 | TestPoint_Small | TestPoint:TestPoint_Pad_D1.5mm | TP1 |
| 1 | USBLC6-2 | Package_TO_SOT_SMD:SOT-23-6 | U2 |
| 1 | USB_C_Receptacle_USB2.0_14P | Connector_USB:USB_C_Receptacle_GCT_USB4105-xx-A_16P_TopMnt_Horizontal | J2 |
| 1 | USB_PWR_JP | Jumper:SolderJumper-2_P1.3mm_Open_RoundedPad1.0x1.5mm | JP1 |
| 1 | VCC | Connector_PinHeader_2.54mm:PinHeader_1x03_P2.54mm_Vertical | J10 |
| 1 | VDD | Connector_PinHeader_2.54mm:PinHeader_1x03_P2.54mm_Vertical | J9 |
| 1 | W25Q128JVS | Package_SO:SOIC-8_5.23x5.23mm_P1.27mm | U5 |
| 1 | WP_JP | Connector_PinHeader_2.54mm:PinHeader_1x02_P2.54mm_Vertical | JP5 |
| 1 | YL 2V/20mA | LED_SMD:LED_0805_2012Metric | D4 |

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




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.

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

maximus64/opendiag-hardware
OpenDIAG - Open Source OBD2 Interface (Hardware)

It measures 50 × 81.3 mm and has 6 copper layers, 1.6 mm thick.
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.
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.
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).