Project Start Inquiry


Inspect the completed LoRa routing changes and summarize trace lengths, vias, and remaining risks.
I can’t inspect the completed LoRa routing changes because no ACUs are currently available.
Known prior state
  • LoRa CS was connected.
  • Board had 0 airwires and no routing DRC errors before optimization.
  • J12/J13 placement and 15.24 mm spacing were verified.
Still unverified
  • Before/after trace lengths and via counts for each LoRa net
  • Shared SPI continuity to the display, touchscreen, and microSD
  • Remaining airwires, shorts, dangling/floating copper, and clearance violations
  • Whether optimization altered antenna/U.FL clearance or return paths
Inspect the current PCB routing for the LoRa nets and report trace lengths, via counts, and DRC risks.
I can’t inspect the live PCB because no ACUs are available.
Pending verification:
  • Trace length and via count for each LoRa SPI/control/power net
  • Shared SPI continuity to the display, touchscreen, and microSD
  • Airwires, shorts, clearance violations, and dangling/floating copper
  • Copper clearance near the LoRa module’s U.FL/RF-launch area
No routing changes were made in this request.
Review LoRa routing
Check LoRa placement
Review LoRa schematic

ESP32 DevKit Socket Orientation Audit
Scope and result
Audit target: ESP32-S3-DevKitC-1-N8R2 installed in carrier sockets J14/J15, with J9/J10 as unpopulated one-to-one breakouts.
Result: the live schematic and PCB are already consistent with Espressif’s authoritative component-side/top-view mapping for component-side-up insertion with the DevKit USB end facing the carrier’s right-hand board edge. No socket net reassignment, rotation, copper deletion, or rerouting was required. Blindly changing J14/J9 pins 21 and 22 to GND would be incorrect for the present physical orientation.
Authoritative sources and view convention
Sources:
Espressif’s component-side view has J3 on the left and J1 on the right, with pin numbers running from the antenna end (pin 1) toward the USB end (pin 22). The carrier rotates this arrangement 90° counter-clockwise: antenna end is toward carrier X−/left, USB end is toward carrier X+/right, J1 becomes the upper row, and J3 becomes the lower row. A bottom-side view would visually reverse this relationship and must not be used for socket mapping.
Official header pinout
J1 — carrier J14 and breakout J9

Table


PinOfficial functionLive net
13V3ESP_3V3_BREAKOUT
23V3ESP_3V3_BREAKOUT
3RST/ENESP_RST
4GPIO4LORA_TXEN_GPIO4
5GPIO5LORA_RXEN_GPIO5
6GPIO6LORA_DIO2_GPIO6
7GPIO7LORA_DIO1_GPIO7
8GPIO15ESP_GPIO15
9GPIO16ESP_GPIO16
10GPIO17GPS_TXD_TO_ESP_RX_GPIO17
11GPIO18GPS_RXD_FROM_ESP_TX_GPIO18
12GPIO8LORA_BUSY_GPIO8
13GPIO3ESP_GPIO3
14GPIO46ESP_GPIO46
15GPIO9LORA_RESET_GPIO9
16GPIO10LORA_CS_GPIO10
17GPIO11LORA_MOSI_GPIO11
18GPIO12LORA_SCK_GPIO12
19GPIO13LORA_MISO_GPIO13
20GPIO14ESP_GPIO14
215V5V
22GNDGND
J3 — carrier J15 and breakout J10

Table


PinOfficial functionLive net
1GNDGND
2U0TXD/GPIO43ESP_U0TX_GPIO43
3U0RXD/GPIO44ESP_U0RX_GPIO44
4GPIO1ESP_GPIO1
5GPIO2ESP_GPIO2
6GPIO42ESP_GPIO42
7GPIO41ESP_GPIO41
8GPIO40ESP_GPIO40
9GPIO39ESP_GPIO39
10GPIO38ESP_GPIO38
11GPIO37ESP_GPIO37
12GPIO36ESP_GPIO36
13GPIO35ESP_GPIO35
14GPIO0ESP_GPIO0
15GPIO45ESP_GPIO45
16GPIO48ESP_GPIO48
17GPIO47ESP_GPIO47
18GPIO21GPS_PPS_GPIO21
19GPIO20/USB D+ESP_USB_D+_GPIO20
20GPIO19/USB D−ESP_USB_D-_GPIO19
21GNDGND
22GNDGND
Physical readback
All four headers are on the top side.

Table


RefFunctionCenter (mm)RotationPhysical pin-1 endPhysical pin-22 end
J14DevKit J1 socket, upper row(4.635, 19.200)X−/left, antenna endX+/right, USB end
J15DevKit J3 socket, lower row(4.635, −6.200)X−/left, antenna endX+/right, USB end
J9J14/J1 breakout(4.635, 24.2998)180°X−/leftX+/right
J10J15/J3 breakout(4.635, −11.300)180°X−/leftX+/right
The 180° rotations on J9/J10 compensate for the breakout footprint’s native origin/orientation; readback of pad coordinates and copper confirms pin N remains vertically aligned with socket pin N. Therefore the breakouts are one-to-one, not reversed.
J14-to-J15 row spacing is 25.40 mm, matching the Espressif mechanical arrangement. Pin pitch is 2.54 mm. The DevKit is inserted from the carrier top with its components visible, antenna end toward the left, and USB connectors toward the right-hand board edge/open space.
User GND concern
  • J14:21 = 5V, not GND. This is correct because J14 is physically the official J1 row in the selected component-side-up, USB-right orientation.
  • J14:22 = GND.
  • J9:21 = 5V, not GND. J9 is the one-to-one breakout for J14/J1.
  • J9:22 = GND.
  • The positions that are both GND are J15:21/J15:22 and their one-to-one breakout J10:21/J10:22, because J15/J10 implement official J3.
Changing J14/J9 pins 21 and 22 both to GND would remove the intended protected 5 V feed to the DevKit and would contradict Espressif’s official J1 pinout.
Power-architecture check
  • DevKit 5 V enters at J14:21/J9:21 on net 5V, downstream of the existing protection path.
  • DevKit 3V3 pins J14:1 and J14:2 are on isolated net ESP_3V3_BREAKOUT; they are not tied to the carrier 3.3 V rail.
  • GPS/LoRa remain powered from the carrier 3.3 V architecture. No 3V3 backfeed path was introduced.
Validation readback
  • Schematic mapping: all 44 socket positions match Espressif J1/J3 pin numbers and functions; J9 mirrors J14 pin-for-pin and J10 mirrors J15 pin-for-pin.
  • ERC: no matching open warnings/errors were returned by the selected electrical checks at 2026-08-13 08:06 UTC.
  • Socket-specific changes: none were necessary, so this audit introduced zero new ERC/DRC issues and invalidated no copper.
  • Current board routing state is not globally complete: 18 pre-existing airwires remain, including ESP32 endpoint nets such as GPIO35, GPIO2, GPIO12, GPIO10, GPIO9, GPIO8, GPIO4, GPIO18, GPIO7, GPIO11, GPIO13, GPIO5, GPIO6, GPIO21, GPIO17, and 5V, plus one unrelated rail connection. Two pre-existing dangling traces are reported (e902bc4b…, f14572c9…).
  • Current DRC also reports 44 pre-existing invalid-layer trace errors because the declared stackup is standard-1-layer while existing copper includes bottom-layer traces. These issues predate this no-change audit and were not modified because they are outside the focused socket-orientation correction scope.
Completion status
  • Authoritative top/component-side pinout audit: completed.
  • Socket insertion orientation determination: completed.
  • J14/J15 mapping correction: completed — verified correct as-is; no mutation required.
  • J9/J10 one-to-one breakout verification: completed.
  • J14/J9 pin-21/pin-22 GND concern: completed — concern resolved; pin 21 is correctly 5V and pin 22 is GND.
  • Copper removal/rerouting caused by correction: unattempted/not applicable — no correction invalidated copper.
  • ERC/airwire/DRC readback: completed, with pre-existing global layout residuals documented above.
  • Scope and result

  • Authoritative sources and view convention

  • Official header pinout

  • J1 — carrier J14 and breakout J9

  • J3 — carrier J15 and breakout J10

  • Physical readback

  • User GND concern

  • Power-architecture check

  • Validation readback

  • Completion status