Project Start Inquiry

flux

Yes. The safe fix is to remove only copper that the connectivity checker proves is redundant, then reroute any connection that becomes open.
Recommended sequence:
  1. Save a restore point.
  2. Delete the 29 redundant copper groups in small batches.
  3. Check airwires and DRC after each batch.
  4. Preserve the valid ESP32-to-LoRa paths and shared SPI branches to J18/J19.
  5. Surgically reroute any newly exposed connections using shorter paths and fewer vias.
  6. Finish with full DRC and verify:
    • 0 airwires
    • 0 redundant/dangling/floating copper
    • 0 shorts or clearance violations
    • continuity to LoRa, display, touchscreen, and microSD
This is fixable, but it should be treated as a controlled cleanup rather than deleting all 114 objects at once.
M

merlin2232

do that

flux

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.

flux

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.

flux

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.

flux

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
Sign up to send

Files

Schematic

Layout

3D View

Locked Module BOM
Procurement status
These three modules are procurement-locked for the prototype carrier. Do not substitute a different variant or carrier-board layout without rechecking voltage, pinout, header spacing, body clearance, and firmware configuration.

Table

Ref.FunctionManufacturer / brandLocked ordering designationQty.BOM status
MOD1Main controllerEspressif SystemsESP32-S3-DevKitC-1-N8R21Locked
MOD2GNSS receiverTeyleten Robot carrier using Zhongke Microelectronics ATGM336H-5NTeyleten Robot ATGM336H GPS/BDS breakout, ATGM336H-5N, VCC/GND/TXD/RXD/PPS version1Locked by module description and acceptance criteria; seller SKU must be recorded at purchase
MOD3915 MHz LoRa radioWaveshareSX1262 LoRa Node Module (HF), 850–930 MHz, 22 dBm, 22 × 19 mm, 2×8 at 2.54 mm pitch1Locked
MOD1 — ESP32-S3 development module
  • Exact MPN: ESP32-S3-DevKitC-1-N8R2
  • Required memory variant: N8R2 — 8 MB flash and 2 MB PSRAM.
  • Purchase note: Listing and package label must explicitly contain the full suffix N8R2. Do not accept N8, N8R8, N16R8, or another DevKit variant as an automatic substitute.
  • Mechanical note: Buy the standard Espressif DevKitC-1 board with two 1×22, 2.54 mm header rows. The carrier is intended to use socket headers; confirm the purchased board has pins fitted or purchase suitable male headers separately.
  • Electrical note: The carrier supplies the module through its 5 V input. Do not simultaneously back-power it from an external USB connection unless the final schematic explicitly supports that operating case.
  • Receiving inspection: Verify the module marking, 44-pin header format, antenna end orientation, and full N8R2 suffix before assembly.
MOD2 — ATGM336H GNSS breakout
  • Receiver IC/module: ATGM336H-5N.
  • Locked carrier description: Teyleten Robot ATGM336H GPS/BDS breakout exposing VCC, GND, TXD, RXD, and PPS.
  • Purchase note: “ATGM336H” is sold on multiple carrier layouts and does not uniquely define the PCB footprint. Purchase from the same Teyleten Robot listing used for the prototype and record the seller URL/SKU on the purchase order.
  • Do not substitute: Reject 4-pin versions without PPS, boards with a different pin order, or a different header pitch unless the carrier footprint and wiring are revised first.
  • Voltage note: Confirm the breakout’s stated input-voltage range and onboard regulation from the actual listing. The interface UART logic must be compatible with 3.3 V ESP32 GPIO.
  • Antenna note: Confirm whether the ordered board includes an onboard ceramic antenna and/or an external antenna connector; keep the antenna area unobstructed.
  • Pre-footprint hold point: Before PCB fabrication, archive a dimensioned product drawing or physically measure header pitch, pin order, row arrangement, board outline, and antenna overhang. The BOM is electrically locked, but its seller-specific carrier geometry still requires final verification.
  • Receiving inspection: Check five-pin labeling and pin order against the archived listing before inserting the module.
MOD3 — SX1262 LoRa module
  • Locked product: Waveshare SX1262 LoRa Node Module HF.
  • Required frequency variant: 850–930 MHz, suitable for 915 MHz operation.
  • Required RF output rating: 22 dBm maximum.
  • Required geometry: 22 × 19 mm body, two rows of eight connections, 2.54 mm pitch, intended to receive user-installed header pins.
  • Required pin set: ANT, GND, CS, CLK, MOSI, MISO, RESET, BUSY; GND, GND, RXEN, TXEN, DIO2, DIO1, GND, 3V3.
  • Purchase note: Listing must explicitly state HF or 850–930 MHz. Do not buy the LF 410–525 MHz version.
  • Assembly note: Purchase and solder two straight 1×8 male header strips at 2.54 mm pitch if pins are not included. Maintain the module orientation defined by the ANT and 3V3 end labels.
  • RF note: This is a 3.3 V module. Fit the correct 915 MHz antenna before transmitting; never operate at high power without a suitable antenna/load.
  • Regulatory note: The module selection does not by itself certify the finished device. Antenna choice, output power, enclosure, and regional firmware settings remain part of FCC/ISM compliance.
  • Receiving inspection: Verify HF marking, dimensions, pin labels, and antenna connector/ANT pad arrangement before assembly.
Purchase-order notes
  1. Require exact-match approval for MOD1 and MOD3; substitutions are not authorized.
  2. For MOD2, use the same seller listing and carrier revision. Record the listing URL, seller SKU, and a product-photo revision with the PO.
  3. Buy at least two of each module for prototype bring-up and replacement.
  4. Photograph both sides and measure each delivered module before releasing the carrier PCB for fabrication.
  5. Update this file if a seller changes the module PCB, pin order, dimensions, antenna implementation, or memory/frequency suffix.

  • Procurement status

  • MOD1 — ESP32-S3 development module

  • MOD2 — ATGM336H GNSS breakout

  • MOD3 — SX1262 LoRa module

  • Purchase-order notes