Probe E# — E-Sharp AB
Probe is made by E# (E-Sharp AB) in Sweden. Want your own boards reviewed like this? Book a meeting

AMC CPU COM6

OHWR0026 · revision R1

AMC CPU COM6 (OHWR0026 R1) is an open-hardware circuit board from the CERN Open Hardware Repository, designed in Altium Designer: a 6-layer board of 173.4 × 148.6 mm with 859 components and 842 nets, published under CERN-OHL-1.1.

review 86% walked · 29 findings: 2 blocker · 20 major · 7 minor (219 items)

Open in the interactive viewerRead the full review

AMC CPU COM6 (OHWR0026 R1) circuit board, top view: copper, silkscreen and components
Top view, rendered by Probe from the design's own fabrication data.

Design review

Probe recorded 29 findings: 2 blocker · 20 major · 7 minor (219 items) on this design. Each is shown here with its reasoning; the full review links every one to the pins, nets and datasheet pages it rests on.

  1. CopperShortBetweenNetsblockerOpen

    CopperShortBetweenNets: 2 boards×2

    2 checked by the review by Claude walker W1 (Cern session) — 2 different reasons

    At short:GND|P3V3MP, short:NetC145A_2|NetC145B_2

    Each finding, with its own headline
    • short:GND|P3V3MPGND and P3V3MP copper touch on TOP, at (27.54, 141.71): the two nets are shorted in the copper as exported

      GND and P3V3MP copper touch on TOP, at (27.54, 141.71): the two nets are shorted in the copper as exported. Where: TOP at (27.54, 141.71) (one net's copper edge lies in the other's copper). The netlist still puts the two nets apart, so every connectivity check passes; the copper the fab builds joins them. The usual cause is a pour filled before the other net's via or pad was placed (or moved), so it runs through it without a clearance: refill the zones, check the CAD tool's DRC is clean, and export again. copper-near at a site shows both nets' copper at distance 0.

    • short:NetC145A_2|NetC145B_2NetC145A_2 and NetC145B_2 copper touch on BTM, L1, L2 and TOP, at (6.66, 21.54) and 1 other place(s): the two nets are shorted in the copper as exported

      NetC145A_2 and NetC145B_2 copper touch on BTM, L1, L2 and TOP, at (6.66, 21.54) and 1 other place(s): the two nets are shorted in the copper as exported. Where: BTM at (6.66, 21.54) (one net's copper edge lies in the other's copper); BTM at (12.34, 21.54) (one net's copper edge lies in the other's copper); L1 at (6.66, 21.54) (one net's copper edge lies in the other's copper); L1 at (12.34, 21.54) (one net's copper edge lies in the other's copper); L2 at (6.66, 21.54) (one net's copper edge lies in the other's copper); L2 at (12.34, 21.54) (one net's copper edge lies in the other's copper); TOP at (6.66, 21.54) (one net's copper edge lies in the other's copper); TOP at (12.34, 21.54) (one net's copper edge lies in the other's copper). The netlist still puts the two nets apart, so every connectivity check passes; the copper the fab builds joins them. The usual cause is a pour filled before the other net's via or pad was placed (or moved), so it runs through it without a clearance: refill the zones, check the CAD tool's DRC is clean, and export again. copper-near at a site shows both nets' copper at distance 0.

  2. NetCopperSplitblockerOpen

    NetCopperSplit: 5 boards×5

    Refuted once, awaiting a second check · Claude walker W1 (Cern session)

    At split:NetC145A_2, split:NetC145B_2, split:NetC161A_2, split:NetC161B_2, split:NetC61_2

    Each finding, with its own headline
    • split:NetC145A_2NetC145A_2's copper is in 3 pieces: CON13A.5 and 1 other piece(s) are not connected to the rest of the net

      NetC145A_2's copper is in 3 pieces: CON13A.5 and 1 other piece(s) are not connected to the rest of the net. Piece 1: C145A.2 and R75A.2, on TOP, over (10.73, 21.53) to (15.47, 24.53). Piece 2: CON13A.5, on TOP, L1, L2 and BTM, 1 drill(s), over (5.05, 34.67) to (8.05, 37.67). Piece 3: CON12A.SH, on TOP, L1, L2 and BTM, 1 drill(s), over (10.73, 34.67) to (13.73, 37.67). The export files every one of these pins under the net, so every connectivity check passes; the copper the fab builds leaves them apart. Usually a pour island that touches only one via of its own net, or a track ending short of its copper: join the piece to the net and export again.

    • split:NetC145B_2NetC145B_2's copper is in 3 pieces: CON13B.5 and 1 other piece(s) are not connected to the rest of the net

      NetC145B_2's copper is in 3 pieces: CON13B.5 and 1 other piece(s) are not connected to the rest of the net. Piece 1: C145B.2 and R75B.2, on TOP, over (10.73, 5.4) to (15.47, 8.4). Piece 2: CON13B.5, on TOP, L1, L2 and BTM, 1 drill(s), over (5.05, 5.4) to (8.05, 8.4). Piece 3: CON12B.SH, on TOP, L1, L2 and BTM, 1 drill(s), over (10.73, 18.54) to (13.73, 21.54). The export files every one of these pins under the net, so every connectivity check passes; the copper the fab builds leaves them apart. Usually a pour island that touches only one via of its own net, or a track ending short of its copper: join the piece to the net and export again.

    • split:NetC161A_2NetC161A_2's copper is in 3 pieces: CON14A.10 and CON15A.19 and 1 other piece(s) are not connected to the rest of the net

      NetC161A_2's copper is in 3 pieces: CON14A.10 and CON15A.19 and 1 other piece(s) are not connected to the rest of the net. Piece 1: C161A.2 and R87A.2, on TOP, over (11.98, 80.17) to (17.14, 84.97). Piece 2: CON14A.10 and CON15A.19, on TOP, L1, L2 and BTM, 1 drill(s), over (6.3, 67.03) to (9.3, 71.83). Piece 3: CON15A.20, on TOP, L1, L2 and BTM, 1 drill(s), over (11.98, 67.03) to (14.98, 71.83). The export files every one of these pins under the net, so every connectivity check passes; the copper the fab builds leaves them apart. Usually a pour island that touches only one via of its own net, or a track ending short of its copper: join the piece to the net and export again.

    • split:NetC161B_2NetC161B_2's copper is in 3 pieces: CON14B.10 and CON15B.19 and 1 other piece(s) are not connected to the rest of the net

      NetC161B_2's copper is in 3 pieces: CON14B.10 and CON15B.19 and 1 other piece(s) are not connected to the rest of the net. Piece 1: C161B.2 and R87B.2, on TOP, over (11.98, 96.53) to (17.14, 101.33). Piece 2: CON14B.10 and CON15B.19, on TOP, L1, L2 and BTM, 1 drill(s), over (6.3, 83.39) to (9.3, 88.19). Piece 3: CON15B.20, on TOP, L1, L2 and BTM, 1 drill(s), over (11.98, 83.39) to (14.98, 88.19). The export files every one of these pins under the net, so every connectivity check passes; the copper the fab builds leaves them apart. Usually a pour island that touches only one via of its own net, or a track ending short of its copper: join the piece to the net and export again.

    • split:NetC61_2NetC61_2's copper is in 2 pieces: CON17.SHIELD is not connected to the rest of the net

      NetC61_2's copper is in 2 pieces: CON17.SHIELD is not connected to the rest of the net. Piece 1: C61.2 and R151.2, on TOP, over (-2.65, 54.09) to (-0.55, 63.13). Piece 2: CON17.SHIELD, on TOP, over (1.03, 59.74) to (2.41, 61.54). The export files every one of these pins under the net, so every connectivity check passes; the copper the fab builds leaves them apart. Usually a pour island that touches only one via of its own net, or a track ending short of its copper: join the piece to the net and export again.

  3. observationOBS-408majorOpen

    CBTL02043A PCIe/mSATA mux IC34: shutdown pin XSD (pin 2) is left floating, datasheet requires it driven LOW or tied to VSS

    The shutdown pin XSD (pin 2) of the PCIe/mSATA mux IC34 (CBTL02043A) is left floating, while the datasheet requires it driven LOW or tied to VSS. If it drifts high, every channel goes high-impedance and the mini-PCIe card's PCIe/mSATA link drops.

    Where it is

    IC34 (CBTL02043ABQ) is the 2:1 mux that routes the mini-PCIe socket CON9's lanes between PCIe5 and SATA0.

    PinAs builtSource
    2 XSDunconnected ($NONE$); schematic sheet 17 ("mPCIe") shows it with no wirenetlist; schematic
    1 / 6 / 10 VDDP3V3netlist
    5 / 11 / 20 GNDGNDnetlist
    9 SELCARD_SELnetlist

    These match the A-variant pin numbering (datasheet Table 3, p.4: CBTL02043A column, XSD = pin 2).

    What the datasheet says

    • p.4: XSD "should be driven LOW or connected to VSS for normal operation. When HIGH, all input paths are switched off". No internal pull-down is stated.
    • p.5: "The XSD pin (active HIGH) places all channels in high-impedance state" (An, Bn, Cn high-Z).

    Why it matters

    A floating CMOS shutdown input can drift high and put every channel in high-impedance, dropping the mini-PCIe card's PCIe/mSATA link.

    Fix: tie XSD to GND (or a pull-down / control line).

  4. observationOBS-409majorOpen

    USB Type-A receptacles: connector GND pins reach board GND only through 220R@100MHz ferrite beads, so the TVS arrays' ESD return goes through a bead

    Every USB Type-A receptacle ground contact reaches board GND only through a 220R@100MHz ferrite bead, while the ESD arrays protecting those ports clamp to board GND. Strike current must return to the cable ground through a bead that is a few hundred ohms at ESD frequencies.

    Where it is

    Connector ground contactNetBead to GNDSource
    CON12A A4NetC143A_2 (with C143A.2)L7Anetlist; sheet 7
    CON12A B4 / CON13A 4NetC144A_2L6Anetlist
    CON14A / CON15A 4, 7NetC157A_1L21Anetlist
    CON15A 13, 16NetC158A_1L22Anetlist
    B side (CON12B, CON13B and the others)NetC144B_2 and the B-side netsL7B, L6B, L21B, L22Bnetlist

    All beads are 220R@100MHz. The shells go to GND via 100 ohm || 100 nF (R75A/C145A, R87A/C161A).

    The protectors clamp to board GND: PRTR5V0U2X IC2A/B, IC10A/B, IC13A/B, IC14A/B (pin 1) and RCLAMP0524P IC15A/B, IC16A/B (pins 3/8).

    ``mermaid flowchart LR S["ESD strike<br/>D+/D- or SuperSpeed pair"] --> T["TVS array<br/>clamps to board GND"] T --> G["board GND"] G -- "220R at 100 MHz bead" --> K["connector GND contact"] K --> C["cable ground"] ``

    Why it matters

    This is exactly what the clamp needs to avoid: most of the surge appears across the bead, and the ground offset is passed to the protected lines.

    Fix: connect the connector ground contacts directly to GND (keep any filtering on the shell), or return the TVS to the connector ground.

  5. observationOBS-414majorOpen

    I350 IC18: its EEPROM port is wired to a serial FLASH (AT25F512B, IC20) that needs 3-byte addresses, while the I350 EEPROM interface speaks 8- or 16-bit-address SPI EEPROM

    The I350's EEPROM port drives a serial FLASH (IC20, AT25F512B) that needs 3-byte addresses; the I350 EEPROM protocol uses 8- or 16-bit addresses, so the configuration auto-load is unlikely to read it correctly.

    Wiring (netlist)

    IC20 pinI350 ballI350 function
    1 CSF16EE_CS_N
    6 SCKE16EE_SK
    5 SIE15EE_DI (data to EEPROM)
    2 SOF15EE_DO (data from EEPROM)

    What the documents say

    • I350: the EEPROM interface is "intended for use with a SPI (4-wire) serial EEPROM device such as an AT25040AN" (p.12); EEPROM sizes use "8 bits or 16 bits" of address (p.90).
    • I350 supported devices: EEPROM list = AT25128AN / AT25256AN / M95128 / M95256 / CAT25CS128 (Table 11-27); the AT25F512 is on the separate Flash list (Table 11-26).
    • AT25F512B: addressing "requires a total of three bytes" (p.5).

    Consequence

    A 16-bit-address read is an incomplete address to the flash, so the auto-load (PCIe IDs, MAC addresses, LAN setup) would read wrong data or fall back to EEPROM-less mode. The Flash port (FLSH_*) carries IC19, which is not fitted.

    Suggested fix

    Unless CERN has validated this on hardware, fit a Table 11-27 SPI EEPROM on the EEPROM port.

  6. observationOBS-547majorOpen

    BCP69 went end-of-life (Obsolete)

    Vendor (DigiKey) lifecycle for BCP69 (Fairchild Semiconductor's listing) changed from "Active" to "Obsolete" since this board was reviewed. Placed as T1. A sourcing/longevity risk; consider a replacement before production.

  7. observationOBS-669majorOpen

    GND copper touches the P3V3MP track on TOP at (27.54, 141.71): a short in the exported copper

    On TOP at (27.54, 141.71), a round GND land in the ground pour sits inside the clearance of the P3V3MP track and touches it, so the 3.3 V management supply from the AMC edge is shorted to GND in the copper as exported.

    What the copper shows

    The layer image of the site (TOP, 25.0-30.0 mm by 139.2-144.2 mm) shows the P3V3MP track running in its clearance channel through the GND pour. A small round GND feature (a via land or a pour island) breaks into that channel from below and touches the track edge. Everywhere else the channel keeps its clearance.

    Why it matters

    P3V3MP is the management power the carrier supplies to the MMC. If the gerbers match this export, the board shorts that rail at power-up. Please check whether the ODB++ was exported after a zone refill and a clean DRC. If the touch is real, moving the GND via or refilling the pour with its clearance removes it.

  8. concernCON-001majorOpen

    [eol:BCP69:Obsolete] BCP69 lifecycle changed from "Active" to "Obsolete" since this board was reviewed: OHWR0026 R1 AMC CPU COM6. A sourcing and longevity risk. Should this be replaced before the next build?

  9. PartLifecyclemajorOpen

    BCP69 on T1: the distributor catalogue reports "Obsolete" for Fairchild Semiconductor's BCP69

    BCP69 on T1: the distributor catalogue reports "Obsolete" for Fairchild Semiconductor's BCP69 — a sourcing/longevity risk to confirm against the MANUFACTURER before acting. This board's BOM names no manufacturer for it, so whether that is the fitted maker's product was not checked. A distributor delisting is not the same claim as the part being unavailable; check the vendor's own lifecycle/product-change notice for the status and any named successor. Re-read the source: GET /api/odb/parts/BCP69/providers (which provider said it, the maker and part number it matched, its own words, and when we asked). No approved alternate is recorded for this position.

    At T1

  10. DecapViaFanoutmajorOpen

    C268 on 'P12V0': its rail pad reaches its via over 2.47 mm of track, adding about 0.74 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads

    C268 on 'P12V0': its rail pad reaches its via over 2.47 mm of track, adding about 0.74 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads. C268.2 (rail) runs 2.47 mm along its copper to its nearest via, 1.47 mm past the 1 mm beside the pad: 0.74 nH; C268.1 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 1.60 mm apart (the pad pitch), 0.2 l ln(D/R) nH with R 0.127 mm (the track's width is not read): 0.74 nH in all. Put the vias at the pads (or in them), one per pad at least, the rail's and the ground's close together; the capacitor's own inductance as mounted is 0.68 nH (pad 0.10 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 0.11 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

    At C268

  11. CapVoltageDeratingmajorOpen

    CapVoltageDerating: 18 components×18

    18 checked by the review by Claude walker W4 (Cern session) — 18 different reasons

    At C1, C10, C11, C2, C218, C229 and 12 more

    Each finding, with its own headline
    • C1C1 sits on a 12 V rail and its voltage rating is not in the BOM

      C1: on a 12 V rail but its voltage rating is not stated in the BOM — add it so the rating can be compared to the rail at all. No datasheet is on file for this part; the BOM short-spec is the source.

    • C10C10 sits on a 12 V rail and its voltage rating is not in the BOM

      C10: on a 12 V rail but its voltage rating is not stated in the BOM — add it so the rating can be compared to the rail at all. No datasheet is on file for this part; the BOM short-spec is the source.

    • C11C11 sits on a 12 V rail and its voltage rating is not in the BOM

      C11: on a 12 V rail but its voltage rating is not stated in the BOM — add it so the rating can be compared to the rail at all. No datasheet is on file for this part; the BOM short-spec is the source.

    • C2C2 sits on a 12 V rail and its voltage rating is not in the BOM

      C2: on a 12 V rail but its voltage rating is not stated in the BOM — add it so the rating can be compared to the rail at all. No datasheet is on file for this part; the BOM short-spec is the source.

    • C218C218 sits on a 12 V rail and its voltage rating is not in the BOM

      C218: on a 12 V rail but its voltage rating is not stated in the BOM — add it so the rating can be compared to the rail at all. No datasheet is on file for this part; the BOM short-spec is the source.

    • C229C229 sits on a 12 V rail and its voltage rating is not in the BOM

      C229: on a 12 V rail but its voltage rating is not stated in the BOM — add it so the rating can be compared to the rail at all. No datasheet is on file for this part; the BOM short-spec is the source.

    • C230C230 sits on a 12 V rail and its voltage rating is not in the BOM

      C230: on a 12 V rail but its voltage rating is not stated in the BOM — add it so the rating can be compared to the rail at all. No datasheet is on file for this part; the BOM short-spec is the source.

    • C268C268 sits on a 12 V rail and its voltage rating is not in the BOM

      C268: on a 12 V rail but its voltage rating is not stated in the BOM — add it so the rating can be compared to the rail at all. No datasheet is on file for this part; the BOM short-spec is the source.

    • C3C3 sits on a 12 V rail and its voltage rating is not in the BOM

      C3: on a 12 V rail but its voltage rating is not stated in the BOM — add it so the rating can be compared to the rail at all. No datasheet is on file for this part; the BOM short-spec is the source.

    • C36C36 sits on a 12 V rail and its voltage rating is not in the BOM

      C36: on a 12 V rail but its voltage rating is not stated in the BOM — add it so the rating can be compared to the rail at all. No datasheet is on file for this part; the BOM short-spec is the source.

    • C4C4 sits on a 12 V rail and its voltage rating is not in the BOM

      C4: on a 12 V rail but its voltage rating is not stated in the BOM — add it so the rating can be compared to the rail at all. No datasheet is on file for this part; the BOM short-spec is the source.

    • C47C47 sits on a 12 V rail and its voltage rating is not in the BOM

      C47: on a 12 V rail but its voltage rating is not stated in the BOM — add it so the rating can be compared to the rail at all. No datasheet is on file for this part; the BOM short-spec is the source.

    • C48C48 sits on a 12 V rail and its voltage rating is not in the BOM

      C48: on a 12 V rail but its voltage rating is not stated in the BOM — add it so the rating can be compared to the rail at all. No datasheet is on file for this part; the BOM short-spec is the source.

    • C5C5 sits on a 12 V rail and its voltage rating is not in the BOM

      C5: on a 12 V rail but its voltage rating is not stated in the BOM — add it so the rating can be compared to the rail at all. No datasheet is on file for this part; the BOM short-spec is the source.

    • C6C6 sits on a 12 V rail and its voltage rating is not in the BOM

      C6: on a 12 V rail but its voltage rating is not stated in the BOM — add it so the rating can be compared to the rail at all. No datasheet is on file for this part; the BOM short-spec is the source.

    • C7C7 sits on a 12 V rail and its voltage rating is not in the BOM

      C7: on a 12 V rail but its voltage rating is not stated in the BOM — add it so the rating can be compared to the rail at all. No datasheet is on file for this part; the BOM short-spec is the source.

    • C8C8 sits on a 12 V rail and its voltage rating is not in the BOM

      C8: on a 12 V rail but its voltage rating is not stated in the BOM — add it so the rating can be compared to the rail at all. No datasheet is on file for this part; the BOM short-spec is the source.

    • C9C9 sits on a 12 V rail and its voltage rating is not in the BOM

      C9: on a 12 V rail but its voltage rating is not stated in the BOM — add it so the rating can be compared to the rail at all. No datasheet is on file for this part; the BOM short-spec is the source.

  12. DecapOrdermajorOpen

    DecapOrder: 2 components×2

    Checked by the review, stands · Claude walker W4 (Cern session) — Checked (W4, fleet re-walk): distances are read from placement as stated (IC18 supply pins D6, E6, G6, K14, L13, L14, M11, N12 on 'P1V0': the smallest capacitor C175 sits 2.1 mm away, behind C178 at 0.8 mm; IC18 supply pins M6, M7 on 'P3V3': the smallest capacitor C172 sits 1.7 mm away, behind C186 at 0.5 mm). Which capacitor sits nearest is a layout heuristic (Probe's starting values), not a requirement in the part's datasheet; at mm scale via and plane inductance usually dominate. Not refutable with a citation; left open for the owner.

    At IC18

    Each finding, with its own headline
    • IC18IC18 supply pins D6, E6, G6, K14, L13, L14, M11, N12 on 'P1V0': the smallest capacitor C175 sits 2.1 mm away, behind C178 at 0.8 mm

      IC18 supply pins D6, E6, G6, K14, L13, L14, M11, N12 on 'P1V0': the smallest capacitor C175 sits 2.1 mm away, behind C178 at 0.8 mm. IC18.D6: the smallest value, C175 (1 nF), is 2.1 mm from the pin and C178 (1 uF) 0.8 mm: the high-frequency part sits behind more inductance than the bulk part, which needs it least. IC18.E6: the smallest value, C175 (1 nF), is 2.3 mm from the pin and C164 (10 nF) 0.2 mm: the high-frequency part sits behind more inductance than the bulk part, which needs it least. IC18.G6: the smallest value, C180 (1 nF), is 2.5 mm from the pin and C177 (10 uF) 1.2 mm: the high-frequency part sits behind more inductance than the bulk part, which needs it least. IC18.K14: the smallest value, C182 (1 nF), is 3.2 mm from the pin and C192 (10 nF) 1.3 mm: the high-frequency part sits behind more inductance than the bulk part, which needs it least. IC18.L13: the smallest value, C182 (1 nF), is 2.8 mm from the pin and C179 (10 nF) 1.7 mm: the high-frequency part sits behind more inductance than the bulk part, which needs it least. IC18.L14: the smallest value, C182 (1 nF), is 3.6 mm from the pin and C192 (10 nF) 1.3 mm: the high-frequency part sits behind more inductance than the bulk part, which needs it least. IC18.M11: the smallest value, C166 (1 nF), is 2.4 mm from the pin and C179 (10 nF) 0.5 mm: the high-frequency part sits behind more inductance than the bulk part, which needs it least. IC18.N12: the smallest value, C166 (1 nF), is 3.8 mm from the pin and C191 (1 uF) 0.7 mm: the high-frequency part sits behind more inductance than the bulk part, which needs it least. Swap them, or bring the smallest value to the pin: it serves the fastest current and is the one the loop inductance defeats. Distances are pad centre to pin centre in the board plane. The 5 mm radius, the 10x value step and the 1 mm / 1.5x tie tolerance are Probe's starting values.

    • IC18IC18 supply pins M6, M7 on 'P3V3': the smallest capacitor C172 sits 1.7 mm away, behind C186 at 0.5 mm

      IC18 supply pins M6, M7 on 'P3V3': the smallest capacitor C172 sits 1.7 mm away, behind C186 at 0.5 mm. IC18.M6: the smallest value, C172 (1 nF), is 1.7 mm from the pin and C186 (10 nF) 0.5 mm: the high-frequency part sits behind more inductance than the bulk part, which needs it least. IC18.M7: the smallest value, C170 (1 nF), is 2.5 mm from the pin and C168 (10 nF) 0.5 mm: the high-frequency part sits behind more inductance than the bulk part, which needs it least. Swap them, or bring the smallest value to the pin: it serves the fastest current and is the one the loop inductance defeats. Distances are pad centre to pin centre in the board plane. The 5 mm radius, the 10x value step and the 1 mm / 1.5x tie tolerance are Probe's starting values.

  13. EsdProtectorPlacementmajorOpen

    EsdProtectorPlacement: 10 components×10

    Checked by the review, stands · Claude walker W4 (Cern session) — Checked (W4, fleet re-walk): the placement is measured from the copper as stated (IC12.10 on 'VGA_I2C_DAT': 3 via(s) between CON18.B96 and IC12.10; IC12.11 on 'VGA_I2C_CK': 3 via(s) between CON18.B95 and IC12.11; IC12.13 on 'VGA_HSYNC': 3 via(s) between CON18.B93 and IC12.13; IC12.15 on 'VGA_VSYNC': 3 via(s) between CON18.B94 and IC12.15; IC12.3 on 'NetC142_1': 1 via(s) between CON3.1 and IC12.3; IC12.4 on 'NetC148_1': 1 via(s) between CON3.3 and IC12.4; IC12.5 on 'NetC149_1': 1 via(s) between CON3.5 and IC12.5). Protector placement guidance (on the line, near the connector, no vias/stubs) is layout practice from protector app notes; its effect depends on the ESD event and the protected part's rating, not on file here. Left open for the owner.

    At IC12

    Each finding, with its own headline
    • IC12IC12.10 on 'VGA_I2C_DAT': 3 via(s) between CON18.B96 and IC12.10

      IC12 (CM2009) protects 'VGA_I2C_DAT' at CON18.B96. Along the copper: 115.42 mm of track from the contact, 3 via(s) before it, no other pad on the net to judge the line by; IC12 sits 69.33 mm farther from the contact than the nearest place outside CON18.

      3 via(s) between CON18.B96 and IC12.10: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC12IC12.11 on 'VGA_I2C_CK': 3 via(s) between CON18.B95 and IC12.11

      IC12 (CM2009) protects 'VGA_I2C_CK' at CON18.B95. Along the copper: 115.1 mm of track from the contact, 3 via(s) before it, no other pad on the net to judge the line by; IC12 sits 69.69 mm farther from the contact than the nearest place outside CON18.

      3 via(s) between CON18.B95 and IC12.11: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC12IC12.13 on 'VGA_HSYNC': 3 via(s) between CON18.B93 and IC12.13

      IC12 (CM2009) protects 'VGA_HSYNC' at CON18.B93. Along the copper: 114.92 mm of track from the contact, 3 via(s) before it, no other pad on the net to judge the line by; IC12 sits 70.41 mm farther from the contact than the nearest place outside CON18.

      3 via(s) between CON18.B93 and IC12.13: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC12IC12.15 on 'VGA_VSYNC': 3 via(s) between CON18.B94 and IC12.15

      IC12 (CM2009) protects 'VGA_VSYNC' at CON18.B94. Along the copper: 112.8 mm of track from the contact, 3 via(s) before it, no other pad on the net to judge the line by; IC12 sits 70.05 mm farther from the contact than the nearest place outside CON18.

      3 via(s) between CON18.B94 and IC12.15: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC12IC12.3 on 'NetC142_1': 1 via(s) between CON3.1 and IC12.3

      IC12 (CM2009) protects 'NetC142_1' at CON3.1. Along the copper: 18.9 mm of track from the contact, 1 via(s) before it, on a 1.33 mm branch off the line; the line runs 20.79 mm on to L10.2; IC12 sits 10.42 mm farther from the contact than the nearest place outside CON3.

      1 via(s) between CON3.1 and IC12.3: the strike reaches an inner layer before it is clamped. IC12.3 hangs 1.33 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. IC12 joins the line 17.57 mm from CON3.1 on a 20.79 mm run to L10.2: nearer the far end than the contact, so the surge travels most of the line before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC12IC12.3 on 'NetC142_1': IC12.3 hangs 4.42 mm off the line (limit 1 mm, default

      IC12 (CM2009) protects 'NetC142_1' at L10.2, where a strike from CON18.B89 through L10 enters the net. Along the copper: 4.5 mm of track from the contact, 0 via(s) before it, on a 4.42 mm branch off the line; the line runs 0.94 mm on to C142.1; IC12 sits at L10, within 1.39 mm of the nearest place outside it to the contact: the track to it is mostly the escape out of L10's own pins, which no placement shortens.

      No protection network is recognised at the entry: L10 (220R@100MHz) is in series at the entry, but its value is not read as an impedance, so it is not counted as a protection network.

      IC12.3 hangs 4.42 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC12IC12.4 on 'NetC148_1': 1 via(s) between CON3.3 and IC12.4

      IC12 (CM2009) protects 'NetC148_1' at CON3.3. Along the copper: 18.7 mm of track from the contact, 1 via(s) before it, on a 2.24 mm branch off the line; the line runs 19.84 mm on to C148.1; IC12 sits 10.03 mm farther from the contact than the nearest place outside CON3.

      1 via(s) between CON3.3 and IC12.4: the strike reaches an inner layer before it is clamped. IC12.4 hangs 2.24 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. IC12 joins the line 16.46 mm from CON3.3 on a 19.84 mm run to C148.1: nearer the far end than the contact, so the surge travels most of the line before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC12IC12.4 on 'NetC148_1': IC12.4 hangs 5.57 mm off the line (limit 1 mm, default

      IC12 (CM2009) protects 'NetC148_1' at L11.2, where a strike from CON18.B91 through L11 enters the net. Along the copper: 6.58 mm of track from the contact, 0 via(s) before it, on a 5.57 mm branch off the line; the line runs 1.01 mm on to C148.1; IC12 sits at L11, within 1.39 mm of the nearest place outside it to the contact: the track to it is mostly the escape out of L11's own pins, which no placement shortens.

      No protection network is recognised at the entry: L11 (220R@100MHz) is in series at the entry, but its value is not read as an impedance, so it is not counted as a protection network.

      IC12.4 hangs 5.57 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC12IC12.5 on 'NetC149_1': 1 via(s) between CON3.5 and IC12.5

      IC12 (CM2009) protects 'NetC149_1' at CON3.5. Along the copper: 18.27 mm of track from the contact, 1 via(s) before it, on a 2.97 mm branch off the line; the line runs 20.52 mm on to C149.1; IC12 sits 9.96 mm farther from the contact than the nearest place outside CON3.

      1 via(s) between CON3.5 and IC12.5: the strike reaches an inner layer before it is clamped. IC12.5 hangs 2.97 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. IC12 joins the line 15.3 mm from CON3.5 on a 20.52 mm run to C149.1: nearer the far end than the contact, so the surge travels most of the line before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC12IC12.5 on 'NetC149_1': IC12.5 hangs 8.14 mm off the line (limit 1 mm, default

      IC12 (CM2009) protects 'NetC149_1' at L12.2, where a strike from CON18.B92 through L12 enters the net. Along the copper: 9.12 mm of track from the contact, 0 via(s) before it, on a 8.14 mm branch off the line; the line runs 0.98 mm on to C149.1; IC12 sits at L12, within 1.39 mm of the nearest place outside it to the contact: the track to it is mostly the escape out of L12's own pins, which no placement shortens.

      No protection network is recognised at the entry: L12 (220R@100MHz) is in series at the entry, but its value is not read as an impedance, so it is not counted as a protection network.

      IC12.5 hangs 8.14 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

  14. EsdProtectorPlacementmajorOpen

    EsdProtectorPlacement: 57 components×57

    57 checked by the review by Claude walker W4 (Cern session) — 10 different reasons

    At IC14A, IC14B, IC15A, IC16A, IC16B, IC29 and 4 more

    Each finding, with its own headline
    • IC14AIC14A.2 on 'NetCON14A_3': IC14A joins the line 9.91 mm from CON15A.3 on a 14.45 mm run to L19A.3

      IC14A (PRTR5V0U2X) protects 'NetCON14A_3' at CON15A.3. Along the copper: 9.91 mm of track from the contact, 0 via(s) before it, the line runs through its pad (flow-through); the line runs 14.45 mm on to L19A.3; IC14A sits 6.71 mm farther from the contact than the nearest place outside CON15A.

      IC14A joins the line 9.91 mm from CON15A.3 on a 14.45 mm run to L19A.3: nearer the far end than the contact, so the surge travels most of the line before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC14AIC14A.2 on 'NetCON14A_3': IC14A joins the line 9.91 mm from CON14A.3 on a 14.45 mm run to L19A.3

      IC14A (PRTR5V0U2X) protects 'NetCON14A_3' at CON14A.3. Along the copper: 9.91 mm of track from the contact, 0 via(s) before it, the line runs through its pad (flow-through); the line runs 14.45 mm on to L19A.3; IC14A sits 6.73 mm farther from the contact than the nearest place outside CON14A.

      IC14A joins the line 9.91 mm from CON14A.3 on a 14.45 mm run to L19A.3: nearer the far end than the contact, so the surge travels most of the line before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC14AIC14A.3 on 'NetCON14A_2': IC14A joins the line 11.09 mm from CON15A.2 on a 14.4 mm run to L19A.4

      IC14A (PRTR5V0U2X) protects 'NetCON14A_2' at CON15A.2. Along the copper: 11.09 mm of track from the contact, 0 via(s) before it, the line runs through its pad (flow-through); the line runs 14.4 mm on to L19A.4; IC14A sits 6.94 mm farther from the contact than the nearest place outside CON15A.

      IC14A joins the line 11.09 mm from CON15A.2 on a 14.4 mm run to L19A.4: nearer the far end than the contact, so the surge travels most of the line before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC14AIC14A.3 on 'NetCON14A_2': IC14A joins the line 11.09 mm from CON14A.2 on a 14.4 mm run to L19A.4

      IC14A (PRTR5V0U2X) protects 'NetCON14A_2' at CON14A.2. Along the copper: 11.09 mm of track from the contact, 0 via(s) before it, the line runs through its pad (flow-through); the line runs 14.4 mm on to L19A.4; IC14A sits 6.96 mm farther from the contact than the nearest place outside CON14A.

      IC14A joins the line 11.09 mm from CON14A.2 on a 14.4 mm run to L19A.4: nearer the far end than the contact, so the surge travels most of the line before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC14BIC14B.2 on 'NetCON14B_3': IC14B joins the line 10.59 mm from CON15B.3 on a 15.27 mm run to L19B.3

      IC14B (PRTR5V0U2X) protects 'NetCON14B_3' at CON15B.3. Along the copper: 10.59 mm of track from the contact, 0 via(s) before it, the line runs through its pad (flow-through); the line runs 15.27 mm on to L19B.3; IC14B sits 6.71 mm farther from the contact than the nearest place outside CON15B.

      IC14B joins the line 10.59 mm from CON15B.3 on a 15.27 mm run to L19B.3: nearer the far end than the contact, so the surge travels most of the line before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC14BIC14B.2 on 'NetCON14B_3': IC14B joins the line 10.59 mm from CON14B.3 on a 15.27 mm run to L19B.3

      IC14B (PRTR5V0U2X) protects 'NetCON14B_3' at CON14B.3. Along the copper: 10.59 mm of track from the contact, 0 via(s) before it, the line runs through its pad (flow-through); the line runs 15.27 mm on to L19B.3; IC14B sits 6.73 mm farther from the contact than the nearest place outside CON14B.

      IC14B joins the line 10.59 mm from CON14B.3 on a 15.27 mm run to L19B.3: nearer the far end than the contact, so the surge travels most of the line before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC14BIC14B.3 on 'NetCON14B_2': IC14B joins the line 10.97 mm from CON15B.2 on a 15.06 mm run to L19B.4

      IC14B (PRTR5V0U2X) protects 'NetCON14B_2' at CON15B.2. Along the copper: 10.97 mm of track from the contact, 0 via(s) before it, the line runs through its pad (flow-through); the line runs 15.06 mm on to L19B.4; IC14B sits 6.94 mm farther from the contact than the nearest place outside CON15B.

      IC14B joins the line 10.97 mm from CON15B.2 on a 15.06 mm run to L19B.4: nearer the far end than the contact, so the surge travels most of the line before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC14BIC14B.3 on 'NetCON14B_2': IC14B joins the line 10.97 mm from CON14B.2 on a 15.06 mm run to L19B.4

      IC14B (PRTR5V0U2X) protects 'NetCON14B_2' at CON14B.2. Along the copper: 10.97 mm of track from the contact, 0 via(s) before it, the line runs through its pad (flow-through); the line runs 15.06 mm on to L19B.4; IC14B sits 6.96 mm farther from the contact than the nearest place outside CON14B.

      IC14B joins the line 10.97 mm from CON14B.2 on a 15.06 mm run to L19B.4: nearer the far end than the contact, so the surge travels most of the line before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC15AIC15A.1 on 'USB_2_RX_N': 2 via(s) between CON18.C9 and IC15A.1

      IC15A (RCLAMP0524P.TCT) protects 'USB_2_RX_N' at CON18.C9. Along the copper: 127.52 mm of track from the contact, 2 via(s) before it, no other pad on the net to judge the line by; IC15A sits 91.41 mm farther from the contact than the nearest place outside CON18.

      2 via(s) between CON18.C9 and IC15A.1: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC15AIC15A.10 on 'USB_2_RX_N': 2 via(s) between CON18.C9 and IC15A.10

      IC15A (RCLAMP0524P.TCT) protects 'USB_2_RX_N' at CON18.C9. Along the copper: 126.71 mm of track from the contact, 2 via(s) before it, no other pad on the net to judge the line by; IC15A sits 91.41 mm farther from the contact than the nearest place outside CON18.

      2 via(s) between CON18.C9 and IC15A.10: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC15AIC15A.2 on 'USB_2_RX_P': 2 via(s) between CON18.C10 and IC15A.2

      IC15A (RCLAMP0524P.TCT) protects 'USB_2_RX_P' at CON18.C10. Along the copper: 127.51 mm of track from the contact, 2 via(s) before it, no other pad on the net to judge the line by; IC15A sits 91.2 mm farther from the contact than the nearest place outside CON18.

      2 via(s) between CON18.C10 and IC15A.2: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC15AIC15A.9 on 'USB_2_RX_P': 2 via(s) between CON18.C10 and IC15A.9

      IC15A (RCLAMP0524P.TCT) protects 'USB_2_RX_P' at CON18.C10. Along the copper: 126.71 mm of track from the contact, 2 via(s) before it, no other pad on the net to judge the line by; IC15A sits 91.2 mm farther from the contact than the nearest place outside CON18.

      2 via(s) between CON18.C10 and IC15A.9: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC16AIC16A.1 on 'DSB_D_RXA_N': 1 via(s) between CON15A.5 and IC16A.1

      IC16A (RCLAMP0524P.TCT) protects 'DSB_D_RXA_N' at CON15A.5. Along the copper: 11.3 mm of track from the contact, 1 via(s) before it, no other pad on the net to judge the line by; IC16A sits 5.9 mm farther from the contact than the nearest place outside CON15A.

      1 via(s) between CON15A.5 and IC16A.1: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC16AIC16A.1 on 'DSB_D_RXA_N': 1 via(s) between CON14A.5 and IC16A.1

      IC16A (RCLAMP0524P.TCT) protects 'DSB_D_RXA_N' at CON14A.5. Along the copper: 11.3 mm of track from the contact, 1 via(s) before it, no other pad on the net to judge the line by; IC16A sits 5.92 mm farther from the contact than the nearest place outside CON14A.

      1 via(s) between CON14A.5 and IC16A.1: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC16AIC16A.10 on 'DSB_D_RXA_N': 1 via(s) between CON15A.5 and IC16A.10

      IC16A (RCLAMP0524P.TCT) protects 'DSB_D_RXA_N' at CON15A.5. Along the copper: 12.11 mm of track from the contact, 1 via(s) before it, no other pad on the net to judge the line by; IC16A sits 5.9 mm farther from the contact than the nearest place outside CON15A.

      1 via(s) between CON15A.5 and IC16A.10: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC16AIC16A.10 on 'DSB_D_RXA_N': 1 via(s) between CON14A.5 and IC16A.10

      IC16A (RCLAMP0524P.TCT) protects 'DSB_D_RXA_N' at CON14A.5. Along the copper: 12.11 mm of track from the contact, 1 via(s) before it, no other pad on the net to judge the line by; IC16A sits 5.92 mm farther from the contact than the nearest place outside CON14A.

      1 via(s) between CON14A.5 and IC16A.10: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC16AIC16A.2 on 'DSB_D_RXA_P': 1 via(s) between CON15A.6 and IC16A.2

      IC16A (RCLAMP0524P.TCT) protects 'DSB_D_RXA_P' at CON15A.6. Along the copper: 11.44 mm of track from the contact, 1 via(s) before it, no other pad on the net to judge the line by; IC16A sits 4.52 mm farther from the contact than the nearest place outside CON15A.

      1 via(s) between CON15A.6 and IC16A.2: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC16AIC16A.2 on 'DSB_D_RXA_P': 1 via(s) between CON14A.6 and IC16A.2

      IC16A (RCLAMP0524P.TCT) protects 'DSB_D_RXA_P' at CON14A.6. Along the copper: 11.44 mm of track from the contact, 1 via(s) before it, no other pad on the net to judge the line by; IC16A sits 4.54 mm farther from the contact than the nearest place outside CON14A.

      1 via(s) between CON14A.6 and IC16A.2: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC16AIC16A.4 on 'DSB_D_TXA_N': 1 via(s) between CON15A.8 and IC16A.4

      IC16A (RCLAMP0524P.TCT) protects 'DSB_D_TXA_N' at CON15A.8. Along the copper: 6.56 mm of track from the contact, 1 via(s) before it, no other pad on the net to judge the line by; IC16A sits 2.98 mm farther from the contact than the nearest place outside CON15A.

      1 via(s) between CON15A.8 and IC16A.4: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC16AIC16A.4 on 'DSB_D_TXA_N': 1 via(s) between CON14A.8 and IC16A.4

      IC16A (RCLAMP0524P.TCT) protects 'DSB_D_TXA_N' at CON14A.8. Along the copper: 6.56 mm of track from the contact, 1 via(s) before it, no other pad on the net to judge the line by; IC16A sits 3 mm farther from the contact than the nearest place outside CON14A.

      1 via(s) between CON14A.8 and IC16A.4: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC16AIC16A.5 on 'DSB_D_TXA_P': 1 via(s) between CON15A.9 and IC16A.5

      IC16A (RCLAMP0524P.TCT) protects 'DSB_D_TXA_P' at CON15A.9. Along the copper: 7 mm of track from the contact, 1 via(s) before it, no other pad on the net to judge the line by; IC16A sits 2.96 mm farther from the contact than the nearest place outside CON15A.

      1 via(s) between CON15A.9 and IC16A.5: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC16AIC16A.5 on 'DSB_D_TXA_P': 1 via(s) between CON14A.9 and IC16A.5

      IC16A (RCLAMP0524P.TCT) protects 'DSB_D_TXA_P' at CON14A.9. Along the copper: 7 mm of track from the contact, 1 via(s) before it, no other pad on the net to judge the line by; IC16A sits 2.98 mm farther from the contact than the nearest place outside CON14A.

      1 via(s) between CON14A.9 and IC16A.5: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC16AIC16A.6 on 'DSB_D_TXA_P': 1 via(s) between CON15A.9 and IC16A.6

      IC16A (RCLAMP0524P.TCT) protects 'DSB_D_TXA_P' at CON15A.9. Along the copper: 7.82 mm of track from the contact, 1 via(s) before it, no other pad on the net to judge the line by; IC16A sits 2.96 mm farther from the contact than the nearest place outside CON15A.

      1 via(s) between CON15A.9 and IC16A.6: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC16AIC16A.6 on 'DSB_D_TXA_P': 1 via(s) between CON14A.9 and IC16A.6

      IC16A (RCLAMP0524P.TCT) protects 'DSB_D_TXA_P' at CON14A.9. Along the copper: 7.82 mm of track from the contact, 1 via(s) before it, no other pad on the net to judge the line by; IC16A sits 2.98 mm farther from the contact than the nearest place outside CON14A.

      1 via(s) between CON14A.9 and IC16A.6: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC16AIC16A.7 on 'DSB_D_TXA_N': 1 via(s) between CON15A.8 and IC16A.7

      IC16A (RCLAMP0524P.TCT) protects 'DSB_D_TXA_N' at CON15A.8. Along the copper: 7.36 mm of track from the contact, 1 via(s) before it, no other pad on the net to judge the line by; IC16A sits 2.98 mm farther from the contact than the nearest place outside CON15A.

      1 via(s) between CON15A.8 and IC16A.7: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC16AIC16A.7 on 'DSB_D_TXA_N': 1 via(s) between CON14A.8 and IC16A.7

      IC16A (RCLAMP0524P.TCT) protects 'DSB_D_TXA_N' at CON14A.8. Along the copper: 7.36 mm of track from the contact, 1 via(s) before it, no other pad on the net to judge the line by; IC16A sits 3 mm farther from the contact than the nearest place outside CON14A.

      1 via(s) between CON14A.8 and IC16A.7: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC16AIC16A.9 on 'DSB_D_RXA_P': 1 via(s) between CON15A.6 and IC16A.9

      IC16A (RCLAMP0524P.TCT) protects 'DSB_D_RXA_P' at CON15A.6. Along the copper: 12.25 mm of track from the contact, 1 via(s) before it, no other pad on the net to judge the line by; IC16A sits 4.52 mm farther from the contact than the nearest place outside CON15A.

      1 via(s) between CON15A.6 and IC16A.9: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC16AIC16A.9 on 'DSB_D_RXA_P': 1 via(s) between CON14A.6 and IC16A.9

      IC16A (RCLAMP0524P.TCT) protects 'DSB_D_RXA_P' at CON14A.6. Along the copper: 12.25 mm of track from the contact, 1 via(s) before it, no other pad on the net to judge the line by; IC16A sits 4.54 mm farther from the contact than the nearest place outside CON14A.

      1 via(s) between CON14A.6 and IC16A.9: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC16BIC16B.1 on 'DSB_D_RXB_N': 1 via(s) between CON15B.5 and IC16B.1

      IC16B (RCLAMP0524P.TCT) protects 'DSB_D_RXB_N' at CON15B.5. Along the copper: 6.98 mm of track from the contact, 1 via(s) before it, no other pad on the net to judge the line by; IC16B sits 2.96 mm farther from the contact than the nearest place outside CON15B.

      1 via(s) between CON15B.5 and IC16B.1: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC16BIC16B.1 on 'DSB_D_RXB_N': 1 via(s) between CON14B.5 and IC16B.1

      IC16B (RCLAMP0524P.TCT) protects 'DSB_D_RXB_N' at CON14B.5. Along the copper: 6.98 mm of track from the contact, 1 via(s) before it, no other pad on the net to judge the line by; IC16B sits 2.98 mm farther from the contact than the nearest place outside CON14B.

      1 via(s) between CON14B.5 and IC16B.1: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC16BIC16B.10 on 'DSB_D_RXB_N': 1 via(s) between CON15B.5 and IC16B.10

      IC16B (RCLAMP0524P.TCT) protects 'DSB_D_RXB_N' at CON15B.5. Along the copper: 7.78 mm of track from the contact, 1 via(s) before it, no other pad on the net to judge the line by; IC16B sits 2.96 mm farther from the contact than the nearest place outside CON15B.

      1 via(s) between CON15B.5 and IC16B.10: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC16BIC16B.10 on 'DSB_D_RXB_N': 1 via(s) between CON14B.5 and IC16B.10

      IC16B (RCLAMP0524P.TCT) protects 'DSB_D_RXB_N' at CON14B.5. Along the copper: 7.78 mm of track from the contact, 1 via(s) before it, no other pad on the net to judge the line by; IC16B sits 2.98 mm farther from the contact than the nearest place outside CON14B.

      1 via(s) between CON14B.5 and IC16B.10: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC16BIC16B.2 on 'DSB_D_RXB_P': 1 via(s) between CON15B.6 and IC16B.2

      IC16B (RCLAMP0524P.TCT) protects 'DSB_D_RXB_P' at CON15B.6. Along the copper: 6.47 mm of track from the contact, 1 via(s) before it, no other pad on the net to judge the line by; IC16B sits 2.98 mm farther from the contact than the nearest place outside CON15B.

      1 via(s) between CON15B.6 and IC16B.2: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC16BIC16B.2 on 'DSB_D_RXB_P': 1 via(s) between CON14B.6 and IC16B.2

      IC16B (RCLAMP0524P.TCT) protects 'DSB_D_RXB_P' at CON14B.6. Along the copper: 6.47 mm of track from the contact, 1 via(s) before it, no other pad on the net to judge the line by; IC16B sits 3 mm farther from the contact than the nearest place outside CON14B.

      1 via(s) between CON14B.6 and IC16B.2: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC16BIC16B.5 on 'DSB_D_TXB_P': 1 via(s) between CON15B.9 and IC16B.5

      IC16B (RCLAMP0524P.TCT) protects 'DSB_D_TXB_P' at CON15B.9. Along the copper: 11.07 mm of track from the contact, 1 via(s) before it, no other pad on the net to judge the line by; IC16B sits 5.89 mm farther from the contact than the nearest place outside CON15B.

      1 via(s) between CON15B.9 and IC16B.5: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC16BIC16B.5 on 'DSB_D_TXB_P': 1 via(s) between CON14B.9 and IC16B.5

      IC16B (RCLAMP0524P.TCT) protects 'DSB_D_TXB_P' at CON14B.9. Along the copper: 11.07 mm of track from the contact, 1 via(s) before it, no other pad on the net to judge the line by; IC16B sits 5.91 mm farther from the contact than the nearest place outside CON14B.

      1 via(s) between CON14B.9 and IC16B.5: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC16BIC16B.6 on 'DSB_D_TXB_P': 1 via(s) between CON15B.9 and IC16B.6

      IC16B (RCLAMP0524P.TCT) protects 'DSB_D_TXB_P' at CON15B.9. Along the copper: 11.88 mm of track from the contact, 1 via(s) before it, no other pad on the net to judge the line by; IC16B sits 5.89 mm farther from the contact than the nearest place outside CON15B.

      1 via(s) between CON15B.9 and IC16B.6: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC16BIC16B.6 on 'DSB_D_TXB_P': 1 via(s) between CON14B.9 and IC16B.6

      IC16B (RCLAMP0524P.TCT) protects 'DSB_D_TXB_P' at CON14B.9. Along the copper: 11.88 mm of track from the contact, 1 via(s) before it, no other pad on the net to judge the line by; IC16B sits 5.91 mm farther from the contact than the nearest place outside CON14B.

      1 via(s) between CON14B.9 and IC16B.6: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC16BIC16B.9 on 'DSB_D_RXB_P': 1 via(s) between CON15B.6 and IC16B.9

      IC16B (RCLAMP0524P.TCT) protects 'DSB_D_RXB_P' at CON15B.6. Along the copper: 7.27 mm of track from the contact, 1 via(s) before it, no other pad on the net to judge the line by; IC16B sits 2.98 mm farther from the contact than the nearest place outside CON15B.

      1 via(s) between CON15B.6 and IC16B.9: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC16BIC16B.9 on 'DSB_D_RXB_P': 1 via(s) between CON14B.6 and IC16B.9

      IC16B (RCLAMP0524P.TCT) protects 'DSB_D_RXB_P' at CON14B.6. Along the copper: 7.27 mm of track from the contact, 1 via(s) before it, no other pad on the net to judge the line by; IC16B sits 3 mm farther from the contact than the nearest place outside CON14B.

      1 via(s) between CON14B.6 and IC16B.9: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC29IC29.4 on 'HPD': IC29.4 hangs 1.02 mm off the line (limit 1 mm, default

      IC29 (RCLAMP0524P.TCT) protects 'HPD' at CON8.2. Along the copper: 6.44 mm of track from the contact, 0 via(s) before it, on a 1.02 mm branch off the line; the line runs 9.45 mm on to R33.2; IC29 sits 2.35 mm farther from the contact than the nearest place outside CON8.

      IC29.4 hangs 1.02 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. IC29 joins the line 5.42 mm from CON8.2 on a 9.45 mm run to R33.2: nearer the far end than the contact, so the surge travels most of the line before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC29IC29.5 on 'HPD': IC29 joins the line 6.41 mm from CON8.2 on a 9.45 mm run to R33.2

      IC29 (RCLAMP0524P.TCT) protects 'HPD' at CON8.2. Along the copper: 6.41 mm of track from the contact, 0 via(s) before it, the line runs through its pad (flow-through); the line runs 9.45 mm on to R33.2; IC29 sits 2.35 mm farther from the contact than the nearest place outside CON8.

      IC29 joins the line 6.41 mm from CON8.2 on a 9.45 mm run to R33.2: nearer the far end than the contact, so the surge travels most of the line before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC29IC29.6 on 'HPD': IC29 joins the line 5.54 mm from CON8.2 on a 9.45 mm run to R33.2

      IC29 (RCLAMP0524P.TCT) protects 'HPD' at CON8.2. Along the copper: 5.54 mm of track from the contact, 0 via(s) before it, the line runs through its pad (flow-through); the line runs 9.45 mm on to R33.2; IC29 sits 2.35 mm farther from the contact than the nearest place outside CON8.

      IC29 joins the line 5.54 mm from CON8.2 on a 9.45 mm run to R33.2: nearer the far end than the contact, so the surge travels most of the line before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC29IC29.7 on 'HPD': IC29 joins the line 4.76 mm from CON8.2 on a 9.45 mm run to R33.2

      IC29 (RCLAMP0524P.TCT) protects 'HPD' at CON8.2. Along the copper: 5.57 mm of track from the contact, 0 via(s) before it, on a 0.81 mm branch off the line; the line runs 9.45 mm on to R33.2; IC29 sits 2.35 mm farther from the contact than the nearest place outside CON8.

      IC29 joins the line 4.76 mm from CON8.2 on a 9.45 mm run to R33.2: nearer the far end than the contact, so the surge travels most of the line before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC2AIC2A.2 on 'USB_6_N': 2 via(s) between CON18.A36 and IC2A.2

      IC2A (PRTR5V0U2X) protects 'USB_6_N' at CON18.A36. Along the copper: 150.49 mm of track from the contact, 2 via(s) before it, the line runs through its pad (flow-through); the line runs 152.24 mm on to L2A.4; IC2A sits 120.63 mm farther from the contact than the nearest place outside CON18.

      2 via(s) between CON18.A36 and IC2A.2: the strike reaches an inner layer before it is clamped. IC2A joins the line 150.49 mm from CON18.A36 on a 152.24 mm run to L2A.4: nearer the far end than the contact, so the surge travels most of the line before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC2AIC2A.3 on 'USB_6_P': 2 via(s) between CON18.A37 and IC2A.3

      IC2A (PRTR5V0U2X) protects 'USB_6_P' at CON18.A37. Along the copper: 150.45 mm of track from the contact, 2 via(s) before it, the line runs through its pad (flow-through); the line runs 152.24 mm on to L2A.3; IC2A sits 120.31 mm farther from the contact than the nearest place outside CON18.

      2 via(s) between CON18.A37 and IC2A.3: the strike reaches an inner layer before it is clamped. IC2A joins the line 150.45 mm from CON18.A37 on a 152.24 mm run to L2A.3: nearer the far end than the contact, so the surge travels most of the line before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC4IC4.4 on 'SDA_L': 2 via(s) between CON1.71 and IC4.4

      IC4 (BZA462A) protects 'SDA_L' at CON1.71. Along the copper: 206.72 mm of track from the contact, 2 via(s) before it, the line runs through its pad (flow-through); the line runs 208.29 mm on to R47.2; IC4 sits 109.43 mm farther from the contact than the nearest place outside CON1.

      2 via(s) between CON1.71 and IC4.4: the strike reaches an inner layer before it is clamped. IC4 joins the line 206.72 mm from CON1.71 on a 208.29 mm run to R47.2: nearer the far end than the contact, so the surge travels most of the line before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC4IC4.6 on 'SCL_L': 2 via(s) between CON1.56 and IC4.6

      IC4 (BZA462A) protects 'SCL_L' at CON1.56. Along the copper: 173.65 mm of track from the contact, 2 via(s) before it, the line runs through its pad (flow-through); the line runs 174.79 mm on to R169.2; IC4 sits 108.33 mm farther from the contact than the nearest place outside CON1.

      2 via(s) between CON1.56 and IC4.6: the strike reaches an inner layer before it is clamped. IC4 joins the line 173.65 mm from CON1.56 on a 174.79 mm run to R169.2: nearer the far end than the contact, so the surge travels most of the line before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC5IC5.1 on 'GA2': 2 via(s) between CON1.26 and IC5.1

      IC5 (BZA462A) protects 'GA2' at CON1.26. Along the copper: 145.41 mm of track from the contact, 2 via(s) before it, on a 4.55 mm branch off the line; the line runs 141.35 mm on to R22.1; IC5 sits 115.22 mm farther from the contact than the nearest place outside CON1.

      2 via(s) between CON1.26 and IC5.1: the strike reaches an inner layer before it is clamped. IC5.1 hangs 4.55 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. IC5 joins the line 140.86 mm from CON1.26 on a 141.35 mm run to R22.1: nearer the far end than the contact, so the surge travels most of the line before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC5IC5.3 on 'GA1': 2 via(s) between CON1.17 and IC5.3

      IC5 (BZA462A) protects 'GA1' at CON1.17. Along the copper: 145.98 mm of track from the contact, 2 via(s) before it, on a 3.78 mm branch off the line; the line runs 142.7 mm on to R21.1; IC5 sits 117.57 mm farther from the contact than the nearest place outside CON1.

      2 via(s) between CON1.17 and IC5.3: the strike reaches an inner layer before it is clamped. IC5.3 hangs 3.78 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. IC5 joins the line 142.2 mm from CON1.17 on a 142.7 mm run to R21.1: nearer the far end than the contact, so the surge travels most of the line before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC5IC5.4 on 'GA0': 1 via(s) between CON1.5 and IC5.4

      IC5 (BZA462A) protects 'GA0' at CON1.5. Along the copper: 150.27 mm of track from the contact, 1 via(s) before it, on a 6.48 mm branch off the line; the line runs 144.28 mm on to R137.1; IC5 sits 122.79 mm farther from the contact than the nearest place outside CON1.

      1 via(s) between CON1.5 and IC5.4: the strike reaches an inner layer before it is clamped. IC5.4 hangs 6.48 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. IC5 joins the line 143.79 mm from CON1.5 on a 144.28 mm run to R137.1: nearer the far end than the contact, so the surge travels most of the line before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC8IC8.1 on 'SIM_DAT': 1 via(s) between CON9.10 and IC8.1

      IC8 (BZA462A) protects 'SIM_DAT' at CON9.10. Along the copper: 12.54 mm of track from the contact, 1 via(s) before it, the line runs through its pad (flow-through); the line runs 14.06 mm on to R210.1; IC8 sits 8.28 mm farther from the contact than the nearest place outside CON9.

      1 via(s) between CON9.10 and IC8.1: the strike reaches an inner layer before it is clamped. IC8 joins the line 12.54 mm from CON9.10 on a 14.06 mm run to R210.1: nearer the far end than the contact, so the surge travels most of the line before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC8IC8.1 on 'SIM_DAT': IC8.1 hangs 1.48 mm off the line (limit 1 mm, default

      IC8 (BZA462A) protects 'SIM_DAT' at CON11.C7. Along the copper: 8.1 mm of track from the contact, 0 via(s) before it, on a 1.48 mm branch off the line; the line runs 6.82 mm on to R210.1; IC8 sits 3.21 mm farther from the contact than the nearest place outside CON11.

      IC8.1 hangs 1.48 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. IC8 joins the line 6.62 mm from CON11.C7 on a 6.82 mm run to R210.1: nearer the far end than the contact, so the surge travels most of the line before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC8IC8.3 on 'SIM_CLK': 1 via(s) between CON9.12 and IC8.3

      IC8 (BZA462A) protects 'SIM_CLK' at CON9.12. Along the copper: 13.67 mm of track from the contact, 1 via(s) before it, no other pad on the net to judge the line by; IC8 sits 7.85 mm farther from the contact than the nearest place outside CON9.

      1 via(s) between CON9.12 and IC8.3: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC8IC8.4 on 'SIM_RST': 1 via(s) between CON9.14 and IC8.4

      IC8 (BZA462A) protects 'SIM_RST' at CON9.14. Along the copper: 12.53 mm of track from the contact, 1 via(s) before it, no other pad on the net to judge the line by; IC8 sits 7.49 mm farther from the contact than the nearest place outside CON9.

      1 via(s) between CON9.14 and IC8.4: the strike reaches an inner layer before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC8IC8.6 on 'SIM_VCC': 1 via(s) between CON9.8 and IC8.6

      IC8 (BZA462A) protects 'SIM_VCC' at CON9.8. Along the copper: 12.1 mm of track from the contact, 1 via(s) before it, on a 1.6 mm branch off the line; the line runs 10.7 mm on to C322.1; IC8 sits 8.76 mm farther from the contact than the nearest place outside CON9.

      1 via(s) between CON9.8 and IC8.6: the strike reaches an inner layer before it is clamped. IC8.6 hangs 1.6 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. IC8 joins the line 10.5 mm from CON9.8 on a 10.7 mm run to C322.1: nearer the far end than the contact, so the surge travels most of the line before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

    • IC8IC8.6 on 'SIM_VCC': IC8.6 hangs 1.6 mm off the line (limit 1 mm, default

      IC8 (BZA462A) protects 'SIM_VCC' at CON11.C1. Along the copper: 8.03 mm of track from the contact, 0 via(s) before it, on a 1.6 mm branch off the line; the line runs 6.63 mm on to C322.1; IC8 sits 3.55 mm farther from the contact than the nearest place outside CON11.

      IC8.6 hangs 1.6 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch. IC8 joins the line 6.43 mm from CON11.C1 on a 6.63 mm run to C322.1: nearer the far end than the contact, so the surge travels most of the line before it is clamped.

      Measured on the copper the ODB states: tracks, the pads they land on, and the netlist's vias. Not a straight line between centroids.

  15. FloatingInputmajorOpen

    FloatingInput: 3 nets×3

    e.g. “IC18.C15 on 'NetIC18_C15' has no driver and no pull” · 3 different statements

    At NetIC18_C15, NetIC18_N13, NetIC18_P14

    Each finding, with its own headline
    • NetIC18_C15IC18.C15 on 'NetIC18_C15' has no driver and no pull

      Net 'NetIC18_C15': input(s) IC18.C15 with no driver and no pull — floating input (undefined level); add a driver or a pull resistor.

    • NetIC18_N13IC18.N13 on 'NetIC18_N13' has no driver and no pull

      Net 'NetIC18_N13': input(s) IC18.N13 with no driver and no pull — floating input (undefined level); add a driver or a pull resistor.

    • NetIC18_P14IC18.P14 on 'NetIC18_P14' has no driver and no pull

      Net 'NetIC18_P14': input(s) IC18.P14 with no driver and no pull — floating input (undefined level); add a driver or a pull resistor.

  16. FloatingInputmajorOpen

    IC18.G15 on 'NetIC18_G15' has no driver and no pull

    Net 'NetIC18_G15': input(s) IC18.G15 with no driver and no pull — floating input (undefined level); add a driver or a pull resistor.

    At NetIC18_G15

  17. SinglePointNetmajorOpen

    IC34.2 (XSD) is an IC input left unconnected

    Pin IC34.2 (XSD) is an IC INPUT left UNCONNECTED (on the no-connect bucket). Marked no-connect by the designer, but an input normally needs a defined level - confirm it is truly meant to float. If the datasheet defines this input left open (an internal pull, "read as low when left floating", or a tri-level input whose open state is one of its settings), file it on the pin as if_unused (pull_up, pull_down or may_float) with submit_pin_behavior, citing the page, and this finding clears.

    At IC34.2

  18. PartLifecyclemajorOpen

    PartLifecycle: 3 part numbers×3

    2 Obsolete, 1 Not For New Designs · on 6 placements

    At IC11, IC21A, IC24

    Each finding, with its own headline
    • IC11PI3VDP411LSZBE on IC11: the distributor catalogue reports "Obsolete" for Diodes Incorporated's PI3VDP411LSZBE

      PI3VDP411LSZBE on IC11: the distributor catalogue reports "Obsolete" for Diodes Incorporated's PI3VDP411LSZBE — a sourcing/longevity risk to confirm against the MANUFACTURER before acting. This board's BOM names no manufacturer for it, so whether that is the fitted maker's product was not checked. A distributor delisting is not the same claim as the part being unavailable; check the vendor's own lifecycle/product-change notice for the status and any named successor. Re-read the source: GET /api/odb/parts/PI3VDP411LSZBE/providers (which provider said it, the maker and part number it matched, its own words, and when we asked). THE LAST BUY DATE HAS PASSED (2018-10-12, 2,956 day(s) ago), so this is a substitution rather than a buy. The distributor reports NONE left. No approved alternate is recorded for this position.

    • IC21ACP2102-GM on 2 placements (IC21A, IC21B): the distributor catalogue reports "Not For New Designs" for Silicon Labs's CP2102-GM

      CP2102-GM on 2 placements (IC21A, IC21B): the distributor catalogue reports "Not For New Designs" for Silicon Labs's CP2102-GM — a sourcing/longevity risk to confirm against the MANUFACTURER before acting. This board's BOM names no manufacturer for it, so whether that is the fitted maker's product was not checked. A distributor delisting is not the same claim as the part being unavailable; check the vendor's own lifecycle/product-change notice for the status and any named successor. Re-read the source: GET /api/odb/parts/CP2102-GM/providers (which provider said it, the maker and part number it matched, its own words, and when we asked). No approved alternate is recorded for this position.

    • IC24LM75AIM/NOPB on 3 placements (IC24, IC25, IC28): the distributor catalogue reports "Obsolete" for Texas Instruments's LM75AIM/NOPB

      LM75AIM/NOPB on 3 placements (IC24, IC25, IC28): the distributor catalogue reports "Obsolete" for Texas Instruments's LM75AIM/NOPB — a sourcing/longevity risk to confirm against the MANUFACTURER before acting. This board's BOM names no manufacturer for it, so whether that is the fitted maker's product was not checked. A distributor delisting is not the same claim as the part being unavailable; check the vendor's own lifecycle/product-change notice for the status and any named successor. Re-read the source: GET /api/odb/parts/LM75AIM/NOPB/providers (which provider said it, the maker and part number it matched, its own words, and when we asked). THE LAST BUY DATE HAS PASSED (2024-02-09, 1,010 day(s) ago), so this is a substitution rather than a buy. The distributor reports NONE left. No approved alternate is recorded for this position.

  19. PartLifecyclemajorOpen

    PartLifecycle: 3 part numbers×3

    3 Obsolete · on 10 placements

    At IC15A, IC17, IC20

    Each finding, with its own headline
    • IC15ARCLAMP0524P.TCT on 7 placements (IC15A, IC15B, IC16A, IC16B, IC29, IC30, IC31): the distributor catalogue reports "Obsolete" for Semtech Corporation's RCLAMP0524P.TCT

      RCLAMP0524P.TCT on 7 placements (IC15A, IC15B, IC16A, IC16B, IC29, IC30, IC31): the distributor catalogue reports "Obsolete" for Semtech Corporation's RCLAMP0524P.TCT — a sourcing/longevity risk to confirm against the MANUFACTURER before acting. This board's BOM names no manufacturer for it, so whether that is the fitted maker's product was not checked. A distributor delisting is not the same claim as the part being unavailable; check the vendor's own lifecycle/product-change notice for the status and any named successor. Re-read the source: GET /api/odb/parts/RCLAMP0524P.TCT/providers (which provider said it, the maker and part number it matched, its own words, and when we asked). THE LAST BUY DATE HAS PASSED (2022-09-15, 1,522 day(s) ago), so this is a substitution rather than a buy. The distributor reports NONE left. No approved alternate is recorded for this position.

    • IC17NCP3170ADR2G on 2 placements (IC17, IC6): the distributor catalogue reports "Obsolete" for onsemi's NCP3170ADR2G

      NCP3170ADR2G on 2 placements (IC17, IC6): the distributor catalogue reports "Obsolete" for onsemi's NCP3170ADR2G — a sourcing/longevity risk to confirm against the MANUFACTURER before acting. This board's BOM names no manufacturer for it, so whether that is the fitted maker's product was not checked. A distributor delisting is not the same claim as the part being unavailable; check the vendor's own lifecycle/product-change notice for the status and any named successor. Re-read the source: GET /api/odb/parts/NCP3170ADR2G/providers (which provider said it, the maker and part number it matched, its own words, and when we asked). THE LAST BUY DATE HAS PASSED (2022-04-01, 1,689 day(s) ago), so this is a substitution rather than a buy. The distributor reports NONE left. No approved alternate is recorded for this position.

    • IC20AT25F512B-SSH-B on IC20: the distributor catalogue reports "Obsolete" for Microchip Technology's AT25F512B-SSH-B

      AT25F512B-SSH-B on IC20: the distributor catalogue reports "Obsolete" for Microchip Technology's AT25F512B-SSH-B — a sourcing/longevity risk to confirm against the MANUFACTURER before acting. This board's BOM names no manufacturer for it, so whether that is the fitted maker's product was not checked. A distributor delisting is not the same claim as the part being unavailable; check the vendor's own lifecycle/product-change notice for the status and any named successor. Re-read the source: GET /api/odb/parts/AT25F512B-SSH-B/providers (which provider said it, the maker and part number it matched, its own words, and when we asked). No approved alternate is recorded for this position.

  20. ReferencePlaneDiscontinuitymajorOpen

    ReferencePlaneDiscontinuity: 14 boards×14

    14 checked by the review by Claude walker W4 (Cern session) — 14 different reasons

    At along@VSUP:GND|P3V3_HDMI, along@VSUP:P3V3|P5V0, merged:35.25,110.62|39.79,113.01, refchange:+3.3V_PCI_CLK|GND, refchange:GND|P5V0, split@VSUP:+3.3V_PCI_CLK|GND and 8 more

    Each finding, with its own headline
    • along@VSUP:GND|P3V3_HDMI2 nets run ALONG the split between the GND and P3V3_HDMI planes on VSUP at 2 places, the longest 3 mm; the impedance rises from 43 ohm to 48 ohm there at worst, 5.8 % of each edge reflected (fastest: (S)ATA_ACT# at 100 ps 10-90 %, ASSUMED)

      On VSUP the GND and P3V3_HDMI planes part, and 2 nets run down the slot between them at 2 place(s), rather than across it. This is not a crossing: the return still follows the track, in the plane on its other side and in the slot's edges, so it does not detour. What changes is the track's own impedance. With the plane gone from under it on this side for that length, its field reaches further, to the slot's edges and to the next plane beyond, so its capacitance falls and its impedance rises; every edge travelling down it is partly reflected where it enters the stretch and again where it leaves, by (Z2 - Z1)/(Z2 + Z1). The longer the stretch against the edge's rise, the more of the edge sees the full step. A crossing is generally the worse fault; a mismatch is not free. Over solid plane each track is 43 ohm to 56 ohm; along the slot 48 ohm to 58 ohm, reflecting up to 5.8 % of each edge (a method-of-moments field solve of the cross-section, one dielectric; were the slot's edges to carry none of the return, up to 69 ohm). At 1 of the 2 place(s) the rise is within 10 %, the tolerance controlled impedance is commonly built to (the stackup states none); the rest exceed it or cannot be said, so the finding is a warning. One decision covers the split line's slot: whether these tracks may run down it, or should be moved over solid plane.

      • 'HDMI_HPD' on BTM at (11.19, 52.27), 3.45 mm, running ALONG the split for 3 mm, not across it, 43 ohm over solid plane, 48 ohm along it: 5.8 % of each edge reflected; other side: none: the signal layer is outermost
      • '(S)ATA_ACT#' on L2 at (9.81, 52.26), 0.66 mm, running ALONG the split for 0.29 mm, not across it, 56 ohm over solid plane, 58 ohm along it: 1.7 % of each edge reflected; other side: GND on L1, 0.82 mm from the track against 0.2 mm to VSUP: 80% of the return on VSUP

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=along%40VSUP%3AGND%7CP3V3_HDMI serves each with its own layer_image region; all of them lie in x 8.52..13.92, y 51.15..53.27 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • along@VSUP:P3V3|P5V0'NetC148_1' runs ALONG the split between the P3V3 and P5V0 planes on VSUP at 2 places, the longest 6.79 mm; the impedance rises from 43 ohm to 47 ohm there at worst, 4.9 % of each edge reflected (fastest: NetC148_1 at 100 ps 10-90 %, ASSUMED)

      On VSUP the P3V3 and P5V0 planes part, and 'NetC148_1' runs down the slot between them at 2 place(s), rather than across it. This is not a crossing: the return still follows the track, in the plane on its other side and in the slot's edges, so it does not detour. What changes is the track's own impedance. With the plane gone from under it on this side for that length, its field reaches further, to the slot's edges and to the next plane beyond, so its capacitance falls and its impedance rises; every edge travelling down it is partly reflected where it enters the stretch and again where it leaves, by (Z2 - Z1)/(Z2 + Z1). The longer the stretch against the edge's rise, the more of the edge sees the full step. A crossing is generally the worse fault; a mismatch is not free. Over solid plane each track is 43 ohm; along the slot 47 ohm, reflecting up to 4.9 % of each edge (a method-of-moments field solve of the cross-section, one dielectric; were the slot's edges to carry none of the return, up to 69 ohm). At 1 of the 2 place(s) the rise is within 10 %, the tolerance controlled impedance is commonly built to (the stackup states none); the rest exceed it or cannot be said, so the finding is a warning. One decision covers the split line's slot: whether these tracks may run down it, or should be moved over solid plane.

      • 'NetC148_1' on BTM at (49.41, 12.15), 0.77 mm, running ALONG the split for 0.35 mm, not across it, 43 ohm over solid plane, 47 ohm along it: 4.9 % of each edge reflected; other side: none: the signal layer is outermost
      • 'NetC148_1' on BTM at (49.43, 13.53), 7.03 mm, running ALONG the split for 6.79 mm, not across it, 43 ohm over solid plane, 47 ohm along it: 4.7 % of each edge reflected; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=along%40VSUP%3AP3V3%7CP5V0 serves each with its own layer_image region; all of them lie in x 48.4..50.6, y 9.13..18.09 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • merged:35.25,110.62|39.79,113.012 nets cross the slot of 7 drills from (35.25, 110.62) to (39.79, 113.01), whose anti-pads run together in the GND plane on L2, between 2 pairs of drills (fastest: MDI1_P at 1 ns 10-90 %, suggested by its name)

      The GND plane on L2 is cleared round a field of 7 drills from (35.25, 110.62) to (39.79, 113.01), and the clearances run together: the straight line from one drill to the next is bare all the way. 2 nets cross between drills of it at 2 place(s), each listed below with its two drills. Past one drill's anti-pad the return flows round on either side; here it cannot pass between the drills and detours round the whole merged clearance - the slot a row of pins or vias cuts in a plane. One decision covers the slot: whether these tracks may cross it, or the clearances should leave copper between the drills. 1 of the 2 crossing(s) have a plane on the track's other side at most twice as far away as the broken one (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The rest leave most or all of the return to the break, so the finding is a warning.

      • 'MDI3_P' on L1 at (37.55, 111.25), 1.1 mm between the drills at (36.22, 112.01) and (38.79, 111.01) in L2; other side: no plane on GND
      • 'MDI1_P' on L1 at (39.17, 110.27), 3.2 mm between the drills at (38.79, 111.01) and (39.79, 112.01) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=merged%3A35.25%2C110.62%7C39.79%2C113.01 serves each with its own layer_image region; all of them lie in x 36.28..40.79, y 109.09..114.01 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • refchange:+3.3V_PCI_CLK|GND'IN_SEL' changes reference between +3.3V_PCI_CLK and GND at a via, none with a reference that continues across (fastest: IN_SEL at 20 ns 10-90 %, suggested by its name)

      At 1 via(s), on 1 net(s), the signal leaves a layer referenced by one of +3.3V_PCI_CLK and GND for a layer referenced by the other, and no plane references both layers. Different nets: no via can carry the return across; only decoupling between the two planes near the via can. The capacitor carrying the return across was measured at each via, at the knee of the crossing net's edge against 50 ohm assumed: 1 with none. 1 of them at an ASSUMED edge (no edge on file for the net): state one (net_timing_state) and it is re-read. One decision covers the pair: whether +3.3V_PCI_CLK and GND are decoupled to each other near these vias. A via whose layers have more references than these two is a site of each pair it joins. None is partial: at every one, no reference continues across the via.

      • 'IN_SEL' at (143.64, 87.65), TOP -> BTM: GND on GND to +3.3V_PCI_CLK on VSUP; pure, no reference continues across; stitching none, 34.3 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (20 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. +3.3V_PCI_CLK and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=refchange%3A%2B3.3V_PCI_CLK%7CGND serves each with its own layer_image region; all of them lie in x 141.64..145.64, y 85.65..89.65 mm (board frame, Y up).

      The reference on each layer is the first plane the track meets leaving the via, anti-pads and the net's own copper skipped. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • refchange:GND|P5V010 nets change reference between GND and P5V0 at 10 vias, none with a reference that continues across (fastest: HDMI_HPD at 100 ps 10-90 %, ASSUMED)

      At 10 via(s), on 10 net(s), the signal leaves a layer referenced by one of GND and P5V0 for a layer referenced by the other, and no plane references both layers. Different nets: no via can carry the return across; only decoupling between the two planes near the via can. The capacitor carrying the return across was measured at each via, at the knee of the crossing net's edge against 50 ohm assumed: 10 with none. 10 of them at an ASSUMED edge (no edge on file for the net): state one (net_timing_state) and it is re-read. One decision covers the pair: whether GND and P5V0 are decoupled to each other near these vias. A via whose layers have more references than these two is a site of each pair it joins. None is partial: at every one, no reference continues across the via.

      • 'RST_11' at (3.23, 71.46), TOP -> BTM: GND on GND to P5V0 on VSUP; pure, no reference continues across; stitching none, 76.6 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (20 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. GND and P5V0 are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'USR_SW' at (3.49, 87.43), TOP -> BTM: GND on GND to P5V0 on VSUP; pure, no reference continues across; stitching none, 39.5 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. GND and P5V0 are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'HDMI_SCL' at (4.18, 59.19), TOP -> BTM: GND on GND to P5V0 on VSUP; pure, no reference continues across; stitching none, 18.8 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (10 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. GND and P5V0 are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'NetC148_1' at (53.93, 24.77), TOP -> BTM: GND on GND to P5V0 on VSUP; pure, no reference continues across; stitching none, 18.4 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. GND and P5V0 are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'NetC149_1' at (54.67, 24.12), TOP -> BTM: GND on GND to P5V0 on VSUP; pure, no reference continues across; stitching none, 17.2 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. GND and P5V0 are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'HDMI_HPD' at (3.13, 55.48), TOP -> BTM: GND on GND to P5V0 on VSUP; pure, no reference continues across; stitching none, 14.5 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. GND and P5V0 are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'NetIC12_14' at (56.29, 18.13), TOP -> BTM: GND on GND to P5V0 on VSUP; pure, no reference continues across; stitching none, 3.1 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. GND and P5V0 are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'NetIC12_12' at (57.25, 16.19), TOP -> BTM: GND on GND to P5V0 on VSUP; pure, no reference continues across; stitching none, 2.1 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. GND and P5V0 are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'NetIC12_16' at (57.25, 17.16), TOP -> BTM: GND on GND to P5V0 on VSUP; pure, no reference continues across; stitching none, 2.1 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. GND and P5V0 are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'NetIC12_9' at (57.25, 19.1), TOP -> BTM: GND on GND to P5V0 on VSUP; pure, no reference continues across; stitching none, 2.1 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. GND and P5V0 are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=refchange%3AGND%7CP5V0 serves each with its own layer_image region; all of them lie in x 1.13..59.25, y 14.19..89.43 mm (board frame, Y up).

      The reference on each layer is the first plane the track meets leaving the via, anti-pads and the net's own copper skipped. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • split@VSUP:+3.3V_PCI_CLK|GND7 nets cross the split between the +3.3V_PCI_CLK and GND planes on VSUP at 13 places, with no plane on the track's other side (fastest: PCIE_CLK_REF2_N at 1 ns 10-90 %, suggested by its name)

      On VSUP the +3.3V_PCI_CLK and GND planes part, and 7 nets cross from one to the other at 13 place(s). The return current cannot follow a track across; it detours to wherever the two planes are joined (a stitching capacitor, or the source), and the loop it opens radiates and couples. One decision covers the boundary: whether it is stitched near these crossings, or the nets crossing it are slow enough not to care. Tracks that run ALONG this split, down the slot rather than across it, are a finding of their own: theirs is an impedance step, not a detour. At 0 of the 13 crossing(s) the track's other neighbour carries a plane, which the return can use there; 13 are on an outer layer, with no other neighbour. No crossing has a plane on the track's other side, so the whole return meets the break.

      • 'IN_SEL' on BTM at (145.66, 85.63), 0.28 mm; other side: none: the signal layer is outermost
      • 'PCIE_CLK_REF2_N' on BTM at (141.63, 95.17), 0.2 mm; other side: none: the signal layer is outermost
      • 'PCIE_CLK_REF2_N' on BTM at (142.38, 77.9), 0.2 mm; other side: none: the signal layer is outermost
      • 'PCIE_CLK_REF2_P' on BTM at (141.95, 95.1), 0.39 mm; other side: none: the signal layer is outermost
      • 'PCIE_CLK_REF2_P' on BTM at (142.62, 77.9), 0.2 mm; other side: none: the signal layer is outermost
      • 'RX2_N' on BTM at (130.97, 101.43), 0.2 mm; other side: none: the signal layer is outermost
      • 'RX2_N' on BTM at (137.5, 78.12), 0.39 mm; other side: none: the signal layer is outermost
      • 'RX2_P' on BTM at (131.21, 101.43), 0.2 mm; other side: none: the signal layer is outermost
      • 'RX2_P' on BTM at (137.81, 77.9), 0.21 mm; other side: none: the signal layer is outermost
      • 'SATA1_TX_N' on BTM at (130.12, 101.41), 0.23 mm; other side: none: the signal layer is outermost
      • 'SATA1_TX_N' on BTM at (136.59, 78.98), 0.28 mm; other side: none: the signal layer is outermost
      • 'SATA1_TX_P' on BTM at (130.37, 101.4), 0.2 mm; other side: none: the signal layer is outermost
      • and 1 more

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=split%40VSUP%3A%2B3.3V_PCI_CLK%7CGND serves each with its own layer_image region; all of them lie in x 129.1..146.76, y 76.8..102.49 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • split@VSUP:GND|P1V06 nets cross the split between the GND and P1V0 planes on VSUP at 6 places, all with a plane on the track's other side (fastest: PWR_OK at 100 ps 10-90 %, ASSUMED)

      On VSUP the GND and P1V0 planes part, and 6 nets cross from one to the other at 6 place(s). The return current cannot follow a track across; it detours to wherever the two planes are joined (a stitching capacitor, or the source), and the loop it opens radiates and couples. One decision covers the boundary: whether it is stitched near these crossings, or the nets crossing it are slow enough not to care. Tracks that run ALONG this split, down the slot rather than across it, are a finding of their own: theirs is an impedance step, not a detour. At 6 of the 6 crossing(s) the track's other neighbour carries a plane, which the return can use there. 0 of the 6 crossing(s) have a plane on the track's other side at most twice as far away as the broken one (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The rest leave most or all of the return to the break, so the finding is a warning.

      • 'PWR_OK' on L2 at (74.86, 113.07), 0.2 mm; other side: GND on L1, 0.82 mm from the track against 0.2 mm to VSUP: 80% of the return on VSUP
      • 'SUS3_N' on L2 at (74.86, 115.96), 0.2 mm; other side: GND on L1, 0.82 mm from the track against 0.2 mm to VSUP: 80% of the return on VSUP
      • 'SUS5_N' on L2 at (74.86, 113.43), 0.2 mm; other side: GND on L1, 0.82 mm from the track against 0.2 mm to VSUP: 80% of the return on VSUP
      • 'SUS_S4#' on L2 at (74.86, 115.57), 0.2 mm; other side: GND on L1, 0.82 mm from the track against 0.2 mm to VSUP: 80% of the return on VSUP
      • 'SUS_STAT#' on L2 at (74.86, 115.2), 0.2 mm; other side: GND on L1, 0.82 mm from the track against 0.2 mm to VSUP: 80% of the return on VSUP
      • 'WDT' on L2 at (74.86, 112.68), 0.2 mm; other side: GND on L1, 0.82 mm from the track against 0.2 mm to VSUP: 80% of the return on VSUP

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=split%40VSUP%3AGND%7CP1V0 serves each with its own layer_image region; all of them lie in x 73.76..75.96, y 111.68..116.96 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • split@VSUP:GND|P1V82 nets cross the split between the GND and P1V8 planes on VSUP at 3 places, with no plane on the track's other side (fastest: (S)ATA_ACT# at 100 ps 10-90 %, ASSUMED)

      On VSUP the GND and P1V8 planes part, and 2 nets cross from one to the other at 3 place(s). The return current cannot follow a track across; it detours to wherever the two planes are joined (a stitching capacitor, or the source), and the loop it opens radiates and couples. One decision covers the boundary: whether it is stitched near these crossings, or the nets crossing it are slow enough not to care. Tracks that run ALONG this split, down the slot rather than across it, are a finding of their own: theirs is an impedance step, not a detour. At 0 of the 3 crossing(s) the track's other neighbour carries a plane, which the return can use there. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '(S)ATA_ACT#' on L2 at (69.89, 103.21), 0.28 mm; other side: no plane on L1
      • '(S)ATA_ACT#' on L2 at (73.29, 106.01), 0.28 mm; other side: no plane on L1
      • 'WDT' on L2 at (63.99, 103.21), 0.2 mm; other side: no plane on L1

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=split%40VSUP%3AGND%7CP1V8 serves each with its own layer_image region; all of them lie in x 62.99..74.43, y 102.11..107.01 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • split@VSUP:GND|P2V5_A3 nets cross the split between the GND and P2V5_A planes on VSUP at 6 places; 2 with a plane on the track's other side (fastest: NetIC37_C13 at 100 ps 10-90 %, ASSUMED)

      On VSUP the GND and P2V5_A planes part, and 3 nets cross from one to the other at 6 place(s). The return current cannot follow a track across; it detours to wherever the two planes are joined (a stitching capacitor, or the source), and the loop it opens radiates and couples. One decision covers the boundary: whether it is stitched near these crossings, or the nets crossing it are slow enough not to care. Tracks that run ALONG this split, down the slot rather than across it, are a finding of their own: theirs is an impedance step, not a detour. At 2 of the 6 crossing(s) the track's other neighbour carries a plane, which the return can use there; 2 are on an outer layer, with no other neighbour. 0 of the 6 crossing(s) have a plane on the track's other side at most twice as far away as the broken one (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The rest leave most or all of the return to the break, so the finding is a warning.

      • 'NetIC37_C13' on L2 at (113.16, 31.39), 0.36 mm; other side: P1V0_PCIE on L1, 0.82 mm from the track against 0.2 mm to VSUP: 80% of the return on VSUP
      • 'NetIC37_C13' on L2 at (113.16, 33.45), 0.75 mm; other side: no plane on L1
      • 'NetIC37_C14' on L2 at (113.9, 32.72), 0.75 mm; other side: no plane on L1
      • 'NetIC37_C14' on L2 at (119.52, 25.33), 0.36 mm; other side: P1V0_PCIE on L1, 0.82 mm from the track against 0.2 mm to VSUP: 80% of the return on VSUP
      • 'NetIC37_N11' on BTM at (108.83, 42.85), 0.36 mm; other side: none: the signal layer is outermost
      • 'NetIC37_N11' on BTM at (109.07, 43.03), 0.68 mm; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=split%40VSUP%3AGND%7CP2V5_A serves each with its own layer_image region; all of them lie in x 107.65..120.65, y 24.2..44.19 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • split@VSUP:GND|P5V014 nets cross the split between the GND and P5V0 planes on VSUP at 24 places; 1 with a plane on the track's other side (fastest: (S)ATA_ACT# at 100 ps 10-90 %, ASSUMED)

      On VSUP the GND and P5V0 planes part, and 14 nets cross from one to the other at 24 place(s). The return current cannot follow a track across; it detours to wherever the two planes are joined (a stitching capacitor, or the source), and the loop it opens radiates and couples. One decision covers the boundary: whether it is stitched near these crossings, or the nets crossing it are slow enough not to care. Tracks that run ALONG this split, down the slot rather than across it, are a finding of their own: theirs is an impedance step, not a detour. At 1 of the 24 crossing(s) the track's other neighbour carries a plane, which the return can use there; 23 are on an outer layer, with no other neighbour. 0 of the 24 crossing(s) have a plane on the track's other side at most twice as far away as the broken one (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The rest leave most or all of the return to the break, so the finding is a warning.

      • '(S)ATA_ACT#' on L2 at (5.95, 52.26), 0.2 mm; other side: GND on L1, 0.82 mm from the track against 0.2 mm to VSUP: 80% of the return on VSUP
      • 'BOOT_11' on BTM at (70.97, 23.89), 0.2 mm; other side: none: the signal layer is outermost
      • 'HDMI_HPD' on BTM at (5.95, 54.26), 0.28 mm; other side: none: the signal layer is outermost
      • 'HDMI_SCL' on BTM at (5.95, 53.66), 0.28 mm; other side: none: the signal layer is outermost
      • 'HDMI_SDA' on BTM at (5.95, 53.06), 0.28 mm; other side: none: the signal layer is outermost
      • 'MOD_HANDLE' on BTM at (44.05, 9.99), 0.2 mm; other side: none: the signal layer is outermost
      • 'PROG_RXD_11' on BTM at (66.25, 23.89), 0.2 mm; other side: none: the signal layer is outermost
      • 'PROG_TXD_11' on BTM at (66.69, 23.89), 0.2 mm; other side: none: the signal layer is outermost
      • 'RST_11' on BTM at (5.95, 71.46), 0.2 mm; other side: none: the signal layer is outermost
      • 'RST_11' on BTM at (36.81, 9.99), 0.2 mm; other side: none: the signal layer is outermost
      • 'SATA3_TX_N' on BTM at (5.97, 60.07), 0.54 mm; other side: none: the signal layer is outermost
      • 'SATA3_TX_N' on BTM at (5.97, 60.88), 0.54 mm; other side: none: the signal layer is outermost
      • and 12 more

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=split%40VSUP%3AGND%7CP5V0 serves each with its own layer_image region; all of them lie in x 4.85..71.97, y 8.89..73.6 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • split@VSUP:P1V0|P1V88 nets cross the split between the P1V0 and P1V8 planes on VSUP at 8 places; 6 with a plane on the track's other side (fastest: PWRBTN# at 100 ps 10-90 %, ASSUMED)

      On VSUP the P1V0 and P1V8 planes part, and 8 nets cross from one to the other at 8 place(s). The return current cannot follow a track across; it detours to wherever the two planes are joined (a stitching capacitor, or the source), and the loop it opens radiates and couples. One decision covers the boundary: whether it is stitched near these crossings, or the nets crossing it are slow enough not to care. Tracks that run ALONG this split, down the slot rather than across it, are a finding of their own: theirs is an impedance step, not a detour. At 6 of the 8 crossing(s) the track's other neighbour carries a plane, which the return can use there; 1 are on an outer layer, with no other neighbour. 0 of the 8 crossing(s) have a plane on the track's other side at most twice as far away as the broken one (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The rest leave most or all of the return to the break, so the finding is a warning.

      • 'PCIE_SERDES_RSTN' on BTM at (59.98, 110.71), 0.2 mm; other side: none: the signal layer is outermost
      • 'PWRBTN#' on L2 at (56.35, 112.19), 0.2 mm; other side: no plane on L1
      • 'PWR_OK' on L2 at (68.38, 108.89), 0.28 mm; other side: GND on L1, 0.82 mm from the track against 0.2 mm to VSUP: 80% of the return on VSUP
      • 'SUS3_N' on L2 at (65.56, 110.76), 0.28 mm; other side: GND on L1, 0.82 mm from the track against 0.2 mm to VSUP: 80% of the return on VSUP
      • 'SUS5_N' on L2 at (67.15, 109.16), 0.28 mm; other side: GND on L1, 0.82 mm from the track against 0.2 mm to VSUP: 80% of the return on VSUP
      • 'SUS_S4#' on L2 at (66.34, 109.98), 0.2 mm; other side: GND on L1, 0.82 mm from the track against 0.2 mm to VSUP: 80% of the return on VSUP
      • 'SUS_STAT#' on L2 at (66.64, 109.68), 0.2 mm; other side: GND on L1, 0.82 mm from the track against 0.2 mm to VSUP: 80% of the return on VSUP
      • 'WDT' on L2 at (68.97, 108.89), 0.28 mm; other side: GND on L1, 0.82 mm from the track against 0.2 mm to VSUP: 80% of the return on VSUP

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=split%40VSUP%3AP1V0%7CP1V8 serves each with its own layer_image region; all of them lie in x 55.27..70.07, y 107.79..113.26 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • split@VSUP:P1V0|P3V32 nets cross the split between the P1V0 and P3V3 planes on VSUP at 2 places; 1 with a plane on the track's other side (fastest: PWRBTN# at 100 ps 10-90 %, ASSUMED)

      On VSUP the P1V0 and P3V3 planes part, and 2 nets cross from one to the other at 2 place(s). The return current cannot follow a track across; it detours to wherever the two planes are joined (a stitching capacitor, or the source), and the loop it opens radiates and couples. One decision covers the boundary: whether it is stitched near these crossings, or the nets crossing it are slow enough not to care. Tracks that run ALONG this split, down the slot rather than across it, are a finding of their own: theirs is an impedance step, not a detour. At 1 of the 2 crossing(s) the track's other neighbour carries a plane, which the return can use there; 1 are on an outer layer, with no other neighbour. 0 of the 2 crossing(s) have a plane on the track's other side at most twice as far away as the broken one (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The rest leave most or all of the return to the break, so the finding is a warning.

      • 'PCIE_SERDES_RSTN' on BTM at (59.98, 115.53), 0.2 mm; other side: none: the signal layer is outermost
      • 'PWRBTN#' on L2 at (59.69, 115.53), 0.28 mm; other side: GND on L1, 0.82 mm from the track against 0.2 mm to VSUP: 80% of the return on VSUP

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=split%40VSUP%3AP1V0%7CP3V3 serves each with its own layer_image region; all of them lie in x 58.59..60.98, y 114.43..116.63 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • split@VSUP:P1V8|P3V37 nets cross the split between the P1V8 and P3V3 planes on VSUP at 7 places; 3 with a plane on the track's other side (fastest: PWRBTN# at 100 ps 10-90 %, ASSUMED)

      On VSUP the P1V8 and P3V3 planes part, and 7 nets cross from one to the other at 7 place(s). The return current cannot follow a track across; it detours to wherever the two planes are joined (a stitching capacitor, or the source), and the loop it opens radiates and couples. One decision covers the boundary: whether it is stitched near these crossings, or the nets crossing it are slow enough not to care. Tracks that run ALONG this split, down the slot rather than across it, are a finding of their own: theirs is an impedance step, not a detour. At 3 of the 7 crossing(s) the track's other neighbour carries a plane, which the return can use there; 1 are on an outer layer, with no other neighbour. 0 of the 7 crossing(s) have a plane on the track's other side at most twice as far away as the broken one (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The rest leave most or all of the return to the break, so the finding is a warning.

      • 'PCIE_SERDES_RSTN' on BTM at (60.61, 103.21), 0.28 mm; other side: none: the signal layer is outermost
      • 'PWRBTN#' on L2 at (55.12, 103.21), 0.2 mm; other side: GND on L1, 0.82 mm from the track against 0.2 mm to VSUP: 80% of the return on VSUP
      • 'PWR_OK' on L2 at (63.56, 103.21), 0.2 mm; other side: no plane on L1
      • 'SUS3_N' on L2 at (56.17, 103.21), 0.2 mm; other side: GND on L1, 0.82 mm from the track against 0.2 mm to VSUP: 80% of the return on VSUP
      • 'SUS5_N' on L2 at (62.19, 103.21), 0.2 mm; other side: no plane on L1
      • 'SUS_S4#' on L2 at (56.56, 103.21), 0.2 mm; other side: GND on L1, 0.82 mm from the track against 0.2 mm to VSUP: 80% of the return on VSUP
      • 'SUS_STAT#' on L2 at (61.75, 103.21), 0.2 mm; other side: no plane on L1

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=split%40VSUP%3AP1V8%7CP3V3 serves each with its own layer_image region; all of them lie in x 54.12..64.56, y 102.11..104.31 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • split@VSUP:P3V3|P5V016 nets cross the split between the P3V3 and P5V0 planes on VSUP at 21 places; 1 with a plane on the track's other side (fastest: (S)ATA_ACT# at 100 ps 10-90 %, ASSUMED)

      On VSUP the P3V3 and P5V0 planes part, and 16 nets cross from one to the other at 21 place(s). The return current cannot follow a track across; it detours to wherever the two planes are joined (a stitching capacitor, or the source), and the loop it opens radiates and couples. One decision covers the boundary: whether it is stitched near these crossings, or the nets crossing it are slow enough not to care. Tracks that run ALONG this split, down the slot rather than across it, are a finding of their own: theirs is an impedance step, not a detour. At 1 of the 21 crossing(s) the track's other neighbour carries a plane, which the return can use there; 20 are on an outer layer, with no other neighbour. 0 of the 21 crossing(s) have a plane on the track's other side at most twice as far away as the broken one (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The rest leave most or all of the return to the break, so the finding is a warning.

      • '(S)ATA_ACT#' on L2 at (2.8, 52.26), 0.2 mm; other side: GND on L1, 0.82 mm from the track against 0.2 mm to VSUP: 80% of the return on VSUP
      • 'BOOT_11' on BTM at (70.97, 21.14), 0.2 mm; other side: none: the signal layer is outermost
      • 'HDMI_SCL' on BTM at (2.77, 59.13), 0.25 mm; other side: none: the signal layer is outermost
      • 'HDMI_SCL' on BTM at (2.8, 54.32), 0.2 mm; other side: none: the signal layer is outermost
      • 'HDMI_SDA' on BTM at (2.8, 53.88), 0.2 mm; other side: none: the signal layer is outermost
      • 'MOD_HANDLE' on BTM at (44.05, 6.98), 0.2 mm; other side: none: the signal layer is outermost
      • 'NetC142_1' on BTM at (49.5, 18.12), 0.28 mm; other side: none: the signal layer is outermost
      • 'NetC148_1' on BTM at (53.36, 20.85), 0.28 mm; other side: none: the signal layer is outermost
      • 'NetC149_1' on BTM at (53.36, 20.02), 0.28 mm; other side: none: the signal layer is outermost
      • 'PROG_RXD_11' on BTM at (66.25, 20.29), 0.28 mm; other side: none: the signal layer is outermost
      • 'PROG_TXD_11' on BTM at (66.69, 20.73), 0.28 mm; other side: none: the signal layer is outermost
      • 'RST_11' on BTM at (35.84, 6.95), 0.21 mm; other side: none: the signal layer is outermost
      • and 9 more

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=split%40VSUP%3AP3V3%7CP5V0 serves each with its own layer_image region; all of them lie in x 1.7..71.97, y 5.88..60.19 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

  21. ReferencePlaneDiscontinuitymajorOpen

    ReferencePlaneDiscontinuity: 4 boards×4

    4 checked by the review by Claude walker W4 (Cern session) — 4 different reasons

    At refchange:GND|P3V3, split@VSUP:GND|P3V3, void:GND@L1:hole 5.57,102.75|65.14,124.65, void:routed@L1|L2

    Each finding, with its own headline
    • refchange:GND|P3V313 nets change reference between GND and P3V3 at 14 vias, none with a reference that continues across (fastest: (S)ATA_ACT# at 100 ps 10-90 %, ASSUMED)

      At 14 via(s), on 13 net(s), the signal leaves a layer referenced by one of GND and P3V3 for a layer referenced by the other, and no plane references both layers. Different nets: no via can carry the return across; only decoupling between the two planes near the via can. The capacitor carrying the return across was measured at each via, at the knee of the crossing net's edge against 50 ohm assumed: 14 with none. 14 of them at an ASSUMED edge (no edge on file for the net): state one (net_timing_state) and it is re-read. One decision covers the pair: whether GND and P3V3 are decoupled to each other near these vias. A via whose layers have more references than these two is a site of each pair it joins. None is partial: at every one, no reference continues across the via.

      • '(S)ATA_ACT#' at (1.25, 50.81), TOP -> L2: GND on GND to P3V3 on VSUP; pure, no reference continues across; stitching none, 155.3 mm of track past the via on L2: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. GND and P3V3 are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'PCIE_SERDES_RSTN' at (52.6, 119.68), TOP -> BTM: GND on GND to P3V3 on VSUP; pure, no reference continues across; stitching none, 78.2 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (20 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. GND and P3V3 are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'PCIE_SERDES_RSTN' at (60.28, 95.15), TOP -> BTM: GND on GND to P3V3 on VSUP; pure, no reference continues across; stitching none, 78.2 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (20 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. GND and P3V3 are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'NetLD7_2' at (4.46, 140.95), TOP -> BTM: GND on GND to P3V3 on VSUP; pure, no reference continues across; stitching none, 43.4 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. GND and P3V3 are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'NetIC6_8' at (73.42, 0.88), TOP -> BTM: GND on GND to P3V3 on VSUP; pure, no reference continues across; stitching none, 27.4 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. GND and P3V3 are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'HDMI_SDA' at (0.53, 59.75), TOP -> BTM: GND on GND to P3V3 on VSUP; pure, no reference continues across; stitching none, 20.3 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (10 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. GND and P3V3 are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'NetC142_1' at (53.03, 25.42), TOP -> BTM: GND on GND to P3V3 on VSUP; pure, no reference continues across; stitching none, 19.5 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. GND and P3V3 are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'NetCON16A_15' at (2.56, 109.14), TOP -> BTM: GND on GND to P3V3 on VSUP; pure, no reference continues across; stitching none, 16.1 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. GND and P3V3 are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'NetIC18_E13' at (49.79, 105.01), TOP -> BTM: GND on GND to P3V3 on VSUP; pure, no reference continues across; stitching none, 8.8 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. GND and P3V3 are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'NetIC18_D14' at (49.79, 104.01), TOP -> BTM: GND on GND to P3V3 on VSUP; pure, no reference continues across; stitching none, 6.3 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. GND and P3V3 are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'NetIC18_E14' at (48.79, 104.01), TOP -> BTM: GND on GND to P3V3 on VSUP; pure, no reference continues across; stitching none, 4.9 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. GND and P3V3 are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'NetIC18_F14' at (47.79, 104.01), TOP -> BTM: GND on GND to P3V3 on VSUP; pure, no reference continues across; stitching none, 3.5 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. GND and P3V3 are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. Measured for reference: C188 (1 nF 0201) 2.0 mm away: 1.34 nH in the 1.220 mm cavity + 0.21 nH ESL + 1.27 nH mounting (pad 0.05 nH (vias beside the pads) + 1 via pair(s) at 1.00 mm pitch, 0.20 mm drill, 1.33 mm to the farther plane): 88.8 ohm at the knee, 178 % of 50 ohm (assumed track impedance). None.
      • and 2 more

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=refchange%3AGND%7CP3V3 serves each with its own layer_image region; all of them lie in x -1.47..146.35, y -1.12..143.3 mm (board frame, Y up).

      The reference on each layer is the first plane the track meets leaving the via, anti-pads and the net's own copper skipped. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • split@VSUP:GND|P3V344 nets cross the split between the GND and P3V3 planes on VSUP at 90 places; 10 with a plane on the track's other side (fastest: (S)ATA_ACT# at 100 ps 10-90 %, ASSUMED)

      On VSUP the GND and P3V3 planes part, and 44 nets cross from one to the other at 90 place(s). The return current cannot follow a track across; it detours to wherever the two planes are joined (a stitching capacitor, or the source), and the loop it opens radiates and couples. One decision covers the boundary: whether it is stitched near these crossings, or the nets crossing it are slow enough not to care. Tracks that run ALONG this split, down the slot rather than across it, are a finding of their own: theirs is an impedance step, not a detour. At 10 of the 90 crossing(s) the track's other neighbour carries a plane, which the return can use there; 80 are on an outer layer, with no other neighbour. 0 of the 90 crossing(s) have a plane on the track's other side at most twice as far away as the broken one (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The rest leave most or all of the return to the break, so the finding is a warning.

      • '(S)ATA_ACT#' on L2 at (60.97, 94.91), 0.28 mm; other side: GND on L1, 0.82 mm from the track against 0.2 mm to VSUP: 80% of the return on VSUP
      • '(S)ATA_ACT#' on L2 at (63.85, 97.4), 0.22 mm; other side: GND on L1, 0.82 mm from the track against 0.2 mm to VSUP: 80% of the return on VSUP
      • 'DSB_D_RXA_N' on BTM at (43.73, 125.93), 0.2 mm; other side: none: the signal layer is outermost
      • 'DSB_D_RXA_N' on BTM at (48.8, 125.93), 0.2 mm; other side: none: the signal layer is outermost
      • 'DSB_D_RXA_P' on BTM at (43.73, 125.69), 0.2 mm; other side: none: the signal layer is outermost
      • 'DSB_D_RXA_P' on BTM at (48.8, 125.69), 0.2 mm; other side: none: the signal layer is outermost
      • 'DSB_D_RXB_N' on BTM at (43.73, 135.25), 0.2 mm; other side: none: the signal layer is outermost
      • 'DSB_D_RXB_N' on BTM at (48.8, 135.25), 0.2 mm; other side: none: the signal layer is outermost
      • 'DSB_D_RXB_P' on BTM at (43.73, 135.01), 0.2 mm; other side: none: the signal layer is outermost
      • 'DSB_D_RXB_P' on BTM at (48.8, 135.01), 0.2 mm; other side: none: the signal layer is outermost
      • 'DSB_D_TXA_N' on BTM at (43.71, 125.08), 0.2 mm; other side: none: the signal layer is outermost
      • 'DSB_D_TXA_N' on BTM at (48.87, 125.08), 0.28 mm; other side: none: the signal layer is outermost
      • and 78 more

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=split%40VSUP%3AGND%7CP3V3 serves each with its own layer_image region; all of them lie in x 2.34..151.1, y -1.5..143.07 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L1:hole 5.57,102.75|65.14,124.6516 nets cross one void in the GND plane on L1 and the GND plane on L2 at 5 places, the longest 7.06 mm; 27 over tracks of other nets routed inside it (fastest: ACT#A at 100 ps 10-90 %, ASSUMED)

      Along 'FPGA_ALERTN_5' on L2, the GND plane on L1 has 7.06 mm under the track with copper of MDI1_N, MDI1_P, MDI2_P, MDI2_N, MDI3_N, MDI3_P, LINK1000#A, LINK#A, not a plane, at (27.66, 111.9), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 27 of the crossings pass over tracks of other nets routed inside the hole on the reference layer: the plane is absent there, and those tracks stand in it. 6 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 0.92 mm). 5 places on 16 net(s) cross it, listed below, the longest first. What cleared it: the hole at x 26.38..48.17, y 65.4..132.77 and the hole at x 5.57..65.14, y 102.75..124.65. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 26 of the 27 crossing(s) have a plane on the track's other side at most twice as far away as the broken one (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The rest leave most or all of the return to the break, so the finding is a warning.

      • one crossing of two tracks, seen from each: 'NetIC18_G7' on L1 at (64.63, 117.45), 0.71 mm over copper of PWRBTN#, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'PWRBTN#' on L2 at (64.4, 117.22), 0.71 mm over copper of NetIC18_G7, not a plane; other side: no plane on VSUP
      • one crossing of two tracks, seen from each: 'FPGA_ALERTN_5' on L2 at (27.66, 111.9), 7.06 mm, running ALONG the bare copper for 0.72 mm, not across it over copper of MDI1_N, MDI1_P, MDI2_P, MDI2_N, MDI3_N, MDI3_P, LINK1000#A, LINK#A, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'LINK#A' on L1 at (27.43, 115.35), 1.63 mm over copper of SDA_5, SCL_5, FPGA_ALERTN_5, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'LINK1000#A' on L1 at (27.43, 114.89), 1.63 mm over copper of SDA_5, SCL_5, FPGA_ALERTN_5, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'MDI1_N' on L1 at (26.97, 109.4), 1.63 mm over copper of SDA_5, SCL_5, FPGA_ALERTN_5, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'MDI1_P' on L1 at (26.97, 109.66), 1.63 mm over copper of SDA_5, SCL_5, FPGA_ALERTN_5, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'MDI2_N' on L1 at (26.51, 111.78), 1.96 mm, running ALONG the bare copper for 0.45 mm, not across it over copper of FPGA_ALERTN_5, SCL_5, SDA_5, not a plane, to the end of the track; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'MDI2_N' on L1 at (27.88, 110.85), 0.31 mm over copper of FPGA_ALERTN_5, not a plane, to the end of the track; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'MDI2_P' on L1 at (26.51, 111.52), 1.96 mm, running ALONG the bare copper for 0.45 mm, not across it over copper of SCL_5, FPGA_ALERTN_5, SDA_5, not a plane, to the end of the track; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'MDI2_P' on L1 at (27.88, 110.59), 0.31 mm over copper of FPGA_ALERTN_5, not a plane, to the end of the track; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'MDI3_N' on L1 at (26.51, 112.85), 0.69 mm, running ALONG the bare copper for 0.21 mm, not across it over copper of SDA_5, not a plane, to the end of the track; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'MDI3_N' on L1 at (27.83, 112.85), 0.75 mm over copper of FPGA_ALERTN_5, not a plane, to the end of the track; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'SCL_5' on L2 at (27.2, 112.74), 7.06 mm, running ALONG the bare copper for 0.72 mm, not across it over copper of MDI1_N, MDI1_P, MDI2_P, MDI2_N, MDI3_N, MDI3_P, LINK1000#A, LINK#A, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'SDA_5' on L2 at (26.74, 110.59), 7.06 mm, running ALONG the bare copper for 0.92 mm, not across it over copper of MDI1_N, MDI1_P, MDI2_P, MDI2_N, MDI3_N, MDI3_P, LINK1000#A, LINK#A, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1
      • one crossing of two tracks, seen from each: 'NetC68_1' on L1 at (58.03, 113.55), 1.01 mm over copper of PWRBTN#, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'NetC68_2' on L1 at (58.44, 113.96), 1.01 mm over copper of PWRBTN#, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'NetIC18_G7' on L1 at (56.51, 112.03), 1.01 mm over copper of PWRBTN#, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'PWRBTN#' on L2 at (56.95, 112.79), 3.72 mm over copper of NetIC18_G7, NetC68_1, NetC68_2, not a plane; other side: P1V0 on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1
      • one crossing of two tracks, seen from each: 'ACT#A' on L1 at (26.97, 118.92), 1.63 mm over copper of SDA_5, SCL_5, FPGA_ALERTN_5, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'FPGA_ALERTN_5' on L2 at (27.66, 119.15), 0.71 mm over copper of ACT#A, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'SCL_5' on L2 at (27.2, 118.69), 0.71 mm over copper of ACT#A, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'SDA_5' on L2 at (26.74, 118.69), 0.71 mm over copper of ACT#A, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1
      • one crossing of two tracks, seen from each: 'FPGA_ALERTN_5' on L2 at (27.66, 116.78), 0.71 mm over copper of LINK100#A, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'LINK100#A' on L1 at (27.43, 117.01), 1.63 mm over copper of SDA_5, SCL_5, FPGA_ALERTN_5, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'SCL_5' on L2 at (27.2, 117.24), 0.71 mm over copper of LINK100#A, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'SDA_5' on L2 at (26.74, 117.24), 0.71 mm over copper of LINK100#A, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=void%3AGND%40L1%3Ahole%205.57%2C102.75%7C65.14%2C124.65 serves each with its own layer_image region; all of them lie in x 25.38..65.98, y 107.65..120.28 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:routed@L1|L2Tracks on L1 and L2 cross each other at 162 places, each layer the other's reference with its pour cleared round its own tracks, the longest 26.34 mm; 72 run ALONG the cut round another net's track (fastest: (S)ATA_ACT# at 100 ps 10-90 %, ASSUMED)

      L1 and L2 each carry a pour and routed tracks, and each is the other's nearest reference. Wherever a track on one crosses a track on the other, the pour under it is cleared round that other track, so for the width of the cut the return has no plane under it and detours round the cut. 162 place(s) on 133 net(s), 31 of them seen from both tracks (each counted once). 72 of the crossings run ALONG the cut round another net's track rather than across it, parallel to its edges (the longest 21.14 mm): over or right beside that track, broadside to it as well as off the plane. One decision covers the layer pair: whether these layers may take a pour their own tracks cut as the reference, or the routing or the stackup should give the tracks a plane that is not cut where they cross. 344 of the 345 crossing(s) have a plane on the track's other side at most twice as far away as the broken one (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The rest leave most or all of the return to the break, so the finding is a warning.

      • one crossing of two tracks, seen from each: '(S)ATA_ACT#' on L2 at (70.83, 104.15), 9.68 mm, running ALONG the bare copper for 3.68 mm, not across it over copper of PCIE_CLK1_P, PCIE_CLK1_N, not a plane; other side: P1V8 on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'I2C_CK' on L2 at (71.13, 103.99), 8.76 mm, running ALONG the bare copper for 3.38 mm, not across it over copper of PCIE_CLK1_P, PCIE_CLK1_N, not a plane; other side: no plane on VSUP / 'I2C_DAT' on L2 at (71.45, 103.84), 7.83 mm, running ALONG the bare copper for 3.29 mm, not across it over copper of PCIE_CLK1_P, PCIE_CLK1_N, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'PCIE_CLK1_N' on L1 at (68.59, 102.23), 2.39 mm over copper of I2C_DAT, (S)ATA_ACT#, I2C_CK, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'PCIE_CLK1_N' on L1 at (74.52, 106.38), 2.97 mm over copper of I2C_DAT, I2C_CK, (S)ATA_ACT#, not a plane, to the end of the track; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'PCIE_CLK1_P' on L1 at (68.33, 101.97), 1.99 mm over copper of I2C_DAT, (S)ATA_ACT#, I2C_CK, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'PCIE_CLK1_P' on L1 at (74.83, 106.32), 2.9 mm over copper of I2C_DAT, I2C_CK, (S)ATA_ACT#, not a plane, to the end of the track; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • one crossing of two tracks, seen from each: '(S)ATA_ACT#' on L2 at (60.19, 69.86), 17.11 mm, running ALONG the bare copper for 13.63 mm, not across it over copper of SYS_RESET#, VGA_RED, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'I2C_CK' on L2 at (60.61, 67.22), 23.92 mm, running ALONG the bare copper for 18.47 mm, not across it over copper of PCIE_SERDES_RSTN, SYS_RESET#, VGA_RED, VGA_GRN, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'I2C_DAT' on L2 at (61.01, 67.04), 26.34 mm, running ALONG the bare copper for 19.64 mm, not across it over copper of PCIE_SERDES_RSTN, SYS_RESET#, VGA_RED, VGA_GRN, VGA_BLU, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'PCIE_SERDES_RSTN' on L1 at (58.46, 54.62), 2.9 mm, running ALONG the bare copper for 1.22 mm, not across it over copper of I2C_DAT, I2C_CK, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'SYS_RESET#' on L1 at (58.99, 55.49), 1.57 mm over copper of I2C_DAT, I2C_CK, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'SYS_RESET#' on L1 at (58.99, 62.16), 1.01 mm over copper of (S)ATA_ACT#, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'SYS_RESET#' on L1 at (58.99, 70.02), 16.74 mm, running ALONG the bare copper for 12.23 mm, not across it over copper of WDT, (S)ATA_ACT#, I2C_CK, I2C_DAT, VCC_RTC, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'VGA_BLU' on L1 at (60.92, 67.04), 23.61 mm, running ALONG the bare copper for 21.14 mm, not across it over copper of I2C_DAT, VCC_RTC, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'VGA_GRN' on L1 at (60.53, 67.23), 21.41 mm, running ALONG the bare copper for 18.37 mm, not across it over copper of I2C_DAT, I2C_CK, VCC_RTC, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'VGA_RED' on L1 at (60.14, 56.63), 1.57 mm over copper of I2C_DAT, I2C_CK, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'VGA_RED' on L1 at (60.14, 69.86), 16.57 mm, running ALONG the bare copper for 13.95 mm, not across it over copper of (S)ATA_ACT#, I2C_CK, I2C_DAT, VCC_RTC, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'WDT' on L2 at (58.96, 70.02), 13.29 mm, running ALONG the bare copper for 12.25 mm, not across it over copper of SYS_RESET#, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1
      • one crossing of two tracks, seen from each: '(S)ATA_ACT#' on L2 at (87.86, 107.3), 24.38 mm, running ALONG the bare copper for 15.77 mm, not across it over copper of DDI2_CTRL_AUX_N, DDI2_CTRL_AUX_P, PCIE4_TX_N, PCIE4_TX_P, PCIE4_RX_N, PCIE4_RX_P, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'DDI2_CTRL_AUX_N' on L1 at (78.27, 106.3), 2.13 mm over copper of I2C_DAT, I2C_CK, (S)ATA_ACT#, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'DDI2_CTRL_AUX_N' on L1 at (97.13, 108.09), 1.81 mm, running ALONG the bare copper for 0.95 mm, not across it over copper of (S)ATA_ACT#, not a plane, to the end of the track; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'DDI2_CTRL_AUX_P' on L1 at (78.64, 106.3), 2.24 mm over copper of (S)ATA_ACT#, I2C_DAT, I2C_CK, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'DDI2_CTRL_AUX_P' on L1 at (96.97, 107.83), 1.72 mm over copper of (S)ATA_ACT#, not a plane, to the end of the track; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'DDI3_DDC_AUX_SEL' on L2 at (96.45, 102.2), 11.06 mm, running ALONG the bare copper for 3.91 mm, not across it over copper of DDI3_PAIR2_N, DDI3_PAIR2_P, PCIE4_TX_N, PCIE4_TX_P, PCIE4_RX_N, PCIE4_RX_P, not a plane, to the end of the track; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'DDI3_PAIR1_P' on L1 at (95.86, 103.07), 5.37 mm, running ALONG the bare copper for 4.06 mm, not across it over copper of USB_67_OCN, not a plane, to the end of the track; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'DDI3_PAIR2_N' on L1 at (92.83, 100.81), 1.02 mm over copper of DDI3_DDC_AUX_SEL, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'DDI3_PAIR2_P' on L1 at (93.74, 101.07), 1.01 mm over copper of DDI3_DDC_AUX_SEL, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'I2C_CK' on L2 at (86.58, 106.92), 24.99 mm, running ALONG the bare copper for 17.18 mm, not across it over copper of DDI2_CTRL_AUX_N, DDI2_CTRL_AUX_P, PCIE4_TX_N, PCIE4_TX_P, PCIE4_RX_N, PCIE4_RX_P, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'I2C_DAT' on L2 at (88.66, 106.53), 25.33 mm, running ALONG the bare copper for 17.38 mm, not across it over copper of DDI2_CTRL_AUX_N, DDI2_CTRL_AUX_P, PCIE4_TX_N, PCIE4_TX_P, PCIE4_RX_N, PCIE4_RX_P, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'PCIE4_RX_N' on L1 at (101.01, 104.04), 3.99 mm over copper of DDI3_DDC_AUX_SEL, USB_67_OCN, USB_45_OCN, I2C_DAT, I2C_CK, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'PCIE4_RX_P' on L1 at (101.27, 104.17), 3.47 mm over copper of DDI3_DDC_AUX_SEL, USB_67_OCN, USB_45_OCN, I2C_DAT, I2C_CK, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'PCIE4_TX_N' on L1 at (100.11, 103.6), 5.78 mm over copper of DDI3_DDC_AUX_SEL, USB_67_OCN, USB_45_OCN, I2C_DAT, I2C_CK, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'PCIE4_TX_N' on L1 at (98.06, 109.49), 2.35 mm, running ALONG the bare copper for 0.83 mm, not across it over copper of (S)ATA_ACT#, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'PCIE4_TX_P' on L1 at (100.37, 103.73), 5.27 mm over copper of DDI3_DDC_AUX_SEL, USB_67_OCN, USB_45_OCN, I2C_DAT, I2C_CK, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'PCIE4_TX_P' on L1 at (99.85, 109.2), 1.09 mm over copper of (S)ATA_ACT#, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'USB_45_OCN' on L2 at (94.48, 105.23), 9.62 mm, running ALONG the bare copper for 4.96 mm, not across it over copper of PCIE4_TX_N, PCIE4_TX_P, PCIE4_RX_N, PCIE4_RX_P, not a plane, to the end of the track; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'USB_67_OCN' on L2 at (95.96, 103.1), 10.07 mm, running ALONG the bare copper for 4.42 mm, not across it over copper of DDI3_PAIR1_P, PCIE4_TX_N, PCIE4_TX_P, PCIE4_RX_N, PCIE4_RX_P, not a plane, to the end of the track; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1
      • 'VGA_VSYNC' on L1 at (61.33, 66.8), 20.77 mm, running ALONG the bare copper for 19.28 mm, not across it over copper of VCC_RTC, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • one crossing of two tracks, seen from each: 'FPGA_ALERTN_5' on L1 at (62.08, 34.55), 5.03 mm, running ALONG the bare copper for 4.06 mm, not across it over copper of I2C_DAT, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'FPGA_ALERTN_5' on L1 at (66.67, 27.83), 1.7 mm over copper of I2C_DAT, I2C_CK, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'I2C_CK' on L2 at (61.62, 34.28), 6.42 mm, running ALONG the bare copper for 4.18 mm, not across it over copper of SDA_5, SCL_5, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'I2C_CK' on L2 at (66.58, 27.58), 2.32 mm over copper of SDA_5, SCL_5, FPGA_ALERTN_5, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'I2C_DAT' on L2 at (63.6, 29.67), 13.2 mm, running ALONG the bare copper for 8.69 mm, not across it over copper of SDA_5, SCL_5, FPGA_ALERTN_5, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'SCL_5' on L1 at (61.66, 34.37), 6.28 mm, running ALONG the bare copper for 4.18 mm, not across it over copper of I2C_CK, I2C_DAT, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'SCL_5' on L1 at (66.01, 27.83), 1.7 mm over copper of I2C_DAT, I2C_CK, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'SDA_5' on L1 at (61.23, 36.55), 1.53 mm over copper of I2C_CK, I2C_DAT, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'SDA_5' on L1 at (63.5, 29.68), 6.64 mm, running ALONG the bare copper for 4.32 mm, not across it over copper of I2C_CK, I2C_DAT, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • one crossing of two tracks, seen from each: 'FPGA_ALERTN_5' on L1 at (57.86, 43.16), 1.55 mm over copper of I2C_CK, I2C_DAT, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'GA0' on L1 at (57.86, 51.73), 1.59 mm over copper of I2C_CK, I2C_DAT, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'GA1' on L1 at (57.86, 52.28), 1.59 mm over copper of I2C_CK, I2C_DAT, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'GA2' on L1 at (57.86, 52.84), 1.59 mm over copper of I2C_CK, I2C_DAT, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'I2C_CK' on L2 at (58.09, 46.26), 12.09 mm, running ALONG the bare copper for 3.38 mm, not across it over copper of SDA_5, SCL_5, FPGA_ALERTN_5, PEX_INT#, PRSNT2#, PRSNT1#, GA0, GA1, GA2, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'I2C_DAT' on L2 at (58.5, 45.85), 11.68 mm, running ALONG the bare copper for 3.58 mm, not across it over copper of SDA_5, SCL_5, FPGA_ALERTN_5, PEX_INT#, PRSNT2#, PRSNT1#, GA0, GA1, GA2, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'PEX_INT#' on L1 at (57.86, 49.82), 1.59 mm over copper of I2C_CK, I2C_DAT, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'PRSNT1#' on L1 at (57.86, 51.06), 1.59 mm over copper of I2C_CK, I2C_DAT, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'PRSNT2#' on L1 at (57.86, 50.46), 1.59 mm over copper of I2C_CK, I2C_DAT, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'SCL_5' on L1 at (58.73, 41.77), 1.13 mm over copper of I2C_CK, I2C_DAT, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'SDA_5' on L1 at (57.86, 41.38), 1.12 mm over copper of I2C_CK, I2C_DAT, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • one crossing of two tracks, seen from each: 'PCIE4_RX_N' on L1 at (103.05, 96.33), 2.46 mm over copper of TYPE0#, THRMTRIP#, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'PCIE4_RX_P' on L1 at (103.05, 96.59), 2.46 mm over copper of TYPE0#, THRMTRIP#, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'PCIE4_TX_N' on L1 at (103.05, 95.41), 2.46 mm over copper of TYPE0#, THRMTRIP#, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'PCIE4_TX_P' on L1 at (103.05, 95.68), 2.46 mm over copper of TYPE0#, THRMTRIP#, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'THRMTRIP#' on L2 at (106.5, 100), 11.05 mm, running ALONG the bare copper for 3.83 mm, not across it over copper of PCIE4_TX_N, PCIE4_TX_P, PCIE4_RX_N, PCIE4_RX_P, USB_MUX_SEL, USB_0_P, USB_0_N, not a plane, to the end of the track; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'THRMTRIP#' on L2 at (112.11, 101.51), 6.11 mm, running ALONG the bare copper for 3.89 mm, not across it over copper of USB_0_N, not a plane, to the end of the track; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'USB_0_N' on L1 at (104.01, 99.57), 3.78 mm, running ALONG the bare copper for 1.78 mm, not across it over copper of THRMTRIP#, not a plane, to the end of the track; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'USB_0_N' on L1 at (112.14, 101.58), 8.94 mm, running ALONG the bare copper for 6.03 mm, not across it over copper of THRMTRIP#, not a plane, to the end of the track; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'USB_0_P' on L1 at (103.54, 99.31), 1.58 mm over copper of THRMTRIP#, not a plane, to the end of the track; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'USB_0_P' on L1 at (104.42, 99.03), 0.78 mm over copper of THRMTRIP#, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'USB_MUX_SEL' on L1 at (103.07, 97.9), 2.28 mm over copper of THRMTRIP#, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • one crossing of two tracks, seen from each: 'TYPE2#' on L2 at (62.41, 62.25), 10.96 mm, running ALONG the bare copper for 9.44 mm, not across it over copper of VGA_I2C_DAT, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'VGA_I2C_DAT' on L1 at (62.59, 62.25), 10.81 mm, running ALONG the bare copper for 9.1 mm, not across it over copper of TYPE2#, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'RX3_P' on L1 at (155.99, 29.07), 8.61 mm, running ALONG the bare copper for 5.04 mm, not across it over copper of P12V0, not a plane, to the end of the track; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'GA2' on L1 at (155.99, 20.28), 8.53 mm, running ALONG the bare copper for 2.28 mm, not across it over copper of P12V0, not a plane, to the end of the track; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • one crossing of two tracks, seen from each: 'PWR_OK' on L2 at (99.37, 112.38), 4.09 mm over copper of SATA3_TX_P, SATA3_TX_N, SATA3_RX_P, SATA3_RX_N, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'SATA3_RX_N' on L1 at (100.94, 111.69), 2.13 mm over copper of WDT, PWR_OK, SUS5_N, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'SATA3_RX_P' on L1 at (100.68, 111.95), 2.13 mm over copper of WDT, PWR_OK, SUS5_N, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'SATA3_TX_N' on L1 at (99.82, 112.81), 2.13 mm over copper of WDT, PWR_OK, SUS5_N, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'SATA3_TX_P' on L1 at (96.83, 113.07), 4.05 mm, running ALONG the bare copper for 1.77 mm, not across it over copper of WDT, PWR_OK, SUS5_N, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'SUS5_N' on L2 at (99.92, 112.38), 4.09 mm over copper of SATA3_TX_P, SATA3_TX_N, SATA3_RX_P, SATA3_RX_N, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'WDT' on L2 at (100.54, 110.65), 7.84 mm, running ALONG the bare copper for 2.52 mm, not across it over copper of SATA3_TX_P, SATA3_TX_N, SATA3_RX_P, SATA3_RX_N, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1
      • 'ENABLE#' on L1 at (156.7, 33.85), 7.76 mm, running ALONG the bare copper for 5.18 mm, not across it over copper of P12V0, not a plane, to the end of the track; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • and 150 more

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=void%3Arouted%40L1%7CL2 serves each with its own layer_image region; all of them lie in x 0.25..163.11, y 5.02..143.4 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

  22. SinglePointNetmajorOpen

    SinglePointNet: 11 pins×11

    11 checked by the review by evaluation@esharp.se — 2 different reasons

    At IC18.A3, IC18.A8, IC18.A9, IC18.B3, IC18.B8, IC18.B9 and 5 more

    Each finding, with its own headline
    • IC18.A3IC18.A3 (PER_3_p) is an IC input left unconnected

      Pin IC18.A3 (PER_3_p) is an IC INPUT left UNCONNECTED (on the no-connect bucket). Marked no-connect by the designer, but an input normally needs a defined level - confirm it is truly meant to float. If the datasheet defines this input left open (an internal pull, "read as low when left floating", or a tri-level input whose open state is one of its settings), file it on the pin as if_unused (pull_up, pull_down or may_float) with submit_pin_behavior, citing the page, and this finding clears.

    • IC18.A8IC18.A8 (PER_2_p) is an IC input left unconnected

      Pin IC18.A8 (PER_2_p) is an IC INPUT left UNCONNECTED (on the no-connect bucket). Marked no-connect by the designer, but an input normally needs a defined level - confirm it is truly meant to float. If the datasheet defines this input left open (an internal pull, "read as low when left floating", or a tri-level input whose open state is one of its settings), file it on the pin as if_unused (pull_up, pull_down or may_float) with submit_pin_behavior, citing the page, and this finding clears.

    • IC18.A9IC18.A9 (PER_1_p) is an IC input left unconnected

      Pin IC18.A9 (PER_1_p) is an IC INPUT left UNCONNECTED (on the no-connect bucket). Marked no-connect by the designer, but an input normally needs a defined level - confirm it is truly meant to float. If the datasheet defines this input left open (an internal pull, "read as low when left floating", or a tri-level input whose open state is one of its settings), file it on the pin as if_unused (pull_up, pull_down or may_float) with submit_pin_behavior, citing the page, and this finding clears.

    • IC18.B3IC18.B3 (PER_3_n) is an IC input left unconnected

      Pin IC18.B3 (PER_3_n) is an IC INPUT left UNCONNECTED (on the no-connect bucket). Marked no-connect by the designer, but an input normally needs a defined level - confirm it is truly meant to float. If the datasheet defines this input left open (an internal pull, "read as low when left floating", or a tri-level input whose open state is one of its settings), file it on the pin as if_unused (pull_up, pull_down or may_float) with submit_pin_behavior, citing the page, and this finding clears.

    • IC18.B8IC18.B8 (PER_2_n) is an IC input left unconnected

      Pin IC18.B8 (PER_2_n) is an IC INPUT left UNCONNECTED (on the no-connect bucket). Marked no-connect by the designer, but an input normally needs a defined level - confirm it is truly meant to float. If the datasheet defines this input left open (an internal pull, "read as low when left floating", or a tri-level input whose open state is one of its settings), file it on the pin as if_unused (pull_up, pull_down or may_float) with submit_pin_behavior, citing the page, and this finding clears.

    • IC18.B9IC18.B9 (PER_1_n) is an IC input left unconnected

      Pin IC18.B9 (PER_1_n) is an IC INPUT left UNCONNECTED (on the no-connect bucket). Marked no-connect by the designer, but an input normally needs a defined level - confirm it is truly meant to float. If the datasheet defines this input left open (an internal pull, "read as low when left floating", or a tri-level input whose open state is one of its settings), file it on the pin as if_unused (pull_up, pull_down or may_float) with submit_pin_behavior, citing the page, and this finding clears.

    • IC18.C13IC18.C13 (NCSI_ARB_IN) is an IC input left unconnected

      Pin IC18.C13 (NCSI_ARB_IN) is an IC INPUT left UNCONNECTED (on the no-connect bucket). Marked no-connect by the designer, but an input normally needs a defined level - confirm it is truly meant to float. If the datasheet defines this input left open (an internal pull, "read as low when left floating", or a tri-level input whose open state is one of its settings), file it on the pin as if_unused (pull_up, pull_down or may_float) with submit_pin_behavior, citing the page, and this finding clears.

    • IC18.H1IC18.H1 (NCSI_CLK_IN) is an IC input left unconnected

      Pin IC18.H1 (NCSI_CLK_IN) is an IC INPUT left UNCONNECTED (on the no-connect bucket). Marked no-connect by the designer, but an input normally needs a defined level - confirm it is truly meant to float. If the datasheet defines this input left open (an internal pull, "read as low when left floating", or a tri-level input whose open state is one of its settings), file it on the pin as if_unused (pull_up, pull_down or may_float) with submit_pin_behavior, citing the page, and this finding clears.

    • IC18.J2IC18.J2 (NCSI_TX_EN) is an IC input left unconnected

      Pin IC18.J2 (NCSI_TX_EN) is an IC INPUT left UNCONNECTED (on the no-connect bucket). Marked no-connect by the designer, but an input normally needs a defined level - confirm it is truly meant to float. If the datasheet defines this input left open (an internal pull, "read as low when left floating", or a tri-level input whose open state is one of its settings), file it on the pin as if_unused (pull_up, pull_down or may_float) with submit_pin_behavior, citing the page, and this finding clears.

    • IC18.J3IC18.J3 (NCSI_TXD_0) is an IC input left unconnected

      Pin IC18.J3 (NCSI_TXD_0) is an IC INPUT left UNCONNECTED (on the no-connect bucket). Marked no-connect by the designer, but an input normally needs a defined level - confirm it is truly meant to float. If the datasheet defines this input left open (an internal pull, "read as low when left floating", or a tri-level input whose open state is one of its settings), file it on the pin as if_unused (pull_up, pull_down or may_float) with submit_pin_behavior, citing the page, and this finding clears.

    • IC18.J4IC18.J4 (NCSI_TXD_1) is an IC input left unconnected

      Pin IC18.J4 (NCSI_TXD_1) is an IC INPUT left UNCONNECTED (on the no-connect bucket). Marked no-connect by the designer, but an input normally needs a defined level - confirm it is truly meant to float. If the datasheet defines this input left open (an internal pull, "read as low when left floating", or a tri-level input whose open state is one of its settings), file it on the pin as if_unused (pull_up, pull_down or may_float) with submit_pin_behavior, citing the page, and this finding clears.

  23. observationOBS-410minorOpen

    USB 2.0 D+/D- TVS arrays sit behind the common-mode chokes, not at the connector (IC2A/B, IC10A/B, IC22A/B) - contrary to the designer's own note

    On the USB 2.0 host ports and the USB micro-AB console ports, the PRTR5V0U2X ESD arrays (IC2A/B, IC10A/B, IC22A/B) sit behind the common-mode chokes instead of at the connector, contrary to the designer's own note "Pulse guard (TVS) should be first, before choke."

    The signal chain as built

    ``mermaid flowchart LR C["Connector<br/>D+ / D-"] --> L["Common-mode choke<br/>DLSCM0805-900M or DLW21SN900SQ2L"] L --> T["PRTR5V0U2X TVS"] T --> D["COM Express<br/>or CP2102"] ``

    PortConnectorChokeTVSDevice sideSource
    USB host ACON12A A2/A3L5A (pins 1/2 connector side, 3/4 device side)IC10A (USB_UA_N/P)IC23netlist
    USB host BCON12BL5BIC10Bnetlist
    USB host A, secondCON12A B2/B3 + CON13A 2/3L2AIC2Anetlist
    USB host B, secondCON12B / CON13BL2BIC2Bnetlist
    Console ACON2A pins 2/3L8AIC22A (USB_DA_N/P)IC21A (CP2102)netlist
    Console BCON2BL8BIC22Bnetlist

    The note "Pulse guard (TVS) should be first, before choke." is beside these arrays on schematic sheets 7, 8, 24 and 25, and the drawing does not follow it.

    Why it matters

    • An ESD strike passes through the choke before it is clamped, stressing the choke and letting its inductance raise the voltage the downstream side sees.
    • On CON2A/B the arrays are also about 31 mm from the connector and about 7 mm from the CP2102 (placement: IC22A at (30.0, 31.0), CON2A at (-1.1, 30.8), IC21A at (37.2, 31.6)).

    Fix: move the TVS to the connector side of the choke, as the note says.

  24. observationOBS-418minorOpen

    No test point on any power rail or reset: the 44 TPs sit only on spare I350 / PEX8617 / LPC1764 / COM Express pins, plus 5 GND sockets

    None of the 44 test points is on a power rail or a reset: they sit only on spare I350, PEX8617, LPC1764 and COM Express pins, plus five GND sockets. Bring-up and production test must probe capacitor pads.

    Where the test points are

    The 44 test points TP1-TP46 are all top side and land only on otherwise-unused device pins:

    • NetIC37_* (PEX8617), e.g. TP1 on NetIC37_P16
    • NetIC18_* (I350), e.g. TP17 on NetIC18_P14
    • NetIC1_16/18/36/40/43 (LPC1764), e.g. TP4 on NetIC1_16
    • NetCON18_* (COM Express spare contacts), e.g. TP15 on NetCON18_A48

    The five "Test Point" sockets B5, B6, B7, B8 and B22 (VERO_20-2136) are all on GND.

    What has no probe point

    • Rails: P12V0, P5V0, P3V3, P3V3MP, 3P3V_LDO, P2V5, P1V8, P1V0_PCIE, PCIE_1V5, P3V3_HDMI
    • Resets: RST_11, PCIE_NRESET

    This is a testability observation, not a functional defect.

  25. observationOBS-419minorOpen

    Regulator output notes: the AP133 equations name R97/R108 instead of the fitted dividers, and the three buck dividers carry no output-voltage note

    The Vout note beside both AP133 LDOs (IC36, IC26) names R97/R108, which are unrelated parts, instead of the fitted dividers, and the three buck regulators IC6, IC17 and IC35 carry no output-voltage note at all.

    The regulators

    RegulatorSheetNote on the sheetFitted dividerOutputSource
    IC36 AP133SUPPLY (PDF 22)"Vout=0.8(1+R97/R108)", "I(out)=300mA"R181 10k / R182 4k7 (ADJ pin 4, NetIC36_4)schematic text; netlist; BOM
    IC26 AP133mPCIe (PDF 17)"Vout=0.8(1+R97/R108)", "I(out)=300mA"R213 24k / R214 27kschematic text; netlist; BOM
    IC6 NCP3170SUPPLYnoneR43 24k / R45 4k74.89 VBOM; Vref 0.8 V from the datasheet
    IC17 NCP3170SUPPLYnoneR71 24k / R88 7k53.36 VBOM; Vref 0.8 V from the datasheet
    IC35 TPS54620SUPPLYnoneR172 180 + R217 2k37 over R178 10k1.00 VBOM; Vref 0.8 V from the datasheet

    What R97 and R108 are

    • R97 sits only on the PCIe clocks sheet (PDF 18).
    • R108 is the pull-up on the I350 JRST ball E13, unrelated to any regulator.

    The AP133 note is a copy that points at unrelated parts. For the three bucks, the intended output of each divider is recorded only by the rail name.

  26. observationOBS-493minorOpen

    I350 IC18 NC-SI inputs are not terminated as the datasheet asks for a disconnected NC-SI port

    The I350 (IC18) NC-SI port is unused, but its inputs are not terminated the way the I350 datasheet asks: NCSI_CLK_IN and NCSI_TXD_0 float, and NCSI_TX_EN and NCSI_TXD_1 are pulled up instead of down.

    What the board does

    Ball (datasheet Table 2-20, p.46)FunctionBoard connectionDatasheet asks (p.46 note)
    G2NCSI_CLK_IN (input)openexternal pull-down
    G4NCSI_TX_EN (input)R120 10k to P3V3 (pull-up)external pull-down
    G3NCSI_TXD_1 (input)R119 10k to P3V3 (pull-up)10 kOhm pull-down
    H2NCSI_TXD_0 (input)open10 kOhm pull-down
    L3NCSI_CLK_OUTTP34 only-

    No BMC is connected, so the NC-SI port is disconnected in the datasheet's sense.

    Why it matters

    A floating NC-SI clock and transmit-data input can toggle on noise. TX_EN held high marks a BMC frame in progress. The datasheet revision history (p.5) records that the guidance for NCSI_TXD[1:0] changed from pull-up to pull-down in rev 2.4 (January 2016). The 10k pull-ups on G3/G4 look like the older guidance, but CLK_IN and TXD_0 were left open under either revision. NC-SI is normally disabled in the EEPROM image, so the practical effect is likely small. That is why this is graded minor.

    Suggested fix: 10k pull-downs on G2, G3, G4 and H2.

  27. ConnectorDomainMixedminorOpen

    ConnectorDomainMixed: 4 components×4

    4 checked by the review by Claude walker W4 (Cern session) — 4 different reasons

    At CON1, CON18, CON4, CON9

    Each finding, with its own headline
    • CON1CON1 takes 2 different supplies off the board on one connector: P12V0 (12.0 V), P3V3MP (3.3 V)

      CON1 carries 2 different supplies out of the board on one connector: P12V0 (12.0 V) on 18/2/27/42/57/72/84/9, P3V3MP (3.3 V) on 4. Declare the intent. Two rails on one connector is ordinary in a docking or power-distribution interface and a hazard in a signal one, and the difference is not visible from the netlist — but note that adjacent contacts at different voltages are exactly what a mirrored, reversed or off-by-one cable shorts together, so the cost of getting the mating wrong is a rail collision rather than a dead signal. If this is a standard connector, declare its family (connector_family_declare) and file the standard's contact map: supplies on the contacts it assigns to power are then not reported.

    • CON18CON18 takes 3 different supplies off the board on one connector: P12V0 (12.0 V), P5V0 (4.885 V), VCC_RTC (2.8 V)

      CON18 carries 3 different supplies out of the board on one connector: P12V0 (12.0 V) on A104/A105/A106/A107/A108/A109/B104/B105/B106/B107/B108/B109/C104/C105/C106/C107/C108/C109/D104/D105/D106/D107/D108/D109, P5V0 (4.885 V) on B84/B85/B86/B87, VCC_RTC (2.8 V) on A47. Declare the intent. Two rails on one connector is ordinary in a docking or power-distribution interface and a hazard in a signal one, and the difference is not visible from the netlist — but note that adjacent contacts at different voltages are exactly what a mirrored, reversed or off-by-one cable shorts together, so the cost of getting the mating wrong is a rail collision rather than a dead signal. If this is a standard connector, declare its family (connector_family_declare) and file the standard's contact map: supplies on the contacts it assigns to power are then not reported.

    • CON4CON4 takes 2 different supplies off the board on one connector: P12V0 (12.0 V), P3V3 (3.36 V)

      CON4 carries 2 different supplies out of the board on one connector: P12V0 (12.0 V) on 71/72/73/74, P3V3 (3.36 V) on 65/66/67/68. Declare the intent. Two rails on one connector is ordinary in a docking or power-distribution interface and a hazard in a signal one, and the difference is not visible from the netlist — but note that adjacent contacts at different voltages are exactly what a mirrored, reversed or off-by-one cable shorts together, so the cost of getting the mating wrong is a rail collision rather than a dead signal. If this is a standard connector, declare its family (connector_family_declare) and file the standard's contact map: supplies on the contacts it assigns to power are then not reported.

    • CON9CON9 takes 3 different supplies off the board on one connector: 3P3V_LDO (3.3 V), NetCON9_24 (3.3 V), PCIE_1V5 (1.511 V)

      CON9 carries 3 different supplies out of the board on one connector: 3P3V_LDO (3.3 V) on 2/39/41/52, NetCON9_24 (3.3 V) on 24, PCIE_1V5 (1.511 V) on 28/48/6. Declare the intent. Two rails on one connector is ordinary in a docking or power-distribution interface and a hazard in a signal one, and the difference is not visible from the netlist — but note that adjacent contacts at different voltages are exactly what a mirrored, reversed or off-by-one cable shorts together, so the cost of getting the mating wrong is a rail collision rather than a dead signal. If this is a standard connector, declare its family (connector_family_declare) and file the standard's contact map: supplies on the contacts it assigns to power are then not reported.

  28. DecapViaFanoutminorOpen

    DecapViaFanout: 7 components×7

    7 checked by the review by Claude walker W4 (Cern session) — 7 different reasons

    At C184, C197, C235, C236, C36, C47, C48

    Each finding, with its own headline
    • C184C184 on 'P3V3': its rail pad reaches its via over 2.05 mm of track, adding about 0.56 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads (a 10 uF bulk capacitor: its inductance matters only far above the band it serves)

      C184 on 'P3V3': its rail pad reaches its via over 2.05 mm of track, adding about 0.56 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads (a 10 uF bulk capacitor: its inductance matters only far above the band it serves). C184.2 (rail) runs 2.05 mm along its copper to its nearest via, 1.05 mm past the 1 mm beside the pad: 0.56 nH; C184.1 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 1.80 mm apart (the pad pitch), 0.2 l ln(D/R) nH with R 0.127 mm (the track's width is not read): 0.56 nH in all. Put the vias at the pads (or in them), one per pad at least, the rail's and the ground's close together; the capacitor's own inductance as mounted is 0.68 nH (pad 0.10 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 0.11 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

    • C197C197 on 'P1V8': its rail pad reaches its via over 2.09 mm of track, adding about 0.58 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads (a 10 uF bulk capacitor: its inductance matters only far above the band it serves)

      C197 on 'P1V8': its rail pad reaches its via over 2.09 mm of track, adding about 0.58 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads (a 10 uF bulk capacitor: its inductance matters only far above the band it serves). C197.2 (rail) runs 2.09 mm along its copper to its nearest via, 1.09 mm past the 1 mm beside the pad: 0.58 nH; C197.1 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 1.80 mm apart (the pad pitch), 0.2 l ln(D/R) nH with R 0.127 mm (the track's width is not read): 0.58 nH in all. Put the vias at the pads (or in them), one per pad at least, the rail's and the ground's close together; the capacitor's own inductance as mounted is 0.68 nH (pad 0.10 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 0.11 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

    • C235C235 on 'P1V0_PCIE': its rail pad reaches its via over 2.88 mm of track, adding about 1.46 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads (a 470 uF bulk capacitor: its inductance matters only far above the band it serves)

      C235 on 'P1V0_PCIE': its rail pad reaches its via over 2.88 mm of track, adding about 1.46 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads (a 470 uF bulk capacitor: its inductance matters only far above the band it serves). C235.1 (rail) runs 2.88 mm along its copper to its nearest via, 1.88 mm past the 1 mm beside the pad: 1.46 nH; C235.2 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 6.20 mm apart (the pad pitch), 0.2 l ln(D/R) nH with R 0.127 mm (the track's width is not read): 1.46 nH in all. Put the vias at the pads (or in them), one per pad at least, the rail's and the ground's close together; the capacitor's own inductance as mounted is 2.00 nH (pad 0.20 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 1.33 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

    • C236C236 on 'P1V0_PCIE': its rail pad reaches its via over 2.01 mm of track, adding about 0.79 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads (a 470 uF bulk capacitor: its inductance matters only far above the band it serves)

      C236 on 'P1V0_PCIE': its rail pad reaches its via over 2.01 mm of track, adding about 0.79 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads (a 470 uF bulk capacitor: its inductance matters only far above the band it serves). C236.1 (rail) runs 2.01 mm along its copper to its nearest via, 1.01 mm past the 1 mm beside the pad: 0.79 nH; C236.2 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 6.20 mm apart (the pad pitch), 0.2 l ln(D/R) nH with R 0.127 mm (the track's width is not read): 0.79 nH in all. Put the vias at the pads (or in them), one per pad at least, the rail's and the ground's close together; the capacitor's own inductance as mounted is 2.00 nH (pad 0.20 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 1.33 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

    • C36C36 on 'P12V0': its rail pad reaches its via over 2.50 mm of track and its ground pad over 0.00 mm, adding about 0.95 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads (a 10 uF bulk capacitor: its inductance matters only far above the band it serves)

      C36 on 'P12V0': its rail pad reaches its via over 2.50 mm of track and its ground pad over 0.00 mm, adding about 0.95 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads (a 10 uF bulk capacitor: its inductance matters only far above the band it serves). C36.2 (rail) runs 2.50 mm along its copper to its nearest via, 1.50 mm past the 1 mm beside the pad: 0.95 nH; C36.1 (ground) runs 0.00 mm along its copper to its nearest via, beside the pad. Each run past the pad as one conductor of a pair 3.00 mm apart (the pad pitch), 0.2 l ln(D/R) nH with R 0.127 mm (the track's width is not read): 0.95 nH in all. Put the vias at the pads (or in them), one per pad at least, the rail's and the ground's close together; the capacitor's own inductance as mounted is 1.07 nH (pad 0.20 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 0.11 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

    • C47C47 on 'P12V0': its rail pad reaches its via over 2.54 mm of track and its ground pad over 0.00 mm, adding about 0.97 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads (a 10 uF bulk capacitor: its inductance matters only far above the band it serves)

      C47 on 'P12V0': its rail pad reaches its via over 2.54 mm of track and its ground pad over 0.00 mm, adding about 0.97 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads (a 10 uF bulk capacitor: its inductance matters only far above the band it serves). C47.2 (rail) runs 2.54 mm along its copper to its nearest via, 1.54 mm past the 1 mm beside the pad: 0.97 nH; C47.1 (ground) runs 0.00 mm along its copper to its nearest via, beside the pad. Each run past the pad as one conductor of a pair 3.00 mm apart (the pad pitch), 0.2 l ln(D/R) nH with R 0.127 mm (the track's width is not read): 0.97 nH in all. Put the vias at the pads (or in them), one per pad at least, the rail's and the ground's close together; the capacitor's own inductance as mounted is 1.07 nH (pad 0.20 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 0.11 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

    • C48C48 on 'P12V0': its rail pad reaches its via over 2.09 mm of track, adding about 0.55 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads (within a quarter of the starting value)

      C48 on 'P12V0': its rail pad reaches its via over 2.09 mm of track, adding about 0.55 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads (within a quarter of the starting value). C48.2 (rail) runs 2.09 mm along its copper to its nearest via, 1.09 mm past the 1 mm beside the pad: 0.55 nH; C48.1 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 1.60 mm apart (the pad pitch), 0.2 l ln(D/R) nH with R 0.127 mm (the track's width is not read): 0.55 nH in all. Put the vias at the pads (or in them), one per pad at least, the rail's and the ground's close together; the capacitor's own inductance as mounted is 0.68 nH (pad 0.10 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 0.11 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

  29. ReferencePlaneDiscontinuityminorOpen

    ReferencePlaneDiscontinuity: 62 boards×62

    62 checked by the review by Claude walker W4 (Cern session) — 62 different reasons

    At along@VSUP:GND|P1V8, along@VSUP:GND|P2V5_A, along@VSUP:GND|P3V3, along@VSUP:GND|P5V0, merged:104.68,37.9|107.51,39.31, merged:104.68,40.73|108.92,42.14 and 56 more

    Each finding, with its own headline
    • along@VSUP:GND|P1V82 nets run ALONG the split between the GND and P1V8 planes on VSUP at 2 places, the longest 3.87 mm; the impedance rises from 60 ohm to 66 ohm there at worst, 5 % of each edge reflected (fastest: SATA3_TX_P at 3 ns 10-90 %, suggested by its name)

      On VSUP the GND and P1V8 planes part, and 2 nets run down the slot between them at 2 place(s), rather than across it. This is not a crossing: the return still follows the track, in the plane on its other side and in the slot's edges, so it does not detour. What changes is the track's own impedance. With the plane gone from under it on this side for that length, its field reaches further, to the slot's edges and to the next plane beyond, so its capacitance falls and its impedance rises; every edge travelling down it is partly reflected where it enters the stretch and again where it leaves, by (Z2 - Z1)/(Z2 + Z1). The longer the stretch against the edge's rise, the more of the edge sees the full step. A crossing is generally the worse fault; a mismatch is not free. Over solid plane each track is 57 ohm to 60 ohm; along the slot 59 ohm to 66 ohm, reflecting up to 5 % of each edge (a method-of-moments field solve of the cross-section, one dielectric; were the slot's edges to carry none of the return, up to 88 ohm). At 1 of the 2 place(s) the rise is within 10 %, the tolerance controlled impedance is commonly built to (the stackup states none); the rest exceed it or cannot be said, so the finding is a warning. One decision covers the split line's slot: whether these tracks may run down it, or should be moved over solid plane.

      • 'SATA3_TX_P' on BTM at (71.77, 104.55), 4.6 mm, running ALONG the split for 3.87 mm, not across it, 60 ohm over solid plane, 66 ohm along it: 5 % of each edge reflected; other side: none: the signal layer is outermost
      • 'I2C_CK' on L2 at (71.62, 104.47), 3.92 mm, running ALONG the split for 3.42 mm, not across it, 57 ohm over solid plane, 59 ohm along it: 1.3 % of each edge reflected; other side: no plane on L1

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=along%40VSUP%3AGND%7CP1V8 serves each with its own layer_image region; all of them lie in x 69.25..74.67, y 102.11..107.25 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • along@VSUP:GND|P2V5_A'NetIC37_E14' runs ALONG the split between the GND and P2V5_A planes on VSUP at 1 place, the longest 0.47 mm; the impedance rises from 57 ohm to 60 ohm there at worst, 2.6 % of each edge reflected (fastest: NetIC37_E14 at 100 ps 10-90 %, ASSUMED)

      On VSUP the GND and P2V5_A planes part, and 'NetIC37_E14' runs down the slot between them at 1 place(s), rather than across it. This is not a crossing: the return still follows the track, in the plane on its other side and in the slot's edges, so it does not detour. What changes is the track's own impedance. With the plane gone from under it on this side for that length, its field reaches further, to the slot's edges and to the next plane beyond, so its capacitance falls and its impedance rises; every edge travelling down it is partly reflected where it enters the stretch and again where it leaves, by (Z2 - Z1)/(Z2 + Z1). The longer the stretch against the edge's rise, the more of the edge sees the full step. A crossing is generally the worse fault; a mismatch is not free. Over solid plane each track is 57 ohm; along the slot 60 ohm, reflecting up to 2.6 % of each edge (a method-of-moments field solve of the cross-section, one dielectric; were the slot's edges to carry none of the return, up to 69 ohm). At every place the rise is within 10 %, the tolerance controlled impedance is commonly built to (the stackup states none), so the finding is the lower tier (info). One decision covers the split line's slot: whether these tracks may run down it, or should be moved over solid plane.

      • 'NetIC37_E14' on L2 at (111.75, 33.45), 1.03 mm, running ALONG the split for 0.47 mm, not across it, 57 ohm over solid plane, 60 ohm along it: 2.6 % of each edge reflected; other side: no plane on L1

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=along%40VSUP%3AGND%7CP2V5_A serves each with its own layer_image region; all of them lie in x 110.75..112.75, y 31.62..34.65 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • along@VSUP:GND|P3V32 nets run ALONG the split between the GND and P3V3 planes on VSUP at 2 places, the longest 10 mm; the impedance rises from 60 ohm to 65 ohm there at worst, 3.9 % of each edge reflected (fastest: DSB_D_TXA_P at 100 ps 10-90 %, ASSUMED)

      On VSUP the GND and P3V3 planes part, and 2 nets run down the slot between them at 2 place(s), rather than across it. This is not a crossing: the return still follows the track, in the plane on its other side and in the slot's edges, so it does not detour. What changes is the track's own impedance. With the plane gone from under it on this side for that length, its field reaches further, to the slot's edges and to the next plane beyond, so its capacitance falls and its impedance rises; every edge travelling down it is partly reflected where it enters the stretch and again where it leaves, by (Z2 - Z1)/(Z2 + Z1). The longer the stretch against the edge's rise, the more of the edge sees the full step. A crossing is generally the worse fault; a mismatch is not free. Over solid plane each track is 56 ohm to 60 ohm; along the slot 58 ohm to 65 ohm, reflecting up to 3.9 % of each edge (a method-of-moments field solve of the cross-section, one dielectric; were the slot's edges to carry none of the return, up to 88 ohm). At every place the rise is within 10 %, the tolerance controlled impedance is commonly built to (the stackup states none), so the finding is the lower tier (info). One decision covers the split line's slot: whether these tracks may run down it, or should be moved over solid plane.

      • 'DSB_D_TXA_P' on BTM at (35.21, 116.78), 1.57 mm, running ALONG the split for 1.38 mm, not across it, 60 ohm over solid plane, 65 ohm along it: 3.9 % of each edge reflected; other side: none: the signal layer is outermost
      • 'PWRBTN#' on L2 at (68.77, 117.22), 10.5 mm, running ALONG the split for 10 mm, not across it, 56 ohm over solid plane, 58 ohm along it: 1.7 % of each edge reflected; other side: GND on L1, 0.82 mm from the track against 0.2 mm to VSUP: 80% of the return on VSUP

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=along%40VSUP%3AGND%7CP3V3 serves each with its own layer_image region; all of them lie in x 33.7..75.12, y 115.27..118.38 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • along@VSUP:GND|P5V0'USB_4_N' runs ALONG the split between the GND and P5V0 planes on VSUP at 1 place, the longest 0.52 mm; the impedance rises from 60 ohm to 64 ohm there at worst, 3.7 % of each edge reflected (fastest: USB_4_N at 500 ps 10-90 %, suggested by its name)

      On VSUP the GND and P5V0 planes part, and 'USB_4_N' runs down the slot between them at 1 place(s), rather than across it. This is not a crossing: the return still follows the track, in the plane on its other side and in the slot's edges, so it does not detour. What changes is the track's own impedance. With the plane gone from under it on this side for that length, its field reaches further, to the slot's edges and to the next plane beyond, so its capacitance falls and its impedance rises; every edge travelling down it is partly reflected where it enters the stretch and again where it leaves, by (Z2 - Z1)/(Z2 + Z1). The longer the stretch against the edge's rise, the more of the edge sees the full step. A crossing is generally the worse fault; a mismatch is not free. Over solid plane each track is 60 ohm; along the slot 64 ohm, reflecting up to 3.7 % of each edge (a method-of-moments field solve of the cross-section, one dielectric; were the slot's edges to carry none of the return, up to 88 ohm). At every place the rise is within 10 %, the tolerance controlled impedance is commonly built to (the stackup states none), so the finding is the lower tier (info). One decision covers the split line's slot: whether these tracks may run down it, or should be moved over solid plane.

      • 'USB_4_N' on BTM at (16.37, 10.07), 0.8 mm, running ALONG the split for 0.52 mm, not across it, 60 ohm over solid plane, 64 ohm along it: 3.7 % of each edge reflected; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=along%40VSUP%3AGND%7CP5V0 serves each with its own layer_image region; all of them lie in x 15.11..17.65, y 8.99..11.09 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • merged:104.68,37.9|107.51,39.313 nets cross the slot of 7 drills from (104.68, 37.9) to (107.51, 39.31), whose anti-pads run together in the GND plane on L2, between 3 pairs of drills (fastest: COM_TX4_P at 3 ns 10-90 %, suggested by its name)

      The GND plane on L2 is cleared round a field of 7 drills from (104.68, 37.9) to (107.51, 39.31), and the clearances run together: the straight line from one drill to the next is bare all the way. 3 nets cross between drills of it at 3 place(s), each listed below with its two drills. Past one drill's anti-pad the return flows round on either side; here it cannot pass between the drills and detours round the whole merged clearance - the slot a row of pins or vias cuts in a plane. One decision covers the slot: whether these tracks may cross it, or the clearances should leave copper between the drills. 2 of the 3 crossing(s) have a plane on the track's other side at most twice as far away as the broken one (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The rest leave most or all of the return to the break, so the finding is a warning.

      • 'COM_TX4_P' on L1 at (105.87, 38.12), 1.03 mm between the drills at (104.68, 37.9) and (106.8, 38.6) in L2; other side: no plane on GND
      • 'COM_TX5_N' on L1 at (106.43, 37.54), 2.44 mm between the drills at (106.09, 37.9) and (106.8, 37.19) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'COM_TX5_P' on L1 at (105.97, 36.93), 1.29 mm between the drills at (106.09, 36.48) and (106.09, 37.9) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=merged%3A104.68%2C37.9%7C107.51%2C39.31 serves each with its own layer_image region; all of them lie in x 104.27..108.51, y 35.93..39.34 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • merged:104.68,40.73|108.92,42.142 nets cross the slot of 11 drills from (104.68, 40.73) to (108.92, 42.14), whose anti-pads run together in the GND plane on L2, between 2 pairs of drills (fastest: COM_TX2_P at 3 ns 10-90 %, suggested by its name)

      The GND plane on L2 is cleared round a field of 11 drills from (104.68, 40.73) to (108.92, 42.14), and the clearances run together: the straight line from one drill to the next is bare all the way. 2 nets cross between drills of it at 2 place(s), each listed below with its two drills. Past one drill's anti-pad the return flows round on either side; here it cannot pass between the drills and detours round the whole merged clearance - the slot a row of pins or vias cuts in a plane. One decision covers the slot: whether these tracks may cross it, or the clearances should leave copper between the drills. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'COM_TX2_P' on L1 at (105.76, 43.25), 1.87 mm between the drills at (105.39, 42.85) and (106.09, 43.55) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'COM_TX3_N' on L1 at (104.68, 43.12), 0.81 mm between the drills at (104.68, 43.55) and (106.09, 40.73) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=merged%3A104.68%2C40.73%7C108.92%2C42.14 serves each with its own layer_image region; all of them lie in x 103.43..107.8, y 41.85..45.01 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • merged:107.51,35.09|111.75,35.072 nets cross the slot of 10 drills from (107.51, 35.09) to (111.75, 35.07), whose anti-pads run together in the GND plane on L2, between 2 pairs of drills (fastest: COM_TX6_N at 3 ns 10-90 %, suggested by its name)

      The GND plane on L2 is cleared round a field of 10 drills from (107.51, 35.09) to (111.75, 35.07), and the clearances run together: the straight line from one drill to the next is bare all the way. 2 nets cross between drills of it at 2 place(s), each listed below with its two drills. Past one drill's anti-pad the return flows round on either side; here it cannot pass between the drills and detours round the whole merged clearance - the slot a row of pins or vias cuts in a plane. One decision covers the slot: whether these tracks may cross it, or the clearances should leave copper between the drills. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'COM_TX6_N' on L1 at (108.55, 35.42), 2.33 mm between the drills at (108.92, 35.07) and (108.92, 36.48) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'COM_TX7_N' on L1 at (109.36, 34.81), 2.82 mm between the drills at (108.92, 35.07) and (109.63, 34.36) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=merged%3A107.51%2C35.09%7C111.75%2C35.07 serves each with its own layer_image region; all of them lie in x 107.1..111.34, y 32.38..36.91 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • merged:108.27,98.82|111.08,96.834 nets cross the slot of 10 drills from (108.27, 98.82) to (111.08, 96.83), whose anti-pads run together in the GND plane on L2, between 3 pairs of drills (fastest: W_DISABLE# at 100 ps 10-90 %, ASSUMED)

      The GND plane on L2 is cleared round a field of 10 drills from (108.27, 98.82) to (111.08, 96.83), and the clearances run together: the straight line from one drill to the next is bare all the way. 4 nets cross between drills of it at 4 place(s), each listed below with its two drills. Past one drill's anti-pad the return flows round on either side; here it cannot pass between the drills and detours round the whole merged clearance - the slot a row of pins or vias cuts in a plane. One decision covers the slot: whether these tracks may cross it, or the clearances should leave copper between the drills. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'PCIE3_RX_P' on L1 at (110.04, 95.08), 1.12 mm between the drills at (109.29, 94.57) and (111.08, 96.83) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'PCIE4_TX_P' on L1 at (110.34, 96.59), 1.08 mm between the drills at (109.29, 98.33) and (111.08, 96.07) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'PCIE5_RX_N' on L1 at (110.04, 97.82), 1.12 mm between the drills at (109.29, 98.33) and (111.08, 96.07) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'W_DISABLE#' on L1 at (108.85, 98.65), 2.58 mm between the drills at (108.27, 98.82) and (109.29, 98.33) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=merged%3A108.27%2C98.82%7C111.08%2C96.83 serves each with its own layer_image region; all of them lie in x 107.47..112.08, y 94.08..100.02 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • merged:113.16,36.48|116.7,35.78'RX5_P' crosses between the drills at (114.58, 35.07) and (115.29, 35.78), whose anti-pads run together in the GND plane on L2 (fastest: RX5_P at 3 ns 10-90 %, suggested by its name)

      Along 'RX5_P' on L1, the GND plane on L2 is cleared round the drills at (114.58, 35.07) and (115.29, 35.78), and the two clearances run together: the straight line from one drill to the other is bare all the way, and the track crosses it, over 1.9 mm of bare stretch at (114.95, 35.4). Past one drill's anti-pad the return flows round on either side; here it cannot pass between the drills and detours round the whole merged clearance - the slot a row of pins or vias cuts in a plane. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RX5_P' on L1 at (114.95, 35.4), 1.9 mm between the drills at (114.58, 35.07) and (115.29, 35.78) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=merged%3A113.16%2C36.48%7C116.7%2C35.78 serves each with its own layer_image region; all of them lie in x 113.58..116.74, y 33.95..37.48 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • merged:113.16,46.38|118.11,44.264 nets cross the slot of 17 drills from (113.16, 46.38) to (118.11, 44.26), whose anti-pads run together in the GND plane on L2, between 4 pairs of drills (fastest: RX8_N at 3 ns 10-90 %, suggested by its name)

      The GND plane on L2 is cleared round a field of 17 drills from (113.16, 46.38) to (118.11, 44.26), and the clearances run together: the straight line from one drill to the next is bare all the way. 4 nets cross between drills of it at 4 place(s), each listed below with its two drills. Past one drill's anti-pad the return flows round on either side; here it cannot pass between the drills and detours round the whole merged clearance - the slot a row of pins or vias cuts in a plane. One decision covers the slot: whether these tracks may cross it, or the clearances should leave copper between the drills. 3 of the 4 crossing(s) have a plane on the track's other side at most twice as far away as the broken one (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The rest leave most or all of the return to the break, so the finding is a warning.

      • 'RX9_P' on L1 at (116.95, 44.51), 1.15 mm between the drills at (116.7, 45.67) and (117.41, 43.55) in L2; other side: no plane on GND
      • 'RX8_N' on L1 at (117.81, 43.25), 2.06 mm between the drills at (116.7, 41.43) and (117.41, 43.55) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'RX8_P' on L1 at (117.98, 43.83), 1.06 mm between the drills at (116.7, 41.43) and (118.11, 44.26) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'RX9_N' on L1 at (116.99, 43.84), 2.44 mm between the drills at (116.7, 44.26) and (117.41, 43.55) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=merged%3A113.16%2C46.38%7C118.11%2C44.26 serves each with its own layer_image region; all of them lie in x 114.99..119.55, y 41.72..46.07 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • merged:113.82,70.7|113.82,72.72 nets cross the slot of 3 drills from (113.82, 70.7) to (113.82, 72.7), whose anti-pads run together in the GND plane on L2, between 2 pairs of drills (fastest: SPI_MISO at 2 ns 10-90 %, suggested by its name)

      The GND plane on L2 is cleared round a field of 3 drills from (113.82, 70.7) to (113.82, 72.7), and the clearances run together: the straight line from one drill to the next is bare all the way. 2 nets cross between drills of it at 2 place(s), each listed below with its two drills. Past one drill's anti-pad the return flows round on either side; here it cannot pass between the drills and detours round the whole merged clearance - the slot a row of pins or vias cuts in a plane. One decision covers the slot: whether these tracks may cross it, or the clearances should leave copper between the drills. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'SPI_MISO' on L1 at (113.8, 72.22), 0.55 mm between the drills at (113.82, 71.7) and (113.82, 72.7) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'SPI_POWER' on L1 at (113.82, 71.21), 0.53 mm between the drills at (113.82, 70.7) and (113.82, 71.7) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=merged%3A113.82%2C70.7%7C113.82%2C72.7 serves each with its own layer_image region; all of them lie in x 112.55..115.09, y 70.21..73.22 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • merged:115.99,39.31|118.82,37.9'RX7_P' crosses between the drills at (118.82, 37.9) and (118.11, 38.6), whose anti-pads run together in the GND plane on L2 (fastest: RX7_P at 3 ns 10-90 %, suggested by its name)

      Along 'RX7_P' on L1, the GND plane on L2 is cleared round the drills at (118.82, 37.9) and (118.11, 38.6), and the two clearances run together: the straight line from one drill to the other is bare all the way, and the track crosses it, over 2.24 mm of bare stretch at (118.9, 38.34). Past one drill's anti-pad the return flows round on either side; here it cannot pass between the drills and detours round the whole merged clearance - the slot a row of pins or vias cuts in a plane. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RX7_P' on L1 at (118.9, 38.34), 2.24 mm between the drills at (118.82, 37.9) and (118.11, 38.6) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=merged%3A115.99%2C39.31%7C118.82%2C37.9 serves each with its own layer_image region; all of them lie in x 116.41..120.05, y 37.15..40.31 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • merged:121.13,110.19|123.19,110.56'RX2_P' crosses between the drills at (121.13, 110.19) and (122.48, 108.71), whose anti-pads run together in the GND plane on L2 (fastest: RX2_P at 3 ns 10-90 %, suggested by its name)

      Along 'RX2_P' on L1, the GND plane on L2 is cleared round the drills at (121.13, 110.19) and (122.48, 108.71), and the two clearances run together: the straight line from one drill to the other is bare all the way, and the track crosses it, over 1.12 mm of bare stretch at (121.73, 109.21). Past one drill's anti-pad the return flows round on either side; here it cannot pass between the drills and detours round the whole merged clearance - the slot a row of pins or vias cuts in a plane. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RX2_P' on L1 at (121.73, 109.21), 1.12 mm between the drills at (121.13, 110.19) and (122.48, 108.71) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=merged%3A121.13%2C110.19%7C123.19%2C110.56 serves each with its own layer_image region; all of them lie in x 120.57..123.48, y 108.21..110.5 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • merged:134.7,133.1|139.73,133.782 nets cross the slot of 7 drills from (134.7, 133.1) to (139.73, 133.78), whose anti-pads run together in the GND plane on L2, between 2 pairs of drills (fastest: PCIE5_RX_N at 3 ns 10-90 %, suggested by its name)

      The GND plane on L2 is cleared round a field of 7 drills from (134.7, 133.1) to (139.73, 133.78), and the clearances run together: the straight line from one drill to the next is bare all the way. 2 nets cross between drills of it at 2 place(s), each listed below with its two drills. Past one drill's anti-pad the return flows round on either side; here it cannot pass between the drills and detours round the whole merged clearance - the slot a row of pins or vias cuts in a plane. One decision covers the slot: whether these tracks may cross it, or the clearances should leave copper between the drills. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'PCIE5_RX_N' on L1 at (135.8, 133.17), 0.72 mm between the drills at (134.7, 133.1) and (136.77, 133.85) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'PCIE5_RX_P' on L1 at (135.42, 133.18), 0.47 mm between the drills at (134.7, 133.1) and (136.06, 133.86) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=merged%3A134.7%2C133.1%7C139.73%2C133.78 serves each with its own layer_image region; all of them lie in x 134.19..137.05, y 131.91..134.48 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • merged:14.48,38.57|16.26,39.65'DDI2_CTRL_AUX_N' crosses between the drills at (14.95, 37.91) and (15.5, 39.65), whose anti-pads run together in the GND plane on L2 (fastest: DDI2_CTRL_AUX_N at 100 ps 10-90 %, ASSUMED)

      Along 'DDI2_CTRL_AUX_N' on L1, the GND plane on L2 is cleared round the drills at (14.95, 37.91) and (15.5, 39.65), and the two clearances run together: the straight line from one drill to the other is bare all the way, and the track crosses it, over 1.09 mm of bare stretch at (15.36, 38.37). Past one drill's anti-pad the return flows round on either side; here it cannot pass between the drills and detours round the whole merged clearance - the slot a row of pins or vias cuts in a plane. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'DDI2_CTRL_AUX_N' on L1 at (15.36, 38.37), 1.09 mm between the drills at (14.95, 37.91) and (15.5, 39.65) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=merged%3A14.48%2C38.57%7C16.26%2C39.65 serves each with its own layer_image region; all of them lie in x 13.48..16.77, y 37.37..39.57 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • merged:144.57,54.88|144.57,56.522 nets cross between the drills at (144.57, 54.88) and (144.57, 56.52), whose anti-pads run together in the GND plane on L2 (fastest: PCIE3_TX_N at 3 ns 10-90 %, suggested by its name)

      The GND plane on L2 is cleared round the drills at (144.57, 54.88) and (144.57, 56.52), and the clearances run together: the straight line from one drill to the next is bare all the way. 2 nets cross between drills of it at 2 place(s), each listed below with its two drills. Past one drill's anti-pad the return flows round on either side; here it cannot pass between the drills and detours round the whole merged clearance - the slot a row of pins or vias cuts in a plane. One decision covers the slot: whether these tracks may cross it, or the clearances should leave copper between the drills. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'PCIE3_TX_N' on L1 at (145.25, 55.93), 1.72 mm between the drills at (144.57, 54.88) and (144.57, 56.52) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'PCIE3_TX_P' on L1 at (145.2, 56.25), 2.1 mm between the drills at (144.57, 54.88) and (144.57, 56.52) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=merged%3A144.57%2C54.88%7C144.57%2C56.52 serves each with its own layer_image region; all of them lie in x 142.72..146.48, y 54.63..57.53 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • merged:147.33,16.48|147.33,18.12'GA1' crosses between the drills at (147.33, 16.48) and (147.33, 18.12), whose anti-pads run together in the GND plane on L2 (fastest: GA1 at 100 ps 10-90 %, ASSUMED)

      Along 'GA1' on L1, the GND plane on L2 is cleared round the drills at (147.33, 16.48) and (147.33, 18.12), and the two clearances run together: the straight line from one drill to the other is bare all the way, and the track crosses it, over 1.14 mm of bare stretch at (147.33, 17.27). Past one drill's anti-pad the return flows round on either side; here it cannot pass between the drills and detours round the whole merged clearance - the slot a row of pins or vias cuts in a plane. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'GA1' on L1 at (147.33, 17.27), 1.14 mm between the drills at (147.33, 16.48) and (147.33, 18.12) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=merged%3A147.33%2C16.48%7C147.33%2C18.12 serves each with its own layer_image region; all of them lie in x 145.76..148.9, y 16.27..18.27 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • merged:147.33,18.88|147.33,20.52'GA2' crosses between the drills at (147.33, 18.88) and (147.33, 20.52), whose anti-pads run together in the GND plane on L2 (fastest: GA2 at 100 ps 10-90 %, ASSUMED)

      Along 'GA2' on L1, the GND plane on L2 is cleared round the drills at (147.33, 18.88) and (147.33, 20.52), and the two clearances run together: the straight line from one drill to the other is bare all the way, and the track crosses it, over 1.14 mm of bare stretch at (147.33, 19.68). Past one drill's anti-pad the return flows round on either side; here it cannot pass between the drills and detours round the whole merged clearance - the slot a row of pins or vias cuts in a plane. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'GA2' on L1 at (147.33, 19.68), 1.14 mm between the drills at (147.33, 18.88) and (147.33, 20.52) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=merged%3A147.33%2C18.88%7C147.33%2C20.52 serves each with its own layer_image region; all of them lie in x 145.76..148.9, y 18.68..20.68 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • merged:147.33,28.48|147.33,30.12'ENABLE#' crosses between the drills at (147.33, 28.48) and (147.33, 30.12), whose anti-pads run together in the GND plane on L2 (fastest: ENABLE# at 20 ns 10-90 %, suggested by its name)

      Along 'ENABLE#' on L1, the GND plane on L2 is cleared round the drills at (147.33, 28.48) and (147.33, 30.12), and the two clearances run together: the straight line from one drill to the other is bare all the way, and the track crosses it, over 1.14 mm of bare stretch at (147.33, 29.31). Past one drill's anti-pad the return flows round on either side; here it cannot pass between the drills and detours round the whole merged clearance - the slot a row of pins or vias cuts in a plane. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'ENABLE#' on L1 at (147.33, 29.31), 1.14 mm between the drills at (147.33, 28.48) and (147.33, 30.12) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=merged%3A147.33%2C28.48%7C147.33%2C30.12 serves each with its own layer_image region; all of them lie in x 145.76..148.9, y 28.31..30.31 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • merged:15.03,124.55|17.57,135.732 nets cross the slot of 12 drills from (15.03, 124.55) to (17.57, 135.73), whose anti-pads run together in the GND plane on L2, between 2 pairs of drills (fastest: GBE_MDI1_N at 1 ns 10-90 %, suggested by its name)

      The GND plane on L2 is cleared round a field of 12 drills from (15.03, 124.55) to (17.57, 135.73), and the clearances run together: the straight line from one drill to the next is bare all the way. 2 nets cross between drills of it at 2 place(s), each listed below with its two drills. Past one drill's anti-pad the return flows round on either side; here it cannot pass between the drills and detours round the whole merged clearance - the slot a row of pins or vias cuts in a plane. One decision covers the slot: whether these tracks may cross it, or the clearances should leave copper between the drills. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'GBE_MDI1_N' on L1 at (16.08, 128.22), 2.16 mm between the drills at (15.03, 128.61) and (17.57, 127.6) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'GBE_MDI1_P' on L1 at (16.27, 129.31), 0.75 mm between the drills at (15.03, 130.65) and (17.57, 125.57) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=merged%3A15.03%2C124.55%7C17.57%2C135.73 serves each with its own layer_image region; all of them lie in x 13.82..17.46, y 125.58..130.31 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • merged:15.05,104.82|17.59,1163 nets cross the slot of 12 drills from (15.05, 104.82) to (17.59, 116), whose anti-pads run together in the GND plane on L2, between 3 pairs of drills (fastest: MDI1_N at 1 ns 10-90 %, suggested by its name)

      The GND plane on L2 is cleared round a field of 12 drills from (15.05, 104.82) to (17.59, 116), and the clearances run together: the straight line from one drill to the next is bare all the way. 3 nets cross between drills of it at 3 place(s), each listed below with its two drills. Past one drill's anti-pad the return flows round on either side; here it cannot pass between the drills and detours round the whole merged clearance - the slot a row of pins or vias cuts in a plane. One decision covers the slot: whether these tracks may cross it, or the clearances should leave copper between the drills. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'MDI1_N' on L1 at (15.85, 107.65), 4.15 mm between the drills at (15.05, 108.89) and (17.59, 107.87) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'MDI2_N' on L1 at (15.84, 112.16), 6.03 mm between the drills at (15.05, 110.92) and (17.59, 111.94) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'MDI2_P' on L1 at (15.9, 110.92), 0.92 mm between the drills at (15.05, 108.89) and (17.59, 113.97) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=merged%3A15.05%2C104.82%7C17.59%2C116 serves each with its own layer_image region; all of them lie in x 14.05..19.97, y 105.84..113.95 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • merged:44.79,113.01|49.79,114.01'NetC68_2' crosses between the drills at (48.79, 113.01) and (48.79, 114.01), whose anti-pads run together in the GND plane on L2 (fastest: NetC68_2 at 100 ps 10-90 %, ASSUMED)

      Along 'NetC68_2' on L1, the GND plane on L2 is cleared round the drills at (48.79, 113.01) and (48.79, 114.01), and the two clearances run together: the straight line from one drill to the other is bare all the way, and the track crosses it, over 2.22 mm of bare stretch at (49.17, 113.51). Past one drill's anti-pad the return flows round on either side; here it cannot pass between the drills and detours round the whole merged clearance - the slot a row of pins or vias cuts in a plane. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'NetC68_2' on L1 at (49.17, 113.51), 2.22 mm between the drills at (48.79, 113.01) and (48.79, 114.01) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=merged%3A44.79%2C113.01%7C49.79%2C114.01 serves each with its own layer_image region; all of them lie in x 46.79..51.06, y 112.51..115.01 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • merged:46.79,104.01|50.79,107.013 nets cross the slot of 13 drills from (46.79, 104.01) to (50.79, 107.01), whose anti-pads run together in the GND plane on L2, between 3 pairs of drills (fastest: NetIC18_E12 at 100 ps 10-90 %, ASSUMED)

      The GND plane on L2 is cleared round a field of 13 drills from (46.79, 104.01) to (50.79, 107.01), and the clearances run together: the straight line from one drill to the next is bare all the way. 3 nets cross between drills of it at 3 place(s), each listed below with its two drills. Past one drill's anti-pad the return flows round on either side; here it cannot pass between the drills and detours round the whole merged clearance - the slot a row of pins or vias cuts in a plane. One decision covers the slot: whether these tracks may cross it, or the clearances should leave copper between the drills. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'NetIC18_E12' on L1 at (50.29, 104.53), 1.55 mm between the drills at (49.79, 104.01) and (50.79, 104.01) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'NetIC18_F13' on L1 at (49.29, 104.16), 1.25 mm between the drills at (48.79, 104.01) and (49.79, 104.01) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'NetIC18_G13' on L1 at (48.29, 104.16), 1.22 mm between the drills at (47.79, 104.01) and (48.79, 104.01) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=merged%3A46.79%2C104.01%7C50.79%2C107.01 serves each with its own layer_image region; all of them lie in x 46.79..51.34, y 102.74..106.28 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • merged:69.67,38.16|70.48,38.28'VGA_RED' crosses between the drills at (69.8, 38.96) and (70.48, 38.28), whose anti-pads run together in the GND plane on L2 (fastest: VGA_RED at 100 ps 10-90 %, ASSUMED)

      Along 'VGA_RED' on L1, the GND plane on L2 is cleared round the drills at (69.8, 38.96) and (70.48, 38.28), and the two clearances run together: the straight line from one drill to the other is bare all the way, and the track crosses it, over 0.97 mm of bare stretch at (70.06, 38.55). Past one drill's anti-pad the return flows round on either side; here it cannot pass between the drills and detours round the whole merged clearance - the slot a row of pins or vias cuts in a plane. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'VGA_RED' on L1 at (70.06, 38.55), 0.97 mm between the drills at (69.8, 38.96) and (70.48, 38.28) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=merged%3A69.67%2C38.16%7C70.48%2C38.28 serves each with its own layer_image region; all of them lie in x 68.67..71.27, y 37.16..40.13 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • merged:71.41,36.41|72.9,35.87'VGA_I2C_CK' crosses between the drills at (72.89, 35.87) and (72.21, 36.54), whose anti-pads run together in the GND plane on L2 (fastest: VGA_I2C_CK at 10 ns 10-90 %, suggested by its name)

      Along 'VGA_I2C_CK' on L1, the GND plane on L2 is cleared round the drills at (72.89, 35.87) and (72.21, 36.54), and the two clearances run together: the straight line from one drill to the other is bare all the way, and the track crosses it, over 0.96 mm of bare stretch at (72.48, 36.13). Past one drill's anti-pad the return flows round on either side; here it cannot pass between the drills and detours round the whole merged clearance - the slot a row of pins or vias cuts in a plane. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'VGA_I2C_CK' on L1 at (72.48, 36.13), 0.96 mm between the drills at (72.89, 35.87) and (72.21, 36.54) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=merged%3A71.41%2C36.41%7C72.9%2C35.87 serves each with its own layer_image region; all of them lie in x 71.09..73.69, y 34.74..37.7 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • merged:9.8,93.36|16.58,95.65'DSB_D_TXB_N' crosses between the drills at (14.5, 94.36) and (16.57, 95.01), whose anti-pads run together in the GND plane on L2 (fastest: DSB_D_TXB_N at 100 ps 10-90 %, ASSUMED)

      Along 'DSB_D_TXB_N' on L1, the GND plane on L2 is cleared round the drills at (14.5, 94.36) and (16.57, 95.01), and the two clearances run together: the straight line from one drill to the other is bare all the way, and the track crosses it, over 1.45 mm of bare stretch at (15.91, 94.55). Past one drill's anti-pad the return flows round on either side; here it cannot pass between the drills and detours round the whole merged clearance - the slot a row of pins or vias cuts in a plane. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'DSB_D_TXB_N' on L1 at (15.91, 94.55), 1.45 mm between the drills at (14.5, 94.36) and (16.57, 95.01) in L2; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=merged%3A9.8%2C93.36%7C16.58%2C95.65 serves each with its own layer_image region; all of them lie in x 14.91..17.58, y 93.33..96.67 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • merged:92.08,66.76|92.83,69.152 nets cross the slot of 6 drills from (92.08, 66.76) to (92.83, 69.15), whose anti-pads run together in the GND plane on L1, between 2 pairs of drills (fastest: THRMTRIP# at 100 ps 10-90 %, ASSUMED)

      The GND plane on L1 is cleared round a field of 6 drills from (92.08, 66.76) to (92.83, 69.15), and the clearances run together: the straight line from one drill to the next is bare all the way. 2 nets cross between drills of it at 2 place(s), each listed below with its two drills. Past one drill's anti-pad the return flows round on either side; here it cannot pass between the drills and detours round the whole merged clearance - the slot a row of pins or vias cuts in a plane. One decision covers the slot: whether these tracks may cross it, or the clearances should leave copper between the drills. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'THRMTRIP#' on L2 at (92.75, 67.71), 0.76 mm between the drills at (92.83, 67.24) and (92.83, 68.19) in L1; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1
      • 'TYPE0#' on L2 at (92.75, 68.67), 0.76 mm between the drills at (92.83, 68.19) and (92.83, 69.15) in L1; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=merged%3A92.08%2C66.76%7C92.83%2C69.15 serves each with its own layer_image region; all of them lie in x 91.12..94.13, y 66.71..69.67 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • refchange:GND|P1V0_PCIE'NetIC37_E14' changes reference between GND and P1V0_PCIE at a via, none with a reference that continues across (fastest: NetIC37_E14 at 100 ps 10-90 %, ASSUMED)

      At 1 via(s), on 1 net(s), the signal leaves a layer referenced by one of GND and P1V0_PCIE for a layer referenced by the other, and no plane references both layers. Different nets: no via can carry the return across; only decoupling between the two planes near the via can. The capacitor carrying the return across was measured at each via, at the knee of the crossing net's edge against 50 ohm assumed: 1 served. Every site is served, so the finding is the lower tier (info). 1 of them at an ASSUMED edge (no edge on file for the net): state one (net_timing_state) and it is re-read. One decision covers the pair: whether GND and P1V0_PCIE are decoupled to each other near these vias. A via whose layers have more references than these two is a site of each pair it joins. None is partial: at every one, no reference continues across the via.

      • 'NetIC37_E14' at (111.75, 33.65), TOP -> L2: GND on GND to P1V0_PCIE on L1; pure, no reference continues across; stitching served, 16.5 mm of track past the via on L2: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. GND on GND and P1V0_PCIE on L1 are adjacent, 0.200 mm apart: their own capacitance carries the return. Measured for reference: C251 (100 nF 0201) 1.8 mm away: 0.21 nH in the 0.200 mm cavity + 0.21 nH ESL + 0.85 nH mounting (pad 0.05 nH + no via of the second net within 1 mm of its pad: the study's 0.6 nH per mm of 1.33 mm depth, ASSUMED): 39.9 ohm at the knee, 80 % of 50 ohm (assumed track impedance). Served.

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=refchange%3AGND%7CP1V0_PCIE serves each with its own layer_image region; all of them lie in x 109.75..113.75, y 31.65..35.65 mm (board frame, Y up).

      The reference on each layer is the first plane the track meets leaving the via, anti-pads and the net's own copper skipped. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • split@L1:GND|P1V0_PCIE'NetIC37_E14' crosses the split between the GND and P1V0_PCIE planes on L1 at 1 place, all with a plane on the track's other side (fastest: NetIC37_E14 at 100 ps 10-90 %, ASSUMED)

      On L1 the GND and P1V0_PCIE planes part, and 'NetIC37_E14' crosses from one to the other at 1 place(s). The return current cannot follow a track across; it detours to wherever the two planes are joined (a stitching capacitor, or the source), and the loop it opens radiates and couples. One decision covers the boundary: whether it is stitched near these crossings, or the nets crossing it are slow enough not to care. Tracks that run ALONG this split, down the slot rather than across it, are a finding of their own: theirs is an impedance step, not a detour. At 1 of the 1 crossing(s) the track's other neighbour carries a plane, which the return can use there. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'NetIC37_E14' on L2 at (111.75, 31.67), 0.36 mm; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=split%40L1%3AGND%7CP1V0_PCIE serves each with its own layer_image region; all of them lie in x 110.75..112.75, y 30.49..32.85 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • split@VSUP:GND|P3V3_HDMI4 nets cross the split between the GND and P3V3_HDMI planes on VSUP at 10 places, with no plane on the track's other side (fastest: SATA3_RX_N at 3 ns 10-90 %, suggested by its name)

      On VSUP the GND and P3V3_HDMI planes part, and 4 nets cross from one to the other at 10 place(s). The return current cannot follow a track across; it detours to wherever the two planes are joined (a stitching capacitor, or the source), and the loop it opens radiates and couples. One decision covers the boundary: whether it is stitched near these crossings, or the nets crossing it are slow enough not to care. Tracks that run ALONG this split, down the slot rather than across it, are a finding of their own: theirs is an impedance step, not a detour. At 0 of the 10 crossing(s) the track's other neighbour carries a plane, which the return can use there; 10 are on an outer layer, with no other neighbour. No crossing has a plane on the track's other side, so the whole return meets the break.

      • 'SATA3_RX_N' on BTM at (8.73, 59.49), 0.12 mm; other side: none: the signal layer is outermost
      • 'SATA3_RX_N' on BTM at (8.75, 59.32), 0.26 mm; other side: none: the signal layer is outermost
      • 'SATA3_RX_N' on BTM at (8.77, 59.4), 0.12 mm; other side: none: the signal layer is outermost
      • 'SATA3_RX_N' on BTM at (18.15, 62.28), 0.28 mm; other side: none: the signal layer is outermost
      • 'SATA3_RX_P' on BTM at (8.72, 60.51), 0.2 mm; other side: none: the signal layer is outermost
      • 'SATA3_RX_P' on BTM at (14.25, 62.4), 0.59 mm; other side: none: the signal layer is outermost
      • 'SATA3_TX_N' on BTM at (8.72, 63.53), 0.2 mm; other side: none: the signal layer is outermost
      • 'SATA3_TX_N' on BTM at (12.89, 63.53), 0.28 mm; other side: none: the signal layer is outermost
      • 'SATA3_TX_P' on BTM at (8.72, 63.77), 0.2 mm; other side: none: the signal layer is outermost
      • 'SATA3_TX_P' on BTM at (12.65, 63.77), 0.28 mm; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=split%40VSUP%3AGND%7CP3V3_HDMI serves each with its own layer_image region; all of them lie in x 7.62..19.29, y 58.24..64.77 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L1:101.7,110.6'SUS5_N' crosses where the outline of the GND plane on L1 is drawn back, at 1 place, the longest 0.33 mm (fastest: SUS5_N at 100 ps 10-90 %, ASSUMED)

      Along 'SUS5_N' on L2, the GND plane on L1 has 0.33 mm under the track with no copper, at (101.7, 110.6), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x -2.99..168.24, y -1.07..143.22 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'SUS5_N' on L2 at (101.7, 110.6), 0.33 mm over no copper; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=void%3AGND%40L1%3A101.7%2C110.6 serves each with its own layer_image region; all of them lie in x 100.59..102.82, y 109.49..111.72 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L1:105.34,110.41'SUS5_N' crosses where the outline of the GND plane on L1 is drawn back, at 1 place, the longest 1.6 mm (fastest: SUS5_N at 100 ps 10-90 %, ASSUMED)

      Along 'SUS5_N' on L2, the GND plane on L1 has 1.6 mm under the track with no copper, at (105.34, 110.41), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x -2.99..168.24, y -1.07..143.22 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'SUS5_N' on L2 at (105.34, 110.41), 1.6 mm over no copper; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=void%3AGND%40L1%3A105.34%2C110.41 serves each with its own layer_image region; all of them lie in x 103.71..107.21, y 109.41..111.64 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L1:108.92,112.5'SUS5_N' crosses where the outline of the GND plane on L1 is drawn back, at 1 place, the longest 1.02 mm (fastest: SUS5_N at 100 ps 10-90 %, ASSUMED)

      Along 'SUS5_N' on L2, the GND plane on L1 has 1.02 mm under the track with no copper, at (108.92, 112.5), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x -2.99..168.24, y -1.07..143.22 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'SUS5_N' on L2 at (108.92, 112.5), 1.02 mm over no copper; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=void%3AGND%40L1%3A108.92%2C112.5 serves each with its own layer_image region; all of them lie in x 107.31..110.14, y 111.27..113.73 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L1:109.93,116.15'SUS3_N' crosses where the outline of the GND plane on L1 is drawn back, at 1 place, the longest 0.34 mm (fastest: SUS3_N at 100 ps 10-90 %, ASSUMED)

      Along 'SUS3_N' on L2, the GND plane on L1 has 0.34 mm under the track with no copper, at (109.93, 116.15), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x -2.99..168.24, y -1.07..143.22 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'SUS3_N' on L2 at (109.93, 116.15), 0.34 mm over no copper; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=void%3AGND%40L1%3A109.93%2C116.15 serves each with its own layer_image region; all of them lie in x 108.76..111.1, y 115.15..117.15 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L1:115.74,104.64'THRMTRIP#' crosses where the outline of the GND plane on L1 is drawn back, at 1 place, the longest 3.35 mm (fastest: THRMTRIP# at 100 ps 10-90 %, ASSUMED)

      Along 'THRMTRIP#' on L2, the GND plane on L1 has 3.35 mm under the track with no copper, at (115.74, 104.64), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 2.87 mm). No hole cleared it: the outline of the pour at x -2.99..168.24, y -1.07..143.22 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'THRMTRIP#' on L2 at (115.74, 104.64), 3.35 mm, running ALONG the bare copper for 2.87 mm, not across it over no copper; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=void%3AGND%40L1%3A115.74%2C104.64 serves each with its own layer_image region; all of them lie in x 114.56..116.74, y 102.02..107.23 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L1:57.99,36.41'I2C_CK' crosses where the outline of the GND plane on L1 is drawn back, at 1 place, the longest 0.39 mm (fastest: I2C_CK at 10 ns 10-90 %, suggested by its name)

      Along 'I2C_CK' on L2, the GND plane on L1 has 0.39 mm under the track with no copper, at (57.99, 36.41), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x -2.99..168.24, y -1.07..143.22 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'I2C_CK' on L2 at (57.99, 36.41), 0.39 mm over no copper; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=void%3AGND%40L1%3A57.99%2C36.41 serves each with its own layer_image region; all of them lie in x 56.99..58.99, y 35.21..37.6 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L1:58.26,97.79'SUS_STAT#' crosses where the outline of the GND plane on L1 is drawn back, at 1 place, the longest 0.33 mm (fastest: SUS_STAT# at 100 ps 10-90 %, ASSUMED)

      Along 'SUS_STAT#' on L2, the GND plane on L1 has 0.33 mm under the track with no copper, at (58.26, 97.79), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x -2.99..168.24, y -1.07..143.22 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'SUS_STAT#' on L2 at (58.26, 97.79), 0.33 mm over no copper; other side: P3V3 on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=void%3AGND%40L1%3A58.26%2C97.79 serves each with its own layer_image region; all of them lie in x 57.26..59.26, y 96.63..98.96 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L1:62.81,61.88'TYPE0#' crosses where the outline of the GND plane on L1 is drawn back, at 1 place, the longest 8.75 mm (fastest: TYPE0# at 100 ps 10-90 %, ASSUMED)

      Along 'TYPE0#' on L2, the GND plane on L1 has 8.75 mm under the track with no copper, at (62.81, 61.88), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 8.37 mm). No hole cleared it: the outline of the pour at x -2.99..168.24, y -1.07..143.22 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'TYPE0#' on L2 at (62.81, 61.88), 8.75 mm, running ALONG the bare copper for 8.37 mm, not across it over no copper; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=void%3AGND%40L1%3A62.81%2C61.88 serves each with its own layer_image region; all of them lie in x 61.81..63.95, y 56.56..67.2 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L1:64.42,67.09'TYPE1#' crosses where the outline of the GND plane on L1 is drawn back, at 1 place, the longest 0.26 mm (fastest: TYPE1# at 100 ps 10-90 %, ASSUMED)

      Along 'TYPE1#' on L2, the GND plane on L1 has 0.26 mm under the track with no copper, at (64.42, 67.09), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x -2.99..168.24, y -1.07..143.22 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'TYPE1#' on L2 at (64.42, 67.09), 0.26 mm over no copper; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=void%3AGND%40L1%3A64.42%2C67.09 serves each with its own layer_image region; all of them lie in x 63.42..65.42, y 65.96..68.22 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L1:91.26,114.04'WDT' crosses where the outline of the GND plane on L1 is drawn back, at 1 place, the longest 4.19 mm (fastest: WDT at 100 ps 10-90 %, ASSUMED)

      Along 'WDT' on L2, the GND plane on L1 has 4.19 mm under the track with no copper, at (91.26, 114.04), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 1.19 mm). No hole cleared it: the outline of the pour at x -2.99..168.24, y -1.07..143.22 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'WDT' on L2 at (91.26, 114.04), 4.19 mm, running ALONG the bare copper for 1.19 mm, not across it over no copper; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=void%3AGND%40L1%3A91.26%2C114.04 serves each with its own layer_image region; all of them lie in x 88.16..94.36, y 113.04..115.04 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L1:hole 102.84,92.79|105.52,93.81'THRMTRIP#' crosses one void in the GND plane on L1 at 1 place, the longest 0.71 mm; 1 over tracks of other nets routed inside it (fastest: THRMTRIP# at 100 ps 10-90 %, ASSUMED)

      Along 'THRMTRIP#' on L2, the GND plane on L1 has 0.71 mm under the track with copper of USB_MUX_OEN, not a plane, at (103.92, 93.53), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 1 of the crossings pass over tracks of other nets routed inside the hole on the reference layer: the plane is absent there, and those tracks stand in it. What cleared it: the hole at x 102.84..105.52, y 92.79..93.81. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'THRMTRIP#' on L2 at (103.92, 93.53), 0.71 mm over copper of USB_MUX_OEN, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=void%3AGND%40L1%3Ahole%20102.84%2C92.79%7C105.52%2C93.81 serves each with its own layer_image region; all of them lie in x 102.92..104.92, y 91.94..94.66 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L1:hole 13.53,115.4|111.64,136.798 nets cross one void in the GND plane on L1 and the GND plane on L2 at 5 places, the longest 20.83 mm; 13 over tracks of other nets routed inside it (fastest: CTREFB at 100 ps 10-90 %, ASSUMED)

      Along 'SUS3_N' on L2, the GND plane on L1 has 20.83 mm under the track with copper of FPGA_ALERTN_5, SDA_5, not a plane, at (93.1, 116.15), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 13 of the crossings pass over tracks of other nets routed inside the hole on the reference layer: the plane is absent there, and those tracks stand in it. 5 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 19 mm). 5 places on 8 net(s) cross it, listed below, the longest first. What cleared it: the hole at x 13.53..111.64, y 115.4..136.79 and the hole at x 26.38..48.17, y 65.4..132.77. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • one crossing of two tracks, seen from each: 'PWRBTN#' on L2 at (92.26, 116.55), 17.57 mm, running ALONG the bare copper for 14.51 mm, not across it over copper of FPGA_ALERTN_5, SDA_5, SCL_5, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'SCL_5' on L1 at (92.26, 116.55), 15.15 mm, running ALONG the bare copper for 14.51 mm, not across it over copper of PWRBTN#, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'SDA_5' on L1 at (93.2, 116.15), 19.18 mm, running ALONG the bare copper for 17.6 mm, not across it over copper of PWRBTN#, SUS3_N, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'SUS3_N' on L2 at (93.1, 116.15), 20.83 mm, running ALONG the bare copper for 18.51 mm, not across it over copper of FPGA_ALERTN_5, SDA_5, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1
      • 'SUS_S4#' on L2 at (93.33, 115.76), 20.11 mm, running ALONG the bare copper for 19 mm, not across it over copper of FPGA_ALERTN_5, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1
      • one crossing of two tracks, seen from each: 'CTREFB' on L1 at (32.5, 129.82), 2.42 mm over copper of SDA_5, SCL_5, FPGA_ALERTN_5, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'FPGA_ALERTN_5' on L2 at (32.64, 129.59), 1.01 mm over copper of CTREFB, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'SCL_5' on L2 at (31.89, 129.59), 1.01 mm over copper of CTREFB, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'SDA_5' on L2 at (31.23, 129.59), 1.01 mm over copper of CTREFB, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1
      • one crossing of two tracks, seen from each: 'CTREFB' on L1 at (103.37, 125.12), 1.01 mm over copper of PWRBTN#, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'PWRBTN#' on L2 at (103.58, 125.35), 1.24 mm over copper of CTREFB, not a plane, to the end of the track; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1
      • one crossing of two tracks, seen from each: 'PWRBTN#' on L2 at (100.9, 120.77), 1.01 mm over copper of USB_23_OCN, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'USB_23_OCN' on L1 at (100.67, 120.68), 1.01 mm over copper of PWRBTN#, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=void%3AGND%40L1%3Ahole%2013.53%2C115.4%7C111.64%2C136.79 serves each with its own layer_image region; all of them lie in x 29.96..105.13, y 114.76..131.18 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L1:hole 133.03,21.42|137.31,34.553 nets cross one void in the GND plane on L1 and the GND plane on L2 at 1 place, the longest 10.67 mm; 3 over tracks of other nets routed inside it (fastest: PRSNT1# at 100 ps 10-90 %, ASSUMED)

      Along 'SCL_L' on L1, the GND plane on L2 has 10.67 mm under the track with copper of PRSNT1#, PRSNT2#, not a plane, at (135.25, 26.11), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 3 of the crossings pass over tracks of other nets routed inside the hole on the reference layer: the plane is absent there, and those tracks stand in it. 2 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 9.12 mm). What cleared it: the hole at x 125.24..137.91, y 11.31..43.27 and the hole at x 133.03..137.31, y 21.42..34.55. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • one crossing of two tracks, seen from each: 'PRSNT1#' on L2 at (133.77, 23.77), 1.01 mm over copper of SCL_L, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'PRSNT2#' on L2 at (135.41, 25.98), 10.29 mm, running ALONG the bare copper for 8.82 mm, not across it over copper of SCL_L, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'SCL_L' on L1 at (135.25, 26.11), 10.67 mm, running ALONG the bare copper for 9.12 mm, not across it over copper of PRSNT1#, PRSNT2#, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=void%3AGND%40L1%3Ahole%20133.03%2C21.42%7C137.31%2C34.55 serves each with its own layer_image region; all of them lie in x 132.18..138.18, y 22.04..33.38 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L1:hole 28.49,98.27|35.91,100.943 nets cross one void in the GND plane on L1 at 3 places, the longest 1.09 mm; 3 over tracks of other nets routed inside it (fastest: SCL_5 at 10 ns 10-90 %, suggested by its name)

      Along 'FPGA_ALERTN_5' on L2, the GND plane on L1 has 1.09 mm under the track with copper of P3V3, not a plane, at (30.82, 100.68), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 3 of the crossings pass over tracks of other nets routed inside the hole on the reference layer: the plane is absent there, and those tracks stand in it. 3 places on 3 net(s) cross it, listed below, the longest first. What cleared it: the hole at x 28.49..35.91, y 98.27..100.94. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'FPGA_ALERTN_5' on L2 at (30.82, 100.68), 1.09 mm over copper of P3V3, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1
      • 'SCL_5' on L2 at (30.35, 100.49), 0.77 mm over copper of P3V3, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1
      • 'SDA_5' on L2 at (30.04, 100.18), 0.77 mm over copper of P3V3, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=void%3AGND%40L1%3Ahole%2028.49%2C98.27%7C35.91%2C100.94 serves each with its own layer_image region; all of them lie in x 28.95..32.46, y 98.73..101.81 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2:103.88,111.87'SATA3_RX_P' crosses where the outline of the GND plane on L2 is drawn back, at 1 place, the longest 0.8 mm (fastest: SATA3_RX_P at 3 ns 10-90 %, suggested by its name)

      Along 'SATA3_RX_P' on L1, the GND plane on L2 has 0.8 mm under the track with no copper, at (103.88, 111.87), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x -2.99..168.24, y -1.07..143.22 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'SATA3_RX_P' on L1 at (103.88, 111.87), 0.8 mm over no copper; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=void%3AGND%40L2%3A103.88%2C111.87 serves each with its own layer_image region; all of them lie in x 102.51..105.22, y 110.63..112.95 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2:112.09,114.6'SATA1_TX_P' crosses where the outline of the GND plane on L2 is drawn back, at 1 place, the longest 0.21 mm (fastest: SATA1_TX_P at 3 ns 10-90 %, suggested by its name)

      Along 'SATA1_TX_P' on L1, the GND plane on L2 has 0.21 mm under the track with no copper, at (112.09, 114.6), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x -2.99..168.24, y -1.07..143.22 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'SATA1_TX_P' on L1 at (112.09, 114.6), 0.21 mm over no copper; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=void%3AGND%40L2%3A112.09%2C114.6 serves each with its own layer_image region; all of them lie in x 111.07..113.21, y 113.59..115.74 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2:115.92,101.45'W_DISABLE#' crosses where the outline of the GND plane on L2 is drawn back, at 1 place, the longest 2.3 mm (fastest: W_DISABLE# at 100 ps 10-90 %, ASSUMED)

      Along 'W_DISABLE#' on L1, the GND plane on L2 has 2.3 mm under the track with no copper, at (115.92, 101.45), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x -2.99..168.24, y -1.07..143.22 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'W_DISABLE#' on L1 at (115.92, 101.45), 2.3 mm over no copper; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=void%3AGND%40L2%3A115.92%2C101.45 serves each with its own layer_image region; all of them lie in x 114.92..116.92, y 99.3..103.6 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2:115.92,104.5'W_DISABLE#' crosses where the outline of the GND plane on L2 is drawn back, at 1 place, the longest 3.43 mm (fastest: W_DISABLE# at 100 ps 10-90 %, ASSUMED)

      Along 'W_DISABLE#' on L1, the GND plane on L2 has 3.43 mm under the track with no copper, at (115.92, 104.5), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 2.85 mm). No hole cleared it: the outline of the pour at x -2.99..168.24, y -1.07..143.22 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'W_DISABLE#' on L1 at (115.92, 104.5), 3.43 mm, running ALONG the bare copper for 2.85 mm, not across it over no copper; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=void%3AGND%40L2%3A115.92%2C104.5 serves each with its own layer_image region; all of them lie in x 114.92..117.04, y 101.87..107.25 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2:136.25,66.52'PCIE2_RX_P' crosses where the outline of the GND plane on L2 is drawn back, at 1 place, the longest 0.29 mm (fastest: PCIE2_RX_P at 3 ns 10-90 %, suggested by its name)

      Along 'PCIE2_RX_P' on L1, the GND plane on L2 has 0.29 mm under the track with no copper, at (136.25, 66.52), running to the end of the track. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x -2.99..168.24, y -1.07..143.22 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'PCIE2_RX_P' on L1 at (136.25, 66.52), 0.29 mm over no copper, to the end of the track; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=void%3AGND%40L2%3A136.25%2C66.52 serves each with its own layer_image region; all of them lie in x 135.16..137.36, y 65.4..67.62 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2:155.04,62.84'RX8_N' crosses where the outline of the GND plane on L2 is drawn back, at 1 place, the longest 0.49 mm (fastest: RX8_N at 3 ns 10-90 %, suggested by its name)

      Along 'RX8_N' on L1, the GND plane on L2 has 0.49 mm under the track with no copper, at (155.04, 62.84), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x -2.99..168.24, y -1.07..143.22 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RX8_N' on L1 at (155.04, 62.84), 0.49 mm over no copper; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=void%3AGND%40L2%3A155.04%2C62.84 serves each with its own layer_image region; all of them lie in x 153.98..156.13, y 61.78..64.16 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2:22.49,57.22'DDI3_PAIR0_N' crosses where the outline of the GND plane on L2 is drawn back, at 1 place, the longest 0.18 mm (fastest: DDI3_PAIR0_N at 100 ps 10-90 %, ASSUMED)

      Along 'DDI3_PAIR0_N' on L1, the GND plane on L2 has 0.18 mm under the track with no copper, at (22.49, 57.22), running to the end of the track. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x -2.99..168.24, y -1.07..143.22 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'DDI3_PAIR0_N' on L1 at (22.49, 57.22), 0.18 mm over no copper, to the end of the track; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=void%3AGND%40L2%3A22.49%2C57.22 serves each with its own layer_image region; all of them lie in x 21.45..23.55, y 56.15..58.3 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2:27.45,60.4'DDI3_PAIR3_N' crosses where the outline of the GND plane on L2 is drawn back, at 1 place, the longest 0.34 mm (fastest: DDI3_PAIR3_N at 100 ps 10-90 %, ASSUMED)

      Along 'DDI3_PAIR3_N' on L1, the GND plane on L2 has 0.34 mm under the track with no copper, at (27.45, 60.4), running to the end of the track. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x -2.99..168.24, y -1.07..143.22 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'DDI3_PAIR3_N' on L1 at (27.45, 60.4), 0.34 mm over no copper, to the end of the track; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=void%3AGND%40L2%3A27.45%2C60.4 serves each with its own layer_image region; all of them lie in x 26.23..28.56, y 59.36..61.44 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2:62.18,62.25'VGA_I2C_CK' crosses where the outline of the GND plane on L2 is drawn back, at 1 place, the longest 9.99 mm (fastest: VGA_I2C_CK at 10 ns 10-90 %, suggested by its name)

      Along 'VGA_I2C_CK' on L1, the GND plane on L2 has 9.99 mm under the track with no copper, at (62.18, 62.25), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 9.17 mm). No hole cleared it: the outline of the pour at x -2.99..168.24, y -1.07..143.22 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'VGA_I2C_CK' on L1 at (62.18, 62.25), 9.99 mm, running ALONG the bare copper for 9.17 mm, not across it over no copper; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=void%3AGND%40L2%3A62.18%2C62.25 serves each with its own layer_image region; all of them lie in x 61.18..63.18, y 56.26..68.24 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2:64.43,21.65'SWCLK_11' crosses where the outline of the GND plane on L2 is drawn back, at 1 place, the longest 5.26 mm (fastest: SWCLK_11 at 1 ns 10-90 %, suggested by its name)

      Along 'SWCLK_11' on L1, the GND plane on L2 has 5.26 mm under the track with no copper, at (64.43, 21.65), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 4.95 mm). No hole cleared it: the outline of the pour at x -2.99..168.24, y -1.07..143.22 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'SWCLK_11' on L1 at (64.43, 21.65), 5.26 mm, running ALONG the bare copper for 4.95 mm, not across it over no copper; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=void%3AGND%40L2%3A64.43%2C21.65 serves each with its own layer_image region; all of them lie in x 60.84..68.08, y 20.58..22.65 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2:72.49,106.18'PCIE4_TX_N' crosses where the outline of the GND plane on L2 is drawn back, at 1 place, the longest 1.16 mm (fastest: PCIE4_TX_N at 3 ns 10-90 %, suggested by its name)

      Along 'PCIE4_TX_N' on L1, the GND plane on L2 has 1.16 mm under the track with no copper, at (72.49, 106.18), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 0.49 mm). No hole cleared it: the outline of the pour at x -2.99..168.24, y -1.07..143.22 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'PCIE4_TX_N' on L1 at (72.49, 106.18), 1.16 mm, running ALONG the bare copper for 0.49 mm, not across it over no copper; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=void%3AGND%40L2%3A72.49%2C106.18 serves each with its own layer_image region; all of them lie in x 70.79..73.67, y 104.62..107.36 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2:74.19,107.88'PCIE4_TX_N' crosses where the outline of the GND plane on L2 is drawn back, at 1 place, the longest 1.3 mm (fastest: PCIE4_TX_N at 3 ns 10-90 %, suggested by its name)

      Along 'PCIE4_TX_N' on L1, the GND plane on L2 has 1.3 mm under the track with no copper, at (74.19, 107.88), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x -2.99..168.24, y -1.07..143.22 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'PCIE4_TX_N' on L1 at (74.19, 107.88), 1.3 mm over no copper; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=void%3AGND%40L2%3A74.19%2C107.88 serves each with its own layer_image region; all of them lie in x 72.73..75.65, y 106.42..109.34 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2:97.58,120.41'USB_1_RX_P' crosses where the outline of the GND plane on L2 is drawn back, at 1 place, the longest 0.88 mm (fastest: USB_1_RX_P at 500 ps 10-90 %, suggested by its name)

      Along 'USB_1_RX_P' on L1, the GND plane on L2 has 0.88 mm under the track with no copper, at (97.58, 120.41), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x -2.99..168.24, y -1.07..143.22 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'USB_1_RX_P' on L1 at (97.58, 120.41), 0.88 mm over no copper; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=void%3AGND%40L2%3A97.58%2C120.41 serves each with its own layer_image region; all of them lie in x 96.32..98.9, y 119.41..121.77 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2:hole 100.63,11.82|123.13,49.016 nets cross one void in the GND plane on L2 at 6 places, the longest 1.02 mm; 6 over tracks of other nets routed inside it (fastest: GA0 at 100 ps 10-90 %, ASSUMED)

      Along 'GA1' on L1, the GND plane on L2 has 1.02 mm under the track with copper of P2V5, not a plane, at (117.85, 16.1), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 6 of the crossings pass over tracks of other nets routed inside the hole on the reference layer: the plane is absent there, and those tracks stand in it. 6 places on 6 net(s) cross it, listed below, the longest first. What cleared it: the hole at x 100.63..123.13, y 11.82..49.01. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'ENABLE#' on L1 at (117.85, 16.9), 1.02 mm over copper of P2V5, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'GA0' on L1 at (117.85, 15.71), 1.02 mm over copper of P2V5, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'GA1' on L1 at (117.85, 16.1), 1.02 mm over copper of P2V5, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'GA2' on L1 at (117.85, 16.5), 1.02 mm over copper of P2V5, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'PRSNT1#' on L1 at (117.85, 15.34), 1.02 mm over copper of P2V5, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'PRSNT2#' on L1 at (117.85, 14.96), 1.02 mm over copper of P2V5, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=void%3AGND%40L2%3Ahole%20100.63%2C11.82%7C123.13%2C49.01 serves each with its own layer_image region; all of them lie in x 116.34..119.36, y 13.96..17.9 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2:hole 105.39,8.55|145.09,33.814 nets cross one void in the GND plane on L2 at 4 places, the longest 1.02 mm; 4 over tracks of other nets routed inside it (fastest: GA0 at 100 ps 10-90 %, ASSUMED)

      Along 'GA2' on L1, the GND plane on L2 has 1.02 mm under the track with copper of P3V3, not a plane, at (140.34, 19.68), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 4 of the crossings pass over tracks of other nets routed inside the hole on the reference layer: the plane is absent there, and those tracks stand in it. 4 places on 4 net(s) cross it, listed below, the longest first. What cleared it: the hole at x 105.39..145.09, y 8.55..33.81. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'ENABLE#' on L1 at (140.34, 20.05), 1.02 mm over copper of P3V3, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'GA0' on L1 at (140.34, 13.76), 1.02 mm over copper of P3V3, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'GA1' on L1 at (140.34, 19.29), 1.02 mm over copper of P3V3, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'GA2' on L1 at (140.34, 19.68), 1.02 mm over copper of P3V3, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=void%3AGND%40L2%3Ahole%20105.39%2C8.55%7C145.09%2C33.81 serves each with its own layer_image region; all of them lie in x 138.83..141.85, y 12.76..21.05 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2:hole 125.24,11.31|137.91,43.276 nets cross one void in the GND plane on L1 and the GND plane on L2 at 8 places, the longest 2.14 mm; 14 over tracks of other nets routed inside it (fastest: GA0 at 100 ps 10-90 %, ASSUMED)

      Along 'PRSNT2#' on L1, the GND plane on L2 has 2.14 mm under the track with copper of P1V0_PCIE, not a plane, at (129.36, 14.96), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 14 of the crossings pass over tracks of other nets routed inside the hole on the reference layer: the plane is absent there, and those tracks stand in it. 8 places on 6 net(s) cross it, listed below, the longest first. What cleared it: the hole at x 125.24..137.91, y 11.31..43.27. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'GA0' on L1 at (128.61, 15.71), 2.14 mm over copper of P1V0_PCIE, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'GA1' on L1 at (128.22, 16.1), 2.14 mm over copper of P1V0_PCIE, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'GA2' on L1 at (127.82, 16.5), 2.14 mm over copper of P1V0_PCIE, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'PRSNT1#' on L1 at (128.98, 15.34), 2.14 mm over copper of P1V0_PCIE, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'PRSNT2#' on L1 at (129.36, 14.96), 2.14 mm over copper of P1V0_PCIE, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'ENABLE#' on L1 at (127.42, 16.9), 2.14 mm over copper of P1V0_PCIE, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • one crossing of two tracks, seen from each: 'ENABLE#' on L1 at (131.65, 18.37), 1.99 mm over copper of PRSNT2#, PRSNT1#, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'GA1' on L1 at (131.65, 17.27), 1.99 mm over copper of PRSNT2#, PRSNT1#, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'GA2' on L1 at (131.65, 17.85), 1.99 mm over copper of PRSNT2#, PRSNT1#, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'PRSNT1#' on L2 at (131.99, 17.29), 2.11 mm over copper of GA1, GA2, ENABLE#, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'PRSNT2#' on L2 at (131.3, 16.6), 2.11 mm over copper of GA1, GA2, ENABLE#, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1
      • one crossing of two tracks, seen from each: 'GA0' on L1 at (131.65, 15.71), 1.4 mm over copper of PRSNT2#, PRSNT1#, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'PRSNT1#' on L1 at (131.55, 15.34), 0.92 mm over copper of PRSNT2#, not a plane, to the end of the track; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'PRSNT2#' on L2 at (131.3, 15.08), 1.15 mm over copper of PRSNT1#, GA0, not a plane, to the end of the track; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=void%3AGND%40L2%3Ahole%20125.24%2C11.31%7C137.91%2C43.27 serves each with its own layer_image region; all of them lie in x 125.35..133.35, y 13.67..20.21 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2:hole 26.38,65.4|48.17,132.7717 nets cross one void in the GND plane on L1 and the GND plane on L2 at 3 places, the longest 6.03 mm; 23 over tracks of other nets routed inside it (fastest: DDI2_CTRL_AUX_N at 100 ps 10-90 %, ASSUMED)

      Along 'SDA_5' on L2, the GND plane on L1 has 6.03 mm under the track with copper of DDI3_PAIR3_N, DDI3_PAIR3_P, DDI3_PAIR2_N, DDI3_PAIR2_P, DDI3_PAIR1_N, DDI3_PAIR1_P, not a plane, at (31.22, 84.8), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 23 of the crossings pass over tracks of other nets routed inside the hole on the reference layer: the plane is absent there, and those tracks stand in it. 3 places on 17 net(s) cross it, listed below, the longest first. What cleared it: the hole at x 26.38..48.17, y 65.4..132.77. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • one crossing of two tracks, seen from each: 'DDI3_PAIR1_N' on L1 at (31.88, 87.41), 1.6 mm over copper of SDA_5, SCL_5, FPGA_ALERTN_5, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'DDI3_PAIR1_P' on L1 at (31.88, 87.67), 1.6 mm over copper of SDA_5, SCL_5, FPGA_ALERTN_5, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'DDI3_PAIR2_N' on L1 at (31.88, 85.9), 1.63 mm over copper of SDA_5, SCL_5, FPGA_ALERTN_5, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'DDI3_PAIR2_P' on L1 at (31.88, 86.16), 1.62 mm over copper of SDA_5, SCL_5, FPGA_ALERTN_5, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'DDI3_PAIR3_N' on L1 at (31.88, 83.55), 1.73 mm over copper of SCL_5, SDA_5, FPGA_ALERTN_5, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'DDI3_PAIR3_P' on L1 at (31.88, 83.81), 1.68 mm over copper of SCL_5, SDA_5, FPGA_ALERTN_5, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'FPGA_ALERTN_5' on L2 at (32.11, 84.86), 5.64 mm over copper of DDI3_PAIR3_N, DDI3_PAIR3_P, DDI3_PAIR2_N, DDI3_PAIR2_P, DDI3_PAIR1_N, DDI3_PAIR1_P, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'SCL_5' on L2 at (31.65, 84.85), 5.64 mm over copper of DDI3_PAIR3_N, DDI3_PAIR3_P, DDI3_PAIR2_N, DDI3_PAIR2_P, DDI3_PAIR1_N, DDI3_PAIR1_P, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'SDA_5' on L2 at (31.22, 84.8), 6.03 mm over copper of DDI3_PAIR3_N, DDI3_PAIR3_P, DDI3_PAIR2_N, DDI3_PAIR2_P, DDI3_PAIR1_N, DDI3_PAIR1_P, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1
      • one crossing of two tracks, seen from each: 'DDI2_CTRL_AUX_N' on L1 at (31.88, 93.68), 1.6 mm over copper of SDA_5, SCL_5, FPGA_ALERTN_5, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'DDI2_CTRL_AUX_P' on L1 at (31.88, 93.42), 1.6 mm over copper of SDA_5, SCL_5, FPGA_ALERTN_5, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'DDI3_CTRL_AUX_N' on L1 at (31.88, 92.06), 1.6 mm over copper of SDA_5, SCL_5, FPGA_ALERTN_5, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'DDI3_CTRL_AUX_P' on L1 at (31.88, 91.8), 1.6 mm over copper of SDA_5, SCL_5, FPGA_ALERTN_5, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'DDI3_PAIR0_N' on L1 at (31.88, 90.16), 1.6 mm over copper of SDA_5, SCL_5, FPGA_ALERTN_5, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'DDI3_PAIR0_P' on L1 at (31.88, 90.42), 1.6 mm over copper of SDA_5, SCL_5, FPGA_ALERTN_5, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'FPGA_ALERTN_5' on L2 at (32.11, 91.11), 5.03 mm over copper of DDI3_PAIR0_N, DDI3_PAIR0_P, DDI3_CTRL_AUX_P, DDI3_CTRL_AUX_N, DDI2_CTRL_AUX_P, DDI2_CTRL_AUX_N, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'SCL_5' on L2 at (31.65, 91.11), 5.03 mm over copper of DDI3_PAIR0_N, DDI3_PAIR0_P, DDI3_CTRL_AUX_P, DDI3_CTRL_AUX_N, DDI2_CTRL_AUX_P, DDI2_CTRL_AUX_N, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'SDA_5' on L2 at (31.22, 91.11), 5.03 mm over copper of DDI3_PAIR0_N, DDI3_PAIR0_P, DDI3_CTRL_AUX_P, DDI3_CTRL_AUX_N, DDI2_CTRL_AUX_P, DDI2_CTRL_AUX_N, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1
      • one crossing of two tracks, seen from each: 'FPGA_ALERTN_5' on L2 at (46.2, 67.37), 2.13 mm over copper of PWRBTN#, THRM#, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'PWRBTN#' on L1 at (44.82, 66.97), 2.6 mm over copper of SDA_5, SCL_5, FPGA_ALERTN_5, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2 / 'SCL_5' on L2 at (45.68, 66.72), 1.32 mm over copper of PWRBTN#, THRM#, not a plane; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'SDA_5' on L2 at (44.97, 66.2), 1.17 mm over copper of PWRBTN#, THRM#, not a plane, to the end of the track; other side: GND on VSUP, 0.2 mm from the track against 0.82 mm to L1: 20% of the return on L1 / 'THRM#' on L1 at (46.04, 66.95), 2.93 mm over copper of SDA_5, SCL_5, FPGA_ALERTN_5, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=void%3AGND%40L2%3Ahole%2026.38%2C65.4%7C48.17%2C132.77 serves each with its own layer_image region; all of them lie in x 29.86..48.12, y 64.91..95.44 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

    • void:GND@L2:hole 3.54,60.58|25.73,101.5910 nets cross one void in the GND plane on L2 at 19 places, the longest 18.19 mm; 19 over tracks of other nets routed inside it (fastest: DDI2_CTRL_AUX_N at 100 ps 10-90 %, ASSUMED)

      Along 'DDI3_PAIR0_N' on L1, the GND plane on L2 has 18.19 mm under the track with copper of P5V0, not a plane, at (24.71, 77.71), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 19 of the crossings pass over tracks of other nets routed inside the hole on the reference layer: the plane is absent there, and those tracks stand in it. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 14.87 mm). 19 places on 10 net(s) cross it, listed below, the longest first. What cleared it: the hole at x 3.54..25.73, y 60.58..101.59. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 20% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'DDI3_PAIR0_N' on L1 at (24.71, 77.71), 18.19 mm, running ALONG the bare copper for 14.87 mm, not across it over copper of P5V0, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'DSB_D_RXA_P' on L1 at (15.9, 75.46), 4.7 mm over copper of NetC154A_1, not a plane, to the end of the track; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'DSB_D_RXA_N' on L1 at (16.16, 75.48), 3.93 mm over copper of NetC154A_1, not a plane, to the end of the track; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'DDI3_PAIR0_P' on L1 at (25.34, 87.06), 1.6 mm over copper of P5V0, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'DDI3_PAIR0_P' on L1 at (24.45, 69.82), 1.58 mm over copper of P5V0, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'DDI2_CTRL_AUX_N' on L1 at (20.22, 65.47), 1.44 mm over copper of P5V0, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'DDI2_CTRL_AUX_P' on L1 at (20.48, 65.73), 1.44 mm over copper of P5V0, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'DDI2_CTRL_AUX_P' on L1 at (20.48, 69.79), 1.08 mm over copper of P3V3, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'DDI2_CTRL_AUX_N' on L1 at (20.22, 69.79), 1.02 mm over copper of P3V3, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'DSB_D_TXB_N' on L1 at (15.91, 93.34), 0.82 mm over copper of NetC154B_1, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'DSB_D_TXB_P' on L1 at (16.17, 93.34), 0.82 mm over copper of NetC154B_1, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • 'NetCON9_42' on L1 at (5.63, 72.49), 0.82 mm over copper of NetC154A_1, not a plane; other side: GND on GND, 0.2 mm from the track against 0.82 mm to L2: 20% of the return on L2
      • and 7 more

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/28/reference-planes?group=void%3AGND%40L2%3Ahole%203.54%2C60.58%7C25.73%2C101.59 serves each with its own layer_image region; all of them lie in x 4.2..26.73, y 63.75..94.75 mm (board frame, Y up).

      Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.

Main parts

Part numberMakerDescriptionWhere
160mA-48VFuseF1
3-1827233-6COM Express Type 6CON18
7A-25.000MAAJ-Tor QSDG25M000-TXCminiature crystal oscillator (Maritex)X3
AMC170 Poles, Extended Side, Advanced Mezzanine Card Plug Connector, AMCCON1
AT24MAC602-XHM-TSerial 2K EEPROM+ 48bit MACIC27
AT25F512B-SSH-B512kBit 2.7V Minimum SPI Serial Flash MemoryIC20
BCP69PNP TransistorT1
BHMT16SMaritex BHMT16SCON3
BLUELED Blue Avago C120LD6
BSS138T2
Buzzer CFG06Buzzer (Maritex)BUZ1
CBTL02043ABQ3.3 V, 2 differential channel, 2 : 1 MUX/deMUX switch for PCIe Gen3IC34
CDCLVP1208RHDT2:8 Low Additive Jitter LVPECL BufferIC9
CM2009VGA companion chipIC12
CR1220 batteryCR-21220 Battery 3V 35mAhBAT1
CR1220 Keystone 3000 (1650692)CR-1220 Battery holderBH1
DMN2009LSS-13NMOS 30V, 9mR, 14A, 3W, Vgsth 1VT4
DMP2022LSS-13PMOS 30V, 20mR, 7A, 2.5WT3
ERM8-075-05.0-S-DV-TRRUGGED HIGH SPEED HEADERCON4
goldpin 1.27 2x5PBTD10SJP2
HDMIConnector HDMI 19 Male + 1 ShieldCON17
LD1117DT33TR3-Terminal Regulator 1=GND 2=IN 3=OUTIC7
LPC1764FBD100ARM Cortex-M3 procesorIC1
MCC-SIM or CARD-SIMEE8C15Sim Card Holder with ejector(Tme,maritex)CON11
Mini DPConnector Mini DisplayPort 20 Male + 1 ShieldCON8
MM60-52B1-E1-R650mini PCIE 5.9mm connector (Farnell)CON9
MM60-EZH059-B5-R650mini PCIE 5.9mm latch(Farnell)CON10
NHI350AM2 SLJ3SEthernet Controller I350IC18
PEX8617-BA50BCPCI Express Switch, Gen 2, 16 Lane, 4 PortIC37
PI3VDP411LSZBEDDI to HDMI translatorIC11
PLTD10SGoldpin 2.54mm, male headerJP1
Push ButtonPush-Button Switch SPDTPB1
QSDG8M000-TXCminiature crystal oscillator (Maritex) QSDG8M000-TXCX1
SS141A 80V shottky diode (Maritex)D2
STM809SWX6F2.93V Reset circuitIC3
TPS54620RGYR17V Input, 6A Output, Synchronous Step Down SwitcherIC35
TS3USB221DRCRIC23
47391-20001.27mm Pitch External Serial ATA Plug with Flanged Shell, Bottom Mount, Right AngleCON6, CON7
AP133-WG-7LDO, 300mA, ADJIC26, IC36
CP2102-GMSingle-Chip USB to UART BridgeIC21A, IC21B

About this design

Design
AMC CPU COM6 — OHWR0026 R1
Designed in
Altium Designer
Board
6 copper layers, 173.4 × 148.6 mm, 859 components, 842 nets
Licence
CERN-OHL-1.1
Source
https://gitlab.com/ohwr/project/amc-cpu-com6 at commit bdc6b0b17927
Attribution
CERN Open Hardware Repository, project ohwr/project/amc-cpu-com6 (commit bdc6b0b1792703b1415ab85fb32a22c4a69b13d6, 2025-04-09). Licence: CERN-OHL-1.1. Source: https://gitlab.com/ohwr/project/amc-cpu-com6. This is a snapshot of the copy published on the OHWR GitLab pages (R1), not CERN's released record. CERN's source of truth is EDMS (https://edms.cern.ch), and the current release may be newer.
Reviewed with
Probe by E# (E-Sharp AB)