From 445074a9e6c7c96fb9bfba696258185d07f534dd Mon Sep 17 00:00:00 2001 From: bradley Date: Tue, 28 Nov 2023 21:21:01 -0500 Subject: [PATCH] Change our and we to me cuz I did the work. --- _posts/2023-11-22-3D-Printer.md | 2 +- _posts/2023-4-12-TVC-Rocket.md | 12 ++++++------ 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/_posts/2023-11-22-3D-Printer.md b/_posts/2023-11-22-3D-Printer.md index 734527850b329..5ce156c2b8aff 100644 --- a/_posts/2023-11-22-3D-Printer.md +++ b/_posts/2023-11-22-3D-Printer.md @@ -12,7 +12,7 @@ featured-image: /images/3dPrinter/printer.jpg {:refdef} This image is of the 3D Printer I built to complete various projects, from a Mostly Printed CNC to a planter and everything in between. The frame, the hotbed, the motors, and the wires are just about the only original components on there. Everything was upgraded, including the extruder, cable chains, control board, lead screws, frame support, belts and tensioners, power supply, hotbed MOSFET, and the software used for file selection. -I installed Octoprint on a Raspberry Pi 4, and we now use that for the 3D Printer interface. Octoprint is a considerable improvement. I particularly like the metrics it provides and the raw visibility and access to the Printer and, of course, the remote access. The Octoprint software offers handy plugins, with some improving safety, such as thermal monitoring. I connected a smart outlet switch, which is now used to remotely power on the Printer and automatically power it off when the print is finished via the IFTTT plugin. This addition means I can entirely run a print from another location without worrying about turning the 3D Printer off. +I installed Octoprint on a Raspberry Pi 4, and I now use that for the 3D Printer interface. Octoprint is a considerable improvement. I particularly like the metrics it provides and the raw visibility and access to the Printer and, of course, the remote access. The Octoprint software offers handy plugins, with some improving safety, such as thermal monitoring. I connected a smart outlet switch, which is now used to remotely power on the Printer and automatically power it off when the print is finished via the IFTTT plugin. This addition means I can entirely run a print from another location without worrying about turning the 3D Printer off. By far, the most sophisticated upgrade was to the control board. More specifically, configuring the Marlin software for the setup. The Anet A8 does not lend itself to a simple plug-and-play configuration for Marlin and the SKR V1.4. The first step on this journey was to make sure that any attempts at this upgrade could be reverted if necessary, so I created coupling wires that could easily detach to mate the existing hardware with the new board. diff --git a/_posts/2023-4-12-TVC-Rocket.md b/_posts/2023-4-12-TVC-Rocket.md index aecaa8d1ebd38..17f3312cc6914 100644 --- a/_posts/2023-4-12-TVC-Rocket.md +++ b/_posts/2023-4-12-TVC-Rocket.md @@ -15,9 +15,9 @@ This post is about a Thrust Vector Controlled (TVC) Rocket project I am working This project is a work in progress but can roughly be broken down into four parts. -- Flight computer design (complete) +- Flight computer board design and assembly (complete) - 3d modeling and part selection (mostly complete) -- Physics/control algorithm simulation (complete but waiting on updated rocket characterization) +- Physics/control algorithm simulation (complete but need updated rocket characterization to utilize) - Flight software (peripheral drivers mostly written, main loop WIP) @@ -27,7 +27,7 @@ I designed a flight controller from scratch using KiCad and had it produced and ![an image alt text]({{ site.baseurl }}/images/tvc/enosGlamourShot.jpg "The Flight Computer") -Enos is named after the first chimpanzee to reach orbit! He's depicted in our mascot logo, showcased here: +Enos is named after the first chimpanzee to reach orbit! He's depicted in the mascot logo, showcased here: {:refdef: style="text-align: center;"} ![an image alt text]({{ site.baseurl }}/images/tvc/enosMascot.jpg "Enos Mascot") @@ -45,12 +45,12 @@ The full board is shown below: {:refdef} -The schematic can be found [here](https://github.com/BradleyConn/bc_flight_computer/blob/main/Hardware/KiCad/projects/rp2040_v0/rp2040_v0/schematic_v0.pdf) +The schematic can be found [here](https://github.com/BradleyConn/bc_flight_computer/blob/main/Hardware/KiCad/projects/rp2040_v0/rp2040_v0/schematic_v0.pdf). The schematic is well annotated. The first page and heart of the flight computer, is shown below. ![an image alt text]({{ site.baseurl }}/images/tvc/schematic_v0_page1.jpg "Schematic") -The gerbers can be found [here](https://github.com/BradleyConn/bc_flight_computer/blob/main/Hardware/KiCad/projects/rp2040_v0/rp2040_v0/gerbers_v0.pdf) and [here](https://github.com/BradleyConn/bc_flight_computer/blob/main/Hardware/KiCad/projects/rp2040_v0/rp2040_v0/gerbers_v0_single_page.pdf) +Pdf files of the gerbers can be found [here](https://github.com/BradleyConn/bc_flight_computer/blob/main/Hardware/KiCad/projects/rp2040_v0/rp2040_v0/gerbers_v0.pdf) and [here](https://github.com/BradleyConn/bc_flight_computer/blob/main/Hardware/KiCad/projects/rp2040_v0/rp2040_v0/gerbers_v0_single_page.pdf). And they look like this: @@ -68,7 +68,7 @@ The board typically requires headers to be soldered on. The complete board can b -I figured out a neat little trick for this board. I wanted to maintain as much flexibility as I could, not knowing if the board had design flaws or not, as it was my first board. So, each peripheral component had breaks in the signals to disconnect or rewire completely. To save space and also not have to solder extra through-hole components, I used zero Ohm resistors to bridge the signals. They can easily be removed and updated if needed. This also had the benefit of essentially creating an extra layer for the board as the signals rose over the board, and other signals could run underneath the resistor. An example is shown here: +I figured out a neat little trick for this board. I wanted to maintain as much flexibility as I could, not knowing if the board had design flaws or not, as it was my first board. So, each peripheral component had breaks in the signals to disconnect or rewire completely. To save space and also not have to solder extra through-hole components, I used zero Ohm resistors to bridge the signals over the through-holes. They can easily be removed and updated if needed. This also had the benefit of essentially creating an extra layer for the board as the signals rose over the board, and other signals could run underneath the resistor. An example is shown here: {:refdef: style="text-align: center;"} ![an image alt text]({{ site.baseurl }}/images/tvc/enosZeroOhm.jpg "Zero Ohm trick")