Project Starter


PCB component placement is complete on a preliminary 100 × 100 mm, 4-layer board. P4 faces left, USB-C faces down, microSD ejects right, OLED is along the lower/front edge, ESP32 antenna overhangs the top edge, and ADXL345 is isolated in the rigid interior sensor zone.
Open items
  • No component-body or courtyard collisions were found.
  • No routing was performed; 149 airwires remain as expected.
  • Resizing removed 24 legacy GND stitching vias that were outside the new board outline; 33 in-board vias remain.
Next steps
  1. Review enclosure-facing connector, OLED, button, and LED positions.
  2. Confirm mounting-hole locations around the ADXL345 support region.
  3. Approve placement before routing begins.
I’ll read the placement-review requirements, compare them with the current 100 × 100 mm board, and apply any requested placement-only corrections without routing or schematic changes.
I parsed the compact-placement requirements and prepared the full placement brief, but no board changes were made because no ACUs remain.
Remaining work:
  • Add four mounting holes and mechanical keepouts.
  • Re-place all components from scratch near the 70 × 60 mm target.
  • Iteratively shrink and verify RF, ADXL345 rigidity, regulator clusters, connector access, collisions, and overhangs.
  • Produce the requested datasheet-compliance and dimensional report.
  • Stop before routing, as specified.
Set board and place
Clarify mechanical constraints
Placement compliance report

Waiting for input


Project Specification
Project Overview
Production-intent ESP32 vibration monitoring sensor. Status: Draft / engineering review. Phase 1 is schematic-only.
Intended Use
Monitoring node that samples vibration, displays status, logs to microSD, and communicates over ESP32 Wi-Fi/Bluetooth. Intended for assembled production hardware, not a breakout-board prototype.
What the Device Should Do
  • Operate from protected 9–24 V P4 input, USB-C 5 V, or both.
  • Prefer P4-derived 3.3 V and prevent cross-backfeed.
  • Disable the complete sensor via low-current enable/power-path logic.
  • Program through CP2102N with automatic and manual BOOT/RESET.
  • Measure vibration with ADXL345 at I2C address 0x53 on filtered ADXL_3V3.
  • Support a raw 0.91-inch 128×32 I2C OLED only if an exact LCSC-stocked panel and support circuit are verified.
  • Log to a bare microSD socket with card detect when available.
  • Provide SW1/SW2, a low-side-driven RGB LED, and requested test points.
Main Features
ESP32-WROOM-32E-N4; ADXL345; USB-C USB 2.0 UFP; CP2102N; dual-source 3.3 V power; microSD; conditional raw OLED; RGB LED and switches.
System Architecture

Diagram


9–24 V P4 PTC + reverse MOSFET + TVS + damped EMI BUCK[~2 A synchronous 3.3 V buck USB-C UFP USB ESD + CC Rd REG[USB 5 V to 3.3 V regulator MUX[P4-preferred ideal-diode mux REG-- SYS[SYS_3V3 ESP[ESP32-WROOM-32E-N4 ADXL[ADXL345 @ node_0x53 UI[RGB LED + SW1/SW2
Hardware Subsystems
P4 protection/buck; USB-C/ESD/regulator; preferred-source mux/master enable; ESP32 core and boot; CP2102N programming; ADXL345; conditional raw OLED; microSD; UI; service test points.
Interfaces and Connections
P4 9–24 V nominal; USB-C UFP with independent 5.1 kΩ CC resistors; CP2102N TXD→ESP32 U0RXD and RXD←ESP32 U0TXD; shared 3.3 V I2C; SPI microSD with dedicated CS and card detect.
Power and Runtime Expectations
No battery. USB-only, P4-only, and simultaneous operation are required. P4 is preferred. No USB-PD requested.
Power Tree and Power Budget
A source-referenced budget must precede final power-path sizing. Target at least 1 A continuous SYS_3V3 capability with ESP32 transient margin; requested P4 buck target is about 2 A. Exact budget is gated by selected parts and datasheets.
Manufacturing and Assembly Expectations
Production SMD. Every BOM line, including passives, requires a verified commercially available LCSC number, preferably JLCPCB-assemblable. No dev/breakout boards; only ESP32-WROOM-32E may be a module. No placeholders or silent substitutions.
Firmware-Relevant Hardware Requirements
Automatic DTR/RTS bootloader entry, manual BOOT/RESET, sensor sampling, display, storage, switches, LED, and wireless communication. The exact GPIO map must be copied from the supplied attachment; no attachment is currently visible in project assets/files, so pin assignment remains unresolved. Avoid strapping pins except GPIO0 BOOT.
Physical Design Expectations
PCB sizing, placement, routing, stackup, and manufacturing outputs are outside phase-1 scope.
Important Design Decisions
P4-preferred no-backfeed mux; master switch acts through enable logic; unresolved OLED is omitted rather than approximated.
Assumptions
Common ground; 3.3 V I2C. Exact GPIO map, exact requested test-point list, and raw OLED panel details are pending because no attachment is visible.
Success Criteria
Readable complete schematic; datasheet-compliant support; LCSC-backed BOM; explicit no-connects; ERC reviewed and justified; stop before PCB work.
Change Notes
Initial requirements capture from the phase-1 brief.
  • Project Overview

  • Intended Use

  • What the Device Should Do

  • Main Features

  • System Architecture

  • Hardware Subsystems

  • Interfaces and Connections

  • Power and Runtime Expectations

  • Power Tree and Power Budget

  • Manufacturing and Assembly Expectations

  • Firmware-Relevant Hardware Requirements

  • Physical Design Expectations

  • Important Design Decisions

  • Assumptions

  • Success Criteria

  • Change Notes