Skip to content

Commit e0e1e36

Browse files
committed
feat: add blog post images
1 parent ee7ddd2 commit e0e1e36

File tree

5 files changed

+23
-9
lines changed

5 files changed

+23
-9
lines changed

blog-posts/return-jan-2026.mdx

Lines changed: 23 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -2,14 +2,16 @@ import BlogMeta from "@/components/blog-meta";
22
import BlogBack from "@/components/blog-back";
33

44
export const meta = {
5-
published: "01-17-2026",
6-
updated: "01-17-2026",
7-
title: "The Return of RoboSub",
5+
published: "01-22-2026",
6+
updated: "01-22-2026",
7+
title: "Our Return to RoboSub",
88
author: "Daniel Bereza",
9-
tags: ["meta", "EE"]
9+
tags: ["EE", "Sponsors", "OSH Park"]
1010
}
1111

12-
# The Return of RoboSub
12+
# Our Return to RoboSub
13+
14+
![the KiCAD layout](/blog-images/ee_board_layout.png)
1315

1416
<BlogMeta meta={meta} />
1517
---
@@ -18,20 +20,32 @@ export const meta = {
1820

1921
With the higher leadership taken care of, I have been happy to take the role of lead EE on the team. I figured a good trial by fire would be making a PCB for the RP2350 microcontroller, and if it worked, we could then base all of our embedded systems on it for motor control, sensor readings, and more. We had considered STM32 and ESP32 microcontrollers as alternatives, but decided that the RP2350 was the best balance of ease of use without the overkill that an ESP32 would be as we had no need for any wireless capabilities. In fact I had just the semester before made my own ESP32 PCB for my battlebot personally and was feeling emboldened, albeit a bit overwhelmed by the required supporting components the RP2350 required.
2022

21-
[insert schematic here]
23+
![image of v1 schematic](/blog-images/ee_schematic_v1.png)
24+
25+
<p style={{textAlign: "center"}}><i>A schematic of the GPIO dev board.</i></p>
2226

2327
In fact our first order of PCBs had to be canceled due to a decently big oversight on my part, you will not see it in the schematic above, but I had missed a crucial warning about the inductor for the 1.1V regulating rail and had picked out a completely wrong inductor which had the right inductance value but anyone after their first circuits class should know there is a lot more that goes on in picking inductors than the one value. I had only realized this after the PCB order had been put in and I was finalizing the DigiKey order, I had not verified the internal resistance had been acceptable so I went back to the RP2350 hardware design document. Even an experienced EE might not expect what I had actually read when I followed up, and one of my professors later thought I was messing with him when I told him about it.
2428

25-
The document explained how due to how tight the constraints on the tiny 1.1V rail were with how close the components had to be, an inductor wound the wrong way would interfere with the capacitor. Now to contextualize the absurdity in this, practically no “small” inductors are in any way marked with the direction of the winding as this is not normal. As my professor put it, the “polarized” inductor that was created for the chip sounds almost like trying to buy blinker fluid. Thankfully I had realized this within a matter of hours of our initial PCB order and OSH Park were awesome and refunded us for our early cancellation. I should also disclose that OSH Park are sponsoring us with free credit for PCB manufacture and they will get more praise at the end for the beauty of the boards they delivered to us compared to their competitors.
29+
The document explained how due to how tight the constraints on the tiny 1.1V rail were with how close the components had to be, an inductor wound the wrong way would interfere with the capacitor. Now to contextualize the absurdity in this, practically no “small” inductors are in any way marked with the direction of the winding as this is not normal. As my professor put it, the “polarized” inductor that was created for the chip sounds almost like trying to buy blinker fluid. Thankfully I had realized this within a matter of hours of our initial PCB order and OSH Park were awesome and refunded us for our early cancellation. I should also disclose that <u>[OSH Park](https://oshpark.com/)</u> is sponsoring us with free credit for PCB manufacture, and they will get more praise at the end for the beauty of the boards they delivered to us compared to their competitors.
2630

27-
[picture of bare PCB]
31+
![blank PCB board](/blog-images/ee_blank_board_v1.jpg)
32+
33+
<p style={{textAlign: "center"}}><i>The blank PCB straight from OSH Park.</i></p>
2834

2935
Once the issue was fixed we had to anxiously wait two weeks for manufacturing and shipping. We do our assembly in house, and the first board we put together did not seem to initially work. With some panicked troubleshooting we found the issue, I had swapped the labels of a resistor and capacitor. With that fixed we had our first working dev board! That was in November but I have been holding off on congratulating myself until the full CAN functionality was verified for a fully working board, which it now has! We will be writing more on the design decisions we made and why, but the most important thing is at least in my mind, we are alive again!
3036

31-
[picture of finished PCB]
37+
![finished PCB board](/blog-images/ee_board_finished_v1.jpg)
38+
39+
<p style={{textAlign: "center"}}><i>The finished GPIO board.</i></p>
3240

3341
-Daniel Bereza, EE Lead
3442

43+
<div style={{textAlign: "center"}}>
44+
45+
![OSH Park Logo](/sponsor-logos/osh-park.png)
46+
47+
</div>
48+
3549
---
3650

3751
<BlogBack/>
781 KB
Loading
542 KB
Loading
369 KB
Loading
103 KB
Loading

0 commit comments

Comments
 (0)