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

PDA 8CH

OHWR0070 · revision R1

PDA 8CH (OHWR0070 R1) is an open-hardware circuit board from the CERN Open Hardware Repository, designed in KiCad EDA: a 2-layer board of 170 × 70 mm with 268 components and 64 nets, published under CERN-OHL-1.2.

review 89% walked · 5 findings: 4 major · 1 minor (18 items)

Open in the interactive viewerRead the full review

PDA 8CH (OHWR0070 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 5 findings: 4 major · 1 minor (18 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. observationOBS-265majorOpen

    LT1963A feedback divider values swapped between schematic and PCB/BOM: +3V3 would regulate to about 1.9 V

    The LT1963A (U301) feedback divider values are swapped between the schematic and the PCB/BOM: built to the PCB/BOM, +3V3 regulates to about 1.92 V instead of 3.31 V.

    Schematic versus PCB/BOM

    ResistorPositionSchematic (PDA_PSU_2017.04.kicad_sch)PCB / designer BOM (BOM_PDA_2017.04.html)Source
    R401upper: pin 1 on +3V3 (U301 pin 4 OUT), pin 2 on the ADJ node Net-(R401-Pad2) (U301 pin 5)6k83k92commit 911c25f
    R402lower: ADJ node to GND3k926k8commit 911c25f

    The schematic note on page 2 (PSU) reads: Vout = 1.21 V (1 + R2/R1) + I_ADJ * R2, 6k8 / 3k9, R2/R1 = 5k / 2k9 gives 3.31V.

    The output as built

    QuantityValueSource
    ADJ pin voltage1.21 V referenced to groundLT1963A datasheet, p.13
    ADJ bias current3 uA into the pinLT1963A datasheet, p.13
    Output with R401 = 3k92, R402 = 6k81.21 V x (1 + 3.92k/6.8k) + 3 uA x 3.92k = about 1.92 Vderived
    Intended output3.31 Vschematic sheet note

    Why it matters

    The +3V3 rail supplies the LT1711 comparator, the LT1790 reference, the LTC6993 one-shot and all nine 5PB1108 buffers. At about 1.9 V the LT1790-1.25 reference loses headroom, and the 3.3 V LVCMOS pulse outputs are far below their intended swing.

    The schematic note shows the intent, so the PCB/BOM values look out of sync with the schematic rather than a deliberate change. Needs a person to check a built unit or the fitted resistors.

  2. CapVoltageDeratingmajorOpen

    CapVoltageDerating: 2 components×2

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

    At C401, C404

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

      C401: on a 8.55 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.

    • C404C404 sits on a 8.55 V rail and its voltage rating is not in the BOM

      C404: on a 8.55 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.

  3. ReferencePlaneDiscontinuitymajorOpen

    ReferencePlaneDiscontinuity: 13 boards×13

    e.g. “'Net-(J101-Pad1)' crosses where the outline of the GND plane on B.CU is drawn back, at 1 place, the longest 1.02 mm (fastest: Net-(J101-Pad1) at 100 ps 10-90 %, ASSUMED)” · 13 different statements

    At void:GND@B.CU:101,-65.2, void:GND@B.CU:116.78,-68.17, void:GND@B.CU:133.22,-68.17, void:GND@B.CU:139.5,-95.52, void:GND@B.CU:140.59,-97.09, void:GND@B.CU:148.78,-68.17 and 7 more

    Each finding, with its own headline
    • void:GND@B.CU:101,-65.2'Net-(J101-Pad1)' crosses where the outline of the GND plane on B.CU is drawn back, at 1 place, the longest 1.02 mm (fastest: Net-(J101-Pad1) at 100 ps 10-90 %, ASSUMED)

      Along 'Net-(J101-Pad1)' on F.CU, the GND plane on B.CU has 1.02 mm under the track with no copper, at (101, -65.2), 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 80.08..249.92, y -124.92..-55.08 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • 'Net-(J101-Pad1)' on F.CU at (101, -65.2), 1.02 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/71/reference-planes?group=void%3AGND%40B.CU%3A101%2C-65.2 serves each with its own layer_image region; all of them lie in x 100..102, y -69.46..-63.94 mm (board frame, Y up).

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

    • void:GND@B.CU:116.78,-68.17'Net-(J203-Pad1)' crosses where the outline of the GND plane on B.CU is drawn back, at 1 place, the longest 2.72 mm (fastest: Net-(J203-Pad1) at 100 ps 10-90 %, ASSUMED)

      Along 'Net-(J203-Pad1)' on F.CU, the GND plane on B.CU has 2.72 mm under the track with no copper, at (116.78, -68.17), 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 80.08..249.92, y -124.92..-55.08 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • 'Net-(J203-Pad1)' on F.CU at (116.78, -68.17), 2.72 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/71/reference-planes?group=void%3AGND%40B.CU%3A116.78%2C-68.17 serves each with its own layer_image region; all of them lie in x 115.57..118.74, y -69.42..-63.94 mm (board frame, Y up).

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

    • void:GND@B.CU:133.22,-68.17'Net-(J201-Pad1)' crosses where the outline of the GND plane on B.CU is drawn back, at 1 place, the longest 2.28 mm (fastest: Net-(J201-Pad1) at 100 ps 10-90 %, ASSUMED)

      Along 'Net-(J201-Pad1)' on F.CU, the GND plane on B.CU has 2.28 mm under the track with no copper, at (133.22, -68.17), 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 80.08..249.92, y -124.92..-55.08 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • 'Net-(J201-Pad1)' on F.CU at (133.22, -68.17), 2.28 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/71/reference-planes?group=void%3AGND%40B.CU%3A133.22%2C-68.17 serves each with its own layer_image region; all of them lie in x 131.6..134.43, y -69.42..-63.94 mm (board frame, Y up).

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

    • void:GND@B.CU:139.5,-95.52'/op2' crosses where the outline of the GND plane on B.CU is drawn back, at 1 place, the longest 1.45 mm (fastest: /op2 at 100 ps 10-90 %, ASSUMED)

      Along '/op2' on F.CU, the GND plane on B.CU has 1.45 mm under the track with no copper, at (139.5, -95.52), 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 80.08..249.92, y -124.92..-55.08 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/op2' on F.CU at (139.5, -95.52), 1.45 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/71/reference-planes?group=void%3AGND%40B.CU%3A139.5%2C-95.52 serves each with its own layer_image region; all of them lie in x 138.32..140.78, y -96.7..-93.75 mm (board frame, Y up).

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

    • void:GND@B.CU:140.59,-97.09'/op2' crosses where the outline of the GND plane on B.CU is drawn back, at 1 place, the longest 1.06 mm (fastest: /op2 at 100 ps 10-90 %, ASSUMED)

      Along '/op2' on F.CU, the GND plane on B.CU has 1.06 mm under the track with no copper, at (140.59, -97.09), 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 80.08..249.92, y -124.92..-55.08 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/op2' on F.CU at (140.59, -97.09), 1.06 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/71/reference-planes?group=void%3AGND%40B.CU%3A140.59%2C-97.09 serves each with its own layer_image region; all of them lie in x 139.4..141.68, y -98.18..-95.32 mm (board frame, Y up).

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

    • void:GND@B.CU:148.78,-68.17'Net-(J401-Pad1)' crosses where the outline of the GND plane on B.CU is drawn back, at 1 place, the longest 2.72 mm (fastest: Net-(J401-Pad1) at 100 ps 10-90 %, ASSUMED)

      Along 'Net-(J401-Pad1)' on F.CU, the GND plane on B.CU has 2.72 mm under the track with no copper, at (148.78, -68.17), 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 80.08..249.92, y -124.92..-55.08 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • 'Net-(J401-Pad1)' on F.CU at (148.78, -68.17), 2.72 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/71/reference-planes?group=void%3AGND%40B.CU%3A148.78%2C-68.17 serves each with its own layer_image region; all of them lie in x 147.57..150.74, y -69.42..-63.94 mm (board frame, Y up).

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

    • void:GND@B.CU:164.78,-68.17'Net-(J403-Pad1)' crosses where the outline of the GND plane on B.CU is drawn back, at 1 place, the longest 2.72 mm (fastest: Net-(J403-Pad1) at 100 ps 10-90 %, ASSUMED)

      Along 'Net-(J403-Pad1)' on F.CU, the GND plane on B.CU has 2.72 mm under the track with no copper, at (164.78, -68.17), 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 80.08..249.92, y -124.92..-55.08 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • 'Net-(J403-Pad1)' on F.CU at (164.78, -68.17), 2.72 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/71/reference-planes?group=void%3AGND%40B.CU%3A164.78%2C-68.17 serves each with its own layer_image region; all of them lie in x 163.57..166.74, y -69.42..-63.94 mm (board frame, Y up).

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

    • void:GND@B.CU:180.78,-68.17'Net-(J503-Pad1)' crosses where the outline of the GND plane on B.CU is drawn back, at 1 place, the longest 2.2 mm (fastest: Net-(J503-Pad1) at 100 ps 10-90 %, ASSUMED)

      Along 'Net-(J503-Pad1)' on F.CU, the GND plane on B.CU has 2.2 mm under the track with no copper, at (180.78, -68.17), 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 80.08..249.92, y -124.92..-55.08 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • 'Net-(J503-Pad1)' on F.CU at (180.78, -68.17), 2.2 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/71/reference-planes?group=void%3AGND%40B.CU%3A180.78%2C-68.17 serves each with its own layer_image region; all of them lie in x 179.57..182.74, y -69.42..-63.94 mm (board frame, Y up).

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

    • void:GND@B.CU:193.59,-94.68'/op6' crosses where the outline of the GND plane on B.CU is drawn back, at 1 place, the longest 1.01 mm (fastest: /op6 at 100 ps 10-90 %, ASSUMED)

      Along '/op6' on F.CU, the GND plane on B.CU has 1.01 mm under the track with no copper, at (193.59, -94.68), 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 80.08..249.92, y -124.92..-55.08 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • '/op6' on F.CU at (193.59, -94.68), 1.01 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/71/reference-planes?group=void%3AGND%40B.CU%3A193.59%2C-94.68 serves each with its own layer_image region; all of them lie in x 192.4..194.68, y -95.77..-93 mm (board frame, Y up).

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

    • void:GND@B.CU:196.78,-68.17'Net-(J501-Pad1)' crosses where the outline of the GND plane on B.CU is drawn back, at 1 place, the longest 2.72 mm (fastest: Net-(J501-Pad1) at 100 ps 10-90 %, ASSUMED)

      Along 'Net-(J501-Pad1)' on F.CU, the GND plane on B.CU has 2.72 mm under the track with no copper, at (196.78, -68.17), 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 80.08..249.92, y -124.92..-55.08 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • 'Net-(J501-Pad1)' on F.CU at (196.78, -68.17), 2.72 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/71/reference-planes?group=void%3AGND%40B.CU%3A196.78%2C-68.17 serves each with its own layer_image region; all of them lie in x 195.57..198.74, y -69.42..-63.94 mm (board frame, Y up).

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

    • void:GND@B.CU:212.78,-68.17'Net-(J603-Pad1)' crosses where the outline of the GND plane on B.CU is drawn back, at 1 place, the longest 2.72 mm (fastest: Net-(J603-Pad1) at 100 ps 10-90 %, ASSUMED)

      Along 'Net-(J603-Pad1)' on F.CU, the GND plane on B.CU has 2.72 mm under the track with no copper, at (212.78, -68.17), 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 80.08..249.92, y -124.92..-55.08 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • 'Net-(J603-Pad1)' on F.CU at (212.78, -68.17), 2.72 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/71/reference-planes?group=void%3AGND%40B.CU%3A212.78%2C-68.17 serves each with its own layer_image region; all of them lie in x 211.57..214.74, y -69.42..-63.94 mm (board frame, Y up).

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

    • void:GND@B.CU:228.78,-68.17'Net-(J601-Pad1)' crosses where the outline of the GND plane on B.CU is drawn back, at 1 place, the longest 2.72 mm (fastest: Net-(J601-Pad1) at 100 ps 10-90 %, ASSUMED)

      Along 'Net-(J601-Pad1)' on F.CU, the GND plane on B.CU has 2.72 mm under the track with no copper, at (228.78, -68.17), 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 80.08..249.92, y -124.92..-55.08 is drawn back there. One decision covers the void: whether these tracks may cross it, or the plane should be filled under them. No crossing has a plane on the track's other side, so the whole return meets the break.

      • 'Net-(J601-Pad1)' on F.CU at (228.78, -68.17), 2.72 mm over no copper; other side: none: the signal layer is outermost

      Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/71/reference-planes?group=void%3AGND%40B.CU%3A228.78%2C-68.17 serves each with its own layer_image region; all of them lie in x 227.57..230.74, y -69.42..-63.94 mm (board frame, Y up).

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

    • void:routed@B.CU|F.CU11 nets on F.CU cross the tracks routed through the GND pour on B.CU at 58 places, the longest 4.78 mm; 4 run ALONG the cut round another net's track (fastest: /1PPS_Blink at 100 ps 10-90 %, ASSUMED)

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

      • '/op4' on F.CU at (171.05, -89.5), 4.78 mm, running ALONG the bare copper for 2.95 mm, not across it over copper of +3V3, not a plane; other side: none: the signal layer is outermost
      • '/op5' on F.CU at (186.45, -85.5), 4.75 mm, running ALONG the bare copper for 2.98 mm, not across it over copper of +3V3, not a plane; other side: none: the signal layer is outermost
      • '/op3' on F.CU at (154.55, -95.53), 3.44 mm, running ALONG the bare copper for 1.6 mm, not across it over copper of +3V3, not a plane; other side: none: the signal layer is outermost
      • '/op5' on F.CU at (187.51, -93.51), 3.24 mm over copper of +3V3, not a plane; other side: none: the signal layer is outermost
      • '/op6' on F.CU at (187.05, -96.05), 3.21 mm, running ALONG the bare copper for 1.4 mm, not across it over copper of +3V3, not a plane; other side: none: the signal layer is outermost
      • '/op7' on F.CU at (208.57, -93.63), 2.77 mm over copper of +3V3, not a plane; other side: none: the signal layer is outermost
      • 'Net-(R107-Pad2)' on F.CU at (89.43, -76.43), 2.13 mm over copper of +3V3, not a plane; other side: none: the signal layer is outermost
      • '/1PPS_IN' on F.CU at (125.61, -100.5), 1.94 mm over copper of +3V3, not a plane; other side: none: the signal layer is outermost
      • '/op8' on F.CU at (218.57, -92.66), 1.93 mm over copper of +3V3, not a plane; other side: none: the signal layer is outermost
      • '/1PPS_Blink' on F.CU at (89.43, -87.43), 1.92 mm over copper of +3V3, not a plane; other side: none: the signal layer is outermost
      • '/1PPS_IN' on F.CU at (107.57, -94.57), 1.92 mm over copper of +3V3, not a plane; other side: none: the signal layer is outermost
      • '/op1' on F.CU at (123.43, -92), 1.92 mm over copper of +3V3, not a plane; other side: none: the signal layer is outermost
      • and 46 more

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

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

  4. FiducialMissingmajorOpen

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

    The top side carries 77 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-264minorOpen

    R102 and R103 (VREF to trigger divider) have no resistance value in the BOM or PCB

    R102 and R103, the VREF-to-trigger divider that sets the LT1711 comparator threshold, have no resistance value in the BOM or PCB, so the trigger threshold cannot be built from the released BOM.

    • R102 (0805): VREF to /Vtrig, value "R"
    • R103 (0805): /Vtrig to GND, value "R"

    The schematic only shows ratio labels. The divider sets the threshold from the 1.25 V LT1790 reference; without values an assembler must guess. The schematic ratio (about 1 V intended) should be turned into real values. Documentation issue, no electrical fault shown.

Main parts

Part numberMakerDescriptionWhere
BAT54S-SOT-23D101
LT1711U102
LT1790U101
LT1963AU301
LTC6993U103
IDT5PB1108U104, U201, U202, U401, U402, U501 and 3 more

About this design

Design
PDA 8CH — OHWR0070 R1
Designed in
KiCad EDA
Board
2 copper layers, 170 × 70 mm, 268 components, 64 nets
Licence
CERN-OHL-1.2
Source
https://gitlab.com/ohwr/project/pda-8ch-fda-8ch at commit 911c25f444c6
Attribution
CERN Open Hardware Repository, project ohwr/project/pda-8ch-fda-8ch (commit 911c25f444c6630dac731f8eacf6c6b89fd4a4c7, 2025-04-09). Licence: CERN-OHL-1.2. Source: https://gitlab.com/ohwr/project/pda-8ch-fda-8ch. 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)