MDIOR
OHWR0081 · revision R1
MDIOR (OHWR0081 R1) is an open-hardware circuit board from the CERN Open Hardware Repository, designed in KiCad EDA: a 6-layer board of 160 × 100 mm with 226 components and 242 nets, published under CERN-OHL-W-2.0.
review 69% walked · 16 findings: 1 blocker · 8 major · 7 minor (24 items)
Open in the interactive viewerRead the full review

Design review
Probe recorded 16 findings: 1 blocker · 8 major · 7 minor (24 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.
- NetCopperSplitblockerOpen
Chassis's copper is in 4 pieces: B1.1, B2.1, B3.1, C46.2, D19.2, D20.2, D21.2, D22.2 and 3 more pin(s) and 2 other piece(s) are not connected to the rest of the net
Chassis's copper is in 4 pieces: B1.1, B2.1, B3.1, C46.2, D19.2, D20.2, D21.2, D22.2 and 3 more pin(s) and 2 other piece(s) are not connected to the rest of the net. Piece 1: D1.1, D10.1, D11.2, D12.1, D13.2, D2.2, D4.1, D5.2 and 4 more pin(s), on TOP, L2_GND, L3, L4, L5_PWR and BOTTOM, 10 drill(s), over (103.75, -100) to (203.95, -63.47). Piece 2: B1.1, B2.1, B3.1, C46.2, D19.2, D20.2, D21.2, D22.2 and 3 more pin(s), on TOP, L2_GND, L3, L4, L5_PWR and BOTTOM, 9 drill(s), 1176.28 mm2 of pour, over (164.33, -150.11) to (210.1, -51.11). Piece 3: J3.16, on TOP, 90.79 mm2 of pour, over (197.77, -67.55) to (210.38, -60.35). Piece 4: J3.17, on TOP, 90.79 mm2 of pour, over (197.77, -100.86) to (210.38, -93.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.
At split:Chassis
BAT54S went end-of-life (Obsolete)
Vendor (DigiKey) lifecycle for BAT54S (onsemi's listing) changed from "Active" to "Obsolete" since this board was reviewed. Placed as D14, D17, D18, D3. A sourcing/longevity risk; consider a replacement before production.
- concernCON-001majorOpen
[eol:BAT54S:Obsolete] BAT54S lifecycle changed from "Active" to "Obsolete" since this board was reviewed: OHWR0081 R1 MDIOR. A sourcing and longevity risk. Should this be replaced before the next build?
- ReferencePlaneDiscontinuitymajorOpen
26 nets change reference between +2V5 and GND at 49 vias; 35 of them partial (fastest: /RTM_SHARED_BUS0 at 100 ps 10-90 %, ASSUMED)
At 49 via(s), on 26 net(s), the signal leaves a layer referenced by one of +2V5 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: 49 with none. 49 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 +2V5 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. 35 of them are partial: another reference continues across through a stitching via of its net, so only part of the return has nowhere to go. The pure ones are listed first, then the partial ones with the farthest stitching via first.
- '/bus_ready_n' at (126.99, -88.46), TOP -> BOTTOM: GND on L2_GND to +2V5 on L5_PWR; pure, no reference continues across; stitching none, 128.3 mm of track past the via on BOTTOM: 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. +2V5 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.
- '/bus_ready_n' at (148.45, -88.46), TOP -> BOTTOM: GND on L2_GND to +2V5 on L5_PWR; pure, no reference continues across; stitching none, 128.3 mm of track past the via on BOTTOM: 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. +2V5 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.
- '/bus_ready_n' at (169.92, -88.46), TOP -> BOTTOM: GND on L2_GND to +2V5 on L5_PWR; pure, no reference continues across; stitching none, 128.3 mm of track past the via on BOTTOM: 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. +2V5 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.
- '/bus_ready_n' at (191.38, -88.46), TOP -> BOTTOM: GND on L2_GND to +2V5 on L5_PWR; pure, no reference continues across; stitching none, 128.3 mm of track past the via on BOTTOM: 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. +2V5 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.
- '/R_IO3' at (192.52, -92.39), TOP -> BOTTOM: GND on L2_GND to +2V5 on L5_PWR; pure, no reference continues across; stitching none, 126.7 mm of track past the via on BOTTOM: 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. +2V5 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.
- '/R_IO2' at (171.06, -92.39), TOP -> BOTTOM: GND on L2_GND to +2V5 on L5_PWR; pure, no reference continues across; stitching none, 119.9 mm of track past the via on BOTTOM: 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. +2V5 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.
- '/RTM_SHARED_BUS0' at (124.58, -72.46), TOP -> L4: GND on L2_GND to GND on L3, +2V5 on L5_PWR; partial, GND continues through a via of GND 8.57 mm away; stitching none, 88.3 mm of track past the via on L4: 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. +2V5 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.
- '/R_IO1' at (149.6, -92.39), TOP -> BOTTOM: GND on L2_GND to +2V5 on L5_PWR; pure, no reference continues across; stitching none, 83.3 mm of track past the via on BOTTOM: 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. +2V5 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.
- '/R_IO5' at (99.56, -69.41), TOP -> L4: GND on L2_GND to GND on L3, +2V5 on L5_PWR; partial, GND continues through a via of GND 4.72 mm away; stitching none, 71.9 mm of track past the via on L4: 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. +2V5 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.
- '/R_IO0' at (128.13, -92.39), TOP -> BOTTOM: GND on L2_GND to +2V5 on L5_PWR; pure, no reference continues across; stitching none, 65.2 mm of track past the via on BOTTOM: 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. +2V5 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.
- '/R_IO4' at (99.95, -84.77), TOP -> BOTTOM: GND on L2_GND to +2V5 on L5_PWR; pure, no reference continues across; stitching none, 55.3 mm of track past the via on BOTTOM: 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. +2V5 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.
- '/RTM_SHARED_BUS3' at (188.97, -72.46), TOP -> L4: GND on L2_GND to GND on L3, +2V5 on L5_PWR; partial, GND continues through a via of GND 8.71 mm away; stitching none, 40.3 mm of track past the via on L4: 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. +2V5 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 37 more
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/81/reference-planes?group=refchange%3A%2B2V5%7CGND serves each with its own layer_image region; all of them lie in x 97.56..195.92, y -94.39..-59.03 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.
At refchange:+2V5|GND
- BomLayoutMismatchmajorOpen
BomLayoutMismatch: 3 components×3
Checked by the review, stands · evaluation@esharp.se — NUT1, NUT2 (BOSSARD M3 hex nuts, "Fasteners & Fixings") and ST1 (SAMTEC SNT-100-RD-G closed jumper shunt, "Accessories") are loose hardware lines in the source BOM (ohwr/output/mdior/mdior-bom.csv) with no copper footprint, so the layout has nothing to place. The mismatch is real but describes assembly hardware, not a missing part; left for the owner.
At NUT1, NUT2, ST1
Each finding, with its own headline
- NUT1BOM refdes 'NUT1' is not placed in the layout.
- NUT2BOM refdes 'NUT2' is not placed in the layout.
- ST1BOM refdes 'ST1' is not placed in the layout.
- CapVoltageDeratingmajorOpen
CapVoltageDerating: 2 components×2
2 checked by the review by Claude walker W4 (Cern session) — 2 different reasons
At C34, C35
Each finding, with its own headline
C34C34 sits on a 12 V rail and its voltage rating is not in the BOM
C34: 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.
C35C35 sits on a 12 V rail and its voltage rating is not in the BOM
C35: 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.
- DecapOrdermajorOpen
IC39 supply pin 5 on '+12V': the smallest capacitor C34 sits 3.3 mm away, behind C35 at 2.0 mm
IC39 supply pin 5 on '+12V': the smallest capacitor C34 sits 3.3 mm away, behind C35 at 2.0 mm. IC39.5: the smallest value, C34 (100 nF), is 3.3 mm from the pin and C35 (10 uF) 2.0 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 IC39.5
- PartLifecyclemajorOpen
PartLifecycle: 2 part numbers×2
2 Obsolete · on 5 placements
At D14, IC39
Each finding, with its own headline
D14BAT54S on 4 placements (D14, D17, D18, D3): the distributor catalogue reports "Obsolete" for onsemi's BAT54S
BAT54S on 4 placements (D14, D17, D18, D3): the distributor catalogue reports "Obsolete" for onsemi's BAT54S — a sourcing/longevity risk to confirm against the MANUFACTURER before acting. This board's BOM names 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/BAT54S/providers (which provider said it, the maker and part number it matched, its own words, and when we asked). THE LAST BUY DATE HAS PASSED (2018-11-23, 2,914 day(s) ago), so this is a substitution rather than a buy. The distributor reports NONE left. No approved alternate is recorded for this position.
IC39LM2736XMK on IC39: the distributor catalogue reports "Obsolete" for Texas Instruments's LM2736XMK
LM2736XMK on IC39: the distributor catalogue reports "Obsolete" for Texas Instruments's LM2736XMK — 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/LM2736XMK/providers (which provider said it, the maker and part number it matched, its own words, and when we asked). THE LAST BUY DATE HAS PASSED (2024-09-21, 785 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.
- ReferencePlaneDiscontinuitymajorOpen
ReferencePlaneDiscontinuity: 4 boards×4
4 checked by the review by Claude walker W4 (Cern session) — 4 different reasons
At along@L5_PWR:+2V5|+5V, refchange:+5V|GND, split@L5_PWR:+2V5|+5V, void:routed@L3|L4
Each finding, with its own headline
along@L5_PWR:+2V5|+5V2 nets run ALONG the split between the +2V5 and +5V planes on L5_PWR at 2 places, the longest 19.95 mm; the impedance rises from 53 ohm to 99 ohm there at worst, 30.4 % of each edge reflected (fastest: /RTM_SHARED_BUS3 at 100 ps 10-90 %, ASSUMED)
On L5_PWR the +2V5 and +5V planes part, and 2 nets run down the slot between them at 2 place(s), rather than across it. This is not a crossing: the return still follows the track, in the plane on its other side and in the slot's edges, so it does not detour. What changes is the track's own impedance. With the plane gone from under it on this side for that length, its field reaches further, to the slot's edges and to the next plane beyond, so its capacitance falls and its impedance rises; every edge travelling down it is partly reflected where it enters the stretch and again where it leaves, by (Z2 - Z1)/(Z2 + Z1). The longer the stretch against the edge's rise, the more of the edge sees the full step. A crossing is generally the worse fault; a mismatch is not free. Over solid plane each track is 53 ohm; along the slot 64 ohm to 99 ohm, reflecting up to 30.4 % 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 104 ohm). No place stays within 10 %, the tolerance controlled impedance is commonly built to (the stackup states none), 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.
- '/R_IO3' on BOTTOM at (106.74, -103.32), 21.49 mm, running ALONG the split for 19.95 mm, not across it, 53 ohm over solid plane, 99 ohm along it: 30.4 % of each edge reflected; other side: none: the signal layer is outermost
- '/RTM_SHARED_BUS3' on BOTTOM at (111.88, -101.79), 7.14 mm, running ALONG the split for 7.11 mm, not across it, 53 ohm over solid plane, 64 ohm along it: 9.7 % of each edge reflected; other side: none: the signal layer is outermost
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/81/reference-planes?group=along%40L5_PWR%3A%2B2V5%7C%2B5V serves each with its own layer_image region; all of them lie in x 95..118.49, y -104.32..-100.77 mm (board frame, Y up).
Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.
refchange:+5V|GND3 nets change reference between +5V and GND at 3 vias; 1 of them partial (fastest: /RTM_SHARED_BUS1 at 100 ps 10-90 %, ASSUMED)
At 3 via(s), on 3 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: 3 with none. 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 +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. 1 of them are partial: another reference continues across through a stitching via of its net, so only part of the return has nowhere to go. The pure ones are listed first, then the partial ones with the farthest stitching via first.
- '/bus_ready_n' at (76.44, -79.57), TOP -> BOTTOM: GND on L2_GND to +5V on L5_PWR; pure, no reference continues across; stitching none, 128.3 mm of track past the via on BOTTOM: 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.
- '/R_IO3' at (71.24, -101.28), L4 -> BOTTOM: GND on L3 to +5V on L5_PWR; pure, no reference continues across; stitching none, 126.7 mm of track past the via on BOTTOM: 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. +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.
- '/RTM_SHARED_BUS1' at (89.4, -95.95), L3 -> L4: GND on L2_GND, GND on L4 to GND on L3, +5V on L5_PWR; partial, GND continues through a via of GND 9.38 mm away; stitching none, 35.5 mm of track past the via on L4: 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.
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/81/reference-planes?group=refchange%3A%2B5V%7CGND serves each with its own layer_image region; all of them lie in x 69.24..91.4, y -103.28..-77.57 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@L5_PWR:+2V5|+5V9 nets cross the split between the +2V5 and +5V planes on L5_PWR at 10 places; 2 with a plane on the track's other side (fastest: /RTM_SHARED_BUS0 at 100 ps 10-90 %, ASSUMED)
On L5_PWR the +2V5 and +5V planes part, and 9 nets cross from one to the other at 10 place(s). The return current cannot follow a track across; it detours to wherever the two planes are joined (a stitching capacitor, or the source), and the loop it opens radiates and couples. One decision covers the boundary: whether it is stitched near these crossings, or the nets crossing it are slow enough not to care. Tracks that run ALONG this split, down the slot rather than across it, are a finding of their own: theirs is an impedance step, not a detour. At 2 of the 10 crossing(s) the track's other neighbour carries a plane, which the return can use there; 8 are on an outer layer, with no other neighbour. 2 of the 10 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.
- '/RTM_SHARED_BUS2' on BOTTOM at (97.53, -95.06), 3.05 mm; other side: none: the signal layer is outermost
- '/RTM_SHARED_BUS3' on BOTTOM at (97.53, -97.09), 3.05 mm; other side: none: the signal layer is outermost
- '/R_IO0' on BOTTOM at (97.53, -93.16), 3.05 mm; other side: none: the signal layer is outermost
- '/R_IO1' on BOTTOM at (94.85, -91.04), 4.21 mm; other side: none: the signal layer is outermost
- '/R_IO2' on BOTTOM at (93.97, -90.53), 4.23 mm; other side: none: the signal layer is outermost
- '/R_IO4' on BOTTOM at (77.91, -77.92), 2.08 mm; other side: none: the signal layer is outermost
- '/R_IO4' on BOTTOM at (85.28, -84.34), 1.82 mm; other side: none: the signal layer is outermost
- '/bus_ready_n' on BOTTOM at (93.1, -90.02), 4.25 mm; other side: none: the signal layer is outermost
- '/RTM_SHARED_BUS0' on L4 at (96.95, -92.55), 2.69 mm; other side: GND on L3, 0.1 mm from the track against 0.53 mm to L5_PWR: 16% of the return on L5_PWR
- '/R_IO5' on L4 at (80.95, -59.8), 2.16 mm; other side: GND on L3, 0.1 mm from the track against 0.53 mm to L5_PWR: 16% of the return on L5_PWR
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/81/reference-planes?group=split%40L5_PWR%3A%2B2V5%7C%2B5V serves each with its own layer_image region; all of them lie in x 75.95..100.05, y -98.09..-58.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.
void:routed@L3|L4Tracks on L3 and L4 cross each other at 83 places, each layer the other's reference with its pour cleared round its own tracks, the longest 16.65 mm; 11 run ALONG the cut round another net's track (fastest: /RTM_SHARED_BUS0 at 100 ps 10-90 %, ASSUMED)
L3 and L4 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. 83 place(s) on 43 net(s), 71 of them seen from both tracks (each counted once). 11 of the crossings run ALONG the cut round another net's track rather than across it, parallel to its edges (the longest 14.95 mm): over or right beside that track, broadside to it as well as off the plane. One decision covers the layer pair: whether these layers may take a pour their own tracks cut as the reference, or the routing or the stackup should give the tracks a plane that is not cut where they cross. 0 of the 169 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.
- '/R_IO3' on L4 at (61.49, -101.28), 16.65 mm, running ALONG the bare copper for 14.95 mm, not across it over copper of Vext1, Vcc_PB, not a plane; other side: no plane on L5_PWR
- one crossing of two tracks, seen from each: '/R_IO5' on L4 at (65.39, -88.99), 7.42 mm, running ALONG the bare copper for 6.43 mm, not across it over copper of /R_IO6, not a plane; other side: no plane on L5_PWR / '/R_IO6' on L3 at (65.46, -88.98), 8.02 mm, running ALONG the bare copper for 6.54 mm, not across it over copper of /R_IO5, not a plane, to the end of the track; other side: GND on L2_GND, 0.53 mm from the track against 0.1 mm to L4: 84% of the return on L4
- '/RTM_SHARED_BUS0' on L4 at (52.15, -98.87), 5.64 mm, running ALONG the bare copper for 2 mm, not across it over copper of Vext1, not a plane; other side: no plane on L5_PWR
- one crossing of two tracks, seen from each: '/RTM_SHARED_BUS1' on L4 at (78.36, -97.22), 4.95 mm over copper of /R_IO8, /R_IO9, /R_IO7, /R_IO6, not a plane; other side: +5V on L5_PWR, 0.53 mm from the track against 0.1 mm to L3: 84% of the return on L3 / '/R_IO6' on L3 at (79.24, -97.41), 0.62 mm over copper of /RTM_SHARED_BUS1, not a plane; other side: GND on L2_GND, 0.53 mm from the track against 0.1 mm to L4: 84% of the return on L4 / '/R_IO7' on L3 at (77.65, -97.41), 0.88 mm over copper of /RTM_SHARED_BUS1, not a plane; other side: GND on L2_GND, 0.53 mm from the track against 0.1 mm to L4: 84% of the return on L4 / '/R_IO9' on L3 at (76.43, -97.41), 0.88 mm over copper of /RTM_SHARED_BUS1, not a plane; other side: GND on L2_GND, 0.53 mm from the track against 0.1 mm to L4: 84% of the return on L4
- '/R_IO3' on L4 at (51.51, -97.16), 4.92 mm, running ALONG the bare copper for 4 mm, not across it over copper of Vcc_PB, not a plane; other side: no plane on L5_PWR
- one crossing of two tracks, seen from each: '/output_channel1/interlock_nc' on L3 at (193.09, -78.7), 0.63 mm over copper of Net-(IC22-OUT), not a plane; other side: GND on L2_GND, 0.53 mm from the track against 0.1 mm to L4: 84% of the return on L4 / '/output_channel2/interlock_com' on L3 at (193.09, -77.85), 0.63 mm over copper of Net-(IC22-OUT), not a plane; other side: GND on L2_GND, 0.53 mm from the track against 0.1 mm to L4: 84% of the return on L4 / '/output_channel2/interlock_nc' on L3 at (193.09, -81.85), 0.63 mm over copper of Net-(IC22-OUT), not a plane; other side: GND on L2_GND, 0.53 mm from the track against 0.1 mm to L4: 84% of the return on L4 / 'Net-(IC22-OUT)' on L4 at (192.9, -80.28), 4.62 mm over copper of /output_channel2/interlock_nc, /output_channel1/interlock_nc, /output_channel2/interlock_com, not a plane; other side: +2V5 on L5_PWR, 0.53 mm from the track against 0.1 mm to L3: 84% of the return on L3
- '/R_IO8' on L3 at (67.55, -91.31), 4.35 mm, running ALONG the bare copper for 3.17 mm, not across it over copper of VIO_PB, not a plane, to the end of the track; other side: GND on L2_GND, 0.53 mm from the track against 0.1 mm to L4: 84% of the return on L4
- '/R_IO9' on L3 at (68.57, -90.98), 4.03 mm, running ALONG the bare copper for 2.96 mm, not across it over copper of VIO_PB, not a plane, to the end of the track; other side: GND on L2_GND, 0.53 mm from the track against 0.1 mm to L4: 84% of the return on L4
- one crossing of two tracks, seen from each: '/output_channel0/interlock_nc' on L3 at (171.25, -81.6), 0.62 mm over copper of Net-(IC20-OUT), not a plane; other side: GND on L2_GND, 0.53 mm from the track against 0.1 mm to L4: 84% of the return on L4 / '/output_channel1/interlock_nc' on L3 at (171.63, -78.7), 0.62 mm over copper of Net-(IC20-OUT), not a plane; other side: GND on L2_GND, 0.53 mm from the track against 0.1 mm to L4: 84% of the return on L4 / '/output_channel2/interlock_nc' on L3 at (171.63, -79.57), 0.62 mm over copper of Net-(IC20-OUT), not a plane; other side: GND on L2_GND, 0.53 mm from the track against 0.1 mm to L4: 84% of the return on L4 / 'Net-(IC20-OUT)' on L4 at (171.44, -80.59), 3.52 mm over copper of /output_channel0/interlock_nc, /output_channel2/interlock_nc, /output_channel1/interlock_nc, not a plane; other side: +2V5 on L5_PWR, 0.53 mm from the track against 0.1 mm to L3: 84% of the return on L3
- one crossing of two tracks, seen from each: '/RTM_SHARED_BUS0' on L4 at (78.54, -99.25), 3.42 mm over copper of /R_IO6, /R_IO7, /R_IO9, /R_IO8, not a plane; other side: +5V on L5_PWR, 0.53 mm from the track against 0.1 mm to L3: 84% of the return on L3 / '/R_IO6' on L3 at (79.24, -99.44), 0.63 mm over copper of /RTM_SHARED_BUS0, not a plane; other side: GND on L2_GND, 0.53 mm from the track against 0.1 mm to L4: 84% of the return on L4 / '/R_IO7' on L3 at (77.84, -99.44), 0.63 mm over copper of /RTM_SHARED_BUS0, not a plane; other side: GND on L2_GND, 0.53 mm from the track against 0.1 mm to L4: 84% of the return on L4 / '/R_IO9' on L3 at (77.21, -99.44), 0.63 mm over copper of /RTM_SHARED_BUS0, not a plane; other side: GND on L2_GND, 0.53 mm from the track against 0.1 mm to L4: 84% of the return on L4
- one crossing of two tracks, seen from each: '/input_channel0/input_anode' on L3 at (144, -86.72), 3.21 mm, running ALONG the bare copper for 2.18 mm, not across it over copper of Net-(IC17-Y), not a plane; other side: GND on L2_GND, 0.53 mm from the track against 0.1 mm to L4: 84% of the return on L4 / 'Net-(IC17-Y)' on L4 at (143.84, -86.43), 3.41 mm, running ALONG the bare copper for 2.23 mm, not across it over copper of /input_channel0/input_anode, not a plane, to the end of the track; other side: +2V5 on L5_PWR, 0.53 mm from the track against 0.1 mm to L3: 84% of the return on L3
- one crossing of two tracks, seen from each: '/RTM_SHARED_BUS3' on L4 at (178.3, -79.14), 2.71 mm over copper of /output_channel2/interlock_com, /output_channel2/interlock_nc, /output_channel1/interlock_nc, not a plane; other side: +2V5 on L5_PWR, 0.53 mm from the track against 0.1 mm to L3: 84% of the return on L3 / '/output_channel1/interlock_nc' on L3 at (178.11, -78.7), 0.63 mm over copper of /RTM_SHARED_BUS3, not a plane; other side: GND on L2_GND, 0.53 mm from the track against 0.1 mm to L4: 84% of the return on L4 / '/output_channel2/interlock_com' on L3 at (179.14, -77.85), 0.89 mm over copper of /RTM_SHARED_BUS3, not a plane; other side: GND on L2_GND, 0.53 mm from the track against 0.1 mm to L4: 84% of the return on L4 / '/output_channel2/interlock_nc' on L3 at (178.11, -79.57), 0.63 mm over copper of /RTM_SHARED_BUS3, not a plane; other side: GND on L2_GND, 0.53 mm from the track against 0.1 mm to L4: 84% of the return on L4
- and 71 more
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/81/reference-planes?group=void%3Arouted%40L3%7CL4 serves each with its own layer_image region; all of them lie in x 50.51..195.34, y -102.28..-65.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.
Schematic sheet 2: P3V3_PB power label overprinted by a GND label at the EEPROM (IC4) address straps
On schematic sheet 2 (base project connectors, EEPROM block), the P3V3_PB power-port label that feeds the 24AA025E48 IC4 VCC (pin 8) and A0 (pin 1) is drawn on top of the "GND" text of the ground symbol tying A1/A2 (pins 2/3). The two labels print over each other and read as one garbled word. The connectivity is correct; only the drawing is unreadable at that spot.
Where
- Sheet 2 of 13, "DI/OT Mixed Digital IO RTM - base project connectors", EEPROM box "2kB EEPROM with EUI-48 Node Identity", lower-left of IC4.
- The netlist confirms the intended ties: IC4.1 (A0) and IC4.8 (VCC) on P3V3_PB; IC4.2 (A1) and IC4.3 (A2) on GND.
Why it matters
A reader checking the EEPROM address from the drawing cannot tell which strap goes to which rail at that spot, and the address (0x51) depends on exactly those three pins. It is a cosmetic fix: move the power-port or the ground symbol so the labels don't overlap.
Not a connectivity defect
The ODB netlist carries the correct nets, so the board as built is unaffected.
Schematic sheet 7: TPS73001 (IC1) output voltage set by R1/R3 is not annotated, so VIO_PB's local-LDO option has no stated value
The adjustable LDO IC1 (TPS73001) sets its output with R1 31k6 / R3 30k, but sheet 7 states neither the output voltage nor the divider equation, and the output net has no rail name. That output is one of the two sources the solder jumper SW1 can select for VIO_PB, the I/O reference supply sent to the backplane on J1 H4/I4. A reader has to work out from the datasheet that this option gives about 2.52 V. The companion buck (LM2736, R49/R50) is labelled "+5V", and sheet 3 annotates its monostable timing ("T=R*C"), so this is the one derived value on the power sheet left unstated.
Derived value
Quantity Source Value VREF (TPS73001) datasheet p.17 Eq.1 1.225 V typ R1 / R3 BOM / sheet 7 31.6 kΩ / 30 kΩ VOUT = VREF x (1 + R1/R3) computed 2.515 V Rail name on Net-(IC1-OUT) sheet 7 none What sits between
``
mermaid flowchart LR P5["+5V (LM2736)"] --> IC1["IC1 TPS73001<br/>R1 31k6 / R3 30k"] IC1 -->|"Net-(IC1-OUT), unlabelled"| SW1["SW1 solder jumper pad 3"] P25["+2V5"] --> SW1b["SW1 pad 2"] SW1 --> VIO["VIO_PB"] SW1b --> VIO VIO --> J1["J1 H4/I4 to backplane"]``Suggested fix
Add a rail name (e.g. +2V5_LDO) or a note "VOUT = 1.225 V x (1 + R1/R3) = 2.52 V" beside IC1, and say which SW1 position is the default.
+5V start-up: LM2736 (IC39) soft-start asks about 1.8 A to charge 72 µF, above its 1.0 A minimum switch current limit
The +5V rail from the LM2736 buck (IC39) carries about 72 µF of ceramic capacitance. Charging that along the part's fixed 200 µs soft-start ramp needs about 1.8 A, which exceeds the switch current limit (1.0 A minimum, 1.5 A typical). The start-up will therefore not follow soft-start: the converter runs in cycle-by-cycle current limit until the rail is charged. The limit is cycle-by-cycle, not latching or hiccup, so this should lengthen the ramp to roughly 0.25-0.4 ms rather than stop start-up. It is a margin issue, not a failure: the soft-start the designer is relying on for controlled inrush is not what governs this rail.
Numbers
Quantity Source Value Output capacitance on +5V (nominal) netlist + BOM: C37 22 µF, C1/C38/C40/C42/C44 10 µF, C39/C41/C43/C45 100 nF 72.4 µF Soft-start time LM2736 datasheet p.10 ≈ 200 µs Required charging current C·V/t computed, 72.4 µF × 5 V / 200 µs ≈ 1.81 A Same, with a pessimistic ~35% DC-bias loss (≈ 47 µF) estimate ≈ 1.2 A Switch current limit datasheet p.5 (min / typ / max) 1.0 / 1.5 / 2.3 A Margin at minimum limit −0.2 to −0.8 A (limit exceeded) Start-up load adds to this: the TPS73001 LDO (IC1) also starts on +5V and charges its own 10 µF output at up to its current limit.
What sits between
``
mermaid flowchart LR V12["+12V via F1 500 mA"] --> IC39["IC39 LM2736<br/>soft-start ≈200 µs<br/>I_CL min 1.0 A"] IC39 --> L1["L1 4.7 µH"] L1 --> R5V["+5V"] R5V --> C["C37 22 µF + 5× 10 µF + 4× 100 nF"] R5V --> IC1["IC1 TPS73001 (C3 10 µF)"] R5V --> DRV["IC42-IC45 UCC27517 VDD"]``Why it is only minor
- The datasheet's limit is cycle-by-cycle (p.9, §7.3.3), so exceeding it clips each switching cycle; it does not trip a latch.
- Worth checking on hardware: +5V overshoot when the ramp ends in current limit (output OVP at +10% will act), and whether L1 stays out of saturation at the 1.5-2.3 A limit peak. L1's saturation current is not on file.
GP-output TVS D19-D22 clamp to Chassis, but the LEMO return is GND, linked to Chassis only through C46 1 nF
The GP-output TVS diodes D19-D22 return to Chassis, while the LEMO outputs they protect (LM2, LM3) carry their return on GND; the two nets meet only through C46 (1 nF), so the clamp current has no direct path back to the connector it came in on.
What is wired
Item Net / value Source D19, D20, D21, D22 (PESD24VL1BA) signal side on Net-(IC4x-OUT), other side on Chassis netlist Series resistor, connector side of the TVS R76-R79, 10 ohm 2512 netlist LEMO return (LM2.3, LM3.3) GND netlist; sheet 1 "GP Outputs" Chassis to GND C46 1 nF 2 kV; R64 10 M drawn crossed out (not fitted) sheet 1 "ESD discharge path" J3 D-sub shell (pins 8, 16, 17) Chassis netlist ``
mermaid graph LR LEMO[LM2/LM3 centre] --> R[R76-R79 10R] --> N[IC42-45 OUT] N --> TVS[D19-D22] --> CH[Chassis] CH -- C46 1nF --> GND LEMOS[LM2/LM3 shell] --> GND``Why it matters
A discharge on a GP-output centre pin is referenced to the LEMO shell (GND). The TVS sends it to Chassis, and from there it can reach GND only through C46. During the event the UCC27517A output, which is directly on the node and returns to GND, takes a share of it through 10 ohm. The D-sub J3 TVS (D1-D13) return to Chassis, which is right there, because J3's shell is Chassis.
What would settle it
Whether the LEMO bodies are bonded to the front panel (Chassis) in the assembly. If they are, GND and Chassis meet at the panel and this is benign; if the LEMOs are isolated, returning D19-D22 to GND (or adding a local GND-Chassis path) would give the clamp a direct return.
J3 front-panel TVS (D1-D13) sit beside the optoMOS parts up to ~100 mm from the D-sub, returned to Chassis by one thin daisy-chained top-layer track
The PESD24VL1BA diodes on the J3 D-sub lines are placed next to the parts they protect, 8-101 mm from J3, and their Chassis side appears to be one thin top-layer track chained from TVS pair to TVS pair back to the connector, so a discharge travels the full length of the line in and the full length of that track back.
Placement (pad-to-pad, straight line)
TVS Line to J3 pin Protected part part to J3 D1 input_channel0 cathode 101.0 mm (J3.9) IC2 CPC1020N 103.3 mm D2 input_channel0 anode 96.5 mm (J3.1) R4 1k 96.7 mm D12 / D13 input_channel1 98.2 / 93.3 mm IC9 / R32 100.4 mm D4 / D5 output_channel0 interlock 75.2 / 70.6 mm IC5 / R9 77.3 / 70.8 mm D6 / D7 output_channel1 53.7 / 49.1 mm IC6 / R10 D8 / D9 output_channel2 32.2 / 27.7 mm IC7 / R11 D10 / D11 output_channel3 11.4 / 8.1 mm IC8 / R12 13.1 / 9.6 mm Source: component pad coordinates in the layout (get_component). Each TVS is about 2 mm nearer J3 than its part, so the order connector, TVS, part holds; the TVS is at the part, not at the connector.
Return
The Chassis net is J3's shell (pins 8, 16, 17), the mounting holes B1/B3 and a copper strip on L5_PWR along the panel edge. On the TOP/BOTTOM copper render (x 95-215, y -90..-55) a single thin top-layer track runs from D1/D2 down to D12/D13 and then along D4/D5, D6/D7, D8/D9, D10/D11 to J3, which is consistent with the TVS Chassis pads being daisy-chained on it. The bottom layer there is a GND pour, not Chassis.
Why it matters
A TVS works against the inductance between it and the connector return. With the clamp ~100 mm from the shell and its return on one narrow track, the voltage the CPC1020N and the input optocoupler see during an IEC 61000-4-2 event is the clamp plus the drop along both runs. The parts behind are isolated switches and opto inputs, which are fairly robust, so this is a layout-quality point, not a demonstrated failure.
The track identification is read from the picture and the net's feature list, not from a net-highlighted render; a reviewer with the KiCad layout can confirm it in a minute.
- ConnectorDomainMixedminorOpen
J1 takes 3 different supplies off the board on one connector: Vcc_PB (12.0 V), Vext1 (12.0 V), P3V3_PB (3.3 V)
J1 carries 3 different supplies out of the board on one connector: Vcc_PB (12.0 V) on A3/B3, Vext1 (12.0 V) on A1/B1/D1/E1, P3V3_PB (3.3 V) on D3. 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 J1
- ReferencePlaneDiscontinuityminorOpen
ReferencePlaneDiscontinuity: 2 boards×2
2 checked by the review by Claude walker W4 (Cern session) — 2 different reasons
At void:GND@L2_GND:77.21,-120.46, void:GND@L4:65.92,-89.31
Each finding, with its own headline
void:GND@L2_GND:77.21,-120.46'/R_IO9' crosses where the outline of the GND plane on L2_GND and the GND plane on L4 is drawn back, at 1 place, the longest 0.4 mm; 1 cleared on both sides of the track (fastest: /R_IO9 at 2 ns 10-90 %, suggested by its name)
Along '/R_IO9' on L3, the GND plane on L4 has 0.4 mm under the track with no copper, at (77.21, -120.46), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 51.14..210.1, y -150.11..-51.11 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. 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: '/R_IO9' on L3 at (77.21, -120.46), 0.39 mm over no copper; other side: no plane on L4 / '/R_IO9' on L3 at (77.21, -120.46), 0.4 mm over no copper; other side: no plane on L2_GND
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/81/reference-planes?group=void%3AGND%40L2_GND%3A77.21%2C-120.46 serves each with its own layer_image region; all of them lie in x 76.21..78.21, y -121.66..-119.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.
void:GND@L4:65.92,-89.31'/R_IO7' crosses where the outline of the GND plane on L4 is drawn back, at 1 place, the longest 2.58 mm (fastest: /R_IO7 at 2 ns 10-90 %, suggested by its name)
Along '/R_IO7' on L3, the GND plane on L4 has 2.58 mm under the track with no copper, at (65.92, -89.31), 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.58 mm). No hole cleared it: the outline of the pour at x 51.14..210.1, y -150.11..-51.11 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. 0 of the 1 crossing(s) have a plane on the track's other side at most twice as far away as the broken one (to first order each plane beside a stripline carries a share of the return inversely proportional to its distance from the track). The rest leave most or all of the return to the break, so the finding is a warning.
- '/R_IO7' on L3 at (65.92, -89.31), 2.58 mm, running ALONG the bare copper for 2.58 mm, not across it over no copper; other side: GND on L2_GND, 0.53 mm from the track against 0.1 mm to L4: 84% of the return on L4
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/81/reference-planes?group=void%3AGND%40L4%3A65.92%2C-89.31 serves each with its own layer_image region; all of them lie in x 63.63..68.21, y -90.31..-88.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.
About this design
- Design
- MDIOR — OHWR0081 R1
- Designed in
- KiCad EDA
- Board
- 6 copper layers, 160 × 100 mm, 226 components, 242 nets
- Licence
- CERN-OHL-W-2.0
- Source
- https://gitlab.com/ohwr/project/mdior at commit
cac6b1bcb86d - Attribution
- CERN Open Hardware Repository, project ohwr/project/mdior (commit cac6b1bcb86ddbd2baab95120e12ea747770830a, 2026-03-03). Licence: CERN-OHL-W-2.0. Source: https://gitlab.com/ohwr/project/mdior. 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)