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

AFC

OHWR0021 · revision R1

AFC (OHWR0021 R1) is an open-hardware circuit board from the CERN Open Hardware Repository, designed in Altium Designer: a 14-layer board of 180.7 × 148.6 mm with 1515 components and 1340 nets, published under CERN-OHL-1.1.

review 82% walked · 41 findings: 1 blocker · 16 major · 24 minor (314 items)

Open in the interactive viewerRead the full review

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

Design review

Probe recorded 41 findings: 1 blocker · 16 major · 24 minor (314 items) on this design. Each is shown here with its reasoning; the full review links every one to the pins, nets and datasheet pages it rests on.

  1. NetCopperSplitblockerOpen

    NetCopperSplit: 25 boards×25

    e.g. “FMC1_CLK3_BIDIR_C_N's copper is in 2 pieces: C855.1 and IC76.2 are not connected to the rest of the net” · 25 different statements

    At split:FMC1_CLK3_BIDIR_C_N, split:FMC1_CLK3_BIDIR_C_P, split:FMC1_P3V3, split:FMC2_CLK3_BIDIR_C_N, split:FMC2_CLK3_BIDIR_C_P, split:FMC2_P3V3 and 19 more

    Each finding, with its own headline
    • split:FMC1_CLK3_BIDIR_C_NFMC1_CLK3_BIDIR_C_N's copper is in 2 pieces: C855.1 and IC76.2 are not connected to the rest of the net

      FMC1_CLK3_BIDIR_C_N's copper is in 2 pieces: C855.1 and IC76.2 are not connected to the rest of the net. Piece 1: C497.2 and IC8.56, on TOP, L1, L2, L3, L5, L6 and BTM, 2 drill(s), over (-133.05, 1.4) to (-121.26, 49.65). Piece 2: C855.1 and IC76.2, on TOP, over (-120.69, 47.14) to (-119.07, 47.7). The export files every one of these pins under the net, so every connectivity check passes; the copper the fab builds leaves them apart. Usually a pour island that touches only one via of its own net, or a track ending short of its copper: join the piece to the net and export again.

    • split:FMC1_CLK3_BIDIR_C_PFMC1_CLK3_BIDIR_C_P's copper is in 2 pieces: C852.1 and IC76.1 are not connected to the rest of the net

      FMC1_CLK3_BIDIR_C_P's copper is in 2 pieces: C852.1 and IC76.1 are not connected to the rest of the net. Piece 1: C495.2 and IC8.55, on TOP, L1, L2, L3, L5, L6 and BTM, 2 drill(s), over (-132.5, 1.4) to (-121.23, 49.09). Piece 2: C852.1 and IC76.1, on TOP, over (-120.69, 46.54) to (-119.07, 46.94). The export files every one of these pins under the net, so every connectivity check passes; the copper the fab builds leaves them apart. Usually a pour island that touches only one via of its own net, or a track ending short of its copper: join the piece to the net and export again.

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

      FMC1_P3V3's copper is in 3 pieces: C3A.1 and 1 other piece(s) are not connected to the rest of the net. Piece 1: C139.1, C142.1, C1A.1, C4A.2, C5A.1, C6A.2, IC12.6, J15A.c39 and 6 more pin(s), on TOP, L1, L2, L3, L5, L6 and BTM, 19 drill(s), 40.74 mm2 of pour, over (-109.5, -24.93) to (-52.12, 100.58). Piece 2: C3A.1, on TOP, over (-106.53, 97.05) to (-105.58, 98.05). Piece 3: C2A.1, on TOP, over (-106.55, 94.48) to (-105.6, 95.48). The export files every one of these pins under the net, so every connectivity check passes; the copper the fab builds leaves them apart. Usually a pour island that touches only one via of its own net, or a track ending short of its copper: join the piece to the net and export again.

    • split:FMC2_CLK3_BIDIR_C_NFMC2_CLK3_BIDIR_C_N's copper is in 2 pieces: C513.2 and IC8.3 are not connected to the rest of the net

      FMC2_CLK3_BIDIR_C_N's copper is in 2 pieces: C513.2 and IC8.3 are not connected to the rest of the net. Piece 1: C870.1 and IC77.2, on TOP, over (-120.64, -23.94) to (-119.02, -23.37). Piece 2: C513.2 and IC8.3, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-141.49, -21.57) to (-120.48, -13.1). The export files every one of these pins under the net, so every connectivity check passes; the copper the fab builds leaves them apart. Usually a pour island that touches only one via of its own net, or a track ending short of its copper: join the piece to the net and export again.

    • split:FMC2_CLK3_BIDIR_C_PFMC2_CLK3_BIDIR_C_P's copper is in 2 pieces: C511.2 and IC8.2 are not connected to the rest of the net

      FMC2_CLK3_BIDIR_C_P's copper is in 2 pieces: C511.2 and IC8.2 are not connected to the rest of the net. Piece 1: C866.1 and IC77.1, on TOP, over (-120.64, -24.53) to (-119.02, -24.13). Piece 2: C511.2 and IC8.2, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-142.05, -21.54) to (-121.09, -13.1). The export files every one of these pins under the net, so every connectivity check passes; the copper the fab builds leaves them apart. Usually a pour island that touches only one via of its own net, or a track ending short of its copper: join the piece to the net and export again.

    • split:FMC2_P3V3FMC2_P3V3's copper is in 4 pieces: C1B.1 and 2 other piece(s) are not connected to the rest of the net

      FMC2_P3V3's copper is in 4 pieces: C1B.1 and 2 other piece(s) are not connected to the rest of the net. Piece 1: C119.1, C122.1, C4B.2, C5B.1, C6B.2, IC12.1, J15B.c39, J15B.d36 and 5 more pin(s), on TOP, L1, L2, L3, L5, L6 and BTM, 18 drill(s), 41.59 mm2 of pour, over (-109.25, -24.93) to (-58.95, 28.02). Piece 2: C1B.1, on TOP, over (-105.08, 26.2) to (-103.28, 27.88). Piece 3: C2B.1, on TOP, over (-103.83, 23.58) to (-102.83, 24.53). Piece 4: C3B.1, on TOP, over (-105.8, 23.6) to (-104.8, 24.55). The export files every one of these pins under the net, so every connectivity check passes; the copper the fab builds leaves them apart. Usually a pour island that touches only one via of its own net, or a track ending short of its copper: join the piece to the net and export again.

    • split:MGTAVCC_G10MGTAVCC_G10's copper is in 8 pieces: C730.2, C736.2, IC2.AJ18 and IC2.AJ20 and 6 other piece(s) are not connected to the rest of the net

      MGTAVCC_G10's copper is in 8 pieces: C730.2, C736.2, IC2.AJ18 and IC2.AJ20 and 6 other piece(s) are not connected to the rest of the net. Piece 1: C253.2, C267.2, C734.2, IC2.AG17 and IC2.AJ16, on TOP, L1, L2, L3, L5, L6 and BTM, 2 drill(s), over (-60.19, 65.08) to (-57.01, 68.21). Piece 2: C730.2, C736.2, IC2.AJ18 and IC2.AJ20, on TOP, L1, L2, L3, L5, L6 and BTM, 2 drill(s), over (-58.19, 62.38) to (-57.07, 66.2). Piece 3: C737.2 and IC2.AG19, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-60.19, 62.88) to (-59.24, 65.18). Piece 4: C254.2 and IC2.AG15, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-60.19, 67.17) to (-59.24, 68.78). Piece 5: C731.2 and IC2.AG21, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-60.19, 61) to (-59.24, 62.33). Piece 6: FB5.2, on TOP, over (-50.45, 68.58) to (-48.85, 71.98). Piece 7: C735.2, on TOP, over (-57.83, 68.88) to (-57.38, 69.28). Piece 8: IC2.AJ14, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-58.88, 68.83) to (-57.24, 69.78). The export files every one of these pins under the net, so every connectivity check passes; the copper the fab builds leaves them apart. Usually a pour island that touches only one via of its own net, or a track ending short of its copper: join the piece to the net and export again.

    • split:MGTAVCC_G11MGTAVCC_G11's copper is in 16 pieces: C252.2 and IC2.F18 and 14 other piece(s) are not connected to the rest of the net

      MGTAVCC_G11's copper is in 16 pieces: C252.2 and IC2.F18 and 14 other piece(s) are not connected to the rest of the net. Piece 1: C733.2 and IC2.H21, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-79.95, 60.02) to (-78.69, 62.33). Piece 2: C252.2 and IC2.F18, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-81.64, 63.4) to (-80.68, 65.33). Piece 3: C263.2, on TOP, over (-79.52, 62.37) to (-78.85, 63.28). Piece 4: IC2.H19, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-79.99, 63.38) to (-78.69, 64.54). Piece 5: C601.2, on TOP, over (-81, 67.85) to (-79.95, 68.68). Piece 6: C272.2, on TOP, over (-79.43, 65.08) to (-78.48, 66.08). Piece 7: C603.2, on TOP, over (-79.52, 66.88) to (-79.07, 67.28). Piece 8: C732.2, on TOP, over (-79.52, 67.88) to (-79.07, 68.28). Piece 9: C262.2, on TOP, over (-81.53, 61.88) to (-81.08, 62.28). Piece 10: C604.2, on TOP, over (-81.53, 69.88) to (-81.08, 70.28). Piece 11: FB6.2, on TOP, over (-91.48, 57.63) to (-88.08, 59.23). Piece 12: IC2.H17, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-79.64, 65.83) to (-78.69, 66.78). Piece 13: IC2.H15, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-79.64, 67.83) to (-78.69, 68.78). Piece 14: IC2.F16, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-81.19, 66.83) to (-80.24, 67.78). Piece 15: IC2.F20, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-81.64, 62.38) to (-80.69, 63.33). Piece 16: IC2.F14, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-81.64, 68.83) to (-80.69, 69.78). The export files every one of these pins under the net, so every connectivity check passes; the copper the fab builds leaves them apart. Usually a pour island that touches only one via of its own net, or a track ending short of its copper: join the piece to the net and export again.

    • split:MGTAVTT_G10MGTAVTT_G10's copper is in 11 pieces: C722.2, IC2.AJ22 and R239.1 and 9 other piece(s) are not connected to the rest of the net

      MGTAVTT_G10's copper is in 11 pieces: C722.2, IC2.AJ22 and R239.1 and 9 other piece(s) are not connected to the rest of the net. Piece 1: C257.2, C725.2, IC2.AL21, IC2.AN20 and IC2.AN22, on TOP, L1, L2, L3, L5, L6 and BTM, 3 drill(s), over (-56.19, 60.38) to (-53.07, 63.33). Piece 2: C722.2, IC2.AJ22 and R239.1, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-58.19, 59.8) to (-56.87, 61.73). Piece 3: C726.2 and IC2.AN14, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-54.19, 68.83) to (-53.07, 69.78). Piece 4: C729.2 and IC2.AN18, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-54.19, 63.88) to (-53.07, 65.33). Piece 5: C605.2 and IC2.AN16, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-54.64, 65.87) to (-53.03, 67.78). Piece 6: C251.2 and IC2.AL13, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-56.19, 69.5) to (-54.87, 70.78). Piece 7: C600.2 and IC2.AL15, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-56.19, 67.3) to (-54.67, 68.78). Piece 8: C255.2, on TOP, over (-56.52, 64.5) to (-55.87, 65.28). Piece 9: FB8.2, on TOP, over (-52.08, 63.5) to (-48.68, 65.1). Piece 10: IC2.AL19, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-56.19, 63.38) to (-54.82, 64.33). Piece 11: IC2.AL17, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-56.64, 65.38) to (-55.69, 66.33). The export files every one of these pins under the net, so every connectivity check passes; the copper the fab builds leaves them apart. Usually a pour island that touches only one via of its own net, or a track ending short of its copper: join the piece to the net and export again.

    • split:MGTAVTT_G11MGTAVTT_G11's copper is in 14 pieces: IC2.F22 and R142.1 and 12 other piece(s) are not connected to the rest of the net

      MGTAVTT_G11's copper is in 14 pieces: IC2.F22 and R142.1 and 12 other piece(s) are not connected to the rest of the net. Piece 1: C256.2, C259.2, IC2.D13 and IC2.D15, on TOP, L1, L2, L3, L5, L6 and BTM, 2 drill(s), over (-83.65, 67.83) to (-82.58, 70.78). Piece 2: IC2.F22 and R142.1, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-81.85, 59.75) to (-80.69, 61.33). Piece 3: C599.2 and IC2.B16, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-85.19, 66.67) to (-84.24, 67.78). Piece 4: C724.2 and IC2.B22, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-86.16, 59.51) to (-84.69, 61.33). Piece 5: C723.2 and IC2.B18, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-85.99, 64.83) to (-84.69, 66.48). Piece 6: C258.2 and IC2.B14, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-85.19, 68.35) to (-84.23, 69.33). Piece 7: C728.2, on TOP, over (-83.33, 60.51) to (-82.5, 61.25). Piece 8: C727.2, on TOP, over (-84.53, 62.62) to (-83.89, 63.33). Piece 9: FB7.2, on TOP, over (-88.55, 63.53) to (-86.52, 66.93). Piece 10: C268.2, on TOP, over (-82.72, 65.08) to (-81.77, 66.08). Piece 11: IC2.D19, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-83.19, 63.83) to (-82.24, 64.84). Piece 12: IC2.D17, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-83.61, 65.4) to (-82.69, 66.33). Piece 13: IC2.D21, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-83.65, 61.33) to (-82.69, 62.33). Piece 14: IC2.B20, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-85.65, 62.33) to (-84.69, 63.33). The export files every one of these pins under the net, so every connectivity check passes; the copper the fab builds leaves them apart. Usually a pour island that touches only one via of its own net, or a track ending short of its copper: join the piece to the net and export again.

    • split:P1V0P1V0's copper is in 6 pieces: C583.2 and 4 other piece(s) are not connected to the rest of the net

      P1V0's copper is in 6 pieces: C583.2 and 4 other piece(s) are not connected to the rest of the net. Piece 1: C154.2, C155.2, C156.2, C157.2, C158.2, C160.2, C161.1, C162.1 and 133 more pin(s), on TOP, L1, L2, L3, L5, L6 and BTM, 154 drill(s), 408.96 mm2 of pour, over (-97.18, 5.65) to (-33.15, 78.03). Piece 2: C583.2, on BTM, over (-78.28, 36.48) to (-77.08, 37.48). Piece 3: C608.2, on BTM, over (-93.31, 76.95) to (-92.36, 77.95). Piece 4: C586.2, on BTM, over (-93.48, 50.03) to (-92.53, 51.03). Piece 5: C609.2, on BTM, over (-93.5, 74.75) to (-92.55, 75.75). Piece 6: C607.2, on BTM, over (-93.68, 47.88) to (-92.73, 48.88). The export files every one of these pins under the net, so every connectivity check passes; the copper the fab builds leaves them apart. Usually a pour island that touches only one via of its own net, or a track ending short of its copper: join the piece to the net and export again.

    • split:P1V2P1V2's copper is in 2 pieces: FB8.1 is not connected to the rest of the net

      P1V2's copper is in 2 pieces: FB8.1 is not connected to the rest of the net. Piece 1: C33.1, C34.1, C41.1, C46.1, C47.1, C64.1, FB7.1, L2.2 and 2 more pin(s), on TOP, L1, L2, L3, L5, L6 and BTM, 11 drill(s), 84.57 mm2 of pour, over (-92.9, 4.5) to (-46.08, 66.93). Piece 2: FB8.1, on TOP, over (-52.08, 59.3) to (-48.68, 60.9). The export files every one of these pins under the net, so every connectivity check passes; the copper the fab builds leaves them apart. Usually a pour island that touches only one via of its own net, or a track ending short of its copper: join the piece to the net and export again.

    • split:P1V5P1V5's copper is in 17 pieces: C641.2 and IC2.AN10 and 15 other piece(s) are not connected to the rest of the net

      P1V5's copper is in 17 pieces: C641.2 and IC2.AN10 and 15 other piece(s) are not connected to the rest of the net. Piece 1: C101.1, C103.1, C104.1, C105.1, C109.1, C110.2, C143.1, C144.1 and 147 more pin(s), on TOP, L1, L2, L3, L5, L6 and BTM, 105 drill(s), 100.73 mm2 of pour, over (-99.15, -28.23) to (-21.48, 109.66). Piece 2: C641.2 and IC2.AN10, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-54.33, 72.83) to (-53.24, 73.78). Piece 3: C637.2, on TOP, over (-50.13, 93.53) to (-49.18, 94.53). Piece 4: C638.1, on TOP, over (-51.05, 86.35) to (-49.9, 89.05). Piece 5: C447.1, on TOP, over (-51.05, 90.05) to (-49.9, 92.75). Piece 6: C106.2, on TOP, over (-51.15, 75.98) to (-50.2, 76.98). Piece 7: C446.2, on TOP, over (-51.35, 73.68) to (-50.4, 74.68). Piece 8: C636.2, on TOP, over (-51.38, 80.53) to (-50.43, 81.53). Piece 9: C639.2, on TOP, over (-58.78, 80.88) to (-58.33, 81.28). Piece 10: C478.2, on TOP, over (-60.08, 83.65) to (-59.08, 84.6). Piece 11: C107.2, on TOP, over (-61.83, 83.65) to (-60.83, 84.6). Piece 12: IC26.A9, on BTM, over (-47.51, 96.21) to (-47.21, 96.51). Piece 13: IC24.A9, on BTM, over (-69.24, 96.2) to (-68.93, 96.5). Piece 14: IC15.A2, on BTM, over (-42.26, 96.21) to (-41.96, 96.51). Piece 15: IC26.A2, on BTM, over (-53.11, 96.21) to (-52.81, 96.51). Piece 16: IC16.A9, on BTM, over (-58.33, 96.2) to (-58.02, 96.5). Piece 17: IC16.A2, on BTM, over (-63.93, 96.2) to (-63.62, 96.5). The export files every one of these pins under the net, so every connectivity check passes; the copper the fab builds leaves them apart. Usually a pour island that touches only one via of its own net, or a track ending short of its copper: join the piece to the net and export again.

    • split:P1V8P1V8's copper is in 2 pieces: L12.1 is not connected to the rest of the net

      P1V8's copper is in 2 pieces: L12.1 is not connected to the rest of the net. Piece 1: C456.1, C50.1, C53.1, C54.1, C55.1, C71.1, L7.2, R307.1 and 1 more pin(s), on TOP, L1, L2, L3, L5, L6 and BTM, 16 drill(s), 84.38 mm2 of pour, over (-75.92, 3.5) to (-54.19, 44.6). Piece 2: L12.1, on BTM, over (-56.68, 39.1) to (-55.28, 42.3). The export files every one of these pins under the net, so every connectivity check passes; the copper the fab builds leaves them apart. Usually a pour island that touches only one via of its own net, or a track ending short of its copper: join the piece to the net and export again.

    • split:P3V3P3V3's copper is in 20 pieces: C260.2, C261.2, C769.1, C771.1, C772.1, C775.1, IC2.L13, IC2.T11 and 5 more pin(s) and 18 other piece(s) are not connected to the rest of the net

      P3V3's copper is in 20 pieces: C260.2, C261.2, C769.1, C771.1, C772.1, C775.1, IC2.L13, IC2.T11 and 5 more pin(s) and 18 other piece(s) are not connected to the rest of the net. Piece 1: C29.1, C30.1, C31.1, C389.2, C391.2, C398.1, C400.1, C543.2 and 55 more pin(s), on TOP, L1, L2, L3, L5, L6 and BTM, 44 drill(s), 6472.1 mm2 of pour, over (-179.58, -34.61) to (-87.58, 109.66). Piece 2: C260.2, C261.2, C769.1, C771.1, C772.1, C775.1, IC2.L13, IC2.T11 and 5 more pin(s), on TOP, L1, L2, L3, L5, L6 and BTM, 6 drill(s), over (-76.93, 63.58) to (-21.6, 84.78). Piece 3: C500.1, C502.1, C508.1, C510.1, IC36.6, IC37.6, IC40.23, IC40.24 and 1 more pin(s), on TOP, L1, L2, L3, L5, L6 and BTM, 4 drill(s), over (-21.88, -23.68) to (-19.45, -20.03). Piece 4: C539.1, C540.1, C541.1, C542.1, IC43.6, L15.2, R53.2 and R65.2, on TOP, L1, L2, L3, L5, L6 and BTM, 9 drill(s), 69.18 mm2 of pour, over (-79.83, -25.93) to (-70.1, -13.4). Piece 5: C383.1, C385.1, IC23.11, IC23.15 and IC23.16, on TOP, L1, L2, L3, L5, L6 and BTM, 2 drill(s), over (-14.1, -21.45) to (-10.35, -19.29). Piece 6: C384.1, C388.1, IC23.2, IC23.45 and IC23.46, on TOP, L1, L2, L3, L5, L6 and BTM, 2 drill(s), over (-14.28, -27.71) to (-10.28, -25.43). Piece 7: C303.1, IC22.45 and IC22.46, on TOP, L1, L2, L3, L5, L6 and BTM, 2 drill(s), over (-14.1, -16.71) to (-13.2, -15.19). Piece 8: C297.1, IC22.15 and IC22.16, on TOP, L1, L2, L3, L5, L6 and BTM, 2 drill(s), over (-14.1, -9.81) to (-13.2, -8.29). Piece 9: C496.1, IC34.6 and R309.1, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-21.63, -12.65) to (-19.63, -11.83). Piece 10: C304.1 and IC22.24, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-18.23, -9.4) to (-17.7, -8.29). Piece 11: C300.1 and IC22.37, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-18.23, -16.71) to (-17.7, -15.6). Piece 12: C386.1 and IC23.24, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-18.23, -20.4) to (-17.73, -19). Piece 13: C387.1 and IC23.37, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-18.23, -27.71) to (-17.7, -26.6). Piece 14: C378.2 and IC28.6, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-21.63, -8.15) to (-20.13, -7.43). Piece 15: C377.2 and IC29.6, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-21.63, -10.4) to (-20.13, -9.68). Piece 16: C498.1 and IC35.6, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-21.6, -14.9) to (-20.13, -14.03). Piece 17: C504.1 and IC39.6, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-21.65, -28.18) to (-20.15, -27.68). Piece 18: C302.1 and IC22.11, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-12.51, -10.56) to (-10.23, -10.06). Piece 19: C301.1 and IC22.2, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-12.05, -14.95) to (-10.28, -14.55). Piece 20: C506.1 and IC38.6, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-21.65, -25.93) to (-20.15, -25.2). The export files every one of these pins under the net, so every connectivity check passes; the copper the fab builds leaves them apart. Usually a pour island that touches only one via of its own net, or a track ending short of its copper: join the piece to the net and export again.

    • split:P3V3_CLEANP3V3_CLEAN's copper is in 17 pieces: C888.1, IC82.1 and R317.2 and 15 other piece(s) are not connected to the rest of the net

      P3V3_CLEAN's copper is in 17 pieces: C888.1, IC82.1 and R317.2 and 15 other piece(s) are not connected to the rest of the net. Piece 1: C468.2, IC51.1 and IC51.3, on TOP, L1, L2, L3, L5, L6 and BTM, 3 drill(s), over (-175.55, 4.98) to (-170.45, 7.7). Piece 2: C888.1, IC82.1 and R317.2, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-157.45, -28.01) to (-148.56, -25.99). Piece 3: C767.1, IC48.7 and L9.2, on TOP, L1, L2, L3, L5, L6 and BTM, 2 drill(s), over (-156.7, -18.5) to (-153.3, -14.03). Piece 4: C455a.2, C455b.2 and L13.2, on TOP, over (-175.07, -9.11) to (-171.19, -6.23). Piece 5: C428.2 and IC50.7, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-159.18, 1.8) to (-156.9, 2.33). Piece 6: C434.1 and OSC2.6, on TOP, L1, L2, L3, L5, L6 and BTM, 2 drill(s), over (-165.87, -6.75) to (-164.07, -3.18). Piece 7: C749.1 and IC52.1, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-170.3, -7.85) to (-169.13, -5.63). Piece 8: C750.1 and IC53.1, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-173.25, 0.85) to (-171.65, 2.95). Piece 9: C433.1 and IC50.1, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-159.18, -1.2) to (-157.08, -0.75). Piece 10: C584.1 and IC50.4, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-159.18, 0.31) to (-157.4, 0.76). Piece 11: C429.1 and IC50.9, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-159.58, 2.76) to (-158.53, 4.7). Piece 12: C430.1 and IC50.30, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-160.7, -3.45) to (-160.2, -1.24). Piece 13: C431.1 and IC50.27, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-162.18, -3.35) to (-161.7, -1.24). Piece 14: C432.1 and IC50.20, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-165.73, 0.65) to (-163.18, 1.25). Piece 15: OSC2.2, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-163.33, -10.23) to (-161.53, -7.4). Piece 16: L21.2, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-171.28, 8.28) to (-169.48, 9.73). Piece 17: R219.1, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-174.54, -13.64) to (-173.38, -13.04). The export files every one of these pins under the net, so every connectivity check passes; the copper the fab builds leaves them apart. Usually a pour island that touches only one via of its own net, or a track ending short of its copper: join the piece to the net and export again.

    • split:P3V3_PMONP3V3_PMON's copper is in 11 pieces: C617.1 and IC19.6 and 9 other piece(s) are not connected to the rest of the net

      P3V3_PMON's copper is in 11 pieces: C617.1 and IC19.6 and 9 other piece(s) are not connected to the rest of the net. Piece 1: C620.1 and IC59.6, on TOP, over (-159.07, 39.85) to (-156.75, 40.51). Piece 2: C617.1 and IC19.6, on TOP, over (-159.08, 31.6) to (-156.78, 32.26). Piece 3: C621.1 and IC61.6, on TOP, over (-159.08, 43.35) to (-156.78, 44.01). Piece 4: C616.1 and IC60.6, on TOP, over (-159.08, 28.1) to (-156.78, 28.76). Piece 5: C618.1 and IC20.6, on TOP, over (-159.08, 36.35) to (-156.78, 37.01). Piece 6: C619.1 and IC21.6, on TOP, over (-159.08, 24.1) to (-157.58, 25.26). Piece 7: IC61.1 and IC61.2, on TOP, over (-163.98, 45.24) to (-161.79, 46.01). Piece 8: R147.2 and R265.2, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-166.53, 24.58) to (-164.65, 27.78). Piece 9: IC21.1, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-163.98, 26.99) to (-162.48, 27.75). Piece 10: L17.2, on TOP, over (-163.78, 34.76) to (-162.63, 36.21). Piece 11: IC60.2, on TOP, over (-163.98, 29.99) to (-162.48, 30.26). The export files every one of these pins under the net, so every connectivity check passes; the copper the fab builds leaves them apart. Usually a pour island that touches only one via of its own net, or a track ending short of its copper: join the piece to the net and export again.

    • split:POWER1.12P0VPOWER1.12P0V's copper is in 3 pieces: C15A.2 and J15A.c37 and 1 other piece(s) are not connected to the rest of the net

      POWER1.12P0V's copper is in 3 pieces: C15A.2 and J15A.c37 and 1 other piece(s) are not connected to the rest of the net. Piece 1: C12A.1, C13A.1, C14A.1, R266.2 and R41.2, on TOP, over (-123.58, 93.64) to (-116.63, 102.55). Piece 2: C15A.2 and J15A.c37, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-107.98, 93.07) to (-106.53, 94.21). Piece 3: C11A.2 and J15A.c35, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-107.98, 90.53) to (-106.53, 92.1). The export files every one of these pins under the net, so every connectivity check passes; the copper the fab builds leaves them apart. Usually a pour island that touches only one via of its own net, or a track ending short of its copper: join the piece to the net and export again.

    • split:POWER2.12P0VPOWER2.12P0V's copper is in 6 pieces: C15B.2 and J15B.c35 and 4 other piece(s) are not connected to the rest of the net

      POWER2.12P0V's copper is in 6 pieces: C15B.2 and J15B.c35 and 4 other piece(s) are not connected to the rest of the net. Piece 1: C11B.2 and J15B.c37, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-107.98, 23.07) to (-106.38, 24.21). Piece 2: C15B.2 and J15B.c35, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-107.98, 20.53) to (-106.8, 21.67). Piece 3: C13B.1 and C14B.1, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-123.58, 15.2) to (-120.63, 16.15). Piece 4: C12B.1, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-126.58, 14.03) to (-124.1, 15.43). Piece 5: R42.2, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-127.28, 16.26) to (-125.41, 17.38). Piece 6: R267.2, on TOP, over (-123.97, 16.61) to (-121.94, 19.79). The export files every one of these pins under the net, so every connectivity check passes; the copper the fab builds leaves them apart. Usually a pour island that touches only one via of its own net, or a track ending short of its copper: join the piece to the net and export again.

    • split:PVADJ1PVADJ1's copper is in 8 pieces: C100.1, IC25.2 and R178.2 and 6 other piece(s) are not connected to the rest of the net

      PVADJ1's copper is in 8 pieces: C100.1, IC25.2 and R178.2 and 6 other piece(s) are not connected to the rest of the net. Piece 1: C474.1, C676.1, C677.1, C678.1, C679.1, C682.2, C683.2, C684.2 and 76 more pin(s), on TOP, L1, L2, L3, L5, L6 and BTM, 69 drill(s), 48.37 mm2 of pour, over (-115.1, -17.38) to (-21.72, 100.2). Piece 2: C100.1, IC25.2 and R178.2, on TOP, L1, L2, L3, L5, L6 and BTM, 2 drill(s), over (-112.02, 106.03) to (-109.75, 107.6). Piece 3: C680.2, on TOP, over (-67.33, 80.3) to (-65.55, 81.25). Piece 4: C690.2, on TOP, over (-68.85, 82.95) to (-67.85, 84.23). Piece 5: C695.2, on TOP, over (-69.33, 80.51) to (-68.82, 81.73). Piece 6: C681.2, on TOP, over (-64.9, 83.3) to (-63.95, 84.3). Piece 7: C10A.2, on TOP, over (-111.35, 95.85) to (-110.9, 96.25). Piece 8: R83.2, on BTM, over (-111, 107.03) to (-110.4, 107.63). The export files every one of these pins under the net, so every connectivity check passes; the copper the fab builds leaves them apart. Usually a pour island that touches only one via of its own net, or a track ending short of its copper: join the piece to the net and export again.

    • split:PVADJ2PVADJ2's copper is in 9 pieces: C715.1, IC2.B28, IC2.C25, IC2.D32, IC2.E29 and IC2.F26 and 7 other piece(s) are not connected to the rest of the net

      PVADJ2's copper is in 9 pieces: C715.1, IC2.B28, IC2.C25, IC2.D32, IC2.E29 and IC2.F26 and 7 other piece(s) are not connected to the rest of the net. Piece 1: C10B.2, C128.2, C408.2, C644.2, C645.2, C646.2, C647.2, C648.2 and 71 more pin(s), on TOP, L1, L2, L3, L5, L6 and BTM, 66 drill(s), 24.48 mm2 of pour, over (-167.85, -28.52) to (-22.78, 77.75). Piece 2: C715.1, IC2.B28, IC2.C25, IC2.D32, IC2.E29 and IC2.F26, on TOP, L1, L2, L3, L5, L6 and BTM, 13 drill(s), 9.89 mm2 of pour, over (-85.88, 49.14) to (-80.63, 58.33). Piece 3: R214.1 and R271.1, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-170.05, -22.65) to (-169.13, -20.05). Piece 4: C665.2, on TOP, over (-66.58, 51.95) to (-65.32, 52.45). Piece 5: C658.2, on TOP, over (-72.1, 53.45) to (-71.58, 54.68). Piece 6: C659.2, on TOP, over (-75.63, 54.45) to (-74.58, 55.83). Piece 7: C714.1, on TOP, over (-83.03, 48.95) to (-81.88, 51.65). Piece 8: C661.2, on TOP, over (-84.12, 52.08) to (-83.17, 53.08). Piece 9: IC2.A31, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-86.76, 51.27) to (-85.63, 52.4). The export files every one of these pins under the net, so every connectivity check passes; the copper the fab builds leaves them apart. Usually a pour island that touches only one via of its own net, or a track ending short of its copper: join the piece to the net and export again.

    • split:PWRAPWRA's copper is in 7 pieces: J1.A1 and 5 other piece(s) are not connected to the rest of the net

      PWRA's copper is in 7 pieces: J1.A1 and 5 other piece(s) are not connected to the rest of the net. Piece 1: J1.B1 and J1.B2, on TOP, L1, L2, L3, L5, L6 and BTM, 2 drill(s), 6.07 mm2 of pour, over (-12.73, 43.38) to (-9.15, 52.9). Piece 2: J1.A1, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-8.75, 49.3) to (-7.65, 50.4). Piece 3: J1.A2, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-8.75, 51.8) to (-7.65, 52.9). Piece 4: Q13.5, on TOP, over (-13.33, 38.84) to (-11.3, 39.45). Piece 5: Q13.6, on TOP, over (-13.33, 40.11) to (-11.3, 40.72). Piece 6: Q13.7, on TOP, over (-13.33, 41.38) to (-11.3, 41.99). Piece 7: Q13.8, on TOP, over (-13.33, 42.65) to (-11.3, 43.26). The export files every one of these pins under the net, so every connectivity check passes; the copper the fab builds leaves them apart. Usually a pour island that touches only one via of its own net, or a track ending short of its copper: join the piece to the net and export again.

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

      VCCAUX's copper is in 5 pieces: C597.2 and 3 other piece(s) are not connected to the rest of the net. Piece 1: C266.2, C269.2, C270.2, C271.2, C275.2, C276.2, C277.2, C278.2 and 33 more pin(s), on TOP, L1, L2, L3, L5, L6 and BTM, 36 drill(s), 4.67 mm2 of pour, over (-75.64, 39.87) to (-58.19, 72.09). Piece 2: C597.2, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-58.59, 37.13) to (-56.35, 38.83). Piece 3: L12.2, on BTM, over (-58.68, 39.1) to (-57.28, 42.3). Piece 4: C592.1, on BTM, over (-62.45, 40.65) to (-59.75, 41.8). Piece 5: C593.1, on BTM, over (-65.85, 40.68) to (-63.15, 41.83). The export files every one of these pins under the net, so every connectivity check passes; the copper the fab builds leaves them apart. Usually a pour island that touches only one via of its own net, or a track ending short of its copper: join the piece to the net and export again.

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

      VCCBRAM's copper is in 3 pieces: C246.2 and 1 other piece(s) are not connected to the rest of the net. Piece 1: C226.1, C244.2, C245.2, C247.2, C248.2, C249.2, C250.2, C264.2 and 18 more pin(s), on TOP, L1, L2, L3, L5, L6 and BTM, 25 drill(s), 2.4 mm2 of pour, over (-79.55, 40.48) to (-63.15, 64.38). Piece 2: C246.2, on TOP, over (-68.21, 63) to (-67.37, 63.45). Piece 3: C243.2, on TOP, over (-68.14, 61.21) to (-67.74, 61.66). The export files every one of these pins under the net, so every connectivity check passes; the copper the fab builds leaves them apart. Usually a pour island that touches only one via of its own net, or a track ending short of its copper: join the piece to the net and export again.

    • split:VTTVTT's copper is in 12 pieces: C369.1, C373.1, C375.1, R163.1, R183.1, R187.1, R189.1, R190.1 and 5 more pin(s) and 10 other piece(s) are not connected to the rest of the net

      VTT's copper is in 12 pieces: C369.1, C373.1, C375.1, R163.1, R183.1, R187.1, R189.1, R190.1 and 5 more pin(s) and 10 other piece(s) are not connected to the rest of the net. Piece 1: C366.1, C367.1, C368.1, R177.1, R182.1, R185.1, R193.1, R194.1 and 5 more pin(s), on TOP, L1, L2, L3, L5, L6 and BTM, 3 drill(s), over (-86.3, 95.64) to (-84.78, 107.04). Piece 2: C369.1, C373.1, C375.1, R163.1, R183.1, R187.1, R189.1, R190.1 and 5 more pin(s), on TOP, L1, L2, L3, L5, L6 and BTM, 4 drill(s), over (-86.3, 95.09) to (-84.78, 106.44). Piece 3: C371.1, C544.2, C545.2, IC44.3, R143.1 and R181.1, on TOP, L1, L2, L3, L5, L6 and BTM, 11 drill(s), 24.26 mm2 of pour, over (-95.23, 77.7) to (-47, 102.33). Piece 4: C364.1, C365.1, R199.1 and R203.1, on TOP, over (-80.78, 95.74) to (-78.54, 97.83). Piece 5: R186.1 and R188.1, on TOP, over (-79.85, 105.29) to (-79.25, 106.74). Piece 6: C374.1 and R184.1, on TOP, over (-80.25, 104.06) to (-78.75, 105.04). Piece 7: R286.1, on TOP, over (-91.25, 102.12) to (-89.07, 103.08). Piece 8: R197.1, on TOP, over (-79.21, 102.83) to (-78.36, 103.68). Piece 9: C370.1, on TOP, over (-80, 102.36) to (-79.4, 102.96). Piece 10: C92.1, on TOP, over (-81.6, 107.26) to (-80.65, 108.26). Piece 11: R205.1, on TOP, L1, L2, L3, L5, L6 and BTM, 1 drill(s), over (-85.8, 94.26) to (-84.78, 94.86). Piece 12: C372.1, on BTM, over (-86.3, 94.74) to (-85.85, 95.14). The export files every one of these pins under the net, so every connectivity check passes; the copper the fab builds leaves them apart. Usually a pour island that touches only one via of its own net, or a track ending short of its copper: join the piece to the net and export again.

  2. observationOBS-227majorOpen

    FPGA configuration banks 14/15 run from the adjustable FMC rail PVADJ2 (about 1.7-3.0 V), but CFGBVS is tied high and the SPI config flash is on 3.3 V

    The FPGA's SPI boot bank (bank 14) and bank 15 are powered from PVADJ2, the MMC-adjustable FMC2 VADJ rail. That rail reaches only about 1.7-3.0 V. The configuration straps and the boot flash, however, assume 3.3 V.

    What is connected

    ItemOn this boardSource
    Bank 14 / 15 VCCO balls (V30, W27, Y24, Y34, AA31, AB28 / M28, N25, P32, R29, T26, U33)PVADJ2netlist; UG475 Fig. 3-94 p.126
    SPI boot pins D00-D03, FCS_B (V28, V29, V26, V27, Y27)bank 14UG475 Fig. 3-94 p.126
    PVADJ2 regulatorIC10 TPS53126 ch1, FB set by R247 1k5 / R263 453 / R261 1k8 and the AD8402 rheostatnetlist; VFB 0.765 V (TPS53126 p.5)
    CFGBVS_0 (M12)R162 10k to P3V3 (high)netlist
    Boot flashes IC13, IC64 (M25P128)VCC = P3V3; W/HOLD pull-ups to P3V3; 10 Ohm series to bank-14 ballsnetlist

    Why it matters

    • UG475 Table 1-12 (p.22) allows CFGBVS high only when banks 0, 14 and 15 are at 2.5 V or 3.3 V. Below that it must be tied to GND, and a wrong connection can damage the device.
    • Whatever VADJ2 is set to (at most about 3.0 V), the 3.3 V flash outputs drive a bank below 3.3 V through only 10 Ohm.
    • The FPGA can only boot once the MMC has enabled PVADJ2.

    Open question for the designer

    What VADJ2 range does the firmware use, and was bank 14 meant to sit on a fixed 3.3 V rail?

  3. observationOBS-533majorOpen

    LD1117 IC74 has about 4 µF on its output; ST requires 10 µF minimum for stability

    IC74 (LD1117DT33, P12V_AUX to P3V3MP_AUX) has only C817 1 µF at its output. Even counting the 25 decoupling capacitors beyond polyfuse F3 (about 3.4 µF), the total is about 4.4 µF nominal, under half the 10 µF ST requires for stability.

    ItemValueSource
    Required output capacitance10 µF minimumLD1117 datasheet p.1
    At the output pin (P3V3MP_AUX)C817 1 µF ceramicnetlist
    Beyond F3 (P3V3MP)24 × 100 nF + C475 1 µF, ceramicnetlist
    Nominal totalabout 4.4 µF, before DC-bias and tolerance lossesarithmetic

    Why it matters

    The LD1117 is a classic NPN-pass 1117 that needs output capacitance (and ESR) for phase margin. Below the minimum it can oscillate. This rail is the management power for the MMC (P3V3MP).

    Fix: add a 10 µF or larger tantalum or low-ESR capacitor at IC74's output.

  4. ReferencePlaneDiscontinuitymajorOpen

    3 nets cross one gap in P3 and P4's negative-plane field at 3 places, the longest 31.3 mm (fastest: POWER2.3P3VAUX at 100 ps 10-90 %, ASSUMED)

    Along 'TCLKA_FMC1_N' on L3, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 31.3 mm under the track at (-118.31, 10.44). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 30.03 mm). 3 places on 3 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -118.63..-118.17, y -14.64..25.58 and the hole at x -120.03..-104.15, y 0.52..1.03 and the hole at x -123.08..-118, y 12.2..17.28. At 1 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 3 of the 5 crossing(s) have a plane on the track's other side at most twice as far away as the broken one (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The rest leave most or all of the return to the break, so the finding is a warning.

    • one stretch, cleared on 3 reference layers: 'TCLKA_FMC1_N' on L3 at (-118.31, 10.44), 31.3 mm, running ALONG the bare copper for 30.03 mm, not across it; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3 / 'TCLKA_FMC1_N' on L3 at (-118.31, 0.77), 0.51 mm; other side: no plane on P3 / 'TCLKA_FMC1_N' on L3 at (-118.31, 12.53), 0.62 mm; other side: no plane on P3
    • 'TCLKA_FMC1_P' on L3 at (-118.36, -5.44), 1.08 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
    • 'POWER2.3P3VAUX' on L2 at (-118.44, 11.4), 0.65 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3

    Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-118.63%2C-14.64%7C-118.17%2C25.58 serves each with its own layer_image region; all of them lie in x -119.63..-117.17, y -6.9..26.76 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.

    At gap:P3:hole -118.63,-14.64|-118.17,25.58

  5. CapVoltageDeratingmajorOpen

    CapVoltageDerating: 44 components×44

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

    At C108, C11A, C11B, C126, C12A, C12B and 38 more

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  6. DecapViaFanoutmajorOpen

    DecapViaFanout: 8 components×8

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

    At C398, C476, C597, C682, C696, C704, C706, C773

    Each finding, with its own headline
    • C398C398 on 'P3V3': its rail pad reaches its via over 3.96 mm of track, adding about 1.01 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads

      C398 on 'P3V3': its rail pad reaches its via over 3.96 mm of track, adding about 1.01 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads. C398.1 (rail) runs 3.96 mm along its copper to its nearest via, 2.96 mm past the 1 mm beside the pad: 1.01 nH; C398.2 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 0.70 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.01 nH in all. Put the vias at the pads (or in them), one per pad at least, the rail's and the ground's close together; the capacitor's own inductance as mounted is 0.64 nH (pad 0.05 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 0.63 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

    • C476C476 on 'P3V3MP': its rail pad reaches its via over 6.00 mm of track, adding about 1.71 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads

      C476 on 'P3V3MP': its rail pad reaches its via over 6.00 mm of track, adding about 1.71 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads. C476.1 (rail) runs at least 6.00 mm along its copper to its nearest via, 5.00 mm past the 1 mm beside the pad: 1.71 nH; C476.2 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 0.70 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.71 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.08 nH (pad 0.05 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 1.37 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

    • C597C597 on 'VCCAUX': its rail pad reaches its via over 2.34 mm of track, adding about 0.68 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads

      C597 on 'VCCAUX': its rail pad reaches its via over 2.34 mm of track, adding about 0.68 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads. C597.2 (rail) runs 2.34 mm along its copper to its nearest via, 1.34 mm past the 1 mm beside the pad: 0.68 nH; C597.1 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 1.60 mm apart (the pad pitch), 0.2 l ln(D/R) nH with R 0.127 mm (the track's width is not read): 0.68 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.43 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.37 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

    • C682C682 on 'PVADJ1': its rail pad reaches its via over 4.33 mm of track, adding about 1.69 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads

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

    • C696C696 on 'PVADJ1': its rail pad reaches its via over 2.36 mm of track, adding about 0.69 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads

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

    • C704C704 on 'PVADJ1': its rail pad reaches its via over 4.81 mm of track, adding about 1.93 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads

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

    • C706C706 on 'PVADJ1': its rail pad reaches its via over 3.24 mm of track, adding about 1.14 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads

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

    • C773C773 on 'PVADJ2': its rail pad reaches its via over 5.94 mm of track, adding about 1.69 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads

      C773 on 'PVADJ2': its rail pad reaches its via over 5.94 mm of track, adding about 1.69 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads. C773.1 (rail) runs 5.94 mm along its copper to its nearest via, 4.94 mm past the 1 mm beside the pad: 1.69 nH; C773.2 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 0.70 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.69 nH in all. Put the vias at the pads (or in them), one per pad at least, the rail's and the ground's close together; the capacitor's own inductance as mounted is 0.39 nH (pad 0.05 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 0.21 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

  7. EsdProtectorPlacementmajorOpen

    EsdProtectorPlacement: 11 components×11

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

    At IC4, IC5, IC7

    Each finding, with its own headline
    • IC4IC4.4 on 'IPMB.SCL': 1 via(s) between P1.56 and IC4.4

      IC4 (BZA462A) protects 'IPMB.SCL' at P1.56. Along the copper: 4.46 mm of track from the contact, 1 via(s) before it, on a 2.18 mm branch off the line; the line runs 306.56 mm on to IC67.16; IC4 sits 2.3 mm farther from the contact than the nearest place outside P1.

      1 via(s) between P1.56 and IC4.4: the strike reaches an inner layer before it is clamped. IC4.4 hangs 2.18 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch.

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

    • IC4IC4.6 on 'IPMB.SDA': 2 via(s) between P1.71 and IC4.6

      IC4 (BZA462A) protects 'IPMB.SDA' at P1.71. Along the copper: 21.55 mm of track from the contact, 2 via(s) before it, on a 2.18 mm branch off the line; the line runs 375.95 mm on to IC1.25; IC4 sits 8.93 mm farther from the contact than the nearest place outside P1.

      2 via(s) between P1.71 and IC4.6: the strike reaches an inner layer before it is clamped. IC4.6 hangs 2.18 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch.

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

    • IC5IC5.1 on 'ADD.GA2': IC5.1 hangs 2.65 mm off the line (limit 1 mm, default

      IC5 (BZA462A) protects 'ADD.GA2' at P1.26. Along the copper: 9.74 mm of track from the contact, 0 via(s) before it, on a 2.65 mm branch off the line; the line runs 260.37 mm on to IC67.68; IC5 sits 5.92 mm farther from the contact than the nearest place outside P1.

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

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

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

      IC5 (BZA462A) protects 'ADD.GA0' at P1.5. Along the copper: 12.68 mm of track from the contact, 1 via(s) before it, on a 4.32 mm branch off the line; the line runs 253.39 mm on to IC67.70; IC5 sits 8.41 mm farther from the contact than the nearest place outside P1.

      1 via(s) between P1.5 and IC5.4: the strike reaches an inner layer before it is clamped. IC5.4 hangs 4.32 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch.

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

    • IC7IC7.1 on 'AJTAG.TMS': 2 via(s) between P1.166 and IC7.1

      IC7 (BZA462A) protects 'AJTAG.TMS' at P1.166. Along the copper: 256.62 mm of track from the contact, 2 via(s) before it, the line runs through its pad (flow-through); the line runs 260.47 mm on to R229.1; IC7 sits 167.49 mm farther from the contact than the nearest place outside P1.

      2 via(s) between P1.166 and IC7.1: the strike reaches an inner layer before it is clamped. IC7 joins the line 256.62 mm from P1.166 on a 260.47 mm run to R229.1: nearer the far end than the contact, so the surge travels most of the line before it is clamped.

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

    • IC7IC7.1 on 'AJTAG.TMS': 2 via(s) between J6.4 and IC7.1

      IC7 (BZA462A) protects 'AJTAG.TMS' at J6.4. Along the copper: 160.67 mm of track from the contact, 2 via(s) before it, the line runs through its pad (flow-through); the line runs 164.51 mm on to R229.1; IC7 sits 106.16 mm farther from the contact than the nearest place outside J6.

      2 via(s) between J6.4 and IC7.1: the strike reaches an inner layer before it is clamped. IC7 joins the line 160.67 mm from J6.4 on a 164.51 mm run to R229.1: nearer the far end than the contact, so the surge travels most of the line before it is clamped.

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

    • IC7IC7.3 on 'AJTAG.TDI': 2 via(s) between P1.169 and IC7.3

      IC7 (BZA462A) protects 'AJTAG.TDI' at P1.169. Along the copper: 266.59 mm of track from the contact, 2 via(s) before it, the line runs through its pad (flow-through); the line runs 268.04 mm on to R230.1; IC7 sits 168.82 mm farther from the contact than the nearest place outside P1.

      2 via(s) between P1.169 and IC7.3: the strike reaches an inner layer before it is clamped. IC7 joins the line 266.59 mm from P1.169 on a 268.04 mm run to R230.1: nearer the far end than the contact, so the surge travels most of the line before it is clamped.

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

    • IC7IC7.3 on 'AJTAG.TDI': 2 via(s) between J6.10 and IC7.3

      IC7 (BZA462A) protects 'AJTAG.TDI' at J6.10. Along the copper: 161 mm of track from the contact, 2 via(s) before it, the line runs through its pad (flow-through); the line runs 162.45 mm on to R230.1; IC7 sits 100.75 mm farther from the contact than the nearest place outside J6.

      2 via(s) between J6.10 and IC7.3: the strike reaches an inner layer before it is clamped. IC7 joins the line 161 mm from J6.10 on a 162.45 mm run to R230.1: nearer the far end than the contact, so the surge travels most of the line before it is clamped.

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

    • IC7IC7.4 on 'AJTAG.TRST#': 2 via(s) between P1.167 and IC7.4

      IC7 (BZA462A) protects 'AJTAG.TRST#' at P1.167. Along the copper: 258.71 mm of track from the contact, 2 via(s) before it, the line runs through its pad (flow-through); the line runs 259.83 mm on to R226.1; IC7 sits 167.93 mm farther from the contact than the nearest place outside P1.

      2 via(s) between P1.167 and IC7.4: the strike reaches an inner layer before it is clamped. IC7 joins the line 258.71 mm from P1.167 on a 259.83 mm run to R226.1: nearer the far end than the contact, so the surge travels most of the line before it is clamped.

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

    • IC7IC7.6 on 'AJTAG.TCK': 2 via(s) between P1.165 and IC7.6

      IC7 (BZA462A) protects 'AJTAG.TCK' at P1.165. Along the copper: 261.46 mm of track from the contact, 2 via(s) before it, the line runs through its pad (flow-through); the line runs 265.34 mm on to R227.1; IC7 sits 167.05 mm farther from the contact than the nearest place outside P1.

      2 via(s) between P1.165 and IC7.6: the strike reaches an inner layer before it is clamped. IC7 joins the line 261.46 mm from P1.165 on a 265.34 mm run to R227.1: nearer the far end than the contact, so the surge travels most of the line before it is clamped.

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

    • IC7IC7.6 on 'AJTAG.TCK': 2 via(s) between J6.6 and IC7.6

      IC7 (BZA462A) protects 'AJTAG.TCK' at J6.6. Along the copper: 163.44 mm of track from the contact, 2 via(s) before it, the line runs through its pad (flow-through); the line runs 167.32 mm on to R227.1; IC7 sits 104.35 mm farther from the contact than the nearest place outside J6.

      2 via(s) between J6.6 and IC7.6: the strike reaches an inner layer before it is clamped. IC7 joins the line 163.44 mm from J6.6 on a 167.32 mm run to R227.1: nearer the far end than the contact, so the surge travels most of the line before it is clamped.

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

  8. EsdProtectorPlacementmajorOpen

    EsdProtectorPlacement: 3 components×3

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

    At D7A, D7B

    Each finding, with its own headline
    • D7AD7A.3 on 'USB_D_RA_N': D7A.3 hangs 1.12 mm off the line (limit 1 mm, default

      D7A (PRTR5V0U2X) protects 'USB_D_RA_N' at CON2A.2. Along the copper: 5.09 mm of track from the contact, 0 via(s) before it, on a 1.12 mm branch off the line; the line runs 7.14 mm on to R284A.1; D7A sits at CON2A, within 0.9 mm of the nearest place outside it to the contact: the track to it is mostly the escape out of CON2A's own pins, which no placement shortens.

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

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

    • D7AD7A.4 on 'USB_VBUSA': D7A.4 hangs 2.38 mm off the line (limit 1 mm, default

      D7A (PRTR5V0U2X) protects 'USB_VBUSA' at CON2A.1. Along the copper: 2.38 mm of track from the contact, 0 via(s) before it, on a 2.38 mm branch off the line; the line runs 9.86 mm on to C622A.2; D7A sits at CON2A, within 0.9 mm of the nearest place outside it to the contact: the track to it is mostly the escape out of CON2A's own pins, which no placement shortens.

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

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

    • D7BD7B.4 on 'USB_VBUSB': 2 via(s) between CON2B.1 and D7B.4

      D7B (PRTR5V0U2X) protects 'USB_VBUSB' at CON2B.1. Along the copper: 5.38 mm of track from the contact, 2 via(s) before it, on a 3.36 mm branch off the line; the line runs 2.02 mm on to C622B.2; D7B sits at CON2B, within 1 mm of the nearest place outside it to the contact: the track to it is mostly the escape out of CON2B's own pins, which no placement shortens.

      2 via(s) between CON2B.1 and D7B.4: the strike reaches an inner layer before it is clamped. D7B.4 hangs 3.36 mm off the line (limit 1 mm, default: no datasheet figure on file): the line carries the strike past it while the clamp is reached through the branch.

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

  9. DecapOrdermajorOpen

    IC14 supply pins 13, 14, 15, 16, 17 on 'P12V': the smallest capacitor C209 sits 2.0 mm away, behind C167 at 1.0 mm

    IC14 supply pins 13, 14, 15, 16, 17 on 'P12V': the smallest capacitor C209 sits 2.0 mm away, behind C167 at 1.0 mm. IC14.13: the smallest value, C209 (1 uF), is 2.0 mm from the pin and C167 (10 uF) 1.0 mm: the high-frequency part sits behind more inductance than the bulk part, which needs it least. IC14.14: the smallest value, C209 (1 uF), is 2.5 mm from the pin and C167 (10 uF) 1.1 mm: the high-frequency part sits behind more inductance than the bulk part, which needs it least. IC14.15: the smallest value, C209 (1 uF), is 3.0 mm from the pin and C167 (10 uF) 1.4 mm: the high-frequency part sits behind more inductance than the bulk part, which needs it least. IC14.16: the smallest value, C209 (1 uF), is 3.5 mm from the pin and C167 (10 uF) 1.8 mm: the high-frequency part sits behind more inductance than the bulk part, which needs it least. IC14.17: the smallest value, C209 (1 uF), is 4.0 mm from the pin and C167 (10 uF) 2.2 mm: the high-frequency part sits behind more inductance than the bulk part, which needs it least. Swap them, or bring the smallest value to the pin: it serves the fastest current and is the one the loop inductance defeats. Distances are pad centre to pin centre in the board plane. The 5 mm radius, the 10x value step and the 1 mm / 1.5x tie tolerance are Probe's starting values.

    At IC14

  10. FloatingInputmajorOpen

    IC14.22 on 'SUP1.0_RF' has no driver and no pull

    Net 'SUP1.0_RF': input(s) IC14.22 with no driver and no pull — floating input (undefined level); add a driver or a pull resistor.

    At SUP1.0_RF

  11. NetCopperSplitmajorOpen

    P12V's copper is in 3 pieces joined only through Q13: Q13.1 and R122.2 and 1 other piece(s) are connected only if the part bonds its pins inside

    P12V's copper is in 3 pieces joined only through Q13: Q13.1 and R122.2 and 1 other piece(s) are connected only if the part bonds its pins inside. Piece 1: C108.2, C126.2, C130.2, C147.1, C148.1, C149.1, C150.2, C151.2 and 61 more pin(s), on TOP, L1, L2, L3, L5, L6 and BTM, 75 drill(s), 214.85 mm2 of pour, over (-131.84, -33.38) to (-0.7, 93.44). Piece 2: Q13.1 and R122.2, on TOP, over (-19.93, 42.2) to (-16.88, 43.27). Piece 3: Q13.2, on TOP, over (-18.92, 41.38) to (-16.88, 41.99). Only Q13 has pins in more than one piece; if those pins are bonded inside the package the net is whole, and if not, the copper leaves it open. A track or a via of the net joining the pieces closes it.

    At split:P12V

  12. PartLifecyclemajorOpen

    PartLifecycle: 2 part numbers×2

    2 Obsolete · on 4 placements

    At IC13, IC55

    Each finding, with its own headline
    • IC13M25P128-VME6G on 2 placements (IC13, IC64): the distributor catalogue reports "Obsolete" for Micron Technology Inc.'s M25P128-VME6G

      M25P128-VME6G on 2 placements (IC13, IC64): the distributor catalogue reports "Obsolete" for Micron Technology Inc.'s M25P128-VME6G — a sourcing/longevity risk to confirm against the MANUFACTURER before acting. This board's BOM names no manufacturer for it, so whether that is the fitted maker's product was not checked. A distributor delisting is not the same claim as the part being unavailable; check the vendor's own lifecycle/product-change notice for the status and any named successor. Re-read the source: GET /api/odb/parts/M25P128-VME6G/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.

    • IC55NCP3170ADR2G on 2 placements (IC55, IC57): the distributor catalogue reports "Obsolete" for onsemi's NCP3170ADR2G

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

  13. PartLifecyclemajorOpen

    PartLifecycle: 5 part numbers×5

    2 Obsolete, 1 Last Time Buy, 1 Discontinued at DigiKey, 1 Not For New Designs · on 16 placements

    At IC11, IC19, IC51, IC62A, T1

    Each finding, with its own headline
    • IC11AD8402ARZ1 on IC11: the distributor catalogue reports "Last Time Buy" for Analog Devices Inc.'s AD8402ARZ1

      AD8402ARZ1 on IC11: the distributor catalogue reports "Last Time Buy" for Analog Devices Inc.'s AD8402ARZ1 — a sourcing/longevity risk to confirm against the MANUFACTURER before acting. This board's BOM names no manufacturer for it, so whether that is the fitted maker's product was not checked. A distributor delisting is not the same claim as the part being unavailable; check the vendor's own lifecycle/product-change notice for the status and any named successor. Re-read the source: GET /api/odb/parts/AD8402ARZ1/providers (which provider said it, the maker and part number it matched, its own words, and when we asked). LAST BUY 2027-07-29 — 256 day(s) remaining to place a final order. The distributor reports 63 left. No approved alternate is recorded for this position.

    • IC19INA220AIDGST on 6 placements (IC19, IC20, IC21, IC59, IC60, IC61): the distributor catalogue reports "Obsolete" for Texas Instruments's INA220AIDGST

      INA220AIDGST on 6 placements (IC19, IC20, IC21, IC59, IC60, IC61): the distributor catalogue reports "Obsolete" for Texas Instruments's INA220AIDGST — a sourcing/longevity risk to confirm against the MANUFACTURER before acting. This board's BOM names no manufacturer for it, so whether that is the fitted maker's product was not checked. A distributor delisting is not the same claim as the part being unavailable; check the vendor's own lifecycle/product-change notice for the status and any named successor. Re-read the source: GET /api/odb/parts/INA220AIDGST/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 (2025-12-30, 320 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.

    • IC51LP5951MF-3.0/NOPB on IC51: the distributor catalogue reports "Obsolete" for National Semiconductor's LP5951MF-3.0/NOPB

      LP5951MF-3.0/NOPB on IC51: the distributor catalogue reports "Obsolete" for National Semiconductor's LP5951MF-3.0/NOPB — a sourcing/longevity risk to confirm against the MANUFACTURER before acting. This board's BOM names no manufacturer for it, so whether that is the fitted maker's product was not checked. A distributor delisting is not the same claim as the part being unavailable; check the vendor's own lifecycle/product-change notice for the status and any named successor. Re-read the source: GET /api/odb/parts/LP5951MF-3.0/NOPB/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.

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

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

    • T1IRF9910Pbf on 6 placements (T1, T2, T3, T4, T5, T6): the distributor catalogue reports "Discontinued at DigiKey" for Infineon Technologies's IRF9910PBF

      IRF9910Pbf on 6 placements (T1, T2, T3, T4, T5, T6): the distributor catalogue reports "Discontinued at DigiKey" for Infineon Technologies's IRF9910PBF — a sourcing/longevity risk to confirm against the MANUFACTURER before acting. This board's BOM names no manufacturer for it, so whether that is the fitted maker's product was not checked. A distributor delisting is not the same claim as the part being unavailable; check the vendor's own lifecycle/product-change notice for the status and any named successor. Re-read the source: GET /api/odb/parts/IRF9910Pbf/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.

  14. ReferencePlaneDiscontinuitymajorOpen

    ReferencePlaneDiscontinuity: 11 boards×11

    e.g. “'RTM_LVDS.RTM_LVD4_P' crosses one gap in G's negative-plane field at 1 place, the longest 0.62 mm (fastest: RTM_LVDS.RTM_LVD4_P at 100 ps 10-90 %, ASSUMED)” · 9 different statements

    At gap:G:hole -11.52,55.63|-10.88,55.9, gap:G:hole -16.02,55.63|-15.38,55.9, gap:G:hole -20.52,55.63|-19.88,55.9, gap:G:hole -20.52,58.13|-19.88,58.4, gap:GND:hole -16.02,51.3|-15.38,51.57, gap:GND:hole -16.75,52.03|-16.48,52.67 and 5 more

    Each finding, with its own headline
    • gap:G:hole -11.52,55.63|-10.88,55.9'RTM_LVDS.RTM_LVD4_P' crosses one gap in G's negative-plane field at 1 place, the longest 0.62 mm (fastest: RTM_LVDS.RTM_LVD4_P at 100 ps 10-90 %, ASSUMED)

      Along 'RTM_LVDS.RTM_LVD4_P' on TOP, G is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.62 mm under the track at (-11.2, 55.81). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -11.52..-10.88, y 55.63..55.9. 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.

      • 'RTM_LVDS.RTM_LVD4_P' on TOP at (-11.2, 55.81), 0.62 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/24/reference-planes?group=gap%3AG%3Ahole%20-11.52%2C55.63%7C-10.88%2C55.9 serves each with its own layer_image region; all of them lie in x -12.51..-9.89, y 54.81..56.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.

    • gap:G:hole -16.02,55.63|-15.38,55.9'RTM_LVDS.RTM_LVD4_P' crosses one gap in G's negative-plane field at 1 place, the longest 0.62 mm (fastest: RTM_LVDS.RTM_LVD4_P at 100 ps 10-90 %, ASSUMED)

      Along 'RTM_LVDS.RTM_LVD4_P' on TOP, G is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.62 mm under the track at (-15.7, 55.81). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -16.02..-15.38, y 55.63..55.9. 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.

      • 'RTM_LVDS.RTM_LVD4_P' on TOP at (-15.7, 55.81), 0.62 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/24/reference-planes?group=gap%3AG%3Ahole%20-16.02%2C55.63%7C-15.38%2C55.9 serves each with its own layer_image region; all of them lie in x -17.01..-14.39, y 54.81..56.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.

    • gap:G:hole -20.52,55.63|-19.88,55.9'RTM_LVDS.RTM_LVD4_P' crosses one gap in G's negative-plane field at 1 place, the longest 0.62 mm (fastest: RTM_LVDS.RTM_LVD4_P at 100 ps 10-90 %, ASSUMED)

      Along 'RTM_LVDS.RTM_LVD4_P' on TOP, G is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.62 mm under the track at (-20.2, 55.81). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -20.52..-19.88, y 55.63..55.9. 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.

      • 'RTM_LVDS.RTM_LVD4_P' on TOP at (-20.2, 55.81), 0.62 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/24/reference-planes?group=gap%3AG%3Ahole%20-20.52%2C55.63%7C-19.88%2C55.9 serves each with its own layer_image region; all of them lie in x -21.51..-18.89, y 54.81..56.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.

    • gap:G:hole -20.52,58.13|-19.88,58.4'RTM_LVDS.RTM_LVD3_P' crosses one gap in G's negative-plane field at 1 place, the longest 0.5 mm (fastest: RTM_LVDS.RTM_LVD3_P at 100 ps 10-90 %, ASSUMED)

      Along 'RTM_LVDS.RTM_LVD3_P' on TOP, G is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.5 mm under the track at (-20.35, 58.17). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -20.52..-19.88, y 58.13..58.4. 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.

      • 'RTM_LVDS.RTM_LVD3_P' on TOP at (-20.35, 58.17), 0.5 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/24/reference-planes?group=gap%3AG%3Ahole%20-20.52%2C58.13%7C-19.88%2C58.4 serves each with its own layer_image region; all of them lie in x -21.39..-18.97, y 57.13..59.37 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.

    • gap:GND:hole -16.02,51.3|-15.38,51.57'RTM_PS#' crosses one gap in GND and P6's negative-plane field at 1 place, the longest 0.55 mm (fastest: RTM_PS# at 100 ps 10-90 %, ASSUMED)

      Along 'RTM_PS#' on L5, GND is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.55 mm under the track at (-15.57, 51.46). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 2 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 0.28 mm). What cleared it: the hole at x -16.02..-15.38, y 51.3..51.57. At 1 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. 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.

      • one stretch, cleared on 2 reference layers: 'RTM_PS#' on L5 at (-15.57, 51.46), 0.55 mm, running ALONG the bare copper for 0.28 mm, not across it; other side: no plane on P6 / 'RTM_PS#' on L5 at (-15.57, 51.46), 0.55 mm, running ALONG the bare copper for 0.28 mm, not across it; other side: no plane on GND

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AGND%3Ahole%20-16.02%2C51.3%7C-15.38%2C51.57 serves each with its own layer_image region; all of them lie in x -16.88..-14.38, y 50.46..52.57 mm (board frame, Y up).

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

    • gap:GND:hole -16.75,52.03|-16.48,52.67'RTM_PS#' crosses one gap in GND and P6's negative-plane field at 1 place, the longest 0.52 mm (fastest: RTM_PS# at 100 ps 10-90 %, ASSUMED)

      Along 'RTM_PS#' on L5, GND is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.52 mm under the track at (-16.52, 52.42). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -16.75..-16.48, y 52.03..52.67. At 1 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. 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.

      • one stretch, cleared on 2 reference layers: 'RTM_PS#' on L5 at (-16.52, 52.42), 0.52 mm; other side: no plane on P6 / 'RTM_PS#' on L5 at (-16.52, 52.42), 0.52 mm; other side: no plane on GND

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AGND%3Ahole%20-16.75%2C52.03%7C-16.48%2C52.67 serves each with its own layer_image region; all of them lie in x -17.54..-15.48, y 51.17..53.66 mm (board frame, Y up).

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

    • gap:G_2:hole -16.02,53.13|-15.38,53.4'CLK_EXT_P' crosses one gap in G_2's negative-plane field at 1 place, the longest 0.6 mm (fastest: CLK_EXT_P at 1 ns 10-90 %, suggested by its name)

      Along 'CLK_EXT_P' on BTM, G_2 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.6 mm under the track at (-15.7, 53.32). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -16.02..-15.38, y 53.13..53.4. 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.

      • 'CLK_EXT_P' on BTM at (-15.7, 53.32), 0.6 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/24/reference-planes?group=gap%3AG_2%3Ahole%20-16.02%2C53.13%7C-15.38%2C53.4 serves each with its own layer_image region; all of them lie in x -17..-14.4, y 52.32..54.32 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.

    • gap:G_2:hole -20.52,53.13|-19.88,53.4'CLK_EXT_P' crosses one gap in G_2's negative-plane field at 1 place, the longest 0.63 mm (fastest: CLK_EXT_P at 1 ns 10-90 %, suggested by its name)

      Along 'CLK_EXT_P' on BTM, G_2 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.63 mm under the track at (-20.01, 53.32). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 0.26 mm). What cleared it: the hole at x -20.52..-19.88, y 53.13..53.4. 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.

      • 'CLK_EXT_P' on BTM at (-20.01, 53.32), 0.63 mm, running ALONG the bare copper for 0.26 mm, not across it; 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/24/reference-planes?group=gap%3AG_2%3Ahole%20-20.52%2C53.13%7C-19.88%2C53.4 serves each with its own layer_image region; all of them lie in x -21.52..-18.9, y 52.27..54.32 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.

    • gap:P3:hole -16.02,93.13|-15.38,93.4'FPGA_CLK1_P' crosses one gap in P3 and P4's negative-plane field at 1 place, the longest 0.46 mm (fastest: FPGA_CLK1_P at 1 ns 10-90 %, suggested by its name)

      Along 'FPGA_CLK1_P' on L3, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.46 mm under the track at (-15.7, 93.37). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 0.46 mm). What cleared it: the hole at x -16.02..-15.38, y 93.13..93.4 and the hole at x -16.43..-12.47, y 90.3..94.26. At 1 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. 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.

      • one stretch, cleared on 2 reference layers: 'FPGA_CLK1_P' on L3 at (-15.7, 93.37), 0.46 mm, running ALONG the bare copper for 0.46 mm, not across it; other side: no plane on P4 / 'FPGA_CLK1_P' on L3 at (-15.55, 93.37), 0.36 mm; other side: no plane on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-16.02%2C93.13%7C-15.38%2C93.4 serves each with its own layer_image region; all of them lie in x -16.93..-14.37, y 92.37..94.37 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.

    • gap:P6:hole -150.9,53.55|-150.25,54.2'MISC2.PG_M2C' crosses one gap in P6's negative-plane field at 1 place, the longest 1.05 mm (fastest: MISC2.PG_M2C at 100 ps 10-90 %, ASSUMED)

      Along 'MISC2.PG_M2C' on L6, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 1.05 mm under the track at (-150.46, 53.76). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -150.9..-150.25, y 53.55..54.2. 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.

      • 'MISC2.PG_M2C' on L6 at (-150.46, 53.76), 1.05 mm; other side: no plane on G_2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-150.9%2C53.55%7C-150.25%2C54.2 serves each with its own layer_image region; all of them lie in x -151.58..-148.9, y 52.08..54.88 mm (board frame, Y up).

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

    • merged:-124.1,54.02|-123.62,53.09'TCLKA_FMC1_P' crosses between the drills at (-124.1, 54.01) and (-123.62, 53.09), whose anti-pads run together in G's negative-plane field (fastest: TCLKA_FMC1_P at 1 ns 10-90 %, suggested by its name)

      Along 'TCLKA_FMC1_P' on TOP, G's negative-plane field is cleared round the drills at (-124.1, 54.01) and (-123.62, 53.09), and the two clearances run together: the straight line from one drill to the other is bare all the way, and the track crosses it, over 0.85 mm of bare stretch at (-123.93, 53.52). Past one drill's anti-pad the return flows round on either side; here it cannot pass between the drills and detours round the whole merged clearance - the slot a row of pins or vias cuts in a plane. No crossing has a plane on the track's other side, so the whole return meets the break.

      • 'TCLKA_FMC1_P' on TOP at (-123.93, 53.52), 0.85 mm between the drills at (-124.1, 54.01) and (-123.62, 53.09) in G; 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/24/reference-planes?group=merged%3A-124.1%2C54.02%7C-123.62%2C53.09 serves each with its own layer_image region; all of them lie in x -125.47..-122.73, y 52.39..54.52 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.

  15. ReferencePlaneDiscontinuitymajorOpen

    ReferencePlaneDiscontinuity: 6 boards×6

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

    At along@P6:P1V2|P1V8, gap:P3:hole -7.18,47.89|-6.17,107.95, gap:P6:hole -66.77,55.26|-66.12,55.91, gap:P6:hole -68.82,73.21|-68.07,73.96, gap:P6:hole -93.05,69.38|-92.3,70.13, merged:-118.01,53.7|-117.96,52.6

    Each finding, with its own headline
    • along@P6:P1V2|P1V83 nets run ALONG the split between the P1V2 and P1V8 planes on P6 at 3 places, the longest 25.26 mm; the impedance rises from 52 ohm to 59 ohm there at worst, 6.3 % of each edge reflected (fastest: GBT2.GBTCLK0_M2C_P at 1 ns 10-90 %, suggested by its name)

      On P6 the P1V2 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 52 ohm; along the slot 57 ohm to 59 ohm, reflecting up to 6.3 % 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 60 ohm). At 1 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.

      • 'TCLKD_P' on L5 at (-68.2, 14.24), 19.48 mm, running ALONG the split for 18.59 mm, not across it, 52 ohm over solid plane, 59 ohm along it: 6.3 % of each edge reflected; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'TCLKD_N' on L5 at (-68.35, 14.4), 19.84 mm, running ALONG the split for 18.62 mm, not across it, 52 ohm over solid plane, 59 ohm along it: 6 % of each edge reflected; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'GBT2.GBTCLK0_M2C_P' on L6 at (-65.8, 16.98), 25.9 mm, running ALONG the split for 25.26 mm, not across it, 52 ohm over solid plane, 57 ohm along it: 4.4 % of each edge reflected; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6

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

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

    • gap:P3:hole -7.18,47.89|-6.17,107.953 nets cross one gap in P3 and P4's negative-plane field at 3 places, the longest 9.34 mm (fastest: RTM_LVDS.RTM_LVD0_N at 100 ps 10-90 %, ASSUMED)

      Along 'FPGA_CLK1_N' on L3, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 9.34 mm under the track at (-7.02, 88.5). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 6 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 8.88 mm). 3 places on 3 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -7.18..-6.17, y 47.89..107.95. At 3 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. 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.

      • one stretch, cleared on 2 reference layers: 'FPGA_CLK1_N' on L3 at (-7.02, 88.5), 9.34 mm, running ALONG the bare copper for 8.88 mm, not across it; other side: no plane on P4 / 'FPGA_CLK1_N' on L3 at (-7.02, 88.5), 9.34 mm, running ALONG the bare copper for 8.88 mm, not across it; other side: no plane on P3
      • one stretch, cleared on 2 reference layers: 'RTM_LVDS.RTM_LVD0_N' on L3 at (-7.18, 62.45), 1.51 mm, running ALONG the bare copper for 1.49 mm, not across it; other side: no plane on P4 / 'RTM_LVDS.RTM_LVD0_N' on L3 at (-7.18, 62.45), 1.51 mm, running ALONG the bare copper for 1.49 mm, not across it; other side: no plane on P3
      • one stretch, cleared on 2 reference layers: 'RTM_LVDS.RTM_LVD4_N' on L3 at (-7.05, 60.02), 1.48 mm, running ALONG the bare copper for 1.09 mm, not across it; other side: no plane on P4 / 'RTM_LVDS.RTM_LVD4_N' on L3 at (-7.05, 60.02), 1.48 mm, running ALONG the bare copper for 1.09 mm, not across it; other side: no plane on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-7.18%2C47.89%7C-6.17%2C107.95 serves each with its own layer_image region; all of them lie in x -8.18..-6.02, y 58.33..94.1 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.

    • gap:P6:hole -66.77,55.26|-66.12,55.91'VREF2.VREF_A_M2C' crosses one gap in P6's negative-plane field at 1 place, the longest 1.59 mm (fastest: VREF2.VREF_A_M2C at 100 ps 10-90 %, ASSUMED)

      Along 'VREF2.VREF_A_M2C' on L6, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 1.59 mm under the track at (-66.33, 55.47). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 0.47 mm). What cleared it: the hole at x -66.77..-66.12, y 55.26..55.91. 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.

      • 'VREF2.VREF_A_M2C' on L6 at (-66.33, 55.47), 1.59 mm, running ALONG the bare copper for 0.47 mm, not across it; other side: no plane on G_2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-66.77%2C55.26%7C-66.12%2C55.91 serves each with its own layer_image region; all of them lie in x -68.26..-65.21, y 54.35..57.08 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.

    • gap:P6:hole -68.82,73.21|-68.07,73.96'HB1.HB03_P' crosses one gap in P6's negative-plane field at 1 place, the longest 0.77 mm (fastest: HB1.HB03_P at 100 ps 10-90 %, ASSUMED)

      Along 'HB1.HB03_P' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.77 mm under the track at (-68.41, 73.62). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -68.82..-68.07, y 73.21..73.96. 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.

      • 'HB1.HB03_P' on L5 at (-68.41, 73.62), 0.77 mm; other side: no plane on GND

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-68.82%2C73.21%7C-68.07%2C73.96 serves each with its own layer_image region; all of them lie in x -69.44..-67.09, y 72.58..75.25 mm (board frame, Y up).

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

    • gap:P6:hole -93.05,69.38|-92.3,70.13'DP1.DP2_C2M_N' crosses one gap in P6's negative-plane field at 1 place, the longest 1.14 mm (fastest: DP1.DP2_C2M_N at 100 ps 10-90 %, ASSUMED)

      Along 'DP1.DP2_C2M_N' on L6, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 1.14 mm under the track at (-92.56, 69.86). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -93.05..-92.3, y 69.38..70.13. 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.

      • 'DP1.DP2_C2M_N' on L6 at (-92.56, 69.86), 1.14 mm; other side: no plane on G_2

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-93.05%2C69.38%7C-92.3%2C70.13 serves each with its own layer_image region; all of them lie in x -93.68..-90.9, y 68.75..71.49 mm (board frame, Y up).

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

    • merged:-118.01,53.7|-117.96,52.6'CLKS1.CLK2_BIDIR_P' crosses between the drills at (-118.01, 53.7) and (-117.96, 52.6), whose anti-pads run together in G's negative-plane field and G_2's negative-plane field, at 2 places (fastest: CLKS1.CLK2_BIDIR_P at 1 ns 10-90 %, suggested by its name)

      G's negative-plane field and G_2's negative-plane field are cleared round the drills at (-118.01, 53.7) and (-117.96, 52.6), and the clearances run together: the straight line from one drill to the next is bare all the way. 'CLKS1.CLK2_BIDIR_P' crosses between drills of it at 2 place(s), each listed below with its two drills. Past one drill's anti-pad the return flows round on either side; here it cannot pass between the drills and detours round the whole merged clearance - the slot a row of pins or vias cuts in a plane. One decision covers the slot: whether these tracks may cross it, or the clearances should leave copper between the drills. No crossing has a plane on the track's other side, so the whole return meets the break.

      • 'CLKS1.CLK2_BIDIR_P' on BTM at (-118.2, 53.21), 0.77 mm between the drills at (-118.01, 53.7) and (-117.96, 52.6) in G_2; other side: none: the signal layer is outermost
      • 'CLKS1.CLK2_BIDIR_P' on TOP at (-117.84, 53.26), 0.79 mm between the drills at (-118.01, 53.7) and (-117.96, 52.6) in G; 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/24/reference-planes?group=merged%3A-118.01%2C53.7%7C-117.96%2C52.6 serves each with its own layer_image region; all of them lie in x -119.36..-116.64, y 52.09..54.28 mm (board frame, Y up).

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

  16. SinglePointNetmajorOpen

    SinglePointNet: 6 findings (4 nets, 2 pins)×6

    6 checked by the review by Claude walker (cern session) — 2 different reasons

    At IC2.U18, IC2.V17, TCLKA_C_N, TCLKA_C_P, TCLKC_C_N, TCLKC_C_P

    Each finding, with its own headline
    • IC2.U18IC2.U18 (VP_0) is an IC input left unconnected

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

    • IC2.V17IC2.V17 (VN_0) is an IC input left unconnected

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

    • TCLKA_C_N'TCLKA_C_N' continues through R336 into a node that reaches no device pin

      Net 'TCLKA_C_N' continues through fitted series part(s) R336 into a node (TCLKA_C_N, TCLKA_C_P) that reaches NO device pin at all — a dangling chain of passives.

    • TCLKA_C_P'TCLKA_C_P' continues through R336 into a node that reaches no device pin

      Net 'TCLKA_C_P' continues through fitted series part(s) R336 into a node (TCLKA_C_N, TCLKA_C_P) that reaches NO device pin at all — a dangling chain of passives.

    • TCLKC_C_N'TCLKC_C_N' continues through R337 into a node that reaches no device pin

      Net 'TCLKC_C_N' continues through fitted series part(s) R337 into a node (TCLKC_C_N, TCLKC_C_P) that reaches NO device pin at all — a dangling chain of passives.

    • TCLKC_C_P'TCLKC_C_P' continues through R337 into a node that reaches no device pin

      Net 'TCLKC_C_P' continues through fitted series part(s) R337 into a node (TCLKC_C_N, TCLKC_C_P) that reaches NO device pin at all — a dangling chain of passives.

  17. CrystalLoadCapsmajorOpen

    X3 has no load capacitor on its terminal net(s) RT_X1, RT_X2

    X3 (crystal): no load capacitor found on its terminal net(s) RT_X1, RT_X2 — a passive crystal is specified for a load capacitance; verify the oscillator driver integrates the caps or add them. X3's load capacitance is not on file — and the datasheet on file for Q0M032D6-SMD does not name that exact ordering code, so it describes the family and a load capacitance read from it would be the family's range, not this part's. State it on the BOM row as parametrics.loadCapacitanceF (farads) from the part's own record, or submit parametric 'c_load' for Q0M032D6-SMD with a cite. The oscillator load of IC9 is not on file: read the crystal-oscillator table of its datasheet and submit parametric 'c_osc_load' (as the datasheet states it, with a cite).

    At X3

  18. observationOBS-217minorOpen

    TXB0104 translators IC68-IC71 have OE tied directly to VCCA, so outputs can be active while the supplies ramp

    The TXB0104 translators IC68-IC71 have OE (pin 8) tied directly to their own VCCA rail, so their outputs can be active while the supplies ramp, against TI's power-supply recommendation.

    Where it is

    IC68, IC69, IC70 and IC71 (TXB0104PWR) connect FPGA I/O to the RTM connector J1/J2 and to the CP2102 UART.

    PartOE (pin 8) tied to its VCCA rail
    IC68PVADJ1
    IC69PVADJ1
    IC70PVADJ2
    IC71P1V5

    What the datasheet asks

    OE should be tied to GND through a pulldown and not enabled until VCCA and VCCB are fully ramped and stable (TXB0104 datasheet, p.25).

    Why it matters

    As wired, the translators are enabled as soon as VCCA rises, with no control over the ramp window. The VCC-isolation feature keeps outputs high-Z while either supply is fully at 0 V, which limits but does not remove the exposure.

  19. observationOBS-218minorOpen

    ESD protector IC7 on the AMC JTAG lines sits at the SCANSTA111, 110-170 mm from the ports it protects

    The ESD protector IC7 (BZA462A) on the AMC JTAG lines sits 5 mm from the SCANSTA111 IC6 it protects, about 170 mm from the P1 contacts and 110 mm from J6, so an ESD event travels the full trace run across the board before it is clamped.

    Where it is

    IC7 clamps AJTAG.TCK/TMS/TDI/TRST#, which enter at the AMC edge connector P1 (contacts 165-169) and at the JTAG header J6.

    Part / portDistance from IC7
    IC6 SCANSTA1115 mm
    AMC edge connector P1 contactsabout 170 mm
    JTAG header J6about 110 mm

    Source: placement record. IC6 is no farther from the ports than the protector.

    Why it matters

    An ESD event on the connector travels the full trace run across the board before it is clamped. The other protectors on this board (IC4 IPMB, IC5 GA, D7A/D7B USB) sit within about 5-12 mm of their connector.

  20. observationOBS-225minorOpen

    FPGA die-temperature sensor IC18 (MAX6642) has no 2200 pF filter capacitor on DXP

    The FPGA die-temperature sensor IC18 (MAX6642) has no 2200 pF filter capacitor on DXP (net FTMP.DXP), which its datasheet asks for, so noise pickup can bias the FPGA temperature reading.

    Where it is

    • IC18 (MAX6642ATT90) reads the Artix-7 on-die thermal diode through FTMP.DXP (IC2 W18).
    • The diode return FTMP.DXN (W17) is grounded through R135 0 Ohm.
    • None is fitted or drawn: the DXP net carries only the two pins.

    What the datasheet asks

    "Place a 2200pF capacitor between DXP and GND for noise filtering" (MAX6642 datasheet, p.5).

    Why it matters

    The line runs about 35 mm across a board carrying switching regulators and multi-gigabit links, so noise pickup can bias the remote reading. The datasheet layout section notes that noise typically makes the conversion read higher than the actual temperature.

  21. observationOBS-226minorOpen

    FPGA UART receive line from CP2102 IC62B bypasses the level translator: 3.3 V TXD drives a PVADJ1 bank ball directly

    The CP2102 IC62B-to-FPGA UART line bypasses the level translator: CP2102 TXD at 3.3 V drives FPGA IC2 ball AB11 in the PVADJ1 bank through only R275B 2k2, so it is clamped by the FPGA input diode whenever PVADJ1 is set below about 3.1 V.

    Where it is

    The second USB-UART (IC62B CP2102, connector CON2B) talks to the FPGA. One direction is level-shifted, the other is not.

    ``mermaid flowchart LR CP["IC62B CP2102<br/>3.3 V VDD"] -- "TXD pin 26" --> R1["R275B 2k2"] R1 -- "TXD_USBB, no translator" --> AB11["IC2 ball AB11<br/>bank 34, VCCO = PVADJ1"] Y11["IC2 ball Y11<br/>VADJ1_RXD"] --> TXB["IC69 TXB0104<br/>VCCA = PVADJ1"] TXB -- "RXD_USBB" --> R2["R276B 2k2"] R2 -- "RXD pin 25" --> CP ``

    The numbers

    QuantityValueSource
    CP2102 TXD high leveldriven at the CP2102 3.3 V VDD (3.0-3.6 V)CP2102 datasheet, p.11
    Bank of AB11bank 34, VCCO = PVADJ1 (the adjustable FMC VADJ rail)UG475 Figure 3-94, p.126
    HR I/O input limitVCCO + 0.20 VDS181, p.2
    Clamp-diode current limit10 mADS181, p.2
    Condition for the violationPVADJ1 below about 3.1 Vderived

    Why it matters

    Whenever PVADJ1 is set below about 3.1 V, the CP2102 high level exceeds the DS181 input limit and is clamped through the FPGA input diode. The 2k2 keeps the clamp current well below the 10 mA limit, and the same current back-feeds into PVADJ1.

  22. observationOBS-230minorOpen

    ADN4604 UPDATE pin is driven by both the MMC GPIO and the FPGA translator through two fitted 0 Ohm links

    The ADN4604 UPDATE pin (IC8 pin 25, net UPD_R) is driven by both the MMC GPIO and an always-enabled IC41 translator output through two fitted 0 Ohm links, R139 and R140, so two push-pull drivers can fight.

    Where it is

    ``mermaid flowchart LR MMC["IC1 LPC1764 pin 40<br/>UPDATEN"] -- "R139 0 Ohm, fitted" --> UPD["IC8 ADN4604 pin 25<br/>UPDATE, net UPD_R"] FPGA["FPGA ball U24"] --> IC41["IC41 SN74AVC8T245<br/>B7 pin 15, always driven"] IC41 -- "CLK_UPDATEN, R140 0 Ohm, fitted" --> UPD ``

    FactSource
    R139 and R140 are both fitted (value 0, not DNP)BOM
    IC41 DIR (pin 2) = VCCA, OE (pin 22) = GNDnetlist: IC41
    OE low, DIR high: A data to B bus, so B outputs are always drivenSN74AVC8T245 datasheet, p.16
    UPDATE is the second-rank write enable, active low, normally pulled up to DVCCADN4604 datasheet, p.8

    Why it matters

    The IC41 output is always driven. The moment the MMC configures pin 40 as an output at the opposite level, or the FPGA drives U24 while the MMC holds UPDATEN, two push-pull drivers fight through 0 Ohm. It looks like an either/or population option (one of R139/R140 meant DNP), or it relies on firmware keeping one side an input, and nothing says which.

  23. observationOBS-231minorOpen

    SCANSTA111 IC6: the MMC "SCN.RSTN" line lands on TRIST_B, an output, not on the TRST_B reset input

    The MMC net SCN.RSTN lands on SCANSTA111 IC6 pin 7, which is TRIST_B, a 12 mA output, not the TRST_B reset input (pin 2); the MMC cannot reset the scan bridge as the name implies, and may fight its output.

    Where it is

    ``mermaid flowchart LR MMC["IC1 LPC1764<br/>pin 66, P2[7] GPIO"] -- "SCN.RSTN" --> P7["IC6 pin 7<br/>TRIST_B output"] AMC["AMC P1.167<br/>AJTAG.TRST#, R60 10k to P3V3"] -- "R226 100 Ohm, TRST#_R" --> P2["IC6 pin 2<br/>TRST_B reset input"] ``

    IC6 pin (TSSOP-48)FunctionSource
    2TRST_B, active-low reset input with 25 kOhm pull-upSCANSTA111 datasheet, p.2 (connection diagram), p.4
    7TRIST_B, backplane tri-state notification output (12 mA), high while TDO_B is tri-statedSCANSTA111 datasheet, p.2, p.4

    Nothing else drives SCN.RSTN except the MMC GPIO (IC67 pin 2, the DNP alternate, is also on the net). TRST_B is fed only from the AMC backplane TRST# line.

    Why it matters

    • If firmware drives SCN.RSTN as an output, it fights the SCANSTA111's TRIST_B driver.
    • As an input it would read the TDO_B tri-state status.
    • Either the net is misnamed (a status input to the MMC) or the reset was meant to go to TRST_B.
  24. observationOBS-232minorOpen

    P1V2 and P1V8 converters (IC55, IC57 NCP3170) have no pull-down on EN and turn on by themselves while the MMC is in reset

    The P1V2 and P1V8 bucks IC55 and IC57 (NCP3170) have no pull-down on EN (EN_P1V2_R, EN_P1V8_R), so they turn on by themselves from the MMC reset pull-ups whenever P12V is present, outside the MMC power sequence.

    Where it is

    ``mermaid flowchart LR MMC["IC1 LPC1764<br/>pins 9 and 8, reset pull-up 2.3-2.6 V"] -- "PM.EN_P1V2" --> R103["R103 10k"] R103 -- "EN_P1V2_R, no pull-down" --> IC55["IC55 NCP3170 EN pin 6<br/>P1V2"] MMC -- "PM.EN_P1V8" --> R61["R61 10k"] R61 -- "EN_P1V8_R, no pull-down" --> IC57["IC57 NCP3170 EN pin 6<br/>P1V8"] ``

    The numbers

    QuantityValueSource
    LPC1764 P0[23] (pin 9) and P0[24] (pin 8) from reset until configuredinputs, pulled up to 2.3-2.6 VLPC1764 datasheet, p.20 note [2]; pin rows p.13
    NCP3170 enable threshold1.41 V typicalNCP3170 datasheet, p.4
    NCP3170 ENmust not be left openNCP3170 datasheet, p.2

    Every other payload converter has a fitted pull-down

    Converter / enablePull-down
    IC43 PM.EN_P3V3R69 4k7
    IC43 PM.1V5_VTT_ENR49 4k7
    IC14 PM.EN_P1V0R114 10k
    IC10/IC12 PM.EN_FMCx_*R71/R78/R85/R92 10k to GND

    Why it matters

    Whenever P12V is present and the MMC is resetting, booting or being reprogrammed, P1V2 and P1V8 come up on their own, while every other payload converter (P1V0, P1V5/VTT, P3V3, the FMC rails) is held off by its pull-down. The rails therefore come up outside the MMC's power sequence.

  25. observationOBS-233minorOpen

    Silkscreen carries designators only for ICs: passives, diodes, LEDs and transistors have no refdes on the board

    The AFC silkscreen prints reference designators only for ICs; passives, diodes, LEDs and transistors carry an outline but no refdes, so rework and bring-up depend entirely on an assembly drawing.

    What was seen

    Area rendered from the silk layersDesignators printed
    Top, x -172..-156 / y 76..90, around IC1/IC3/IC9/IC27/IC58 (22 components in view)IC58 only
    Top, x -146..-118 / y 58..76, around IC6/IC7/LED3-LED5 (27 components in view)IC6, IC73 only
    Bottom, around IC10/IC40/J4/D5/D6IC10, IC40 only

    Functional labels are printed: "3.3V RST SUP", "DONE", "JTAG SWITCH", "HPC1 VADJ", "12V", "GND".

    Parts with an outline but no designator

    • Diodes D1, D3, D4, D5, D6; LEDs LED16, LED3, LED4.
    • Transistor Q9.
    • The EEPROM/RTC area parts and all resistors and capacitors in view.

    Where IC designators are printed they are about 1.2 mm high, which is fine.

  26. observationOBS-234minorOpen

    No test points on power rails, resets or configuration signals; the only signal test points serve a UART and the unfitted ATxmega

    No test points on the AFC power rails, resets, configuration signals or I2C/JTAG buses; the only signal test points serve one UART and the unfitted ATxmega IC67.

    What the 26 test points are on

    • TPD2...TPD38: 21 differential-probe points, all on GND.
    • TP4 (TXD_USBB) and TP13 (VADJ1_RXD): the FPGA USB-UART.
    • TP1, TP2, TP10: nets whose only other member is IC67, the not-fitted ATxmega alternate (pins 86/85/38).

    What has none

    • Rails: P1V0, P1V2, P1V5, P1V8, P3V3, PVADJ1, PVADJ2, VTT, P3V3MP, P12V.
    • Resets and FPGA configuration: RESETN, FPGA_RESETN, FSPI.PROGRAM_B, FSPI.DONE, FSPI.INIT_B.
    • The I2C and JTAG buses.

    Bring-up and production test would have to probe capacitor or component pads, many 0402/0201 and several on the bottom under the FPGA.

  27. observationOBS-235minorOpen

    SN74AVC8T245 translators IC40 and IC41 have OE tied to GND, so they drive their outputs during supply ramp

    The SN74AVC8T245 translators IC40 and IC41 have OE (pin 22, active low) tied straight to GND, so they drive their B outputs as soon as their supplies rise, against TI's power-supply recommendation.

    Where it is

    PartOE (pin 22)DIR (pin 2) = VCCAB outputs drive
    IC40GNDP1V5the SN65MLVD040 M-LVDS driver/receiver enables DE1-DE8
    IC41GNDPVADJ2the AD5662 clock-DAC SYNC/SCLK/DIN lines, the Si570 OE, the ADN4604 UPDATE (through R140 0 Ohm)

    Both are permanently enabled A to B from the moment their supplies rise.

    What the datasheet asks

    • OE must be pulled up to VCCA and held until VCCA and VCCB are fully ramped (SN74AVC8T245 datasheet, p.18).
    • OE is pin 22, active low, referenced to VCCA; pull OE high for 3-state (p.3).

    Why it matters

    The translator inputs are only defined once the FPGA is configured (PUDC_B pull-ups during configuration). Partial-power-down (Ioff) protects the fully-unpowered case only. This is the same pattern as the TXB0104 parts in OBS-217.

  28. observationOBS-238minorOpen

    VCCBRAM filter inductor L10 is rated 1.4 A but the design budgets 1.8 A for VCCBRAM

    The VCCBRAM filter inductor L10 is rated 1.4 A in its BOM description, but the designer's rail table budgets 1.8 A for VCCBRAM; if that budget is real, L10 runs above its rating and its DC drop exceeds the rail's tolerance window.

    The numbers

    QuantityValueSource
    VCCBRAM feedonly L10, from P1V0netlist: L10, VCCBRAM
    L10 rating"2.2uH, 1.4A, 92mR"BOM description, L10
    VCCBRAM budget1.8 A ("VCCBRAM 1V 1.8A seq0")designer rail table, schematic sheets 10 and 16
    DC drop in L10 at 1.8 A1.8 A x 92 mOhm = about 0.17 V on a 1.0 V railderived

    Why it matters

    Above its rating L10 saturates and heats. Its DC resistance alone would drop more than the whole +/-50 mV window a 1.0 V FPGA supply is normally held to.

    The BOM row is inconsistent

    • The L10 value ELLVGG1R0N is a 1.0 uH part number.
    • Its own description says 2.2 uH, and its footprint is L_ELLVGG2R2N.
    • The same ELLVGG part and description appear on L11, L12 and L13.
  29. observationOBS-239minorOpen

    FPGA PUDC_B is strapped to GND through 10 kOhm; UG475 requires 1 kOhm or less

    PUDC_B on the FPGA IC2 (ball W26) is strapped to GND only through R180 = 10 kOhm, where UG475 requires 1 kOhm or less, so the pin that sets the configuration-time I/O pull-ups is only weakly defined.

    The requirement

    QuantityValueSource
    Strap on net PUDCR180 = 10 kOhm to GND, the only strap on the pinnetlist / BOM: R180, IC2 ball W26
    Required straptied to VCCO_14 or GND directly or through 1 kOhm or less; must not float before or during configurationUG475 Table 1-12, p.22

    Why it matters

    PUDC_B is the multi-function pin that enables the SelectIO pull-ups during configuration. With 10 kOhm the pin is weakly defined, so input leakage or noise can move it during power-up and configuration. That changes whether every I/O is pulled up during configuration, which this board relies on. Two groups of lines are held inactive only by those pull-ups:

    • the IC40/IC41 translator inputs;
    • the DAC SYNC lines behind them.

    Note also that the PUDC_B buffer sits in bank 14, which here runs from PVADJ2 (OBS-227).

  30. observationOBS-242minorOpen

    GTP reference clock MGTREFCLK0_116 has two fitted drivers: the RTM clock (J2) and ADN4604 output 9

    The GTP quad-116 refclk input MGTREFCLK0_116 (net MGT116_CLK0, FPGA H16/G16) has two fitted drivers, the RTM clock from J2 and ADN4604 IC8 output 9, so two clock drivers can fight on one differential pair.

    Where it is

    ``mermaid flowchart LR J2["RTM connector J2<br/>FPGA_CLK1, contact A5"] -- "C797 / C799 100 nF, fitted" --> REF["FPGA H16 / G16<br/>MGTREFCLK0_116"] IC8["IC8 ADN4604<br/>OP9 / ON9, pins 80 / 81"] -- "C838 / C839 100 nF, fitted" --> REF FMC["FMC1 GBTCLK option"] -. "C188 / C189, DNP" .-> REF ``

    SourceCoupling capacitors (P / N leg)BOM state
    FPGA_CLK1 from RTM connector J2C797 / C799fitted
    ADN4604 crosspoint output OP9/ON9C838 / C839fitted
    FMC1 GBTCLK optionC188 / C189DNP

    Why it matters

    • If the RTM drives FPGA_CLK1 while crosspoint output 9 is enabled, two clock drivers fight on one differential pair.
    • Even with one side idle, the idle side is an unterminated stub on a GHz-class reference clock.
    • The FMC1 option on the same input is correctly DNP, which suggests the RTM/crosspoint pair was also meant to be a population choice.
  31. observationOBS-243minorOpen

    Net names MGT216_CLK0 and MGT216_CLK1 are swapped against the FPGA balls (REFCLK1 and REFCLK0 of quad 216)

    The quad-216 reference-clock nets MGT216_CLK0 and MGT216_CLK1 carry the opposite index to the FPGA IC2 balls they land on, so FPGA constraints written from the net names will pick the wrong IBUFDS_GTE2 site.

    Where it is

    NetFPGA ballsBall name (AMD package file xc7a200t/ffg1156)
    MGT216_CLK0_P/NH20 / G20MGTREFCLK1P/N_216
    MGT216_CLK1_P/NH18 / G18MGTREFCLK0P/N_216

    All other MGT net names (RX/TX lane and quad numbers, MGT113/116/213 CLK indices) agree with their balls. Only these two disagree.

    Why it matters

    • Electrically nothing is lost today: both 216 refclk pairs are fed from the same ADN4604 output (MGT.PCIE_CLK1, the PCIe clock, IC8 pins 77/78) through C457/C459 and C461/C463.
    • But anyone writing the FPGA constraints from the net names will instantiate the wrong IBUFDS_GTE2 site.
    • The schematic sheet 17 designer note already records confusion about the MGT assignments.
  32. observationOBS-247minorOpen

    Auxiliary 3.3 V LDO IC74 (LD1117) has about 4.5 uF on its output; the datasheet needs 10 uF minimum for stability

    IC74 (LD1117DT33), the auxiliary 3.3 V LDO for the MMC supply P3V3MP_AUX, sees about 4.5 uF on its output where the datasheet needs 10 uF minimum for stability, so the MMC supply can oscillate or ring when the board runs from the auxiliary input.

    Where it is

    IC74 makes P3V3MP_AUX from the J4 12 V input and feeds P3V3MP through PTC fuse F3.

    ``mermaid flowchart LR J4["J4<br/>12 V aux input"] --> IC74["IC74 LD1117DT33<br/>OUT pin 3"] IC74 -- "P3V3MP_AUX" --> C817["C817 1 uF"] IC74 -- "P3V3MP_AUX" --> F3["F3 PTC fuse"] F3 -- "P3V3MP" --> DEC["26 capacitors<br/>about 3.5 uF total"] ``

    The numbers

    QuantityValueSource
    Local output capacitorC817 = 1 uFnetlist: IC74 pin 3, net P3V3MP_AUX
    Decoupling on P3V3MP behind F3about 3.5 uF (26 capacitors, mostly 100 nF)netlist / BOM: net P3V3MP
    Total output capacitance1 + 3.5 = about 4.5 uF nominal, before DC-bias derating (dielectrics not on the BOM)derived
    Required output capacitance10 uF minimum for stabilityLD1117 datasheet, p.1
    Characterisation conditionCO = 10 uFLD1117 datasheet, p.9-12
    LDO dissipation12 V to 3.3 V linear: 0.87 W per 100 mAderived

    Why it matters

    When the board is run from the auxiliary input, the MMC supply can oscillate or ring on load steps. The LDO also drops 12 V to 3.3 V linearly, so its dissipation is worth checking at the same time.

  33. observationOBS-476minorOpen

    Clock crosspoint IC8 (ADN4604): five inputs are wired P/N reversed in copper (TCLKA-D and the Si570 clock); the part can correct this per input with its SIGN bits, so it is correct only if the MMC firmware sets them

    On the AFC, five inputs of the clock crosspoint IC8 (ADN4604) are wired P/N reversed in copper. The part can undo this per input in its RX control registers, so the reversal is correctable in configuration: the forwarded clocks are right only if the MMC firmware sets those five SIGN bits.

    Where it is

    IC8 inputs IPx (true) and INx (complement) against the nets on them, from the ODB netlist and the ADN4604 pin table (p.8-9):

    IC8 inputPin IPx / INxNet on IPxNet on INxSource
    IP4 / IN414 / 15TCLKB_CIN_NTCLKB_CIN_PAMC P1 via AC coupling
    IP5 / IN517 / 18TCLKA_CIN_NTCLKA_CIN_PAMC P1 via AC coupling
    IP6 / IN620 / 21TCLKC_CIN_NTCLKC_CIN_PAMC P1 via AC coupling
    IP7 / IN723 / 24TCLKD_CIN_NTCLKD_CIN_PAMC P1 via AC coupling
    IP15 / IN1573 / 74SI57X_CLK_C_NSI57X_CLK_C_POSC4 via AC coupling

    The other eleven inputs have _P on IPx. The outputs back to the backplane are wired straight: for example OP2 pin 33 = TCLKA_COUT_P and ON2 pin 34 = TCLKA_COUT_N (pin table p.8).

    ``mermaid flowchart LR A["AMC P1 TCLKA_P"] -- "AC coupled" --> B["IC8 IN5 (complement)"] C["AMC P1 TCLKA_N"] -- "AC coupled" --> D["IC8 IP5 (true)"] B --> E["IC8 core, SIGN5 = 0 by default"] D --> E E --> F["OP/ON outputs, wired straight"] ``

    What the part allows

    QuantityValueSource
    Per-input polarity controlSIGN[15:0], "available independently for each of the 16 input channels"ADN4604 datasheet p.16
    Register addressesRX control registers 0x12 and 0x13ADN4604 datasheet p.16
    Reset stateSIGN = 0, noninverting (default)ADN4604 datasheet p.16, Table 8
    Datasheet cautionusing it for inversions "requires additional attention when switching connectivity"ADN4604 datasheet p.16

    The two refuting evidence rows on the earlier record (SIGN bit, p.16) are right: the swap is recoverable in configuration. They do not make the finding go away, because the default is noninverting. Until firmware writes SIGN4-7 and SIGN15 to 1, every path from these five inputs is inverted.

    Why it matters

    • For a clock used only by frequency, an inversion is usually harmless.
    • It matters for any phase-sensitive use: a backplane clock returned to the crate inverted, a clock compared in phase with another input that is not inverted, and any use of these paths for data.
    • Nothing on the board or in the schematic notes says the reversal is intended, so the only record of it would be the MMC firmware.

    Severity

    Kept minor: the fix is a register setting, not copper. If a person confirms that the MMC firmware sets these five SIGN bits, this can be closed as benign. If the firmware does not, it becomes a firmware defect.

  34. observationOBS-535minorOpen

    AFC RGB status LED LD1: green and blue get almost no current from 3.3 V through the same 330 Ω as red

    LD1 (Optek OVSRRGBCC3, common anode on P3V3) drives all three colours through identical 330 Ω resistors. Green and blue have a typical Vf of 3.3 V, equal to the rail, so they barely light while red runs at about 4 mA.

    ColourVf typ (min-max) at 20 mAResistorCurrent from 3.3 V (BSS138 on)Source
    Red2.0 V (1.8-2.4)R277 330 Ωabout 3.9 mAdatasheet p.3; netlist
    Green3.3 V (3.0-3.6)R278 330 Ω0 to 0.9 mA (Vf at low current, a few hundred µA typical)same
    Blue3.3 V (3.0-3.6)R279 330 Ω0 to 0.9 mAsame

    Why it matters

    At minimum the green and blue states are much dimmer than red. A part at the high end of the Vf spread (3.6 V) cannot light at all from 3.3 V, so a status colour can read as 'off'. No weighting intent is recorded on the schematic.

    Fix: feed green/blue from a higher rail (5 V or 12 V with resized resistors), or use a lower-Vf part.

  35. observationOBS-666minorOpen

    CP2102 USB lines carry 33 ohm series resistors on top of the CP2102's own 38 ohm driver impedance

    Both USB-UART bridges (IC62A, IC62B, CP2102) drive D+ / D- through 33 ohm series resistors (R284A/B, R285A/B), although the CP2102 datasheet already gives a 38 ohm driver output impedance: the source impedance becomes about 71 ohm, above the 28-44 ohm full-speed driver range of USB 2.0.

    Numbers

    QuantityValueSource
    CP2102 driver output impedance Z_DRV38 ohm typ, high and lowCP2102 datasheet, Table 7, p.9
    Series resistor33 ohm (R284A, R284B, R285A, R285B)BOM
    Total source impedanceabout 71 ohmderived
    Full-speed rise time4-20 nsCP2102 datasheet, Table 7, p.9

    Why it matters

    The lines are short (about 55 ps one way), so reflections do not matter at full speed. The extra 33 ohm slows the edges and lowers the eye margin, and it moves the driver outside the USB 2.0 full-speed output-resistance range. Silicon Labs' CP2102 needs no external series resistors. CERN may have added them on purpose, for example to limit ESD current through the D7A/D7B clamps. If not, 0 ohm would restore the datasheet configuration.

  36. observationOBS-677minorOpen

    BC847B went end-of-life (Not For New Designs)

    Vendor (DigiKey) lifecycle for BC847B (Nexperia USA Inc.'s listing) changed from "Active" to "Not For New Designs" since this board was reviewed. Placed as Q12, Q5, Q6. A sourcing/longevity risk; consider a replacement before production.

  37. concernCON-001minorOpen

    [eol:BC847B:Not For New Designs] BC847B lifecycle changed from "Active" to "Not For New Designs" since this board was reviewed: OHWR0021 R1 AFC. A sourcing and longevity risk. Should this be replaced before the next build?

  38. DecapViaFanoutminorOpen

    DecapViaFanout: 5 components×5

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

    At C313, C587, C654, C678, C768

    Each finding, with its own headline
    • C313C313 on 'P3V3MP': its rail pad reaches its via over 2.58 mm of track, adding about 0.54 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)

      C313 on 'P3V3MP': its rail pad reaches its via over 2.58 mm of track, adding about 0.54 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). C313.1 (rail) runs 2.58 mm along its copper to its nearest via, 1.58 mm past the 1 mm beside the pad: 0.54 nH; C313.2 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 0.70 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.54 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.08 nH (pad 0.05 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 1.37 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

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

      C587 on 'VCCBRAM': its rail pad reaches its via over 2.61 mm of track, adding about 1.02 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads (a 100 uF bulk capacitor: its inductance matters only far above the band it serves). C587.1 (rail) runs 2.61 mm along its copper to its nearest via, 1.61 mm past the 1 mm beside the pad: 1.02 nH; C587.2 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 3.00 mm apart (the pad pitch), 0.2 l ln(D/R) nH with R 0.127 mm (the track's width is not read): 1.02 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.25 nH (pad 0.20 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 0.42 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

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

      C654 on 'PVADJ2': its rail pad reaches its via over 2.10 mm of track, adding about 0.56 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads (within a quarter of the starting value). C654.2 (rail) runs 2.10 mm along its copper to its nearest via, 1.10 mm past the 1 mm beside the pad: 0.56 nH; C654.1 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 1.60 mm apart (the pad pitch), 0.2 l ln(D/R) nH with R 0.127 mm (the track's width is not read): 0.56 nH in all. Put the vias at the pads (or in them), one per pad at least, the rail's and the ground's close together; the capacitor's own inductance as mounted is 1.43 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.37 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

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

      C678 on 'PVADJ1': its rail pad reaches its via over 1.90 mm of track, adding about 0.57 nH to its loop, past Probe's 0.5 nH starting value; put the vias at the pads (a 100 uF bulk capacitor: its inductance matters only far above the band it serves). C678.1 (rail) runs 1.90 mm along its copper to its nearest via, 0.90 mm past the 1 mm beside the pad: 0.57 nH; C678.2 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 3.00 mm apart (the pad pitch), 0.2 l ln(D/R) nH with R 0.127 mm (the track's width is not read): 0.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.38 nH (pad 0.20 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 0.63 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

    • C768C768 on 'PVADJ1': its rail pad reaches its via over 2.80 mm of track, adding about 0.61 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)

      C768 on 'PVADJ1': its rail pad reaches its via over 2.80 mm of track, adding about 0.61 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). C768.1 (rail) runs 2.80 mm along its copper to its nearest via, 1.80 mm past the 1 mm beside the pad: 0.61 nH; C768.2 (ground) not measured: the pad sits in a pour of its net on its own layer, which has no track length to measure. Each run past the pad as one conductor of a pair 0.70 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.61 nH in all. Put the vias at the pads (or in them), one per pad at least, the rail's and the ground's close together; the capacitor's own inductance as mounted is 0.64 nH (pad 0.05 nH + no via of the first net within 1 mm of its pad: the study's 0.6 nH per mm of 0.63 mm depth, ASSUMED). 0.5 nH is Probe's starting value, about the whole mounted inductance of a well-mounted 0402.

  39. ConnectorDomainMixedminorOpen

    P1 takes 2 different supplies off the board on one connector: P12V (12.0 V), P3V3MP (3.3 V)

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

    At P1

  40. ReferencePlaneDiscontinuityminorOpen

    ReferencePlaneDiscontinuity: 121 boards×121

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

    At gap:G_2:hole -3.79,-32.36|-0.15,32.16, gap:P3:hole -111.48,44.07|-77.99,44.53, gap:P3:hole -119,61.55|-118.5,81.25, gap:P3:hole -119.58,81.38|-119.13,91.26, gap:P3:hole -119.58,90.8|-119.13,97.69, gap:P3:hole -127.61,-23.62|-118.17,-14.18 and 115 more

    Each finding, with its own headline — 100 of 121 shown
    • gap:G_2:hole -3.79,-32.36|-0.15,32.16'PORT2.RX2_P' crosses one gap in G_2's negative-plane field at 1 place, the longest 0.82 mm (fastest: PORT2.RX2_P at 3 ns 10-90 %, suggested by its name)

      Along 'PORT2.RX2_P' on BTM, G_2 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.82 mm under the track at (-3.37, -8.25). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -3.79..-0.15, y -32.36..32.16. 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.

      • 'PORT2.RX2_P' on BTM at (-3.37, -8.25), 0.82 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/24/reference-planes?group=gap%3AG_2%3Ahole%20-3.79%2C-32.36%7C-0.15%2C32.16 serves each with its own layer_image region; all of them lie in x -4.79..-2.2, y -9.25..-7.21 mm (board frame, Y up).

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

    • gap:P3:hole -111.48,44.07|-77.99,44.534 nets cross one gap in P3 and P4's negative-plane field at 4 places, the longest 0.65 mm (fastest: RTM_LVDS.RTM_LVD4_N at 100 ps 10-90 %, ASSUMED)

      Along 'MGT.LINK23_CLK_P' on L3, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.65 mm under the track at (-105.09, 44.3). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 4 places on 4 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -108.89..-89.66, y 27.76..46.99 and the hole at x -111.48..-77.99, y 44.07..44.53. At 1 place(s) the track's plane is cleared on both sides of it, the same stretch on each reference layer: it has no plane on either side there, counted once. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • one stretch, cleared on 2 reference layers: 'MGT.LINK23_CLK_N' on L3 at (-105.41, 44.3), 0.65 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3 / 'MGT.LINK23_CLK_N' on L3 at (-105.8, 43.9), 0.51 mm; other side: (negative-layer field) on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4
      • 'MGT.LINK23_CLK_P' on L3 at (-105.09, 44.3), 0.65 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_LVDS.RTM_LVD4_N' on L3 at (-78.89, 44.43), 0.49 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_LVDS.RTM_LVD4_P' on L3 at (-78.62, 44.42), 0.47 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-111.48%2C44.07%7C-77.99%2C44.53 serves each with its own layer_image region; all of them lie in x -106.98..-77.56, y 42.72..45.53 mm (board frame, Y up).

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

    • gap:P3:hole -119,61.55|-118.5,81.252 nets cross one gap in P3's negative-plane field at 2 places, the longest 0.51 mm (fastest: FJTAG.TCK at 2 ns 10-90 %, suggested by its name)

      Along 'FJTAG.TMS' on L2, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.51 mm under the track at (-118.75, 76.69). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 2 places on 2 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -119..-118.5, y 61.55..81.25. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'FJTAG.TCK' on L2 at (-118.75, 77.03), 0.51 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'FJTAG.TMS' on L2 at (-118.75, 76.69), 0.51 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-119%2C61.55%7C-118.5%2C81.25 serves each with its own layer_image region; all of them lie in x -120..-117.5, y 75.69..78.03 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.

    • gap:P3:hole -119.58,81.38|-119.13,91.26'RTM_PS#' crosses one gap in P3's negative-plane field at 1 place, the longest 0.46 mm (fastest: RTM_PS# at 100 ps 10-90 %, ASSUMED)

      Along 'RTM_PS#' on L3, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.46 mm under the track at (-119.36, 89.63). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -119.58..-119.13, y 81.38..91.26. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RTM_PS#' on L3 at (-119.36, 89.63), 0.46 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-119.58%2C81.38%7C-119.13%2C91.26 serves each with its own layer_image region; all of them lie in x -120.58..-118.13, y 88.63..90.63 mm (board frame, Y up).

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

    • gap:P3:hole -119.58,90.8|-119.13,97.694 nets cross one gap in P3's negative-plane field at 4 places, the longest 0.46 mm (fastest: RTM_TCK at 2 ns 10-90 %, suggested by its name)

      Along 'RTM_TCK' on L3, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.46 mm under the track at (-119.36, 93.11). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 4 places on 4 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -119.58..-119.13, y 90.8..97.69. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RTM_TCK' on L3 at (-119.36, 93.11), 0.46 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_TDI' on L3 at (-119.36, 90.93), 0.46 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_TDO' on L3 at (-119.36, 93.4), 0.46 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_TMS' on L3 at (-119.36, 92.18), 0.46 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-119.58%2C90.8%7C-119.13%2C97.69 serves each with its own layer_image region; all of them lie in x -120.58..-118.13, y 89.93..94.4 mm (board frame, Y up).

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

    • gap:P3:hole -127.61,-23.62|-118.17,-14.18'CLK_DIRB' crosses one gap in P3's negative-plane field at 1 place, the longest 0.65 mm (fastest: CLK_DIRB at 1 ns 10-90 %, suggested by its name)

      Along 'CLK_DIRB' on L2, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.65 mm under the track at (-123.55, -19.56). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -127.61..-118.17, y -23.62..-14.18. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'CLK_DIRB' on L2 at (-123.55, -19.56), 0.65 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-127.61%2C-23.62%7C-118.17%2C-14.18 serves each with its own layer_image region; all of them lie in x -124.55..-122.55, y -20.88..-18.23 mm (board frame, Y up).

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

    • gap:P3:hole -36.63,36.6|-36.12,4918 nets cross one gap in P3's negative-plane field at 18 places, the longest 0.72 mm (fastest: RTM_LVDS.RTM_LVD0_N at 100 ps 10-90 %, ASSUMED)

      Along 'RTM_LVDS.RTM_LVD0_P' on L3, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.72 mm under the track at (-36.43, 37.9). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 18 places on 18 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -36.63..-36.12, y 36.6..49. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RTM_LVDS.RTM_LVD0_N' on L3 at (-36.5, 37.51), 0.72 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_LVDS.RTM_LVD0_P' on L3 at (-36.43, 37.9), 0.72 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'MLVDS_F.IO_RX_P19' on L2 at (-36.37, 41.37), 0.72 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.IO_RX_P20' on L2 at (-36.37, 44.35), 0.72 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.IO_TX_P19' on L2 at (-36.37, 42.97), 0.72 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.IO_TX_P20' on L2 at (-36.37, 45.2), 0.72 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.R\E\_DE_RX_P20' on L2 at (-36.37, 38.67), 0.72 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.R\E\_DE_TX_P20' on L2 at (-36.37, 40.12), 0.72 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'RTM_LVDS.RTM_LVD1_N' on L3 at (-36.37, 40.63), 0.72 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_LVDS.RTM_LVD1_P' on L3 at (-36.37, 40.95), 0.72 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_LVDS.RTM_LVD5_N' on L3 at (-36.37, 43.99), 0.72 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_LVDS.RTM_LVD5_P' on L3 at (-36.37, 43.67), 0.72 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • and 6 more

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-36.63%2C36.6%7C-36.12%2C49 serves each with its own layer_image region; all of them lie in x -37.63..-35.12, y 36.38..47.36 mm (board frame, Y up).

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

    • gap:P3:hole -40.84,41.4|-40.39,47.277 nets cross one gap in P3's negative-plane field at 7 places, the longest 0.65 mm (fastest: RTM_LVDS.RTM_LVD5_N at 100 ps 10-90 %, ASSUMED)

      Along 'MLVDS_F.R\E\_DE_RX_P20' on L2, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.65 mm under the track at (-40.62, 42.92). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 7 places on 7 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -40.84..-40.39, y 41.4..47.27. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'MLVDS_F.IO_RX_P19' on L2 at (-40.62, 45.62), 0.65 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.R\E\_DE_RX_P20' on L2 at (-40.62, 42.92), 0.65 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.R\E\_DE_TX_P20' on L2 at (-40.62, 44.37), 0.65 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'RTM_LVDS.RTM_LVD5_N' on L3 at (-40.62, 42.45), 0.46 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_LVDS.RTM_LVD5_P' on L3 at (-40.62, 42.23), 0.46 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_LVDS.RTM_LVD6_N' on L3 at (-40.62, 44.2), 0.46 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_LVDS.RTM_LVD6_P' on L3 at (-40.62, 43.97), 0.46 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-40.84%2C41.4%7C-40.39%2C47.27 serves each with its own layer_image region; all of them lie in x -41.84..-39.39, y 41.23..46.84 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.

    • gap:P3:hole -44.48,28.75|-36.12,37.1116 nets cross one gap in P3's negative-plane field at 16 places, the longest 3.38 mm (fastest: RTM_LVDS.RTM_LVD3_N at 100 ps 10-90 %, ASSUMED)

      Along 'RTM_LVDS.RTM_LVD3_P' on L3, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 3.38 mm under the track at (-37.33, 35.8). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 3.08 mm). 16 places on 16 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -44.48..-36.12, y 28.75..37.11. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RTM_LVDS.RTM_LVD3_P' on L3 at (-37.33, 35.8), 3.38 mm, running ALONG the bare copper for 3.08 mm, not across it; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_LVDS.RTM_LVD3_N' on L3 at (-39.24, 34.14), 0.83 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_LVDS.RTM_LVD4_N' on L3 at (-39.8, 33.43), 0.72 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_LVDS.RTM_LVD4_P' on L3 at (-39.58, 33.65), 0.72 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_SYNC_CLK_N' on L3 at (-40.92, 32.31), 0.72 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_SYNC_CLK_P' on L3 at (-40.69, 32.54), 0.72 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'MLVDS_F.IO_RX_P18' on L2 at (-36.39, 36.84), 0.59 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.IO_RX_P17' on L2 at (-36.99, 36.23), 0.51 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.IO_TX_P17' on L2 at (-37.46, 35.77), 0.51 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.IO_TX_P18' on L2 at (-38.84, 34.39), 0.51 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.R\E\_DE_RX_P17' on L2 at (-40.91, 32.31), 0.51 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.R\E\_DE_RX_P18' on L2 at (-40.14, 33.09), 0.51 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • and 4 more

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-44.48%2C28.75%7C-36.12%2C37.11 serves each with its own layer_image region; all of them lie in x -42.28..-35.12, y 31.13..38.08 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.

    • gap:P3:hole -48.55,46.81|-40.39,54.987 nets cross one gap in P3's negative-plane field at 7 places, the longest 3.4 mm (fastest: MLVDS_F.IO_RX_P17 at 3 ns 10-90 %, suggested by its name)

      Along 'MLVDS_F.R\E\_DE_TX_P19' on L2, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 3.4 mm under the track at (-47.27, 53.99). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 2.62 mm). 7 places on 7 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -48.55..-40.39, y 46.81..54.98. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'MLVDS_F.R\E\_DE_TX_P19' on L2 at (-47.27, 53.99), 3.4 mm, running ALONG the bare copper for 2.62 mm, not across it; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.IO_RX_P17' on L2 at (-45.55, 51.98), 0.65 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.IO_RX_P18' on L2 at (-45.2, 51.63), 0.65 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.IO_RX_P19' on L2 at (-43.55, 49.98), 0.65 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.IO_TX_P17' on L2 at (-45.9, 52.33), 0.65 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.R\E\_DE_RX_P20' on L2 at (-44.83, 51.25), 0.65 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.R\E\_DE_TX_P20' on L2 at (-44.45, 50.88), 0.65 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-48.55%2C46.81%7C-40.39%2C54.98 serves each with its own layer_image region; all of them lie in x -49.24..-42.55, y 48.65..55.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.

    • gap:P3:hole -49.73,11.85|-49.27,32.97'RTM_SYNC_CLK_N' crosses one gap in P3's negative-plane field at 1 place, the longest 0.46 mm (fastest: RTM_SYNC_CLK_N at 1 ns 10-90 %, suggested by its name)

      Along 'RTM_SYNC_CLK_N' on L3, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.46 mm under the track at (-49.5, 32.31). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -49.73..-49.27, y 11.85..32.97. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RTM_SYNC_CLK_N' on L3 at (-49.5, 32.31), 0.46 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-49.73%2C11.85%7C-49.27%2C32.97 serves each with its own layer_image region; all of them lie in x -50.73..-48.27, y 31.31..33.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.

    • gap:P3:hole -49.73,32.52|-40.39,41.8623 nets cross one gap in P3's negative-plane field at 23 places, the longest 0.65 mm (fastest: RTM_LVDS.RTM_LVD0_N at 100 ps 10-90 %, ASSUMED)

      Along 'RTM_LVDS.RTM_LVD2_N' on L3, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.65 mm under the track at (-45.52, 36.73). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 23 places on 23 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -49.73..-40.39, y 32.52..41.86. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RTM_LVDS.RTM_LVD0_N' on L3 at (-46.96, 35.28), 0.65 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_LVDS.RTM_LVD0_P' on L3 at (-46.74, 35.51), 0.65 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_LVDS.RTM_LVD1_N' on L3 at (-42.65, 39.6), 0.65 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_LVDS.RTM_LVD1_P' on L3 at (-42.42, 39.83), 0.65 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_LVDS.RTM_LVD2_N' on L3 at (-45.52, 36.73), 0.65 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_LVDS.RTM_LVD2_P' on L3 at (-45.29, 36.95), 0.65 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_LVDS.RTM_LVD3_N' on L3 at (-48.11, 34.14), 0.65 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_LVDS.RTM_LVD3_P' on L3 at (-47.88, 34.36), 0.65 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_LVDS.RTM_LVD4_N' on L3 at (-48.82, 33.43), 0.65 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_LVDS.RTM_LVD4_P' on L3 at (-48.59, 33.65), 0.65 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_LVDS.RTM_LVD7_N' on L3 at (-41.47, 40.78), 0.65 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_LVDS.RTM_LVD7_P' on L3 at (-41.7, 40.55), 0.65 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • and 11 more

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-49.73%2C32.52%7C-40.39%2C41.86 serves each with its own layer_image region; all of them lie in x -50.73..-39.74, y 31.54..42.51 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.

    • gap:P3:hole -50.6,48.49|-36.12,62.9711 nets cross one gap in P3's negative-plane field at 12 places, the longest 1.03 mm (fastest: MLVDS_F.IO_RX_P17 at 3 ns 10-90 %, suggested by its name)

      Along 'MLVDS_F.IO_TX_P20' on L2, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 1.03 mm under the track at (-43.62, 55.73). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 12 places on 11 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -50.6..-36.12, y 48.49..62.97. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'MLVDS_F.IO_TX_P20' on L2 at (-43.62, 55.73), 1.03 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.IO_RX_P20' on L2 at (-45.55, 58.18), 0.83 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.IO_RX_P20' on L2 at (-44.25, 56.8), 0.75 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.IO_TX_P19' on L2 at (-45.95, 58.22), 0.73 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.IO_RX_P17' on L2 at (-48.38, 60.75), 0.72 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.IO_RX_P18' on L2 at (-48.03, 60.4), 0.72 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.IO_RX_P19' on L2 at (-46.95, 59.32), 0.72 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.IO_TX_P17' on L2 at (-48.78, 61.15), 0.72 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.R\E\_DE_RX_P19' on L2 at (-49.95, 62.32), 0.72 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.R\E\_DE_RX_P20' on L2 at (-47.68, 60.05), 0.72 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.R\E\_DE_TX_P19' on L2 at (-49.6, 61.97), 0.72 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.R\E\_DE_TX_P20' on L2 at (-47.33, 59.7), 0.72 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-50.6%2C48.49%7C-36.12%2C62.97 serves each with its own layer_image region; all of them lie in x -50.95..-42.53, y 54.54..63.68 mm (board frame, Y up).

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

    • gap:P3:hole -50.6,62.46|-50.09,69.67'PVADJ2_IO7' crosses one gap in P3's negative-plane field at 1 place, the longest 0.51 mm (fastest: PVADJ2_IO7 at 2 ns 10-90 %, suggested by its name)

      Along 'PVADJ2_IO7' on L3, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.51 mm under the track at (-50.34, 69.05). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -50.6..-50.09, y 62.46..69.67. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'PVADJ2_IO7' on L3 at (-50.34, 69.05), 0.51 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-50.6%2C62.46%7C-50.09%2C69.67 serves each with its own layer_image region; all of them lie in x -51.6..-49.09, y 68.05..70.05 mm (board frame, Y up).

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

    • gap:P3:hole -51.76,69.16|-50.09,70.842 nets cross one gap in P3's negative-plane field at 2 places, the longest 2.74 mm (fastest: PVADJ2_IO8 at 2 ns 10-90 %, suggested by its name)

      Along 'MLVDS_F.R\E\_DE_RX_P19' on L2, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 2.74 mm under the track at (-50.96, 69.91). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 1.67 mm). 2 places on 2 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -51.76..-50.09, y 69.16..70.84. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'MLVDS_F.R\E\_DE_RX_P19' on L2 at (-50.96, 69.91), 2.74 mm, running ALONG the bare copper for 1.67 mm, not across it; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'PVADJ2_IO8' on L3 at (-50.97, 70.05), 0.72 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-51.76%2C69.16%7C-50.09%2C70.84 serves each with its own layer_image region; all of them lie in x -52.9..-49.09, y 67.81..71.84 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.

    • gap:P3:hole -51.8,54.52|-48.1,54.985 nets cross one gap in P3's negative-plane field at 5 places, the longest 0.65 mm (fastest: MLVDS_F.IO_TX_P18 at 3 ns 10-90 %, suggested by its name)

      Along 'MLVDS_F.R\E\_DE_RX_P19' on L2, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.65 mm under the track at (-48.68, 54.75). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 5 places on 5 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -51.8..-48.1, y 54.52..54.98. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'MLVDS_F.IO_TX_P18' on L2 at (-49.18, 54.75), 0.65 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.R\E\_DE_RX_P18' on L2 at (-50.73, 54.75), 0.65 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.R\E\_DE_RX_P19' on L2 at (-48.68, 54.75), 0.65 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.R\E\_DE_TX_P17' on L2 at (-50.18, 54.75), 0.65 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.R\E\_DE_TX_P18' on L2 at (-49.68, 54.75), 0.65 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-51.8%2C54.52%7C-48.1%2C54.98 serves each with its own layer_image region; all of them lie in x -51.95..-47.45, y 53.52..55.98 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.

    • gap:P3:hole -52.12,54.84|-51.66,58.25'MLVDS_F.R\E\_DE_RX_P17' crosses one gap in P3's negative-plane field at 1 place, the longest 4.07 mm (fastest: MLVDS_F.R\E\_DE_RX_P17 at 3 ns 10-90 %, suggested by its name)

      Along 'MLVDS_F.R\E\_DE_RX_P17' on L2, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 4.07 mm under the track at (-51.95, 56.64). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 3.12 mm). What cleared it: the hole at x -52.12..-51.66, y 54.84..58.25. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'MLVDS_F.R\E\_DE_RX_P17' on L2 at (-51.95, 56.64), 4.07 mm, running ALONG the bare copper for 3.12 mm, not across it; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-52.12%2C54.84%7C-51.66%2C58.25 serves each with its own layer_image region; all of them lie in x -52.95..-50.2, y 53.52..59.3 mm (board frame, Y up).

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

    • gap:P3:hole -62.56,73.61|-62.1,86.612 nets cross one gap in P3's negative-plane field at 12 places, the longest 0.46 mm (fastest: PVADJ2_IO10 at 2 ns 10-90 %, suggested by its name)

      Along 'VADJ1_IO1' on L3, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.46 mm under the track at (-62.33, 82.18). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 12 places on 12 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -62.56..-62.1, y 73.61..86.6. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'PVADJ2_IO10' on L3 at (-62.33, 78), 0.46 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'SFP_GTP.SFP8RX_P' on L3 at (-62.33, 83.33), 0.46 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'SFP_GTP.SFP8TX_N' on L3 at (-62.33, 85.35), 0.46 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'SFP_GTP.SFP8TX_P' on L3 at (-62.33, 85.58), 0.46 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'VADJ1_IO0' on L3 at (-62.33, 81.17), 0.46 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'VADJ1_IO1' on L3 at (-62.33, 82.18), 0.46 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'VADJ1_IO2' on L3 at (-62.33, 78.99), 0.46 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'VADJ1_IO3' on L3 at (-62.33, 76.13), 0.46 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'VADJ1_IO4' on L3 at (-62.33, 77.13), 0.46 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'VADJ1_IO5' on L3 at (-62.33, 80.18), 0.46 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'VADJ1_IO6' on L3 at (-62.33, 81.93), 0.46 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'VADJ1_RXD' on L3 at (-62.33, 75.08), 0.46 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-62.56%2C73.61%7C-62.1%2C86.6 serves each with its own layer_image region; all of them lie in x -63.56..-61.1, y 74.08..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.

    • gap:P3:hole -62.56,86.14|-62.1,88.744 nets cross one gap in P3's negative-plane field at 4 places, the longest 0.46 mm (fastest: SFP_GTP.SFP7RX_N at 3 ns 10-90 %, suggested by its name)

      Along 'SFP_GTP.SFP7TX_N' on L3, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.46 mm under the track at (-62.33, 86.3). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 4 places on 4 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -62.56..-62.1, y 86.14..88.74. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'SFP_GTP.SFP7RX_N' on L3 at (-62.33, 88.07), 0.46 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'SFP_GTP.SFP7RX_P' on L3 at (-62.18, 88.29), 0.46 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'SFP_GTP.SFP7TX_N' on L3 at (-62.33, 86.3), 0.46 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'SFP_GTP.SFP7TX_P' on L3 at (-62.33, 86.53), 0.46 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-62.56%2C86.14%7C-62.1%2C88.74 serves each with its own layer_image region; all of them lie in x -63.56..-61.1, y 85.3..89.29 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.

    • gap:P3:hole -62.78,73.21|-62.27,74.3'IO0_33' crosses one gap in P3's negative-plane field at 1 place, the longest 0.72 mm (fastest: IO0_33 at 100 ps 10-90 %, ASSUMED)

      Along 'IO0_33' on L3, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.72 mm under the track at (-62.55, 74.05). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -62.78..-62.27, y 73.21..74.3. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'IO0_33' on L3 at (-62.55, 74.05), 0.72 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-62.78%2C73.21%7C-62.27%2C74.3 serves each with its own layer_image region; all of them lie in x -63.78..-61.1, y 72.95..75.05 mm (board frame, Y up).

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

    • gap:P3:hole -64.88,88.28|-62.1,91.055 nets cross one gap in P3's negative-plane field at 5 places, the longest 0.65 mm (fastest: SFP_GTP.SFP5TX_P at 3 ns 10-90 %, suggested by its name)

      Along 'SFP_GTP.SFP6TX_P' on L3, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.65 mm under the track at (-62.65, 88.83). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 5 places on 5 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -64.88..-62.1, y 88.28..91.05. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'SFP_GTP.SFP5TX_P' on L3 at (-64.33, 90.63), 0.65 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'SFP_GTP.SFP6RX_N' on L3 at (-63.45, 89.63), 0.65 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'SFP_GTP.SFP6RX_P' on L3 at (-63.68, 89.85), 0.65 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'SFP_GTP.SFP6TX_N' on L3 at (-62.88, 89.05), 0.65 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'SFP_GTP.SFP6TX_P' on L3 at (-62.65, 88.83), 0.65 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-64.88%2C88.28%7C-62.1%2C91.05 serves each with its own layer_image region; all of them lie in x -65.77..-61.33, y 87.83..91.63 mm (board frame, Y up).

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

    • gap:P3:hole -68.53,90.6|-64.42,94.74 nets cross one gap in P3's negative-plane field at 4 places, the longest 0.65 mm (fastest: FPGA_CLK1_N at 1 ns 10-90 %, suggested by its name)

      Along 'SFP_GTP.SFP5TX_N' on L3, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.65 mm under the track at (-64.71, 90.85). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 4 places on 4 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -68.53..-64.42, y 90.6..94.7. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'FPGA_CLK1_N' on L3 at (-67.45, 93.62), 0.65 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'FPGA_CLK1_P' on L3 at (-67.22, 93.4), 0.65 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'SFP_GTP.SFP5RX_P' on L3 at (-65.93, 92.1), 0.65 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'SFP_GTP.SFP5TX_N' on L3 at (-64.71, 90.85), 0.65 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-68.53%2C90.6%7C-64.42%2C94.7 serves each with its own layer_image region; all of them lie in x -68.77..-63.35, y 89.85..94.62 mm (board frame, Y up).

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

    • gap:P3:hole -69.64,72.31|-68.1,73.85'VADJ1_IO4' crosses one gap in P3's negative-plane field at 1 place, the longest 0.72 mm (fastest: VADJ1_IO4 at 2 ns 10-90 %, suggested by its name)

      Along 'VADJ1_IO4' on L3, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.72 mm under the track at (-69.05, 73.27). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -69.64..-68.1, y 72.31..73.85. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'VADJ1_IO4' on L3 at (-69.05, 73.27), 0.72 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-69.64%2C72.31%7C-68.1%2C73.85 serves each with its own layer_image region; all of them lie in x -70.05..-68.05, y 71.91..74.63 mm (board frame, Y up).

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

    • gap:P3:hole -71.94,70.33|-51.25,70.8410 nets cross one gap in P3's negative-plane field at 10 places, the longest 0.67 mm (fastest: RTM_LVDS.RTM_LVD1_N at 100 ps 10-90 %, ASSUMED)

      Along 'PVADJ2_IO9' on L3, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.67 mm under the track at (-65.91, 70.73). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 10 places on 10 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -71.94..-51.25, y 70.33..70.84. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'PVADJ2_IO9' on L3 at (-65.91, 70.73), 0.67 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'MLVDS_F.IO_TX_P18' on L2 at (-54.95, 70.76), 0.53 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.R\E\_DE_RX_P17' on L2 at (-58.93, 70.58), 0.51 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.R\E\_DE_RX_P18' on L2 at (-57.93, 70.58), 0.51 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.R\E\_DE_TX_P17' on L2 at (-56.9, 70.58), 0.51 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MLVDS_F.R\E\_DE_TX_P18' on L2 at (-55.9, 70.58), 0.51 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'RTM_LVDS.RTM_LVD1_N' on L3 at (-70.09, 70.58), 0.51 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_LVDS.RTM_LVD1_P' on L3 at (-69.86, 70.58), 0.51 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_LVDS.RTM_LVD2_N' on L3 at (-71.04, 70.58), 0.51 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_LVDS.RTM_LVD2_P' on L3 at (-70.81, 70.58), 0.51 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-71.94%2C70.33%7C-51.25%2C70.84 serves each with its own layer_image region; all of them lie in x -72.04..-53.85, y 69.33..71.84 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.

    • gap:P3:hole -72.08,61.95|-55.96,62.468 nets cross one gap in P3's negative-plane field at 8 places, the longest 0.51 mm (fastest: PUDC at 100 ps 10-90 %, ASSUMED)

      Along 'PVADJ2_IO7' on L3, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.51 mm under the track at (-61.11, 62.21). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 8 places on 8 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -72.08..-55.96, y 61.95..62.46. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'PUDC' on L3 at (-69.44, 62.21), 0.51 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'PVADJ2_IO7' on L3 at (-61.11, 62.21), 0.51 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'PVADJ2_IO8' on L3 at (-62, 62.21), 0.51 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'PVADJ2_IO9' on L3 at (-66.98, 62.21), 0.51 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_LVDS.RTM_LVD1_N' on L3 at (-70.09, 62.21), 0.51 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_LVDS.RTM_LVD1_P' on L3 at (-69.86, 62.21), 0.51 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_LVDS.RTM_LVD2_N' on L3 at (-71.04, 62.21), 0.51 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_LVDS.RTM_LVD2_P' on L3 at (-70.81, 62.21), 0.51 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-72.08%2C61.95%7C-55.96%2C62.46 serves each with its own layer_image region; all of them lie in x -72.04..-60.11, y 60.95..63.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.

    • gap:P3:hole -72.68,73.35|-69.13,73.853 nets cross one gap in P3's negative-plane field at 3 places, the longest 0.56 mm (fastest: LA1.LA24_N at 100 ps 10-90 %, ASSUMED)

      Along 'LA1.LA24_N' on L2, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.56 mm under the track at (-72.05, 73.62). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 3 places on 3 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -72.68..-69.13, y 73.35..73.85. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'LA1.LA24_N' on L2 at (-72.05, 73.62), 0.56 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'PVADJ2_IO10' on L3 at (-71.93, 73.59), 0.52 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'LA1.LA24_P' on L2 at (-71.83, 73.69), 0.51 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-72.68%2C73.35%7C-69.13%2C73.85 serves each with its own layer_image region; all of them lie in x -73.14..-70.83, y 72.35..74.85 mm (board frame, Y up).

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

    • gap:P3:hole -73.91,68.35|-71.43,70.842 nets cross one gap in P3's negative-plane field at 2 places, the longest 0.72 mm (fastest: FJTAG.TMS at 2 ns 10-90 %, suggested by its name)

      Along 'PVADJ2_IO10' on L3, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.72 mm under the track at (-71.93, 70.34). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 2 places on 2 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -73.91..-71.43, y 68.35..70.84. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'PVADJ2_IO10' on L3 at (-71.93, 70.34), 0.72 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'FJTAG.TMS' on L2 at (-72.17, 70.1), 0.72 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-73.91%2C68.35%7C-71.43%2C70.84 serves each with its own layer_image region; all of them lie in x -73.52..-70.81, y 68.98..71.7 mm (board frame, Y up).

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

    • gap:P3:hole -74.7,59.33|-71.57,62.46'PVADJ2_IO10' crosses one gap in P3's negative-plane field at 1 place, the longest 0.69 mm (fastest: PVADJ2_IO10 at 2 ns 10-90 %, suggested by its name)

      Along 'PVADJ2_IO10' on L3, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.69 mm under the track at (-71.93, 62.09). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -74.7..-71.57, y 59.33..62.46. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'PVADJ2_IO10' on L3 at (-71.93, 62.09), 0.69 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-74.7%2C59.33%7C-71.57%2C62.46 serves each with its own layer_image region; all of them lie in x -72.93..-70.93, y 60.74..63.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.

    • gap:P3:hole -74.7,71.33|-72.17,73.852 nets cross one gap in P3's negative-plane field at 2 places, the longest 0.85 mm (fastest: LA1.LA24_N at 100 ps 10-90 %, ASSUMED)

      Along 'LA1.LA24_N' on L2, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.85 mm under the track at (-72.87, 73.23). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 2 places on 2 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -74.7..-72.17, y 71.33..73.85. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'LA1.LA24_N' on L2 at (-72.87, 73.23), 0.85 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'LA1.LA24_P' on L2 at (-73.03, 73), 0.72 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-74.7%2C71.33%7C-72.17%2C73.85 serves each with its own layer_image region; all of them lie in x -74.39..-71.31, y 72..74.23 mm (board frame, Y up).

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

    • gap:P3:hole -75.67,58.49|-74.35,59.812 nets cross one gap in P3's negative-plane field at 2 places, the longest 0.65 mm (fastest: RTM_LVDS.RTM_LVD0_N at 100 ps 10-90 %, ASSUMED)

      Along 'RTM_LVDS.RTM_LVD0_N' on L3, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.65 mm under the track at (-75.02, 59.15). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 2 places on 2 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -75.67..-74.35, y 58.49..59.81. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RTM_LVDS.RTM_LVD0_N' on L3 at (-75.02, 59.15), 0.65 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_LVDS.RTM_LVD0_P' on L3 at (-74.79, 59.37), 0.65 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-75.67%2C58.49%7C-74.35%2C59.81 serves each with its own layer_image region; all of them lie in x -76.02..-73.79, y 57.82..60.69 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.

    • gap:P3:hole -76.17,48.85|-75.72,57.31'HB2.HB19_N' crosses one gap in P3's negative-plane field at 1 place, the longest 2.36 mm (fastest: HB2.HB19_N at 100 ps 10-90 %, ASSUMED)

      Along 'HB2.HB19_N' on L2, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 2.36 mm under the track at (-75.85, 49.94). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 1.11 mm). What cleared it: the hole at x -76.17..-75.72, y 48.85..57.31. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'HB2.HB19_N' on L2 at (-75.85, 49.94), 2.36 mm, running ALONG the bare copper for 1.11 mm, not across it; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-76.17%2C48.85%7C-75.72%2C57.31 serves each with its own layer_image region; all of them lie in x -76.85..-74.72, y 47.85..52.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.

    • gap:P3:hole -76.17,56.85|-75.22,57.81'VADJ1_IO0' crosses one gap in P3's negative-plane field at 1 place, the longest 0.77 mm (fastest: VADJ1_IO0 at 2 ns 10-90 %, suggested by its name)

      Along 'VADJ1_IO0' on L3, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.77 mm under the track at (-75.8, 57.26). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -76.17..-75.22, y 56.85..57.81. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'VADJ1_IO0' on L3 at (-75.8, 57.26), 0.77 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-76.17%2C56.85%7C-75.22%2C57.81 serves each with its own layer_image region; all of them lie in x -76.8..-74.72, y 55.97..58.7 mm (board frame, Y up).

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

    • gap:P3:hole -76.43,46.09|-75.97,49.05'HB2.HB19_P' crosses one gap in P3's negative-plane field at 1 place, the longest 6.19 mm (fastest: HB2.HB19_P at 100 ps 10-90 %, ASSUMED)

      Along 'HB2.HB19_P' on L2, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 6.19 mm under the track at (-76.08, 47.51). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 4.03 mm). What cleared it: the hole at x -76.43..-75.97, y 46.09..49.05. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'HB2.HB19_P' on L2 at (-76.08, 47.51), 6.19 mm, running ALONG the bare copper for 4.03 mm, not across it; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-76.43%2C46.09%7C-75.97%2C49.05 serves each with its own layer_image region; all of them lie in x -77.08..-74.72, y 45.12..53.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.

    • gap:P3:hole -76.93,71.33|-74.19,71.844 nets cross one gap in P3's negative-plane field at 4 places, the longest 0.51 mm (fastest: RTM_LVDS.RTM_LVD0_N at 100 ps 10-90 %, ASSUMED)

      Along 'RTM_LVDS.RTM_LVD0_N' on L3, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.51 mm under the track at (-75.02, 71.58). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 4 places on 4 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -76.93..-74.19, y 71.33..71.84. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RTM_LVDS.RTM_LVD0_N' on L3 at (-75.02, 71.58), 0.51 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_LVDS.RTM_LVD0_P' on L3 at (-74.79, 71.58), 0.51 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'VADJ1_IO0' on L3 at (-75.8, 71.58), 0.51 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'VADJ1_IO1' on L3 at (-76.07, 71.58), 0.51 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-76.93%2C71.33%7C-74.19%2C71.84 serves each with its own layer_image region; all of them lie in x -77.07..-73.79, y 70.33..72.84 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.

    • gap:P3:hole -77.14,68.35|-73.41,68.864 nets cross one gap in P3's negative-plane field at 4 places, the longest 0.51 mm (fastest: RTM_LVDS.RTM_LVD0_N at 100 ps 10-90 %, ASSUMED)

      Along 'RTM_LVDS.RTM_LVD0_N' on L3, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.51 mm under the track at (-75.02, 68.61). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 4 places on 4 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -77.14..-73.41, y 68.35..68.86. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RTM_LVDS.RTM_LVD0_N' on L3 at (-75.02, 68.61), 0.51 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_LVDS.RTM_LVD0_P' on L3 at (-74.79, 68.61), 0.51 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'VADJ1_IO0' on L3 at (-75.8, 68.61), 0.51 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'VADJ1_IO1' on L3 at (-76.07, 68.61), 0.51 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-77.14%2C68.35%7C-73.41%2C68.86 serves each with its own layer_image region; all of them lie in x -77.07..-73.79, y 67.35..69.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.

    • gap:P3:hole -78.11,68.35|-76.63,69.832 nets cross one gap in P3's negative-plane field at 2 places, the longest 0.72 mm (fastest: RTM_LVDS.RTM_LVD3_N at 100 ps 10-90 %, ASSUMED)

      Along 'RTM_LVDS.RTM_LVD3_N' on L3, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.72 mm under the track at (-77.08, 68.79). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 2 places on 2 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -78.11..-76.63, y 68.35..69.83. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RTM_LVDS.RTM_LVD3_N' on L3 at (-77.08, 68.79), 0.72 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_LVDS.RTM_LVD3_P' on L3 at (-76.85, 68.64), 0.58 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-78.11%2C68.35%7C-76.63%2C69.83 serves each with its own layer_image region; all of them lie in x -78.08..-75.85, y 67.35..70.15 mm (board frame, Y up).

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

    • gap:P3:hole -78.11,69.32|-77.6,70.66'FJTAG.TMS' crosses one gap in P3's negative-plane field at 1 place, the longest 0.51 mm (fastest: FJTAG.TMS at 2 ns 10-90 %, suggested by its name)

      Along 'FJTAG.TMS' on L2, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.51 mm under the track at (-77.85, 70.1). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -78.11..-77.6, y 69.32..70.66. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'FJTAG.TMS' on L2 at (-77.85, 70.1), 0.51 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-78.11%2C69.32%7C-77.6%2C70.66 serves each with its own layer_image region; all of them lie in x -79.11..-76.6, y 69.1..71.1 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.

    • gap:P3:hole -78.11,70.16|-76.42,71.842 nets cross one gap in P3's negative-plane field at 2 places, the longest 0.94 mm (fastest: RTM_LVDS.RTM_LVD3_N at 100 ps 10-90 %, ASSUMED)

      Along 'RTM_LVDS.RTM_LVD3_N' on L3, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.94 mm under the track at (-77.08, 71.03). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 2 places on 2 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -78.11..-76.42, y 70.16..71.84. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RTM_LVDS.RTM_LVD3_N' on L3 at (-77.08, 71.03), 0.94 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'FJTAG.TCK' on L2 at (-77.11, 71.15), 0.72 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-78.11%2C70.16%7C-76.42%2C71.84 serves each with its own layer_image region; all of them lie in x -78.47..-75.75, y 69.83..72.61 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.

    • gap:P3:hole -78.45,44.07|-76.22,46.32 nets cross one gap in P3's negative-plane field at 2 places, the longest 1.06 mm (fastest: RTM_LVDS.RTM_LVD3_N at 100 ps 10-90 %, ASSUMED)

      Along 'RTM_LVDS.RTM_LVD3_N' on L3, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 1.06 mm under the track at (-77.63, 45.09). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 2 places on 2 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -78.45..-76.22, y 44.07..46.3. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RTM_LVDS.RTM_LVD3_N' on L3 at (-77.63, 45.09), 1.06 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_LVDS.RTM_LVD3_P' on L3 at (-77.4, 45.16), 0.65 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-78.45%2C44.07%7C-76.22%2C46.3 serves each with its own layer_image region; all of them lie in x -78.95..-76.4, y 43.25..46.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.

    • gap:P3:hole -84.23,94.25|-68.07,94.74 nets cross one gap in P3's negative-plane field at 4 places, the longest 10.01 mm (fastest: RTM_PS# at 100 ps 10-90 %, ASSUMED)

      Along 'RTM_PS#' on L3, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 10.01 mm under the track at (-72.87, 94.46). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 9.37 mm). 4 places on 4 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -84.23..-68.07, y 94.25..94.7. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RTM_PS#' on L3 at (-72.87, 94.46), 10.01 mm, running ALONG the bare copper for 9.37 mm, not across it; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_TCK' on L3 at (-80.35, 94.48), 0.65 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_TDI' on L3 at (-78.63, 94.48), 0.65 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_TMS' on L3 at (-79.2, 94.48), 0.65 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-84.23%2C94.25%7C-68.07%2C94.7 serves each with its own layer_image region; all of them lie in x -81.58..-66.96, y 93.25..95.7 mm (board frame, Y up).

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

    • gap:P3:hole -87.73,33.65|-84.91,36.47'MGT.PCIE_CLK1_P' crosses one gap in P3's negative-plane field at 1 place, the longest 4.13 mm (fastest: MGT.PCIE_CLK1_P at 1 ns 10-90 %, suggested by its name)

      Along 'MGT.PCIE_CLK1_P' on L2, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 4.13 mm under the track at (-86.22, 35.26). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 3.39 mm). What cleared it: the hole at x -87.73..-84.91, y 33.65..36.47. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'MGT.PCIE_CLK1_P' on L2 at (-86.22, 35.26), 4.13 mm, running ALONG the bare copper for 3.39 mm, not across it; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-87.73%2C33.65%7C-84.91%2C36.47 serves each with its own layer_image region; all of them lie in x -88.84..-83.91, y 32.65..37.57 mm (board frame, Y up).

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

    • gap:P3:hole -97.38,94.25|-90.37,101.25'RTM_TDO' crosses one gap in P3's negative-plane field at 1 place, the longest 0.65 mm (fastest: RTM_TDO at 2 ns 10-90 %, suggested by its name)

      Along 'RTM_TDO' on L3, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.65 mm under the track at (-92.03, 95.9). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -97.38..-90.37, y 94.25..101.25. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RTM_TDO' on L3 at (-92.03, 95.9), 0.65 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-97.38%2C94.25%7C-90.37%2C101.25 serves each with its own layer_image region; all of them lie in x -93.35..-90.7, y 94.9..96.9 mm (board frame, Y up).

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

    • gap:P4:hole -106.46,87.82|-101.89,92.392 nets cross one gap in P4's negative-plane field at 2 places, the longest 0.4 mm (fastest: RTM_PS# at 100 ps 10-90 %, ASSUMED)

      Along 'RTM_TDI' on L3, P4 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.4 mm under the track at (-105.08, 91.04). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 2 places on 2 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -106.46..-101.89, y 87.82..92.39. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RTM_TDI' on L3 at (-105.08, 91.04), 0.4 mm; other side: PVADJ1 on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4
      • 'RTM_PS#' on L3 at (-104.52, 90.45), 0.38 mm; other side: PVADJ1 on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP4%3Ahole%20-106.46%2C87.82%7C-101.89%2C92.39 serves each with its own layer_image region; all of them lie in x -106.27..-103.39, y 89.32..92.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.

    • gap:P4:hole -106.78,92.9|-106.4,95.922 nets cross one gap in P4's negative-plane field at 2 places, the longest 0.45 mm (fastest: RTM_TCK at 2 ns 10-90 %, suggested by its name)

      Along 'RTM_TCK' on L3, P4 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.45 mm under the track at (-106.59, 93.1). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 2 places on 2 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -106.78..-106.4, y 92.9..95.92. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RTM_TCK' on L3 at (-106.59, 93.1), 0.45 mm; other side: PVADJ1 on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4
      • 'RTM_TDO' on L3 at (-106.59, 93.4), 0.38 mm; other side: PVADJ1 on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP4%3Ahole%20-106.78%2C92.9%7C-106.4%2C95.92 serves each with its own layer_image region; all of them lie in x -107.78..-105.33, y 92.1..94.4 mm (board frame, Y up).

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

    • gap:P4:hole -108.89,27.76|-89.66,46.99'MGT.LINK23_CLK_P' crosses one gap in P4's negative-plane field at 1 place, the longest 0.51 mm (fastest: MGT.LINK23_CLK_P at 1 ns 10-90 %, suggested by its name)

      Along 'MGT.LINK23_CLK_P' on L3, P4 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.51 mm under the track at (-105.64, 43.74). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -108.89..-89.66, y 27.76..46.99. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'MGT.LINK23_CLK_P' on L3 at (-105.64, 43.74), 0.51 mm; other side: (negative-layer field) on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP4%3Ahole%20-108.89%2C27.76%7C-89.66%2C46.99 serves each with its own layer_image region; all of them lie in x -106.82..-104.47, y 42.57..44.92 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.

    • gap:P4:hole -109.99,92.01|-106.08,92.39'RTM_TMS' crosses one gap in P4's negative-plane field at 1 place, the longest 4.07 mm (fastest: RTM_TMS at 2 ns 10-90 %, suggested by its name)

      Along 'RTM_TMS' on L3, P4 is a negative layer (copper everywhere inside the profile), and its field is cleared for 4.07 mm under the track at (-107.85, 92.18). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 3.46 mm). What cleared it: the hole at x -109.99..-106.08, y 92.01..92.39. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RTM_TMS' on L3 at (-107.85, 92.18), 4.07 mm, running ALONG the bare copper for 3.46 mm, not across it; other side: PVADJ1 on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP4%3Ahole%20-109.99%2C92.01%7C-106.08%2C92.39 serves each with its own layer_image region; all of them lie in x -111.04..-104.98, y 91.18..93.18 mm (board frame, Y up).

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

    • gap:P4:hole -110.39,92.41|-110.01,93.59'RTM_TCK' crosses one gap in P4's negative-plane field at 1 place, the longest 0.38 mm (fastest: RTM_TCK at 2 ns 10-90 %, suggested by its name)

      Along 'RTM_TCK' on L3, P4 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.38 mm under the track at (-110.2, 93.1). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -110.39..-110.01, y 92.41..93.59. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RTM_TCK' on L3 at (-110.2, 93.1), 0.38 mm; other side: PVADJ1 on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP4%3Ahole%20-110.39%2C92.41%7C-110.01%2C93.59 serves each with its own layer_image region; all of them lie in x -111.39..-109.01, y 92.1..94.1 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.

    • gap:P4:hole -110.89,93.21|-110.01,94.09'RTM_TDO' crosses one gap in P4's negative-plane field at 1 place, the longest 0.46 mm (fastest: RTM_TDO at 2 ns 10-90 %, suggested by its name)

      Along 'RTM_TDO' on L3, P4 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.46 mm under the track at (-110.24, 93.4). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -110.89..-110.01, y 93.21..94.09. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RTM_TDO' on L3 at (-110.24, 93.4), 0.46 mm; other side: PVADJ1 on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP4%3Ahole%20-110.89%2C93.21%7C-110.01%2C94.09 serves each with its own layer_image region; all of them lie in x -111.47..-109.01, y 92.4..94.4 mm (board frame, Y up).

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

    • gap:P4:hole -12.73,54.05|-12.47,90.556 nets cross one gap in P4's negative-plane field at 6 places, the longest 0.25 mm (fastest: RTM_LVDS.RTM_LVD0_N at 100 ps 10-90 %, ASSUMED)

      Along 'RTM_LVDS.RTM_LVD0_N' on L3, P4 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.25 mm under the track at (-12.6, 61.4). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 6 places on 6 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -12.73..-12.47, y 54.05..90.55. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RTM_LVDS.RTM_LVD0_N' on L3 at (-12.6, 61.4), 0.25 mm; other side: (negative-layer field) on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4
      • 'RTM_LVDS.RTM_LVD0_P' on L3 at (-12.6, 61.63), 0.25 mm; other side: (negative-layer field) on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4
      • 'RTM_LVDS.RTM_LVD4_N' on L3 at (-12.6, 58.15), 0.25 mm; other side: (negative-layer field) on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4
      • 'RTM_LVDS.RTM_LVD4_P' on L3 at (-12.6, 58.38), 0.25 mm; other side: (negative-layer field) on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4
      • 'RTM_SYNC_CLK_N' on L3 at (-12.6, 56.26), 0.25 mm; other side: (negative-layer field) on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4
      • 'RTM_SYNC_CLK_P' on L3 at (-12.6, 56.49), 0.25 mm; other side: (negative-layer field) on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP4%3Ahole%20-12.73%2C54.05%7C-12.47%2C90.55 serves each with its own layer_image region; all of them lie in x -13.73..-11.47, y 55.26..62.63 mm (board frame, Y up).

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

    • gap:P4:hole -124.21,87.78|-115.09,88.29'RTM_PS#' crosses one gap in P4's negative-plane field at 1 place, the longest 0.51 mm (fastest: RTM_PS# at 100 ps 10-90 %, ASSUMED)

      Along 'RTM_PS#' on L3, P4 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.51 mm under the track at (-120.73, 88.04). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -124.21..-115.09, y 87.78..88.29. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RTM_PS#' on L3 at (-120.73, 88.04), 0.51 mm; other side: (negative-layer field) on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP4%3Ahole%20-124.21%2C87.78%7C-115.09%2C88.29 serves each with its own layer_image region; all of them lie in x -121.73..-119.73, y 86.78..89.29 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.

    • gap:P4:hole -125.43,86.56|-123.7,88.292 nets cross one gap in P4's negative-plane field at 2 places, the longest 0.72 mm (fastest: RTM_TDI at 2 ns 10-90 %, suggested by its name)

      Along 'RTM_TMS' on L3, P4 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.72 mm under the track at (-124.88, 87.11). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 2 places on 2 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -125.43..-123.7, y 86.56..88.29. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RTM_TDI' on L3 at (-124.36, 87.63), 0.72 mm; other side: (negative-layer field) on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4
      • 'RTM_TMS' on L3 at (-124.88, 87.11), 0.72 mm; other side: (negative-layer field) on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP4%3Ahole%20-125.43%2C86.56%7C-123.7%2C88.29 serves each with its own layer_image region; all of them lie in x -125.88..-123.36, y 85.75..88.98 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.

    • gap:P4:hole -132.41,53.14|-131.95,90.47'RTM_PS#' crosses one gap in P4's negative-plane field at 1 place, the longest 0.46 mm (fastest: RTM_PS# at 100 ps 10-90 %, ASSUMED)

      Along 'RTM_PS#' on L3, P4 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.46 mm under the track at (-132.18, 78.28). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -132.41..-131.95, y 53.14..90.47. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RTM_PS#' on L3 at (-132.18, 78.28), 0.46 mm; other side: (negative-layer field) on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP4%3Ahole%20-132.41%2C53.14%7C-131.95%2C90.47 serves each with its own layer_image region; all of them lie in x -133.41..-130.95, y 77.28..79.28 mm (board frame, Y up).

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

    • gap:P4:hole -138.07,68.22|-137.62,89.872 nets cross one gap in P4's negative-plane field at 2 places, the longest 0.46 mm (fastest: FPGA_SCL at 10 ns 10-90 %, suggested by its name)

      Along 'FPGA_SCL' on L3, P4 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.46 mm under the track at (-137.85, 83.36). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 2 places on 2 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -138.07..-137.62, y 68.22..89.87. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'FPGA_SCL' on L3 at (-137.85, 83.36), 0.46 mm; other side: (negative-layer field) on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4
      • 'FPGA_SDA' on L3 at (-137.85, 82.98), 0.46 mm; other side: (negative-layer field) on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP4%3Ahole%20-138.07%2C68.22%7C-137.62%2C89.87 serves each with its own layer_image region; all of them lie in x -139.07..-136.62, y 81.98..84.36 mm (board frame, Y up).

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

    • gap:P4:hole -58.62,28.52|-54.48,32.66'RTM_SYNC_CLK_N' crosses one gap in P4's negative-plane field at 1 place, the longest 0.36 mm (fastest: RTM_SYNC_CLK_N at 1 ns 10-90 %, suggested by its name)

      Along 'RTM_SYNC_CLK_N' on L3, P4 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.36 mm under the track at (-58.27, 32.31). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -58.62..-54.48, y 28.52..32.66. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RTM_SYNC_CLK_N' on L3 at (-58.27, 32.31), 0.36 mm; other side: (negative-layer field) on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP4%3Ahole%20-58.62%2C28.52%7C-54.48%2C32.66 serves each with its own layer_image region; all of them lie in x -59.45..-57.09, y 31.31..33.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.

    • gap:P4:hole -76.99,94.01|-16.18,94.26'RTM_PS#' crosses one gap in P4's negative-plane field at 1 place, the longest 1.51 mm (fastest: RTM_PS# at 100 ps 10-90 %, ASSUMED)

      Along 'RTM_PS#' on L3, P4 is a negative layer (copper everywhere inside the profile), and its field is cleared for 1.51 mm under the track at (-63.54, 94.24). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 1.48 mm). What cleared it: the hole at x -76.99..-16.18, y 94.01..94.26. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RTM_PS#' on L3 at (-63.54, 94.24), 1.51 mm, running ALONG the bare copper for 1.48 mm, not across it; other side: (negative-layer field) on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP4%3Ahole%20-76.99%2C94.01%7C-16.18%2C94.26 serves each with its own layer_image region; all of them lie in x -65.29..-61.8, y 93.24..95.26 mm (board frame, Y up).

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

    • gap:P4:hole -84.71,32.41|-58.37,32.662 nets cross one gap in P4's negative-plane field at 2 places, the longest 21.51 mm (fastest: RTM_SYNC_CLK_N at 1 ns 10-90 %, suggested by its name)

      Along 'RTM_SYNC_CLK_P' on L3, P4 is a negative layer (copper everywhere inside the profile), and its field is cleared for 21.51 mm under the track at (-68.7, 32.54). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 20.95 mm). 2 places on 2 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -84.71..-58.37, y 32.41..32.66. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RTM_SYNC_CLK_P' on L3 at (-68.7, 32.54), 21.51 mm, running ALONG the bare copper for 20.95 mm, not across it; other side: (negative-layer field) on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4
      • 'RTM_SYNC_CLK_N' on L3 at (-80.08, 32.53), 0.67 mm; other side: (negative-layer field) on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP4%3Ahole%20-84.71%2C32.41%7C-58.37%2C32.66 serves each with its own layer_image region; all of them lie in x -81.37..-57.32, y 31.41..33.66 mm (board frame, Y up).

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

    • gap:P6:hole -101.4,-21.93|-95.83,-21.47'RXD_USBB' crosses one gap in P6's negative-plane field at 1 place, the longest 3.6 mm (fastest: RXD_USBB at 500 ps 10-90 %, suggested by its name)

      Along 'RXD_USBB' on L6, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 3.6 mm under the track at (-99.2, -21.7). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 2.95 mm). What cleared it: the hole at x -101.4..-95.83, y -21.93..-21.47. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RXD_USBB' on L6 at (-99.2, -21.7), 3.6 mm, running ALONG the bare copper for 2.95 mm, not across it; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-101.4%2C-21.93%7C-95.83%2C-21.47 serves each with its own layer_image region; all of them lie in x -101.9..-96.5, y -22.93..-20.47 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.

    • gap:P6:hole -103.88,95.57|-95.6,96.032 nets cross one gap in P6's negative-plane field at 2 places, the longest 0.5 mm (fastest: M1 at 100 ps 10-90 %, ASSUMED)

      Along 'M1' on L6, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.5 mm under the track at (-95.88, 95.8). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 2 places on 2 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -103.88..-95.6, y 95.57..96.03. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'M1' on L6 at (-95.88, 95.8), 0.5 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'M2' on L6 at (-97, 95.8), 0.46 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-103.88%2C95.57%7C-95.6%2C96.03 serves each with its own layer_image region; all of them lie in x -98..-94.88, y 94.53..97.03 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.

    • gap:P6:hole -133.3,95.57|-103.42,96.035 nets cross one gap in P6's negative-plane field at 5 places, the longest 0.88 mm (fastest: LED_B at 100 ps 10-90 %, ASSUMED)

      Along 'LED_R' on L6, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.88 mm under the track at (-132.66, 95.75). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 5 places on 5 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -133.3..-103.42, y 95.57..96.03. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'LED_R' on L6 at (-132.66, 95.75), 0.88 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'I2C1.SDA' on L5 at (-126.35, 95.8), 0.65 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'LED_B' on L6 at (-129.63, 95.8), 0.65 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'LED_G' on L6 at (-130.98, 95.8), 0.65 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'I2C1.SCL' on L6 at (-122.53, 95.8), 0.46 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-133.3%2C95.57%7C-103.42%2C96.03 serves each with its own layer_image region; all of them lie in x -134.18..-121.53, y 94.57..97.03 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.

    • gap:P6:hole -150.35,38.72|-149.9,44.332 nets cross one gap in P6's negative-plane field at 2 places, the longest 0.65 mm (fastest: I2C2.SCL at 10 ns 10-90 %, suggested by its name)

      Along 'I2C2.SCL' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.65 mm under the track at (-150.13, 41.13). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 2 places on 2 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -150.35..-149.9, y 38.72..44.33. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'I2C2.SCL' on L5 at (-150.13, 41.13), 0.65 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'I2C2.SDA' on L5 at (-150.13, 42.45), 0.65 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-150.35%2C38.72%7C-149.9%2C44.33 serves each with its own layer_image region; all of them lie in x -151.35..-148.9, y 39.9..43.68 mm (board frame, Y up).

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

    • gap:P6:hole -24.25,62.75|-21.75,63.254 nets cross one gap in P6's negative-plane field at 4 places, the longest 0.51 mm (fastest: RTM_PS# at 100 ps 10-90 %, ASSUMED)

      Along 'RTM_PS#' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.51 mm under the track at (-22.84, 63). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 4 places on 4 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -24.25..-21.75, y 62.75..63.25. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RTM_PS#' on L5 at (-22.84, 63), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'RTM_SCL' on L5 at (-22.66, 63), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'RTM_TDI' on L5 at (-23.13, 63), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'RTM_TMS' on L5 at (-23.73, 63), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-24.25%2C62.75%7C-21.75%2C63.25 serves each with its own layer_image region; all of them lie in x -24.73..-21.66, y 61.75..64.25 mm (board frame, Y up).

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

    • gap:P6:hole -25.65,62.75|-23.75,64.653 nets cross one gap in P6's negative-plane field at 3 places, the longest 0.72 mm (fastest: RTM_TCK at 2 ns 10-90 %, suggested by its name)

      Along 'RTM_TCK' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.72 mm under the track at (-24.6, 63.6). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 3 places on 3 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -25.65..-23.75, y 62.75..64.65. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RTM_TCK' on L5 at (-24.6, 63.6), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'RTM_TDO' on L5 at (-25.02, 64.02), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'RTM_SDA' on L5 at (-24.15, 63.15), 0.71 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-25.65%2C62.75%7C-23.75%2C64.65 serves each with its own layer_image region; all of them lie in x -26.02..-23.15, y 61.8..65.37 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.

    • gap:P6:hole -28.2,90.65|-22.85,967 nets cross one gap in P6's negative-plane field at 7 places, the longest 0.46 mm (fastest: RTM_PS# at 100 ps 10-90 %, ASSUMED)

      Along 'RTM_TCK' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.46 mm under the track at (-26.66, 92.2). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 7 places on 7 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -28.2..-22.85, y 90.65..96. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RTM_PS#' on L5 at (-26.14, 92.71), 0.46 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'RTM_SCL' on L5 at (-26.01, 92.84), 0.46 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'RTM_SDA' on L5 at (-26.53, 92.32), 0.46 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'RTM_TCK' on L5 at (-26.66, 92.2), 0.46 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'RTM_TDI' on L5 at (-26.27, 92.58), 0.46 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'RTM_TDO' on L5 at (-26.8, 92.05), 0.46 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'RTM_TMS' on L5 at (-26.4, 92.45), 0.46 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-28.2%2C90.65%7C-22.85%2C96 serves each with its own layer_image region; all of them lie in x -27.97..-24.85, y 90.88..94 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.

    • gap:P6:hole -28.23,85.75|-21.25,86.257 nets cross one gap in P6's negative-plane field at 7 places, the longest 0.51 mm (fastest: RTM_PS# at 100 ps 10-90 %, ASSUMED)

      Along 'RTM_TDI' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.51 mm under the track at (-23.13, 86). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 7 places on 7 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -28.23..-21.25, y 85.75..86.25. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RTM_PS#' on L5 at (-22.78, 86), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'RTM_SCL' on L5 at (-22.35, 86), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'RTM_SDA' on L5 at (-24.15, 86), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'RTM_TCK' on L5 at (-24.6, 86), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'RTM_TDI' on L5 at (-23.13, 86), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'RTM_TDO' on L5 at (-25.02, 86), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'RTM_TMS' on L5 at (-23.73, 86), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-28.23%2C85.75%7C-21.25%2C86.25 serves each with its own layer_image region; all of them lie in x -26.02..-21.35, y 84.75..87.25 mm (board frame, Y up).

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

    • gap:P6:hole -45.49,35.03|-41.22,39.296 nets cross one gap in P6's negative-plane field at 6 places, the longest 0.51 mm (fastest: DP2.DP0_C2M_N at 100 ps 10-90 %, ASSUMED)

      Along 'GBT2.GBTCLK0_M2C_N' on L6, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.51 mm under the track at (-44.64, 38.45). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 6 places on 6 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -45.49..-41.22, y 35.03..39.29. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'DP2.DP0_C2M_N' on L6 at (-41.96, 35.76), 0.51 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP0_C2M_P' on L6 at (-41.8, 35.6), 0.51 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP1_M2C_N' on L6 at (-43.74, 37.54), 0.51 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP1_M2C_P' on L6 at (-43.58, 37.38), 0.51 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'GBT2.GBTCLK0_M2C_N' on L6 at (-44.64, 38.45), 0.51 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'GBT2.GBTCLK0_M2C_P' on L6 at (-44.49, 38.29), 0.51 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-45.49%2C35.03%7C-41.22%2C39.29 serves each with its own layer_image region; all of them lie in x -45.82..-40.62, y 34.42..39.63 mm (board frame, Y up).

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

    • gap:P6:hole -47.32,60.99|-44.98,63.322 nets cross one gap in P6's negative-plane field at 2 places, the longest 0.72 mm (fastest: RX213_3_N at 3 ns 10-90 %, suggested by its name)

      Along 'RX213_3_N' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.72 mm under the track at (-45.82, 61.82). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 2 places on 2 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -47.32..-44.98, y 60.99..63.32. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RX213_3_N' on L5 at (-45.82, 61.82), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'RX213_3_P' on L5 at (-46.04, 62.04), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-47.32%2C60.99%7C-44.98%2C63.32 serves each with its own layer_image region; all of them lie in x -47.4..-44.46, y 60.82..63.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.

    • gap:P6:hole -51.82,62.81|-46.81,63.323 nets cross one gap in P6's negative-plane field at 5 places, the longest 5.08 mm (fastest: RX213_2_N at 3 ns 10-90 %, suggested by its name)

      Along 'RX213_2_N' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 5.08 mm under the track at (-49.08, 62.96). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 3 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 4.54 mm). 5 places on 3 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -51.82..-46.81, y 62.81..63.32. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RX213_2_N' on L5 at (-49.08, 62.96), 5.08 mm, running ALONG the bare copper for 4.35 mm, not across it; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'RX213_2_P' on L5 at (-49.09, 63.19), 4.97 mm, running ALONG the bare copper for 4.54 mm, not across it; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'TX213_1_P' on L6 at (-50.51, 62.96), 1.23 mm, running ALONG the bare copper for 0.51 mm, not across it; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'TX213_1_P' on L6 at (-47.1, 63.23), 1.14 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'TX213_1_P' on L6 at (-48.45, 63.07), 0.51 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-51.82%2C62.81%7C-46.81%2C63.32 serves each with its own layer_image region; all of them lie in x -52.8..-45.6, y 61.74..64.32 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.

    • gap:P6:hole -53.68,46.97|-53.22,58.82 nets cross one gap in P6's negative-plane field at 2 places, the longest 0.46 mm (fastest: FTMP.DXN at 100 ps 10-90 %, ASSUMED)

      Along 'FTMP.DXN' on L6, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.46 mm under the track at (-53.37, 56.08). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 2 places on 2 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -53.68..-53.22, y 46.97..58.8. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'FTMP.DXN' on L6 at (-53.37, 56.08), 0.46 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'FTMP.DXP' on L6 at (-53.45, 55.1), 0.46 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-53.68%2C46.97%7C-53.22%2C58.8 serves each with its own layer_image region; all of them lie in x -54.68..-52.22, y 54.1..57.11 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.

    • gap:P6:hole -53.7,58.32|-53.2,61.434 nets cross one gap in P6's negative-plane field at 4 places, the longest 0.51 mm (fastest: MGT213_CLK1_N at 1 ns 10-90 %, suggested by its name)

      Along 'TX213_2_N' on L6, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.51 mm under the track at (-53.45, 60.2). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 4 places on 4 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -53.7..-53.2, y 58.32..61.43. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'MGT213_CLK1_N' on L5 at (-53.45, 59.15), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'MGT213_CLK1_P' on L5 at (-53.45, 58.93), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'TX213_2_N' on L6 at (-53.45, 60.2), 0.51 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'TX213_2_P' on L6 at (-53.45, 59.98), 0.51 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-53.7%2C58.32%7C-53.2%2C61.43 serves each with its own layer_image region; all of them lie in x -54.7..-52.2, y 57.93..61.2 mm (board frame, Y up).

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

    • gap:P6:hole -53.7,60.93|-51.31,63.324 nets cross one gap in P6's negative-plane field at 4 places, the longest 0.65 mm (fastest: MGT213_CLK0_N at 1 ns 10-90 %, suggested by its name)

      Along 'RX213_3_P' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.65 mm under the track at (-53.19, 61.23). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 4 places on 4 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -53.7..-51.31, y 60.93..63.32. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RX213_3_P' on L5 at (-53.19, 61.23), 0.65 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'RX213_2_N' on L5 at (-52.01, 62.64), 0.63 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'MGT213_CLK0_N' on L6 at (-51.79, 63.05), 0.6 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'RX213_3_N' on L5 at (-53.45, 61), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-53.7%2C60.93%7C-51.31%2C63.32 serves each with its own layer_image region; all of them lie in x -54.7..-50.56, y 60..64.32 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.

    • gap:P6:hole -55.9,74.12|-30.82,74.583 nets cross one gap in P6's negative-plane field at 3 places, the longest 0.65 mm (fastest: IO17N_32 at 100 ps 10-90 %, ASSUMED)

      Along 'IO17N_32' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.65 mm under the track at (-34.42, 74.35). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 3 places on 3 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -55.9..-30.82, y 74.12..74.58. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'IO17N_32' on L5 at (-34.42, 74.35), 0.65 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'IO17P_32' on L5 at (-35.16, 74.35), 0.65 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'I2C_CPU.SCL' on L5 at (-31.04, 74.35), 0.56 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-55.9%2C74.12%7C-30.82%2C74.58 serves each with its own layer_image region; all of them lie in x -36.39..-30.04, y 73.12..75.68 mm (board frame, Y up).

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

    • gap:P6:hole -57.25,43.4|-53.22,47.43'PLL_CTRL.PLL_VADJ2_DAC2_SYNC_N' crosses one gap in P6's negative-plane field at 1 place, the longest 0.65 mm (fastest: PLL_CTRL.PLL_VADJ2_DAC2_SYNC_N at 100 ps 10-90 %, ASSUMED)

      Along 'PLL_CTRL.PLL_VADJ2_DAC2_SYNC_N' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.65 mm under the track at (-54.93, 45.73). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -57.25..-53.22, y 43.4..47.43. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'PLL_CTRL.PLL_VADJ2_DAC2_SYNC_N' on L5 at (-54.93, 45.73), 0.65 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-57.25%2C43.4%7C-53.22%2C47.43 serves each with its own layer_image region; all of them lie in x -55.93..-53.93, y 44.4..47.05 mm (board frame, Y up).

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

    • gap:P6:hole -59.67,58.35|-53.23,58.812 nets cross one gap in P6's negative-plane field at 2 places, the longest 0.47 mm (fastest: FTMP.DXN at 100 ps 10-90 %, ASSUMED)

      Along 'FTMP.DXP' on L6, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.47 mm under the track at (-58.03, 58.72). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 2 places on 2 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -59.67..-53.23, y 58.35..58.81. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'FTMP.DXP' on L6 at (-58.03, 58.72), 0.47 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'FTMP.DXN' on L6 at (-53.98, 58.55), 0.46 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-59.67%2C58.35%7C-53.23%2C58.81 serves each with its own layer_image region; all of them lie in x -59.03..-52.98, y 57.35..59.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.

    • gap:P6:hole -59.67,58.35|-59.22,59.81'FTMP.DXP' crosses one gap in P6's negative-plane field at 1 place, the longest 0.47 mm (fastest: FTMP.DXP at 100 ps 10-90 %, ASSUMED)

      Along 'FTMP.DXP' on L6, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.47 mm under the track at (-59.31, 59.05). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -59.67..-59.22, y 58.35..59.81. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'FTMP.DXP' on L6 at (-59.31, 59.05), 0.47 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-59.67%2C58.35%7C-59.22%2C59.81 serves each with its own layer_image region; all of them lie in x -60.67..-58.22, y 58.05..60.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.

    • gap:P6:hole -59.67,59.35|-59.22,70.052 nets cross one gap in P6's negative-plane field at 2 places, the longest 0.48 mm (fastest: FTMP.DXN at 100 ps 10-90 %, ASSUMED)

      Along 'FTMP.DXN' on L6, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.48 mm under the track at (-59.27, 60.03). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 2 places on 2 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -59.67..-59.22, y 59.35..70.05. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'FTMP.DXN' on L6 at (-59.27, 60.03), 0.48 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'MGTAVTT_G10' on L6 at (-59.44, 62.03), 0.46 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-59.67%2C59.35%7C-59.22%2C70.05 serves each with its own layer_image region; all of them lie in x -60.67..-58.22, y 59.03..63.03 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.

    • gap:P6:hole -62.67,61.65|-62.22,63.81'PLL_CTRL.PLL_VADJ2_DAC1_SYNC_N' crosses one gap in P6's negative-plane field at 1 place, the longest 0.46 mm (fastest: PLL_CTRL.PLL_VADJ2_DAC1_SYNC_N at 100 ps 10-90 %, ASSUMED)

      Along 'PLL_CTRL.PLL_VADJ2_DAC1_SYNC_N' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.46 mm under the track at (-62.5, 62.13). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -62.67..-62.22, y 61.65..63.81. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'PLL_CTRL.PLL_VADJ2_DAC1_SYNC_N' on L5 at (-62.5, 62.13), 0.46 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-62.67%2C61.65%7C-62.22%2C63.81 serves each with its own layer_image region; all of them lie in x -63.67..-61.22, y 61.11..63.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.

    • gap:P6:hole -63.43,60.9|-62.22,62.11'FTMP.DXP' crosses one gap in P6's negative-plane field at 1 place, the longest 0.65 mm (fastest: FTMP.DXP at 100 ps 10-90 %, ASSUMED)

      Along 'FTMP.DXP' on L6, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.65 mm under the track at (-62.95, 61.38). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -63.43..-62.22, y 60.9..62.11. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'FTMP.DXP' on L6 at (-62.95, 61.38), 0.65 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-63.43%2C60.9%7C-62.22%2C62.11 serves each with its own layer_image region; all of them lie in x -63.95..-61.95, y 60.05..62.7 mm (board frame, Y up).

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

    • gap:P6:hole -63.67,63.35|-62.22,64.81'FTMP.DXP' crosses one gap in P6's negative-plane field at 1 place, the longest 0.65 mm (fastest: FTMP.DXP at 100 ps 10-90 %, ASSUMED)

      Along 'FTMP.DXP' on L6, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.65 mm under the track at (-62.95, 64.09). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -63.67..-62.22, y 63.35..64.81. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'FTMP.DXP' on L6 at (-62.95, 64.09), 0.65 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-63.67%2C63.35%7C-62.22%2C64.81 serves each with its own layer_image region; all of them lie in x -63.95..-61.95, y 62.77..65.41 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.

    • gap:P6:hole -65.25,71.75|-57.77,72.25'FDDR.D2' crosses one gap in P6's negative-plane field at 1 place, the longest 0.68 mm (fastest: FDDR.D2 at 100 ps 10-90 %, ASSUMED)

      Along 'FDDR.D2' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.68 mm under the track at (-64.18, 72.05). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -65.25..-57.77, y 71.75..72.25. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'FDDR.D2' on L5 at (-64.18, 72.05), 0.68 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-65.25%2C71.75%7C-57.77%2C72.25 serves each with its own layer_image region; all of them lie in x -65.38..-62.98, y 70.75..73.25 mm (board frame, Y up).

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

    • gap:P6:hole -65.79,39.29|-59.74,39.757 nets cross one gap in P6's negative-plane field at 7 places, the longest 0.65 mm (fastest: HA2.HA04_N at 100 ps 10-90 %, ASSUMED)

      Along 'HA2.HA04_N' on L6, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.65 mm under the track at (-62.53, 39.52). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 7 places on 7 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -65.79..-59.74, y 39.29..39.75. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'HA2.HA04_N' on L6 at (-62.53, 39.52), 0.65 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'HA2.HA04_P' on L6 at (-62.85, 39.52), 0.65 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'LA2.LA05_N' on L6 at (-64.2, 39.52), 0.65 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'LA2.LA05_P' on L6 at (-63.89, 39.52), 0.65 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'PLL_CTRL.PLL_VADJ2_DAC1_SYNC_N' on L5 at (-62.83, 39.52), 0.65 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'PLL_CTRL.PLL_VADJ2_DAC_DIN' on L5 at (-64.18, 39.52), 0.65 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'PLL_CTRL.PLL_VADJ2_DAC_SCLK' on L5 at (-61.45, 39.52), 0.65 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-65.79%2C39.29%7C-59.74%2C39.75 serves each with its own layer_image region; all of them lie in x -65.43..-60.22, y 38.29..40.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.

    • gap:P6:hole -66.12,69.75|-55.75,70.252 nets cross one gap in P6's negative-plane field at 2 places, the longest 4.17 mm (fastest: MGT113_CLK0_N at 1 ns 10-90 %, suggested by its name)

      Along 'MGT113_CLK0_P' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 4.17 mm under the track at (-56.9, 70.2). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 2 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 2.35 mm). 2 places on 2 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -66.12..-55.75, y 69.75..70.25. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'MGT113_CLK0_P' on L5 at (-56.9, 70.2), 4.17 mm, running ALONG the bare copper for 2.35 mm, not across it; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'MGT113_CLK0_N' on L5 at (-56.62, 69.98), 2.88 mm, running ALONG the bare copper for 1.69 mm, not across it; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-66.12%2C69.75%7C-55.75%2C70.25 serves each with its own layer_image region; all of them lie in x -60.44..-54.44, y 68.58..71.2 mm (board frame, Y up).

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

    • gap:P6:hole -66.17,39.29|-65.33,40.133 nets cross one gap in P6's negative-plane field at 3 places, the longest 0.62 mm (fastest: LA2.LA06_N at 100 ps 10-90 %, ASSUMED)

      Along 'LA2.LA06_N' on L6, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.62 mm under the track at (-65.5, 39.46). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 3 places on 3 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -66.17..-65.33, y 39.29..40.13. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'LA2.LA06_N' on L6 at (-65.5, 39.46), 0.62 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'LA2.LA06_P' on L6 at (-65.66, 39.62), 0.46 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'PLL_CTRL.VADJ2_SI57X_OE' on L5 at (-65.65, 39.61), 0.46 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-66.17%2C39.29%7C-65.33%2C40.13 serves each with its own layer_image region; all of them lie in x -66.82..-64.21, y 38.31..40.78 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.

    • gap:P6:hole -66.17,39.67|-65.71,42.76 nets cross one gap in P6's negative-plane field at 6 places, the longest 0.65 mm (fastest: LA2.LA00_CC_N at 100 ps 10-90 %, ASSUMED)

      Along 'LA2.LA00_CC_P' on L6, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.65 mm under the track at (-66.03, 42.11). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 6 places on 6 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -66.17..-65.71, y 39.67..42.7. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'LA2.LA00_CC_N' on L6 at (-65.94, 41.89), 0.65 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'LA2.LA00_CC_P' on L6 at (-66.03, 42.11), 0.65 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'LA2.LA01_CC_N' on L6 at (-65.94, 40.76), 0.65 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'LA2.LA01_CC_P' on L6 at (-65.94, 40.44), 0.65 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'PLL_CTRL.VADJ2_CLK_UPDATEN' on L5 at (-66.03, 42.11), 0.65 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'PLL_CTRL.VADJ2_SI57X_TUNE' on L5 at (-65.94, 40.73), 0.65 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-66.17%2C39.67%7C-65.71%2C42.7 serves each with its own layer_image region; all of them lie in x -67.17..-64.71, y 39.22..43.43 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.

    • gap:P6:hole -66.17,42.24|-65.71,48.312 nets cross one gap in P6's negative-plane field at 2 places, the longest 3.99 mm (fastest: PLL_CTRL.VADJ2_SI57X_SCL at 10 ns 10-90 %, suggested by its name)

      Along 'PLL_CTRL.VADJ2_SI57X_SDA' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 3.99 mm under the track at (-65.94, 46.57). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 3.18 mm). 2 places on 2 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -66.17..-65.71, y 42.24..48.31. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'PLL_CTRL.VADJ2_SI57X_SDA' on L5 at (-65.94, 46.57), 3.99 mm, running ALONG the bare copper for 3.18 mm, not across it; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'PLL_CTRL.VADJ2_SI57X_SCL' on L5 at (-65.94, 43.58), 0.65 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-66.17%2C42.24%7C-65.71%2C48.31 serves each with its own layer_image region; all of them lie in x -67.17..-64.71, y 42.36..49.41 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.

    • gap:P6:hole -67.25,71.75|-64.75,74.25'FDDR.D2' crosses one gap in P6's negative-plane field at 1 place, the longest 0.72 mm (fastest: FDDR.D2 at 100 ps 10-90 %, ASSUMED)

      Along 'FDDR.D2' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.72 mm under the track at (-66.15, 73.15). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -67.25..-64.75, y 71.75..74.25. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'FDDR.D2' on L5 at (-66.15, 73.15), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-67.25%2C71.75%7C-64.75%2C74.25 serves each with its own layer_image region; all of them lie in x -67.51..-64.79, y 72.15..74.15 mm (board frame, Y up).

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

    • gap:P6:hole -67.67,73.77|-67.22,82.924 nets cross one gap in P6's negative-plane field at 4 places, the longest 0.71 mm (fastest: HB1.HB15_N at 100 ps 10-90 %, ASSUMED)

      Along 'HB1.HB18_N' on L6, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.71 mm under the track at (-67.33, 79.56). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 4 places on 4 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -67.67..-67.22, y 73.77..82.92. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'HB1.HB18_N' on L6 at (-67.33, 79.56), 0.71 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'HB1.HB15_N' on L6 at (-67.37, 75.72), 0.68 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'HB1.HB18_P' on L6 at (-67.44, 79.35), 0.65 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'HB1.HB15_P' on L6 at (-67.53, 75.56), 0.63 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-67.67%2C73.77%7C-67.22%2C82.92 serves each with its own layer_image region; all of them lie in x -68.67..-66.22, y 74.27..80.97 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.

    • gap:P6:hole -68.42,69.75|-65.61,72.55'TXD_USBB' crosses one gap in P6's negative-plane field at 1 place, the longest 0.72 mm (fastest: TXD_USBB at 500 ps 10-90 %, suggested by its name)

      Along 'TXD_USBB' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.72 mm under the track at (-66.99, 71.13). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -68.42..-65.61, y 69.75..72.55. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'TXD_USBB' on L5 at (-66.99, 71.13), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-68.42%2C69.75%7C-65.61%2C72.55 serves each with its own layer_image region; all of them lie in x -68.35..-65.63, y 70.13..72.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.

    • gap:P6:hole -68.99,33.93|-66.78,36.147 nets cross one gap in P6's negative-plane field at 7 places, the longest 0.72 mm (fastest: HA2.HA04_N at 100 ps 10-90 %, ASSUMED)

      Along 'PLL_CTRL.PLL_VADJ2_DAC_SCLK' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.72 mm under the track at (-66.91, 34.07). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 7 places on 7 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -68.99..-66.78, y 33.93..36.14. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'PLL_CTRL.PLL_VADJ2_DAC_SCLK' on L5 at (-66.91, 34.07), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'HA2.HA04_N' on L6 at (-67.45, 34.61), 0.51 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'HA2.HA04_P' on L6 at (-67.61, 34.77), 0.51 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'LA2.LA05_N' on L6 at (-68.28, 35.44), 0.51 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'LA2.LA05_P' on L6 at (-68.12, 35.28), 0.51 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'PLL_CTRL.PLL_VADJ2_DAC1_SYNC_N' on L5 at (-67.6, 34.75), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'PLL_CTRL.PLL_VADJ2_DAC_DIN' on L5 at (-68.27, 35.43), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-68.99%2C33.93%7C-66.78%2C36.14 serves each with its own layer_image region; all of them lie in x -69.46..-65.78, y 32.69..36.62 mm (board frame, Y up).

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

    • gap:P6:hole -69.67,56.35|-67.22,56.81'VREF2.VREF_A_M2C' crosses one gap in P6's negative-plane field at 1 place, the longest 0.76 mm (fastest: VREF2.VREF_A_M2C at 100 ps 10-90 %, ASSUMED)

      Along 'VREF2.VREF_A_M2C' on L6, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.76 mm under the track at (-69.15, 56.43). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -69.67..-67.22, y 56.35..56.81. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'VREF2.VREF_A_M2C' on L6 at (-69.15, 56.43), 0.76 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-69.67%2C56.35%7C-67.22%2C56.81 serves each with its own layer_image region; all of them lie in x -70.5..-68.08, y 55.35..57.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.

    • gap:P6:hole -73.67,57.35|-72.22,58.81'VREF2.VREF_B_M2C' crosses one gap in P6's negative-plane field at 1 place, the longest 0.51 mm (fastest: VREF2.VREF_B_M2C at 100 ps 10-90 %, ASSUMED)

      Along 'VREF2.VREF_B_M2C' on L6, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.51 mm under the track at (-72.97, 58.32). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -73.67..-72.22, y 57.35..58.81. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'VREF2.VREF_B_M2C' on L6 at (-72.97, 58.32), 0.51 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-73.67%2C57.35%7C-72.22%2C58.81 serves each with its own layer_image region; all of them lie in x -74.13..-71.96, y 56.94..59.42 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.

    • gap:P6:hole -73.88,82.47|-67.22,89.139 nets cross one gap in P6's negative-plane field at 11 places, the longest 11 mm (fastest: HB1.HB10_N at 100 ps 10-90 %, ASSUMED)

      Along 'HB1.HB11_N' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 11 mm under the track at (-70.24, 85.39). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 10.35 mm). 11 places on 9 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -73.88..-67.22, y 82.47..89.13. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'HB1.HB11_N' on L5 at (-70.24, 85.39), 11 mm, running ALONG the bare copper for 10.35 mm, not across it; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'LA1.LA31_N' on L6 at (-70.83, 86.29), 1.11 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'HB1.HB10_N' on L6 at (-69.83, 85.22), 1.08 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'HB1.HB10_P' on L6 at (-70.05, 85.3), 0.65 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'HB1.HB15_P' on L6 at (-69.06, 84.31), 0.65 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'HB1.HB18_N' on L6 at (-67.83, 83.08), 0.65 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'HB1.HB18_P' on L6 at (-68.05, 83.3), 0.65 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'LA1.LA31_N' on L6 at (-73.18, 88.43), 0.65 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'LA1.LA31_P' on L6 at (-71.05, 86.3), 0.65 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'LA1.LA31_P' on L6 at (-72.95, 88.2), 0.65 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'HB1.HB15_N' on L6 at (-68.55, 83.89), 0.53 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-73.88%2C82.47%7C-67.22%2C89.13 serves each with its own layer_image region; all of them lie in x -76.15..-66.44, y 81.58..91.3 mm (board frame, Y up).

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

    • gap:P6:hole -74.13,60.9|-62.97,61.353 nets cross one gap in P6's negative-plane field at 3 places, the longest 6.15 mm (fastest: PLL_CTRL.PLL_VADJ2_DAC1_SYNC_N at 100 ps 10-90 %, ASSUMED)

      Along 'PLL_CTRL.VADJ2_SI57X_TUNE' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 6.15 mm under the track at (-65.95, 61.08). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 2 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 5.69 mm). 3 places on 3 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -74.13..-62.97, y 60.9..61.35. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'PLL_CTRL.VADJ2_SI57X_TUNE' on L5 at (-65.95, 61.08), 6.15 mm, running ALONG the bare copper for 5.69 mm, not across it; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'FPGA_RESET_DN' on L6 at (-71.94, 61.1), 4.74 mm, running ALONG the bare copper for 3.93 mm, not across it; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'PLL_CTRL.PLL_VADJ2_DAC1_SYNC_N' on L5 at (-69.77, 61.21), 0.6 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-74.13%2C60.9%7C-62.97%2C61.35 serves each with its own layer_image region; all of them lie in x -75.25..-62.04, y 59.9..62.35 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.

    • gap:P6:hole -74.7,58.67|-74.25,60.782 nets cross one gap in P6's negative-plane field at 2 places, the longest 0.46 mm (fastest: VREF2.VREF_A_M2C at 100 ps 10-90 %, ASSUMED)

      Along 'VREF2.VREF_A_M2C' on L6, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.46 mm under the track at (-74.48, 60.08). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 2 places on 2 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -74.7..-74.25, y 58.67..60.78. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'VREF2.VREF_A_M2C' on L6 at (-74.48, 60.08), 0.46 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'VREF2.VREF_B_M2C' on L6 at (-74.48, 59.08), 0.46 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-74.7%2C58.67%7C-74.25%2C60.78 serves each with its own layer_image region; all of them lie in x -75.7..-73.25, y 58.08..61.08 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.

    • gap:P6:hole -75.15,88.67|-73.42,90.42 nets cross one gap in P6's negative-plane field at 2 places, the longest 0.65 mm (fastest: HB1.HB10_N at 100 ps 10-90 %, ASSUMED)

      Along 'HB1.HB10_N' on L6, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.65 mm under the track at (-74.45, 89.7). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 2 places on 2 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -75.15..-73.42, y 88.67..90.4. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'HB1.HB10_N' on L6 at (-74.45, 89.7), 0.65 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'HB1.HB10_P' on L6 at (-74.23, 89.48), 0.65 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-75.15%2C88.67%7C-73.42%2C90.4 serves each with its own layer_image region; all of them lie in x -75.77..-72.9, y 88.48..90.7 mm (board frame, Y up).

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

    • gap:P6:hole -75.15,89.95|-74.7,94.558 nets cross one gap in P6's negative-plane field at 8 places, the longest 0.65 mm (fastest: FDDR.D2 at 100 ps 10-90 %, ASSUMED)

      Along 'FDDR.D2' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.65 mm under the track at (-74.93, 92.68). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 8 places on 8 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -75.15..-74.7, y 89.95..94.55. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'FDDR.D2' on L5 at (-74.93, 92.68), 0.65 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'HB1.HB15_N' on L6 at (-74.93, 90.95), 0.46 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'HB1.HB15_P' on L6 at (-74.93, 90.73), 0.46 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'HB1.HB17_CC_N' on L6 at (-74.93, 93.5), 0.46 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'HB1.HB17_CC_P' on L6 at (-74.93, 93.28), 0.46 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'HB1.HB18_N' on L6 at (-74.93, 92.23), 0.46 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'HB1.HB18_P' on L6 at (-74.93, 92), 0.46 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'HB1.HB20_P' on L6 at (-74.93, 94), 0.46 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-75.15%2C89.95%7C-74.7%2C94.55 serves each with its own layer_image region; all of them lie in x -76.15..-73.7, y 89.73..95 mm (board frame, Y up).

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

    • gap:P6:hole -75.37,94.1|-74.7,94.77'HB1.HB20_N' crosses one gap in P6's negative-plane field at 1 place, the longest 0.46 mm (fastest: HB1.HB20_N at 100 ps 10-90 %, ASSUMED)

      Along 'HB1.HB20_N' on L6, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.46 mm under the track at (-74.93, 94.23). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -75.37..-74.7, y 94.1..94.77. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'HB1.HB20_N' on L6 at (-74.93, 94.23), 0.46 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-75.37%2C94.1%7C-74.7%2C94.77 serves each with its own layer_image region; all of them lie in x -76.15..-73.7, y 93.23..95.23 mm (board frame, Y up).

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

    • gap:P6:hole -77.67,64.35|-63.22,64.813 nets cross one gap in P6's negative-plane field at 3 places, the longest 0.46 mm (fastest: M0 at 100 ps 10-90 %, ASSUMED)

      Along 'M0' on L6, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.46 mm under the track at (-76.05, 64.58). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 3 places on 3 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -77.67..-63.22, y 64.35..64.81. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'M0' on L6 at (-76.05, 64.58), 0.46 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'M1' on L6 at (-76.83, 64.58), 0.46 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'M2' on L6 at (-77.09, 64.58), 0.46 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-77.67%2C64.35%7C-63.22%2C64.81 serves each with its own layer_image region; all of them lie in x -78.09..-75.05, y 63.35..65.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.

    • gap:P6:hole -79.23,47.22|-78.77,63.25'TXD_USBB' crosses one gap in P6's negative-plane field at 1 place, the longest 4.56 mm (fastest: TXD_USBB at 500 ps 10-90 %, suggested by its name)

      Along 'TXD_USBB' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 4.56 mm under the track at (-78.95, 60.99). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 3.86 mm). What cleared it: the hole at x -79.23..-78.77, y 47.22..63.25. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'TXD_USBB' on L5 at (-78.95, 60.99), 4.56 mm, running ALONG the bare copper for 3.86 mm, not across it; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-79.23%2C47.22%7C-78.77%2C63.25 serves each with its own layer_image region; all of them lie in x -80.23..-77.95, y 58.03..64.4 mm (board frame, Y up).

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

    • gap:P6:hole -80.11,35.64|-68.48,36.1421 nets cross one gap in P6's negative-plane field at 21 places, the longest 0.72 mm (fastest: FLASH_D2 at 100 ps 10-90 %, ASSUMED)

      Along 'PLL_CTRL.VADJ2_SI57X_SDA' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.72 mm under the track at (-74.66, 35.89). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 21 places on 21 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -80.11..-68.48, y 35.64..36.14. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'FLASH_D2' on L5 at (-79.06, 35.89), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'FLASH_D3' on L5 at (-78.49, 35.89), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'FSPI.FCS_B\' on L5 at (-76.82, 35.89), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'FSPI.FLASH_SI/D0' on L5 at (-77.79, 35.89), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'HB2.HB00_CC_N' on L6 at (-76.46, 35.89), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'HB2.HB00_CC_P' on L6 at (-76.14, 35.89), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'HB2.HB10_N' on L6 at (-79.18, 35.89), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'HB2.HB10_P' on L6 at (-78.87, 35.89), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'HB2.HB11_N' on L6 at (-77.78, 35.89), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'HB2.HB11_P' on L6 at (-77.46, 35.89), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'LA2.LA00_CC_N' on L6 at (-71.93, 35.89), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'LA2.LA00_CC_P' on L6 at (-72.25, 35.89), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • and 9 more

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-80.11%2C35.64%7C-68.48%2C36.14 serves each with its own layer_image region; all of them lie in x -80.44..-67.82, y 34.64..37.14 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.

    • gap:P6:hole -83.31,46.05|-79.89,46.564 nets cross one gap in P6's negative-plane field at 4 places, the longest 0.58 mm (fastest: TXD_USBB at 500 ps 10-90 %, suggested by its name)

      Along 'MGT216_CLK0_P' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.58 mm under the track at (-82.62, 46.29). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 4 places on 4 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -83.31..-79.89, y 46.05..46.56. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'MGT216_CLK0_P' on L5 at (-82.62, 46.29), 0.58 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'MGT216_CLK1_P' on L6 at (-81.6, 46.2), 0.53 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'MGT216_CLK1_N' on L6 at (-81.78, 46.43), 0.52 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'TXD_USBB' on L5 at (-80.78, 46.3), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-83.31%2C46.05%7C-79.89%2C46.56 serves each with its own layer_image region; all of them lie in x -83.73..-79.78, y 45.05..47.56 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.

    All 121 in the full review

  41. ReferencePlaneDiscontinuityminorOpen

    ReferencePlaneDiscontinuity: 39 boards×39

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

    At gap:P3:hole -106.75,-26.2|-84.27,-3.72, gap:P3:hole -110.89,29.57|-106.35,34.1, gap:P3:hole -112.47,100.8|-96.92,101.25, gap:P3:hole -115.26,-26.2|-106.29,-25.75, gap:P3:hole -117.58,-26.2|-114.8,-23.42, gap:P3:hole -119.58,97.23|-115.56,101.25 and 33 more

    Each finding, with its own headline
    • gap:P3:hole -106.75,-26.2|-84.27,-3.722 nets cross one gap in P3's negative-plane field at 2 places, the longest 0.65 mm (fastest: PM.EN_P1V2 at 20 ns 10-90 %, suggested by its name)

      Along 'PM.EN_P1V8' on L2, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.65 mm under the track at (-85.27, -4.72). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 2 places on 2 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -106.75..-84.27, y -26.2..-3.72. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'PM.EN_P1V2' on L2 at (-85.93, -5.39), 0.65 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'PM.EN_P1V8' on L2 at (-85.27, -4.72), 0.65 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-106.75%2C-26.2%7C-84.27%2C-3.72 serves each with its own layer_image region; all of them lie in x -87.26..-83.95, y -6.39..-3.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.

    • gap:P3:hole -110.89,29.57|-106.35,34.12 nets cross one gap in P3's negative-plane field at 2 places, the longest 0.65 mm (fastest: MGT.PCIE_CLK1_N at 1 ns 10-90 %, suggested by its name)

      Along 'MGT.PCIE_CLK1_N' on L2, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.65 mm under the track at (-108.13, 32.33). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 2 places on 2 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -110.89..-106.35, y 29.57..34.1. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'MGT.PCIE_CLK1_N' on L2 at (-108.13, 32.33), 0.65 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'MGT.PCIE_CLK1_P' on L2 at (-108.36, 32.1), 0.65 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-110.89%2C29.57%7C-106.35%2C34.1 serves each with its own layer_image region; all of them lie in x -109.68..-106.81, y 31.1..33.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.

    • gap:P3:hole -112.47,100.8|-96.92,101.252 nets cross one gap in P3's negative-plane field at 2 places, the longest 0.65 mm (fastest: PROG_RXD at 3 ns 10-90 %, suggested by its name)

      Along 'PROG_TXD' on L2, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.65 mm under the track at (-111.72, 101.05). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 2 places on 2 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -112.47..-96.92, y 100.8..101.25. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'PROG_TXD' on L2 at (-111.72, 101.05), 0.65 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'PROG_RXD' on L2 at (-108.65, 101.03), 0.46 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-112.47%2C100.8%7C-96.92%2C101.25 serves each with its own layer_image region; all of them lie in x -112.98..-107.65, y 99.8..102.25 mm (board frame, Y up).

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

    • gap:P3:hole -115.26,-26.2|-106.29,-25.754 nets cross one gap in P3's negative-plane field at 4 places, the longest 3.68 mm (fastest: PM.1V5_VTT_EN at 20 ns 10-90 %, suggested by its name)

      Along 'PM.EN_P3V3' on L2, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 3.68 mm under the track at (-113.15, -25.8). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 1.97 mm). 4 places on 4 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -115.26..-106.29, y -26.2..-25.75. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'PM.EN_P3V3' on L2 at (-113.15, -25.8), 3.68 mm, running ALONG the bare copper for 1.97 mm, not across it; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'PM.1V5_VTT_EN' on L2 at (-110.81, -25.99), 0.65 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'PM.EN_FMC1_P3V3' on L2 at (-109.83, -25.98), 0.65 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'PM.EN_FMC2_P3V3' on L2 at (-108.53, -25.98), 0.65 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-115.26%2C-26.2%7C-106.29%2C-25.75 serves each with its own layer_image region; all of them lie in x -115.78..-107.3, y -27.2..-24.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.

    • gap:P3:hole -117.58,-26.2|-114.8,-23.424 nets cross one gap in P3's negative-plane field at 4 places, the longest 0.46 mm (fastest: PM.1V5_VTT_EN at 20 ns 10-90 %, suggested by its name)

      Along 'PM.1V5_VTT_EN' on L2, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.46 mm under the track at (-115.46, -25.56). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 4 places on 4 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -117.58..-114.8, y -26.2..-23.42. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'PM.1V5_VTT_EN' on L2 at (-115.46, -25.56), 0.46 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'PM.EN_FMC1_P3V3' on L2 at (-115.91, -25.02), 0.46 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'PM.EN_FMC2_P3V3' on L2 at (-116.61, -24.39), 0.46 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'PM.EN_P1V2' on L2 at (-116.87, -24.13), 0.46 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-117.58%2C-26.2%7C-114.8%2C-23.42 serves each with its own layer_image region; all of them lie in x -118.03..-114.25, y -26.7..-22.97 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.

    • gap:P3:hole -119.58,97.23|-115.56,101.252 nets cross one gap in P3's negative-plane field at 2 places, the longest 0.65 mm (fastest: PROG_RXD at 3 ns 10-90 %, suggested by its name)

      Along 'PROG_RXD' on L2, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.65 mm under the track at (-117.61, 99.2). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 2 places on 2 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -119.58..-115.56, y 97.23..101.25. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'PROG_RXD' on L2 at (-117.61, 99.2), 0.65 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'PROG_TXD' on L2 at (-116.44, 100.38), 0.65 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-119.58%2C97.23%7C-115.56%2C101.25 serves each with its own layer_image region; all of them lie in x -118.94..-115.12, y 98.2..101.38 mm (board frame, Y up).

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

    • gap:P3:hole -44.48,12.75|-43.97,29.262 nets cross one gap in P3's negative-plane field at 2 places, the longest 0.51 mm (fastest: PM.EN_P1V0 at 20 ns 10-90 %, suggested by its name)

      Along 'PM.PGOOD_P1V0' on L3, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.51 mm under the track at (-44.22, 22.13). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 2 places on 2 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -44.48..-43.97, y 12.75..29.26. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'PM.EN_P1V0' on L3 at (-44.22, 22.5), 0.51 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'PM.PGOOD_P1V0' on L3 at (-44.22, 22.13), 0.51 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-44.48%2C12.75%7C-43.97%2C29.26 serves each with its own layer_image region; all of them lie in x -45.48..-42.97, y 21.13..23.5 mm (board frame, Y up).

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

    • gap:P3:hole -85.37,36.02|-84.91,44.533 nets cross one gap in P3's negative-plane field at 3 places, the longest 0.65 mm (fastest: MGT.PCIE_CLK1_N at 1 ns 10-90 %, suggested by its name)

      Along 'MGT.PCIE_CLK1_N' on L2, P3 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.65 mm under the track at (-85.14, 36.66). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 3 places on 3 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -85.37..-84.91, y 36.02..44.53. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'MGT.PCIE_CLK1_N' on L2 at (-85.14, 36.66), 0.65 mm; other side: (negative-layer field) on G_1, 0.1 mm from the track against 0.11 mm to P3: 48% of the return on P3
      • 'RTM_SYNC_CLK_N' on L3 at (-85.22, 37.17), 0.49 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3
      • 'RTM_SYNC_CLK_P' on L3 at (-85.23, 37.41), 0.48 mm; other side: (negative-layer field) on P4, 0.11 mm from the track against 0.1 mm to P3: 52% of the return on P3

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP3%3Ahole%20-85.37%2C36.02%7C-84.91%2C44.53 serves each with its own layer_image region; all of them lie in x -86.37..-83.91, y 35.43..38.43 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.

    • gap:P4:hole -120.03,0.52|-104.15,1.033 nets cross one gap in P4's negative-plane field at 3 places, the longest 0.51 mm (fastest: TCLKA_FMC1_P at 1 ns 10-90 %, suggested by its name)

      Along 'TCLKA_FMC1_P' on L3, P4 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.51 mm under the track at (-118.09, 0.77). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 3 places on 3 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -120.03..-104.15, y 0.52..1.03. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'TCLKA_FMC1_P' on L3 at (-118.09, 0.77), 0.51 mm; other side: (negative-layer field) on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4
      • 'TCLKB_C_N' on L3 at (-119.2, 0.78), 0.51 mm; other side: (negative-layer field) on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4
      • 'TCLKB_C_P' on L3 at (-118.98, 0.78), 0.51 mm; other side: (negative-layer field) on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP4%3Ahole%20-120.03%2C0.52%7C-104.15%2C1.03 serves each with its own layer_image region; all of them lie in x -120.2..-117.09, y -0.48..2.03 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.

    • gap:P4:hole -123.08,12.2|-118,17.283 nets cross one gap in P4's negative-plane field at 3 places, the longest 0.65 mm (fastest: TCLKA_FMC1_P at 1 ns 10-90 %, suggested by its name)

      Along 'TCLKB_C_P' on L3, P4 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.65 mm under the track at (-118.98, 13.18). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 3 places on 3 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -123.08..-118, y 12.2..17.28. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'TCLKB_C_N' on L3 at (-119.2, 13.4), 0.65 mm; other side: (negative-layer field) on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4
      • 'TCLKB_C_P' on L3 at (-118.98, 13.18), 0.65 mm; other side: (negative-layer field) on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4
      • 'TCLKA_FMC1_P' on L3 at (-118.09, 12.43), 0.46 mm; other side: (negative-layer field) on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP4%3Ahole%20-123.08%2C12.2%7C-118%2C17.28 serves each with its own layer_image region; all of them lie in x -120.2..-117.09, y 11.2..14.73 mm (board frame, Y up).

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

    • gap:P4:hole -125.43,37.39|-124.92,87.075 nets cross one gap in P4's negative-plane field at 7 places, the longest 1.53 mm (fastest: RTM_PS# at 100 ps 10-90 %, ASSUMED)

      Along 'TCLKB_C_P' on L3, P4 is a negative layer (copper everywhere inside the profile), and its field is cleared for 1.53 mm under the track at (-124.98, 47.07). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 7 places on 5 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -125.43..-124.92, y 37.39..87.07. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'TCLKB_C_P' on L3 at (-124.98, 47.07), 1.53 mm; other side: (negative-layer field) on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4
      • 'RTM_PS#' on L3 at (-125.17, 79.37), 0.72 mm; other side: (negative-layer field) on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4
      • 'TCLKB_C_N' on L3 at (-125.01, 47.62), 0.68 mm; other side: (negative-layer field) on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4
      • 'TCLKA_FMC1_P' on L3 at (-125.25, 52.64), 0.66 mm; other side: (negative-layer field) on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4
      • 'TCLKA_FMC1_P' on L3 at (-124.97, 53.67), 0.62 mm; other side: (negative-layer field) on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4
      • 'TCLKA_FMC1_N' on L3 at (-125.39, 52.46), 0.54 mm; other side: (negative-layer field) on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4
      • 'TCLKA_FMC1_N' on L3 at (-124.97, 53.9), 0.54 mm; other side: (negative-layer field) on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP4%3Ahole%20-125.43%2C37.39%7C-124.92%2C87.07 serves each with its own layer_image region; all of them lie in x -126.43..-123.92, y 46..80.63 mm (board frame, Y up).

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

    • gap:P4:hole -16.43,90.3|-12.47,94.26'FPGA_CLK1_N' crosses one gap in P4's negative-plane field at 1 place, the longest 0.36 mm (fastest: FPGA_CLK1_N at 1 ns 10-90 %, suggested by its name)

      Along 'FPGA_CLK1_N' on L3, P4 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.36 mm under the track at (-15.77, 93.6). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. What cleared it: the hole at x -16.43..-12.47, y 90.3..94.26. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'FPGA_CLK1_N' on L3 at (-15.77, 93.6), 0.36 mm; other side: (negative-layer field) on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP4%3Ahole%20-16.43%2C90.3%7C-12.47%2C94.26 serves each with its own layer_image region; all of them lie in x -16.95..-14.59, y 92.6..94.6 mm (board frame, Y up).

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

    • gap:P4:hole -32.87,8.99|-32.61,34.162 nets cross one gap in P4's negative-plane field at 2 places, the longest 0.25 mm (fastest: PM.EN_P1V0 at 20 ns 10-90 %, suggested by its name)

      Along 'PM.EN_P1V0' on L3, P4 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.25 mm under the track at (-32.74, 22.5). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 2 places on 2 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -32.87..-32.61, y 8.99..34.16. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'PM.EN_P1V0' on L3 at (-32.74, 22.5), 0.25 mm; other side: (negative-layer field) on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4
      • 'PM.PGOOD_P1V0' on L3 at (-32.74, 22.13), 0.25 mm; other side: (negative-layer field) on P3, 0.1 mm from the track against 0.11 mm to P4: 48% of the return on P4

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP4%3Ahole%20-32.87%2C8.99%7C-32.61%2C34.16 serves each with its own layer_image region; all of them lie in x -33.87..-31.61, y 21.13..23.5 mm (board frame, Y up).

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

    • gap:P6:hole -120.03,-21.95|-100.92,-21.454 nets cross one gap in P6's negative-plane field at 4 places, the longest 0.72 mm (fastest: I_FMC1_PADJN at 100 ps 10-90 %, ASSUMED)

      Along 'I_FMC1_PADJN' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.72 mm under the track at (-102.12, -21.7). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 4 places on 4 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -120.03..-100.92, y -21.95..-21.45. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'I_FMC1_PADJN' on L5 at (-102.12, -21.7), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'I_FMC2_P3V3N' on L5 at (-104.35, -21.7), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'I_FMC2_PADJN' on L5 at (-101.32, -21.71), 0.69 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'VREF2.VREF_A_M2C' on L6 at (-116.55, -21.55), 0.53 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-120.03%2C-21.95%7C-100.92%2C-21.45 serves each with its own layer_image region; all of them lie in x -117.55..-100.08, y -22.95..-20.45 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.

    • gap:P6:hole -126.95,-15.04|-126.44,5.114 nets cross one gap in P6's negative-plane field at 4 places, the longest 0.51 mm (fastest: FCLKA_N at 1 ns 10-90 %, suggested by its name)

      Along 'FCLKA_N' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.51 mm under the track at (-126.7, -4.93). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 4 places on 4 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -126.95..-126.44, y -15.04..5.11. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'FCLKA_N' on L5 at (-126.7, -4.93), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'FCLKA_P' on L5 at (-126.7, -5.15), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'MGT.LINK01_CLK_N' on L5 at (-126.7, -1.99), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'MGT.LINK01_CLK_P' on L5 at (-126.7, -2.21), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-126.95%2C-15.04%7C-126.44%2C5.11 serves each with its own layer_image region; all of them lie in x -127.95..-125.44, y -6.15..-0.99 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.

    • gap:P6:hole -138.33,67.85|-137.87,914 nets cross one gap in P6's negative-plane field at 4 places, the longest 0.65 mm (fastest: MISC1.PG_M2C at 100 ps 10-90 %, ASSUMED)

      Along 'MISC1.PRSNT' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.65 mm under the track at (-138.1, 69.4). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 4 places on 4 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -138.33..-137.87, y 67.85..91. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'MISC1.PRSNT' on L5 at (-138.1, 69.4), 0.65 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'P3' on L5 at (-138.11, 72.57), 0.58 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'P2' on L5 at (-138.06, 71.39), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'MISC1.PG_M2C' on L5 at (-138.26, 70.45), 0.47 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-138.33%2C67.85%7C-137.87%2C91 serves each with its own layer_image region; all of them lie in x -139.33..-136.87, y 68.17..73.78 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.

    • gap:P6:hole -138.33,90.55|-132.85,96.035 nets cross one gap in P6's negative-plane field at 5 places, the longest 0.86 mm (fastest: MISC1.PG_M2C at 100 ps 10-90 %, ASSUMED)

      Along 'MISC1.PG_M2C' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.86 mm under the track at (-135.01, 93.73). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 5 places on 5 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -138.33..-132.85, y 90.55..96.03. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'MISC1.PG_M2C' on L5 at (-135.01, 93.73), 0.86 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'MISC2.PG_M2C' on L6 at (-136.72, 91.93), 0.75 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'PM.EN_FMC1_P12V' on L5 at (-133.11, 95.88), 0.64 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'MISC1.PRSNT' on L5 at (-134.42, 94.44), 0.58 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'FPGA_RESET_DN' on L6 at (-134.98, 93.9), 0.46 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-138.33%2C90.55%7C-132.85%2C96.03 serves each with its own layer_image region; all of them lie in x -138.36..-131.75, y 90.84..97.03 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.

    • gap:P6:hole -14.78,-9.5|0.23,-9.058 nets cross one gap in P6's negative-plane field at 8 places, the longest 0.48 mm (fastest: PORT0.RX0_N at 3 ns 10-90 %, suggested by its name)

      Along 'PORT1.RX1_P' on L6, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.48 mm under the track at (-5.72, -9.17). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 8 places on 8 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -14.78..0.23, y -9.5..-9.05. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'PORT1.RX1_P' on L6 at (-5.72, -9.17), 0.48 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'PORT1.RX1_N' on L6 at (-5.5, -9.2), 0.47 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'IPMB.SCL' on L5 at (-2.3, -9.28), 0.46 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'IPMB.SDA' on L5 at (-3.18, -9.28), 0.46 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'PORT0.RX0_N' on L6 at (-9.61, -9.28), 0.46 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'PORT0.RX0_P' on L6 at (-9.83, -9.28), 0.46 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'PORT0.TX0_N' on L6 at (-8.73, -9.28), 0.46 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'PORT0.TX0_P' on L6 at (-8.95, -9.28), 0.46 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-14.78%2C-9.5%7C0.23%2C-9.05 serves each with its own layer_image region; all of them lie in x -10.83..-1.3, y -10.5..-8.05 mm (board frame, Y up).

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

    • gap:P6:hole -150.38,6.48|-140.44,16.4214 nets cross one gap in P6's negative-plane field at 14 places, the longest 0.72 mm (fastest: MISC2.PG_M2C at 100 ps 10-90 %, ASSUMED)

      Along 'MISC2.PRSNT' on L6, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.72 mm under the track at (-147.68, 13.72). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 14 places on 14 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -150.38..-140.44, y 6.48..16.42. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'I2C_SI57.SCL' on L6 at (-144.75, 10.79), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'I2C_SI57.SDA' on L6 at (-143.73, 9.76), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'MISC2.PG_M2C' on L6 at (-149.55, 15.59), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'MISC2.PRSNT' on L6 at (-147.68, 13.72), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'PLL_CTRL.PLL_VADJ2_DAC2_SYNC_N' on L5 at (-141.34, 7.38), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'I2C_CPU.SCL' on L6 at (-146.29, 12.46), 0.58 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'PLL_CTRL.PLL_VADJ2_DAC_SCLK' on L5 at (-142.3, 8.1), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'PLL_CTRL.PLL_VADJ2_DAC1_SYNC_N' on L5 at (-143.26, 9.3), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'PLL_CTRL.PLL_VADJ2_DAC_DIN' on L5 at (-144.17, 10.21), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'PLL_CTRL.VADJ2_CLK_UPDATEN' on L5 at (-145.97, 12.01), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'PLL_CTRL.VADJ2_SI57X_OE' on L5 at (-144.62, 10.66), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'PLL_CTRL.VADJ2_SI57X_SCL' on L5 at (-146.8, 12.84), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • and 2 more

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-150.38%2C6.48%7C-140.44%2C16.42 serves each with its own layer_image region; all of them lie in x -150.55..-139.98, y 6.38..16.95 mm (board frame, Y up).

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

    • gap:P6:hole -41.73,17.7|-41.22,35.547 nets cross one gap in P6's negative-plane field at 7 places, the longest 0.72 mm (fastest: RXD_USBB at 500 ps 10-90 %, suggested by its name)

      Along 'I2C_CPU.SCL' on L6, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.72 mm under the track at (-41.48, 32.25). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 7 places on 7 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -41.73..-41.22, y 17.7..35.54. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'I2C_CPU.SCL' on L6 at (-41.48, 32.25), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'I2C_CPU.SDA' on L6 at (-41.48, 33.12), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'RXD_USBB' on L6 at (-41.48, 34.55), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'FCLKA_N' on L5 at (-41.48, 29.45), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'FCLKA_P' on L5 at (-41.48, 29.23), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'TCLKD_N' on L5 at (-41.48, 21.7), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'TCLKD_P' on L5 at (-41.48, 21.48), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-41.73%2C17.7%7C-41.22%2C35.54 serves each with its own layer_image region; all of them lie in x -42.73..-40.22, y 20.48..35.8 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.

    • gap:P6:hole -45.49,38.79|-44.98,61.4925 nets cross one gap in P6's negative-plane field at 25 places, the longest 2.5 mm (fastest: DP2.DP0_M2C_N at 100 ps 10-90 %, ASSUMED)

      Along 'TX213_1_P' on L6, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 2.5 mm under the track at (-45.45, 60.5). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 1.55 mm). 25 places on 25 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -45.49..-44.98, y 38.79..61.49. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'TX213_1_P' on L6 at (-45.45, 60.5), 2.5 mm, running ALONG the bare copper for 1.55 mm, not across it; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP1_C2M_N' on L6 at (-45.24, 46.92), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP1_C2M_P' on L6 at (-45.24, 46.6), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP2_C2M_N' on L6 at (-45.24, 48.34), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP2_C2M_P' on L6 at (-45.24, 48.02), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP2_M2C_N' on L6 at (-45.24, 41.08), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP2_M2C_P' on L6 at (-45.24, 40.76), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP3_C2M_N' on L6 at (-45.24, 49.77), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP3_C2M_P' on L6 at (-45.24, 49.46), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP3_M2C_N' on L6 at (-45.24, 42.56), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP3_M2C_P' on L6 at (-45.24, 42.25), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'GBT2.GBTCLK1_M2C_N' on L6 at (-45.24, 44.18), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • and 13 more

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-45.49%2C38.79%7C-44.98%2C61.49 serves each with its own layer_image region; all of them lie in x -46.49..-43.98, y 37.82..62.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.

    • gap:P6:hole -54.75,71.25|-26.75,71.753 nets cross one gap in P6's negative-plane field at 3 places, the longest 0.51 mm (fastest: I2C_CPU.SCL at 10 ns 10-90 %, suggested by its name)

      Along 'FPGA_ALERTN' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.51 mm under the track at (-29.03, 71.5). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 3 places on 3 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -54.75..-26.75, y 71.25..71.75. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'FPGA_ALERTN' on L5 at (-29.03, 71.5), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'I2C_CPU.SCL' on L5 at (-31.04, 71.5), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'I2C_CPU.SDA' on L5 at (-30.45, 71.5), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-54.75%2C71.25%7C-26.75%2C71.75 serves each with its own layer_image region; all of them lie in x -32.04..-28.03, y 70.25..72.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.

    • gap:P6:hole -63.04,-3.61|-41.22,18.213 nets cross one gap in P6's negative-plane field at 3 places, the longest 0.72 mm (fastest: I2C_CPU.SCL at 10 ns 10-90 %, suggested by its name)

      Along 'I2C_CPU.SDA' on L6, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.72 mm under the track at (-50.06, 9.37). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 3 places on 3 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -63.04..-41.22, y -3.61..18.21. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'I2C_CPU.SCL' on L6 at (-48.08, 11.36), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'I2C_CPU.SDA' on L6 at (-50.06, 9.37), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'PM.PGOOD_P1V0' on L6 at (-49.61, 9.83), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-63.04%2C-3.61%7C-41.22%2C18.21 serves each with its own layer_image region; all of them lie in x -51.06..-47.08, y 8.01..12.71 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.

    • gap:P6:hole -67.29,24.71|-66.78,34.4411 nets cross one gap in P6's negative-plane field at 15 places, the longest 1.07 mm (fastest: DP2.DP2_C2M_N at 100 ps 10-90 %, ASSUMED)

      Along 'DP2.DP3_C2M_N' on L6, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 1.07 mm under the track at (-67.09, 28.78). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 15 places on 11 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -67.29..-66.78, y 24.71..34.44. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'DP2.DP3_C2M_N' on L6 at (-67.09, 28.78), 1.07 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP2_C2M_N' on L6 at (-67.03, 26.54), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP2_C2M_P' on L6 at (-67.03, 26.23), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP3_C2M_P' on L6 at (-67.03, 29.03), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'MGT.LINK01_CLK_N' on L5 at (-67.03, 27.97), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'MGT.LINK01_CLK_P' on L5 at (-67.03, 27.65), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'MGT113_CLK0_N' on L5 at (-67.03, 26.57), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'MGT113_CLK0_P' on L5 at (-67.03, 26.25), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'MGT113_CLK1_N' on L5 at (-67.03, 31.09), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'MGT113_CLK1_P' on L5 at (-67.03, 30.78), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'PLL_CTRL.PLL_VADJ2_DAC2_SYNC_N' on L5 at (-67.03, 32.27), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'DP2.DP3_C2M_P' on L6 at (-66.97, 29.94), 0.69 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • and 3 more

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-67.29%2C24.71%7C-66.78%2C34.44 serves each with its own layer_image region; all of them lie in x -68.29..-65.78, y 24.97..33.52 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.

    • gap:P6:hole -73.67,64.35|-73.22,70.815 nets cross one gap in P6's negative-plane field at 5 places, the longest 0.46 mm (fastest: TXD_USBB at 500 ps 10-90 %, suggested by its name)

      Along 'CLKS1.CLK1_M2C_N' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.46 mm under the track at (-73.52, 67.2). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 5 places on 5 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -73.67..-73.22, y 64.35..70.81. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'CLKS1.CLK1_M2C_N' on L5 at (-73.52, 67.2), 0.46 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'CLKS1.CLK1_M2C_P' on L5 at (-73.52, 66.98), 0.46 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'CLKS1.CLK3_BIDIR_N' on L5 at (-73.44, 65.98), 0.46 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'CLKS1.CLK3_BIDIR_P' on L5 at (-73.44, 66.2), 0.46 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'TXD_USBB' on L5 at (-73.44, 65.15), 0.46 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-73.67%2C64.35%7C-73.22%2C70.81 serves each with its own layer_image region; all of them lie in x -74.67..-72.22, y 64.15..68.24 mm (board frame, Y up).

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

    • gap:P6:hole -73.67,70.35|-71.8,72.234 nets cross one gap in P6's negative-plane field at 4 places, the longest 0.65 mm (fastest: CLKS1.CLK1_M2C_N at 1 ns 10-90 %, suggested by its name)

      Along 'CLKS1.CLK1_M2C_P' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.65 mm under the track at (-72.83, 71.2). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 4 places on 4 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -73.67..-71.8, y 70.35..72.23. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'CLKS1.CLK1_M2C_N' on L5 at (-73.05, 70.98), 0.65 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'CLKS1.CLK1_M2C_P' on L5 at (-72.83, 71.2), 0.65 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'CLKS1.CLK3_BIDIR_P' on L5 at (-72.08, 71.93), 0.6 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'CLKS1.CLK3_BIDIR_N' on L5 at (-71.85, 72), 0.46 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-73.67%2C70.35%7C-71.8%2C72.23 serves each with its own layer_image region; all of them lie in x -74.05..-70.85, y 69.65..73.23 mm (board frame, Y up).

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

    • gap:P6:hole -73.75,73.75|-66.75,74.257 nets cross one gap in P6's negative-plane field at 7 places, the longest 4.93 mm (fastest: FDDR.D2 at 100 ps 10-90 %, ASSUMED)

      Along 'FSPI.INIT_B' on L6, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 4.93 mm under the track at (-71.25, 74.09). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 3.83 mm). 7 places on 7 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -73.75..-66.75, y 73.75..74.25. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'FSPI.INIT_B' on L6 at (-71.25, 74.09), 4.93 mm, running ALONG the bare copper for 3.83 mm, not across it; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'HB1.HB03_N' on L5 at (-67.78, 74.15), 0.78 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'FDDR.D2' on L5 at (-66.94, 74), 0.66 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'CLKS1.CLK1_M2C_N' on L5 at (-73.05, 74), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'CLKS1.CLK1_M2C_P' on L5 at (-72.83, 74), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'CLKS1.CLK3_BIDIR_N' on L5 at (-71.85, 74), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'CLKS1.CLK3_BIDIR_P' on L5 at (-72.08, 74), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-73.75%2C73.75%7C-66.75%2C74.25 serves each with its own layer_image region; all of them lie in x -74.7..-65.94, y 72.58..75.25 mm (board frame, Y up).

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

    • gap:P6:hole -77.7,64.33|-77.19,70.316 nets cross one gap in P6's negative-plane field at 6 places, the longest 0.51 mm (fastest: TXD_USBB at 500 ps 10-90 %, suggested by its name)

      Along 'CLKS1.CLK3_BIDIR_P' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.51 mm under the track at (-77.44, 66.2). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 6 places on 6 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -77.7..-77.19, y 64.33..70.31. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'CLKS1.CLK1_M2C_N' on L5 at (-77.44, 67.2), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'CLKS1.CLK1_M2C_P' on L5 at (-77.44, 66.98), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'CLKS1.CLK3_BIDIR_N' on L5 at (-77.44, 65.98), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'CLKS1.CLK3_BIDIR_P' on L5 at (-77.44, 66.2), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'FSPI.PROGRAM_B' on L5 at (-77.44, 69.05), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'TXD_USBB' on L5 at (-77.44, 65.15), 0.51 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-77.7%2C64.33%7C-77.19%2C70.31 serves each with its own layer_image region; all of them lie in x -78.7..-76.19, y 64.15..70.05 mm (board frame, Y up).

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

    • gap:P6:hole -77.7,69.8|-73.25,74.255 nets cross one gap in P6's negative-plane field at 6 places, the longest 1.68 mm (fastest: CFGBVS_0 at 100 ps 10-90 %, ASSUMED)

      Along 'FSPI.DONE' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 1.68 mm under the track at (-74.98, 72.42). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 6 places on 5 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -77.7..-73.25, y 69.8..74.25. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'FSPI.DONE' on L5 at (-74.98, 72.42), 1.68 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'M0' on L6 at (-76.05, 71.45), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'M1' on L6 at (-76.83, 70.68), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'M2' on L6 at (-77.09, 70.41), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'FSPI.DONE' on L5 at (-77.37, 70.1), 0.65 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'CFGBVS_0' on L6 at (-75.69, 71.92), 0.61 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-77.7%2C69.8%7C-73.25%2C74.25 serves each with its own layer_image region; all of them lie in x -78.69..-73.05, y 69.05..74.1 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.

    • gap:P6:hole -80.35,-14.38|-33.67,-13.923 nets cross one gap in P6's negative-plane field at 3 places, the longest 0.65 mm (fastest: I2C_CPU.SCL at 10 ns 10-90 %, suggested by its name)

      Along 'FPGA_ALERTN' on L6, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.65 mm under the track at (-39.83, -14.15). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 3 places on 3 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -80.35..-33.67, y -14.38..-13.92. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 48% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'FPGA_ALERTN' on L6 at (-39.83, -14.15), 0.65 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'I2C_CPU.SCL' on L6 at (-48.5, -14.15), 0.46 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'I2C_CPU.SDA' on L6 at (-48.9, -14.15), 0.46 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-80.35%2C-14.38%7C-33.67%2C-13.92 serves each with its own layer_image region; all of them lie in x -49.9..-38.6, y -15.38..-12.92 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.

    • gap:P6:hole -85.57,19.48|-72.01,19.9918 nets cross one gap in P6's negative-plane field at 20 places, the longest 0.72 mm (fastest: DP2.DP2_C2M_N at 100 ps 10-90 %, ASSUMED)

      Along 'DP2.DP3_C2M_N' on L6, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.72 mm under the track at (-76.93, 19.74). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 20 places on 18 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -85.57..-72.01, y 19.48..19.99. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'DP2.DP3_C2M_N' on L6 at (-76.93, 19.74), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP2_C2M_N' on L6 at (-73.84, 19.74), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP2_C2M_P' on L6 at (-73.52, 19.74), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'HA2.HA04_N' on L6 at (-82.32, 19.74), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'HA2.HA04_P' on L6 at (-82.64, 19.74), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'LA2.LA05_N' on L6 at (-83.99, 19.74), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'LA2.LA05_P' on L6 at (-83.67, 19.74), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'MGT.LINK01_CLK_N' on L5 at (-75.26, 19.74), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'MGT.LINK01_CLK_P' on L5 at (-74.95, 19.74), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'MGT113_CLK0_N' on L5 at (-73.86, 19.74), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'MGT113_CLK0_P' on L5 at (-73.55, 19.74), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'MGT113_CLK1_N' on L5 at (-78.39, 19.74), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • and 8 more

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-85.57%2C19.48%7C-72.01%2C19.99 serves each with its own layer_image region; all of them lie in x -85.24..-72.27, y 18.48..20.99 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.

    • gap:P6:hole -88.01,50.75|-87.5,68.7816 nets cross one gap in P6's negative-plane field at 16 places, the longest 0.81 mm (fastest: CLKS1.CLK1_M2C_N at 1 ns 10-90 %, suggested by its name)

      Along 'TX116_3_N' on L6, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.81 mm under the track at (-87.65, 65.9). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 16 places on 16 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -88.01..-87.5, y 50.75..68.78. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'TX116_3_N' on L6 at (-87.65, 65.9), 0.81 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'RX116_2_N' on L6 at (-87.59, 54.3), 0.79 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'CLKS1.CLK3_BIDIR_N' on L5 at (-87.68, 64.79), 0.77 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'RX116_2_P' on L6 at (-87.8, 53.71), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'TX116_3_P' on L6 at (-87.74, 66.13), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'CLKS1.CLK1_M2C_N' on L5 at (-87.76, 66.09), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'CLKS1.CLK1_M2C_P' on L5 at (-87.76, 65.77), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'CLKS1.CLK3_BIDIR_P' on L5 at (-87.76, 65.04), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'FSPI.FPGA_CCLK' on L5 at (-87.76, 67.04), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'FSPI.PROGRAM_B' on L5 at (-87.76, 67.77), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'RX216_3_N' on L6 at (-87.76, 51.47), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'TX216_3_N' on L5 at (-87.76, 53.89), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • and 4 more

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-88.01%2C50.75%7C-87.5%2C68.78 serves each with its own layer_image region; all of them lie in x -89.01..-86.5, y 49.91..69.02 mm (board frame, Y up).

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

    • gap:P6:hole -88.21,-3.61|-73.97,10.6426 nets cross one gap in P6's negative-plane field at 26 places, the longest 0.51 mm (fastest: DP2.DP0_C2M_N at 100 ps 10-90 %, ASSUMED)

      Along 'MGT.LINK01_CLK_P' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.51 mm under the track at (-86.13, 8.56). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 26 places on 26 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -88.21..-73.97, y -3.61..10.64. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'DP2.DP0_C2M_N' on L6 at (-77.65, 0.07), 0.51 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP0_C2M_P' on L6 at (-77.49, -0.09), 0.51 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP0_M2C_N' on L6 at (-81.04, 3.47), 0.51 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP0_M2C_P' on L6 at (-80.88, 3.31), 0.51 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP1_C2M_N' on L6 at (-84.86, 7.29), 0.51 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP1_C2M_P' on L6 at (-84.7, 7.13), 0.51 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP1_M2C_N' on L6 at (-79.43, 1.86), 0.51 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP1_M2C_P' on L6 at (-79.27, 1.7), 0.51 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP2_M2C_N' on L6 at (-81.94, 4.37), 0.51 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP2_M2C_P' on L6 at (-81.78, 4.21), 0.51 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP3_M2C_N' on L6 at (-82.69, 5.11), 0.51 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP3_M2C_P' on L6 at (-82.53, 4.96), 0.51 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • and 14 more

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-88.21%2C-3.61%7C-73.97%2C10.64 serves each with its own layer_image region; all of them lie in x -88.87..-75.62, y -1.95..11.3 mm (board frame, Y up).

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

    • gap:P6:hole -89.71,68.28|-87.5,70.498 nets cross one gap in P6's negative-plane field at 8 places, the longest 0.94 mm (fastest: LA1.LA00_CC_N at 100 ps 10-90 %, ASSUMED)

      Along 'RX116_0_N' on L6, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.94 mm under the track at (-89.1, 70.03). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 8 places on 8 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -89.71..-87.5, y 68.28..70.49. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RX116_0_N' on L6 at (-89.1, 70.03), 0.94 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'LA1.LA02_N' on L5 at (-88.94, 69.71), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'LA1.LA02_P' on L5 at (-88.72, 69.49), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'FSPI.DONE' on L5 at (-87.66, 68.44), 0.71 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'LA1.LA00_CC_N' on L5 at (-88.13, 68.95), 0.69 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'LA1.LA00_CC_P' on L5 at (-87.9, 68.79), 0.65 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'MGT116_CLK1_N' on L6 at (-88.08, 68.85), 0.51 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'MGT116_CLK1_P' on L6 at (-88.24, 69.01), 0.51 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-89.71%2C68.28%7C-87.5%2C70.49 serves each with its own layer_image region; all of them lie in x -90.83..-86.51, y 67.09..71.07 mm (board frame, Y up).

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

    • gap:P6:hole -95.99,35.64|-79.6,52.0232 nets cross one gap in P6's negative-plane field at 32 places, the longest 0.72 mm (fastest: HB2.HB01_N at 100 ps 10-90 %, ASSUMED)

      Along 'TX216_0_P' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.72 mm under the track at (-85.74, 41.77). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 32 places on 32 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -95.99..-79.6, y 35.64..52.02. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'RX216_0_N' on L6 at (-84.85, 40.88), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'RX216_0_P' on L6 at (-84.63, 40.66), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'RX216_1_N' on L6 at (-87.03, 43.07), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'RX216_1_P' on L6 at (-86.79, 42.82), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'RX216_2_N' on L6 at (-89.64, 45.67), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'RX216_2_P' on L6 at (-89.41, 45.45), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'TX216_0_N' on L5 at (-85.51, 41.54), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'TX216_0_P' on L5 at (-85.74, 41.77), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'TX216_1_N' on L5 at (-88.34, 44.37), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'TX216_1_P' on L5 at (-88.12, 44.15), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'TX116_3_P' on L6 at (-94.39, 50.31), 0.7 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'FPGA_RESET_DN' on L6 at (-82.88, 38.97), 0.68 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • and 20 more

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-95.99%2C35.64%7C-79.6%2C52.02 serves each with its own layer_image region; all of them lie in x -96.85..-78.89, y 34.92..52.65 mm (board frame, Y up).

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

    • gap:P6:hole -95.99,51.51|-95.48,69.4216 nets cross one gap in P6's negative-plane field at 16 places, the longest 0.93 mm (fastest: LA1.LA00_CC_N at 100 ps 10-90 %, ASSUMED)

      Along 'LA1.LA01_CC_P' on L5, P6 is a negative layer (copper everywhere inside the profile), and its field is cleared for 0.93 mm under the track at (-95.79, 65.29). The layer does not state the nets either side, so whether this is a split between two planes or a void in one is not said; either way the return current has to go round it. 16 places on 16 net(s) cross it, listed below, the longest first. What cleared it: the hole at x -95.99..-95.48, y 51.51..69.42. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'LA1.LA01_CC_P' on L5 at (-95.79, 65.29), 0.93 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'LA1.LA01_CC_N' on L5 at (-95.65, 65.92), 0.9 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'FSPI.DONE' on L5 at (-95.73, 59.31), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'FSPI.PROGRAM_B' on L5 at (-95.73, 58.24), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'LA1.LA00_CC_N' on L5 at (-95.73, 61.51), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'LA1.LA00_CC_P' on L5 at (-95.73, 61.19), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'LA1.LA02_N' on L5 at (-95.73, 63.19), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'LA1.LA02_P' on L5 at (-95.73, 62.87), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'LA1.LA06_N' on L5 at (-95.73, 66.14), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'LA1.LA06_P' on L5 at (-95.73, 66.46), 0.72 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • 'MGT116_CLK0_P' on L6 at (-95.73, 68.38), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'FSPI.FPGA_CCLK' on L5 at (-95.67, 52.57), 0.52 mm; other side: (negative-layer field) on GND, 0.11 mm from the track against 0.1 mm to P6: 52% of the return on P6
      • and 4 more

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=gap%3AP6%3Ahole%20-95.99%2C51.51%7C-95.48%2C69.42 serves each with its own layer_image region; all of them lie in x -96.99..-94.46, y 51.53..69.63 mm (board frame, Y up).

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

    • refchange:(negative-layer field)|P1V23 nets change reference between (negative-layer field) and P1V2 at 3 vias, none with a reference that continues across (fastest: FTMP.DXN at 100 ps 10-90 %, ASSUMED)

      At 3 via(s), on 3 net(s), the signal leaves a layer referenced by one of (negative-layer field) and P1V2 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: 3 served. Every site is served, so the finding is the lower tier (info). 3 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 (negative-layer field) and P1V2 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.

      • 'FTMP.DXP' at (-51.1, 52.58), L6 -> BTM: P1V2 on P6, (negative-layer field) on G_2 to (negative-layer field) on G_2; pure, no reference continues across; stitching served, 13.9 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. (negative-layer field) on G_2 is 0.100 mm from GND on L6 and P1V2 on P6 0.100 mm from GND on L5: their own capacitance carries the return. Served.
      • 'FTMP.DXN' at (-49.02, 52.45), L6 -> BTM: P1V2 on P6, (negative-layer field) on G_2 to (negative-layer field) on G_2; pure, no reference continues across; stitching served, 10.5 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. (negative-layer field) on G_2 is 0.100 mm from GND on L6 and P1V2 on P6 0.100 mm from GND on L5: their own capacitance carries the return. Served.
      • 'PM.PGOOD_P1V0' at (-48.82, 16.85), L6 -> BTM: P1V2 on P6, (negative-layer field) on G_2 to (negative-layer field) on G_2; pure, no reference continues across; stitching served, 0.9 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (20 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. (negative-layer field) on G_2 is 0.100 mm from GND on L6 and P1V2 on P6 0.100 mm from GND on L5: their own capacitance carries the return. Served.

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=refchange%3A%28negative-layer%20field%29%7CP1V2 serves each with its own layer_image region; all of them lie in x -53.1..-46.82, y 14.85..54.58 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:(negative-layer field)|P1V563 nets change reference between (negative-layer field) and P1V5 at 121 vias, none with a reference that continues across (fastest: CFGBVS_0 at 100 ps 10-90 %, ASSUMED)

      At 121 via(s), on 63 net(s), the signal leaves a layer referenced by one of (negative-layer field) and P1V5 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: 121 served. Every site is served, so the finding is the lower tier (info). 121 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 (negative-layer field) and P1V5 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.

      • 'LED_R' at (-176.82, 47.7), L6 -> BTM: P1V5 on P6, (negative-layer field) on G_2 to (negative-layer field) on G_2; pure, no reference continues across; stitching served, 61.3 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. (negative-layer field) on G_2 is 0.100 mm from GND on L6 and P1V5 on P6 0.100 mm from GND on L5: their own capacitance carries the return. Served.
      • 'LED_R' at (-174.5, 97.95), L6 -> BTM: P1V5 on P6, (negative-layer field) on G_2 to (negative-layer field) on G_2; pure, no reference continues across; stitching served, 61.3 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. (negative-layer field) on G_2 is 0.100 mm from GND on L6 and P1V5 on P6 0.100 mm from GND on L5: their own capacitance carries the return. Served.
      • 'LED_R' at (-154.7, 94.75), L6 -> BTM: P1V5 on P6, (negative-layer field) on G_2 to (negative-layer field) on G_2; pure, no reference continues across; stitching served, 61.3 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. (negative-layer field) on G_2 is 0.100 mm from GND on L6 and P1V5 on P6 0.100 mm from GND on L5: their own capacitance carries the return. Served.
      • 'LED_G' at (-176.35, 46.58), L6 -> BTM: P1V5 on P6, (negative-layer field) on G_2 to (negative-layer field) on G_2; pure, no reference continues across; stitching served, 58.4 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. (negative-layer field) on G_2 is 0.100 mm from GND on L6 and P1V5 on P6 0.100 mm from GND on L5: their own capacitance carries the return. Served.
      • 'LED_G' at (-173.25, 97.68), L6 -> BTM: P1V5 on P6, (negative-layer field) on G_2 to (negative-layer field) on G_2; pure, no reference continues across; stitching served, 58.4 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. (negative-layer field) on G_2 is 0.100 mm from GND on L6 and P1V5 on P6 0.100 mm from GND on L5: their own capacitance carries the return. Served.
      • 'LED_G' at (-153.52, 95.45), L6 -> BTM: P1V5 on P6, (negative-layer field) on G_2 to (negative-layer field) on G_2; pure, no reference continues across; stitching served, 58.4 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. (negative-layer field) on G_2 is 0.100 mm from GND on L6 and P1V5 on P6 0.100 mm from GND on L5: their own capacitance carries the return. Served.
      • 'RST' at (-155.85, 43.08), L6 -> BTM: P1V5 on P6, (negative-layer field) on G_2 to (negative-layer field) on G_2; pure, no reference continues across; stitching served, 53.5 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (20 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. (negative-layer field) on G_2 is 0.100 mm from GND on L6 and P1V5 on P6 0.100 mm from GND on L5: their own capacitance carries the return. Served.
      • 'LED_B' at (-172.32, 98.03), L6 -> BTM: P1V5 on P6, (negative-layer field) on G_2 to (negative-layer field) on G_2; pure, no reference continues across; stitching served, 40.6 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. (negative-layer field) on G_2 is 0.100 mm from GND on L6 and P1V5 on P6 0.100 mm from GND on L5: their own capacitance carries the return. Served.
      • 'LED_B' at (-155.53, 96.58), L6 -> BTM: P1V5 on P6, (negative-layer field) on G_2 to (negative-layer field) on G_2; pure, no reference continues across; stitching served, 40.6 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. (negative-layer field) on G_2 is 0.100 mm from GND on L6 and P1V5 on P6 0.100 mm from GND on L5: their own capacitance carries the return. Served.
      • 'PDI_DATA' at (-156.58, 49.9), L6 -> BTM: P1V5 on P6, (negative-layer field) on G_2 to (negative-layer field) on G_2; pure, no reference continues across; stitching served, 33.6 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. (negative-layer field) on G_2 is 0.100 mm from GND on L6 and P1V5 on P6 0.100 mm from GND on L5: their own capacitance carries the return. Served.
      • 'TDI' at (-157.5, 47), L6 -> BTM: P1V5 on P6, (negative-layer field) on G_2 to (negative-layer field) on G_2; pure, no reference continues across; stitching served, 32.6 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (2 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. (negative-layer field) on G_2 is 0.100 mm from GND on L6 and P1V5 on P6 0.100 mm from GND on L5: their own capacitance carries the return. Served.
      • 'I2C1.SCL' at (-124.3, 99.6), L6 -> BTM: P1V5 on P6, (negative-layer field) on G_2 to (negative-layer field) on G_2; pure, no reference continues across; stitching served, 32.5 mm of track past the via on BTM: At the 5 GHz knee of a 100 ps edge (10 ns 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. (negative-layer field) on G_2 is 0.100 mm from GND on L6 and P1V5 on P6 0.100 mm from GND on L5: their own capacitance carries the return. Served.
      • and 109 more

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/24/reference-planes?group=refchange%3A%28negative-layer%20field%29%7CP1V5 serves each with its own layer_image region; all of them lie in x -178.82..-3.34, y -30.25..110.3 mm (board frame, Y up).

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

    • split@P6:P1V2|P1V832 nets cross the split between the P1V2 and P1V8 planes on P6 at 62 places, all with a plane on the track's other side (fastest: DP2.DP0_C2M_N at 100 ps 10-90 %, ASSUMED)

      On P6 the P1V2 and P1V8 planes part, and 32 nets cross from one to the other at 62 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 62 of the 62 crossing(s) the track's other neighbour carries a plane, which the return can use there. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 52% of the return meets the break and the rest follows the track on that plane (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The finding is the lower tier (info).

      • 'DP2.DP0_C2M_N' on L6 at (-72.83, 4.89), 0.51 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP0_C2M_N' on L6 at (-52.07, 25.65), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP0_C2M_P' on L6 at (-72.67, 4.73), 0.51 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP0_C2M_P' on L6 at (-52.07, 25.33), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP0_M2C_N' on L6 at (-56.79, 27.71), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP0_M2C_N' on L6 at (-52.07, 32.44), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP0_M2C_P' on L6 at (-56.79, 27.4), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP0_M2C_P' on L6 at (-52.07, 32.12), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP1_C2M_N' on L6 at (-56.79, 35.36), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP1_C2M_N' on L6 at (-52.07, 40.09), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP1_C2M_P' on L6 at (-56.79, 35.04), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • 'DP2.DP1_C2M_P' on L6 at (-52.07, 39.77), 0.72 mm; other side: (negative-layer field) on G_2, 0.1 mm from the track against 0.11 mm to P6: 48% of the return on P6
      • and 50 more

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

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

Main parts

Part numberMakerDescriptionWhere
10-280MHzAny-Rate I2C Programmable XO Oscillator Si570 SerieOSC4
74HC4053DIC73
AD8402ARZ11k dual digital potentiometerIC11
ADN4604ASVZ16x16 CML crosspoint switchIC8
AT24MAC602-XHM-TSerial 2K EEPROM+ 48bit MACIC27
ATS-50350B-C2-R0Heat sink BGA 35x35(44.9)mmHS1
BLUELED Blue Avago C120LDy
CDCM61004RHBTFour Output, Integrated VCO, Low-Jitter Clock GeneratorIC50
FamilySingle Pin FemaleJ12
goldpin 1.27 2x5PBTD10SJP2
GREENLED Green Avago C120LDx
LD1117DT33CTR3-Terminal Regulator 1=GND 2=IN 3=OUTIC74
LP5951MF-3.0/NOPB150mA Micropower Low-Dropout CMOS Voltage RegulatorIC51
LPC1764FBD100ARM Cortex-M3 procesorIC1
MAX6642ATT90±1°C, SMBus- Remote/Local Temperature Sensor with Overtemperature AlarmIC18
MCP79410-I/SNRTC with 1k EEPROM and RAMIC9
Milli-Grid™Connector 14 MaleJ6
Mini-Fit Jr.™Connector 4 MaleJ4
PCA9517DGKLEVEL-TRANSLATING I2C BUS REPEATERIC42
PCA9547BS8-channel I2C-bus multiplexer with resetIC79
PLTD10SGoldpin 2.54mm, male headerJP1
PT7M7811 or STM811SWvoltage supervisorIC58
Push ButtonPush-Button Switch SPDTPB1
Q0M032D6-SMDCrystal oscillator 32k (Maritex)X3
QSDG8M000-TXCminiature crystal oscillator (Maritex) QSDG8M000-TXCX1
Red/Green/BlueRight Angle Tricolor (RGB) Surface Mount LED, Body 3.2x1mmLD1
RFSM250 or MF-SM250-2-992.50A/15VF3
SCANSTA111MTEnhanced SCAN Bridge Multidrop Addressable IEEE 1149.1 (JTAG) PortIC6
SR60 batterySR60 6.8x2.15mm Battery 1.5V, 15mAhBAT1
SR60 Keystone 2998SR60 Battery 1.5V 17mAh (Farnell: 1854967)BH1
STM809SWX6F2.93V Reset circuitIC3
TACTR75H84B160Push buttonS1
TL431QDBZT2.5V ADJ Voltage referenceIC54
TPS51200DRCTSink/Source DDR Termination RegulatorIC44
TPS53353DQPTHigh-Efficiency 20-A Synchronous Buck Converter with Eco-mode™IC14
TS34312.5V ADJ Voltage referenceIC45
XC7A200T-3FFG1156CArtix-6 FPGA, 16 GTPs, 600 User I/Os, 1156-Pin BGA, Speed Grade 2, Commercial Grade, Pb-FreeIC2
67800-5005SATA conenctor PCB MolexJ13, J14
AD5662BRMZ-12.7V to 5.5V, 250uA, Rail-to-Rail Output 16-Bit nanoDACIC52, IC53
Advanced TCAConnector 60 ATCA Female 30 Pairs (60 Signals) + 3x10 GroundJ1, J2

About this design

Design
AFC — OHWR0021 R1
Designed in
Altium Designer
Board
14 copper layers, 180.7 × 148.6 mm, 1515 components, 1340 nets
Licence
CERN-OHL-1.1
Source
https://gitlab.com/ohwr/project/afc at commit c77f55bea83c
Attribution
CERN Open Hardware Repository, project ohwr/project/afc (commit c77f55bea83cea9ddc09ee9142b59e9974ea33b0, 2025-04-10). Licence: CERN-OHL-1.1. Source: https://gitlab.com/ohwr/project/afc. 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)