FMC CONN TESTER
OHWR0009 · revision R1
FMC CONN TESTER (OHWR0009 R1) is an open-hardware circuit board from the CERN Open Hardware Repository, designed in Altium Designer: a 4-layer board of 76.5 × 69 mm with 142 components and 205 nets, published under CERN-OHL-1.1.
review 84% walked · 17 findings: 8 major · 9 minor (53 items)
Open in the interactive viewerRead the full review

Design review
Probe recorded 17 findings: 8 major · 9 minor (53 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.
GPIO expanders IC1-IC5: 10 FMC lines sit on MCP23017 pins GPA7/GPB7, which current MCP23017 silicon makes output-only, so the tester cannot read them back
Ten FMC lines sit on MCP23017 pins GPA7/GPB7 of IC1-IC5, which the current MCP23017 datasheet makes output-only, so the tester cannot read back what the carrier drives on them.
Where it is
The tester exercises FMC user I/O through six MCP23017s, using every port pin as a bidirectional test point. The current MCP23017 datasheet (DS20001952D) restricts GPA7 (SSOP pin 28) and GPB7 (SSOP pin 8) to output only on the I2C part (p.1, pin table p.11).
Expander GPA7 (pin 28) GPB7 (pin 8) IC1 IO_VADJ_51 IO_VADJ_53 IC2 IO_VADJ_45 IO_VADJ_56 IC3 IO_VADJ_17 IO_VADJ_66 IC4 IO_VADJ_61 IO_VADJ_14 IC5 IO_VADJ_5 IO_VADJ_26 Each line goes straight to a J1 contact. IC6 pins 8 and 28 are unconnected.
Why it matters
With parts bought against today's datasheet, the tester can drive these ten lines toward the carrier but cannot sense a level the carrier drives on them. The carrier-to-mezzanine direction of those contacts goes untested, or reads back wrong, depending on the firmware. The 2011 design predates the restriction.
BAT54S went end-of-life (Obsolete)
Vendor (DigiKey) lifecycle for BAT54S (onsemi's listing) changed from "Active" to "Obsolete" since this board was reviewed. Placed as D1, D2, D3, D4, D5, D6. A sourcing/longevity risk; consider a replacement before production.
- concernCON-001majorOpen
[eol:BAT54S:Obsolete] BAT54S lifecycle changed from "Active" to "Obsolete" since this board was reviewed: OHWR0009 R1 FMC CONN TESTER. A sourcing and longevity risk. Should this be replaced before the next build?
- PartLifecyclemajorOpen
BAT54S on 6 placements (D1, D2, D3, D4, D5, D6): the distributor catalogue reports "Obsolete" for onsemi's BAT54S
BAT54S on 6 placements (D1, D2, D3, D4, D5, D6): the distributor catalogue reports "Obsolete" for onsemi's BAT54S — a sourcing/longevity risk to confirm against the MANUFACTURER before acting. This board's BOM names FAIRCHILD SEMICONDUCTOR, and that is one line with onsemi: ON Semiconductor completed its acquisition of Fairchild Semiconductor on 2016-09-19 and renamed itself onsemi on 2021-08-05. 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/BAT54S/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-11-23, 2,914 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.
At D1
- DecapViaFanoutmajorOpen
DecapViaFanout: 2 components×2
Checked by the review, stands · Claude walker W3 (Cern session) — Checked: the fan-out length is read from the copper as stated. The 0.5 nH limit is Probe's starting value, not a datasheet or vendor requirement on file; whether it matters depends on this capacitor's role in the rail's PDN target. Left for the owner.
At C4, C49
Each finding, with its own headline
C4C4 on 'P3V3': its rail pad reaches its via over 0.00 mm of track and its ground pad over 2.86 mm, adding about 0.94 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads
C4 on 'P3V3': its rail pad reaches its via over 0.00 mm of track and its ground pad over 2.86 mm, adding about 0.94 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads. C4.1 (rail) runs 0.00 mm along its copper to its nearest via, beside the pad; C4.2 (ground) runs 2.86 mm along its copper to its nearest via, 1.86 mm past the 1 mm beside the pad: 0.94 nH. 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.94 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.34 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 1.22 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.
C49C49 on 'VADJ': its rail pad reaches its via over 2.53 mm of track and its ground pad over 1.55 mm, adding about 1.05 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads
C49 on 'VADJ': its rail pad reaches its via over 2.53 mm of track and its ground pad over 1.55 mm, adding about 1.05 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads. C49.2 (rail) runs 2.53 mm along its copper to its nearest via, 1.53 mm past the 1 mm beside the pad: 0.78 nH; C49.1 (ground) runs 1.55 mm along its copper to its nearest via, 0.55 mm past the 1 mm beside the pad: 0.28 nH. 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): 1.05 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.34 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 1.22 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.
- PartLifecyclemajorOpen
PartLifecycle: 2 part numbers×2
2 Obsolete · on 2 placements
At IC9, J2
Each finding, with its own headline
IC9TLC274CD on IC9: the distributor catalogue reports "Obsolete" for Texas Instruments's TLC274CD
TLC274CD on IC9: the distributor catalogue reports "Obsolete" for Texas Instruments's TLC274CD — a sourcing/longevity risk to confirm against the MANUFACTURER before acting. That is the maker this board's BOM names (TEXAS INSTRUMENTS). 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/TLC274CD/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-17, 1,002 day(s) ago), so this is a substitution rather than a buy. The distributor reports 12 left. No approved alternate is recorded for this position.
J25607-4200-SH on J2: the distributor catalogue reports "Obsolete" for 3M's 5607-4200-SH
5607-4200-SH on J2: the distributor catalogue reports "Obsolete" for 3M's 5607-4200-SH — a sourcing/longevity risk to confirm against the MANUFACTURER before acting. That is the maker this board's BOM names (3M). 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/5607-4200-SH/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.
- ReferencePlaneDiscontinuitymajorOpen
ReferencePlaneDiscontinuity: 28 boards×28
Checked by the review, stands · Claude walker W3 (Cern session) — Checked: the reference break is read from the copper as stated. Whether it matters depends on the signal's edge rate and the receiver's margin, which no datasheet or app note on file fixes for this net; the impedance step and reflection figures are Probe's model, and the thresholds are its starting values. Layout practice, not a datasheet requirement. Left for the owner.
At along@TOP_LAYER:GND|P1V8, refchange:GND|P1V8, refchange:GND|P3V3, refchange:GND|VADJ, split@L2:P1V8|P3V3, split@L2:P3V3|VADJ and 22 more
Each finding, with its own headline
along@TOP_LAYER:GND|P1V83 nets run ALONG the split between the GND and P1V8 planes on TOP_LAYER at 3 places, the longest 1.36 mm; the impedance rises from 68 ohm to 79 ohm there at worst, 7 % of each edge reflected (fastest: IO_VADJ_26 at 100 ps 10-90 %, ASSUMED)
On TOP_LAYER the GND and P1V8 planes part, and 3 nets run down the slot between them at 3 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 68 ohm; along the slot 71 ohm to 79 ohm, reflecting up to 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 112 ohm). At 2 of the 3 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.
- 'IO_VADJ_26' on L2 at (104.84, 72.63), 1.36 mm, running ALONG the split for 1.36 mm, not across it, 68 ohm over solid plane, 79 ohm along it: 7 % of each edge reflected; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'CLK1_M2C_P' on L2 at (104.89, 72.96), 1.36 mm, running ALONG the split for 1.36 mm, not across it, 68 ohm over solid plane, 72 ohm along it: 2.3 % of each edge reflected; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'IO_VADJ_5' on L2 at (104.4, 76.46), 1.3 mm, running ALONG the split for 1.14 mm, not across it, 68 ohm over solid plane, 71 ohm along it: 1.8 % of each edge reflected; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/12/reference-planes?group=along%40TOP_LAYER%3AGND%7CP1V8 serves each with its own layer_image region; all of them lie in x 102.76..106.57, y 71.63..77.46 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|P1V87 nets change reference between GND and P1V8 at 7 vias, none with a reference that continues across (fastest: NetIC6_18 at 100 ps 10-90 %, ASSUMED)
At 7 via(s), on 7 net(s), the signal leaves a layer referenced by one of GND and P1V8 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: 7 with none. 7 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 P1V8 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.
- 'XPT_I6_N' at (111.2, 79.56), TOP_LAYER -> BOTTOM_LAYER: P1V8 on L2 to GND on PLANE_L3GND; pure, no reference continues across; stitching none, 55.2 mm of track past the via on BOTTOM_LAYER: 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 P1V8 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.
- 'XPT_I6_P' at (111.2, 80.4), TOP_LAYER -> BOTTOM_LAYER: P1V8 on L2 to GND on PLANE_L3GND; pure, no reference continues across; stitching none, 54.0 mm of track past the via on BOTTOM_LAYER: 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 P1V8 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.
- 'XPT_I8_P' at (104.32, 82.62), TOP_LAYER -> BOTTOM_LAYER: P1V8 on L2 to GND on PLANE_L3GND; pure, no reference continues across; stitching none, 31.2 mm of track past the via on BOTTOM_LAYER: 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 P1V8 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.
- 'XPT_I8_N' at (104.32, 83.46), TOP_LAYER -> BOTTOM_LAYER: P1V8 on L2 to GND on PLANE_L3GND; pure, no reference continues across; stitching none, 31.2 mm of track past the via on BOTTOM_LAYER: 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 P1V8 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.
- 'XPT_I4_N' at (114.78, 95.94), TOP_LAYER -> BOTTOM_LAYER: P1V8 on L2 to GND on PLANE_L3GND; pure, no reference continues across; stitching none, 23.1 mm of track past the via on BOTTOM_LAYER: 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 P1V8 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.
- 'XPT_I4_P' at (115.72, 95.92), TOP_LAYER -> BOTTOM_LAYER: P1V8 on L2 to GND on PLANE_L3GND; pure, no reference continues across; stitching none, 22.5 mm of track past the via on BOTTOM_LAYER: 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 P1V8 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_18' at (101.67, 86.47), TOP_LAYER -> BOTTOM_LAYER: P1V8 on L2 to GND on PLANE_L3GND; pure, no reference continues across; stitching none, 1.6 mm of track past the via on BOTTOM_LAYER: 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 P1V8 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/12/reference-planes?group=refchange%3AGND%7CP1V8 serves each with its own layer_image region; all of them lie in x 99.67..117.72, y 77.56..97.94 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|P3V385 nets change reference between GND and P3V3 at 97 vias, none with a reference that continues across (fastest: ADC_IN2 at 100 ps 10-90 %, ASSUMED)
At 97 via(s), on 85 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: 97 with none. 97 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.
- 'XPT_O8_P' at (102.77, 89.36), TOP_LAYER -> BOTTOM_LAYER: P3V3 on L2 to GND on PLANE_L3GND; pure, no reference continues across; stitching none, 161.9 mm of track past the via on BOTTOM_LAYER: 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.
- 'IO_VADJ_71' at (135.41, 89.62), TOP_LAYER -> L2: P3V3 on L2 to GND on PLANE_L3GND; pure, no reference continues across; stitching none, 86.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.
- 'IO_VADJ_79' at (139.22, 76.89), TOP_LAYER -> L2: P3V3 on L2 to GND on PLANE_L3GND; pure, no reference continues across; stitching none, 79.0 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.
- 'IO_VADJ_4' at (132.89, 89.59), TOP_LAYER -> L2: P3V3 on L2 to GND on PLANE_L3GND; pure, no reference continues across; stitching none, 78.4 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.
- 'IO_VADJ_26' at (134.16, 87.03), TOP_LAYER -> L2: P3V3 on L2 to GND on PLANE_L3GND; pure, no reference continues across; stitching none, 71.9 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.
- 'IO_VADJ_62' at (133.96, 74.71), TOP_LAYER -> L2: P3V3 on L2 to GND on PLANE_L3GND; pure, no reference continues across; stitching none, 71.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 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.
- 'IO_VADJ_75' at (137.95, 99.73), TOP_LAYER -> L2: P3V3 on L2 to GND on PLANE_L3GND; pure, no reference continues across; stitching none, 71.0 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.
- 'IO_VADJ_54' at (137.95, 98.48), TOP_LAYER -> L2: P3V3 on L2 to GND on PLANE_L3GND; pure, no reference continues across; stitching none, 66.0 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.
- 'IO_VADJ_55' at (136.73, 99.73), TOP_LAYER -> L2: P3V3 on L2 to GND on PLANE_L3GND; pure, no reference continues across; stitching none, 65.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 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.
- 'IO_VADJ_5' at (131.62, 89.62), TOP_LAYER -> L2: P3V3 on L2 to GND on PLANE_L3GND; pure, no reference continues across; stitching none, 59.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 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.
- 'IO_VADJ_65' at (136.68, 114.99), TOP_LAYER -> L2: P3V3 on L2 to GND on PLANE_L3GND; pure, no reference continues across; stitching none, 58.8 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.
- 'FMC_SCL' at (137.95, 113.72), TOP_LAYER -> L2: P3V3 on L2 to GND on PLANE_L3GND; pure, no reference continues across; stitching none, 58.1 mm of track past the via on L2: 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.
- and 85 more
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/12/reference-planes?group=refchange%3AGND%7CP3V3 serves each with its own layer_image region; all of them lie in x 100.39..143.76, y 72.71..135.99 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|VADJ33 nets change reference between GND and VADJ at 37 vias, none with a reference that continues across (fastest: IO_VADJ_1 at 100 ps 10-90 %, ASSUMED)
At 37 via(s), on 33 net(s), the signal leaves a layer referenced by one of GND and VADJ 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: 37 with none. 37 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 VADJ 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.
- 'IO_VADJ_79' at (84.68, 92.95), TOP_LAYER -> L2: VADJ on L2 to GND on PLANE_L3GND; pure, no reference continues across; stitching none, 79.0 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 VADJ 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.
- 'IO_VADJ_56' at (73.76, 102.19), TOP_LAYER -> L2: VADJ on L2 to GND on PLANE_L3GND; pure, no reference continues across; stitching none, 69.7 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 VADJ 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.
- 'IO_VADJ_54' at (79.6, 104.43), TOP_LAYER -> L2: VADJ on L2 to GND on PLANE_L3GND; pure, no reference continues across; stitching none, 66.0 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 VADJ 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.
- 'IO_VADJ_55' at (79.02, 103.69), TOP_LAYER -> L2: VADJ on L2 to GND on PLANE_L3GND; pure, no reference continues across; stitching none, 65.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 and VADJ 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: C34 (100 nF 0603) 2.7 mm away: 1.22 nH in the 1.000 mm cavity + 0.51 nH ESL + 0.83 nH mounting (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 1.22 mm depth, ASSUMED): 80.5 ohm at the knee, 161 % of 50 ohm (assumed track impedance). None.
- 'CLK1_M2C_N' at (88.14, 88.78), TOP_LAYER -> L2: VADJ on L2 to GND on PLANE_L3GND; pure, no reference continues across; stitching none, 62.5 mm of track past the via on L2: At the 5 GHz knee of a 100 ps edge (1 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. GND and VADJ 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.
- 'IO_VADJ_24' at (91.62, 90.33), TOP_LAYER -> L2: VADJ on L2 to GND on PLANE_L3GND; pure, no reference continues across; stitching none, 61.2 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 VADJ 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.
- 'IO_VADJ_5' at (91.59, 93), TOP_LAYER -> L2: VADJ on L2 to GND on PLANE_L3GND; pure, no reference continues across; stitching none, 59.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 and VADJ 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.
- 'IO_VADJ_11' at (80.77, 104.48), TOP_LAYER -> L2: VADJ on L2 to GND on PLANE_L3GND; pure, no reference continues across; stitching none, 58.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 and VADJ 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.
- 'FMC_SCL' at (97.36, 93.15), TOP_LAYER -> L2: VADJ on L2 to GND on PLANE_L3GND; pure, no reference continues across; stitching none, 58.1 mm of track past the via on L2: 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 VADJ 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.
- 'IO_VADJ_10' at (80.19, 103.69), TOP_LAYER -> L2: VADJ on L2 to GND on PLANE_L3GND; pure, no reference continues across; stitching none, 57.9 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 VADJ 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.
- 'IO_VADJ_51' at (86.31, 97.21), TOP_LAYER -> L2: VADJ on L2 to GND on PLANE_L3GND; pure, no reference continues across; stitching none, 57.4 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 VADJ 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.
- 'IO_VADJ_32' at (81.28, 105.37), TOP_LAYER -> L2: VADJ on L2 to GND on PLANE_L3GND; pure, no reference continues across; stitching none, 56.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 and VADJ 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.
- and 25 more
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/12/reference-planes?group=refchange%3AGND%7CVADJ serves each with its own layer_image region; all of them lie in x 70.18..125.47, y 81.9..128.93 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@L2:P1V8|P3V32 nets cross the split between the P1V8 and P3V3 planes on L2 at 2 places, with no plane on the track's other side (fastest: XPT_I7_N at 100 ps 10-90 %, ASSUMED)
On L2 the P1V8 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 0 of the 2 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. No crossing has a plane on the track's other side, so the whole return meets the break.
- 'XPT_I7_N' on TOP_LAYER at (116.28, 80.21), 0.23 mm; other side: none: the signal layer is outermost
- 'XPT_I8_N' on TOP_LAYER at (113.22, 83.22), 0.16 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/12/reference-planes?group=split%40L2%3AP1V8%7CP3V3 serves each with its own layer_image region; all of them lie in x 112.22..117.28, y 79.09..84.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@L2:P3V3|VADJ5 nets cross the split between the P3V3 and VADJ planes on L2 at 9 places, with no plane on the track's other side (fastest: ADC_IN1 at 100 ps 10-90 %, ASSUMED)
On L2 the P3V3 and VADJ planes part, and 5 nets cross from one to the other at 9 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 9 crossing(s) the track's other neighbour carries a plane, which the return can use there; 9 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.
- 'ADC_IN1' on TOP_LAYER at (105.81, 120.27), 1.3 mm; other side: none: the signal layer is outermost
- 'ADC_IN2' on TOP_LAYER at (109.22, 126.4), 0.21 mm; other side: none: the signal layer is outermost
- 'ADC_IN2' on TOP_LAYER at (111.68, 126.38), 0.23 mm; other side: none: the signal layer is outermost
- 'ADC_IN3' on TOP_LAYER at (108.81, 126.38), 0.16 mm; other side: none: the signal layer is outermost
- 'ADC_IN3' on TOP_LAYER at (119.38, 126.38), 0.17 mm; other side: none: the signal layer is outermost
- 'ADC_IN5' on TOP_LAYER at (107.57, 126.27), 0.17 mm; other side: none: the signal layer is outermost
- 'ADC_IN5' on TOP_LAYER at (108.06, 126.38), 0.23 mm; other side: none: the signal layer is outermost
- 'ADC_IN5' on TOP_LAYER at (120.89, 126.38), 0.16 mm; other side: none: the signal layer is outermost
- 'ADC_IN8' on TOP_LAYER at (124.57, 127.21), 0.23 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/12/reference-planes?group=split%40L2%3AP3V3%7CVADJ serves each with its own layer_image region; all of them lie in x 104.65..125.57, y 118.93..128.33 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@TOP_LAYER:GND|P1V812 nets cross the split between the GND and P1V8 planes on TOP_LAYER at 12 places, all with a plane on the track's other side (fastest: IO_VADJ_1 at 100 ps 10-90 %, ASSUMED)
On TOP_LAYER the GND and P1V8 planes part, and 12 nets cross from one to the other at 12 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 12 of the 12 crossing(s) the track's other neighbour carries a plane, which the return can use there. 0 of the 12 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.
- 'CLK0_M2C_N' on L2 at (104.13, 75.47), 1.3 mm; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'CLK0_M2C_P' on L2 at (104.13, 74.48), 1.3 mm; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'CLK1_M2C_N' on L2 at (104.9, 73.29), 0.31 mm; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'FMC_SCL' on L2 at (104.9, 76.79), 0.31 mm; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'FMC_SDA' on L2 at (104.9, 77.12), 0.31 mm; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'IO_1V8_1' on L2 at (104.13, 74.15), 1.3 mm; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'IO_VADJ_1' on L2 at (104.9, 73.62), 0.31 mm; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'IO_VADJ_24' on L2 at (104.13, 74.81), 1.3 mm; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'IO_VADJ_25' on L2 at (104.13, 75.8), 1.3 mm; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'IO_VADJ_4' on L2 at (104.6, 72.3), 0.63 mm; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'SCL_VADJ' on L2 at (104.13, 75.14), 1.3 mm; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'SDA_VADJ' on L2 at (104.13, 76.13), 1.3 mm; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/12/reference-planes?group=split%40TOP_LAYER%3AGND%7CP1V8 serves each with its own layer_image region; all of them lie in x 102.76..106.05, y 71.3..78.12 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@TOP_LAYER:hole 105.35,73.74|106.35,74.963 nets cross one void in the GND plane on TOP_LAYER at 3 places, the longest 0.25 mm (fastest: IO_VADJ_24 at 100 ps 10-90 %, ASSUMED)
Along 'IO_1V8_1' on L2, the GND plane on TOP_LAYER has 0.25 mm under the track with no copper, at (105.48, 74.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. 3 places on 3 net(s) cross it, listed below, the longest first. What cleared it: the hole at x 105.35..106.35, y 73.74..74.96. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 0 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.
- 'CLK0_M2C_P' on L2 at (105.48, 74.48), 0.25 mm over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'IO_1V8_1' on L2 at (105.48, 74.15), 0.25 mm over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'IO_VADJ_24' on L2 at (105.48, 74.81), 0.25 mm over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/12/reference-planes?group=void%3AGND%40TOP_LAYER%3Ahole%20105.35%2C73.74%7C106.35%2C74.96 serves each with its own layer_image region; all of them lie in x 104.35..106.6, y 73.15..75.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@TOP_LAYER:hole 105.35,75.27|106.35,76.494 nets cross one void in the GND plane on TOP_LAYER at 4 places, the longest 1 mm (fastest: IO_VADJ_25 at 100 ps 10-90 %, ASSUMED)
Along 'IO_VADJ_5' on L2, the GND plane on TOP_LAYER has 1 mm under the track with no copper, at (105.85, 76.46), 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 mm). 4 places on 4 net(s) cross it, listed below, the longest first. What cleared it: the hole at x 105.35..106.35, y 75.27..76.49. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 0 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.
- 'IO_VADJ_5' on L2 at (105.85, 76.46), 1 mm, running ALONG the bare copper for 1 mm, not across it over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'CLK0_M2C_N' on L2 at (105.48, 75.47), 0.25 mm over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'IO_VADJ_25' on L2 at (105.48, 75.8), 0.25 mm over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'SDA_VADJ' on L2 at (105.48, 76.13), 0.25 mm over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/12/reference-planes?group=void%3AGND%40TOP_LAYER%3Ahole%20105.35%2C75.27%7C106.35%2C76.49 serves each with its own layer_image region; all of them lie in x 104.35..107.35, y 74.47..77.46 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@TOP_LAYER:hole 106.66,73.74|107.66,74.963 nets cross one void in the GND plane on TOP_LAYER at 3 places, the longest 0.25 mm (fastest: IO_VADJ_24 at 100 ps 10-90 %, ASSUMED)
Along 'IO_1V8_1' on L2, the GND plane on TOP_LAYER has 0.25 mm under the track with no copper, at (107.53, 74.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. 3 places on 3 net(s) cross it, listed below, the longest first. What cleared it: the hole at x 106.66..107.66, y 73.74..74.96. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 0 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.
- 'CLK0_M2C_P' on L2 at (107.53, 74.48), 0.25 mm over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'IO_1V8_1' on L2 at (107.53, 74.15), 0.25 mm over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'IO_VADJ_24' on L2 at (107.53, 74.81), 0.25 mm over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/12/reference-planes?group=void%3AGND%40TOP_LAYER%3Ahole%20106.66%2C73.74%7C107.66%2C74.96 serves each with its own layer_image region; all of them lie in x 106.4..108.66, y 73.15..75.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@TOP_LAYER:hole 106.66,75.27|107.66,76.494 nets cross one void in the GND plane on TOP_LAYER at 4 places, the longest 1 mm (fastest: IO_VADJ_25 at 100 ps 10-90 %, ASSUMED)
Along 'IO_VADJ_5' on L2, the GND plane on TOP_LAYER has 1 mm under the track with no copper, at (107.16, 76.46), 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 mm). 4 places on 4 net(s) cross it, listed below, the longest first. What cleared it: the hole at x 106.66..107.66, y 75.27..76.49. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 0 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.
- 'IO_VADJ_5' on L2 at (107.16, 76.46), 1 mm, running ALONG the bare copper for 1 mm, not across it over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'CLK0_M2C_N' on L2 at (107.53, 75.47), 0.25 mm over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'IO_VADJ_25' on L2 at (107.53, 75.8), 0.25 mm over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'SDA_VADJ' on L2 at (107.53, 76.13), 0.25 mm over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/12/reference-planes?group=void%3AGND%40TOP_LAYER%3Ahole%20106.66%2C75.27%7C107.66%2C76.49 serves each with its own layer_image region; all of them lie in x 105.66..108.66, y 74.47..77.46 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:P1V8@TOP_LAYER:100.59,74.81'IO_VADJ_24' crosses where the outline of the P1V8 plane on TOP_LAYER is drawn back, at 1 place, the longest 1.25 mm (fastest: IO_VADJ_24 at 100 ps 10-90 %, ASSUMED)
Along 'IO_VADJ_24' on L2, the P1V8 plane on TOP_LAYER has 1.25 mm under the track with no copper, at (100.59, 74.81), 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.18 mm). No hole cleared it: the outline of the pour at x 93.11..104.75, y 71.84..82.1 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 0 of the 1 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.
- 'IO_VADJ_24' on L2 at (100.59, 74.81), 1.25 mm, running ALONG the bare copper for 1.18 mm, not across it over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/12/reference-planes?group=void%3AP1V8%40TOP_LAYER%3A100.59%2C74.81 serves each with its own layer_image region; all of them lie in x 98.95..102.18, y 73.81..75.86 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:P1V8@TOP_LAYER:93.54,77.96'CLK0_M2C_P' crosses where the outline of the P1V8 plane on TOP_LAYER is drawn back, at 1 place, the longest 1.9 mm (fastest: CLK0_M2C_P at 1 ns 10-90 %, suggested by its name)
Along 'CLK0_M2C_P' on L2, the P1V8 plane on TOP_LAYER has 1.9 mm under the track with copper of P1V8, not a plane, at (93.54, 77.96), 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 93.11..104.75, y 71.84..82.1 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 0 of the 1 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.
- 'CLK0_M2C_P' on L2 at (93.54, 77.96), 1.9 mm over copper of P1V8, not a plane, to the end of the track; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/12/reference-planes?group=void%3AP1V8%40TOP_LAYER%3A93.54%2C77.96 serves each with its own layer_image region; all of them lie in x 91.1..95, y 76.96..79.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.
void:P1V8@TOP_LAYER:copper of GND2 nets cross where the P1V8 plane on TOP_LAYER is drawn back round copper of GND, at 2 places, the longest 2.6 mm (fastest: CLK0_M2C_P at 1 ns 10-90 %, suggested by its name)
Along 'IO_1V8_1' on L2, the P1V8 plane on TOP_LAYER has 2.6 mm under the track with copper of GND, not a plane, at (100.38, 74.15), 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. 2 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 1.45 mm). 2 places on 2 net(s) cross it, listed below, the longest first. No hole cleared it: the outline of the pour at x 93.11..104.75, y 71.84..82.1 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 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.
- 'IO_1V8_1' on L2 at (100.38, 74.15), 2.6 mm, running ALONG the bare copper for 1.45 mm, not across it over copper of GND, not a plane, to the end of the track; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'CLK0_M2C_P' on L2 at (100.44, 74.48), 1.85 mm, running ALONG the bare copper for 1.32 mm, not across it over copper of GND, not a plane; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/12/reference-planes?group=void%3AP1V8%40TOP_LAYER%3Acopper%20of%20GND serves each with its own layer_image region; all of them lie in x 98.02..102.18, y 73.15..75.86 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:P1V8@TOP_LAYER:copper of P3V34 nets cross where the P1V8 plane on TOP_LAYER is drawn back round copper of P3V3, at 4 places, the longest 1.77 mm (fastest: IO_VADJ_25 at 100 ps 10-90 %, ASSUMED)
Along 'IO_VADJ_5' on L2, the P1V8 plane on TOP_LAYER has 1.77 mm under the track with copper of P3V3, not a plane, at (99.79, 78.76), 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 places on 4 net(s) cross it, listed below, the longest first. No hole cleared it: the outline of the pour at x 93.11..104.75, y 71.84..82.1 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 0 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.
- 'IO_VADJ_5' on L2 at (99.79, 78.76), 1.77 mm over copper of P3V3, not a plane; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'SDA_VADJ' on L2 at (99.39, 78.69), 1.66 mm over copper of P3V3, not a plane; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'FMC_SCL' on L2 at (100.2, 78.81), 1.61 mm over copper of P3V3, not a plane, to the end of the track; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'IO_VADJ_25' on L2 at (99.08, 78.54), 1 mm over copper of P3V3, not a plane; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/12/reference-planes?group=void%3AP1V8%40TOP_LAYER%3Acopper%20of%20P3V3 serves each with its own layer_image region; all of them lie in x 97.72..101.83, y 77.19..80.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:P1V8@TOP_LAYER:hole 100.1,75.78|101.28,76.36'CLK0_M2C_N' crosses one void in the P1V8 plane on TOP_LAYER at 1 place, the longest 0.36 mm (fastest: CLK0_M2C_N at 1 ns 10-90 %, suggested by its name)
Along 'CLK0_M2C_N' on L2, the P1V8 plane on TOP_LAYER has 0.36 mm under the track with no copper, at (100.88, 75.91), 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. What cleared it: the hole at x 100.1..101.28, y 75.78..76.36. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 0 of the 1 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.
- 'CLK0_M2C_N' on L2 at (100.88, 75.91), 0.36 mm over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/12/reference-planes?group=void%3AP1V8%40TOP_LAYER%3Ahole%20100.1%2C75.78%7C101.28%2C76.36 serves each with its own layer_image region; all of them lie in x 99.75..102.01, y 74.78..77.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:P1V8@TOP_LAYER:hole 100.1,76.66|101.28,77.242 nets cross one void in the P1V8 plane on TOP_LAYER at 2 places, the longest 0.49 mm (fastest: IO_VADJ_25 at 100 ps 10-90 %, ASSUMED)
Along 'SDA_VADJ' on L2, the P1V8 plane on TOP_LAYER has 0.49 mm under the track with no copper, at (101.01, 77.07), 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. 2 places on 2 net(s) cross it, listed below, the longest first. What cleared it: the hole at x 100.1..101.28, y 76.66..77.24. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 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.
- 'SDA_VADJ' on L2 at (101.01, 77.07), 0.49 mm over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'IO_VADJ_25' on L2 at (100.5, 77.11), 0.36 mm over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/12/reference-planes?group=void%3AP1V8%40TOP_LAYER%3Ahole%20100.1%2C76.66%7C101.28%2C77.24 serves each with its own layer_image region; all of them lie in x 99.37..102.19, y 75.89..78.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:P1V8@TOP_LAYER:hole 102.45,73.74|103.45,74.963 nets cross one void in the P1V8 plane on TOP_LAYER at 3 places, the longest 0.25 mm (fastest: IO_VADJ_24 at 100 ps 10-90 %, ASSUMED)
Along 'IO_VADJ_24' on L2, the P1V8 plane on TOP_LAYER has 0.25 mm under the track with no copper, at (102.58, 74.81), 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 places on 3 net(s) cross it, listed below, the longest first. What cleared it: the hole at x 102.45..103.45, y 73.74..74.96. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 0 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.
- 'CLK0_M2C_P' on L2 at (102.58, 74.48), 0.25 mm over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'IO_1V8_1' on L2 at (102.58, 74.15), 0.25 mm over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'IO_VADJ_24' on L2 at (102.58, 74.81), 0.25 mm over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/12/reference-planes?group=void%3AP1V8%40TOP_LAYER%3Ahole%20102.45%2C73.74%7C103.45%2C74.96 serves each with its own layer_image region; all of them lie in x 101.45..103.7, y 73.15..75.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:P1V8@TOP_LAYER:hole 102.45,75.27|103.45,76.494 nets cross one void in the P1V8 plane on TOP_LAYER at 4 places, the longest 0.87 mm (fastest: IO_VADJ_25 at 100 ps 10-90 %, ASSUMED)
Along 'IO_VADJ_5' on L2, the P1V8 plane on TOP_LAYER has 0.87 mm under the track with no copper, at (103.02, 76.46), 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.87 mm). 4 places on 4 net(s) cross it, listed below, the longest first. What cleared it: the hole at x 102.45..103.45, y 75.27..76.49. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 0 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.
- 'IO_VADJ_5' on L2 at (103.02, 76.46), 0.87 mm, running ALONG the bare copper for 0.87 mm, not across it over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'CLK0_M2C_N' on L2 at (102.58, 75.47), 0.25 mm over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'IO_VADJ_25' on L2 at (102.58, 75.8), 0.25 mm over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'SDA_VADJ' on L2 at (102.58, 76.13), 0.25 mm over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/12/reference-planes?group=void%3AP1V8%40TOP_LAYER%3Ahole%20102.45%2C75.27%7C103.45%2C76.49 serves each with its own layer_image region; all of them lie in x 101.45..104.45, y 74.47..77.46 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:P1V8@TOP_LAYER:hole 102.51,72.47|103.08,73.082 nets cross one void in the P1V8 plane on TOP_LAYER at 2 places, the longest 0.58 mm (fastest: IO_VADJ_26 at 100 ps 10-90 %, ASSUMED)
Along 'CLK1_M2C_P' on L2, the P1V8 plane on TOP_LAYER has 0.58 mm under the track with no copper, at (102.8, 72.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. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 0.58 mm). 2 places on 2 net(s) cross it, listed below, the longest first. What cleared it: the hole at x 102.51..103.08, y 72.47..73.08. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 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.
- 'CLK1_M2C_P' on L2 at (102.8, 72.96), 0.58 mm, running ALONG the bare copper for 0.58 mm, not across it over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'IO_VADJ_26' on L2 at (102.63, 72.63), 0.25 mm over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/12/reference-planes?group=void%3AP1V8%40TOP_LAYER%3Ahole%20102.51%2C72.47%7C103.08%2C73.08 serves each with its own layer_image region; all of them lie in x 101.51..104.08, y 71.63..73.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:P1V8@TOP_LAYER:hole 103.39,72.47|103.97,73.082 nets cross one void in the P1V8 plane on TOP_LAYER at 2 places, the longest 0.58 mm (fastest: IO_VADJ_26 at 100 ps 10-90 %, ASSUMED)
Along 'CLK1_M2C_P' on L2, the P1V8 plane on TOP_LAYER has 0.58 mm under the track with no copper, at (103.68, 72.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. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 0.58 mm). 2 places on 2 net(s) cross it, listed below, the longest first. What cleared it: the hole at x 103.39..103.97, y 72.47..73.08. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 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.
- 'CLK1_M2C_P' on L2 at (103.68, 72.96), 0.58 mm, running ALONG the bare copper for 0.58 mm, not across it over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'IO_VADJ_26' on L2 at (103.84, 72.63), 0.25 mm over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/12/reference-planes?group=void%3AP1V8%40TOP_LAYER%3Ahole%20103.39%2C72.47%7C103.97%2C73.08 serves each with its own layer_image region; all of them lie in x 102.39..104.97, y 71.63..73.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:P1V8@TOP_LAYER:hole 94.3,76.66|95.48,78.394 nets cross one void in the P1V8 plane on TOP_LAYER at 4 places, the longest 0.25 mm (fastest: IO_VADJ_1 at 100 ps 10-90 %, ASSUMED)
Along 'CLK1_M2C_N' on L2, the P1V8 plane on TOP_LAYER has 0.25 mm under the track with no copper, at (95.35, 76.97), 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 places on 4 net(s) cross it, listed below, the longest first. What cleared it: the hole at x 94.3..95.48, y 76.66..78.39. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 0 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.
- 'CLK0_M2C_P' on L2 at (95.35, 77.96), 0.25 mm over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'CLK1_M2C_N' on L2 at (95.35, 76.97), 0.25 mm over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'IO_1V8_1' on L2 at (95.35, 77.63), 0.25 mm over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'IO_VADJ_1' on L2 at (95.35, 77.3), 0.25 mm over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/12/reference-planes?group=void%3AP1V8%40TOP_LAYER%3Ahole%2094.3%2C76.66%7C95.48%2C78.39 serves each with its own layer_image region; all of them lie in x 94.23..96.48, y 75.97..78.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:P1V8@TOP_LAYER:hole 98.62,75.78|99.8,76.362 nets cross one void in the P1V8 plane on TOP_LAYER at 2 places, the longest 0.49 mm (fastest: IO_VADJ_24 at 100 ps 10-90 %, ASSUMED)
Along 'IO_VADJ_24' on L2, the P1V8 plane on TOP_LAYER has 0.49 mm under the track with no copper, at (98.85, 75.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. 2 places on 2 net(s) cross it, listed below, the longest first. What cleared it: the hole at x 98.62..99.8, y 75.78..76.36. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 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.
- 'IO_VADJ_24' on L2 at (98.85, 75.96), 0.49 mm over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'SCL_VADJ' on L2 at (99.37, 75.91), 0.36 mm over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/12/reference-planes?group=void%3AP1V8%40TOP_LAYER%3Ahole%2098.62%2C75.78%7C99.8%2C76.36 serves each with its own layer_image region; all of them lie in x 97.68..100.49, y 74.78..77.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.
void:P1V8@TOP_LAYER:hole 98.62,76.66|99.8,77.24'CLK0_M2C_N' crosses one void in the P1V8 plane on TOP_LAYER at 1 place, the longest 0.35 mm (fastest: CLK0_M2C_N at 1 ns 10-90 %, suggested by its name)
Along 'CLK0_M2C_N' on L2, the P1V8 plane on TOP_LAYER has 0.35 mm under the track with no copper, at (99.67, 77.12), 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. What cleared it: the hole at x 98.62..99.8, y 76.66..77.24. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 0 of the 1 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.
- 'CLK0_M2C_N' on L2 at (99.67, 77.12), 0.35 mm over no copper; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/12/reference-planes?group=void%3AP1V8%40TOP_LAYER%3Ahole%2098.62%2C76.66%7C99.8%2C77.24 serves each with its own layer_image region; all of them lie in x 98.55..100.8, y 75.99..78.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:P3V3@L2:131.71,85.44'IO_VADJ_25' crosses where the outline of the P3V3 plane on L2 is drawn back, at 1 place, the longest 0.49 mm (fastest: IO_VADJ_25 at 100 ps 10-90 %, ASSUMED)
Along 'IO_VADJ_25' on TOP_LAYER, the P3V3 plane on L2 has 0.49 mm under the track with no copper, at (131.71, 85.44), 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.25 mm). No hole cleared it: the outline of the pour at x 100.82..144.02, y 69.78..136.52 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.
- 'IO_VADJ_25' on TOP_LAYER at (131.71, 85.44), 0.49 mm, running ALONG the bare copper for 0.25 mm, not across it over no copper; 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/12/reference-planes?group=void%3AP3V3%40L2%3A131.71%2C85.44 serves each with its own layer_image region; all of them lie in x 130.57..132.85, y 84.22..86.58 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:P3V3@L2:134.41,76.26'IO_VADJ_62' crosses where the outline of the P3V3 plane on L2 is drawn back, at 1 place, the longest 1.66 mm (fastest: IO_VADJ_62 at 100 ps 10-90 %, ASSUMED)
Along 'IO_VADJ_62' on TOP_LAYER, the P3V3 plane on L2 has 1.66 mm under the track with no copper, at (134.41, 76.26), 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.29 mm). No hole cleared it: the outline of the pour at x 100.82..144.02, y 69.78..136.52 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.
- 'IO_VADJ_62' on TOP_LAYER at (134.41, 76.26), 1.66 mm, running ALONG the bare copper for 1.29 mm, not across it over no copper; 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/12/reference-planes?group=void%3AP3V3%40L2%3A134.41%2C76.26 serves each with its own layer_image region; all of them lie in x 132.96..136.05, y 74.62..77.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:P3V3@L2:hole 129.53,127.23|135.87,129.37'NetJ1_h40' crosses one void in the P3V3 plane on L2 at 1 place, the longest 1.18 mm; 1 over tracks of other nets routed inside it (fastest: NetJ1_h40 at 100 ps 10-90 %, ASSUMED)
Along 'NetJ1_h40' on TOP_LAYER, the P3V3 plane on L2 has 1.18 mm under the track with copper of NetJ1_f40, not a plane, at (131.33, 127.82), 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 129.53..135.87, y 127.23..129.37. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.
- 'NetJ1_h40' on TOP_LAYER at (131.33, 127.82), 1.18 mm over copper of NetJ1_f40, not a plane; 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/12/reference-planes?group=void%3AP3V3%40L2%3Ahole%20129.53%2C127.23%7C135.87%2C129.37 serves each with its own layer_image region; all of them lie in x 129.76..132.8, y 126.49..128.82 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@L2|TOP_LAYERTracks on L2 and TOP_LAYER cross each other at 42 places, each layer the other's reference with its pour cleared round its own tracks, the longest 56.06 mm; 45 run ALONG the cut round another net's track (fastest: ADC_IN1 at 100 ps 10-90 %, ASSUMED)
L2 and TOP_LAYER 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. 42 place(s) on 40 net(s), 3 of them seen from both tracks (each counted once). 45 of the crossings run ALONG the cut round another net's track rather than across it, parallel to its edges (the longest 27.57 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. 0 of the 75 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.
- 'IO_VADJ_27' on L2 at (105.4, 70.42), 56.06 mm, running ALONG the bare copper for 27.57 mm, not across it over copper of FMC_SCL, GND, PROG_CLK_N, CLK1_M2C_P, IO_VADJ_1, IO_1V8_1, not a plane, to the end of the track; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'IO_VADJ_49' on L2 at (105.53, 70.06), 54.16 mm, running ALONG the bare copper for 26.14 mm, not across it over copper of FMC_SCL, CLK1_M2C_P, IO_VADJ_1, GND, not a plane, to the end of the track; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'IO_VADJ_4' on L2 at (123.11, 71.64), 41.62 mm, running ALONG the bare copper for 18.16 mm, not across it over copper of FMC_SCL, GND, PROG_CLK_N, CLK1_M2C_P, IO_VADJ_1, IO_1V8_1, IO_VADJ_27, not a plane, to the end of the track; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'IO_VADJ_26' on L2 at (118.29, 71.97), 37.65 mm, running ALONG the bare copper for 17.56 mm, not across it over copper of FMC_SCL, CLK1_M2C_P, IO_VADJ_1, IO_1V8_1, GND, not a plane, to the end of the track; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'ADC_IN1' on TOP_LAYER at (107.14, 114.91), 33.36 mm, running ALONG the bare copper for 0.24 mm, not across it over copper of IO_VADJ_22, IO_VADJ_21, FMC_SCL, IO_VADJ_18, IO_VADJ_41, IO_VADJ_65, IO_VADJ_42, IO_VADJ_19, IO_VADJ_66, IO_VADJ_67, IO_VADJ_80, IO_VADJ_40, IO_VADJ_64, IO_VADJ_17, IO_VADJ_16, IO_VADJ_39, IO_VADJ_63, IO_VADJ_38, IO_VADJ_70, IO_VADJ_60, IO_VADJ_15, IO_VADJ_61, IO_VADJ_14, IO_VADJ_37, IO_VADJ_69, IO_VADJ_36, IO_VADJ_59, IO_VADJ_78, IO_VADJ_77, IO_VADJ_58, IO_VADJ_57, IO_VADJ_13, IO_VADJ_12, IO_VADJ_34, IO_VADJ_35, IO_VADJ_76, IO_VADJ_75, IO_VADJ_56, IO_VADJ_55, IO_VADJ_54, IO_VADJ_10, IO_VADJ_11, IO_VADJ_32, IO_VADJ_33, IO_VADJ_31, IO_VADJ_8, IO_VADJ_74, IO_VADJ_9, IO_VADJ_73, IO_VADJ_52, IO_VADJ_51, IO_VADJ_53, IO_VADJ_30, IO_VADJ_72, IO_VADJ_28, IO_VADJ_29, IO_VADJ_20, IO_VADJ_43, IO_VADJ_68, not a plane, to the end of the track; other side: none: the signal layer is outermost
- one crossing of two tracks, seen from each: 'CLK0_C2M_N' on TOP_LAYER at (129.07, 80.7), 3.07 mm over copper of IO_VADJ_5, SDA_VADJ, IO_VADJ_25, CLK0_M2C_N, SCL_VADJ, IO_VADJ_24, not a plane, to the end of the track; other side: none: the signal layer is outermost / 'CLK0_C2M_P' on TOP_LAYER at (128.46, 79.4), 4.09 mm over copper of IO_VADJ_5, SDA_VADJ, IO_VADJ_25, CLK0_M2C_N, SCL_VADJ, IO_VADJ_24, CLK0_M2C_P, not a plane, to the end of the track; other side: none: the signal layer is outermost / 'CLK0_M2C_N' on L2 at (122.17, 75.47), 27.83 mm, running ALONG the bare copper for 14.18 mm, not across it over copper of FMC_SCL, P3V3, GND, CLK0_C2M_P, CLK0_C2M_N, not a plane, to the end of the track; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER / 'CLK0_M2C_P' on L2 at (120.86, 74.48), 26.52 mm, running ALONG the bare copper for 13.81 mm, not across it over copper of FMC_SCL, P3V3, GND, CLK0_C2M_P, not a plane, to the end of the track; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER / 'CLK1_C2M_N' on TOP_LAYER at (129.44, 82.37), 0.83 mm over copper of IO_VADJ_5, SDA_VADJ, not a plane, to the end of the track; other side: none: the signal layer is outermost / 'CLK1_C2M_P' on TOP_LAYER at (129.44, 81.58), 0.87 mm over copper of IO_VADJ_5, SDA_VADJ, not a plane, to the end of the track; other side: none: the signal layer is outermost / 'FMC_SDA' on TOP_LAYER at (116.23, 76.62), 0.25 mm over copper of IO_VADJ_5, not a plane, to the end of the track; other side: none: the signal layer is outermost / 'IO_VADJ_24' on L2 at (120.79, 74.81), 30.68 mm, running ALONG the bare copper for 14.34 mm, not across it over copper of FMC_SCL, P3V3, GND, CLK0_C2M_P, CLK0_C2M_N, CLK0_M2C_P, not a plane, to the end of the track; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER / 'IO_VADJ_25' on L2 at (122.11, 75.8), 28.66 mm, running ALONG the bare copper for 14.11 mm, not across it over copper of FMC_SCL, FMC_SDA, P3V3, CLK0_C2M_P, CLK0_C2M_N, GND, not a plane, to the end of the track; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER / 'IO_VADJ_5' on L2 at (129.26, 84.79), 32.2 mm, running ALONG the bare copper for 16.42 mm, not across it over copper of FMC_SCL, FMC_SDA, P3V3, CLK0_C2M_P, CLK0_C2M_N, CLK1_C2M_P, CLK1_C2M_N, GND, not a plane, to the end of the track; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER / 'SCL_VADJ' on L2 at (121.1, 75.14), 30.01 mm, running ALONG the bare copper for 14.28 mm, not across it over copper of FMC_SCL, P3V3, GND, CLK0_C2M_P, CLK0_C2M_N, CLK0_M2C_N, not a plane, to the end of the track; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER / 'SDA_VADJ' on L2 at (111.35, 76.13), 30.81 mm, running ALONG the bare copper for 15.09 mm, not across it over copper of FMC_SCL, FMC_SDA, P3V3, CLK0_C2M_P, GND, CLK0_C2M_N, CLK1_C2M_P, CLK1_C2M_N, not a plane, to the end of the track; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'CLK1_M2C_N' on L2 at (117.69, 72.63), 28.12 mm, running ALONG the bare copper for 14.42 mm, not across it over copper of FMC_SCL, IO_VADJ_1, IO_1V8_1, GND, not a plane, to the end of the track; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- 'FMC_SDA' on TOP_LAYER at (129.95, 116.24), 27.46 mm, running ALONG the bare copper for 22.25 mm, not across it over copper of IO_VADJ_21, IO_VADJ_22, IO_VADJ_68, IO_VADJ_43, IO_VADJ_20, IO_VADJ_80, IO_VADJ_67, IO_VADJ_66, IO_VADJ_19, IO_VADJ_42, not a plane; other side: none: the signal layer is outermost
- 'FMC_SDA' on TOP_LAYER at (100.87, 119.17), 26.04 mm, running ALONG the bare copper for 2.48 mm, not across it over copper of IO_VADJ_43, IO_VADJ_68, IO_VADJ_21, IO_VADJ_22, IO_VADJ_20, IO_VADJ_80, IO_VADJ_67, IO_VADJ_66, IO_VADJ_19, IO_VADJ_42, IO_VADJ_6, IO_VADJ_50, IO_VADJ_7, IO_VADJ_29, IO_VADJ_28, IO_VADJ_72, IO_VADJ_30, IO_VADJ_53, IO_VADJ_51, IO_VADJ_52, IO_VADJ_73, IO_VADJ_9, IO_VADJ_74, IO_VADJ_8, IO_VADJ_31, IO_VADJ_33, IO_VADJ_32, IO_VADJ_11, IO_VADJ_10, IO_VADJ_54, IO_VADJ_55, IO_VADJ_56, IO_VADJ_75, IO_VADJ_76, IO_VADJ_35, IO_VADJ_34, IO_VADJ_12, IO_VADJ_13, IO_VADJ_57, IO_VADJ_58, IO_VADJ_77, IO_VADJ_78, IO_VADJ_59, IO_VADJ_36, IO_VADJ_69, IO_VADJ_37, IO_VADJ_14, IO_VADJ_61, IO_VADJ_15, IO_VADJ_60, IO_VADJ_70, IO_VADJ_38, IO_VADJ_63, IO_VADJ_39, IO_VADJ_16, IO_VADJ_17, IO_VADJ_64, IO_VADJ_40, IO_VADJ_18, IO_VADJ_41, IO_VADJ_65, not a plane; other side: none: the signal layer is outermost
- one crossing of two tracks, seen from each: 'CLK1_M2C_N' on L2 at (87.12, 80.56), 18.14 mm, running ALONG the bare copper for 8.37 mm, not across it over copper of SDA_VADJ, SCL_VADJ, P1V8, not a plane, to the end of the track; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER / 'CLK1_M2C_P' on L2 at (86.79, 80.49), 19.61 mm, running ALONG the bare copper for 8.95 mm, not across it over copper of SDA_VADJ, SCL_VADJ, P1V8, not a plane, to the end of the track; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER / 'IO_VADJ_1' on L2 at (87.45, 80.63), 16.3 mm, running ALONG the bare copper for 8.11 mm, not across it over copper of SDA_VADJ, SCL_VADJ, P1V8, not a plane, to the end of the track; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER / 'IO_VADJ_26' on L2 at (86.46, 80.52), 19.43 mm, running ALONG the bare copper for 10.05 mm, not across it over copper of SDA_VADJ, SCL_VADJ, P1V8, not a plane, to the end of the track; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER / 'IO_VADJ_26' on TOP_LAYER at (86.11, 88.26), 2.77 mm over copper of IO_VADJ_79, IO_VADJ_62, IO_VADJ_48, IO_VADJ_71, IO_VADJ_49, IO_VADJ_27, IO_VADJ_4, not a plane, to the end of the track; other side: none: the signal layer is outermost / 'IO_VADJ_27' on L2 at (85.44, 80.61), 23.4 mm, running ALONG the bare copper for 13.38 mm, not across it over copper of SDA_VADJ, SCL_VADJ, IO_VADJ_26, IO_VADJ_4, P1V8, not a plane, to the end of the track; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER / 'IO_VADJ_27' on TOP_LAYER at (85.45, 89.54), 2.21 mm over copper of IO_VADJ_79, IO_VADJ_62, IO_VADJ_48, IO_VADJ_71, IO_VADJ_49, not a plane, to the end of the track; other side: none: the signal layer is outermost / 'IO_VADJ_49' on L2 at (85.11, 80.71), 24.25 mm, running ALONG the bare copper for 14.05 mm, not across it over copper of SDA_VADJ, SCL_VADJ, IO_VADJ_26, IO_VADJ_4, IO_VADJ_27, P1V8, not a plane, to the end of the track; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER / 'IO_VADJ_4' on L2 at (85.77, 80.53), 22.05 mm, running ALONG the bare copper for 12.24 mm, not across it over copper of SDA_VADJ, SCL_VADJ, IO_VADJ_26, P1V8, not a plane, to the end of the track; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER / 'IO_VADJ_4' on TOP_LAYER at (85.8, 89.03), 2.53 mm over copper of IO_VADJ_79, IO_VADJ_62, IO_VADJ_48, IO_VADJ_71, IO_VADJ_49, IO_VADJ_27, not a plane, to the end of the track; other side: none: the signal layer is outermost / 'SCL_VADJ' on TOP_LAYER at (86.12, 84.25), 5.08 mm over copper of IO_VADJ_79, IO_VADJ_62, IO_VADJ_48, IO_VADJ_71, IO_VADJ_49, IO_VADJ_27, IO_VADJ_4, IO_VADJ_26, CLK1_M2C_P, CLK1_M2C_N, IO_VADJ_1, not a plane; other side: none: the signal layer is outermost / 'SDA_VADJ' on TOP_LAYER at (86.12, 83.69), 4.96 mm over copper of IO_VADJ_79, IO_VADJ_62, IO_VADJ_48, IO_VADJ_71, IO_VADJ_49, IO_VADJ_27, IO_VADJ_4, IO_VADJ_26, CLK1_M2C_P, CLK1_M2C_N, IO_VADJ_1, not a plane; other side: none: the signal layer is outermost
- 'NetIC9_9' on TOP_LAYER at (105.23, 114.31), 23.22 mm over copper of IO_VADJ_40, IO_VADJ_64, IO_VADJ_17, IO_VADJ_16, IO_VADJ_39, IO_VADJ_63, IO_VADJ_38, IO_VADJ_70, IO_VADJ_60, IO_VADJ_15, IO_VADJ_61, IO_VADJ_14, IO_VADJ_37, IO_VADJ_69, IO_VADJ_36, IO_VADJ_59, IO_VADJ_78, IO_VADJ_77, IO_VADJ_58, IO_VADJ_57, IO_VADJ_13, IO_VADJ_12, IO_VADJ_34, IO_VADJ_35, IO_VADJ_76, IO_VADJ_75, IO_VADJ_56, IO_VADJ_55, IO_VADJ_54, IO_VADJ_10, IO_VADJ_11, IO_VADJ_32, IO_VADJ_33, IO_VADJ_31, IO_VADJ_8, IO_VADJ_74, IO_VADJ_9, IO_VADJ_73, IO_VADJ_52, IO_VADJ_51, IO_VADJ_53, IO_VADJ_30, IO_VADJ_72, IO_VADJ_28, IO_VADJ_29, IO_VADJ_7, IO_VADJ_50, IO_VADJ_6, not a plane, to the end of the track; other side: none: the signal layer is outermost
- 'IO_VADJ_1' on L2 at (122.15, 72.96), 20.21 mm, running ALONG the bare copper for 12.29 mm, not across it over copper of FMC_SCL, P3V3, PROG_CLK_P, not a plane, to the end of the track; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
- and 30 more
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/12/reference-planes?group=void%3Arouted%40L2%7CTOP_LAYER serves each with its own layer_image region; all of them lie in x 73.85..138.95, y 69.06..125.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.
- SinglePointNetmajorOpen
SinglePointNet: 3 pins×3
3 checked by the review by Claude walker (cern session) — 2 different reasons
At IC12.16, IC9.12, IC9.13
Each finding, with its own headline
IC12.16IC12.16 (CONVST) is an IC input left unconnected
Pin IC12.16 (CONVST) 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.
IC9.12IC9.12 (4IN+) is an IC input left unconnected
Pin IC9.12 (4IN+) 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.
IC9.13IC9.13 (4IN-) is an IC input left unconnected
Pin IC9.13 (4IN-) 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.
ADC IC12 (AD7997) reference input REFIN has none of the decoupling the datasheet asks for
The AD7997 reference input REFIN (IC12 pin 6, net NetIC8_1) has none of the 0.1 uF and 1 uF decoupling the datasheet asks for, so conversion kicks and P12V noise land directly on the full scale of every ADC channel.
Where it is
``
mermaid flowchart LR P12["P12V"] -- "R14 1k" --> REF["NetIC8_1<br/>no capacitor"] REF --- TL["IC8 TL431<br/>cathode and ref tied"] REF --> ADC["IC12 AD7997<br/>pin 6 REFIN"]``What the datasheet asks
Quantity Value Source REFIN decoupling 0.1 uF and 1 uF to AGND AD7997 datasheet, p.10 REFIN load during a conversion switched, 69 kOhm typ AD7997 datasheet, p.3 Capacitors on NetIC8_1 none netlist; schematic Why it matters
Conversion kicks and noise coupled from P12V through the TL431 dynamic impedance land directly on the ADC full scale of every channel. Any capacitor added must also be checked against the TL431 stability-boundary chart.
ADC IC12 (AD7997) CONVST input is left floating; the datasheet says to tie it low when conversions are started over I2C
The AD7997 CONVST input (IC12 pin 16) is left floating, although the datasheet says to tie it low when conversions are started over I2C.
What the datasheet says
- CONVST is an edge-triggered CMOS input: a rising edge powers the ADC up and a falling edge starts a conversion (AD7997 datasheet, p.10).
- CONVST should be tied low in every mode other than Mode 1 (p.28).
Where it is
IC12 pin 16 is marked no-connect. The board controls the ADC only over I2C (command mode), not Mode 1.
Why it matters
Left floating, the pin can pick up edges from nearby signals and trigger spurious power-ups or conversions, and a floating CMOS input can draw extra supply current.
ADC IC12: nets ADC_IN2 and ADC_IN5 are on channels VIN5 and VIN2, so their names do not match the channel they are read from
On ADC IC12, net ADC_IN2 lands on channel VIN5 and net ADC_IN5 on VIN2, so test software that reads channel n as ADC_INn reports M12V_BI as P5V_BI and the reverse.
Where it is
Net Signal IC12 pin AD7997 channel ADC_IN2 M12V_BI inverting-amplifier output (IC9A), gain -0.2 9 VIN5 ADC_IN5 P5V_BI divider (R22/R23 + R26), ratio 0.505 14 VIN2 Source: netlist IC12; AD7997 pin table, p.10. The other six nets land on the channel of the same number.
Why it matters
The schematic draws this explicitly, so it may be deliberate (for layout). Nothing states it, though. The two channels also have different scaling (inverting gain -0.2 against a 0.505 divider).
VADJ monitor: the fitted divider (R45 = 10k) gives 2.0 V at VADJ = 2.5 V, outside the schematic's own pass window of 1.53-1.81 V, and clips above about 3.1 V
The VADJ monitor divider on ADC_IN8 (R45 = 10k) reads 2.0 V at VADJ = 2.5 V, outside the schematic's own 1.53-1.81 V pass window, and clips above about 3.1 V; either R45 or the table row is wrong.
The numbers
Quantity Value Source Divider four 10k resistors R35-R38 against R45 to GND netlist: ADC_IN8, IC12 pin 11 R45 10k, fitted BOM Ratio 10k / (10k + 2.5k) = 0.80 derived Reading at VADJ = 2.5 V 2.00 V derived Schematic pass window for Vadj (2.5V) 1.53-1.81 V schematic valid-voltage table, sheet 1 Ratio the table matches about 0.667 (R45 about 5k1) derived ADC full scale REFIN, the TL431: 2.44-2.55 V AD7997 datasheet, p.10; TL431C datasheet, p.6 VADJ at which the channel clips about 3.05-3.19 V derived Why it matters
- A tester that applies the table fails a good VADJ.
- The P3V3 and P12V rows do match their dividers, so either R45 or the VADJ table row is wrong.
- With R45 = 10k, a carrier running VADJ at 3.3 V (allowed by VITA 57.1) reads as clipped.
R14 and R43 (1k, 0.1 W 0603) from P12V dissipate about 90 mW and 104 mW, at or above their rating at nominal 12 V
R14 and R43 (1k, 0.1 W, 0603) drop most of P12V and dissipate about 90 mW and 104 mW at nominal 12 V, at or above their rating.
The numbers
Quantity Value Source R14, R43 1k, 0.1 W 0603 (R0603_1K_1%_0.1W_100PPM) BOM P12V 12 V nominal, 13.3 V at the top of the schematic P12V window schematic valid-voltage table TL431 IC8 Vref (R14 load) 2.495 V typ TL431C datasheet, p.6 LD3 SML-311UT forward voltage (R43 load) 1.8 V typ at 2 mA SML-311UT datasheet, p.1 R14 at 12 V (12 - 2.495) V / 1k = 9.5 mA, 90 mW (90% of rating) derived R14 at 13.3 V 117 mW derived R43 at 12 V (12 - 1.8) V / 1k = 10.2 mA, 104 mW, over the 0.1 W rating derived R43 at 13.3 V 132 mW derived Why it matters
Both run hot continuously while P12V is present, and resistor power ratings are normally also derated with temperature.
Fix
A 0.25 W part (1206) or a larger value would fix both. For LD3, the SML-311UT is characterised at 2 mA, so around 4k7 still lights it clearly.
Crosspoint IC7 (ADN4600): most gigabit pairs are wired P/N reversed (6 of 8 inputs, all 7 used outputs, and SATA J2 B pair), so polarity depends on firmware RX PNSWAP settings
Most gigabit pairs through the crosspoint IC7 (ADN4600) are wired P/N reversed (6 of 8 inputs, all 7 used outputs, and the SATA J2 B pair), so each route's polarity depends on firmware RX PNSWAP settings.
Where it is
On IC7 the net named _P goes to the complement pin (ADN4600 pin table, p.7) as follows.
Group Reversed Straight Inputs XPT_I1 (from CLK1_C2M), I2 (CLK0_C2M), I3 (DP1_C2M), I4 (DP2_C2M), I5 (DP3_C2M), I6 (DP4_C2M) XPT_I7 (DP0_C2M), XPT_I8 Outputs all used: XPT_O1 (GBTCLK1_M2C), O2 (DP1_M2C), O3 (DP2_M2C), O4 (DP3_M2C), O5 (DP4_M2C), O7 (DP0_M2C), O8 (J2 A pair) none; XPT_O6 goes nowhere J2 XPT_I8 pair lands on SATA B-/B+ reversed (XPT_I8_P on pin 5 B-) - So whether a path is inverted depends on which input feeds which output:
- DP1_C2M to DP1_M2C has two reversals and is true.
- DP0_C2M (straight) to DP0_M2C (reversed) is inverted.
Why it matters
- The ADN4600 can correct only on the receive side: RX PNSWAP per lane (p.14). Its own datasheet warns that using lane inversion to account for inversions needs extra care.
- For a connector tester that checks DP lanes with PRBS or 8b10b patterns, a wrong polarity reads as a failed lane, so the test software must set RX PNSWAP per route.
- Nothing on the schematic states the intended polarities. It may be deliberate (for routing), but it should be documented.
Top silkscreen: 17 designators near IC9 and J1 are printed in stacked lists (R45/R26/R22/R23, R36/R37/R35/R38, R34/R16/R32, C29/C27, C14/C16, C18/C20), so they cannot be matched to their footprints
Seventeen designators on the top silkscreen near IC9 and J1 are printed as stacked lists (R45/R26/R22/R23, R36/R37/R35/R38, R34/R16/R32, C29/C27, C14/C16, C18/C20), so they cannot be matched to their footprints.
Where it is
In the analog block around IC9/IC12 and along the J1 edge, the top silk prints these designators as stacked lists beside columns of identical 0603/0402 footprints instead of one label per part:
- R45, R26, R22, R23;
- R36, R37, R35, R38;
- R34, R16, R32;
- the pairs C29/C27, C14/C16, C18/C20.
The other designators sit next to their own parts and read at about 1 mm cap height.
Why it matters
On the board you cannot tell which footprint is R45 (the VADJ divider leg, see OBS-332) and which is R26, or which cap is on which gigabit pair. That slows rework, probing and the value change the VADJ divider may need.
- DecapViaFanoutminorOpen
DecapViaFanout: 3 components×3
Checked by the review, stands · Claude walker W3 (Cern session) — Checked: the fan-out length is read from the copper as stated. The 0.5 nH limit is Probe's starting value, not a datasheet or vendor requirement on file; whether it matters depends on this capacitor's role in the rail's PDN target. Left for the owner.
At C11, C13, C60
Each finding, with its own headline
C11C11 on 'P3V3': its rail pad reaches its via over 2.22 mm of track and its ground pad over 0.00 mm, adding about 0.62 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)
C11 on 'P3V3': its rail pad reaches its via over 2.22 mm of track and its ground pad over 0.00 mm, adding about 0.62 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). C11.1 (rail) runs 2.22 mm along its copper to its nearest via, 1.22 mm past the 1 mm beside the pad: 0.62 nH; C11.2 (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 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.62 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.34 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 1.22 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.
C13C13 on 'P3V3': its rail pad reaches its via over 1.38 mm of track and its ground pad over 1.62 mm, adding about 0.51 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)
C13 on 'P3V3': its rail pad reaches its via over 1.38 mm of track and its ground pad over 1.62 mm, adding about 0.51 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). C13.1 (rail) runs 1.38 mm along its copper to its nearest via, 0.38 mm past the 1 mm beside the pad: 0.19 nH; C13.2 (ground) runs 1.62 mm along its copper to its nearest via, 0.62 mm past the 1 mm beside the pad: 0.31 nH. 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.51 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.34 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 1.22 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.
C60C60 on 'P3V3': its rail pad reaches its via over 1.45 mm of track and its ground pad over 1.67 mm, adding about 0.57 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)
C60 on 'P3V3': its rail pad reaches its via over 1.45 mm of track and its ground pad over 1.67 mm, adding about 0.57 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). C60.2 (rail) runs 1.45 mm along its copper to its nearest via, 0.45 mm past the 1 mm beside the pad: 0.23 nH; C60.1 (ground) runs 1.67 mm along its copper to its nearest via, 0.67 mm past the 1 mm beside the pad: 0.34 nH. 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.57 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.34 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 1.22 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.
- ReferencePlaneDiscontinuityminorOpen
ReferencePlaneDiscontinuity: 4 boards×4
Checked by the review, stands · Claude walker W3 (Cern session) — Checked: the reference break is read from the copper as stated. Whether it matters depends on the signal's edge rate and the receiver's margin, which no datasheet or app note on file fixes for this net; the impedance step and reflection figures are Probe's model, and the thresholds are its starting values. Layout practice, not a datasheet requirement. Left for the owner.
At along@L2:P1V8|P3V3, along@L2:P3V3|VADJ, void:P1V8@TOP_LAYER:92.27,77.63, void:P1V8@TOP_LAYER:99.64,79.38
Each finding, with its own headline
along@L2:P1V8|P3V3'FMC_SDA' runs ALONG the split between the P1V8 and P3V3 planes on L2 at 1 place, the longest 2.61 mm; the impedance rises from 70 ohm to 71 ohm there at worst, 1 % of each edge reflected (fastest: FMC_SDA at 10 ns 10-90 %, suggested by its name)
On L2 the P1V8 and P3V3 planes part, and 'FMC_SDA' 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 70 ohm; along the slot 71 ohm, reflecting up to 1 % 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 117 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.
- 'FMC_SDA' on TOP_LAYER at (112.97, 78.16), 2.9 mm, running ALONG the split for 2.61 mm, not across it, 70 ohm over solid plane, 71 ohm along it: 1 % 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/12/reference-planes?group=along%40L2%3AP1V8%7CP3V3 serves each with its own layer_image region; all of them lie in x 110.49..115.35, y 77.07..79.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.
along@L2:P3V3|VADJ'NetIC9_2' runs ALONG the split between the P3V3 and VADJ planes on L2 at 1 place, the longest 2.07 mm; the impedance rises from 66 ohm to 67 ohm there at worst, 1.1 % of each edge reflected (fastest: NetIC9_2 at 100 ps 10-90 %, ASSUMED)
On L2 the P3V3 and VADJ planes part, and 'NetIC9_2' 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 66 ohm; along the slot 67 ohm, reflecting up to 1.1 % 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 113 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.
- 'NetIC9_2' on TOP_LAYER at (111.97, 124.06), 4.24 mm, running ALONG the split for 2.07 mm, not across it, 66 ohm over solid plane, 67 ohm along it: 1.1 % 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/12/reference-planes?group=along%40L2%3AP3V3%7CVADJ serves each with its own layer_image region; all of them lie in x 109.24..114.05, y 122.62..125.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.
void:P1V8@TOP_LAYER:92.27,77.63'IO_1V8_1' crosses where the outline of the P1V8 plane on TOP_LAYER is drawn back, at 1 place, the longest 3 mm (fastest: IO_1V8_1 at 20 ns 10-90 %, suggested by its name)
Along 'IO_1V8_1' on L2, the P1V8 plane on TOP_LAYER has 3 mm under the track with copper of P1V8, not a plane, at (92.27, 77.63), 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 93.11..104.75, y 71.84..82.1 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 0 of the 1 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.
- 'IO_1V8_1' on L2 at (92.27, 77.63), 3 mm over copper of P1V8, not a plane, to the end of the track; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/12/reference-planes?group=void%3AP1V8%40TOP_LAYER%3A92.27%2C77.63 serves each with its own layer_image region; all of them lie in x 89.9..95, y 76.63..79.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.
void:P1V8@TOP_LAYER:99.64,79.38'FMC_SCL' crosses where the outline of the P1V8 plane on TOP_LAYER is drawn back, at 1 place, the longest 0.16 mm (fastest: FMC_SCL at 10 ns 10-90 %, suggested by its name)
Along 'FMC_SCL' on L2, the P1V8 plane on TOP_LAYER has 0.16 mm under the track with no copper, at (99.64, 79.38), 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 93.11..104.75, y 71.84..82.1 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 0 of the 1 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.
- 'FMC_SCL' on L2 at (99.64, 79.38), 0.16 mm over no copper, to the end of the track; other side: GND on PLANE_L3GND, 1 mm from the track against 0.225 mm to TOP_LAYER: 82% of the return on TOP_LAYER
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/12/reference-planes?group=void%3AP1V8%40TOP_LAYER%3A99.64%2C79.38 serves each with its own layer_image region; all of them lie in x 98.58..100.69, y 78.32..80.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.
Main parts
| Part number | Maker | Description | Where |
|---|---|---|---|
| 24AA64T-I/MC | MICROCHIP TECHNOLOGY | 1.7-5.5V 64K I2C Serial EEPROM | IC11 |
| 5607-4200-SH | 3M | 7 Pin + 1 Shield SATA Receptacle | J2 |
| 570BBC000121DG | SILICON LABS | Any-Rate I2C Programmable XO Oscillator Si570 Serie | OSC1 |
| AD7997BRUZ-1 | ANALOG DEVICES | 8-Channel, 10-Bit ADCs with I2C-Compatible Interface | IC12 |
| ADN4600ACPZ | ANALOG DEVICES | 4.25Gbps, 8 × 8, Asynchronous Crosspoint Switch | IC7 |
| ASP-134488-01 | SAMTEC | Connector VITA 57, 400 Male contacts in 10 row abcdefghj | J1 |
| LM1117MP-1.8/NOPB | NATIONAL SEMICONDUCTOR | 3-Terminal Regulator 1=GND 2=OUT 3=IN 4=OUT | IC10 |
| TL431CD | TEXAS INSTRUMENTS | Precision Programmable Reference | IC8 |
| TLC274CD | TEXAS INSTRUMENTS | Quad Operational Amplifier | IC9 |
| SML-311UTT86K | ROHM | LED Red 1C 2A | LD1, LD2, LD3 |
| BAT54S | FAIRCHILD SEMICONDUCTOR | Serial Schottky Diode | D1, D2, D3, D4, D5, D6 |
| MCP23017-E/SS | MICROCHIP TECHNOLOGY | 16-bit I/O Port Expander With Serial Interface | IC1, IC2, IC3, IC4, IC5, IC6 |
| R0603_270R_1%_0.1W_100PPM | GENERIC | Resistor - 1% | R41, R42 |
| R0603_2K2_1%_0.1W_100PPM | GENERIC | Resistor - 1% | R12, R15 |
| R0603_5K1_1%_0.1W_100PPM | GENERIC | Resistor - 1% | R24, R26 |
| R0603_0R_JUMPER | GENERIC | Resistor - 1% | R44, R46, R47 |
| CTE3528-21_10UF_16V_10%_LESR0800 | GENERIC | Polarised capacitor | C51, C54, C57, C58 |
| R0603_1K_1%_0.1W_100PPM | GENERIC | Resistor - 1% | R10, R11, R14, R16, R43 |
| CC0603_100NF_50V_10%_X7R | GENERIC | Non-polarised capacitor | C1, C10, C11, C12, C13, C2 and 18 more |
| CC0402_10NF_16V_10%_X7R | GENERIC | Non-polarised capacitor | C14, C15, C16, C17, C18, C19 and 26 more |
| R0603_10K_1%_0.1W_100PPM | GENERIC | Resistor - 1% | R1, R13, R17, R18, R19, R2 and 28 more |
About this design
- Design
- FMC CONN TESTER — OHWR0009 R1
- Designed in
- Altium Designer
- Board
- 4 copper layers, 76.5 × 69 mm, 142 components, 205 nets
- Licence
- CERN-OHL-1.1
- Source
- https://gitlab.com/ohwr/project/fmc-conn-tester at commit
ef5fdf2c6e71 - Attribution
- CERN Open Hardware Repository, project ohwr/project/fmc-conn-tester (commit ef5fdf2c6e712d4bfc2cd68bfae597a487d6808f, 2025-04-09). Licence: CERN-OHL-1.1 (stated on the schematic sheets). Source: https://gitlab.com/ohwr/project/fmc-conn-tester. 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)