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

WREN PATCH PANEL

OHWR0094 · revision R2

WREN PATCH PANEL (OHWR0094 R2) is an open-hardware circuit board from its public repository, designed in KiCad EDA: a 4-layer board of 430 × 30 mm with 83 components and 73 nets, published under CERN-OHL-W-2.0.

review complete · 3 findings: 1 major · 2 minor (7 items)

Open in the interactive viewerRead the full review

WREN PATCH PANEL (OHWR0094 R2) circuit board, top view: copper, silkscreen and components
Top view, rendered by Probe from the design's own fabrication data.

Design review

Probe recorded 3 findings: 1 major · 2 minor (7 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. ReferencePlaneDiscontinuitymajorOpen

    ReferencePlaneDiscontinuity: 5 boards×5

    Checked by the review, stands · Claude walker P1 (cern-04 session) — Verify step: checked all 6 against CERN's KiCad layout (EDA-05024-V2-0.kicad_pcb, 4 copper layers, IN1.CU 'L2_5V/GND' split pour). The geometry is as the rule describes, so it is not refuted. The 5VREG|GND split on IN1.CU is crossed by PP_OUT/LED-data tracks. GND is cleared round PP_OUT tracks near J1 at x 115-118 mm where the 'fancy pinout' fans out. There are short (0.5-3 mm) crossings of routed cuts between B.CU/IN1.CU/IN2.CU. Whether these matter is layout practice, not a datasheet limit. The fastest local signal is the 19-C47 data line (800 kbps, datasheet p2, 74HCT1G125 edges). The PP_OUT1-32 edge rates are set by the node's drivers, off-board. No document on file sets a crossing limit for them, so each finding stands for CERN's judgement. Not a dispositioned defect.

    At split@IN1.CU:5VREG|GND, void:GND@B.CU:copper of /PP_OUT22,/PP_OUT23, void:GND@IN1.CU:118.25,-233.01, void:routed@B.CU|IN2.CU, void:routed@IN1.CU|IN2.CU

    Each finding, with its own headline
    • split@IN1.CU:5VREG|GND13 nets cross the split between the 5VREG and GND planes on IN1.CU at 22 places; 17 with a plane on the track's other side (fastest: /PP_LED1_DATA at 100 ps 10-90 %, ASSUMED)

      On IN1.CU the 5VREG and GND planes part, and 13 nets cross from one to the other at 22 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 17 of the 22 crossing(s) the track's other neighbour carries a plane, which the return can use there; 5 are on an outer layer, with no other neighbour. 17 of the 22 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.

      • '/LED_IO0_DIN_5V' on F.CU at (133.9, -226.4), 0.3 mm; other side: none: the signal layer is outermost
      • '/LED_IO1_DIN_5V' on F.CU at (119.03, -226.4), 0.3 mm; other side: none: the signal layer is outermost
      • '/LED_STAT_DIN_5V' on F.CU at (316.45, -226.4), 0.3 mm; other side: none: the signal layer is outermost
      • '/PP_LED1_DATA' on F.CU at (118.6, -230.6), 0.3 mm; other side: none: the signal layer is outermost
      • '/PP_LED1_DATA' on F.CU at (119.61, -231.61), 0.3 mm; other side: none: the signal layer is outermost
      • '/PP_OUT1' on IN2.CU at (120.84, -232.3), 0.25 mm; other side: GND on B.CU, 0.1 mm from the track against 1.2 mm to IN1.CU: 8% of the return on IN1.CU
      • '/PP_OUT1' on IN2.CU at (123.11, -232.25), 0.21 mm; other side: GND on B.CU, 0.1 mm from the track against 1.2 mm to IN1.CU: 8% of the return on IN1.CU
      • '/PP_OUT2' on IN2.CU at (120.89, -231.75), 0.23 mm; other side: GND on B.CU, 0.1 mm from the track against 1.2 mm to IN1.CU: 8% of the return on IN1.CU
      • '/PP_OUT2' on IN2.CU at (123.11, -231.75), 0.22 mm; other side: GND on B.CU, 0.1 mm from the track against 1.2 mm to IN1.CU: 8% of the return on IN1.CU
      • '/PP_OUT3' on IN2.CU at (119.15, -231.61), 0.3 mm; other side: GND on B.CU, 0.1 mm from the track against 1.2 mm to IN1.CU: 8% of the return on IN1.CU
      • '/PP_OUT3' on IN2.CU at (130.36, -231.61), 0.3 mm; other side: GND on B.CU, 0.1 mm from the track against 1.2 mm to IN1.CU: 8% of the return on IN1.CU
      • '/PP_OUT4' on IN2.CU at (131.11, -231.61), 0.3 mm; other side: GND on B.CU, 0.1 mm from the track against 1.2 mm to IN1.CU: 8% of the return on IN1.CU
      • and 10 more

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/99/reference-planes?group=split%40IN1.CU%3A5VREG%7CGND serves each with its own layer_image region; all of them lie in x 117.49..317.55, y -233.35..-225.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.

    • void:GND@B.CU:copper of /PP_OUT22,/PP_OUT2317 nets cross where the GND plane on B.CU, the GND plane on F.CU, the GND plane on IN1.CU and the GND plane on IN2.CU is drawn back round copper of /PP_LED0_DATA, /PP_OUT10, /PP_OUT11, /PP_OUT12, /PP_OUT13, /PP_OUT14, /PP_OUT15, /PP_OUT16, /PP_OUT17, /PP_OUT18, /PP_OUT19, /PP_OUT20, /PP_OUT21, /PP_OUT22, /PP_OUT23, /PP_OUT5, /PP_OUT6, /PP_OUT7, /PP_OUT8, /PP_OUT9, at 1 place, the longest 9.94 mm (fastest: /PP_LED0_DATA at 100 ps 10-90 %, ASSUMED)

      Along '/PP_OUT8' on IN2.CU, the GND plane on IN1.CU has 9.94 mm under the track with copper of /PP_OUT15, /PP_OUT11, /PP_OUT12, /PP_OUT13, /PP_OUT14, not a plane, at (115.25, -234.13), running to the end of the track. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 16 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 5.61 mm). No hole cleared it: the outline of the pour at x 100.5..529.5, y -249.5..-220.5 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 8 of the 31 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 31 reference layers: '/PP_LED0_DATA' on F.CU at (113, -235.25), 7.41 mm over copper of /PP_OUT16, /PP_OUT15, /PP_OUT14, /PP_OUT13, /PP_OUT12, /PP_OUT11, /PP_OUT10, /PP_OUT21, /PP_OUT20, /PP_OUT19, /PP_OUT18, /PP_OUT17, not a plane; other side: none: the signal layer is outermost / '/PP_OUT10' on IN1.CU at (117.9, -236.9), 0.54 mm over copper of /PP_LED0_DATA, not a plane; other side: no plane on IN2.CU / '/PP_OUT10' on IN1.CU at (117.75, -234.6), 6.56 mm, running ALONG the bare copper for 3.97 mm, not across it over copper of /PP_OUT5, /PP_OUT6, not a plane, to the end of the track; other side: GND on F.CU, 0.1 mm from the track against 1.2 mm to IN2.CU: 8% of the return on IN2.CU / '/PP_OUT11' on IN1.CU at (117.25, -236.9), 0.4 mm over copper of /PP_LED0_DATA, not a plane; other side: no plane on IN2.CU / '/PP_OUT11' on IN1.CU at (117.25, -234), 6.63 mm, running ALONG the bare copper for 2.98 mm, not across it over copper of /PP_OUT6, /PP_OUT7, /PP_OUT8, /PP_OUT9, not a plane, to the end of the track; other side: GND on F.CU, 0.1 mm from the track against 1.2 mm to IN2.CU: 8% of the return on IN2.CU / '/PP_OUT12' on IN1.CU at (116.75, -236.9), 0.4 mm over copper of /PP_LED0_DATA, not a plane; other side: no plane on IN2.CU / '/PP_OUT12' on IN1.CU at (116.75, -234.55), 4.83 mm, running ALONG the bare copper for 2.12 mm, not across it over copper of /PP_OUT7, /PP_OUT8, /PP_OUT9, not a plane, to the end of the track; other side: GND on F.CU, 0.1 mm from the track against 1.2 mm to IN2.CU: 8% of the return on IN2.CU / '/PP_OUT13' on IN1.CU at (116.25, -236.9), 0.4 mm over copper of /PP_LED0_DATA, not a plane; other side: no plane on IN2.CU / '/PP_OUT13' on IN1.CU at (116.25, -234.07), 5.63 mm, running ALONG the bare copper for 2.72 mm, not across it over copper of /PP_OUT7, /PP_OUT8, /PP_OUT9, not a plane, to the end of the track; other side: GND on F.CU, 0.1 mm from the track against 1.2 mm to IN2.CU: 8% of the return on IN2.CU / '/PP_OUT14' on IN1.CU at (115.75, -236.9), 0.4 mm over copper of /PP_LED0_DATA, not a plane; other side: no plane on IN2.CU / '/PP_OUT14' on IN1.CU at (115.75, -234.63), 3.83 mm, running ALONG the bare copper for 2.14 mm, not across it over copper of /PP_OUT8, /PP_OUT9, not a plane, to the end of the track; other side: GND on F.CU, 0.1 mm from the track against 1.2 mm to IN2.CU: 8% of the return on IN2.CU / '/PP_OUT15' on IN1.CU at (115.25, -236.9), 0.4 mm over copper of /PP_LED0_DATA, not a plane; other side: GND on IN2.CU, 1.2 mm from the track against 0.1 mm to F.CU: 92% of the return on F.CU / '/PP_OUT15' on IN1.CU at (115.25, -234.13), 4.63 mm, running ALONG the bare copper for 2.98 mm, not across it over copper of /PP_OUT8, /PP_OUT9, not a plane, to the end of the track; other side: GND on F.CU, 0.1 mm from the track against 1.2 mm to IN2.CU: 8% of the return on IN2.CU / '/PP_OUT16' on IN1.CU at (114.75, -236.75), 0.41 mm over copper of /PP_LED0_DATA, not a plane; other side: GND on IN2.CU, 1.2 mm from the track against 0.1 mm to F.CU: 92% of the return on F.CU / '/PP_OUT16' on IN1.CU at (114.75, -234.55), 2.83 mm, running ALONG the bare copper for 2.24 mm, not across it over copper of /PP_OUT9, not a plane, to the end of the track; other side: GND on F.CU, 0.1 mm from the track against 1.2 mm to IN2.CU: 8% of the return on IN2.CU / '/PP_OUT17' on IN1.CU at (114.25, -236.5), 0.57 mm over copper of /PP_LED0_DATA, not a plane; other side: GND on IN2.CU, 1.2 mm from the track against 0.1 mm to F.CU: 92% of the return on F.CU / '/PP_OUT17' on IN1.CU at (114.25, -233.98), 3.63 mm, running ALONG the bare copper for 2.92 mm, not across it over copper of /PP_OUT9, not a plane, to the end of the track; other side: GND on F.CU, 0.1 mm from the track against 1.2 mm to IN2.CU: 8% of the return on IN2.CU / '/PP_OUT18' on IN1.CU at (113.75, -236), 0.56 mm over copper of /PP_LED0_DATA, not a plane; other side: GND on IN2.CU, 1.2 mm from the track against 0.1 mm to F.CU: 92% of the return on F.CU / '/PP_OUT19' on IN1.CU at (113.25, -235.5), 0.56 mm over copper of /PP_LED0_DATA, not a plane; other side: GND on IN2.CU, 1.2 mm from the track against 0.1 mm to F.CU: 92% of the return on F.CU / '/PP_OUT20' on IN1.CU at (112.75, -235), 0.56 mm over copper of /PP_LED0_DATA, not a plane; other side: GND on IN2.CU, 1.2 mm from the track against 0.1 mm to F.CU: 92% of the return on F.CU / '/PP_OUT21' on IN1.CU at (112.25, -234.5), 0.56 mm over copper of /PP_LED0_DATA, not a plane; other side: GND on IN2.CU, 1.2 mm from the track against 0.1 mm to F.CU: 92% of the return on F.CU / '/PP_OUT6' on IN2.CU at (117.25, -234.65), 3.29 mm, running ALONG the bare copper for 2.75 mm, not across it over copper of /PP_OUT11, not a plane; other side: no plane on IN1.CU / '/PP_OUT6' on IN2.CU at (117.25, -234), 5.34 mm, running ALONG the bare copper for 3 mm, not across it over copper of /PP_OUT10, /PP_OUT11, not a plane; other side: no plane on B.CU / '/PP_OUT7' on IN2.CU at (116.25, -234.65), 3.21 mm, running ALONG the bare copper for 2.65 mm, not across it over copper of /PP_OUT13, not a plane; other side: no plane on IN1.CU / '/PP_OUT7' on IN2.CU at (116.25, -234), 8.98 mm, running ALONG the bare copper for 5.61 mm, not across it over copper of /PP_OUT11, /PP_OUT12, /PP_OUT13, not a plane, to the end of the track; other side: no plane on B.CU / '/PP_OUT8' on IN2.CU at (115.25, -234.65), 3.07 mm, running ALONG the bare copper for 2.55 mm, not across it over copper of /PP_OUT15, not a plane; other side: no plane on IN1.CU / '/PP_OUT8' on IN2.CU at (117.75, -238.05), 1.27 mm over copper of /PP_OUT9, /PP_OUT22, not a plane, to the end of the track; other side: no plane on IN1.CU / '/PP_OUT8' on IN2.CU at (115.25, -234.13), 9.94 mm, running ALONG the bare copper for 5.17 mm, not across it over copper of /PP_OUT15, /PP_OUT11, /PP_OUT12, /PP_OUT13, /PP_OUT14, not a plane, to the end of the track; other side: no plane on B.CU / '/PP_OUT9' on IN2.CU at (114.25, -234.65), 3.26 mm, running ALONG the bare copper for 2.7 mm, not across it over copper of /PP_OUT17, not a plane; other side: no plane on IN1.CU / '/PP_OUT9' on IN2.CU at (117.25, -238.4), 1.77 mm over copper of /PP_OUT22, /PP_OUT23, not a plane, to the end of the track; other side: no plane on IN1.CU / '/PP_OUT9' on IN2.CU at (114.25, -233.98), 9.4 mm, running ALONG the bare copper for 3.77 mm, not across it over copper of /PP_OUT17, /PP_OUT11, /PP_OUT12, /PP_OUT13, /PP_OUT14, /PP_OUT15, /PP_OUT16, not a plane, to the end of the track; other side: no plane on B.CU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/99/reference-planes?group=void%3AGND%40B.CU%3Acopper%20of%20%2FPP_OUT22%2C%2FPP_OUT23 serves each with its own layer_image region; all of them lie in x 110.98..120.95, y -241.25..-230.46 mm (board frame, Y up).

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

    • void:GND@IN1.CU:118.25,-233.01'/PP_OUT5' crosses where the GND plane on B.CU and the GND plane on IN1.CU is drawn back round copper of /PP_OUT4, at 1 place, the longest 3.12 mm; 1 cleared on both sides of the track (fastest: /PP_OUT5 at 100 ps 10-90 %, ASSUMED)

      Along '/PP_OUT5' on IN2.CU, the GND plane on B.CU has 3.12 mm under the track with copper of /PP_OUT4, not a plane, at (118.25, -234.65), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 2.6 mm). No hole cleared it: the outline of the pour at x 100.5..529.5, y -249.5..-220.5 is drawn back there. 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. 0 of the 2 crossing(s) have a plane on the track's other side at most twice as far away as the broken one (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The rest leave most or all of the return to the break, so the finding is a warning.

      • one stretch, cleared on 2 reference layers: '/PP_OUT5' on IN2.CU at (118.25, -234.65), 3.12 mm, running ALONG the bare copper for 2.6 mm, not across it over copper of /PP_OUT4, not a plane; other side: GND on IN1.CU, 1.2 mm from the track against 0.1 mm to B.CU: 92% of the return on B.CU / '/PP_OUT5' on IN2.CU at (118.25, -233.01), 0.5 mm over no copper; other side: no plane on B.CU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/99/reference-planes?group=void%3AGND%40IN1.CU%3A118.25%2C-233.01 serves each with its own layer_image region; all of them lie in x 117.06..119.25, y -236.5..-231.46 mm (board frame, Y up).

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

    • void:routed@B.CU|IN2.CUTracks on B.CU and IN2.CU cross each other at 2 places, each layer the other's reference with its pour cleared round its own tracks, the longest 0.7 mm (fastest: /PP_LED1_DATA at 100 ps 10-90 %, ASSUMED)

      B.CU and IN2.CU each carry a pour and routed tracks, and each is the other's nearest reference. Wherever a track on one crosses a track on the other, the pour under it is cleared round that other track, so for the width of the cut the return has no plane under it and detours round the cut. 2 place(s) on 3 net(s), 1 of them seen from both tracks (each counted once). One decision covers the layer pair: whether these layers may take a pour their own tracks cut as the reference, or the routing or the stackup should give the tracks a plane that is not cut where they cross. No crossing has a plane on the track's other side, so the whole return meets the break.

      • one crossing of two tracks, seen from each: '/PP_LED1_DATA' on B.CU at (120.25, -233.1), 0.53 mm over copper of /PP_OUT1, not a plane, to the end of the track; other side: none: the signal layer is outermost / '/PP_OUT1' on IN2.CU at (120.05, -233.09), 0.7 mm over copper of /PP_LED1_DATA, not a plane, to the end of the track; other side: no plane on IN1.CU
      • '/PP_OUT22' on B.CU at (117.25, -238.42), 0.28 mm over copper of /PP_OUT9, not a plane, to the end of the track; 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/99/reference-planes?group=void%3Arouted%40B.CU%7CIN2.CU serves each with its own layer_image region; all of them lie in x 116.25..121.45, y -239.63..-231.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.

    • void:routed@IN1.CU|IN2.CU2 nets on IN2.CU cross the tracks routed through the GND pour on IN1.CU at 2 places, the longest 2.08 mm; 1 runs ALONG the cut round another net's track (fastest: /PP_OUT5 at 100 ps 10-90 %, ASSUMED)

      The GND pour on IN1.CU is cleared round tracks routed through it, and tracks on IN2.CU, which take that pour as their reference, cross them: for the width of each cut the return has no plane under it and detours round the cut. 2 place(s) on 2 net(s). 1 of the crossings run ALONG the cut round another net's track rather than across it, parallel to its edges (the longest 0.98 mm): over or right beside that track, broadside to it as well as off the plane. One decision covers the layer pair: whether these layers may take a pour their own tracks cut as the reference, or the routing or the stackup should give the tracks a plane that is not cut where they cross. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/PP_OUT6' on IN2.CU at (119.25, -239.15), 2.08 mm, running ALONG the bare copper for 0.98 mm, not across it over copper of /PP_OUT10, not a plane, to the end of the track; other side: no plane on B.CU
      • '/PP_OUT5' on IN2.CU at (119.75, -239.02), 0.83 mm over copper of /PP_OUT10, not a plane, to the end of the track; other side: no plane on B.CU

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/99/reference-planes?group=void%3Arouted%40IN1.CU%7CIN2.CU serves each with its own layer_image region; all of them lie in x 118.25..120.75, y -241.25..-236.87 mm (board frame, Y up).

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

  2. observationOBS-661minorOpen

    33 addressable LEDs share three capacitors at one end of a 430 mm board: no 0.1 uF VDD bypass at any LED, which the LED datasheet calls necessary

    None of the 33 Everlight 19-C47 addressable RGB LEDs (LD1-LD33) has its own VDD bypass capacitor. The datasheet says a 0.1 uF bypass at each VDD pin is necessary for stable chip operation. The only capacitors on 5VREG sit next to IC1/IC2/J1, 11 mm from the nearest LED and 388 mm from the farthest.

    What the LED datasheet asks for

    The 19-C47 datasheet (Rev. 5, p4, "Cascading connection") draws a 0.1 uF capacitor from VDD to GND at every LED in the chain. Note 2 under that figure reads: "The by-pass capacitor of VDD pin is necessary to be added on the board for the stability of chip operation. The suggested value of capacitor is 0.1uF."

    Each LED holds a 3-channel constant-current driver with 8-bit PWM (datasheet p1). The LED load therefore switches at the PWM rate, at every LED.

    What the board has

    ItemValueSource
    LEDs on 5VREG33 (LD1-LD33, pin 2 VDD)netlist: net 5VREG
    Capacitors on 5VREG3: C1 100 nF, C3 100 nF, C2 220 uFnetlist: net 5VREG; CERN BOM EDA-05024-V2-0_pcb-mat
    Where they sitC1/C3 at IC1/IC2 (2.5 mm), C2 between them, all near J1 at x = 121-128 mmlayout (EDA-05024-V2-0.kicad_pcb)
    LED positionsx = 139 to 516 mm along the 430 mm panellayout
    Nearest capacitor to any LED11.4 mm (LD1 to C3)layout, centre to centre
    Farthest LED from any capacitor388 mm (LD32 to C3)layout, centre to centre

    ``mermaid flowchart LR J1["J1 pins 38/39 (5 V from node)"] --> C["C1, C2, C3 at IC1/IC2"] C -->|"11 to 388 mm of 5VREG copper, no capacitor"| L["LD1 ... LD33 VDD (pin 2)"] ``

    Why it matters

    Without local bypass, each LED's PWM current steps are supplied through hundreds of millimetres of 5VREG copper. The datasheet calls the capacitor necessary for stable operation of the LED's own driver and data receiver. Supply droop at a far LED can corrupt the serial data relayed down the chain, which shows up as wrong colours or flicker on the front panel. A 0.1 uF 0402 at each LED's VDD pin, as on p4, would remove the departure.

  3. ReferencePlaneDiscontinuityminorOpen

    '/PP_OUT5' crosses where the outline of the GND plane on IN1.CU is drawn back, at 1 place, the longest 0.49 mm (fastest: /PP_OUT5 at 100 ps 10-90 %, ASSUMED)

    Along '/PP_OUT5' on IN2.CU, the GND plane on IN1.CU has 0.49 mm under the track with no copper, at (117.75, -231.71), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 100.5..529.5, y -249.5..-220.5 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. Every crossing has a plane on the track's other side at most twice as far away as the broken one, so at most 8% 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).

    • '/PP_OUT5' on IN2.CU at (117.75, -231.71), 0.49 mm over no copper; other side: GND on B.CU, 0.1 mm from the track against 1.2 mm to IN1.CU: 8% of the return on IN1.CU

    Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/99/reference-planes?group=void%3AGND%40IN1.CU%3A117.75%2C-231.71 serves each with its own layer_image region; all of them lie in x 116.75..118.75, y -232.95..-230.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.

    At void:GND@IN1.CU:117.75,-231.71

Main parts

Part numberMakerDescriptionWhere
GRM32ER60J227ME05LMURATA±20% 6.3V X5R SMD Multilayer Chip Ceramic CapacitorC2
LSHM-120-02.5-L-DV-A-SSAMTEC40 Contacts, Pitch 0.5mm, Razor Beam™ Vertical High Speed Hermaphroditic Strip, with Shield, Lead Style-02.5J1
74HCT1G125GWNEXPERIABus Buffer/Line Driver 3-StateIC1, IC2
BN3318 Art.1384740BOSSARDM3 L=5mm, Hex Stand-Off with Internal Thread on Both Sides, Steel, Zinc Plated BlueSPACER1, SPACER2
GRM155R61C104KA88DMURATA±10% 16V X5R SMD Multilayer Chip Ceramic CapacitorC1, C3
KFS2-M3PEMBroaching Nut M3, Internally Threaded for Mounting on PC BoardsNUT1, NUT2
EPA.00.250.NTNLEMOSize 00, 50 Ohms Coaxial Straight SocketLM1, LM10, LM11, LM12, LM13, LM14 and 26 more
19-C47/RSGHBHC-5V01/2TEVERLIGHTAddressable Lighting - 1 LED Serial Red, Green, Blue (RGB) 1.80mm L x 1.80mm WLD1, LD10, LD11, LD12, LD13, LD14 and 27 more

About this design

Design
WREN PATCH PANEL — OHWR0094 R2
Designed in
KiCad EDA
Board
4 copper layers, 430 × 30 mm, 83 components, 73 nets
Licence
CERN-OHL-W-2.0
Source
https://edms.cern.ch/item/EDA-05024-V2-0/0 at commit EDMS EDA-050
Attribution
CERN EDMS item EDA-05024-V2-0 'WREN Patch Panel': document 3257027 v.1, retrieved 2026-10-23T06:50:57Z. Converted by E-Sharp with KiCad 10.0.6 (zones refilled); part identity from CERN's assembly BOM EDA-05024-V2-0_pcb-mat.xls.
Reviewed with
Probe by E# (E-Sharp AB)