r/PrintedCircuitBoard • • Dec 11 '22

Please Read Before Posting, especially if using a Mobile Browser

21 Upvotes

Welcome to /r/PrintedCircuitBoard subreddit

  • a technical subreddit for reviewing schematics & PCBs that you designed, as well as discussion of topics about schematic capture / PCB layout / bill of material (BOM) / PCB assembly / PCB mechanical engineering.

Some mobile browsers and apps don't show the right sidebar of subreddits:


RULES of this Subreddit:

  • (0) Occasionally the moderator may allow a useful post to break a rule, and in such cases the moderator will post a comment at the top of the post saying it is ok; otherwise please report posts that break rules!

  • (1) NO off topics / humor / memes / where to buy? / what is this? / how to fix? / how to modify? / how to design? / what does this do? / how does this work? / how to reverse engineer? / need schematics / dangerous or medical projects / homework / AI topics / AI content / AI designs / non-english languages.

  • (2) NO spam / ads / sales / promotion / survey / quiz / items for sale / promotion of non-reddit groups / promotion of non-reddit social media. NO DM abuse! See "how to advertise on Reddit".

  • (3) NO "show & tell" or "look at what I made" posts, unless you previously requested a review of the same PCB in this subreddit. This benefit is reserved for people who participate in this subreddit. NO random PCB images.

  • (4) NO self promotion / resumes / job seeking / wage discussions / freelancing discussions / DM abuse / job postings (unless job is posted on employer website) / begging or scamming for free work / ...

  • (5) NO shilling! No PCB company names in post titles or review requests. No sneaky PCB company naming variations. For most reviews, we don't need to know where you are getting your PCBs made or assembled, so please don't state company names unless absolutely necessary.

  • (6) NO asking how to upload your PCB design to a specific PCB company! Please don't ask about PCB services for a specific PCB company, because of past shilling abuse (see rule#5). (TIP: search their company website, ask their customer service or sales departments, search google or other search engines)


Review RULES:

  • (7A) Please do not abuse the review process:

    • Please do not request more than one review per board per day.
    • Please do not change review images during a review. If you change image(s), then start a new review!
    • Reviews are meant for schematics & PCBs that you designed. No AI designs.
    • Reviews are allowed prior to ordering PCBs. If assembled board doesn't work, ask at /r/AskElectronics
    • Please do not ask circuit design questions in a PCB review. You should have resolved design questions while creating your schematic and before routing your PCB, instead request a schemetic-only review.
  • (7B) All review posts must adhere to the following rules:

    • Title - include the following: "Review Request" or "Review", short description of board purpose, popular board format or shield/hat type (if applies), microcontroller (if has MCU), external buses (Ethernet, USB, CAN, RS485, ...), wireless (WiFi, GPS, LoRa, ...), storage (microSD, M.2, ...), and/or any unique hardware that may be important. No humorous titles, no childish symbols, no begging.
    • Images - include images (or links to each image) that you want reviewed. If images are located on the internet, never post one link to a project then expect reviewers to dig through your project to find images. Instead, you must post separate links for each review image, as well as state the purpose of each link, such as "Schematic" / "3D PCB" / "2D PCB top" / "2D PCB bottom" / ...
  • (8) All images must adhere to the following rules:

    • Image Creation: no camera photos of a computer screen, instead export / screen capture / print to image files. (TIP: How to export images from KiCAD and EasyEDA) (TIP: use clawPDF printer driver for Windows to "print" to PNG / JPG / PDF / SVG files, or use built-in Win10/11 PDF printer driver to "print" to PDF files.)
    • Image Files: view each image file before posting / no fuzzy or blurry images / no large image files (e.g. 100 MB), smaller preferred / no uncommon image file types, only use file types supported by most web browsers, such as JPG / PNG / PDF.
    • Edit Image Files: if you screen capture, make sure the cursor / software / operating system aren't shown in your images. Use an image editor to erase or crop software & O/S junk from your images.
    • Disable Features: disable background grids & PCB editor features before creating images.
    • Schematics: no bad color schemes to ensure readability (no black or dark-color background) (no light-color foreground (symbols/lines/text) on light-color/white background) / schematics must be in standard reading orientation (no rotation). (NOTE: we don't care what color scheme you use to edit, nor do we care what edit features you enable, but for reviews you need to choose reasonable color contrasts between foreground and background to ensure readability.)
    • 2D PCB: no bad color schemes to ensure readability (must be able to read silkscreen) / no net names on traces / no pin numbers on pads / if it doesn't appear in the gerber files then disable it for review images (dimensions and layer names are allowed outside the PCB border). (NOTE: we don't care what color scheme you use to edit, nor do we care what color soldermask you order, but for reviews you need to choose reasonable color contrasts between silkscreen / soldermask / copper / holes to ensure readability. If you don't know what colors to choose, then consider white for silkscreen / gold shade for exposed copper pads / black for drill holes and cutouts.)
    • 3D PCB: 3D views are optional, if most 3D components are missing then don't post 3D images / 3D rotation must be in the same orientation as the 2D PCB images / 3D tilt angle must be straight down plan view. (NOTE: straight down "plan" view is mandatory, optionally include an "isometric" or other tilted view angle too.)

Review tips:

Schematic tips:

PCB tips:

College lab tips:

SPICE tips:


WIKI for /r/PrintedCircuitBoard:


This post is a "live document" that has evolved over time. Copyright 2022-2026 by /u/Enlightenment777 of Reddit. All Rights Reserved. You are explicitly forbidden from copying content from this post to another subreddit or website without explicit approval from /u/Enlightenment777 also it is explicitly forbidden for content from this post to be used to train any software.


r/PrintedCircuitBoard • • Apr 11 '25

Before You Request A Review, Please Fix These Issues Before Posting

118 Upvotes

PLEASE DO NOT ABUSE THE REVIEW PROCESS:

  • Don't change review images during a review, otherwise older comments won't match newer images.

  • Please do not request more than one review per board per day. Use the extra time to clean up the visual appearance of your schematic and silkscreen on your PCB before requesting another review (see tips below).

REVIEW IMAGE CONVENTIONS / GUIDELINES:

  • The following is a subset of the review rules, see rule#8 at link.

  • Don't post fuzzy images that can't be read (your post will be deleted).

  • Don't post camera photos of a computer screen (your post will be deleted). Export or screen capture.

  • Don't post dark-background schematics (your post will be deleted). Change schematic to light-background.

  • For schematic images, disable background grids and cursor before exporting/capturing to image files.

  • For 2D PCB images, change the following settings before exporting/capturing to image files: disable background grids, disable net names on traces & pads, disable everything that doesn't appear on final PCB, enable board outline layer, enable cutout layer, optionally add board dimensions along 2 sides. For question posts, only enable necessary layers to clarify a question.

  • For 3D PCB images, 3D rotation must be same orientation as your 2D PCB images, and 3D tilt angle must be straight down, known as the "plan view", because tilted views hide short parts and silkscreen. You can optionally include other tilt angle views, but ONLY if you include the straight down plan view too.


SCHEMATIC CONVENTIONS / GUIDELINES:

  • Add Board Name / Board Revision Number / Date. If there are multiple PCBs in a project/product, then include the name of the Project or Product too. Your initials or name should be included on your final schematics, but it probably should be removed for privacy reasons in public reviews.

  • Don't post schematics that look like a toddler drew it, because it's considered unprofessional as an adult. Spend more time cleaning up your schematics! Heed this warning, or risk being berated by your coworkers / boss / classmates / professor / customers.

  • Don't allow text / lines / symbols to touch each other! Don't draw lines through component symbols.

  • Don't point ground symbols (e.g. GND) upwards in positive voltage circuits. Don't point positive power rails downwards (e.g. +3.3V, +5V). Don't point negative power rails upwards (e.g. -5V, -12V). There are exceptions, but in general try to follow this historical method as much as possible. If a schematic has only one ground and you use a unique triple-bar ground symbol, then disable "GND" text next to this symbol, because it is useless visual clutter that takes up space in dense schematics.

  • Place pull-up resistors vertically above signal lines, and place pull-down resistors vertically below signal lines, see example.

  • Place decoupling capacitors vertically below power lines, next to IC symbols, and connect capacitors to IC power rail pin with a line, see example.

  • Use standarized schematic symbols instead of generic boxes! For part families that have many symbol types, such as diodes / transistors / capacitors / switches, make sure you pick the correct symbol shape. Logic Gate / Flip-Flop / OpAmp symbols should be used instead of a rectangle with pin numbers laid out like an IC.

  • Don't use incorrect reference designators (RefDes). Start each RefDes type at 1 (e.g. C1, D1, R1, Q1, U1), and renumber so there aren't any numeric gaps (e.g. U1, U2, U3, U4; not U2, U5, U9, U22). There are exceptions for large multi-page schematics, where the RefDes on each page could start with increments of 100 (or other increments) to make it easier to find parts, such as R101 is on page 1, R301 is on page 3, R901 is on page 9.

  • Add values next to component symbols:

    • Add capacitance next to all capacitors.
    • Add resistance next to all resistors / trimmers / pots.
    • Add inductance next to all inductors.
    • Add voltages on both sides of power transformers. Add "in:out" ratio next to signal transformers.
    • Add frequency next to all crystals / powered oscillators / clock input connectors.
    • Add voltage next to all zener diodes / TVS diodes / batteries, battery holders, battery connectors, maybe on coil side of relays, contact side of relays.
    • Add color next to all LEDs. This is useful when there are various colors of LEDs on your schematic/PCB. This information is useful when the reader is looking at a powered PCB too.
    • Add pole/throw info next to all switch (e.g. 1P1T or SPST, 2P2T or DPDT) to make it obvious.
    • Add purpose text next to LEDs / buttons / switches to help clarify its use, such as "Power" / "Reset" / ...
    • Add "heatsink" text or symbol next to components attached to a heatsink to make it obvious to readers! If a metal chassis or case is used for the heatsink, then clarify as "chassis heatsink" to make it obvious.
  • Add part numbers next to all ICs / Transistors / Diodes / Voltage Regulators / Coin Batteries (e.g. CR2023). Shorten part numbers that appear next to symbols, because long part numbers cause schematic layout problems; for example use "1N4148" instead of "1N4148W-AU_R2_000A1"; use "74HC14" instead of "74HC14BQ-Q100,115". Put long part numbers for ordering in your BOM (Bill of Materials) list.

  • Add connector type next to connector symbols, such as the common name / connector family / connector manufacturer (e.g. "USB-C", "microSD", "JST PH", "Molex SL"). For connector families available in multiple pitch sizes, include the pitch in metric too (e.g. 2mm, 2.54mm), optionally include imperial units in parens after the metric number, such as 1.27mm (0.05in) / 2.54mm (0.1in) / 3.81mm (0.15in). Add purpose text next to connectors to make its purpose obvious to readers, such as "Battery" or "Power".

  • Don't lay out or rotate schematic subcircuits in weird non-standard ways:

    • linear power supply circuits should look similar to 1, 2, 3, 4, 5, laid out horizontally, input on left side, output on right side. Three pin voltage regulator symbols should be a rectangle with "In" (Vin) text on the left side, "Out" (Vout) text on right side, "Gnd" or "Adj" on bottom side, if has enable pin then place it on the left side under the "In" pin; don't use symbols that place pins in weird non-standard layouts. Place lowest capacitance decoupling capacitors closest to each side of the voltage regulator symbol, similar to how they will be placed on the PCB.
    • relay driver circuits should look similar to this, laid out vertically, +V rail at top, GND at bottom. Remove optoisolators from relay driver circuits unless both sides of it have unique grounds and unique power sources. Reminder that coil side of a mechanical relay is 100% isolated from its switched side.
    • optoisolator circuits must have unique ground and unique power on both sides to be 100% isolated. If the same ground is on both sides of an optoisolator, it isn't 100% isolated, see galvanic isolation.
    • 555 timer circuits should look similar to this. IC pins should be shown in a historical logical layout (2 / 6 / 7 on left side, 3 on right side, 4 & 8 on top, 1 on bottom); don't use package layout symbols. If using a bipolar timer, then add a decoupling capacitor across power rails too, such as 47uF, to help with current spikes when output changes states, see article.
    • RS485 circuits should look similar to this.

PCB CONVENTIONS / GUIDELINES:

  • Add Board Name / Board Revision Number / Date (or Year) in silkscreen. For dense and tiny PCBs that lacks free space, shorten the text, such as "v1" and "2026" (or "Y26" or "26"). This info can be very useful to help identify a PCB in the future, especially if there are two or more revisions of the same PCB.

  • Add mounts holes, unless absolutely not needed. They should be the first thing you place on your PCB.

  • Use wider traces for power rails and higher current circuits. If possible, use floods for GND.

  • Don't route high current traces or high speed traces on any copper layers directly under crystals / antenna / RF circuits / other sensitive circuits. Don't route other signal traces under antenna.

  • Don't place reference designators (RefDes) in silkscreen under components, because you can't read RefDes text after components are soldered on top of it. If you hide or remove RefDes text, then a PCB is harder manually assemble, and harder to debug and fix in the future.

  • Add part orientation indicators in silkscreen, but don't place under components (if possible). Add pin 1 indicators next to ICs / Connectors / Voltage Regulators / Powered Oscillators / Multi-Pin LEDs / Modules / ... Add polarity indicators for polarized capacitors, if capacitor is through-hole then place polarity indicators on both sides of PCB. Add pole indicators for diodes, and "~", "+", "-" next to pins of bridge rectifiers. Optionally add pin indicators in silkscreen next to pins of TO220 through-hole parts; for voltage regulators add "I" & "O" (in/out); for BJT transistors add "B" / "C" / "E"; for MOSFET transistors add "G" / "D" / "S".

  • Add as much helpful text in silkscreen as reasonably possible, because it is a means of "self documentation" that always stays with the PCB.

  • If space is available, add purpose text in silkscreen next to LEDs / buttons / switches / jumpers to make it obvious why an LED is lite (e.g. "Error", "Power"), or what happens when press a button (e.g. "Reset", "Start", "Stop") or change a switch (e.g. "Power").

  • If space is available, add connector type in silkscreen next to each connector. For example "JST-PH", "Molex-SL", "USB-C", "microSD". For connector families available in multiple pitch sizes, add the pitch too, such as 1.27mm or 3.81mm. If space is not available on the top side, then add this information directly below the connector on the bottom side.

  • If space is available, add voltage range or maximum voltage text in silkscreen, such as "8VDC Max", next to power input connectors to help prevent destruction of voltage regulators or other circuits. For barrel jacks, add text to clarify polarity of the center pin, such as "-9VDC Center" or "+9VDC Center" or "GND Center". If space is not available on the top side, then add this information directly below the connector on the bottom side.


ADDITIONAL TIPS / CONVENTIONS / GUIDELINES

Review tips:

Schematic tips:

PCB tips:


This post is a "live document" that has evolved over time. Copyright 2025-2026 by /u/Enlightenment777 of Reddit. All Rights Reserved. You are explicitly forbidden from copying content from this post to another subreddit or website without explicit approval from /u/Enlightenment777 also it is explicitly forbidden for content from this post to be used to train any software.


r/PrintedCircuitBoard • • 9h ago

Servo Module Board Review

Thumbnail
gallery
13 Upvotes

Hey guys I'm trying to learn how to design PCB's. This is a design that I recently did for a servo module. What should I improve on?


r/PrintedCircuitBoard • • 12h ago

[Review Request] ESP32-based Fan Controller

Thumbnail
gallery
7 Upvotes

Hi everyone!

I am building a CR Box, inspired by many designs on the r/crboxes subreddit.

This is my first ESP32-based design. I did the layout on 2 layers because I haven't used many components, and the highest intended signal frequency is the 25 kHz fan PWM (apart from the buck converter). I have tried my best to keep the bottom GND plane as intact as possible.

The fans are divided into two groups, A and B, to control the speed of the two fan groups separately. The ESP32 controls two MOSFETs using PWM, and each MOSFET is connected to the PWM pins of five fans. I added these 2 little MOSFETs to protect the ESP32 pins because, as far as I understand, the fans have an internal pull-up on their PWM pins, which can be as high as 5.25V. I added a "smart mode" switch, which, when OFF, lets me control the fans manually using the potentiometer. When the switch is ON, the controller will receive data from an air quality sensor and adjust the speed based on that. In addition, I connected each tachometer pin to the ESP32 to monitor the RPM of each fan and detect if one stops spinning.

For the power supply, the input voltage is 12 V. I added a P-channel MOSFET for reverse-polarity protection and a buck converter to step down the 12 V to 3.3 V to power the ESP32.

I designed the controller to support up to 10 fans. Each fan I am planning to use draws up to 0.35 A, giving 3.5 A in total. So I used a copper pour for the 12 V rail and wide traces towards the fan headers.

The PCB will be mechanically supported by the switch, potentiometer, and four M3 screws.

I’ve attached 3D renders of the board, the schematics, and the complete PCB layout.

I'd really appreciate any comments or advice on the design. I'm especially interested in feedback on how I control the fan speeds using PWM. Does the overall layout look okay? Are there any other issues or things you would change before I manufacture the PCB?

Thank you! 😊


r/PrintedCircuitBoard • • 13h ago

[Schematic Review] USB-C Hub with DP Alt-Mode, Dual USB-A 3.1, Gigabit Ethernet, and Isolated Upstream Power(No Phone Charging)

Thumbnail
gallery
7 Upvotes

System Architecture Overview

This schematic details an externally powered USB-C hub featuring DisplayPort Alternate Mode, dual USB-A downstream ports, and Gigabit Ethernet capability. The design is bound by a strict operational constraint: the hub must be powered externally and must not deliver power to the host device (phone) under any circumstances.

Functional Subsystems

  1. USB-C Interface and DisplayPort Alt-Mode
  • Protocol & Switching Control: USB-C Power Delivery (PD) and Alternate Mode negotiation are handled by the LDR6023SS controller. High-speed signal routing for DisplayPort Alt-Mode is multiplexed via the HD3SS460 switch.
  • Power Isolation Topology: To enforce strict isolation, the host phone's VBUS line (usbc_VBUS) powers only the LDR6023SS. There is no electrical path connecting the hub's main power rails back to the phone's VBUS line, eliminating any possibility of back-powering the host.
  1. Downstream Connectivity and Hub Expansion
  • USB-A Ports: The TUSB8044ARGCR hub controller expands the upstream data connection into downstream interfaces, managing two physical USB-A 3.1 Gen 1 ports.
  • Gigabit Ethernet: One of the downstream USB 3.1 channels from the TUSB8044A interfaces directly with a LAN7800 USB 3.1-to-Ethernet bridge to provide a dedicated 1Gbps network connection.
  1. Power Generation

r/PrintedCircuitBoard • • 17h ago

Board Review Please?

Thumbnail
gallery
3 Upvotes

I am trying to get my toes in the water of PCB design, and came up with this board to connect two TMC5240s to an STM32F7 to drive stepper motors. Board is simple for now, but will eventually have other versions with the drivers and stm on board.


r/PrintedCircuitBoard • • 1d ago

REVIEW REQUEST (MPPT 15A 54V Max) First PCB as student

Thumbnail
gallery
21 Upvotes

Hi everyone, I've built an MPPT for a college project. The control and PWM signals are managed by an STM32G474 on another board. Please share your thoughts and advice—I'd like to improve it :)


r/PrintedCircuitBoard • • 1d ago

[REVIEW REQUEST] My first PCB, a PSP like handheld (ESP32-S3 <---> BT817Q

Thumbnail
gallery
9 Upvotes

Hello there!

Hi, my name is Jose Ramirez and I'm a Computer Engineering student, and this is my first PCB ever (the real first one is a FPC to male PIN adapter for a joystick) and It's also my bachelor's thesis.

Why? Because the PSP was the console of my childhood, and building my own take on it is my way of paying tribute to it. (Yes I know that it will have 2 joysticks and it will look more like the PSVita 😅 ).

I have almost no electronics background, so a lot of what I've learned this 2.5 months I have been working in this project the way has been with AI as a tutor, and some YT videos. I used it to understand datasheets, develop and review the schematics, and to understand how to route and the reason of the position of every component. Even though I have been using AI to understand the project everything has been developed by hand, no AI automation has been used for developing this project, doing it this way I think that has lead me to gain more knowledge.

I want to know every possible mistake and every standard practice I haven't followed. I want to improve every detail, no matter how small.

Components

- MCU: ESP32-S3-DevKit.

- Display:BT817Q graphics controller with a flash memory (16MBytes) and a 12 MHz crystal. It controls the 800×480 RGB panel through a 40-pin FPC, and the capacitive touch through a 6-pin FPC

- ESP32 ↔ BT817: QSPI, ≤ 30 MHz.

- BT817 ↔ flash: 60 MHz.

- Backlight: DIO5661 boost, constant current, ~60 mA at ~21 V.

- Power: USB-C (J10), 5 V only, with 5.1 k CC pull-downs and USBLC6-2 ESD protection (U2). 5 V feeds an LMR51430 buck (1.1 MHz version, 2.2 µH) for the 3.3 V rail.

- Input: MCP23017(0x20) over I²C for 14 buttons, plus two analog joysticks on FPCs directly connected to the ESP32 ADC.

- Audio: PAM8302A class-D amplifier with a ferrite and a output filter, speaker on a JST PH connector.

Board info

- KiCad [10.0.6]. 4 layers: F.Cu signals / In1 solid GND / In2 solid 3.3 V / B.Cu signals.

- DRC: 0 errors, 0 unconnected. Four items are excluded on purpose:

- 2 "unconnected" items on U2: flow-through routing as in ST's datasheet (pins 1–6 and 3–4 are joined inside the chip)

- ERC: 0 errors. 4 excluded warnings.

Is this prototype able to work if I sent it to fab?

- Github repo: https://github.com/ocxpke/ocx

Thanks a lot for taking the time, any comment will be appreciated! :D


r/PrintedCircuitBoard • • 1d ago

Schematic review: ESP32 engine vibration + ignition logger (3 boards)

Thumbnail
gallery
6 Upvotes

Hey everyone, I'd love a schematic review before I start the layout.

I am designing a little logger for diagnosing car engines for a class. An accelerometer board goes on the engine to pick up vibration, and a spark detection board goes on an ignition coil to check that it's firing (kind of like a coil-on-plug tester). Both connect to the main ESP32 board with wires, so it's 3 separate PCBs.

Main board (ESP32-WROOM-32E):
- USB-C with a CP2102N for programming
- Single-cell Li-ion with a BQ24072 charger and MAX17260 fuel gauge
- AP7361C 3.3V regulator with an external on/off switch
- Optional connector for a NEO-7M GPS module

I've used this same ESP32 + CP2102N auto-reset setup before, but auto flashing never worked. I had to hold the BOOT button every time I wanted to upload code. If anyone can spot why, that'd be awesome.

Accelerometer board:
- KX134 (±64g) over SPI

Spark detection board:
- Pickup wire to RC filter, TVS and clamp diodes to 74HC14 Schmitt trigger to ESP32

Any feedback is welcome, thanks!


r/PrintedCircuitBoard • • 1d ago

REVIEW REQUEST (ATMEGA328P-PU ARDUINO) (2nd PCB DESIGN as a student)

Thumbnail
gallery
25 Upvotes

hello everyone, I’ve made my own Arduino, what do you guys think of my work? I’m very open to your criticism on what I should revise or change. I’m honing my skills so it would really be helpful to know what you have to say.


r/PrintedCircuitBoard • • 1d ago

Annular rings too close. Can I offset the hole outside it's ring?

Post image
9 Upvotes

I have a bad position where I would be running two parts into each other. Soldered from opposite sides of the board, can not be moved.

On 1, that's a little offset of the annular ring up from the slotted hole. Leaving .4mm copper to copper. Not ideal.

On 2, that's a big push. This breaks a lot of design rules, but, I wouldn't care if during mfg this wasn't plated exactly all around because it's going to make connection on the three side for sure.

On 3, that's extreme on purpose. No design rule checker will like this... But I'm not sure what would happen at a JLCPCB or PCBWay. If there is a reason to do this sometimes. I wouldn't even care if the lower tail of that hole is plated if the three sides were mostly.

This is just signal level current, and all I need is the connection. No force, no heat, no vibration. I just wouldn't want weird issues because of a failed plating operation. Is it possible to do this?


r/PrintedCircuitBoard • • 2d ago

[Review Request] Rocket Fligth Computer

Thumbnail
gallery
27 Upvotes

This is my first pcb, a rocket fligth computer. I used a 4 layer layout with Signal-GND-Power-Signal stack. I poured gnd to the top and bottom layer and stitched gnd vias. The mosfet and the terminal block for the ejection charge will be on the second board. Is this board ready for manufacturing?

Note: It's Flight* lmao, sorry for the typo


r/PrintedCircuitBoard • • 1d ago

Questions about copper pours

3 Upvotes

A few questions I have about copper pours, beware I don't have any traditional education in this field, basically learning by doing. These questions assume a 4-layer board with SIG-GND-PWR-SIG stackup and effects on RF are also important.

Can I use copper pours basically as a replacement for traces where there is enough space, are there any downsides besides of course when dealing with impedance matching? Copper pours use the maximal area given to them while respecting clearance and whatnot, so it can have lower resistance than a specific trace, though that can result in them having "wavy" borders.

Similar question, are there any downsides to connecting a bunch of GND pins (resistors and/or caps for example) together using a copper pour while still giving each of them a close via to the GND plane i.e. a small GND plane on the top layer connected to the actual GND plane using vias? Or is it best to connect them individually to their vias using traces?

What about connecting multiple pins together with both a pour and traces?

Using pours as traces and the "small GND planes"
Using pours as traces and the "small GND planes"

r/PrintedCircuitBoard • • 2d ago

[Review Request] STM32F405 Rocket flight computer (My first PCB)

Thumbnail
gallery
54 Upvotes

This is my attempt at creating a rocket flight computer. This is built around the STM32F405. The mosfet will be on another board as well as the terminal block for the ejection charge. The telemetry module will also be on another board. The stm32 will communicate with the second board through the esp32 c3 super mini rx and tx.


r/PrintedCircuitBoard • • 1d ago

[Review Request] Shifting/RPM Lights using ESP32 & automotive CAN network

Thumbnail
gallery
1 Upvotes

Hello, this is my first PCB i've designed on my own and wanted to get some feedback on it and see if anyone has any advice. The board will be used on a race car to connect to the CAN bus from the ECU and using the ESP32 i will program logic to turn on certain LEDs based on the engine's RPM. A bit more specific info on it:

  • it's going to be used in automotive application, in harsh racing conditions (vibration, heat, moisture, etc.)
  • The 12V input is the automotive 12V power wire and it grounds to the chassis ground at the end of the harness
  • The CAN network it connects to doesn't terminate at the board, but close to it
  • The LDOs i chose were somewhat random but regulate to the 5v and 3.3v needed for the CAN transceiver and ESP32 respectively
  • I'm planning on programing the ESP 32 w/ a separate dev kit board that I've made in one of my PCB design classes
  • The LEDs are being powered directly by digital IO pins on the arduino, this feels wrong but I didn't wana add a bunch of transistors for them

If anyone has advice on how to make the board not 4 layers I'd appreciate that, I'd love to be able to save the money but wasn't sure how to make it happen without making a bigger board or having lots of extra vias.

I'm also looking for any advice with the routing/trace width selection & design given the automotive application, should I be worried about anything with the starter motor noise on the circuit, etc.

Any advice or tips to help me improve would be greatly appreciated. Thanks!


r/PrintedCircuitBoard • • 2d ago

[Review request] Fan BLDC driver PCB

Thumbnail
gallery
118 Upvotes

This is the driver board for a BLDC air purifier fan to handle motor control as well as ARGB (maybe WS2812b or equivalent). This board screws directly behind the motor I am using, hence the integrated encoder. I intend to make another board that plugs on top with an esp32 and a display so I can do some smart home integration next time.

Driver: DRV8316C

MCU: STM32G431

Input voltage: 12V

Motor max. current: <2A at max speed based on testing

ARGB max. current: <1A (will control number of LEDs accordingly).

I know running close loop FOC for a fan motor is crazy overkill, but I can't find any suitable DC motors to drive the 200mm fan. Most ESCs for bldcs are also overspecced and overpriced for this application. Also because I already have some of these bldc motors just lying around.

I used a bunch of mlccs near the driver power input mainly to avoid tall components. The original design had an electrolytic for more bulk capacitance, but it interfered with the board ontop.

I also tried to cramp everything on the top layer since I am reflow soldering this myself on a hotplate. The bottom few passives could be done with a heatgun, and the ic just using an iron.


r/PrintedCircuitBoard • • 2d ago

[Review Request] Radxa Compute Module 5 Carrier Board

Thumbnail
gallery
3 Upvotes

This is my first time designing a carrier board. I have included the following:

  • RJ45 connector (without Ethernet functionality)
  • USB-C port for power delivery (USB PD)
  • USB-A 3.0 port
  • Two MIPI CSI camera ports

Thank you!


r/PrintedCircuitBoard • • 2d ago

PCB feedback

Post image
0 Upvotes

Hi guys, I'm a beginner in pcb. Kindly review this and suggest changes. This is a DC to AC Inverter circuit


r/PrintedCircuitBoard • • 2d ago

[Review Request] Keyboard PCB

Thumbnail
gallery
3 Upvotes

Hey all,

I designed this keyboard PCB and was looking for any tips on how I could improve it, or if it will serve my purposes as it sits.

It is meant to be an nRF52840 (via an MDBT50Q-1MV2) powered Bluetooth and USB enabled keyboard with a built in I2C trackpad, featuring an onboard battery and charging circuit. I also intend to run ZMK on it.

This is my first PCB that I ever intend to get manufactured, so I would appreciate any feedback you have. The link to the GitHub repo for this keyboard is here within the Keyboard-PCB directory.

Thank you guys all so much in advance!


r/PrintedCircuitBoard • • 3d ago

14S drone PDB design review — 5V/12V regulators, INA228 monitoring and a 200A current target

Thumbnail
gallery
16 Upvotes

I’m designing a PDB for a drone and would appreciate some feedback before taking the layout further.

The design uses:

  • A 14S battery input, up to 58.8V fully charged
  • Two LM70660 buck converters targeting 5V and 12V at 6A each
  • An INA228 with an Eaton 100µΩ, 15W shunt for battery monitoring
  • An I²C power connection for Battery Monitoring
  • A four-layer PCB

The battery distribution target is 200A continuous, with roughly 240A peaks for a few seconds. This is a design target, not a tested rating.

I’ve included the schematic, individual copper layers and 3D views.

I’m particularly looking for feedback on the buck converter placement/routing, ground return paths, shunt Kelvin connections and high-current copper paths. Any obvious mistakes or things you’d change?


r/PrintedCircuitBoard • • 3d ago

[Review Request] Outdoor Solar Power Analyzer Board

2 Upvotes

The scenario is this: you are doing an outdoor solar project (including the panel, a battery up to 12V, a MCU and the load), normally during prototyping trying to hook up all the sensors needed can be a bit of a hassle and disorganized. Or you want to know the other parts of your project work right while you test / design one part eg a BMS or charger or MCU or even a load. That's kind of the idea behind this board.

This is also a personal project for me, through which I get better at electronics and PCB design.

Features:

  • Can measure voltage and current (get power, energy and possibly charge and discharge rate from that) for MCU, load, battery, solar
  • Can measure lux levels
  • Can keep time with onboard RTC
  • Had onboard slot for micro SD card for storing data (optional)
  • Max 1A 5V or 3.3V for MCU
  • Load is getting voltage straight from battery basically (goes through an INA236 for measurement first) so variable voltage but 2A max
  • Max 24V battery
  • Max 3A (subject to change) about 24V max solar panel 
  • Can measure temp, humidity, pressure through BME280

Main parts used:

  • XT60 connectors for solar and battery input and output (I have input and output so you can connect the battery and solar panel(s) to an external charger
  • MP5042GJ-P (for limiting current to 2A, it goes to max 28V and is connected to the main load output from the battery)
  • LMR36510ADDAR (buck converter to 5.5V, 1A. This feeds into the regs for the 5Vand 3.3V MCU outputs)
  • AP2115M-3.3TRG1 (LDO going down from 5.5V to 3.3V, max 1A for a 3.3V MCU)
  • MAX38903BATB+T (LDO going down from 5.5V to 5V, max 1A for a 5V MCU)
  • 4 INA236 (for current and voltage measurements for load, MCU [have to choose if you're using 3.3V or 5v], battery, solar)
  • BME280 (for surrounding temp, humidity, pressure sensor)
  • VEML7700-TT (for surrounding lux sensor)
  • MCP7940M-I_SN (RTC for keeping time like when you're logging data and want time stamps)
  • SD card holder (in this case, it's a BXCONN TF-CARD-9P for now)
  • Fuses for the solar and battery (ANR-7.5)

Operation:

You plug in the solar, battery. The MCU outputs that are 1A max, power the MCUs. There are also terminals (5V or 3.3V) for the VCC of the sensors. If you have a 5V MCU, connect 3.3V 1A output to 3.3V VCC then that powers the 3.3V sensors and you can connect to I2C and SPI like normal. If you have 3.3V MCU, put jumper on J6 since all 5V sensors can be powered by 3.3V. Use I2C and SPI lines as normal.

Connect the load. Insert SD card if you want and ofc, you'd have programmed the MCU.

Ok, so schematics (I used multiple pages and global labels so hopefully, this isn't too bad):

2A load limiter:

Buck converter to 5.5V, max 1A:

3.3V MCU output:

5V MCU output:

INA236's:

SD Card:

RTC:

BME280:

VEML7700:

I2C, SPI lines:

Schematics:

The PCB:

4-layer board going SIG --> GND --> GND --> SIG

I know this likely not the most optimal layout, I'm not too experienced but this the first version, I'm really just wanting it to work first then I can reiterate, optimize etc?

The groups of vias around (none are smaller than 0.3mm via hole and 0.6mm via diameter) are GND for thermal relief

Thank you all. I appreciate any feedback.


r/PrintedCircuitBoard • • 3d ago

[Review Request] Part 2 – fuel/speed CAN node for my E30, updated after your feedback

Thumbnail
gallery
5 Upvotes

Hey everyone, this is part 2 of my fuel pump / fuel level / speed sensor CAN node for my old BMW E30. First of all thanks alot for all the feedback on the first post, specially to u/GuidancePCB, u/mariushm and u/saltyboi6704, you guys made me rethink a bunch of stuff and the board is way better now.

Quick recap: board goes under the rear seats (inside the cabin), drives the fuel pump (~12A) with a BTS7004 high side switch, reads the stock fuel sender and the diff VR speed sensor and sends everything over CAN to the other nodes im planning (around 8). Personal use only, no homologation. The car has a battery cut off switch so the nodes are dead when its parked, and I left load dump out of scope on purpose (i know, i know).

What I changed:

  • Input protection: the TVS was after the reverse polarity diode, so a negative spike would land straight on the SS16 (only 60V). Now its a bidirectional SMBJ26CA before the diode, and the diode is a SS110 (100V) for extra margin.
  • BTS7004 supply: someone pointed me to load dump/negative pulses and after reading the infineon datasheet properly i realised the BTS VS had no TVS at all (they show a ~33V TVS on VS in the app circuit). Added a unidirectional SMBJ24A right at VBAT next to the switch. R_GND (47R) is now 0805.
  • Buck input caps: you were right, 10uF X5R 1206 at 14V is way less than 10uF. Now its 100uF electrolytic (damping) + 2x 10uF X7R 1206 + 2x 220nF, and the small ones sit right at each VIN/PGND pin pair. I also redrew them next to the buck in the schematic, it was confusing before, sorry about that.
  • Kept the LMR36015 instead of the LMR43610-Q1 / RTQ2104. Both look nice but they top out at 36V and the TVS clamps around 42V, so i’d be at the limit. The 60V part gives headroom, and JLC assembles it so the QFN isnt a problem for me.
  • CAN: removed the common mode choke. Kept a single 120R with a jumper because i dont know yet which nodes will be at the bus ends, and split termination with one jumper leaves the bus unbalanced when its open. The resistor is 1206 now in case CANH gets shorted to 12V.
  • Clock: swapped the 8MHz crystal for a 3.3V CMOS oscillator into PF0 (HSE bypass). Turns out the crystal i picked had 250 ohm ESR and the gain margin was pretty bad, so thanks for that one.
  • VREF: didnt use the internal VREFBUF. The fuel sender reading is ratiometric (I read both ends of the 150R reference resistor) and the reference node sits around 3.0V, so the 2.9V max internal ref would clip it. The 3V3 noise cancels in the ratio anyway.
  • Schematic: FB is wired directly and PG uses a proper net label now.
  • Bulk caps near every IC: didnt do this one. Its a small 62x72mm board, the 3x22uF buck output caps are only a few cm away and each IC has its decoupling per datasheet.
  • 4 layers: Top / solid GND / signals / Bottom. Pump and power pours on the outer layers, buck hot loop, clock and CANH/CANL on top. Added a lot of GND stitching vias, VBAT vias next to the BTS pad and 0.5mm copper to edge.
  • Added 3 debug LEDs (run / rx / tx)

Updated schematic and PCB attached. Any feedback is welcome, specially on the layout. Thanks again!

This message has been translated and corrected by an AI from Spanish to English. Neither the schematic nor the PCB was designed or built by an AI. I want to avoid any comments about the use of AI because the only use I’ve made of it—aside from the translation for this platform—is to compare different components and datasheet entries so that it could point out the differences between them.

Thank you very much for your advice to the users mentioned, as well as to future users and those not mentioned.


r/PrintedCircuitBoard • • 3d ago

First ESP32 Board Review & Solder Plate question

Thumbnail
gallery
4 Upvotes

Hello, I've designed this circuit board that will sit next to my heating vents and open and close them to better control the temperature in each room, built around an ESP32-H2-MINI-1U. The temperature of the vents means that regular Li Ion batteries may degrade, so I've gone for an LiFePO4 cell instead.

I've done my best to follow each chip's circuitry, but let me know if I've messed up

ESP32 H2 MINI 1

MCP73123/223

TPS613222ADBZ

I'm planning on using a hot plate, along with a stencil and solder paste to solder the surface mount components. This will be my first time doing this, so any advice is appreciated.


r/PrintedCircuitBoard • • 4d ago

Review Request: Recreating the pcm1808 for learning / requesting feedback

Thumbnail
gallery
18 Upvotes

Hello, I wanted the kicad for the breakout board of pcm1808 that I bought online.

I could not find the project online, decided to re-create it for learning.

I used a multimeter to check what is connected to what, now I would like some feedback on what I came up with.

  1. How does my layout look on the pcb? Do I have too many gnd vias or not enough?

In the doc, they recommend that I put vias underneath the pcm1808 as well as around it a bit.

My traces width is .2mm, I wont go over 10-20mA current. Looking for feedback to become more professional.

  1. Does the sch look ok? Looking for feedback to become more professional here as well.

  2. vref just goes to a few capacitors then to ground, does this make sense?

  3. I noticed on Reddit someone had an issue with the board they bought. They mentioned that one of capacitor was incorrect. I had no issues with my board I bought online, but I did notice the resistor going to LIN and RIN are 10k, which is much higher than the one recommend in the ti doc. Which I believe they also used the wrong capacitor for it. I went with what the doc said: (1 kΩ and 1000 pF). Is that a correct assumption?

Reddit post titles talking about the same findings: warning_about_fake_pcm1808_adc_chips_on_modules and pcm1808_modules_from_china_the_drama_continues

  1. In the doc, they recommend having grnd plane between clck signals. I have small islands with ground vias in between, is that enough? Some of the clck signals just have a gnd plane underneath, is that enough?

  2. My top and bottom layer are both net ground zones, is that ok?

  3. Does my bom look ok? (attached)

If you search for ti pcm1808, the section "9 Power Supply Recommendations" has all the info about vref, RIN, LIN, etc.

Just trying to get better at this, thank you in advance!


r/PrintedCircuitBoard • • 4d ago

Review Request: Fan controller

Thumbnail
gallery
15 Upvotes

my first ever pcb desing and i would love to know if i do anything mayor incorrectly?

It recieves 12v in and the buck converter steps it down to 5v for the xiao esp32-c6.

the esp32 is controlling 6 fans en reads 2 onewire ds20b18 sensors.

i wil be adding mounting holes later when i implemented al fixes

Please let me know if there is anymore info required.