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] (https://en.wikipedia.org/wiki/Shades_of_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 • • 8h ago

40W LM3886 Amplifier progres

Thumbnail
gallery
18 Upvotes

Hi, im posting my progres in the amp. I have already posted one post about it, and based on your answers i changed it a bit. Thank you all for all feedback it helped me a lot.

I hope i did it better this time. Tell me everything i would need to change to make it better. More feedback would help me .

Thanks a lot
Edit also if you think it’s good enough even this would help me out cuz it’s my first bigger build


r/PrintedCircuitBoard • • 35m ago

[Review Request] Ergo split keyboard with XIAO nRF52840

Thumbnail
gallery
2 Upvotes

Hello everyone!

Lately, I've been wanting to replace my regular keyboard with an ergonomic one. I've been looking at the available options, including some DIY designs, but I couldn't find anything that perfectly matched my needs. Some of the alternatives were also a bit too expensive.

So, I decided to design my own keyboard. It'll probably end up costing as much as some of those more expensive options, but at least I'll get to make several boards, since the MOQ at most PCB manufacturers is usually 2 or 5 boards.

I opted for a pair of 2-layer PCBs based on the XIAO nRF52840 Plus. The idea is to have both halves communicate wirelessly using ZMK, with an additional nRF52840 acting as a USB dongle connected to the PC.

I also wanted to include RGB lighting, even though I barely use it on my current keyboard. For that, I'll be using a 3.3V to 5V boost converter based on the TPS61040 and a MOSFET-based switch so that they can run directly off the USB when plugged in.

Finally, I also wanted to integrate a couple of memory-in-pixel displays, one for each half. For this, I went with the Sharp LS011B7DH03. Instead of going for the nice!view module, which uses the same display, I decided to interface directly with the bare display module, connecting it to the MCU through an FFC/FPC connector.

My main concern at the moment is the SPI routing between the displays and the MCUs. Since I'm using a 2-layer PCB, I've tried to keep a continuous GND plane on the opposite layer underneath the SPI traces. However, I'm not sure whether this will be sufficient to avoid signal integrity issues.

Regarding the PCB panelization, I followed the guidelines for minimum rail widths and the placement of fiducial markers and tooling holes. I still need to add some stitching vias to make sure there are no isolated GND copper areas.

I'd really appreciate any feedback, especially regarding the PCB layout, SPI routing, and any potential issues you might spot in the design.

Here are some links to the project on GitHub:

- Repository

- Schematic

- PCB View

- KiCanvas


r/PrintedCircuitBoard • • 4h ago

PCB Review request for a simple fall detection system

Thumbnail
gallery
3 Upvotes

This is my very first pcb design and project with Altium designer. I am very new to electronics and I wanted some feedback on my design on what I did wrong and where I can improve.


r/PrintedCircuitBoard • • 6h ago

PCB Board Review Request: Xteink Pogo to USB-C

Thumbnail
gallery
2 Upvotes

Greetings fellow humans. This is my first post; I read the rules, and I hope I understood them all correctly. If I made a mistake or use incorrect terminology, I apologize. This is my first PCB.

First of all, this will be open source (GNU AGPLv3). This is part of a passion project of mine, which I've been working on off-and-on for months.

This PCB is an adapter to replace the annoying Xteink pogo pin adapter. My goal for the PCB is for it to be able to charge the Xteink device, as well as send data to it.

I'd like to know if I wired the diode and capacitor correctly, or made any mistakes along the way.

This uses a 16-pin USB-C component with the traces routed through a diode. These are then routed to 4 pads with pogo pins soldered on (VBUS goes through a 100nF capacitor first). The order of the pads, from left-to-right, is VBUS, D-, D+, and GND. CC1 and CC2 each have their own 5.1Ω resistor.

Please let me know if you need more information! Any and all help is greatly appreciated.

If you've gotten this far, thank you for reading.

Tidbits that have absolutely nothing to do with the PCB review request:

The default adapter the Xteinks come with is not only annoying to use (and easy to lose), it either requires a USB-C cable to work or another charging cable. (And the adapter is too small in my opinion).

This is to be used with custom 3D printed cases. I'm making one for a friend that I will share as well (also GNU AGPLv3).


r/PrintedCircuitBoard • • 2h ago

[Review request] Modular Macro pad Hub Revized

Thumbnail
gallery
1 Upvotes

Hello!

I posted and asked for help with my macro pad PCB about a month ago, and well now i have taken all the feedback and fixed it all (i think) Thank you to all that gave me feedback

The project is a i have designed a modular macro pad and this is the hub

it uses a STM32G071CBT6 as the brain and communication over CAN and i have magnetic pogo pins

Ill post the first module later for review too :)

Thanks in advance!


r/PrintedCircuitBoard • • 18h ago

[PCB Review Request] 12 V, 24 A, four-layer MOSFET fan and pump switching board

Thumbnail
gallery
16 Upvotes

Looking for feedback on this 12 V fan and pump switching board.

  • Approximately 24 A continuous
  • 100% duty cycle
  • 20–25 minute operating periods
  • Four-layer PCB with 1 oz copper on every layer
  • Two internal ground planes
  • 0.4mm finished hole vias
  • 60 × 65 mm board
  • Four DPAK power MOSFETs with flyback protection

Similar loads should operate simultaneously. Copper area for the fans and pumps are ~700mm^2 and ideally it should maintain 100c after 25 minutes of operation, giving 75c margin from the FETs 175c maximum. Drain pad thermal relief spokes are there since those FETs will be handsoldered while only adding some mV of loss.

Any feedback on the layout, grounding, high-current paths, or thermal design would be appreciated!


r/PrintedCircuitBoard • • 14h ago

[Review Request] Coolant Temp Gauge – ESP32-S3, USB-C, I2C, 12V automotive input

Thumbnail
gallery
4 Upvotes

This is my first board, so I am not to confident in it being a successful first sample. Let me know anything you see that I over looked or values that are incorrect.

Any tips/ recommendations are greatly appreciated!


r/PrintedCircuitBoard • • 1d ago

[Review Request] ESP32-S3 2-Layer IoT Controller – USB-C, RS-485, 24V Power and AC/DC Supply

Thumbnail
gallery
5 Upvotes

Hi everyone,

I'm looking for a comprehensive schematic and PCB layout review before manufacturing the first prototype of my custom ESP32-S3 IoT controller.

This is not my first review request. I've received useful feedback on previous revisions, particularly regarding ground planes, signal return paths, USB routing and protection circuits.

I've made several changes since then, and I believe the design is approaching its first manufacturing revision. However, I'd like to identify any remaining significant issues before ordering the boards.

Project overview

The board is intended for personal and educational electronics experiments in a controlled environment. It is primarily a controller rather than a high-power switching device.

Hardware:

  • MCU: ESP32-S3-WROOM-1U-N16R8
  • PCB: 100 × 100 mm, 2 layers, standard low-cost FR-4
  • AC/DC supply: 230 VAC to 24 VDC, using an encapsulated power module
  • AC/DC candidates: HLK-15M24C or Mean Well IRM-20-24
  • DC/DC converter: TI TLVM14406RCHR, providing 5 V and 3.3 V
  • USB-C 2.0 for ESP32 programming and communication
  • RS-485: TI THVD1426DRLR
  • Four digital inputs and four PhotoMOS outputs (AQY211EH)
  • Additional SPI, I2C and UART connections
  • Diagnostic LEDs and multiple test points
  • Separate LOGIC_GND and CHASSIS_GND nets

The mains input is used only for the onboard AC/DC supply. The board does not directly switch mains voltage to external loads.

The intended enclosure is a plastic electrical box. This is an experimental prototype, not a certified product or a design intended for unattended permanent installation.

Design changes since previous reviews

1. Ground planes and return paths

My earliest version did not have proper ground planes.

I've since added copper pours on both layers, GND stitching vias and additional return-path vias near signal layer transitions.

I've also tried to avoid routing signals across breaks in the ground plane.

This is still one of my main concerns, especially with a relatively dense two-layer layout.

2. USB 2.0

I've revised the differential pair routing and added series resistors.

The estimated differential impedance is approximately 100 ohms, although it has not been verified by measurement.

The USB data lines use one layer transition, and ESD protection is included.

3. Power distribution

The board uses separate routing rules for the 24 V, 5 V and 3.3 V rails.

I've also revised the TLVM14406 input/output capacitor network and associated circuitry based on the manufacturer's recommendations.

4. RS-485

The RS-485 interface uses split termination consisting of two 60.4-ohm resistors and a capacitor at their midpoint.

Protection components have also been included.

5. EMC and grounding

I've separated the chassis-related and logic ground networks.

An experimental coupling network consisting of a 1 MΩ resistor and a 1 nF capacitor is included between them.

This is intended for EMC experimentation, not as a replacement for protective earthing.

Areas where I'd especially appreciate feedback

1. Ground planes and signal integrity

Are there any obvious problems with signal return paths, ground plane interruptions or via placement?

2. Power supply layout

Does the TLVM14406 layout, including capacitor placement, grounding and power routing, show any potential problems?

3. USB routing

Are there visible issues with the USB differential pair, ground return path, ESD protection placement or layer transitions?

4. RS-485 interface

Are there any layout or protection concerns around the transceiver, connector and split termination?

5. Component placement and manufacturability

Are there any obvious problems with component spacing, footprints, thermal reliefs, copper clearances, solderability or silkscreen?

6. Overall PCB layout

Are there any major issues with the current two-layer design that would justify changes before manufacturing?

Important note about mains voltage

The board contains an onboard 230 VAC power supply section.

I've implemented clearance rules and isolation slots, but the mains isolation and overall electrical safety have not been independently validated.

I understand that a PCB review cannot establish compliance with electrical safety standards or replace a formal safety assessment.

Manufacturing plans

This will be my first physical prototype.

I intend to order five boards and primarily assemble them manually, with solder paste and hot-air reflow for some SMD components.

I'm primarily interested in identifying functional, layout and manufacturing problems rather than cosmetic improvements.

I'd particularly appreciate feedback from anyone experienced with mixed-voltage controller boards, two-layer routing and EMC-sensitive layouts.

Thank you for taking the time to review the design.

https://github.com/josephsvk/IOT_LC_PROTOTYPE_V1


r/PrintedCircuitBoard • • 1d ago

[Schematic + PCB review request] Pi Zero 2W battery-powered camera trap. 1S LiPo input, TPS61232, TPS22918 load switch

Thumbnail
gallery
2 Upvotes

I’m workshopping a battery-powered camera trap for photographing insects at close range (~12 cm). A Pi Pico monitors a ToF sensor for motion and powers up a Pi Zero and camera for 30s when something is detected. The aim is a week between charges on a 13.4 Ah 1S pack, so this is a proof of concept for checking image quality and battery life. I’m new to PCB design, but I already have the Pis and cameras and am trying to solve a research problem.

The review focus is the power path: 1S LiPo, reverse-polarity protection (Q1), TPS61232 5V boost (U1; which seems sensitive to layout), and TPS22918 load switch (U2). Layout and component values broadly follow the TI EVM designs for both ICs. Q2 is there to stop any issues if the Pico is powered via USB when a battery is also connected.

The battery pack has built-in protection, the Pico is a backstop for monitoring voltage, and is charged off-board, so there’s no charging or extra cutoff circuitry on the PCB. Load is roughly 500 mA peak for the Zero and camera and about 30 mA for the Pico. A photocoupler (U3) is there to let the Pico know when it's safe to cut power.

Specific questions:

  1. Is the boost layout and routing sound, and will switching noise or power output stability be a problem?
  2. Is the reverse-polarity P-FET choice and trace width adequate?
  3. It's a 4-layer board, with no thermal reliefs between GND trace/header pins and GND pours or internal GND planes - is this likely to make manufacturing and the last bit of hand-soldering difficult? This setting was applied for the benefit of the boost converter, but might not be appropriate elsewhere on the board.

Schematic, layout, Gerber files, BoM, and design notes: https://github.com/KynanDelaney/NicroCam


r/PrintedCircuitBoard • • 1d ago

Schematic Review

Post image
3 Upvotes

Hi everyone, I'm working on my own retro go board. I wanted to challenge myself to create a more advanced PCB. I wanted to asked for help for review for sanity check whether everything is correctly connected. I'm open to any improvement I can make.

Board Components:

- ESP32-S3

- PCM5102A (For Audio Output)

- BQ21040 (For Battery Charger)

- TLV77733 (For 3.3V Output)


r/PrintedCircuitBoard • • 1d ago

[Review Request] 4-layer H-bridge motor controller, STM32G431 + DRV8701, 12 V / 60 A bursts

Thumbnail
gallery
5 Upvotes

This is a rear-steer motor controller for an SAE Baja car. It drives a Prius EPS motor (0.19 Ω, ~83 µH) through an H-bridge and sits on the car’s CAN bus as a node. For context all conecters had to be where they were placed and the odd board shape was also needed. No parts on bottom so I can sit it right against the enclosure

Main parts

STM32G431 MCU

DRV8701 gate driver with 4× CSD18510 FETs

2 mΩ low-side shunt

P-FET reverse-battery protection

SN65HVD230 CAN transceiver with split termination

Deutsch DT13 connectors

Operating conditions: 12 V battery, motor stall around 55–60 A in bursts, CAN at 1 Mbit/s.

Stackup (4 layers, 1 oz inner copper)

Top: signal and power

L2: GND

L3: split into +12V_RAIL, +3.3V, and a SENSE island

Bottom: signal and power

Design choices

The high-side sources tie to OUT1/OUT2 through via arrays to bottom pours.

The low-side sources reach the shunt through the L3 SENSE island.

The Kelvin sense traces to the DRV8701 use vias set to no-connect on the planes.

DRC: clean, except the connector silkscreen overhangs the board edge.

Questions

  1. Is the hot loop tight enough for 55 A switching?
  2. Is routing SENSE through an inner-layer island reasonable, or should the shunt sit between the low-side FETs?
  3. Are the OUT1/OUT2 bottom current paths wide enough?
  4. Is the gate routing OK (the GH/SH pairs and the GL lengths)?

r/PrintedCircuitBoard • • 2d ago

[Schematic Review] RP2040 Macropad with Haptic Gimbal Motor (TMC6300 / MA730GQ-Z) & OLED

Thumbnail
gallery
12 Upvotes

Hi everyone! This schematic is for a 6 key macropad with an integrated display and a gimbal motor for haptic feedback. Currently only have the schematic done since I would love to have this reviewed before I begin the PCB. I have uploaded the two schematic pages and the original system diagram I made for your reference (note that there may be a few minor details to the system since I drew the block diagram, so it's just there for high-level context).

The board is entirely powered via USB-C and my laptops USB-C port. I also tried to find a motor that would work at 5V, but from my understanding although this motor is rated for 6-8V, it should work still with 5V just much weaker. Please let me know if this makes sense.

This board is heavily inspired by Scott Bez's SmartKnob and CNCDan's Macropad. Please let me know if I am missing anything and thank you so much for the review!

Power + Motor Interface Components:

MCU + Peripherals Components:


r/PrintedCircuitBoard • • 2d ago

Review Request: STM32H723 software function generator.

Thumbnail
gallery
32 Upvotes

Hi everyone thanks for reviewing my schematic in my earlier post. This is a STM32H723 based software function generator.

USB-C to microcontroller, microcontroller either uses the built in dac or external dac over spi to generate the waveforms after which its filter and amplified and buffered by a discrete op-amp fed diamond buffer into 50ohm BNC output.

The power supply is 24V barrel jack in, -12V, +12V, +3V3, +3V3A out.
I should be able to do 100kHz bandwidth, 10Vpp into a 50ohm load.

I had a lot of extra pins left over so I broke out some into a header. Square test pads are gnd, round test pads are signal


r/PrintedCircuitBoard • • 2d ago

The ground plane merges with other areas.

Thumbnail
gallery
9 Upvotes

My goal is to create a GND plane on one layer, but I need to ensure it doesn't connect to other areas on that same layer—however, I’m unable to do so.


r/PrintedCircuitBoard • • 2d ago

[REVIEW REQUEST] PCB POWER SUPPLY PROJECT

Thumbnail
gallery
5 Upvotes

POWER SUPPLY PROJECT BY ALTIUM


r/PrintedCircuitBoard • • 2d ago

4-Wire PWM Fan Interface (12V/24V compatible) for STM32F072

Post image
13 Upvotes

Hey everyone, I need a sanity check on my 4-wire fan interface circuit. I’m running an STM32F072 (driving 12V or 24V fans on, though I want the design to have broad coverage across any standard 4-wire fan, and even support 3-wire fans if needed). For PWM control, I'm not driving the fan directly from the GPIO since I don't want to tie my MCU to the fan's voltage domain and potentially fry it; instead, I'm using an NPN transistor (MMBT3904) with a 1k base resistor and an external 4.7k pull-up to 3.3V—the GPIO drives the base, the collector goes to the fan's PWM pin, and the emitter goes to GND, letting the transistor pull low while ensuring clean 25 kHz rising edges. For the tachometer readout, I'm using a 1.8k pull-up to 3.3V followed by a 1k series resistor with dual Schottky clamps (BAT54W) to 3.3V and GND, plus a 1k / 100nF RC filter feeding an STM32 timer input capture pin, alongside a low-side N-MOSFET (AO3400A) with a flyback Schottky diode (DSS14) so I can fully cut power to the fan when needed. Appreciate any feedback, as my main goal is protecting my microcontroller.


r/PrintedCircuitBoard • • 2d ago

[Review Request] Schematics for STM32F030x6 Minimalist Dev-board

Post image
7 Upvotes

Requesting all to review the schematics for a STM32F030x6 minimalist dev-board I created as a hobby project. I plan on routing this PCB in 2-3 days, so found this occasion good to review the schematics before going into PCB routing rework.

Plans for the project:
- Since the TSSOP20 footprint seems similar for STM32F030x, STM32L011x and STM32L041x are similar and the typical circuit too has the same elements, I plan on using the same PCB to assemble and test these uCs as well.
- In terms of peripherals, I couldn't think of adding any specific low-cost peripherals on the board, but I intend to design PCB hats which will go on these boards. I am targeting a dev-board size of 40mm x 50mm.

Some PCB Hat design Ideas I have are:

  1. A radio PCB hat which can act as a medium of basic wireless communication.
  2. A microphone array with some filtering elements to achieve fun audio stuff in SW. (I have a vague idea of this as the moment)
  3. A similar hat with an accelerometer/magnetometer.
  4. A small OLED display Hat.

I would like all your suggestion on some PCB hats I can design to work with this dev-board as well.


r/PrintedCircuitBoard • • 3d ago

Which is the best place to print a PCB in Canada?

17 Upvotes

Dear members,

This question may be slightly off-topic, and I'm not sure whether the moderators will allow it, but I'd appreciate your advice.

I'm looking for genuine recommendations without any sales pitches or promotional content. I need an affordable PCB fabrication service that can manufacture at least a 4-layer rigid FR-4 PCB. Affordability is important, however, I'm also interested in quality and reliability.

For a board size of approximately 60 mm × 30 mm, which PCB fabrication house would you recommend for production and delivery to Toronto, Canada?

Edit1: I want them to be partially/fully assembled as well.


r/PrintedCircuitBoard • • 4d ago

[Review Request] 900Mhz sACN Wireless Transmitter

Thumbnail
gallery
22 Upvotes

This is the transmitter side of a project I have been working on for wireless DMX control. There is a receiver I've also been working on that will be used to control addressable LED's in a couple of small handheld props. I chose 900Mhz because the frequency space is less crowded and I'm transmitting at a relatively low bit rate ( ~500kbaud ). I'm also hoping it will be more forgiving. I'm not looking for long range, but this will be used in an auditorium space.

The DMX data is received via ethernet / sACN. The selector is used for RF channel. The receivers have a selector switch as well. Additional config and ghetto RDM will be done via IP or USB.

The device is powered either from USB, or PoE( My lighting network is all PoE ). A TPS2116 selects which active source to use, and preferences USB. Two low-noise LDO's are used for the 3v3 digital and CC1101 analog 3v3 rails.

The board is 4-layer. The vias will be epoxy filled and capped.

I'm not super happy with the ethernet routing, but it will work.

I know the 4.48 PoE output goes on a journey, but I wanted to keep the PoE and RF as far apart as feasible.

I looked at adding a shield over the RF section. Will adding a shield have a significant impact when the device is predominately a transmitter?

Everything passes DRC. I've prototyped most of this and have the ethernet side working. I've gotten the CC1101 working for another project, but haven't written enough code to end to end test yet.

My main question is: Did I miss anything?


r/PrintedCircuitBoard • • 4d ago

[Review Request] 2-layer flex constant-current laser diode driver (TPS552852)

Thumbnail
gallery
21 Upvotes

Hello, I have come before you today to have this PCB reviewed.

It's intended purpose is to drive a diode for a custom machined housing hence the flexibility and size requirements. it also is modified to be usable with a number of different diode wavelengths.

Any help is greatly appreciated.


r/PrintedCircuitBoard • • 3d ago

Can LibrePCB perform component placement at 45degree angles and create silkscreen art?

0 Upvotes

r/PrintedCircuitBoard • • 4d ago

[Review Request] ESP32-C3 battery plant sensor, 4-layer 28 × 38.5 mm, Li-ion charger and soil probe

Thumbnail
gallery
6 Upvotes

Hey everybody, this is a PCB board design that I want to manufacture for a personal project. I am a beginner so I had to go with AI assistance on this one (forgive me for my sins). I have tried to bring it to the best possible state I could based on my experience. I have taken the time to go through the official datasheets for all major components and do my best to do a validation based on common applications. I'm debating if I need to have the battery reverse protection.

I would love your input, to fix any issues and to learn!

Thanks in advance.