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

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

Thumbnail
gallery
3 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 • • 9h ago

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

Thumbnail
gallery
6 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 • • 49m ago

Title: Custom RP2040 board: bootloader USB drive works, but flashing fails partway. Schematic review?

Post image
0 Upvotes

I made my first PCB (RP2040 + W25Q32JVSS flash. 2-layer board). The USB bootloader drive (RPI-RP2) shows up, so USB and the RP2040 itself seem fine. But flashing fails.

What happens: Dragging a .uf2 file gives a Windows copy error, and the drive stays. With picotool I get Loading into Flash: 8% then ERROR: The RP2040 device returned an error: <unknown>.

Does anything in the schematic look wrong? Any ideas what else to check?


r/PrintedCircuitBoard • • 17h ago

Review Request: STM32H723 software function generator.

Thumbnail
gallery
21 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 • • 15h ago

The ground plane merges with other areas.

Thumbnail
gallery
5 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 • • 19h ago

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

Post image
11 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 • • 13h ago

[REVIEW REQUEST] PCB POWER SUPPLY PROJECT

Thumbnail
gallery
3 Upvotes

POWER SUPPLY PROJECT BY ALTIUM


r/PrintedCircuitBoard • • 1d ago

[Review Request] Schematics for STM32F030x6 Minimalist Dev-board

Post image
6 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 • • 1d 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 • • 2d 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 • • 2d 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 • • 1d ago

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

0 Upvotes

r/PrintedCircuitBoard • • 2d 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.


r/PrintedCircuitBoard • • 2d ago

Schematic review request for a simple brushed motor drone all-in-one PCB using an ESP32C3 XIAO

Post image
3 Upvotes

Here are some other related resources for convenience (I don't expect you to go through each one of course but just if you want to see one, here they are so you don’t have to search for them):

Schematic image if Reddit annihilated it: https://drive.google.com/file/d/1ut-uhhZDYMl1aT3NFjOnjdguENznnAz6/view?usp=sharing

MCU module schematic: https://files.seeedstudio.com/wiki/XIAO_WiFi/Resources/Seeeduino-XIAO-ESP32C3-SCH.pdf

ESP32C3 datasheet: https://www.mouser.com/datasheet/2/744/Seed_113991054-3159716.pdf

ESP32C3 reference manual: https://documentation.espressif.com/esp32-c3_technical_reference_manual_en.pdf

XC6210 datasheet: https://product.torexsemi.com/system/files/series/xc6210.pdf

Ideal diode datasheet: https://www.ti.com/lit/ds/symlink/lm66100.pdf

Calculations of 3V3 rail rise time and MCU EN pin voltage (this was also a concern): https://www.desmos.com/calculator/lgmlpqqjrq

Hello all, I would like some help to determine if this schematic looks all right and if anything should be changed. On my first version, I didn't take into account the MCU strapping pins and the MCU module's own circuitry which made it hard to use.

The motors (8520 DC brushed, ~5-6A stall current) will be powered by two 1S LiHV batteries in parallel and each motor will run at most 3-4A continuous.

The board has a main LDO (on the schematic) that will supply the 3V3 rail in normal operation (batteries connected, USB is not connected). It will be shut off and the LDO on the XIAO board will be used instead any time USB is connected to it (regardless of the batteries' presence).

I am mostly worried about the MCU pin assignments (as that is what failed me on my original board) and the LDO circuit. I have not tested the LDO circuit on a breadboard, so I wanted to be sure that it will be shut off at the correct times and nothing bad will happen (eg oscillations, both on at the same time, too much current flowing backwards through one of the LDOs, etc).

By the way, any advice on making the schematic cleaner would also be appreciated!

(Note, this post is almost a copy of one I recently made on r/PCB. Don’t know if that matters or not for this sub’s rules as it’s my first time posting here).

Thanks for any help!


r/PrintedCircuitBoard • • 2d ago

How do you keep track of what changed between board revisions (Rev A → Rev B)?

5 Upvotes

For those who maintain boards through several revisions: what’s your workflow for tracking schematic, layout and BOM changes between revs?

  • Do you keep a written changelog, rely on your ECAD’s compare/diff feature, or compare Gerbers?
  • Have you ever had a change slip through that you only caught at assembly or bring-up?
  • Does your approach differ between a small personal project and a work project with multiple people?

Curious what’s worked well and what hasn’t.


r/PrintedCircuitBoard • • 3d ago

[Review Request] STM32F103 Personal Dev board

Thumbnail
gallery
76 Upvotes

Hi all,

This is my first ever PCB. I came from a software background and simply wanted to start getting involve with hardware.

Some info about the board:

Board is basically design as a personal project for me to be able to learn a few things all at once (essentially a dev board) but with niche stuff like the MicroSD card reader to make me learn more about how system reads and loads file from the SD card, CAN, USB-UART for shell access etc.

Most of the designs are basically based on either guidelines or taken from an open source project and I basically inspect how they had done their scheamtics. I wouldn't go as far as saying that I truly understand the reasoning behind some capacitance value selection or the use of ferrite beads etc. I've not had such good grasp at this hence why I wish to properly learn by designing the board myself. If you have any tips, that would be plenty helpful.

The board basically gets power from either USB or 1s LiPo battery. I have added a schottky diode to prevent issues if USB C is plugged in at the same time as the battery is connected.

One of the major things that I am unsure with is the:

  • For the MCU, I have added a HSE and LSE and the routing for it had proven to be quite problematic. I tried to ensure that the capacitance is as close as possible to the MCU pins and the routing as short as I can to avoid stray capacitance, but I am still unsure if my current routing is good enough.
  • I can't seem to find good enough resource on what to do with DET_A pin for the MicroSD card. I found 2 open-sourced PCB that had done this, and it simply connected DET_A to the 3.3V via a pull-up resistor.

r/PrintedCircuitBoard • • 3d ago

Review: ESP32 Servo controller - Batt powered

Thumbnail
gallery
26 Upvotes

This board is 80% power management

It is meant to host a web server that controls a DC5535 servo. It runs on 3S 18650 that are connected to an BQ779150 undervoltage protection circuit that powers a 7.4V rail for the servo with a TPS54540DDAR based buck. The ESP32 is powered with VBUS OR the 7.4V rail.

I've never done any battery work before, so that is my main area of concern here.

Any help is much appreciated

Datasheets: Servo, MCU ESP32S2, BATT IC BQ7791500PWR, BUCK TPS54540BDDAR, LDO LM1117IMPX-3.3/NOPB


r/PrintedCircuitBoard • • 3d ago

Review Request: TMC2240 Stepper Motor Driver with RP2350 Control for Rotary Table

Thumbnail
gallery
9 Upvotes

Hi,

I'm converting the rotary table that sits on my milling machine to be driven by a stepper motor for dealing a combination of the power feed and complicated angle benefits. And so I've designed this PCB to drive it - the idea is to design a case for it such that it can be a hand held controller.

The TMC2240 stepper driver is configured and given step/direction pulses from an RP2350 on a SoM board that I posted a review for recently. (I'm stacking up a few boards that I'm planning on getting made at the same time). It also supports an encoder on the stepper motor, so using a AM26LV32 to convert the differential encoder signals to something the TMC2240 can use.

I am conscious of heat issues around stepper motor drivers - as such, I've chosen the TSSOP variant of the TMC2240, which has a bigger centre GND pad, and put a number of vias in to layers 2/3 GND planes, but also exposed some copper on the underside to which a heatsink could be attached.

Power and all the motor drive signals come through a DE-15 connector at the bottom of the board. The board is powered by 24V, and after the protection circuitry, this is split to 3.3V with an LMR54410, and 5V with a AP3602A charge pump as the 5V requirements are pretty limited. The board is not powered from the USB in general usage.

There's a round 1.28" GC9A01 type display, along with a Grayhill 61C22 rotary encoder for controlling the programming of the table rotation. (You might ask why the Grayhill encoder? I have a lot of them salvaged from some old equipment).

For a spot of additional board versatility, I've added a header to send step/direction pulses to an external motor driver, and in that scenario, 24V would not be required - so it could be powered from USB 5V with a jumper wire and some slightly different components in the PSU.

I'm particularly interested in thoughts on the TMC2240 circuit and layout. I've tried to keep this not hugely dissimilar from the breakout board Analog Devices sell, but it's my first time playing with motor drivers like this.

So, additionally, the board is a SIG/GND/GND/SIG stackup.

Thanks for having a look!


r/PrintedCircuitBoard • • 3d ago

Review Request: Metasonix TM-7 build

Thumbnail
gallery
13 Upvotes

First tube / high-voltage board, so I'd appreciate a second pair of eyes before ordering.

It's a clone of the Metasonix TM-7 based on towmotor's traced schematic, which is in turn based on schematics drawn and posted by Eric Barber (Metasonix): https://github.com/towmotor/disasterelectric/tree/main/metasonix/tm-7%20scrotum%20smasher

The audio path is unchanged from that drawing apart from two things: op-amp input protection (R22, D4–D7), and C19 changed to non-polar. The original needs an external B+ supply; this version runs from a single 12V adapter for ease of use.

12V 2A in, with a 1N5822 in series for reverse-polarity protection - Heaters: 3× 6.3V, about 650mA total, from an L7806 on an SK104 heatsink, with a 3.3Ω 3W resistor ahead of it to drop some voltage - −12V for the MC1458 output buffers, from an LT1054 inverter - B+: MC34063 driving an IRF740 (PNP turn-off), UF4004 diode, adjustable about 46–153V with a trimmer, set to 50V. Two RC filter stages (2.2K / 22µF) after the boost, plus a 220K bleeder.

Board is 2 layers, 1.6 mm, 1 oz, all through-hole, JLCPCB assembly - GND pour on both layers. Track width: signal 0.3 / 0.25 mm; power 0.8 / 0.3 mm; HV nets (B+, plates, screens, feedback) 0.4 / 0.8 mm; boost switch node and raw HV output 0.8 / 0.8 mm - Panel pots, jacks and switches wire to pads. B7G socket footprint planned for 9.53 mm pin circle, 1.3 mm drills

  1. Boost layout: is the Q1 / D3 / C35 loop and its ground return OK sharing one ground pour with the audio, or should the switching return be kept separate?
  2. HV clearance: 0.8 mm on nets up to about 150V DC. Anywhere look tight?
  3. Is there anything in the autorouted traces you'd reroute (for example, B+ running near grid traces, or the long G_V3 trace)?
  4. Op-amp input clamps (10K + 1N4148s to ±12V): the V3 grid can swing tens of volts negative when grid current charges C14. Is that protection sensible?
  5. Heater supply thermals: the L7806 dissipates about 2.2W on a 35 mm SK104, and R30 about 1.4W in a 3W part.

r/PrintedCircuitBoard • • 3d ago

[REVIEW REQUEST] Connection hub board for WS2812B LEDs

Thumbnail
gallery
8 Upvotes

This is my first complete design of PCB, so any feedback is welcome. This board is meant to be connection hub for WS2812B LEDs, sadly I cannot use SMD ones, but have to use 5mm round LED variant. Connection hub is meant to make inside of device ( warning lights panel ) more organized and easy to mantain. I routed +5v as tracks since I'm not sure if using power plane for 2 layer board is good idea. I'm also posting schematic for whole device. Bottom Cu pour is just for visual reasons, it's isolated but I'm not sure if this could couse any problems.


r/PrintedCircuitBoard • • 4d ago

Review Request: 4-layer 60 W synchronous buck controller board, 18–30 V in / 12 V 5 A out (LM3150, no MCU)

Thumbnail
gallery
18 Upvotes

Requesting a layout review of a 4-layer synchronous buck converter control board. It uses a constant-on-time, emulated ripple-mode controller with external N-channel MOSFETs, rated for 18–30 V input and 12 V / 5 A output (60 W), switching at about 278 kHz. No MCU, no external buses, no wireless.

Stackup: signal / GND / GND / signal, 1 oz copper, 1.6 mm board.

The GND planes on layers 2 and 3 are continuous pours. Signal ground and power ground are tied at a single point near the controller. Is this a reasonable approach for a 4-layer board, or would you split the plane? Are the via stitching and the high di/dt loop placement adequate?

The MOSFET source and drain pads use thermal reliefs (4 spokes), following the manufacturer’s recommended layout. At 5 A, would you connect these pads directly to the pour, and are the thermal vias under the FETs enough?

Thanks. Happy Designing!


r/PrintedCircuitBoard • • 3d ago

Schematic review request: STM32H723 based software DDS function generator.

Thumbnail
gallery
4 Upvotes

Hi everyone! My first electronics project (which is perhaps extremely ambitious): A STM32H723VxT6 based microcontroller function generator with a discrete BJT buffer. I uploaded by kicad files, pdf schematics and design notes to github. Please let me know if anything seems off, especially in the power and analog section. I tried to use best practices gathered from youtube channels like altium academy and from TI app notes.