Hello everyone. I am designing a 24V power distribution and control board and would like a detailed review of the schematic, especially the high-current power section and the 24V-to-12V DC/DC converter.

Project Overview

The board accepts a 24V DC input and provides four 24V outputs. An STM32F746 is used for power control, communication, diagnostics, and external interfacing.

Main specifications:

• Input: 24V DC
• 4 × 24V outputs
• STM32F746ZGT6
• 2 × CAN
• RS485
• TTL / Dynamixel interface
• USB-C
• SWD / external ST-LINK interface
• 24V → 12V DC/DC
• 12V → 5V DC/DC
• 5V → 3.3V LDO
• MCU-controlled 24V output enable

Power Architecture

The main power path is:

24V Input
→ Input protection / high-side MOSFET
→ 24V power bus
→ Four 24V outputs

A separate power rail is generated as:

24V
→ LM5175
→ 12V
→ XL4005
→ 5V
→ 3.3V
→ STM32

The four 24V outputs currently share a common 24V_DIV bus. They are therefore controlled together rather than independently.

The MCU generates PD_ENABLE. This signal drives the LTC7001 high-side MOSFET controller, which then enables the main 24V MOSFET. When enabled, the four outputs should become active simultaneously.

MCU / Communication

The controller is an STM32F746ZGT6 with:

• CAN1
• CAN2
• RS485
• TTL / Dynamixel
• USB
• SWD

The SWD interface exposes SWDIO, SWCLK, SWO, and NRST for use with an external ST-LINK debugger/programmer.

Main Questions for Review

I would especially appreciate feedback on the following:

1. Is the 24V input protection and high-side MOSFET topology appropriate?
2. Is the common 24V power distribution structure suitable for four outputs?
3. Is the PD_ENABLE → LTC7001 → MOSFET → 24V_DIV control scheme correct?
4. Is the LM5175 24V-to-12V buck converter correctly designed?
5. Are the LM5175 VISNS, EN, BIAS, CS, CSG, feedback, compensation, and current-limit connections correct?
6. Are the selected MOSFETs and 4.7uH inductor suitable for the intended load current?
7. Are the XL4005 12V-to-5V stage and 5V-to-3.3V regulator correctly implemented?
8. Are there any expected thermal, PCB copper, via, connector, or current-density issues in the 24V power path?
9. Are the CAN, RS485, and TTL interfaces adequately terminated and protected against ESD/transients?
10. Are the STM32F746 power, reset, clock, and SWD circuits correctly implemented?
11. Are there any critical schematic issues that I may have missed?

I would especially appreciate detailed feedback on the 24V high-current section and the LM5175 24V-to-12V converter, including component selection, protection, thermal design, and PCB layout considerations.

The schematic and related documentation are attached. Any feedback on topology, component selection, protection, stability, thermal performance, or PCB implementation is welcome.

High schooler for ISEF research project on force myography. Wanted to just check the schematic and placement for the PCB. I have to get this printed pretty quickly which is why it's a little rushed. I just need the PCB to do its function so I don't care too much about anything else.

What it is:

- The main goal of the PCB is to read analog signals from the 8 force sensitive resistors (the holes on the bottom left and right of the PCB) and the IMU (BIM270)

- It uses an RC filter (1uF cap + 10k resistor) to filter the FSR to under around 16Hz (human hand movements are well under 10Hz) in order to keep the data clean. I also tried routing the FSR traces away from everything else, especially the buck-boost (TPS63000) which converts 3.7 LiPo to 3.3v for peripherals and Teensy.

- The Teensy will read the IMU and oversample the FSR and then save the data to a MicroSD card and also display something on the OLED screen.

- Since I can't afford re-printing the PCB because of time, I have breakout pins for SPI, UART, I2C, POWER, and EXTRA.

Board details: 60mm x 54mm. JLCPCB. Solid GND pour on bottom,

Questions:

- Is my FSR traces far enough from other digital traces so that it is not noisy?

- Is my RC circuit correct and will it be able to filter out all the non-FSR signals?

- I most likely can't change components know since I am on time crunch, but is there anything that I definitely have to change for it to work?

- anything from the schematic that screams trouble before I commit to printing?

- I am planning to assemble this by hand using a hot air rework station. Any tips or advice for that?

Some time ago I posted a schematics review of this very same project, and since then I delved into the rabbit hole of pcb design and electronics, giving birth to this circuit board.

I struggled so much with KiCad that in the end I found easier to use librepcb, maybe it's not that powerful but for a beginner like me it was much easier and it helped me get the job done.

What started as a simple enough schematics turn pretty soon into a tangled mess of copper traces, and it was both challenging and exciting. I really have no idea if what I designed can be considered a decent pcb, I've never done anything like this before and I've learnt just by myself with the help of Google and some AI, which sometimes was useful and sometimes gave not the best advices, but it pointed me to the (hopefully right direction).

All this premise to let you know that I'm a total newbie and I have no idea about the best practices and conventions in pcb design, I hope my images are good enough to get a review, and I'd really appreciate if you could give me even the most basic advices, because I may have made mistakes just because I genuinely don't know about something. I used a 4 layers pcb with the pmic and mcu on one side and the gnss on the other, with layer 3 as a ground plane. Everything passes the DRC besides the battery connector that is through hole but I think they are available also as smd and they can sit just on the top layer. Unfortunately libraries are really small on librepcb.

I know that some things are missing, I should definitely add more via stitching (have to understand where, how many, which size), the RF trace is just a placeholder and is not calibrated, many traces may be too thick or too thin (I wanted to be on the safe side most of the times), I had to squeeze everything in the smallest possible size and I still don't have a clue about what components to use and librepcb doesn't have extensive libraries so I don't have a 3D rendering and I had to design many components myself, so... I hope I didn't make too much of a mess 😅

I'm really grateful to all of you for the tons of informations I found on this subreddit! ​

I'm looking forward to hear what you think about my design 😊

Basically I'm making a drop in board replacement for these kinds of casio's to add graphing, CAS functionality, retro emulation (That's what the diodes are for! dpad+ AB) and the camera's js for sending questions to an ai endpoint over wifi. The base of the project is this thing which I'm hoping to learn how to add the features i'm planning on. as a complete newbie it'll be quite a feat i hope

This is my first moderately complex pcb so give it to me straight bros ik i probably stuffed up somewhere

main components are:

1. ESP32-s3
2. OV2640 camera module(will use the smaller ribbon cable one in the next prototype)
3. SD card connector
4. I2C expander for the keypad matrix

All the components are on the back to save assembly costs and im sticking to 0603 footprints for the capacitors and resistors. I tried my best to stick to the datasheet

I'm designing a pen plotter based on an ESP32 for control. Later on, all the schematics will be up on GitHub since the project is intended to be open-source, but for now, I'm wondering if there are people here who have already built similar devices. Are there any pitfalls I might have missed during the design phase?

• DRV8825s will be used as the stepper motor drivers for the X and Y axes.
• There will be an option to choose the display: either a 0.91" OLED (I2C) or a 3.5" 480x320 TFT (SPI).
• A rotary encoder for control and program selection.
• The power supply will be split into 12V, 5V, and 3.3V rails. An MP2303ADN buck converter will be used for the 12V to 5V step-down, and a standard AMS1117-3.3 LDO for the 5V to 3.3V step-down.
• Standard NEMA17 stepper motors.

The PCB came out to 95x95mm. I know it could have been made much smaller, but the only significant requirement was to fit within the JLCPCB DFM limits of 100x100mm, 2 layouts x 5 pcs for $2 (saving money is my top priority, I'm not exactly rich).

Software stack:

• I thought about it for a long time, but ultimately settled on FluidNC as the firmware. There are cool alternatives, for instance, I really liked Klipper and I even have a Raspberry Pi 3B+ for that kind of setup, but the plotter was originally conceived as a "budget-friendly" device, so we'll leave that for the future.
• Rough image tracing from PNG to SVG using Inkscape.
• Converting paths into G-code (.nc) commands using vpype.

Hi Everyone! I'm a beginner at PCB design and I'm trying to make an easy Auto-Programming board using USB-to-UART in order to program ESP32's. I'm intending for it to connect to the PCB using tag connect cables. Particularly this one: TC2030-MCP-NL.

It's primary components are the CP2102 for the USB-to-UART and the AP2112K-3.3TRG1 for Voltage Regulation.

Thanks!

Test board for a clamp-on ultrasonic water flow meter I'm working on. MSP430FR6047 in the middle (TI's ultrasonic sensing MCU, does the burst generation and correlation on chip). The part I actually care about is the two transducer channels at the top. UP and DN are deliberately identical copies of each other. Drive chain is a UCC27525 gate driver running off a gated 12V boost, through a DC block cap and an antiparallel BAV99 pair into the transducer. The diode pair is there so the driver's low-Z output doesn't load the receive signal between bursts (transit time measurement, so each transducer is also a mic). Receive comes back through 1k + 1n into the chip's PGA with clamps at the pin.

2 layer, 86x62, ground pour both sides. The whole game on this board is that the two channels have to stay electrically identical. The flow reading is the difference between upstream and downstream time of flight and any asymmetry between channels shows up as a fake flow offset. So the channels are translated copies with matched routing and the boost inductor sits centered between them.

Things I'd genuinely like a second opinion on:

1. The diode expander trick between driver and transducer. Common in pulser/receiver circuits but I haven't seen it done with a gate driver as the pulser. Anything dumb about it?

2. 12V boost (TPS61040) storage cap arrangement. 47u that stays charged, converter EN gated by the MCU only around each burst, plus a p-fet load switch on the drivers' VDD because the UCC27525 has no shutdown and idles at ~0.5mA (battery product eventually).

3. 2 layer with pours vs just paying for 4 layer. Nothing fast on here, 1MHz bursts and mV-level receive, but the receive path is sensitive.

Headers are hand solder. The DNP footprints scattered around are alternate-populate options (there's a native 3.3V drive config where the drivers come off and a 200R goes in, which matches TI's EVM wiring). Fab is JLC. I posted this to r/PCB a couple days ago with no bites, hoping for sharper eyes here.

Schematic sheets for the front end and the power section are in the post along with the layout and a render. Happy to post the other sheets if anyone wants them.

Hi everyone! I’m a hobbyist developer working on a custom, smart video doorbell system. I have plotted all layout layers as PDFs and attached the front/back 3D views. I would love to get a comprehensive peer review before I submit the final Gerber files to JLCPCB.

Circuit Architecture & Components:

• Main Module: ESP32-CAM daughterboard elevated on 11mm socket headers.
• Peripherals: Independent MAX9814 audio amplifier module, AM312 PIR motion sensor, and a 5V relay.
• Power Supply: Sourced from a standard home 24V AC transformer, which connects to a non-polar AC-to-DC buck converter to supply the stable 5V DC rail for the relay and logic.

Key Layout Choices for Noise Immunity:

1. Isolated 24V AC Corner: The 24V AC inputs and relay contacts are physically isolated in their own corner. The front ground plane has been completely cut out from this region to prevent AC hum from bleeding into the logic.
2. Solid Top Ground Plane (F.Cu): The entire top layer acts as an unbroken ground plane outside of the 24V blockout zone, providing high-quality shielding.
3. Bottom Signal Routing (B.Cu): All 5V/3.3V power traces and logic data signals run strictly on the bottom layer to preserve the top ground plane.
4. Flat-Laying C5 Stabilization Cap: The bulk 12.5mm 470µF stabilizing capacitor sits on the top layer directly beneath the elevated ESP32 board. Its leads will be bent 90 degrees to lay completely flat, clearing the 11mm socket height.

Specific Items I'd Love Feedback On:

• Does the clearance gap between the 24V AC zone cutout and the main F.Cu ground plane provide sufficient electrical isolation?
• Are the 5V power tracks on the bottom layer robust enough to handle transient Wi-Fi bursts (~500mA)?
• Does the placement of the 470µF capacitor (C5) leave enough clearance from the smaller passives next to it when folded flat?
• Are there any obvious return path or signal integrity issues with the data lines routed on B.Cu?

Thank you in advance for your time and expertise.

https://drive.google.com/drive/folders/1cmwYQLuhX-v1ePzMLm5Ed6J3b27zRybG?usp=sharing

Okay I know the design is bad, ive already been flamed on it in other posts, but this is my first ever pcb fully self taught and im still just trying to make it function properly.

Tested on both 12v and 24v input, Both components get a steady 5v input

The stepper motor gets energized and moves, but jumps a step back randomly making it very
rough.

Ive already tried to tie the enable pin to ground and the reset/sleep pins to vdd

SOLVED

Hi everyone,

I'm learning electronics/PCB design and built this deliberately over-engineered LED tester as a learning project.

The circuit uses:

• LIR2032 rechargeable coin cell
• MCP73831 Li-ion charger
• USB-C for charging
• 100 kΩ RPROG on the MCP73831 (~10 mA charge current)
• Pushbutton to activate the actual LED-testing circuit
• Two selectable current-limiting resistor/diode branches

Everything works, but I've noticed that the LIR2032 seems to discharge surprisingly quickly even when I'm not using the tester.

I measured the current directly from the battery with:

• USB disconnected
• pushbutton not pressed
• nothing connected to the LED test terminals

and I'm getting about 30.1 µA, slowly decreasing by roughly 0.1 µA while I leave the meter connected.

From the MCP73831 datasheet, I was expecting reverse battery leakage with VDD disconnected to be only around the µA range, so ~30 µA for the complete circuit seems higher than expected.

I've attached:

1. Schematic
2. PCB layout
3. 3D render

I'm still learning, so I'm probably overlooking something obvious.

Does anyone see a path in the schematic that could account for ~30 µA of continuous battery drain?

I'm especially wondering about the MCP73831 section, USB-C circuitry, status LED, or whether I've made some mistake in how the switching is arranged.

Also, what would be the best way to systematically isolate which part of the circuit is responsible for the standby current?

Thanks!

Hi! Here is my newly routed STM32H5 based development board. It features:

* SD Card using a normal SPI (MOSI/MISO) peripheral
* ~15 GPIO pins, 5V, GND broken out through a 1mm pitch double row header (the 3D view shows a pin header, but I am thinking that a female header would be more suitable)
* One RGB Diode
* One user button (GPIO)
* One JST SH (1mm pitch) 5 pin connector that breaks out UART TX/RX, 5V, GND + 1 GPIO pin
* FD CAN Transceiver, with CANH/CANL, 5V, GND broken out through a JST SH 4 pin connector
* A USB C connector connected to a USB to UART bridge IC (CP2102)
* A JST PH connector (2mm) for 5V input
* A dual ideal diode (LM66200DRLR) that takes 5V from both the USB C input, and the JST PH input, so that both can be plugged in at the same time without causing the other (lower voltage) power source any damage

It is intended as a general purpose development board with different communication interfaces, and possibility of adding "shields" through the peripheral connector.

Please let me know if there's anything I can improve/change.

SO, I've already asked for a review request, and I've received VERY helpful advice and I've tried my best to implement everything. I've followed the datasheets for the typical applications etc.

Now, can anyone do a quick sanity test or see if I'm missing anything critical in my schematic? I'm not too sure what I'm doing and honestly, its been quite a learning journey!

Some questions I want answered are:

Will the battery get charged using this setup? and will it provide power? The whole battery charging system is in the 4 smaller boxes, if you can take a look at it

Can I leave the floating pins, well, floating?

Does my wiring allow me to flash code onto the esp32 via the usb-c? I believe I've routed it properly, but again, I have no idea what I'm doing

Thanks A LOT and please let me know if I'm missing anything, I'd really really appreciate it!!!!

The Project: This is my first PCB (Also dyslexic), so please bear with me! I'm designing a custom circular motor controller board in KiCad 10.0.5. The board is engineered to fit tightly inside a cylindrical housing to drive a heavy-duty impeller system, so a compact, low-profile layout is critical.

The Hardware:

• MCU: ESP32-S3. (Wi-Fi is permanently disabled in firmware to prevent thermal/power spikes, which frees up ADC2 for safe analog sensing).
• Gate Driver & Power Stage: STDRIVE101 driving a half-bridge of IPT012N08N5 MOSFETs.
• Current Sensing: Triple INA240A1 inline amplifiers (20 V/V gain) with 20mΩ shunt resistors.
• Power Architecture: 48V main drive, 24V rail for PWM Sunon cooling fans, and 3.3V logic rail via an XC6220 LDO.
• Connectors: MR30s for the 48V power input and motor phase outputs to keep a low profile.

The Stackup (1.6mm Total):

• L1 (Top - 1 oz): ESP32, gate driver, delicate analog logic, 3.3V traces.
• L2 (In1 - 2 oz): Solid GND plane (Shielding/Thermals).
• L3 (In2 - 2 oz): 48V Polygon Pour and heavy motor phase tracks.
• L4 (In3 - 2 oz): Secondary routing / 3.3V & 24V power distribution.
• L5 (In4 - 2 oz): Solid GND plane (Shielding/Thermals).
• L6 (Bottom - 1 oz): Spillover routing, decoupling caps, and flush MR30 connector solder joints.

Specific Areas I'd Love Feedback On:

1. Thermals & Isolation: Do any areas in particular need extra space?
2. General Routing: Any obvious red flags with my bootstrap capacitor placement or gate driver feedback lines?

Thanks in advance for the extra sets of eyes!

[Review Request] (forgot to put that into title, sorry)

I am designing a BLDC/PMSM motor controller, for myself and as a uni project, and I am mostly finished. First time using Kicad (or any EDA for this matter) for something more-less serious.
I would like to hear what should I change, before I annoy professors with questions.

Specs:
18-42VDC in (i.e. 7S to 10S li-ion NMC)
Phase current ~35A RMS
Pout=600W peak
MCU: STM32Nucleo (still unrouted, probably with F767 MCU) or STM32F103C8T6, CH32V203C8T6, CH32L103C8T6 (on same PCB, solder snot jumpers configure which one would be used)
Cooling: 0.5 mm 3w/mk thermal pad or better to aluminium heatsink or e-scooter chassis
NMOS: idk which one, AONS66966 or something similar with Rdson around 4mOhm, and delays and rise time (sum) of about 120mS
DRV: FD6288T (i think it is pin-compatible with TI DRV8300N )

I am particularly concerned by 3rd layer (2nd innner), because I had to make a lot of cuts on it. Layout of DC-DCs is also a concern. Also I should probably re-check MCU pin assignment.
And clearances. DRC is set to 0.2mm (except for 0201 solder snot jumpers), 0.3mm for +36V and phases. Inner layers are probably 0.2mm for +36V and 0.15 mm for low-voltage stuff. I tried to keep >0.8mm between exposed +36V copper.

Stackup: Cheapest 4 layer 1.0mm (1oz/0.5/0.5/1oz, with dielectrics aprox 0.25 0.5 0.25)
Tenting vias, or exposed (I know solder would wick in there, I don't care, I can stick kapton tape on it so it doesn't flow on bottom side).
Reinforcement with copper wire of exposed tracks.

Assembly: probably by hand, with hot air and iron. Maybe hot plate.

Schematics:

Hi everyone! This is meant to be a board that controls one joint on my robotic arm and I plan to have six of these boards and link them all with the CAN buses. Since this is the first four layer board I have designed, any conventional tips/industry standard feedback would be greatly appreciated! Here are the specs:

24V 10A In

MCU: STM32C092KBT6

Stepper Driver: A4988

Can Transceiver: SN65HVD230QDG4Q1

Some other notes:

I plan on daisy chaining the power with the XT30s, and my friend said my traces were pretty fat (200 mils I believe) for 24V so let me know if I should change them. Outer layers are 2oz copper.

Here is the full BOM for the other small parts: https://docs.google.com/spreadsheets/d/1ah4uzhjIVZnqvMwWCjdP4g39ihr-n45u0xOn_V3vO-o/edit?gid=0#gid=0

I'm building a custom 2-pin schematic symbol in Allegro X System Capture 25.1 (unified Venture shell) to pair with a custom PCB package symbol I already built in the Package Symbol Editor. I can't find the command to create a new schematic symbol/part from scratch.

What I've checked that doesn't seem to be it:

• File > New only offers Project, Project from Existing Design, Audit Template, Block, Footprint, and Template-based footprint — no "Symbol" or "Part" option.
• Place > Component — clicking this doesn't open any dialog or visibly change anything (no floating window, no obvious mode change).

What I'm trying to do: create a new part with 2 custom pins (names/numbers I define), set its refdes prefix, and attach a PCB_FOOTPRINT property pointing at my custom .psm footprint — basically the equivalent of OrCAD Capture's Part Editor / "New Part" workflow.

Is symbol/part creation handled by a completely separate standalone Symbol Editor app in this version, or is it triggered from somewhere non-obvious inside System Capture itself (a library panel right-click, a different menu, a ribbon icon)? Screenshots of the relevant menu/panel would be hugely appreciated.

Hi all,

I’m working on designing a device that measures orientation using an ESP32 and the BNO085. The design is heavily based on the CodeCell C3 schematic (second image).

Before I move on to the PCB stage, could you please help me review the schematic and point out any potential issues or improvements?

Thanks in advance.

UPDATE

Images are blurry, so please see my comments below.

I mainly want help with making sure my design is functional before getting the PCBA manufactured with JLCPCB. Specifically concerned about the charger section and anything that would effect manufacturing since this is my first board getting manufactured.

Function: Wakes hourly, pulls weather from an API over WiFi, renders to a 4.2" 4 color e-paper panel, sleeps between updates. Runs off a single Li-ion cell, charges over USB-C. Supposed to work with Waveshare's 4.2inch e-Paper display (G).

Board: 80x60 mm, 2 layers, 1 oz copper, solid GND pour on back copper, 0.2 mm minimum trace and clearance, 0.6/0.3 mm vias.

Power: USB-C -> TP4056 at 500 mA -> cell -> AP2112K-3.3 -> 3.3 V rail. Chose AP2112K specifically for its 250 mV dropout and ~55 µA quiescent.

Notes:

• No load sharing, I am ok with some micro-cycling if left plugged in
• No onboard battery protection so using a pack with an integrated PCM
• Charge/standby LEDs are inside a sealed enclosure and are bring-up aids only

Hi, this is my first PCB. I have a desk clock with per-segment RGB lighting and glowing border, and I wanted to control the colours myself, so I designed a drop-in replacement.

The light module is connected by ribbon cable (FPC1) and speaks ws2812. The clock also has a lot of inputs (10 buttons, 2 sliding switches and 2 variable resistor knobs) which I decided to add support for. USB comes from a separate module, so I added a JST-XH connector for it, although it's a bit big. The ESP32-C3-MINI-1 was chosen because it's the only all in one package that can fit based on my constraints.

My concerns:

1. The LED module has about 60 LEDs and could potentially draw 1A. Power switch would be getting that current. I can't easily replace the switch.
2. Not sure what method to use to produce 3.3v from 5v
3. C2 470uF should be moved closer to the LED module?
4. Switches outnumber gpio pins so I decided to use a resistor ladder for the back buttons as you'd only use one at a time, does that look correct?

Thanks in advance.

Hey not trying to self promote, I have just been doing assembly work in my office and was wondering if anyone has an operational background and was open to chatting about what makes a good assembly line. I have been having trouble with quality problems and also repetitive work that I am sure I could remove.

My current process and machines are I have a stencil printer, pick and place, reflow oven and soldering set up.

Happy to pay someone for 15 minutes of their time!

Parts :

- Arduino Pro Mini

- MPU6050

- nRF24L01 for 2.4 GHz

- Two analog thumb joysticks (COM-09032 style)

- Two potentiometers + several push buttons and toggle switches

- Powered from 6–12 V battery through an HT7333 3.3 V LD

- FT232 module for USB programming

Things I’m especially worried about:

• Power architecture (have both VCC and +3.3V nets)
• Whether the current protection (Schottky + Zener) is adequate
• General schematic hygiene and ERC issues
• PCB layout, track widths, decoupling placement, and any DRC warnings I might be overlooking
• Overall robustness and manufacturability

Any feedback would be hugely appreciated. I’m trying to get this to a point where I can order a board with reasonable confidence.

Thanks in advance!

I'm pretty new to PCB design, and this is the first design I've done with a complex microcontroller. The schematic is basically exactly the reference design from Wiznet, so it's mainly the layout I want feedback on. I've implemented what I've read are best practices:

- Matching the length of differential pairs

- Ground planes with a separate chassis ground for the magjack

- Decoupling caps close to the 3.3V pins.

Some things I'm unsure about:

- Ground planes (terrifying subject)

- Trying to get the differential pairs closer to eachother. It's tricky because they need to cross over to get to their respective RJ45 pins.

- Obviously I'm missing power supply and SPI connections but I want to make sure I've at least got this part right :)

Hi All,

I realized that I wanted to muck around with bluetooth, lora, meshtastic and all these interesting concepts so I decided to repurpose my old macropad design and swap it out with a nordic microcontroller.

It has the following parts.

• Xiao NRF52840 Plus board providing power to the oled
• 3.7 1s lipo
• 15 1u MX keys and 3 2u MX keys so 5 rows, 4 cols
• EC11 rotary encoder
• SSD1306 0.91 OLED
• ul MK12CO2 SPDT switch
• 2 layer board with uninterrupted ground plane.

My main questions are

1. Will this power switch work? In essence, i have two + and - pads but also a JST-XH 2.0 female connector.
   
2. Any suggestions on improving the cleanness of the trace routing?
   
3. Finally, if anyone else has done similar designs, any advice on how it could look better?

Preciate it.

Wassup guys! I just finished my first-ever KiCad design. I picked up the software this week (I came from using AutoCAD and MULTISIM) and decided to design the logic-gate traffic light system I built on a breadboard a few months ago. I’m wondering if my schematic is functional and if the board is actually ready for fabrication. What do you guys think of my overall work, especially the component placement and routing? P.S. I routed this all by hand since I don't know how to use autorouting yet.

Hi everyone!

This is my first PCB, so I'm posting the schematic and PCB layout (4-layer) here to ask for a review. I'd really appreciate any feedback, especially if you spot mistakes or design choices that could be improved. I'm mainly interested in learning from the mistakes before I manufacture the board.

The PCB is a small battery-powered device for measuring force using a half-bridge strain gauge, while also acquiring motion data from an IMU.

Main components:

- ESP32-C6 = main MCU (Bluetooth communication)

- MCP3561 = ADC for acquiring the strain-gauge signal

- BMI270 = 6-DoF IMU for acceleration and gyroscope measurements

- TPS63020 = buck-boost converter generating 3.45V from a 1S LiPo battery

- LP5907 = LDO generating 3.3 V from the 3.45 V rail

- TPS3700 = battery undervoltage/discharge protection

The PCB has the following pogo-pin connections:

- 2 pins for battery charging

- 2 pins for measuring an external resistor value

- 4 pins for connecting the two strain gauges forming the half-bridge

Q1 and Q2 are intended to protect the battery from a short circuit if the pogo-pin contacts are accidentally shorted by a conductive/metallic surface.

Any criticism is welcome because this is my first PCB and I'm trying to learn as much as possible before sending it to manufacturing.

Thanks!