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

WRS V3 BACKPLANE SIMPLE

OHWR0014 · revision R1

WRS V3 BACKPLANE SIMPLE (OHWR0014 R1) is an open-hardware circuit board from the CERN Open Hardware Repository, designed in Altium Designer: a 4-layer board of 289.2 × 154.1 mm with 147 components and 167 nets, published under CERN-OHL-1.2.

review 86% walked · 15 findings: 4 major · 11 minor (38 items)

Open in the interactive viewerRead the full review

WRS V3 BACKPLANE SIMPLE (OHWR0014 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 15 findings: 4 major · 11 minor (38 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. EsdProtectorPlacementmajorOpen

    EsdProtectorPlacement: 5 components×5

    Checked by the review, stands · Claude walker W2 (Cern session) — Checked: the via count and branch length are measured from the copper and stand; the 1 mm stub limit is Probe's default, with no datasheet figure for the protector on file. Layout practice, left for the owner.

    At IC4, IC6

    Each finding, with its own headline
    • IC4IC4.3 on 'NetIC3_4': 1 via(s) between P1.3 and IC4.3

      IC4 (PRTR5V0U2X) protects 'NetIC3_4' at P1.3. Along the copper: 2.96 mm of track from the contact, 1 via(s) before it, on a 0.97 mm branch off the line; the line runs 7.87 mm on to IC3.4; IC4 sits at P1, within 0.93 mm of the nearest place outside it to the contact: the track to it is mostly the escape out of P1's own pins, which no placement shortens.

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

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

    • IC4IC4.4 on 'NetC14_1': IC4.4 hangs 1.17 mm off the line (limit 1 mm, default

      IC4 (PRTR5V0U2X) protects 'NetC14_1' at P1.1. Along the copper: 9.05 mm of track from the contact, 0 via(s) before it, on a 1.17 mm branch off the line; the line runs 14.66 mm on to C14.1; IC4 sits at P1, within 0.93 mm of the nearest place outside it to the contact: the track to it is mostly the escape out of P1's own pins, which no placement shortens.

      IC4.4 hangs 1.17 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.

    • IC6IC6.2 on 'NetIC5_5': IC6.2 hangs 1.11 mm off the line (limit 1 mm, default

      IC6 (PRTR5V0U2X) protects 'NetIC5_5' at P3.2. Along the copper: 2.96 mm of track from the contact, 0 via(s) before it, on a 1.11 mm branch off the line; the line runs 8.39 mm on to IC5.5; IC6 sits at P3, within 0.98 mm of the nearest place outside it to the contact: the track to it is mostly the escape out of P3's own pins, which no placement shortens.

      IC6.2 hangs 1.11 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.

    • IC6IC6.3 on 'NetIC5_4': IC6.3 hangs 1.15 mm off the line (limit 1 mm, default

      IC6 (PRTR5V0U2X) protects 'NetIC5_4' at P3.3. Along the copper: 3 mm of track from the contact, 0 via(s) before it, on a 1.15 mm branch off the line; the line runs 8.39 mm on to IC5.4; IC6 sits at P3, within 0.98 mm of the nearest place outside it to the contact: the track to it is mostly the escape out of P3's own pins, which no placement shortens.

      IC6.3 hangs 1.15 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.

    • IC6IC6.4 on 'NetC16_1': IC6.4 hangs 1.11 mm off the line (limit 1 mm, default

      IC6 (PRTR5V0U2X) protects 'NetC16_1' at P3.1. Along the copper: 8.88 mm of track from the contact, 0 via(s) before it, on a 1.11 mm branch off the line; the line runs 15.69 mm on to C16.1; IC6 sits at P3, within 0.98 mm of the nearest place outside it to the contact: the track to it is mostly the escape out of P3's own pins, which no placement shortens.

      IC6.4 hangs 1.11 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.

  2. ReferencePlaneDiscontinuitymajorOpen

    ReferencePlaneDiscontinuity: 3 boards×3

    Checked by the review, stands · Claude walker W2 (Cern session) — Checked: the crossings and reference changes are read from the copper and stand as stated. No edge-rate or impedance requirement on file makes them a defect: most nets involved are slow control/IO, and the stackup's stated planes give a nearby return for most crossings as reported. Layout practice, left for the owner.

    At refchange:+3V3|GND, refchange:+5V|GND, split@POWER:+3V3|+5V

    Each finding, with its own headline
    • refchange:+3V3|GND88 nets change reference between +3V3 and GND at 205 vias, none with a reference that continues across (fastest: DETECTA at 100 ps 10-90 %, ASSUMED)

      At 205 via(s), on 88 net(s), the signal leaves a layer referenced by one of +3V3 and GND for a layer referenced by the other, and no plane references both layers. Different nets: no via can carry the return across; only decoupling between the two planes near the via can. The capacitor carrying the return across was measured at each via, at the knee of the crossing net's edge against 50 ohm assumed: 205 with none. 205 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 +3V3 and GND are decoupled to each other near these vias. A via whose layers have more references than these two is a site of each pair it joins. None is partial: at every one, no reference continues across the via.

      • 'MGTRX113_1_P' at (196.05, 43.58), TOP_LAYER -> BOTTOM_LAYER: +3V3 on POWER to GND on GND; pure, no reference continues across; stitching none, 199.3 mm of track past the via on BOTTOM_LAYER: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. +3V3 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'MGTRX113_1_N' at (196.86, 43.58), TOP_LAYER -> BOTTOM_LAYER: +3V3 on POWER to GND on GND; pure, no reference continues across; stitching none, 198.4 mm of track past the via on BOTTOM_LAYER: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. +3V3 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'MGTRX113_0_P' at (175.14, 43.58), TOP_LAYER -> BOTTOM_LAYER: +3V3 on POWER to GND on GND; pure, no reference continues across; stitching none, 189.7 mm of track past the via on BOTTOM_LAYER: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. +3V3 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'MGTRX113_0_N' at (175.95, 43.58), TOP_LAYER -> BOTTOM_LAYER: +3V3 on POWER to GND on GND; pure, no reference continues across; stitching none, 189.1 mm of track past the via on BOTTOM_LAYER: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. +3V3 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'MGTRX112_3_P' at (154.24, 43.58), TOP_LAYER -> BOTTOM_LAYER: +3V3 on POWER to GND on GND; pure, no reference continues across; stitching none, 181.1 mm of track past the via on BOTTOM_LAYER: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. +3V3 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'MGTRX112_3_N' at (155.05, 43.58), TOP_LAYER -> BOTTOM_LAYER: +3V3 on POWER to GND on GND; pure, no reference continues across; stitching none, 180.4 mm of track past the via on BOTTOM_LAYER: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. +3V3 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'MGTTX113_1_N' at (186.1, 50.57), TOP_LAYER -> BOTTOM_LAYER: +3V3 on POWER to GND on GND; pure, no reference continues across; stitching none, 177.7 mm of track past the via on BOTTOM_LAYER: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. +3V3 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'MGTTX113_1_P' at (186.91, 50.57), TOP_LAYER -> BOTTOM_LAYER: +3V3 on POWER to GND on GND; pure, no reference continues across; stitching none, 176.6 mm of track past the via on BOTTOM_LAYER: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. +3V3 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'MGTRX112_2_P' at (133.33, 43.28), TOP_LAYER -> BOTTOM_LAYER: +3V3 on POWER to GND on GND; pure, no reference continues across; stitching none, 173.0 mm of track past the via on BOTTOM_LAYER: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. +3V3 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'MGTRX112_2_N' at (134.15, 43.28), TOP_LAYER -> BOTTOM_LAYER: +3V3 on POWER to GND on GND; pure, no reference continues across; stitching none, 171.3 mm of track past the via on BOTTOM_LAYER: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. +3V3 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'MGTRX112_1_P' at (112.4, 43.55), TOP_LAYER -> BOTTOM_LAYER: +3V3 on POWER to GND on GND; pure, no reference continues across; stitching none, 161.4 mm of track past the via on BOTTOM_LAYER: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. +3V3 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'MGTRX112_1_N' at (113.22, 43.55), TOP_LAYER -> BOTTOM_LAYER: +3V3 on POWER to GND on GND; pure, no reference continues across; stitching none, 160.6 mm of track past the via on BOTTOM_LAYER: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. +3V3 and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • and 193 more

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/17/reference-planes?group=refchange%3A%2B3V3%7CGND serves each with its own layer_image region; all of them lie in x 1.28..272.42, y 6.69..119.48 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:+5V|GND25 nets change reference between +5V and GND at 25 vias, none with a reference that continues across (fastest: MGTRX112_0_N at 100 ps 10-90 %, ASSUMED)

      At 25 via(s), on 25 net(s), the signal leaves a layer referenced by one of +5V and GND for a layer referenced by the other, and no plane references both layers. Different nets: no via can carry the return across; only decoupling between the two planes near the via can. The capacitor carrying the return across was measured at each via, at the knee of the crossing net's edge against 50 ohm assumed: 25 with none. 25 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 +5V and GND are decoupled to each other near these vias. A via whose layers have more references than these two is a site of each pair it joins. None is partial: at every one, no reference continues across the via.

      • 'MGTRX113_1_P' at (76.33, 121.24), TOP_LAYER -> BOTTOM_LAYER: +5V on POWER to GND on GND; pure, no reference continues across; stitching none, 199.3 mm of track past the via on BOTTOM_LAYER: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. +5V and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'MGTRX113_1_N' at (76.33, 120.42), TOP_LAYER -> BOTTOM_LAYER: +5V on POWER to GND on GND; pure, no reference continues across; stitching none, 198.4 mm of track past the via on BOTTOM_LAYER: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. +5V and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'MGTRX113_0_P' at (76.33, 123.14), TOP_LAYER -> BOTTOM_LAYER: +5V on POWER to GND on GND; pure, no reference continues across; stitching none, 189.7 mm of track past the via on BOTTOM_LAYER: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. +5V and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'MGTRX113_0_N' at (76.33, 122.33), TOP_LAYER -> BOTTOM_LAYER: +5V on POWER to GND on GND; pure, no reference continues across; stitching none, 189.1 mm of track past the via on BOTTOM_LAYER: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. +5V and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'MGTRX112_3_P' at (76.3, 125.04), TOP_LAYER -> BOTTOM_LAYER: +5V on POWER to GND on GND; pure, no reference continues across; stitching none, 181.1 mm of track past the via on BOTTOM_LAYER: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. +5V and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'MGTRX112_3_N' at (76.3, 124.23), TOP_LAYER -> BOTTOM_LAYER: +5V on POWER to GND on GND; pure, no reference continues across; stitching none, 180.4 mm of track past the via on BOTTOM_LAYER: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. +5V and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'MGTTX113_1_N' at (65.23, 117.5), TOP_LAYER -> BOTTOM_LAYER: +5V on POWER to GND on GND; pure, no reference continues across; stitching none, 177.7 mm of track past the via on BOTTOM_LAYER: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. +5V and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'MGTTX113_1_P' at (65.23, 116.69), TOP_LAYER -> BOTTOM_LAYER: +5V on POWER to GND on GND; pure, no reference continues across; stitching none, 176.6 mm of track past the via on BOTTOM_LAYER: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. +5V and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'MGTRX112_2_P' at (76.25, 126.95), TOP_LAYER -> BOTTOM_LAYER: +5V on POWER to GND on GND; pure, no reference continues across; stitching none, 173.0 mm of track past the via on BOTTOM_LAYER: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. +5V and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'MGTRX112_2_N' at (76.25, 126.14), TOP_LAYER -> BOTTOM_LAYER: +5V on POWER to GND on GND; pure, no reference continues across; stitching none, 171.3 mm of track past the via on BOTTOM_LAYER: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. +5V and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'MGTRX112_1_P' at (76.25, 128.87), TOP_LAYER -> BOTTOM_LAYER: +5V on POWER to GND on GND; pure, no reference continues across; stitching none, 161.4 mm of track past the via on BOTTOM_LAYER: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. +5V and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • 'MGTRX112_1_N' at (76.25, 128.05), TOP_LAYER -> BOTTOM_LAYER: +5V on POWER to GND on GND; pure, no reference continues across; stitching none, 160.6 mm of track past the via on BOTTOM_LAYER: At the 5 GHz knee of a 100 ps edge (100 ps 10-90 %, assumed: no edge is on file for the net) no capacitor carries the return; only the planes do. +5V and GND are not a thin pair (at most 0.2 mm), so their own capacitance does not carry the return. To serve it, change layers across the same plane, or move the signal to a layer referenced to ground. None.
      • and 13 more

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/17/reference-planes?group=refchange%3A%2B5V%7CGND serves each with its own layer_image region; all of them lie in x 18.42..78.33, y 109.25..132.8 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@POWER:+3V3|+5V3 nets cross the split between the +3V3 and +5V planes on POWER at 4 places, with no plane on the track's other side (fastest: NetIC2_5 at 100 ps 10-90 %, ASSUMED)

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

      • 'DBGU_RXD' on TOP_LAYER at (219.66, 45.57), 0.43 mm; other side: none: the signal layer is outermost
      • 'DBGU_RXD' on TOP_LAYER at (245.34, 31.85), 0.43 mm; other side: none: the signal layer is outermost
      • 'DBGU_TXD' on TOP_LAYER at (246.89, 31.85), 0.43 mm; other side: none: the signal layer is outermost
      • 'NetIC2_5' on TOP_LAYER at (258.09, 40.46), 0.39 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/17/reference-planes?group=split%40POWER%3A%2B3V3%7C%2B5V serves each with its own layer_image region; all of them lie in x 218.51..259.19, y 30.7..46.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.

  3. SinglePointNetmajorOpen

    SinglePointNet: 2 pins×2

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

    At IC1.2, IC2.2

    Each finding, with its own headline
    • IC1.2IC1.2 (Track) is an IC input left unconnected

      Pin IC1.2 (Track) 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.2IC2.2 (Track) is an IC input left unconnected

      Pin IC2.2 (Track) 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.

  4. FiducialMissingmajorOpen

    The top side carries 40 SMT component(s) and no fiducial was found on it

    The top side carries 40 SMT component(s) but no fiducial was found on it — a placement machine has no optical reference to align to. Probe found no pad labelled .pad_usage=g_fiducial/l_fiducial (basis pad_usage); no single-pad, netless, undrilled component whose 0.5-3 mm round pad has a concentric solder-mask opening at least 1.5x its diameter with no other copper inside it (basis geometry); and no component whose refdes starts FID or whose part or package name contains FIDUCIAL (basis footprint-name). If your library names fiducials something Probe does not recognise, mark this benign — disposition_finding(rule='FiducialMissing', entity='top', status='benign', reason=…) — the name match only ever silences this check, it never asserts anything. If the side really has no fiducial, say so with status='confirmed': that answers the finding and keeps it gating release.

    At top

  5. observationOBS-286minorOpen

    PTH12050W modules IC1 (+3V3) and IC2 (+5V): Track input (pin 2) left unconnected, where TI says an unused Track input should be tied to VI

    PTH12050W modules IC1 (+3V3) and IC2 (+5V) leave the Track input (pin 2) unconnected, where TI says an unused Track input should be tied to VI.

    PinFunctionIC1IC2
    1GNDGNDGND
    2Trackunconnectedunconnected
    3VI+12V_PSU+12V_PSU
    4Inhibitunconnectedunconnected
    5setNetIC1_5 (R18 2k)NetIC2_5 (R19 270R)
    6VO+3V3+5V
    • The schematic sheet 8 'Power Supply' draws Track and Inhibit as open stubs.
    • TI's terminal-functions table (p.5) for Track: if unused, the input should be connected to VI, here +12V_PSU (pin 3).
    • Inhibit (pin 4) open is explicitly allowed: the module runs whenever a valid input is present.
  6. observationOBS-287minorOpen

    PTH12050W modules IC1 (+3V3) and IC2 (+5V): no 10 uF ceramic input capacitor on +12V_PSU, which TI lists as required for outputs of 3.3 V and higher

    PTH12050W modules IC1 (+3V3) and IC2 (+5V) have no 10 µF ceramic input capacitor on +12V_PSU, which TI lists as required for outputs of 3.3 V and higher.

    Input net +12V_PSU

    The net joins D1.1, IC1.3, IC2.3, J3.1, J4.1, C9.1 and C11.1 only. C9 and C11 are both 16SEQP150M 150 µF OS-CON polymer parts. There is no ceramic capacitor on +12V_PSU at all.

    Set points

    ModuleSet resistorOutputSource
    IC1R18 = 2k3.3 V (Table 1: 3.3 V -> 2.0 kOhm)PTH12050W datasheet, Table 1
    IC2R19 = 270 ohmabout 5.03 V (Equation 1, Rs = 1.82 kOhm; Table 1: 5 V -> 0.280 kOhm)PTH12050W datasheet, Equation 1 and Table 1

    What TI asks for

    • Electrical-characteristics note (4), p.3: 100 µF electrolytic input required, plus an additional 10 µF ceramic for outputs of 3.3 V and higher.
    • Standard-application note B, p.2: C2 = 10 µF ceramic, required for outputs of 3.3 V or higher.
  7. observationOBS-289minorOpen

    No fiducials on the board: 130 SMT parts including 0.5 mm-pitch QFN-28 bridges and 0.635 mm-pitch QTS connectors are placed with no global or local fiducial

    The board has no fiducials, although it places 130 SMT parts including 0.5 mm-pitch QFN-28 bridges and 0.635 mm-pitch QTS connectors.

    The placement record for the board (289.2 × 154.1 mm, 147 parts all on the top side, 130 SMT / 17 THT, not panelised) contains no fiducials: no pad carries a fiducial usage attribute and no component reads as a fiducial.

    Fine-pitch parts:

    • IC3 / IC5 CP2102-GM USB bridges (QFN-28)
    • J1 / J2 Samtec QTS-075 board-to-board connectors (0.635 mm pitch, per Samtec QSS/QTS spec page 1)
    • six SFP cages
  8. observationOBS-291minorOpen

    USB-UART bridges: the two UART links are named from opposite ends, so FPGA_RXD/FPGA_TXD cannot be read as the FPGA's own RX/TX the way DBGU_TXD/DBGU_RXD read as the CPU's

    The two USB-UART links on the 'USB - serial converters' sheet are named from opposite ends, so FPGA_RXD/FPGA_TXD cannot be read as the FPGA's own RX/TX the way DBGU_TXD/DBGU_RXD read as the CPU's.

    CP2102 pin 25 is RXD (UART receive input) and pin 26 is TXD (UART transmit output) (CP2102 datasheet, p.11).

    The two links

    LinkNet on bridge RXD (pin 25, input)Net driven by bridge TXD (pin 26)Named from
    DBGU, IC3DBGU_TXD (IC3.25 and P2.3 only)DBGU_RXD, through R22the far end: the switch core board CPU's TX and RX
    FPGA, IC5FPGA_RXD (IC5.25 and J2.78 only)FPGA_TXD, through R26 3k3 to J2.80, R27 10k to GNDunclear

    If the FPGA pair were named the same way as the DBGU pair, the FPGA's RX would face the bridge's RX and the FPGA's TX would face the bridge's TX.

    What the drawing suggests

    The matching R22/R23 and R26/R27 dividers (3.3 V down to about 2.4-2.5 V) feed what sheet 9 'SCB connectors' labels a 2.5 V LVCMOS group (J2 even pins 2-80: FPGA_GPIO0-37, FPGA_RXD, FPGA_TXD). That suggests the FPGA link is wired bridge-TX to FPGA-RX and merely named from the bridge side. But nothing on the drawing says which convention each pair uses.

  9. observationOBS-293minorOpen

    Silkscreen line along the front edge crosses the four USB receptacle shell pads of P1 and P3 (GND)

    A silkscreen stroke along the front edge (y = 0 mm) crosses the solder-mask openings of the four GND shell pads of USB Mini-B receptacles P1 and P3.

    ReceptacleShell pad x-spanCrossing point
    P3250.4-252.6 mm(252.55, -0.03)
    P3259.3-261.5 mm(261.39, -0.03)
    P1264.8-267.0 mm(266.87, -0.03)
    P1273.7-275.9 mm(275.79, -0.03)
    • Each pad spans y -0.12 to 2.58 mm. The pads, like the receptacle bodies, run slightly past the outline (both receptacles overhang the y = 0 edge by 1.67 mm).
    • All four pads are GND (P1.6 and P3.6 on the record).
    • The stroke lies about 0.1 mm inside the outer edge of each opening.
    • An overlap test of TOP_OVERLAY strokes against TOP_SOLDER openings over the whole board finds 4 of 1018 openings crossed, all these. Against TOP_PASTE there is no crossing (the shell pads carry no paste in this data).
  10. observationOBS-542minorOpen

    OHWR0014 R1 WRS V3 BACKPLANE SIMPLE: D1 drop on the J5 jack path puts the PTH12050W inputs below 10.8 V at the stated 11 V minimum supply

    On the J5 jack path, D1 (SS34) sits in series ahead of both PTH12050W modules, so at the 11 V lower end of the supply range noted on the sheet, IC1 and IC2 see less than their 10.8 V minimum input.

    Claim

    Sheet 8 (Power Supply) notes "External power supply: 11 - 13 V". Power can enter at J3 directly, or at the J5 DC jack through Schottky diode D1. On the J5 path, +12V_PSU is the jack voltage minus D1's forward drop. Any drop above 0.2 V puts an 11 V supply below the PTH12050W input range. The J3 path has no diode and is not affected.

    Evidence

    QuantityValueSource
    Stated supply range11 - 13 Vschematic sheet 8, note "External power supply: 11 - 13 V"
    J5 pathJ5 pin 3 -> D1 anode (pin 2), D1 cathode (pin 1) -> +12V_PSUschematic sheet 8; netlist NetD1_2 = D1.2, J5.3
    IC1, IC2 input+12V_PSU on VI pin 3schematic sheet 8
    PTH12050W input voltage range10.8 V min, 13.2 V maxPTH12050W datasheet SLTS214H, Electrical Characteristics, p. 3
    SS34 forward voltage500 mV typ, 750 mV max at IF = 3.0 ASS34 datasheet (onsemi), Electrical Characteristics, p. 2
    Headroom at 11 V in11.0 - 10.8 = 0.2 V for D1's dropderived

    Power path

    ``mermaid graph LR J5[J5 DC jack, 11-13 V] --> D1[D1 SS34, Vf about 0.3-0.5 V] D1 --> P12[+12V_PSU] J3[J3 Power, 11-13 V] --> P12 P12 --> IC1[IC1 PTH12050W -> +3V3] P12 --> IC2[IC2 PTH12050W -> +5V] ``

    Why it matters

    At 11 V on J5, the modules get about 10.5-10.7 V, depending on load current through D1. That is outside the range over which TI specifies regulation and the 5 V set point. The lowest jack supply that keeps the modules in range is about 11.3 V at typical drop. Either narrow the stated range for the jack, or feed the jack path without a series diode, for example with an ideal-diode controller.

  11. observationOBS-678minorOpen

    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 T1A, T1B, T1C, T1D, T1E, T1F. A sourcing/longevity risk; consider a replacement before production.

  12. concernCON-001minorOpen

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

  13. AssemblySeamminorOpen

    AssemblySeam: 10 nets×10

    Checked by the review, stands · Claude walker W2 (Cern session) — Checked: a cross-board finding raised through the board's interconnect; it is judged on the interconnect, not in this board walk. Left for the owner.

    At FPGA_GPIO16, FPGA_GPIO17, FPGA_GPIO18, FPGA_GPIO19, PB5, PB7 and 4 more

    Each finding, with its own headline
    • FPGA_GPIO16BP-SIMPLE FPGA_GPIO16 reaches nothing on its board (OHWR-WRS-V3)

      BP-SIMPLE names this net FPGA_GPIO16 and wires it to J2.34, and to nothing else on the board. Across the seam it meets SCB FPGA_GPIO16. A named net that stops at a connector is usually a label that did not attach to the wire it was meant for.

      Found by the seam review of OHWR-WRS-V3 build 2 (M1-continuity, across seam:4), where this board sits as BP-SIMPLE. Decide it here (disposition_finding forwards it to the assembly) or on the assembly (build id 2, kind signal, ref signal:M1-continuity:86025c0b0d2630d3), and the decision holds on both.

    • FPGA_GPIO17BP-SIMPLE FPGA_GPIO17 reaches nothing on its board (OHWR-WRS-V3)

      BP-SIMPLE names this net FPGA_GPIO17 and wires it to J2.36, and to nothing else on the board. Across the seam it meets SCB FPGA_GPIO17. A named net that stops at a connector is usually a label that did not attach to the wire it was meant for.

      Found by the seam review of OHWR-WRS-V3 build 2 (M1-continuity, across seam:4), where this board sits as BP-SIMPLE. Decide it here (disposition_finding forwards it to the assembly) or on the assembly (build id 2, kind signal, ref signal:M1-continuity:8ef8885125a3b317), and the decision holds on both.

    • FPGA_GPIO18BP-SIMPLE FPGA_GPIO18 reaches nothing on its board (OHWR-WRS-V3)

      BP-SIMPLE names this net FPGA_GPIO18 and wires it to J2.38, and to nothing else on the board. Across the seam it meets SCB FPGA_GPIO18. A named net that stops at a connector is usually a label that did not attach to the wire it was meant for.

      Found by the seam review of OHWR-WRS-V3 build 2 (M1-continuity, across seam:4), where this board sits as BP-SIMPLE. Decide it here (disposition_finding forwards it to the assembly) or on the assembly (build id 2, kind signal, ref signal:M1-continuity:c0a5c638f0a7e930), and the decision holds on both.

    • FPGA_GPIO19BP-SIMPLE FPGA_GPIO19 reaches nothing on its board (OHWR-WRS-V3)

      BP-SIMPLE names this net FPGA_GPIO19 and wires it to J2.40, and to nothing else on the board. Across the seam it meets SCB FPGA_GPIO19. A named net that stops at a connector is usually a label that did not attach to the wire it was meant for.

      Found by the seam review of OHWR-WRS-V3 build 2 (M1-continuity, across seam:4), where this board sits as BP-SIMPLE. Decide it here (disposition_finding forwards it to the assembly) or on the assembly (build id 2, kind signal, ref signal:M1-continuity:6e34f034cb098992), and the decision holds on both.

    • PB5BP-SIMPLE PB5 reaches nothing on its board (OHWR-WRS-V3)

      BP-SIMPLE names this net PB5 and wires it to J2.61, and to nothing else on the board. Across the seam it meets SCB PB5. A named net that stops at a connector is usually a label that did not attach to the wire it was meant for.

      Found by the seam review of OHWR-WRS-V3 build 2 (M1-continuity, across seam:4), where this board sits as BP-SIMPLE. Decide it here (disposition_finding forwards it to the assembly) or on the assembly (build id 2, kind signal, ref signal:M1-continuity:9d33677b678a2030), and the decision holds on both.

    • PB7BP-SIMPLE PB7 reaches nothing on its board (OHWR-WRS-V3)

      BP-SIMPLE names this net PB7 and wires it to J2.63, and to nothing else on the board. Across the seam it meets SCB PB7. A named net that stops at a connector is usually a label that did not attach to the wire it was meant for.

      Found by the seam review of OHWR-WRS-V3 build 2 (M1-continuity, across seam:4), where this board sits as BP-SIMPLE. Decide it here (disposition_finding forwards it to the assembly) or on the assembly (build id 2, kind signal, ref signal:M1-continuity:914f8b50825d83d2), and the decision holds on both.

    • PE1BP-SIMPLE PE1 reaches nothing on its board (OHWR-WRS-V3)

      BP-SIMPLE names this net PE1 and wires it to J2.75, and to nothing else on the board. Across the seam it meets SCB PE1. A named net that stops at a connector is usually a label that did not attach to the wire it was meant for.

      Found by the seam review of OHWR-WRS-V3 build 2 (M1-continuity, across seam:4), where this board sits as BP-SIMPLE. Decide it here (disposition_finding forwards it to the assembly) or on the assembly (build id 2, kind signal, ref signal:M1-continuity:dc74b98803f71042), and the decision holds on both.

    • PE2BP-SIMPLE PE2 reaches nothing on its board (OHWR-WRS-V3)

      BP-SIMPLE names this net PE2 and wires it to J2.73, and to nothing else on the board. Across the seam it meets SCB PE2. A named net that stops at a connector is usually a label that did not attach to the wire it was meant for.

      Found by the seam review of OHWR-WRS-V3 build 2 (M1-continuity, across seam:4), where this board sits as BP-SIMPLE. Decide it here (disposition_finding forwards it to the assembly) or on the assembly (build id 2, kind signal, ref signal:M1-continuity:48e44842a054dcc6), and the decision holds on both.

    • PE7BP-SIMPLE PE7 reaches nothing on its board (OHWR-WRS-V3)

      BP-SIMPLE names this net PE7 and wires it to J2.77, and to nothing else on the board. Across the seam it meets SCB PE7. A named net that stops at a connector is usually a label that did not attach to the wire it was meant for.

      Found by the seam review of OHWR-WRS-V3 build 2 (M1-continuity, across seam:4), where this board sits as BP-SIMPLE. Decide it here (disposition_finding forwards it to the assembly) or on the assembly (build id 2, kind signal, ref signal:M1-continuity:d8f563a729612fd4), and the decision holds on both.

    • PE9BP-SIMPLE PE9 reaches nothing on its board (OHWR-WRS-V3)

      BP-SIMPLE names this net PE9 and wires it to J2.79, and to nothing else on the board. Across the seam it meets SCB PE9. A named net that stops at a connector is usually a label that did not attach to the wire it was meant for.

      Found by the seam review of OHWR-WRS-V3 build 2 (M1-continuity, across seam:4), where this board sits as BP-SIMPLE. Decide it here (disposition_finding forwards it to the assembly) or on the assembly (build id 2, kind signal, ref signal:M1-continuity:e59f582d00f6b4ee), and the decision holds on both.

  14. ConnectorDomainMixedminorOpen

    ConnectorDomainMixed: 6 components×6

    Checked by the review, stands · Claude walker W2 (Cern session) — Checked: two supplies leave the board on one connector by design (a board-to-board or power interface); the partner side is not described here. Left for the owner.

    At CN1A, CN1B, CN1C, CN1D, CN1E, CN1F

    Each finding, with its own headline
    • CN1ACN1A takes 3 different supplies off the board on one connector: NetC1A_1 (3.3 V), NetC3A_2 (3.3 V), +2V5 (2.5 V)

      CN1A carries 3 different supplies out of the board on one connector: NetC1A_1 (3.3 V) on 15, NetC3A_2 (3.3 V) on 16, +2V5 (2.5 V) on 7. 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.

    • CN1BCN1B takes 3 different supplies off the board on one connector: NetC1B_1 (3.3 V), NetC3B_2 (3.3 V), +2V5 (2.5 V)

      CN1B carries 3 different supplies out of the board on one connector: NetC1B_1 (3.3 V) on 15, NetC3B_2 (3.3 V) on 16, +2V5 (2.5 V) on 7. 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.

    • CN1CCN1C takes 3 different supplies off the board on one connector: NetC1C_1 (3.3 V), NetC3C_2 (3.3 V), +2V5 (2.5 V)

      CN1C carries 3 different supplies out of the board on one connector: NetC1C_1 (3.3 V) on 15, NetC3C_2 (3.3 V) on 16, +2V5 (2.5 V) on 7. 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.

    • CN1DCN1D takes 3 different supplies off the board on one connector: NetC1D_1 (3.3 V), NetC3D_2 (3.3 V), +2V5 (2.5 V)

      CN1D carries 3 different supplies out of the board on one connector: NetC1D_1 (3.3 V) on 15, NetC3D_2 (3.3 V) on 16, +2V5 (2.5 V) on 7. 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.

    • CN1ECN1E takes 3 different supplies off the board on one connector: NetC1E_1 (3.3 V), NetC3E_2 (3.3 V), +2V5 (2.5 V)

      CN1E carries 3 different supplies out of the board on one connector: NetC1E_1 (3.3 V) on 15, NetC3E_2 (3.3 V) on 16, +2V5 (2.5 V) on 7. 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.

    • CN1FCN1F takes 3 different supplies off the board on one connector: NetC1F_1 (3.3 V), NetC3F_2 (3.3 V), +2V5 (2.5 V)

      CN1F carries 3 different supplies out of the board on one connector: NetC1F_1 (3.3 V) on 15, NetC3F_2 (3.3 V) on 16, +2V5 (2.5 V) on 7. 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.

  15. PartLifecycleminorOpen

    PartLifecycle: 3 part numbers×3

    3 Not For New Designs · on 6 placements

    At C10, C11, IC3

    Each finding, with its own headline
    • C106SEQP150M on 2 placements (C10, C12): the distributor catalogue reports "Not For New Designs" for Panasonic Industry's 6SEQP150M

      6SEQP150M on 2 placements (C10, C12): the distributor catalogue reports "Not For New Designs" for Panasonic Industry's 6SEQP150M — a sourcing/longevity risk to confirm against the MANUFACTURER before acting. This board's BOM names SANYO OS-CON, and that is one line with Panasonic Industry: Panasonic made SANYO Electric a wholly owned subsidiary on 2011-04-01; SANYO's capacitor lines (OS-CON, POSCAP) are sold under the Panasonic name. 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/6SEQP150M/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.

    • C1116SEQP150M on 2 placements (C11, C9): the distributor catalogue reports "Not For New Designs" for Panasonic Industry's 16SEQP150M

      16SEQP150M on 2 placements (C11, C9): the distributor catalogue reports "Not For New Designs" for Panasonic Industry's 16SEQP150M — a sourcing/longevity risk to confirm against the MANUFACTURER before acting. This board's BOM names SANYO OS-CON, and that is one line with Panasonic Industry: Panasonic made SANYO Electric a wholly owned subsidiary on 2011-04-01; SANYO's capacitor lines (OS-CON, POSCAP) are sold under the Panasonic name. 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/16SEQP150M/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.

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

      CP2102-GM on 2 placements (IC3, IC5): 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. That is the maker this board's BOM names (SILICON LABS). 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.

Main parts

Part numberMakerDescriptionWhere
161314LUMBERG24V /3. 5A, 2.1mm Diameter Pin, SMD DC Power Supply Connector With Break ContactJ5
FANConnectorJ4
PowerHeader, 2-PinJ3
SCB DBGUHeader, 3-Pin, Dual row, 2.54mm pitchP2
SS34FAIRCHILD SEMICONDUCTORSchottky DiodeD1
1734035-1TYCO ELECTRONICS5 Pin + 1 Shield USB ReceptacleP1, P3
CP2102-GMSILICON LABSSingle-Chip USB to UART BridgeIC3, IC5
PRTR5V0U2XPHILIPS NXPUltra Low Capacitance Double Rail-to-Rail ESD Protection DiodeIC4, IC6
PTH12050WAHTEXAS INSTRUMENTS6-A, 12-V Input, Non-Isolated, Wide-Output 1.2V to 5.5V, Adjustable Power ModueIC1, IC2
QTS-075-01-L-D-A_WRMODHigh Speed Ground Plane HeaderJ1, J2
BC847BNXP SEMICONDUCTORSNPN TransistorT1A, T1B, T1C, T1D, T1E, T1F
571-0112-100FDIALIGHT2x LED Botom Green, Top RedLD1, LD2, LD3, LD4, LD5, LD6, LD7, LD8
R0805_270R_1%_0.125W_100PPMGENERICResistor - 1%R19
R0805_2K_1%_0.125W_100PPMGENERICResistor - 1%R18
16SEQP150MSANYO OS-CONPolarised capacitorC11, C9
6SEQP150MSANYO OS-CONPolarised capacitorC10, C12
CC0603_1uF_16V_10%_X7RGENERICNon-polarised capacitorC13, C15
R0603_3K3_1%_0.1W_100PPMGENERICResistor - 1%R20, R21, R22, R24, R25, R26
CC0603_10NF_50V_10%_X7RGENERICNon-polarised capacitorC7A, C7B, C7C, C7D, C7E, C7F and 6 more
R0603_10K_1%_0.1W_100PPMGENERICResistor - 1%R17A, R17B, R17C, R17D, R17E, R17F and 8 more
R0603_330R_1%_0.1W_100PPMGENERICResistor - 1%R1, R10, R11, R12, R13, R14 and 10 more
CC1206_10uF_10V_10%_X7RGENERICNon-polarised capacitorC1A, C1B, C1C, C1D, C1E, C1F and 12 more
CC0603_100NF_50V_10%_X7RGENERICNon-polarised capacitorC14, C16, C2A, C2B, C2C, C2D and 14 more

About this design

Design
WRS V3 BACKPLANE SIMPLE — OHWR0014 R1
Designed in
Altium Designer
Board
4 copper layers, 289.2 × 154.1 mm, 147 components, 167 nets
Licence
CERN-OHL-1.2
Source
https://gitlab.com/ohwr/project/wr-switch-hw at commit 54f8a604978b
Attribution
CERN Open Hardware Repository, project ohwr/project/wr-switch-hw (commit 54f8a604978bdc65bbde5b1f4c7ec9bee3505a44, 2025-04-09). Licence: CERN-OHL-1.2. Source: https://gitlab.com/ohwr/project/wr-switch-hw. 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)