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 • • 2h ago

[Review Request] Two-stage boost converter 5V to 170V

Thumbnail
gallery
5 Upvotes

I'm designing a two stage converter to convert 5V from USB to 170V, output current expected to be 20-25mA maximum.

First stage:

SX1308 / MT3608, 1.2MHz boost converter, 10uH inductor, converting 5V to 24V

Second stage:

TPQ50551Q / LM51551 controller, set to about 500khz, 100uH inductor, converting 24V to 170V.

There are two overlapping footprints to test out two sizes of inductors for different output current needs. The design needs to be low profile (3mm max) and as small footprint as possible.


r/PrintedCircuitBoard • • 56m ago

[Review Request] Custom82 – 75% hotswap keyboard, ATmega32U4, per-key RGB + upward-facing LED bar

Thumbnail
gallery
2 Upvotes

Hi everyone!

This is my first custom keyboard PCB and I'd love a review before sending it to fab. It's a 75% layout with per-key RGB and an LED bar along the top edge that shines upward (meant to light up through a diffuser in the case).

Specs

  • Layout: 75%, 82 keys + EC11 rotary encoder (with push button) in the top-right corner
  • MCU: ATmega32U4 (TQFP-44) with a 16 MHz crystal, planning to run QMK
  • USB: USB-C (HRO TYPE-C-31-M-12), 5.1k on CC1/CC2, 22Ω series resistors on D+/D-
  • Switches: MX hotswap sockets, 1N4148W-style SOD-123F diodes, Cherry plate-mount stabilizers (2u ×2, 6u spacebar)
  • Per-key RGB: 82× SK6812MINI-E (reverse mount, shining through the switch)
  • LED bar: 23× SK6812 5050 on the top side along the top edge, facing up
  • LED chain: a single data line from the MCU (PD3) → all 82 per-key LEDs → all 23 bar LEDs (105 LEDs total), 100nF decoupling cap per LED
  • Matrix: 6 rows × 16 columns
  • Board: 309.7 × 144.6 mm, 2 layers, 1.6 mm, GND pour on both sides, 6× M2 mounting holes
  • Routing: +5V mostly 1.5 mm, signals 0.2 mm, vias 0.6/0.3 mm
  • DRC: 0 unconnected pads, 0 clearance errors (only silkscreen/library warnings left)

Things I'd especially like feedback on

  1. Power budget: 105 SK6812s can draw way more than USB can supply. I plan to cap brightness in firmware. Is that enough, or should I change something in hardware (fuse, power-limiting, splitting the chain)?
  2. USB protection: there is currently no polyfuse on VBUS and no ESD protection on D+/D-. Should I add them (e.g. USBLC6-2SC6 + a PTC)?
  3. MCU area: decoupling placement, crystal placement/routing, and D+/D- routing from the connector to the MCU.
  4. LED data line: the MCU drives the first LED directly, with no series resistor or level shifter. With 105 LEDs on one chain, is that OK?
  5. LED bar: any concerns with the upward-facing 5050s on the top edge (placement, current through the +5V trace, heat)?
  6. Anything else that looks off: layout, routing, manufacturability.

Images

  1. 3D isometric view
  2. 3D top
  3. 3D bottom
  4. PCB, all layers
  5. Front copper
  6. Back copper (mirrored)
  7. Routing only (ground pours hidden)
  8. 3D zoom: MCU + USB-C
  9. Routing zoom: MCU + USB-C
  10. 3D zoom: LED bar
  11. Zoom: a single hotswap key (socket + diode + per-key LED)
  12. Schematic: MCU, USB-C, encoder, decoupling
  13. Schematic: key matrix (6 rows × 16 cols)
  14. Schematic: LED chain (82 per-key + 23 bar LEDs)

(The hotswap sockets have no 3D model, which is why only their pads show up in the renders.)

Thanks a lot for taking the time to look at it! 🙏


r/PrintedCircuitBoard • • 22h ago

[Review Request] 4 layer RP2040 + USB-C board, 50 x 49 mm, KiCad 10

Thumbnail
gallery
10 Upvotes

Hi friends, I would like a review before I order this. It is a small RP2040 board with USB-C, 7 LEDs, BOOT and RESET buttons and a push switch.

Gallery order: 1 top composite, 2 to 4 3D views, 5 to 8 copper layers L1 to L4, 9 full schematic, 10 to 14 schematic zoomed in sections, 15 stackup and impedance table.

Board

  • 4 layers, FR4 Isola 370HR, about 62 mil, 1 oz copper on all layers
  • L1 parts and USB pairs, L2 solid GND, L3 3.3 V plane, L4 other signals
  • 50 x 49 mm L outline, four M4 plated holes tied to GND, all parts on the top side
  • USB pairs: 5.0 mil trace, 4.0 mil gap, 90 ohm differential, on L1 over L2
  • 6 mil min track and space elsewhere, 8 mil min drill, 8 mil drill to copper, 12 mil tented through vias, IPC Class 2, 1 A max
  • KiCad DRC and ERC are clean
  • Layout was scripted and most non critical nets were autorouted, so it is not hand tidied

Questions

  1. USB pairs at 5/4 mil on L1. The fab table says 89.7 ohm, my field solver says about 94.5 ohm. Is that a yield risk?
  2. The stackup table shows 0.5 oz inner copper, but I am using 1 oz inner. Does that change the impedance enough to worry about?
  3. Five tented 12 mil ground vias in the RP2040 centre pad. OK, or should I move or fill them?
  4. The USB-C footprint is custom from the datasheet (0.40 mm holes, 5.5 mil annular ring, 0.60 mm shell slots). Anything wrong?
  5. 8 mil power neck downs at the RP2040 pads (16 mil elsewhere) with a 1 A max. Fine?
  6. L4 routing: return paths, anything crossing plane gaps, anything a fab would flag.
  7. One sided assembly with a through hole push switch and USB-C. Any assembly problems?

KiCad 10.0.8. I can share Gerbers or the project if that helps. Thanks!


r/PrintedCircuitBoard • • 1d ago

[Review Request] ESP32-S3 and ov2640 digital camera

Thumbnail
gallery
14 Upvotes

Hello everyone,

This is my first LiPo battert powered project, so I might have got alot of things wrong in the power section.

Stack up : SIG/GND/PWR/SIG

Power: (My main concern)

Battery charging : MCP73871 for 40mm*30mm LiPo battery ( JST_EH_S2B-EH_1x02_P2.50mm for battery connector) (TH1 thermistors footprint is not for SMD component, just for soldering pads for external thermistor)

LDOs : LP2985-3.3 , LP2985-2.8 (ESP32 controlled) , XC6206)122MR (ESP32 controlled)

Peripheral:

microSD card (SPI mode)

ILI9341 TFT LCD (2.8 Inch)

ov2640 camera (Hirose_FH12-24S-0.5SH_1x24-1MP_P0.50mm_Horizontal for connector footprint)

MCU:

ESP32-S3-WROOM-1-N4R8 (USB-C programming)

Thank you in advance!


r/PrintedCircuitBoard • • 19h ago

Anyone here using Allegro PCB Designer tool for routing?

3 Upvotes

Does anyone know shortcut to turn Bubble mode on and off?

Also please suggest some tutorials or books to enhance my knowledge of Allegro.

TIA


r/PrintedCircuitBoard • • 22h ago

[Review Request] DC UPS 12V 1A for GPON terminal (schema only)

Thumbnail
gallery
4 Upvotes

Hi there! I'm trying to get into PCB creation and this thing I would consider my first 'portfolio project'. I have a real prototype already doing its deed, although it uses ready-to-go modules and LM2596 instead of CN3277 chip. But it takes so much space and it was difficult to solder and glue all the components to the box properly, so I figured I could make a PCB.

I won't hide that I'm using AI to learn my way through, but I did read datasheets and went through all the formulas needed and I'm asking questions at every step to understand what's going on and why things like 'reverted' MOSFET were added at the very start of the board.

It looks finished, but I can't do a proper simulation since I couldn't find CN3277 ready SPICE files.

Anyway, I'd greatly appreciate a review from real people with real knowledge.


r/PrintedCircuitBoard • • 1d ago

[REVIEW REQUEST] STM preamplifier

Thumbnail
gallery
4 Upvotes

TIA Preamplifier for Scanning Tunneling Microscope (STM)

Based on Dan Berard's design.

  • Requirements: Tunneling current is in the sub-nanoampere range, so we need to take into account leakage currents from the PCB and choose an op-amp with low input bias current.
  • Op-Amp: LMC6482 was chosen for the job (it's cheap, has low input bias current, and low noise).
  • Assembly: The second leg of the feedback resistor, the wire from the tip, and pin 2 of the op-amp will be soldered together on top of a Teflon standoff.

Questions

Q1: Should I rather go with a guard ring and SMD resistor?

Q2: Are there too many vias stitching the top and bottom grounds together?

Any feedback is welcome. Thanks in advance.


r/PrintedCircuitBoard • • 1d ago

[REVIEW REQUEST] audio streaming and recording for voice recognition project

Thumbnail
gallery
6 Upvotes

BOARD STACKS UP:

A 4-layer board (sig-gnd-pow(3.3v)-sig)

POWER SUPPLY COMPONENTS:

7.4V battery input

TPS5430DDA buck converter, lowers 7.4V to 5V

asm1117-3.3 LDO to convert 5V to 3.3V

KEY COMPONENTS:

INMP441 microphone

MAX98357 audio amplifier

USB-C input for both power and communication.

W25Q128JVS 16MB external quad SPI flash.

QUESTIONS:

Since I'm designing the board so that USB and battery can be used at the same time, I used a diode to protect from reverse polarity, but is it the correct way to do it?

Since I have a dedicated power and ground plane, I didn't have a ground pour on either the front or back layer. But I'm not sure if that is correct for this board. Should I do a ground pour on both the front and back layers?

DATASHEETS:

W25Q128JVS

https://www.mouser.com/datasheet/2/949/w25q128jv_revf_03272018_plus-1489608.pdf

MAX98357

https://www.analog.com/media/en/technical-documentation/data-sheets/max98357a-max98357b.pdf

inmp441

https://www.alldatasheet.com/datasheet-pdf/pdf/1244625/ETC1/INMP441.html

TPS5430DDA

https://www.ti.com/lit/ds/symlink/tps5430.pdf

asm1117

https://www.alldatasheet.com/datasheet-pdf/pdf/205691/ADMOS/AMS1117-3.3.html


r/PrintedCircuitBoard • • 2d ago

[REVIEW REQUEST] STM analog board.

Thumbnail
gallery
17 Upvotes

Overview

A 4-layer board (Signal / GND / GND / Signal + Power) containing an ADC, DACs, and op-amps to generate piezo drive and sample bias voltages for a Scanning Tunneling Microscope (STM), powered by LiPo batteries.

Based on Dan Berard's STM electronics.


Key Components

  • ADC: 1× ADS8685 (16-bit SAR ADC, +5 V / +3.3 V, internal reference) — samples amplified tunneling current from the preamplifier.
  • DACs: 4× AD5761ABRUZ (16-bit bipolar DACs, ±15 V / +3.3 V) — generate voltages for the piezo disc and sample bias.
  • Op-Amps: 2× OPA2227 — sum and subtract outputs from the DACs.
  • Digital Isolators: ISO7760 and ISO7762 (+3.3 V) — isolate the board from a noisy USB-powered MCU on a separate board.

Power Architecture (3× TPS7A4901DGNR + 1× TPS7A3001DGNR)

  • +21 V → +15 V: Analog DACs & op-amps
  • +21 V → +5 V → +3.3 V: Kept separate from +15 V so digital/isolator switching doesn't pollute the analog rail
  • -21 V → -15 V: Negative analog rail for DACs & op-amps

Specific Questions

  1. Is the power trace layout okay? (It turned out a bit tangled.)
  2. Can the DAC SPI clock be routed down to the bottom (Signal + Power) layer and back up?
  3. Is the layout of the LDO traces and their surrounding components correct?
  4. Will the ADC and DAC outputs stay sufficiently free from digital noise with this layout?

All feedback is welcome—thanks in advance!


r/PrintedCircuitBoard • • 2d ago

Review Request - PI Shield for Digital Camera

Thumbnail
gallery
12 Upvotes

Hey guys, this is my PCB for a digital camera that acts as a shield to plug into a Raspberry Pi Zero 2 to add a display, battery with a charging circuit, and buttons. Note that it's intended that the front of the PCB will face towards the Pi, as the display will be on the back of the PCB with the buttons. The PCB is two layers with a ground pour on both connected with vias. I've tried to use some fat traces (0.6mm for the USB Port and 0.5mm for the 5V net) because I'm conscious of how much current that will be drawn. I'll also be getting this assembled.

Here's an explanation of the main components:

1. Battery management and charging circuit:

- Is based on this Lipo charger from Adafruit: PowerBoost 1000 Charger - Rechargeable 5V Lipo USB Boost @ 1A [1000C] : Adafruit Industries, Unique & fun DIY electronics and kits

- Uses a MCP73871for the Lipo charging: Stand-Alone System Load Sharing and Li-Ion / Li-Polymer Battery Charge Management Controller

- Uses a TPS61090 to step up to 5V for the Pi: Synchronous Boost Converters With 2A Switch (Rev. A). Note that I will be connecting a switch to the enable pin here to turn on/off the board.

- Will be using a standard 1100 mAh LiPo battery: EEMB 3.7V Lipo Battery 1100mAh 603449 Rechargeable JST 2.0mm 1-Pack : Amazon.ca: Health & Personal Care

2. Display circuit:

- Will be using this 2.8" TFT display driven over 4-wire SPI: NHD-2.8-240320AF-CSXP-F.pdf

- Using the PAM2808 LED driver for the display backlight: PAM2808

3. IO:

- I have three pushbuttons on the back of the PCB

- I have attached some JST connectors to connect a power switch (which connects to the boost converter enable switch) along with a microphone: Adafruit I2S MEMS Microphone Breakout - SPH0645LM4H : Adafruit Industries, Unique & fun DIY electronics and kits

Please let me know if I've made any mistakes or if you have any advice! Cheers


r/PrintedCircuitBoard • • 2d ago

Sanity check on PCB design quotation.

1 Upvotes

Quoting a from-scratch board and I’d like a reality check on my day count before I send it. Not looking for anyone to do the work, not Job seeking, searching for freelance work — just whether my number is sane and standard quotation practices

Board

  • 6 layers, 0.8 mm, roughly 30 × 40 mm, parts on both sides
  • Component height capped at 1.6 mm top side, 1.0 mm bottom
  • ~600 pins, ~110 components

For PCB with these specs what is a general hourly rate. My knowledge is 5-6k per hour. Let me know if this is the correct rate for India. And also for schematics, component placement and routing estimate of 2 weeks is good to go or more?

How a PCB design quote can be given? Any standards that are followed in the Industry in India and global? Wrt 2,4,6 layers, Processor and no processor boards, Wifi/ble, and component based quote. Routing and PCB dimensions?


r/PrintedCircuitBoard • • 2d ago

Review Request- Devboard Schematic

Post image
0 Upvotes

So I am trying to make a development board that uses the ESP32-S3-MINI, an IMU, and a microphone that will control a small NeoPixel LED strip through voice commands. I made this schematic using symbols from LCSC, and the pinout matched with the datasheet and I created it mostly by looking at the datasheet. I have been running ERC and it comes up with 0 errors, but I still want any feedback on how I should change my schematic and maybe add/remove some things so that it doesn't interfere later on (during the fabrication, or the PCB layout stage). Oh and also, I know that C13 is a really bad thing, so I do plan on removing it.

I have attached an image of my schematic. Thanks!!!


r/PrintedCircuitBoard • • 3d ago

Could use some advice on how to manage sub-PCBs

4 Upvotes

Hello!

start of unnecessary context
I bought a cheap chicken incubator off Vevor a while back. It's mostly fine, but I thought the fan was too loud. I measured it as a 12v fan, and it was a standard computer fan size. So I ordered a Noctua fan to run super quiet. It did run quiet, but for some reason, also threw off the temperature readings of the whole thing. It was constantly way overshooting the heat. I'm a software developer, and figured if I could program an ESP-32 or something to control all the electronics instead of their onboard computer, I could manage it in a way that I wanted to AND get my silent fan working with it with the added bonus of adding it to Home Assistant.
end unnecessary context

The project needs some MOSFETs, transistors, resistors, etc. so I figured I'd try making my own PCB. It's my second time doing that. But one of the requirements this time is a buck converter. I've got a Waveshare 29035 to step down from 12v to 5. The output pins are the standard 2.54mm spacing. But the input pins are 4 pins, spaced 3.5mm apart for a 4-pin screw terminal. I'm not really sure how to deal with that in terms of the final PCB design.

The board needs 12v coming in, both to go to the buck converter, but also to the fan and heater. How do I design my PCB to accommodate this buck converter? The way I see it, I have a few options.

  1. The traces on the buck converter do carry through to the bottom and the bottom is flat, so I technically could surface mount the whole thing, but I don't have any of the solder paste or knowhow to do masking or a way to heat it evenly.
  2. I could keep the entire thing separate - screw terminal soldered to the 12v PCB line goes out to the buck converter's input, then jumper cables from the output of the buck converter to some sort of female connector on soldered to the 5v PCB line.
  3. I could add male header pins just to the outputs and have the female pins soldered to the PCB, the same way I would mount my microcontroller. The buck converter would hang over empty air, supported by the header pins, and just jump from the 12v output of the PCB to the inputs of the buck converter.
  4. I could add through holes to the PCB in the same pattern to the buck converter, and solder individual pins through the holes - essentially the same as option 1, but using pins instead of solder paste.

Do people have other ideas? Thanks.


r/PrintedCircuitBoard • • 3d ago

[Review Request] Daisy Seed 3 based groovebox mainboard

Thumbnail
gallery
3 Upvotes

Hello everyone,

Looking for any tips and insights for my first PCB.

It's a main audio/IO board for a Daisy Seed based groovebox. It has:

  • audio in
  • audio out
  • midi in/out/thru
  • sd card via SDMMC
  • usb power and data
  • on/off via TPS22810DBVR load switch

I've used most of the audio/midi/power schematics from the Daisy Seed Desktop Dev kit. My own additions are the on/off switch and 5V/3V3 for UI board.

My main concern is the power section layout and general PCB layout concepts.

Thank you, appreciate it in advance


r/PrintedCircuitBoard • • 3d ago

[Review Request] STM32 Based Mini Flight Computer

Thumbnail
gallery
17 Upvotes

Hello everyone,

I've designed a 48x53mm board featuring an STM32U375CGT6Q, BMP581 Barometer, BMI323 IMU, a USB-C for DFU programming (added an SWD header just in case), terminal block for a battery and 2 terminal blocks for drogue/main parachutes.

The stackup I used for this board was SIG/GND/GND/SIG with power routed on top and bottom layers.

I would appreciate if you could review my design and point any obvious mistake before I manufacture this board.


r/PrintedCircuitBoard • • 3d ago

Qualcomm IPQ4018 Footprint

2 Upvotes

Hello,

I need a template for a Qualcomm IPQ4018. Unfortunately, I can't find any official data.

Can someone help me? I just need the footprint.


r/PrintedCircuitBoard • • 3d ago

STM32L4 flight controller for TVC model rocket

Thumbnail
gallery
8 Upvotes

Hello all,

Looking for preliminary feedback on my 98mm x 60mm flight controller board for a thrust controlled model rocket. Second-ever board design, first of this complexity. Stack-up is SIG -> GND -> GND - SIG.

It will gather IMU and barometer data, drive two servos, light a pyro charge for parachute ejection, and log data to flash. USB-C only functions as data/DFU, NOT as a power supply.

I have the microcontroller, IMU, barometer, and gimbal mount with servos breadboarded and validated. Everything else is new design and untested.

Feedback I'd especially like is...

  • Power path: reverse-polarity FET, arm switch, bulk caps, and the routing of the main power trace.
  • Pyro channel functionality and the continuity sense circuit.
  • Anything else glaringly obvious.

Thank you, I appreciate your time.


r/PrintedCircuitBoard • • 4d ago

[Review Request] ADF4351 Synthesizer Board (Student Project)

Thumbnail
gallery
4 Upvotes

Hello guys,
This is actually my first serious PCB design project. It’s a student project based on Analog Devices' ADF4351 synthesizer IC. The target frequency is 2.2 to 2.7 GHz with a 5 MHz frequency step. As shown in the uploaded images, I used two USB 2.0 Type-B connectors for both data and power inputs, along with two 0-ohm resistors in case I decide to use only one of them. The upper section is for the synthesizer, and the lower section is for the microcontroller. The MCU I used is an STM32F103C8T6 with an 8 MHz crystal. I also included two pin headers: one for the ST-Link dongle connection and the other for boot mode. Additionally, I added a CH340N for USB-to-UART. I'm not sure if this was strictly necessary, but someone with a lot of microcontroller experience told me it can make programming and debugging easier. I have three regulators: one for the ADF4351 power pins, another for the ADF4351 VCO cores and RF outputs (since they're open-collector), and a third for the digital section. The SMA connector on the right is for an external reference input with a 0-ohm resistor in front of it, though I also included an onboard local oscillator. The attenuator is a digital step attenuator, and the amplifier is a 5V-fed GVA-84+ and the RF tracks are GCPW.
Also, making the PCB 2-layer was something my professor asked me to do because of budget constraints.
This is my first PCB, and any feedback would be greatly appreciated!


r/PrintedCircuitBoard • • 4d ago

[Review Request] Ergo split keyboard with XIAO nRF52840

Thumbnail
gallery
20 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 MOSFET-based switch so that I can run the TPS61040 boost converter either from the battery or directly from VBUS.

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 • • 4d ago

[Review Request] ESP32-C3 Wireless Servo controller, LiPo + USB-C charging

Thumbnail
gallery
3 Upvotes

Hey everyone,

Beginner looking for review for my ESP32-C3 Wireless Servo controller schematics and PCB. This is the receiver half of a wireless servo system. When a button is pressed on the sender remote, it sends a message to this board, and the ESP32 drives the servo.

I’m prototyping first, so the remote is just a breadboard setup for now, and I want to verify this board works before starting on the remote design.

Files:

Details about the board:

  • Input: LiPo 3.7V (4.2V max) or USB-C 5V
  • Connectors:

    • 3-Pin header for Servo
    • JST-PH for LiPo battery
    • USB-C for charging/flashing MCU
  • Board: 50.00x40.26mm
  • Stackup: 4-layer (Signal | GND | Power | Signal)
  • Fab: JLCPCB
  • Layout details:

    • Trace width:

      • 0.6 - 1mm for power / ground
      • 0.4mm for signal
      • 0.284mm 90Ω for USB differential pair
      • Ground pour where applicable
    • Via:

      • 0.62mm diameter
      • 0.31mm drill diameter

Major parts:

  1. U1: SY8089AAAC - Step down regulator to MCU 3.3V input (Datasheet)
  2. U2: TP4054 - LiPo charger IC (100mA charge current) (EN Datasheet)
  3. U3: TPS61023 - 5V boost converter for servo (Disabled by default, controlled by MCU) (Datasheet)
  4. U4: ESP32-C3-Mini-1-N4 - MCU for wireless/enable boost/servo movement (Datasheet)

Other parts:

  • Battery: LiPo 3.7V (4.2V max) 1000mAh protected
  • Servo: TowerPro MG90S Micro Servo 3 Pin Female

    • Min. 4V/0.2A, Avg. 5V/0.3A, Peak 6V/0.5A
    • Can only be powered by 5V boost (cannot be powered by USB)

I would like feedback on:

  1. Will this work? or is there major mistake or something I'm missing?
  2. Any mistakes in schematics? Is there things I misunderstood/mistake?
  3. Is there layout problem? Especially around USB differential pair pathing?
  4. Anything I'm missing for JLCPCB assembly?

Part I'm unsure of:

  • Is 4 layer stackup design necessary? - I prefer to have ground plane since it's easy for me wrap my head around, but not having second layer for signal makes it hard to route. I'm also not sure if USB signal works over 2 layer.
  • Is there something like simulation or test run for PCB? - I did some basic test run with breadboard before starting the design but since the design changed so much, I'm not sure if my design still holds. ERC and DRC did pass though.

This is my first design coming from software engineer background. I tried my best to avoid beginner pitfalls so hopefully I didn't make major mistakes before ordering. No AI is used in design or this post, only for basic schematic/pcb checks, dumb question and grammatical error.


r/PrintedCircuitBoard • • 4d ago

[Review Request] ADF4351 Synthesizer Board (Student Project)

Thumbnail
gallery
2 Upvotes

Hello guys,
This is actually my first serious PCB design project. It’s a student project based on Analog Devices' ADF4351 synthesizer IC. The target frequency is 2.2 to 2.7 GHz with a 5 MHz frequency step. As shown in the uploaded images, I used two USB 2.0 Type-B connectors for both data and power inputs, along with two 0-ohm resistors in case I decide to use only one of them. The upper section is for the synthesizer, and the lower section is for the microcontroller. The MCU I used is an STM32F103C8T6 with an 8 MHz crystal. I also included two pin headers: one for the ST-Link dongle connection and the other for boot mode. Additionally, I added a CH340N for USB-to-UART. I'm not sure if this was strictly necessary, but someone with a lot of microcontroller experience told me it can make programming and debugging easier. I have three regulators: one for the ADF4351 power pins, another for the ADF4351 VCO cores and RF outputs (since they're open-collector), and a third for the digital section. The SMA connector on the right is for an external reference input with a 0-ohm resistor in front of it, though I also included an onboard local oscillator. The attenuator is a digital step attenuator, and the amplifier is a 5V-fed GVA-84+ and the RF tracks are GCPW.
This is my first PCB, and any feedback would be greatly appreciated!


r/PrintedCircuitBoard • • 5d ago

40W LM3886 Amplifier progres

Thumbnail
gallery
39 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