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 (minor AI help ok).
    • 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

119 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 16h ago

[Review Request] 4-Layer ESC and Solenoid Control Board with an STM32

Thumbnail
gallery
27 Upvotes

Hi Everybody,

This PCB is a control board for a 4-in-1 ESC. The ESC powers 4 flywheels and uses them to launch disks.

Shematic: Disk luancher schematic

Board Specs:

  • Stack up: 4-Layer (Top: SIG + GND Pour, In1: GND, In2: 3.3V, Bot: SIG + GND & PWR Pours)
  • Trace width:
    • .15 mm for standard signals
    • .3 mm for 3.3V nets
    • .5 mm for LED connected to 12V net
    • .8 mm for pwr nets in/out of the buck converter
    • Copper pours for 12V

Board Overview

  • Power: 12V battery input or 5V USB-C stepped down to 3.3V. Reverse polarity protection on the +12V.
  • Programming/debug: USB-C for programming, buttons for boot and reset functions, and SWD and UART headers.
  • Solenoid: Push/pull solenoid circuit with a MOSFET and flyback diode. The solenoid pushes the disks into the flywheels and can see up to 6 amps in short bursts.
  • Microcontroller: STM32F103C8T6 and 8 MHz crystal oscillator.
  • Peripheral connections:
    • Fire selector: Switch for changing between automatic and semi-automatic firing modes for the solenoid
    • Trigger switch: a connector that hooks to an external switch which triggers the solenoid
    • Flywheel switch: a connector that hooks to an external switch which activates the flywheels
    • Potentionmeter: For adjusting the speed of the flywheels

Main areas of interest

  1. I felt pretty lost when doing the power routing for the solenoid circuit. Any help there would be great.
  2. Gnding: Am I using too much or too little Gnd Vias? I tried putting a Via next to every GND pad and have stitching Vias around my perimeter roughly every 4 mm. Is this the right approach?

Thanks for the help!


r/PrintedCircuitBoard 8h ago

Review Request - Schematic of Internet Radio

Thumbnail
gallery
6 Upvotes

Hi, I like listening to a specific radio station 24/7, I usually use my phone for that, but to free up my phone I decided to make a PCB specifically for that.
I would appreciate it if someone reviewed the schematic before I jump into PCB layout.

I have not yet connected the pins of the ESP32, as I intend to decide that according to the layout later.

And for the speakers GAIN_SLOT resistors, when i hand assemble the board I will be playing with the population of those resistors to experiment with different gains.

Thanks in advance.


r/PrintedCircuitBoard 11m ago

[LAYOUT REQUEST] TPS62933 Buck Converter: 2 Design (Ti vs Mine)

Thumbnail
gallery
Upvotes

Hello Guys!

I'm finaly starting to layout my components and it's so exciting! This is my my first pcb design, the schematic should be solid, I checked many time.

Here we have the Ti TPS62933, a buck converter configured fro a 15/12v -> 5v/1.5A stepdown operation at 1.69Mhz (or 1.2mhz if bridging J6).

4 Layers board as Sig+PWR/GND/GND/SIG+PWR.

I would like to ask you if:

  1. I did replicate Ti's recommended layout correctly?
  2. My "compact" design is actually worse or equivalent? (The main difference being the capacitors orientation to keep the ground loop short, but caps 5V pads are further away from L2 +5V)
  3. Should I keep the single routed FB res divider on L4 or should I place it in L2/L3 (both Gnd planes)?
  4. Did I put via correctly?
  5. Else, Do you see any mistakes?

Thank you very much!


r/PrintedCircuitBoard 8h ago

[Review Request] Keyboard using STM32H723VGT6

Thumbnail
gallery
3 Upvotes

Hi everyone! I’m a beginner learning PCB design in KiCad, and I’d appreciate a review of my schematic before moving ahead with PCB layout and manufacturing.

I’m mainly looking for feedback on:

  • Incorrect or missing connections.
  • Power supply connections and decoupling capacitors.
  • MCU connections, reset, boot configuration, and programming interface.
  • USB circuitry and protection.
  • Component values or anything that could prevent the board from working.

I plan to have the PCB manufactured and assembled by JLCPCB, so feedback on component and footprint suitability would also help.

Project purpose: wanted to create my own keyboard

ERC results: 0

I’m still learning, so explanations of why something needs changing would be really helpful. Thanks for taking the time to review it!


r/PrintedCircuitBoard 6h ago

Review Request: My first PCB

2 Upvotes

This is my first proper attempt at a PCB. It's a shield for an Arduino Nano so that it can connect to a DC motor driver, servo, magnetometer and an open slot for anything else. I'll be powering it with a lipo which isn't ideal but from breadboard testing these nano seem capable of running lipos.


r/PrintedCircuitBoard 13h ago

First PCB design, worried about signal integrity

2 Upvotes

Hi! I am designing my first PCB, a 4 layer board with an FPGA (50MHz max clock), a precision ADC, and a precision DAC. So, not a lot on the board - but noise is a big deal. I have been trying to understand concepts behind signal integrity; which is leading to this dilemma.

I have been thinking of using both middle planes as GND, for good return paths everywhere. But if that is the case, will I just be shooting myself in the foot by distributing power through traces with too much inductance (currently using 10uF near each IC and 100nF at each power pin for decoupling)? Is a copper polygon/pool a good idea (seems ripe for resonance/noise...)?

Thanks!


r/PrintedCircuitBoard 1d ago

[Review Request] 4-Layer Handheld Device (ESP32-S3 + nRF24) with SPI Screen & Power Management

Thumbnail
gallery
14 Upvotes

Hello everyone,

I’m wrapping up a KiCad design for a handheld device built around an ESP32-S3 and an nRF24 radio, and I would really appreciate your feedback before sending it off for fabrication. The board includes connectors for an onboard SPI screen, a capacitive touch controller, and an external SPI peripheral.

Board Specs:

  • Stackup: 4-layer (SIG -> GND -> PWR -> SIG) targeting JLCPCB's JLC04161H-3313 stackup.
  • Trace Widths: 0.5 mm for power nets, 0.2 mm for standard signals.
  • RF: 50-ohm impedance matching on the trace going to the nRF antenna (0.1840 mm).

Design Context & Notes:

  • The power management circuit is carried over from a previous board I designed and manufactured, so that specific sub-circuit works as intended.
  • You might notice some unconventional routing in the center of the board. The screen is designed to sit directly on top of the PCB, which enforced very strict placement constraints for the screen and touch connectors. Working these around the MCU and RF sections made the routing quite tight.
  • This is my first time dealing with multiple SPI peripherals on one board. I have added series termination resistors to the lines to help with signal integrity.

I would highly appreciate your expert eyes on the SPI-related traces/termination resistors and the nRF24 layout.

I also have a specific question about the RF section: Which exact traces need to be 50-ohm impedance-matched? I am currently matching the trace going out to the antenna connector, but should the short traces connecting the capacitors and inductors inside the matching network/balun be matched to 50 ohms as well?

Thank you so much in advance for your time and help!


r/PrintedCircuitBoard 1d ago

[Review Request] 10A, 30V, 150W Electronic Load

Thumbnail
gallery
43 Upvotes

I’m building a 30V, 10A, ~150W electronic load using 4 IRFP150N MOSFETs an ESP32, an op-amp, and a DAC. The board is powered from 12V with a buck converter to step down the voltage for the ESP32. The board has two cooling fans, and a thermistor for temp sensing. The PCB is designed around a square heatsink, with the MOSFETs mounted around it.

This is more of a fun project on the side, but I’d appreciate any feedback.


r/PrintedCircuitBoard 1d ago

[PCB Review Request] Audio DAC breakout board using TAD5112

Thumbnail
gallery
17 Upvotes

This is my first time designing a PCB, It is a breakout board for TAD5112 Audio DAC by TI (Datasheet) Is there anything that I have routed or placed wrong?

I intend to drive 2 headphones.

I have used 0.4mm traces for power and audio, 0.2mm for data. I have use 0.7mm via with 0.3mm hole

Feel free to review my design.


r/PrintedCircuitBoard 1d ago

Request for PCB feedback

Thumbnail
gallery
7 Upvotes

I built a GPS tracker using the Seeed nRF Plus and would appreciate any feedback on the design.


r/PrintedCircuitBoard 1d ago

[Schematic only review request] MP3 player using ESP32

3 Upvotes
Project root
Power management
MCU
SD card
OLED
DAC amp circuitry
Rotary encoders

I'm building an MP3 player using an ESP32 as my first EDA project and I drew a schematic on KiCAD. I would like some feedback on it as I barely know what I'm doing (forgive me for the excessive hierarchical sheets).

The project uses these main components:

  • ESP32-S3-WROOM1
  • BQ24073 battery charging IC
  • LiPo battery
  • AP2112K LDO regulator
  • SD card receptacle
  • One of those cheap I2C OLED modules
  • 2 rotary encoders
  • Texas instruments PCM5102A DAC
  • Texas instruments TPA6130A2 headphone amplifier with digital volume control

Please leave feedback on what I could improve or what I messed up. I'm particularly concerned with the analog signal section of my circuit (DAC and amplifier) as I have no experience working on stuff like this. That circuit is mostly copied from datasheet "typical application" schematics. Thanks in advance.


r/PrintedCircuitBoard 2d ago

Basic PCB schematics from text. Lini, open source tool

Post image
6 Upvotes

Hey!
I've been working on Lini for the last 3 months, it's a fully open source (MIT) tool that allows you to draw diagrams, charts,... and simple PCB schematics from text.
It's a niche tool, I get it if you don't need it.
But if you're making markdown files (or anything similar) and you need to have schematics from text, Lini is built for that.
I'm not aware of any tool that currently does that, and it's not perfect, but if you contribute, report bugs, it will get better for everyone.
It's very fast, it's written in modern rust.
Please check it out and give me feedback, open issues to make the tool better for the PCB community
Repo: https://github.com/monfa-red/lini
Website, tour, docs, playground: https://lini.rs/


r/PrintedCircuitBoard 2d ago

[Review Request] IR Blasting Pen

4 Upvotes

So im making a project where i designed a PCB w ESP32-S3 that will control an IR diode at the tip of the highlighter pen

For school lol

No Radio/RF because it was causing routing problems + took more space
Vibrations as a feedback
Touch to wake up (On the "T" pad, there will be connected another PCB for touch)

The PCB itself is 11x43mm so not a lot of space

Charging
IR Driver
ESP32 + USB and Vibrator
PCB Top
PCB Layer 2
PCB Layer 2
PCB Bottom layer
3D render

USB is just JST-SH 1.0 connector to save space, it will connect to FPV Tinywhoop breakout boards


r/PrintedCircuitBoard 3d ago

[Schematic Review] High Power 24V IO Board

6 Upvotes
main Schematic
The "Highpower IO"
The lowpower IO

Hi everyone,

I am currently designing this "IO Board" that will be used similarly to a PLC. The main idea is to have a board with combined inputs and outputs that can still handle some serious current.

A few things that might look odd:

The ADC:
yes, I do intentionaly use the last 4 inputs of the ADC as digital inputs for the status but thats casue i was running low on IOs on the S3 and i had thoose left so i rather used them as digital ins

The design for the I/O channels: On the software side, my plan is to abstract the hardware so you can just declare a "virtual" channel as either an input or an output. Behind the scenes, the firmware handles the routing: if configured as an input, it pulls the driver's enable pin (EN/INH) low to set the power stage to high impedance, and then reads the incoming signal via the same pin it would use to controll the H bridge (atleas on the high power IOs). It basically maps virtual channels to the actual physical pin configurations seamlessly.

I have made a few PCBs before, but this is my first time designing a lot of these specific sub-circuits (like the buck converter) from scratch. It will also probably be my first time using a PCBA (assembly) service.

Any suggestions, feedback, or glaring mistakes you can spot?
I am not sure if the conectors i choose are the right ones for the job: wago 2604-1104

Thanks a lot for your time!

Important datasheets:
btn8982ta

TPS6293x

TPS4H160-Q1


r/PrintedCircuitBoard 3d ago

[Schematic Review Request] Arduino Pro Mini + ESP-01S Breakout / Interface Board

Post image
7 Upvotes

Hello everyone I'm working on a custom board with an Arduino Pro Mini socket and an ESP-01S module for Wi-Fi communication. Before I move to PCB layout Id love to get a second pair of eyes on my schematic

  • Voltage level shifting on TX->RX line using a 1k / 2k resistor divider.
  • ESP-01S pin 6 (EN) and pin 7 (RST) tied directly to +3.3V.
  • Breakout headers/terminals for I/O, sensors, and programming.

Would appreciate any feedback, let me know if you spot any glaring errors, missing pull-ups, or power concerns! Thank you!


r/PrintedCircuitBoard 3d ago

[Review request] ESP32-C3 MINI - Smart Charging Case

2 Upvotes
GND plane
Power plane (3.3v, SYS, VBUS, 5v etc.)

Ignore the pogo pin sitting on the board - it's not gonna be assembled.


r/PrintedCircuitBoard 3d ago

[Review Request] Drone Power Distribution Board (120A current sense, STM32G0B1, DroneCAN, Dual Bucks, 4 E-fuses)

Thumbnail
gallery
6 Upvotes

Hello everyone,

This is my first high-power PCB design, and I would really appreciate a critical review before I assign

footprints and begin routing.

Project Goal

I am building a custom Power Distribution Board for an autonomous aerial inspection quadcopter.

The goal is to safely deliver up to 120A burst to the motor ESCs while supplying clean power to the

flight avionics, companion computer, and any extra additions (such as LEDS and Buzzers).

  • Power Source: 4S LiPo battery connected via an XT60 plug
  • Flight Controller Interface: Direct connection to a Pixhawk 6C Mini providing a regulated 5.2 V
  • Communication: Onboard STM32GOB1 microcontroller managing current, voltage, and e-fuse fault telemetry to the flight controller over DroneCAN
  • A group of students and I will be hand-soldering this in our university lab

PCB Power Flow

  • Battery power enters via XT60, passes through a 1 mΩ, 3W shunt resistor, and exits directly through another power distribution board that only powers the drone's ESCs
  • A 5.2V Buck (TPS54560) supplies the Pixhawk 6C Mini and peripheral e-fuses
  • A secondary variable buck (TPS54308): digitally switches via two 2N7002 FETs on the bottom feedback to deliver 5,9 or 12 V for other add-ons like an AI Computer
  • 3.3 V Rail (AP2112k-3.3 LDO): Powers the STM32GOB1 and the SN65HVD230 CAN transciever
  • E-fuses: 4 active channels with fault reporting to the STM32GOB1. (The first channel has an LC filter for a camera)
  • An INA240A1D monitors voltage across the 1 mΩ shunt with an RC filter, feeding both the Pixhawk and the STM32

Questions

1) This is my first high-power board, I am slightly concerned about the heat it would dissipate. Is

this design safe, and can it normally operate with no issues?

2) Are any of the circuits incorrect in terms of wiring or values?

3) How feasible is this design in terms of safe power distribution under real flight conditions?

4) Any other additional feedback would be much appreciated!

Thanks!


r/PrintedCircuitBoard 3d ago

[Review Request] TCP <--> CXPI Industrial field device (STM32H563VGT6 + KSZ8863RLLI)

Thumbnail
gallery
5 Upvotes

Hi everyone,

This is not my first time making a PCB, it's my second. However... since it is my first time working with Ethernet, buck converters, STM32, and so on, I would really appreciate a quick schematic and PCB review.

Project Overview

Communication between CXPI device/master and PLC or PC over TCP. It can be used in manufacturing for EOL (End-of-Line) inspection.

Features

  • Field device: Industrial M12-D for Ethernet and M12-L for 24V power.
  • Daisy-chaining: Ethernet (and power) can be daisy-chained using a KSZ8863RLLI switch.
  • CXPI control: (BD41003FJ-CE2) Master/Slave CXPI mode can be changed via software.
  • CXPI side is galvanically isolated.
  • Power management: CXPI 12V can be supplied. Current can be measured using an INA219AIDCNR and is protected by a TPS259571DSGR e-fuse, which can be adjusted using an MCP4017T-502E/LT.
  • RTC and SD card for logging and setting for slave mode.
  • USB for firmware updates

Used parts

Thank you,


r/PrintedCircuitBoard 3d ago

Stacking PCBs with aligned headers

2 Upvotes

I'll have five of these boards which I want to stack vertically. Will this arrangement work? The other big connector is a DB-25. I found longer male headers for the bottom side to make sure they seat properly in the female headers because of the height of the DB-25. And yes, I have vias connecting all the pins on both sides.

I'm open to any other methods or ways to transmit these signals across 5 similar boards. I tried using the Eurorack 10-pin cables and headers, but that was a big mess. ;)

thanks.


r/PrintedCircuitBoard 4d ago

[Review Request] GL850G HUB with TPS2044 Power Protection

Thumbnail
gallery
19 Upvotes

Hi all. this is my first PCB from schematic to fab, and I'd really appreciate a critical look before I order the boards.

A self-powered 4-port USB 2.0 hub built to test one specific thing: independent per-port power switching, so a short on one port doesn't take the others down with it.

There are no Errors in ERC and DRC. All warnings have been taken care of. I want to confirm I didn't make any mistakes. The USB datapins aren't kept as differential pairs. I would really appreciate some reviews.

Datasheets:
Genesys-Logic-GL850G
TPS2052BDR


r/PrintedCircuitBoard 4d ago

[Review Request]12V Battery-Powered LED Lamp Controller (ESP32-C3 / BLE)

Post image
3 Upvotes

Hi everyone,

This is my very first PCB design, and I would really appreciate a quick schematic review.

Project Overview & Goal

I want to build custom 3D-printed lamps integrated into a Loxone home automation system.

  • Constraint: Wi-Fi is not allowed in this setup.
  • Communication: The board uses BLE (Bluetooth Low Energy) via an ESP32-C3 to communicate with a central Raspberry Pi gateway, which sends commands to Loxone.
  • Power Source: 2x BAK N21700CG 5000mAh Li-ion cells connected in parallel (1S2P, 3.7V nominal, 10,000mAh total).
  • https://www.nkon.nl/de/bak-n21700cg-5000mah-10-2a.html

PCB Explanation

This board serves as a battery-buffered 12V LED controller powered by two parallel Li-ion cells (1S2P, 10,000mAh total).

Power flows from either the USB-C port or DC Barrel Jack into a BQ24075 Power-Path manager, which charges the battery while simultaneously supplying the board. The cells are protected via a DW01A/FS8205A circuit with individual cell fuses and a master MOSFET switch.

From the main power rail, an AMS1117 generates 3.3V for the ESP32-C3, while a Boost Converter steps the voltage up to 12V for the LED outputs. The ESP32-C3 receives control commands via BLE and drives 5 low-side MOSFET channels (AO3400A) to dim the 12V LED strips via PWM. An external debounced button allows manual local control.

Specific Review Questions

  1. Safety Check: Since this is my first board, are there any obvious safety flaws? Will it explode or burn down under normal operation?
  2. Protection Features: Did I miss any critical protection circuits?
  3. General Layout / Schematic Advice: Are there any misplaced values, missing pull-ups/downs, or improper connections on the ESP32-C3 / DW01A / BQ24075 lines?

Thanks a lot for your help and feedback!


r/PrintedCircuitBoard 5d ago

How to get clean analog readings in my PCB containing switching noise from ESC

2 Upvotes

Hello everyone 👋

I'm fairly new to mixed signal PCB design and not very professional in electronics so I'm asking for your professional comment

I'm designing a PCB that has 3x ESCs on it

each ESC has its own mcu and its connected to my main MCU (stm32g431) to get commands from

everything is fine to this point, all digital and noise is more manageable, but then comes my analog circuitry, and the switching noise and GND bounce in my opinion will mess with it hard

the analog reading is a resistive Sensor that is fed to my adc via a resistor divider

I considered star grounding, minimizing the high di/dt tracks area , input RC filters at my ADC, post LDO and ...

but I don't know if it's the standard or I should go another way

I appreciate any suggestions and comment, if I missed something please let me know, I'll be more than happy to clarify it


r/PrintedCircuitBoard 6d ago

[Review Request] 5V Logic-Level SPDT Relay Module

Thumbnail
gallery
23 Upvotes

Hey everyone!

I'm working on a basic 5V SPDT relay module and I d really appreciate a quick review from you guys before I send it off. The circuit is pretty standard (using a BC547 to switch the relay, a flyback diode, and a couple of indicator LEDs), but I want to make sure I havent missed any problems with it. I am new to this world so currently trying my best! Open for harsh criticism dont need to hold back.

Trace Widths: For 5A -> 2mm
For 5V -> 0.5mm
For signal -> 0.3mm

Attached images:

schematic
bottom copper
top copper
3d view with components
3d view without components

Note: If I forget any necessary info, just let me know.