1. Printers
Two printers appear on this page. They work at very different scales, so a number
that applies to one tells you nothing about the other. Ten dots of light measure
about a fifth of a millimetre on the Phrozen Sonic Mighty 12K, and less than a
tenth of a millimetre on the BYU printer.
Technical details
Ten pixels is 0.19 mm across and 0.24 mm down on the Phrozen Sonic
Mighty 12K, and 0.076 mm either way on the BYU printer.
Each printer below is described in the same three parts, in the same order:
What it is, Pixel size and What is not
known. The BYU printer's section then has a fourth part,
the OS1: a printer design the Nordin group has released as open
hardware. Its figures are BYU's published figures for the OS1.
Phrozen Sonic Mighty 12K
Where it is: in the Gale Lab.
What it is used for: it is the printer this project's chips are
meant for. Twenty of the library's 21 reference chips name it as their printer (the
twenty-first, the BYU pump-mixer, is laid out for the BYU printer), and the project's
current printer profile is written for it. Today the lab uses it for its early test
prints of pumps. Our account
What it is
| property | value | tier | source |
| Model |
Phrozen Sonic Mighty 12K |
Our account |
The badge on the machine, read and confirmed by the lab. No tracked file names it; see the history below. |
| XY pixel pitch |
19 µm (X) × 24 µm (Y) — non-square |
Our account |
Derived from the model: 11520 × 5120 over a 218 × 123 mm build area. Labelled "Our account" rather than "Published" because it follows from knowing the model, and the model comes from reading the badge on the machine rather than from a file. |
| Native resolution |
11520 × 5120 |
Published |
Vendor and multiple retailer specifications for the Phrozen Sonic Mighty 12K agree. |
| Build area |
218 × 123 × 235 mm |
Published |
Vendor and multiple retailer specifications agree. |
| Layer height in use |
10 µm (0.01 mm) |
Our records |
openmfda_flow/flow/platforms/h.r.3.3/config.mk — LAYER_VAL = 0.01 |
| Light source |
405 nm |
Our account |
Stated by the lab. physical_interface.json carries the pixel pitch but not the wavelength, and no other tracked file records it. |
| Slicer profile in use |
a Phrozen Sonic Mighty 8K profile, in the one slicer file on record |
Our records |
see the slicer profile below |
Pixel size
Three pitches, and which one is real. The machine was identified
from the badge on it. Until that happened, three different pixel pitches were in
circulation in this project, attached to three different machine names. All three
are recorded here, because the history explains where the figures in the older
files came from.
| name | pitch | where it came from | status |
| Phrozen Sonic Mini 8K |
22 µm |
A 7.1″ machine with a 165 × 72 mm build area. Its specification is where the project's 22 µm figure came from — the lab's printer was misidentified as this model. The name still appears in May 2026 files. |
not the machine |
| Phrozen Sonic Mighty 8K |
28 µm |
The profile the one slicer file on record was produced through. A third machine again. |
not the machine |
| Phrozen Sonic Mighty 12K |
19 × 24 µm |
The badge on the machine in the lab. |
Our account |
This is a documented fact about the project, not a confession. A pixel pitch that
travels between files without a machine attached to it is exactly the failure this
page was built to make visible, and it is the reason every figure here carries where
it came from.
What the corrected pitch does and does not affect
The obvious reading of a wrong pixel pitch is that everything printed came out the
wrong size. That is not what happened, and it is worth being precise
about.
Physical dimensions are not affected. The SCAD and the STL are in
millimetres. The printer rasterises millimetres using its own pitch, whatever that
pitch is. A chamber the tool reports as 8.8 mm prints at 8.8 mm. Volumes are
correct. Nothing printed was the wrong size.
Non-square pixels do not distort parts. A feature designed
880 × 880 µm prints 880 × 880 µm. It simply occupies a
different pixel count on each axis — about 46 across and about 37
down, rather than 40 and 40.
What is affected is every figure expressed in pixels, because the
pixel is the wrong size. A count, a clearance or a minimum feature quoted in px
means something different at 19 or 24 µm than it did at 22.
The files give lengths in millimetres, and the printer rounds them to its own pixels.
The lab has accepted rounding to the nearest printable position. Worst-case
quantisation error is half a pixel: ±9.5 µm in X and
±12 µm in Y.
Layer-height-based dimensions are unaffected entirely. Membrane
thickness and chamber depth are counted in layers, and the layer height has not
changed.
The slicer profile
The one slicer file on record used a Phrozen Sonic Mighty 8K profile
The one slicer file on record was produced through a Phrozen Sonic Mighty
8K profile — a 28 µm machine, not the 19 × 24 µm
machine in the lab.
If the slicer is still set that way, files are being rasterised for a different machine than
the one printing them. Parts still come out the right physical size —
millimetres are millimetres — but the pixel grid the geometry is quantised
onto, and the exposure schedule applied to it, belong to another printer.
Custom DLP-SLA printer, built by the Nordin group at Brigham Young University
Where it is: at Brigham Young University (BYU), where the Nordin
group built it. It is a custom research instrument, not a commercial
product; on this page it is called the BYU printer for short.
What it is used for: this project keeps it for its finest,
high-accuracy prints. In June 2026 a collaborator at BYU printed five pumps on it,
and the lab tested them: some worked and some did not (see
§8). The lab calls this printer the
H.R.3.3, the printer the README of the lab’s process design kit names
(utah-MFDA/h.r.3.3_pdk,
read 2026-09-30).
Our account This project's h.r.3.3 platform
also keeps a profile for it. The OS1 (below) is the printer design the Nordin group has released as open
hardware; what BYU publishes about it is given there as BYU's. The Nordin group prints microfluidic chips with very
small channels on it: their papers report flow channels as small as
18 µm × 20 µm, and those published figures are quoted
elsewhere on this page.
The rows marked Published come from the
papers describing that instrument, and none of them has been reproduced here.
What it is
| property | value | tier | source |
| Type |
Custom DLP-SLA printer |
Published |
Gong, Bickham, Woolley, Nordin, “Custom 3D printer and resin for 18 µm × 20 µm microfluidic flow channels”, Lab on a Chip, 2017 [1] |
| Light source |
385 nm LED |
Published |
Gong 2017 [1], read 2026-09-30; the 2021 paper [2] gives 385 nm as well. Chosen over 405 nm because 385 nm greatly widens the range of usable UV absorbers. Goenner et al. 2025 [9] give 365 nm for the printer used in that paper, as the OS1's Specs page [7] does for the OS1. For both figures, see the OS1's wavelength. |
| XY pixel pitch |
7.6 µm in the projected image plane |
Published |
Gong 2017 [1]. See the pitch note below. |
| XY pixel pitch as this project stores it |
7.6 µm (0.0076 mm) |
Our records |
openmfda_flow/flow/platforms/h.r.3.3/config.mk — PX_VAL = 0.0076; physical_interface.json profile byu_hr33_7p6um |
| Later designation |
“High Resolution 2” (Generation 2) printer |
Published |
Nature Communications 12, 2021, s41467-021-25788-w [2] |
| Light engine |
Visitech (Lier, Norway) |
Published |
Gong 2017 [1]; ASME, “Regime Change in 3D Printed Microfluidics”, 2017 [3] |
| Optical path |
45° turning mirror, three axes of adjustment |
Published |
Gong 2017 [1]; ASME 2017 [3] |
| Mechanism |
Heavily modified Solus DLP-SLA (Junction 3D, Santa Clarita, CA), custom mounts |
Published |
Gong 2017 [1]; ASME 2017 [3] |
| Smallest demonstrated flow-channel cross section |
18 µm × 20 µm |
Published |
Gong 2017 [1] |
| Substrate |
25 mm square silanized glass slides |
Published |
Nat Commun 2021 [2] — rinsed with acetone and IPA, then immersed 2 h in toluene with 10% 3-(trimethoxysilyl)propyl methacrylate |
Pixel size
Pitch note. The pixel pitch is given as 7.6 µm
in the papers and 7.56 µm in Gong's dissertation
(BYU ScholarsArchive etd/7690 [4]). This project's files use 7.6 µm.
The discrepancy is recorded here.
The OS1: a printer design BYU has released as open hardware
BYU's description
Everything in this part is BYU's description of the OS1, in BYU's figures. The BYU
printer this project designs for, the H.R.3.3, is described above; the five pumps in
§8 were printed on it.
What it is. The OS1 (Open Source 1) is a DLP printer for
microfluidic devices, designed by the Nordin group at BYU and published as open
hardware. Like both printers above, it is a vat photopolymerization printer: an
image projected into a vat of liquid resin cures the part one layer at a time. BYU
presents it as the result of more than ten years of the group's work on its own
printers. The features its repository lists are automatic levelling of the build
surface, automatic focus calibration, focus kept across the build area by a
confocal distance sensor, the light engine's output corrected with a fibre-optic
photodiode, and greyscale correction of the projected image for a more even
exposure [8].
Where to get it. The design files are in the Nordin group's
repository on GitHub,
the OS1 repository
of 3D-Printing-for-Microfluidics [8]. BYU's website for the printer is
os1.byu.edu
[7]. This site copies nothing from either: the files, the text and the pictures are
BYU's, and the links lead to them.
What the repository holds, as read on 2026-09-30, at commit
4d22c93 [8]:
- CAD models of the whole printer and of each part made for it, as STEP files; a
3MF file for each part to be printed on a filament (FDM) printer; and DXF cutting
layouts for the aluminium and polycarbonate parts, which are cut on a
waterjet;
- the design and manufacturing files for two circuit boards made for it: a
load-cell board, drawn in Eagle, and a motor board for levelling the build
surface, drawn in KiCad;
- the bill of materials, as an Excel workbook, grouped to follow the build
manual;
- the build manual, and a guide to setting up the Raspberry Pi that runs the
printer, both as PDF;
- a Supplemental folder with a STEP model and a second build manual for the
printer fitted with a newer light engine: see the caveat below.
The printer's control software is not in it. The Raspberry Pi guide installs it from
a separate BYU repository,
3D_printer_control.
Licence. The repository is licensed under the CERN Open Hardware
Licence version 2, strongly reciprocal,
CERN-OHL-S-2.0,
as read on 2026-09-30 [8]. In brief: anyone may study, change, make and share the
design, and whoever shares it, or a product made from it, must share the complete
design files under the same licence. That summary is ours, and the licence text is
what governs. It is not this site's MIT licence, which does not extend to BYU's
files.
BYU's caveat: the light engine is discontinued
The OS1 is built around a Visitech LRS WQ light engine, and the repository's
README says Visitech has discontinued it. Its replacement, the LRS WQ Plus, talks
to the computer in a new way: it needs a new driver, one that does not send the
image from the Raspberry Pi over HDMI, and the current OS1 software cannot drive
it. The Supplemental folder has
a STEP model of the printer with the WQ Plus and a second build manual for it
[8].
BYU's figures. Each figure below is BYU's published claim about
the OS1, with the date it was read. BYU's Specs page gives all its values as approximate.
Which wavelength. Two are published for the Nordin group's
printers: 365 nm, on the OS1's Specs page [7] and in Goenner et al. 2025 [9],
and 385 nm, in Gong et al. 2017 [1].
BYU's own prints and papers. BYU's OS1 page titled
“Validation”
lists papers by the Nordin group from 2015 to 2026, and its
Gallery
shows the printer, renderings of it, and photographs and micrographs of chips the
group has printed, with no captions saying which printer made each [7]. Both are
the Nordin group's own work, published by BYU. None of it is a print made for this
project: this project's prints are in
§8, and BYU's are not counted there.
4. Post-processing
| step | what is recorded | tier | source |
| Flush |
IPA, syringe port-to-port until effluent runs clear |
Our records |
A design report in the lab’s working copy, for reference chip chamberchip_f584, a CAD model: §7, its advice for printing. openmfda_flow/flow/reference_chips/chamberchip_f584/chamberchip_f584_report.md |
| Ordering — hard rule |
Flush the cavity clear BEFORE any UV post-cure |
Our records |
The same design report, §7: resin left inside cures permanently and cannot be removed |
| Alternative clearing method |
IPA ×3 under vacuum; IPA rinse |
Published |
Beauchamp 2018 [5], section 2.5 (three IPA flushes under vacuum); Gong 2017 [1], section 2.4 (an IPA rinse). Read 2026-10-01. The BYU printer's published process. |
The ordering rule is the one post-processing step that has a consequence
attached.
7. Process limits
The limits below are the ones on record for these printers: how small a
feature can be, how thin a wall can be, how wide a roof can span. They are the numbers people quote, and each one says
what it actually rests on. If a design tool sent you here from its
not checked list, this is all there is.
| limit | figure | what it rests on | source |
| Channel height must be less than its width |
h < w |
Our records — a fluid-model constraint, not a printability rule. See below. |
openmfda_flow/flow/platforms/h.r.3.3/pdk/docs/Rectangular Channel.docx — “Component Geometric parameters” |
| Lateral minimum feature, Phrozen Sonic Mighty 12K |
10 px = 0.19 mm (X) / 0.24 mm (Y) |
Our records — has a written derivation, but from a routing-clearance experiment, not a print test |
openmfda_flow/flow/platforms/h.r.3.3/physical_interface.json — clearance._derivation |
| Membrane floor |
100 µm |
Our records — enforced in the generator. |
openmfda_flow/flow/platforms/h.r.3.3/pdk/py_scripts/gen_centerfed_block.py (100 µm); gen_pump.py and gen_mixer.py (20 µm) |
| Edge clearance — hard floor |
0.50 mm |
Our records — enforced in code; the build aborts below it |
openmfda_flow/flow/platforms/h.r.3.3/pdk/py_scripts/gen_centerfed_block.py — --edge-clearance-min |
| Edge clearance — preferred |
0.75 mm |
Our records — enforced in code; warns below it |
gen_centerfed_block.py — --edge-clearance-pref |
What h < w actually is
h < w is the one documented rule the design tools enforce, and it is
the most misread number in the project. It comes from the h.r.3.3 PDK's
rectangular-channel component document, where it sits under “Component
Geometric parameters” alongside the hydraulic-resistance model.
It is the validity condition of the Bruus Hagen–Poiseuille series
— the 0.63 · h/w term — and therefore a fluid-model
constraint, not a printability rule. A channel taller than it is wide does
not fail to print because of this rule. It falls outside the range over which the
resistance approximation is written, so the number the calculator returns for it is
computed on the same duct with the two cross-section dimensions exchanged.
8. What has been printed
Nothing generated by /design/channel/,
/design/chamber/ or
/design/droplet/ has ever been printed.
Those tools produce geometry and arithmetic; they say so on their own pages.
All 21 reference chips in the library carry status
not-tested: designs checked in CAD, 20 for the Phrozen Sonic Mighty
12K and the BYU pump+mixer for the H.R.3.3. Every chip and component in the library is designed for a specific printer: BYU's H.R.3.3 or the Phrozen Sonic Mighty 12K.
One single-pump cell has been printed. A slicer file for it exists,
and its machine profile is readable: see §6.6 above.
Five pumps have been printed on the BYU printer.
Our account
In June 2026 a collaborator at BYU printed five pumps on the
BYU printer, and the lab tested them. Some worked and
some did not. By the lab's account that printer is the H.R.3.3 (§1). The prints BYU
shows on its own OS1 pages are the Nordin group's, not this project's, and are not
counted here.
Sources: each design tool's own “what is checked, and what is not”
section; data/library.json status_enum and the 21 reference-chip
entries. The five pumps printed at BYU: the lab’s account, given on 2026-09-29,
and no file. That the printer was the H.R.3.3: the lab’s account, given on
2026-09-30, and no file.