Project Start Inquiry


do that
I’ll clean the 29 redundant copper groups in controlled batches, preserving required shared-SPI branches, then reroute any exposed connections and finish with full connectivity and DRC verification.
Created a thread
PCB Redundant Copper Cleanup
Completed
View Thread
The cleanup is still running through the batch-by-batch verification. I’m keeping it active until the redundant-copper and final routing checks reach a verified state.
Thought for 14 mins 18 sec
Awaiting 1 background task
"PCB Redundant Copper Cleanup" completed.
The cleanup pass is complete. I’m reconciling its exact removals and reroutes against the live board, then running independent routing-state and full DRC checks before accepting it.
Redundant-copper cleanup is complete and independently verified.
  • Removed 114 redundant trace/via objects across 29 groups
  • Repaired affected 5 V and LoRa TXEN connections
  • 0 airwires
  • 0 redundant, dangling, or floating copper
  • 0 shorts, overlaps, clearance, keepout, layer, via, edge, or component-placement violations
  • All component positions and orientations were preserved

Board Bring-Up Plan
Safety and prerequisites
  • Treat the 3S LiPo path as a high-energy source. Use eye protection, a fire-safe work area, insulated probes, and a current-limited bench supply.
  • Do not connect a battery until all unpowered checks and the initial barrel-input test pass.
  • Install the ESP32-S3-DevKitC-1 only after the carrier rails are verified. U7 is schematic-only; the removable module plugs into J14/J15. Align pin 1 and the USB/antenna end with the board markings before insertion.
  • Power the DevKit carrier from the board's 5 V socket pin only. Do not inject 3.3 V into the module regulator output.
  • USB back-power warning: do not connect the DevKit USB cable while board 5 V is energized unless the measured setup prevents back-feeding between USB VBUS and the carrier 5 V rail. Prefer one source at a time during bring-up.
  • Connect the correct GPS and LoRa antennas before enabling RF tests; never transmit LoRa without its antenna.
1. Visual and mechanical inspection — no power
  1. Inspect polarity/orientation of J1 USB-C, barrel input, charger/protection ICs, MOSFETs, diodes, electrolytic/polarized parts, J3/J4 battery interfaces, and J14/J15 sockets.
  2. Confirm J14/J15 are straight, parallel, and 25.40 mm center-to-center per the official Espressif DevKitC-1 mechanical drawing; verify the module inserts without stress.
  3. Verify J9/J10 remain separate unpopulated breakout/test rows and do not contact or overlap J14/J15 pads.
  4. Confirm the module antenna/USB end faces the board right edge and the antenna region is free of metal, wiring, batteries, and enclosure material.
  5. GPS mechanical verification hold point: stop before GPS electrical test until the exact GPS module footprint, connector orientation, antenna location, height, and enclosure clearance have been physically checked against the purchased module and mating hardware. Record approval/rework disposition.
Pass: no bridges, reversed parts, damaged pads, socket interference, or unresolved GPS mechanical mismatch.
2. Unpowered resistance and short checks
With battery, barrel, USB-C, ESP32, GPS, and LoRa disconnected:
  1. Measure resistance from BARREL_15V_RAW, USB_PD_15V, USB_PD_GATED, CHARGER_VBUS, SYS, BAT+, 5V, 3V3, and each cell tap to GND.
  2. Measure resistance between adjacent balance pins/cell taps and between BAT+ and PACK/BAT negative. A momentary low reading that rises while capacitors charge may be normal; a stable near-short is not.
  3. Check continuity from J14/J15 to corresponding J9/J10 pins and verify no continuity between unrelated adjacent pins.
  4. Verify protection FET source/drain paths are not solder-bridged and the current-shunt Kelvin nodes are not shorted to power copper.
Pass: no persistent low-ohm rail short, no adjacent socket-pin bridge, and socket-to-breakout mapping is one-to-one.
3. Initial current-limited 15 V barrel test — no battery
  1. Leave USB-C and battery disconnected. Leave the ESP32/GPS/LoRa modules removed.
  2. Set bench supply to 15.0 V, current limit initially 100 mA. Connect with supply off; then enable.
  3. If current limit is reached or any component heats, switch off immediately and investigate. Otherwise raise the limit only as needed for expected quiescent operation, not above 300 mA during this unloaded stage.
  4. Verify the protected barrel node, BQ25792 input path, and SYS. With no battery, charging must be disabled or configured safely; the charger datasheet warns against leaving BAT floating while charge is enabled.
  5. Confirm SYS regulation is stable, then verify 5 V and 3.3 V at their test points (TP17 for 5 V, TP18 for 3.3 V; TP6 for SYS). Check ripple and startup with an oscilloscope.
Pass: no current-limit event/heating; protected input and SYS are plausible; 5 V and 3.3 V are within ±5% and stable.
4. USB-C PD negotiation and gated VBUS
  1. Remove barrel power. Use a known-good USB-C PD source and a PD protocol analyzer or trusted inline meter.
  2. Connect USB-C with battery and loads absent. Confirm initial default VBUS behavior and that high-voltage power does not appear downstream before a valid contract.
  3. Verify STUSB4500 negotiation reaches the intended 15 V PDO and source capability is at least 2 A before enabling normal charging.
  4. Measure USB_PD_15V, USB_PD_AUX, PD_SINK_ENABLE_N, the Q7 control stage, USB_PD_GATED, and CHARGER_VBUS. Confirm VBUS gating follows the negotiated/valid state and the eFuse/protection path does not bypass the gate.
  5. Repeat cable flip/orientation and detach/reattach tests; confirm the gated rail discharges or isolates as designed.
Pass: valid 15 V contract; no premature gated VBUS; correct active-low enable behavior; repeatable disconnect isolation.
5. Balance connector and 3S battery pre-check
Before plugging J3/J4 battery/balance harnesses into the board:
  1. Identify pack negative, cell-1 tap, cell-2 tap, and pack positive using the battery manufacturer's pinout—never wire by color alone.
  2. With the pack isolated, measure cumulative voltages in connector order: B-→C1 ≈ one cell, B-→C2 ≈ two cells, B-→B+ ≈ three cells. Also calculate each cell voltage: C1-B-, C2-C1, B+-C2.
  3. Each cell must be within the cell manufacturer's safe range and cell mismatch should be small (target ≤50 mV before first charge; investigate larger mismatch).
  4. Confirm connector order and polarity against the schematic before mating. Plug balance sense first only if required by the selected BMS/module procedure; otherwise follow the battery/protection supplier's prescribed sequence.
Pass: monotonic tap order, correct 3S cumulative voltage, no reversed segment, and acceptable cell balance.
6. Charger SYS/BAT and power-path behavior
  1. Connect the verified battery with input power off. Observe inrush and confirm SYS is supported from BAT through the NVDC path.
  2. Verify BAT+, SYS, 5 V, and 3.3 V test points. Confirm no unintended USB/barrel back-feed.
  3. Apply current-limited 15 V barrel input. Start with conservative charger settings; confirm input current limit, VSYSMIN/SYS behavior, BAT charging direction, and that the pack does not exceed 12.6 V total.
  4. Repeat with USB-C PD after successful negotiation. Verify system load has priority and charging current reduces under input-current or input-voltage DPM.
  5. Remove input power under load; SYS should transition to battery without brownout outside the expected transient envelope.
Pass: correct SYS/BAT direction, stable handover, controlled charge current, no overvoltage or reverse current.
7. Protection and balancing validation
  1. Monitor all three cell voltages individually while charging; verify balance action occurs only near the configured threshold and reduces the highest-cell differential.
  2. Validate pack overvoltage, undervoltage, overcurrent/short-circuit, and recovery behavior with a battery simulator or protected low-energy fixture—not by intentionally abusing a LiPo pack.
  3. Confirm protection FET gate states and voltage drops, shunt/Kelvin measurement accuracy, and that balancing resistors remain within temperature ratings.
Pass: thresholds and recovery match configuration, FETs isolate correctly, no thermal overstress, and cell spread trends downward during balancing.
8. ESP32 installation, power, and programming
  1. Power down all sources. Insert the ESP32-S3-DevKitC-1 into J14/J15 with pin 1, USB end, and antenna end correctly oriented. Confirm every pin enters its intended socket; do not offset by one position.
  2. Reapply board power from one source. Verify 5 V at the module 5V pin and confirm the module's local 3.3 V rail. Do not simultaneously feed the carrier from module USB.
  3. Test reset/boot behavior. Connect an isolated/controlled serial or native USB programming interface and load a minimal firmware image.
  4. Confirm console output, reset cause, flash/PSRAM identification for N8R2, and a GPIO heartbeat.
Pass: module boots repeatedly, programs successfully, reports expected flash/PSRAM, and no socket pin heats or browns out.
9. GPS UART and PPS
After the GPS mechanical hold point is signed off:
  1. Verify GPS power and logic levels before connecting firmware peripherals.
  2. Configure ESP32 UART with GPIO17 = GPS TXD-to-ESP RX, GPIO18 = ESP TX-to-GPS RX, and GPIO21 = PPS input according to live nets.
  3. Confirm valid NMEA/binary messages, bidirectional configuration commands if used, and PPS edge timing/amplitude on GPIO21.
  4. Test cold start with antenna view of sky and record time-to-first-fix.
Pass: error-free UART data, valid fix under suitable conditions, and stable PPS at the configured rate.
10. LoRa SPI and control
  1. Attach the correct LoRa antenna before power or transmit testing.
  2. Configure GPIO12 SCK, GPIO11 MOSI, GPIO13 MISO, GPIO10 CS, GPIO9 RESET, GPIO8 BUSY, GPIO7 DIO1, GPIO6 DIO2, GPIO5 RXEN, GPIO4 TXEN.
  3. Read the radio identity/version register at low SPI speed, then test reset and BUSY timing.
  4. Validate DIO interrupts and RX/TX switch control. Perform a low-power conducted or legal over-the-air packet test before increasing transmit power.
Pass: reliable SPI register access, correct BUSY/reset behavior, interrupts observed, RX/TX controls correct, and packets pass without excess current or heating.
Final acceptance record
  • All visual/mechanical checks pass; GPS mechanical hold point closed.
  • No unpowered shorts and all J14/J15-to-J9/J10 mappings verified.
  • Barrel and USB-C PD inputs independently pass, with correct gated VBUS behavior.
  • SYS, 5 V, and 3.3 V meet ±5% steady-state targets and remain stable through source transitions.
  • 3S tap order and per-cell voltages verified; charger and protection thresholds validated safely.
  • ESP32 boots/programs from carrier 5 V without USB back-power.
  • GPS UART/PPS and LoRa SPI/control tests pass with antennas installed.
  • Record measured values, instrument IDs, firmware revision, board serial/revision, failures, and rework for each board.
  • Safety and prerequisites

  • 1. Visual and mechanical inspection — no power

  • 2. Unpowered resistance and short checks

  • 3. Initial current-limited 15 V barrel test — no battery

  • 4. USB-C PD negotiation and gated VBUS

  • 5. Balance connector and 3S battery pre-check

  • 6. Charger SYS/BAT and power-path behavior

  • 7. Protection and balancing validation

  • 8. ESP32 installation, power, and programming

  • 9. GPS UART and PPS

  • 10. LoRa SPI and control

  • Final acceptance record