MICROSTEPPER OCXO
OHWR0079 · revision R1
MICROSTEPPER OCXO (OHWR0079 R1) is an open-hardware circuit board from the CERN Open Hardware Repository, designed in KiCad EDA: a 2-layer board of 100 × 100 mm with 192 components and 107 nets, published under CERN-OHL-S-2.0.
review 93% walked · 8 findings: 4 major · 4 minor (13 items)
Open in the interactive viewerRead the full review

Design review
Probe recorded 8 findings: 4 major · 4 minor (13 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.
OCXO board: V_OCXO regulator U703 is set to about 2.4-2.5 V (R701 = R702 = 37k4), below the 3.13 V minimum of a 3.3 V OH300 and far below the 5 V/12 V MV317 alternative
V_OCXO, the OCXO supply made by U703 (LT1963EQ), is set to about 2.4-2.5 V; the fitted OH300 needs 3.13-3.47 V (3.3 V models) and the MV317 alternative needs 5 V or 12 V.
How the voltage is set
Item Value LT1963 ADJ reference 1.21 V (datasheet p.10) R701 (OUT to ADJ) 37k4 R702 (ADJ to GND) 37k4 Vout = 1.21 x (1 + R701/R702) 2.42 V ADJ bias current x R701 +0.11 V typ (3 uA), +0.37 V max (10 uA) Result ~2.5 V typ, ~2.8 V worst case What it feeds
U703 OUT -> V_OCXO -> L1 -> R9 -> net OCXO = OH300 X101 pad 3 'Supply Voltage (Vcc)' and MV317 U105 pin 2.
Why 3.3 V was intended
TP701 on V_OCXO is 'Test_3V3', and sheet 1 notes 'Vtune=0.3...3.0 V', the OH300 3.3 V model's control range.
For 3.3 V with R701 = 37k4 the bottom resistor would be ~21.5k. The LT1963 datasheet also advises the bottom resistor below 4.17k to limit the ADJ-current error; this divider and the +5V divider (R703/R704 = 37k4/12k1) both exceed it.
- PartLifecyclemajorOpen
LT1963EQ on 2 placements (U701, U703): the distributor catalogue reports "Obsolete" for Analog Devices Inc.'s LT1963EQ
LT1963EQ on 2 placements (U701, U703): the distributor catalogue reports "Obsolete" for Analog Devices Inc.'s LT1963EQ — 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/LT1963EQ/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.
At U701
- ReferencePlaneDiscontinuitymajorOpen
ReferencePlaneDiscontinuity: 6 boards×6
Checked by the review, stands · Claude walker W3 (Cern session) — Checked: the reference break is read from the copper as stated. Whether it matters depends on the signal's edge rate and the receiver's margin, which no datasheet or app note on file fixes for this net; the impedance step and reflection figures are Probe's model, and the thresholds are its starting values. Layout practice, not a datasheet requirement. Left for the owner.
At void:GND@B.CU:120.57,-134.57, void:GND@B.CU:126.4,-61.1, void:GND@B.CU:155.97,-126, void:GND@F.CU:151.79,-128, void:GND@F.CU:copper of Net-(R102-Pad2),Net-(R18-Pad2), void:routed@B.CU|F.CU
Each finding, with its own headline
void:GND@B.CU:120.57,-134.57'Net-(R39-Pad1)' crosses where the outline of the GND plane on B.CU is drawn back, at 1 place, the longest 0.84 mm (fastest: Net-(R39-Pad1) at 100 ps 10-90 %, ASSUMED)
Along 'Net-(R39-Pad1)' on F.CU, the GND plane on B.CU has 0.84 mm under the track with no copper, at (120.57, -134.57), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 100.1..199.9, y -149.9..-50.1 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-(R39-Pad1)' on F.CU at (120.57, -134.57), 0.84 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/79/reference-planes?group=void%3AGND%40B.CU%3A120.57%2C-134.57 serves each with its own layer_image region; all of them lie in x 119.27..121.86, y -135.87..-133.28 mm (board frame, Y up).
Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.
void:GND@B.CU:126.4,-61.1'/I1(PD)' crosses where the outline of the GND plane on B.CU is drawn back, at 1 place, the longest 1.06 mm (fastest: /I1(PD) at 100 ps 10-90 %, ASSUMED)
Along '/I1(PD)' on F.CU, the GND plane on B.CU has 1.06 mm under the track with no copper, at (126.4, -61.1), the same plane on both sides. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. No hole cleared it: the outline of the pour at x 100.1..199.9, y -149.9..-50.1 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.
- '/I1(PD)' on F.CU at (126.4, -61.1), 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/79/reference-planes?group=void%3AGND%40B.CU%3A126.4%2C-61.1 serves each with its own layer_image region; all of them lie in x 125.14..129.84, y -62.1..-58.5 mm (board frame, Y up).
Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.
void:GND@B.CU:155.97,-126'Net-(C16-Pad1)' crosses where the outline of the GND plane on B.CU is drawn back, at 1 place, the longest 2.39 mm (fastest: Net-(C16-Pad1) at 100 ps 10-90 %, ASSUMED)
Along 'Net-(C16-Pad1)' on F.CU, the GND plane on B.CU has 2.39 mm under the track with no copper, at (155.97, -126), running to the end of the track. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 1.06 mm). No hole cleared it: the outline of the pour at x 100.1..199.9, y -149.9..-50.1 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-(C16-Pad1)' on F.CU at (155.97, -126), 2.39 mm, running ALONG the bare copper for 1.06 mm, not across it over no copper, to the end of the track; other side: none: the signal layer is outermost
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/79/reference-planes?group=void%3AGND%40B.CU%3A155.97%2C-126 serves each with its own layer_image region; all of them lie in x 154.44..158, y -127.41..-123.59 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@F.CU:151.79,-128'Net-(R101-Pad2)' crosses where the outline of the GND plane on F.CU is drawn back, at 1 place, the longest 1.16 mm (fastest: Net-(R101-Pad2) at 100 ps 10-90 %, ASSUMED)
Along 'Net-(R101-Pad2)' on B.CU, the GND plane on F.CU has 1.16 mm under the track with copper of GND, not a plane, at (151.79, -128), running to the end of the track. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 0.83 mm). No hole cleared it: the outline of the pour at x 100.1..199.9, y -140.49..-50.1 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-(R101-Pad2)' on B.CU at (151.79, -128), 1.16 mm, running ALONG the bare copper for 0.83 mm, not across it over copper of GND, not a plane, to the end of the track; other side: none: the signal layer is outermost
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/79/reference-planes?group=void%3AGND%40F.CU%3A151.79%2C-128 serves each with its own layer_image region; all of them lie in x 149.94..153.5, y -129..-127 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@F.CU:copper of Net-(R102-Pad2),Net-(R18-Pad2)'Net-(C16-Pad1)' crosses where the GND plane on F.CU is drawn back round copper of Net-(R102-Pad2), Net-(R18-Pad2), at 1 place, the longest 6.21 mm (fastest: Net-(C16-Pad1) at 100 ps 10-90 %, ASSUMED)
Along 'Net-(C16-Pad1)' on B.CU, the GND plane on F.CU has 6.21 mm under the track with copper of Net-(R18-Pad2), Net-(R102-Pad2), not a plane, at (152.28, -125.5), running to the end of the track. No single drill's anti-pad and no landing explains it: a clearance is excused only when it holds a drill and is drawn round it, or the track ends in it on the net's own pad or via, or runs through its own via's clearance and no farther. The return current detours round the void. 1 of them run ALONG the bare copper, parallel to its edges, rather than across it (the longest 3.52 mm). No hole cleared it: the outline of the pour at x 100.1..199.9, y -140.49..-50.1 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-(C16-Pad1)' on B.CU at (152.28, -125.5), 6.21 mm, running ALONG the bare copper for 3.52 mm, not across it over copper of Net-(R18-Pad2), Net-(R102-Pad2), not a plane, to the end of the track; other side: none: the signal layer is outermost
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/79/reference-planes?group=void%3AGND%40F.CU%3Acopper%20of%20Net-%28R102-Pad2%29%2CNet-%28R18-Pad2%29 serves each with its own layer_image region; all of them lie in x 148.42..158, y -126.5..-124.5 mm (board frame, Y up).
Read from the copper as drawn on the reference layer, along each track's centreline at exact breakpoints. The reference is the copper beside the track, never the layer's type or name. Whether it matters depends on each signal's edge rate, which nothing on file states for these nets: a slow static line crosses a split harmlessly, a fast edge does not.
void:routed@B.CU|F.CU19 nets on F.CU cross the tracks routed through the GND pour on B.CU at 31 places, the longest 5.8 mm; 11 run ALONG the cut round another net's track (fastest: /-I2(I1(PD)) 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. 31 place(s) on 19 net(s). 11 of the crossings run ALONG the cut round another net's track rather than across it, parallel to its edges (the longest 4.51 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.
- 'Net-(CI1-Pad2)' on F.CU at (120.68, -65.85), 5.8 mm, running ALONG the bare copper for 4.51 mm, not across it over copper of +5V, not a plane, to the end of the track; other side: none: the signal layer is outermost
- '/-PD' on F.CU at (117.06, -60.36), 5.37 mm, running ALONG the bare copper for 2.53 mm, not across it over copper of -5V, not a plane, to the end of the track; other side: none: the signal layer is outermost
- 'Net-(RI109-Pad1)' on F.CU at (143.56, -64.51), 4.89 mm, running ALONG the bare copper for 1.71 mm, not across it over copper of -5V, not a plane, to the end of the track; other side: none: the signal layer is outermost
- 'Net-(C31-Pad1)' on F.CU at (113.03, -131.5), 3.56 mm, running ALONG the bare copper for 2.05 mm, not across it over copper of +5V, not a plane, to the end of the track; other side: none: the signal layer is outermost
- 'Net-(C19-Pad1)' on F.CU at (112.73, -71.5), 3.13 mm, running ALONG the bare copper for 2.83 mm, not across it over copper of +5V, not a plane, to the end of the track; other side: none: the signal layer is outermost
- 'Net-(C25-Pad1)' on F.CU at (113, -101.5), 3.13 mm, running ALONG the bare copper for 3.06 mm, not across it over copper of +5V, not a plane, to the end of the track; other side: none: the signal layer is outermost
- 'Net-(C37-Pad1)' on F.CU at (113, -116.5), 3.13 mm, running ALONG the bare copper for 3.06 mm, not across it over copper of +5V, not a plane, to the end of the track; other side: none: the signal layer is outermost
- 'Net-(C43-Pad1)' on F.CU at (113, -86.5), 3.13 mm, running ALONG the bare copper for 3.06 mm, not across it over copper of +5V, not a plane, to the end of the track; other side: none: the signal layer is outermost
- '/100M_distribute' on F.CU at (129.3, -111.8), 2.99 mm over copper of -5V, not a plane; other side: none: the signal layer is outermost
- '/100M_distribute' on F.CU at (132.5, -115), 2.86 mm over copper of +5V, not a plane; other side: none: the signal layer is outermost
- '/10M_distribute' on F.CU at (132.5, -127.91), 2.86 mm over copper of +5V, not a plane; other side: none: the signal layer is outermost
- 'TUNE' on F.CU at (151, -70.5), 2.86 mm over copper of V_OCXO, not a plane; other side: none: the signal layer is outermost
- and 19 more
Every site is a row of this finding's evidence, keyed by net, layers and position. GET /api/odb/boards/79/reference-planes?group=void%3Arouted%40B.CU%7CF.CU serves each with its own layer_image region; all of them lie in x 110.95..160.72, y -138.5..-57.79 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.
- FiducialMissingmajorOpen
The top side carries 176 SMT component(s) and no fiducial was found on it
The top side carries 176 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
OCXO silkscreen: 'TP101' printed across SW101 pad 1, 'U703' printed on the HS701 heatsink solder pad, and 'SW101' printed entirely off the board edge
OCXO silkscreen: "TP101" is printed across SW101 pad 1, "U703" on the HS701 heatsink solder pad, and "SW101" entirely off the board edge, so SW101 carries no designator.
- The vertical "TP101" designator (x ~101.5-102.7 mm, y ~-69 to -73 mm) runs across SW101 pad 1 (101.5, -71.7).
- The "U703" designator sits inside the HS701 heatsink paste pad (GND, around x 163.7-167.4, y -55 to -56.4 mm).
- The "SW101" designator is at x ~97.8-99.1 mm, outside the board outline (left edge x = 100 mm), so it will not be printed.
- Also, "J1" is printed over "RI115".
OCXO board: HS701 D2PAK heatsink outline overhangs the top board edge by about 1 mm
The HS701 D2PAK heatsink outline (under U703) overhangs the top board edge by about 1.1 mm.
Quantity Value Source Heatsink Heatsink_Fischer_FK24413D2PAK_26x13mm, 26 x 13 mm footprint Silkscreen body outline reaches y ~ -48.9 mm layer image, 45 px/mm Board outline top edge y = -50 mm board summary Overhang ~1.1 mm beyond the top edge derived Heatsink solder pad y ~ -53.1 to -56.4 mm, inside the board layer image OCXO schematic: Date blank on all 7 sheets, Rev only on sheet 1 ('2019.01') while the PCB silk says 2020-06-18
OCXO schematic: Date is blank on all 7 sheets and Rev is filled only on sheet 1 ("2019.01"), while the PCB silk says 2020-06-18.
- Sheet 1 (Microstepper - OCXO Board): "Rev: 2019.01".
- Sheets 2-7 (OCXO LDO and five OCXO output stages): empty Rev.
- Every sheet: empty Date.
- PCB silk: "Design Anders Wallin 2020-06-18".
OCXO schematic on file prints the same designators (U704, R21-R27, C18-C23) on all five reused output-stage sheets
The OCXO schematic prints the same designators (U704, R21-R27, C18-C23) on all five reused output-stage sheets, so a reader cannot tell which physical output stage, or which SMA, a page shows.
- ocxo_output.kicad_sch is instantiated five times: 100M_output_A/B/C and 10M_output_A/B.
- The board places U201, U301, U401, U501 and U704, each with its own resistors.
- Sheets 3-7 of the schematic on file all name U704, R21-R27 and C18-C23.
- The affected SMAs are J5, J7, J9, J11 and J13.
Main parts
| Part number | Maker | Description | Where |
|---|---|---|---|
| LT3015Q | U702 | ||
| MC12080 | U108 | ||
| MV317 | U105 | ||
| OH300 | X101 | ||
| BNX025 | FL603, FL604 | ||
| LT1963EQ | U701, U703 | ||
| LMH6702MF | U107, U201, U301, U401, U501, U704 |
About this design
- Design
- MICROSTEPPER OCXO — OHWR0079 R1
- Designed in
- KiCad EDA
- Board
- 2 copper layers, 100 × 100 mm, 192 components, 107 nets
- Licence
- CERN-OHL-S-2.0
- Source
- https://gitlab.com/ohwr/project/microstepper at commit
46ae03051ab5 - Attribution
- CERN Open Hardware Repository, project ohwr/project/microstepper (commit 46ae03051ab5b384582b0fa5100d2e5447509ebe, 2025-04-08). Licence: CERN-OHL-S-2.0. Source: https://gitlab.com/ohwr/project/microstepper. 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)