PCB Routing Congestion

Blocked by permissions: this account has view-only access, so I could not move components or run the edit-gated auto-route board check.
What I verified:
  • Current DRC: 513 errors, 0 warnings
  • All reported DRC errors are Airwires: 513 remaining
  • Routing feasibility from layout inspection: UNROUTABLE
  • Main affected area: near (27.5 mm, 0 mm) around FCC1, UART3_FCC1, U11, LED4
  • Key affected nets/signals called out by congestion analysis: FCC1 PB1–LED4 A, UART3_FCC1 3–FCC1 PD8, U11 RXD–FCC1 PB14, FCC1 PB15–U11 TXD, R53 P1–FCC1 PA11
Open items:
  • Targeted FCC/UART cluster spreading was not applied due to view-only access.
  • Auto-route feasibility check was not executed because that tool also requires edit access.
  • The board still has 513 airwires and remains unrouteable as placed.
Suggested next steps:
  1. Grant edit access or open the owner/editable fork.
  2. Re-run the scoped placement fix for FCC1/UART3_FCC1/U11/LED4.
  3. Run auto-route board check, then full DRC.
  4. If feasibility improves, run the router and report final remaining airwire/DRC counts.
Run FULL DRC feasibility improves, run the router and report final remaining airwire/DRC counts
I’ll re-run the full read-only DRC now and report the current counts; routing/auto-route still requires edit access, so I can only run it if this project becomes editable.
Full DRC re-run completed at 2026-07-27 20:13:58Z.
Results:
  • Total DRC errors: 513
  • Total DRC warnings: 0
  • Airwires remaining: 513
  • Other DRC categories shown: 0 errors / 0 warnings
  • Router was not run because the project is still view-only for this account; routing requires edit access.
The design is therefore not complete and remains unrouted.
Prepare editable fork
Summarize routing blockers
List critical airwires
Check latest commits

Refine this doc
Ask about this doc
KiCad Import Status
Source files
Uploaded KiCad legacy schematic/layout files:
  • Hades.sch — top-level power/input regulation sheet
  • FCC.sch — STM32H753 flight-control computer core
  • FCCPeripherals.sch — PWM, EEPROM/flash, UART/I2C/ADC/RC connectors
  • NAVC.sch — STM32F405 navigation computer core
  • NAVCPeripherals.sch — IMU, magnetometer, temperature sensor, GPS, NAVC connectors
  • Connections.sch — USB, SWD, interconnect, UART bridge, GPS backup connector
  • Sensors.sch — parsed as effectively empty/malformed ($EndSCHEMATC only, no components)
  • Hades.net — KiCad netlist used to reconstruct connectivity
  • Hades.kicad_pcb — PCB layout/reference; board outline and some footprint coordinates were extracted
What is now recreated in Flux
The schematic is now reconstructed at the component and logical-net level.
Current status after this update:
  • Schematic components: 208 physical components plus generated net/no-connect helper objects used by Flux connectivity
  • Nets reconstructed from Hades.net: 171
  • ERC electrical checks run for floating pins, power pins, pin-to-pin, and no-connects: clean for checked categories
  • Added netlist-missing components: C56, FB4, FB5, FB6, D4, D5, JP2
Major recreated blocks:
  • Power input and regulation: XT60 input, INA219 monitor substitute, MIC26903 buck, LD39200 LDO, inductor, Schottky diode, bulk/decoupling/feedback passives, LEDs
  • FCC core: STM32H753VIT6, 25 MHz crystal, decoupling, pullups, switches, status LEDs, test points
  • FCC peripherals: PCA9685 PWM controller, PWM headers, PicoBlade connectors, EEPROM/flash substitutes, support passives
  • NAVC core: STM32F405RGT6, 25 MHz crystal, decoupling, pullups, switches, status LEDs, test points
  • NAVC peripherals: BMI088 IMU, TMP100 temperature sensor, IIS2MDCTR magnetometer, MAX-8Q GPS, pressure sensor, PicoBlade connectors, support passives
  • Connections: USB Micro-B connectors, CH330N USB-UART bridges, SWD headers, solder jumpers, GPS backup connector, ferrite beads, Schottky protection parts
PCB layout recreation status
Board outline recreated from KiCad Edge.Cuts:
  • Bounding box: approximately 100.078 × 60.198 mm
  • Rounded-corner outline reconstructed from KiCad line/arc geometry
  • 4-layer stackup applied with inner GND and power planes
Placement:
  • Exact KiCad coordinates were recovered and applied for the board outline plus a subset of footprint placements, including the main MCUs, several ICs, key USB/connectors, test points, some passives, and selected protection parts.
  • Remaining components were cleaned up with placement optimization inside the KiCad outline.
  • Final placement is not an exact full KiCad placement clone because the uploaded PCB file extraction exposed only partial footprint coordinate data through the available parser.
Routing:
  • Not routed yet. Airwires remain and are expected.
Exact missing parts and substitutions
Exact parts not found in the Flux library; missing-part requests were filed earlier:

Table


KiCad partStatus / Flux substituteNote
W25N01GVZEIG_TRW25N04KVZEIR used for U4SPI NAND density/command assumptions must be reviewed in firmware/layout
24CW1280T-I/OT24LC64T-I/OT used for U3, U9EEPROM capacity differs significantly; verify firmware expectations
TE Connectivity 5-1814832-1CONSMA001-G used for ANT1RF/mechanical footprint must be verified before manufacturing
Other substitutions:

Table


KiCad sourceFlux component usedNote
INA219AIDCNRINA219AIDCNTSame INA219A SOT-23-8/DCN family; tape/reel suffix differs
Ferrite_Bead_SmallMPZ1005S121HT0000402 ferrite bead substitute
u-blox MAX-8Q / MAX module footprintMAX-8QLibrary GPS module used
Molex 53048-0710530470710Related 7-position Molex connector substitute; exact 53048-0710 not found
PWM_SIG1 1x08 vertical 2.54 mm header1x08 2.54 mm horizontal headerExact vertical 1x08 was unavailable in search result
CH330CH330NClosest Flux USB-UART bridge library match
Known limitations remaining
  1. PCB placement is only partially reference-exact because not all footprint coordinates could be extracted from the uploaded .kicad_pcb via the available file parser.
  2. Airwires remain because routing has not been run.
  3. Several generic passives still use Flux generic footprints/properties rather than exact KiCad footprint geometry.
  4. Substituted parts must be reviewed before manufacturing, especially U3, U4, U9, ANT1, and the PWM header.
  5. Mounting holes were identified in KiCad at approximately (29.718,29.718), (121.031,29.845), (29.845,81.153), and (121.031,81.153) mm, but they are not fully recreated as dedicated mounting-hole components yet.
  1. Review the schematic visually for readability; the logical ERC is clean, but the generated net portals are not hand-polished.
  2. Provide the original KiCad project archive if exact full placement/routing recreation is required.
  3. Verify or replace substitute parts before layout finalization.
  4. Add mounting holes/mechanical constraints.
  5. Route the PCB, then run DRC and manufacturing checks.
  • Source files

  • What is now recreated in Flux

  • PCB layout recreation status

  • Exact missing parts and substitutions

  • Known limitations remaining

  • Recommended next actions

Assets

Assets are files uploaded to this project which can be used in various ways.

Hades Flight Computer thumbnail
Imported/reconstructed Hades flight-computer design based on uploaded KiCad schematics, including NAVC, FCC, sensors, peripherals, and connections; layout will be recreated from the KiCad PCB only as a reference.

Properties

V

Pricing & Availability

Distributor

Qty 1

Arrow

$61.19–$72.71

Digi-Key

$2.43

HQonline

$41.99–$42.03

LCSC

$83.59–$84.49

Mouser

$86.21

TME

$22.07

Verical

$50.45–$356.18

Controls