Documenting Settings and Results

A simple print log makes your results repeatable: write down the few settings and conditions that actually change print behavior (printer/nozzle state, filament condition, key slicer settings, environment) plus a one-line outcome and a photo. The goal is to recreate a good print on purpose and to diagnose a bad one without guessing what changed.

TL;DR

For every print, log nozzle size, filament (and whether it was dried), nozzle/bed temps, layer height, speeds/cooling/retraction, and one clear result note with a photo of the first layer. If you can’t re-print the same part a week later, your log is missing a variable that matters.

A compact checklist-style diagram helps learners remember the minimum set of fields to log and how they group (printer, material, slicer, environment, results).

What to record (and why it matters)

A print’s outcome is the combination of (1) the machine’s physical state, (2) the filament’s condition, (3) the slicer’s chosen speeds/flows/cooling, and (4) the environment. If you don’t record those, you can’t tell whether a change fixed the problem or just swapped one problem for another. Your log only needs enough detail to reproduce the conditions and explain what you observed.

Minimum print log (copy/paste fields)

Project/part name, date, and purpose (test vs final)
Printer model; nozzle diameter and material (brass/steel)
Machine state notes: nozzle age (approx hours), recent changes (new bed sheet, tightened belts), anything “off” (oozing, skipping)
Slicer name/version; profile name used (baseline)
Filament: material + brand + color; batch/lot if known
Filament condition: stored how; dried? (temp/time/date); visible moisture symptoms (popping, steam, fuzz)
Nozzle temperature; bed temperature; enclosure on/off
Layer height; line width; perimeters/walls count
Speed highlights: outer wall, inner wall, infill (or “global speed” if that’s what you used)
Cooling: fan % and when it ramps; special settings for bridges/overhangs if used
Retraction distance/speed; Z-hop on/off
Supports: on/off; style/density; interface on/off
Adhesion: none/skirt/brim/raft; bed surface type; any glue or release agent
Orientation and any key placement notes (rotated 90°, printed at front-left, etc.)
Result: one-line outcome + where it shows (e.g., “elephant foot on front edge,” “ringing on X face,” “under-extrusion after 2 hours”)
Photos: first layer, overall part, and a close-up of the defect/success area

Fast workflow for clean iteration

Start from a known-good profile for that material/nozzle size.
Pick one primary change to test (one variable if possible).
Use the smallest model that reveals the issue (first-layer square, overhang test, thin-wall cube, etc.).
Write the delta and a measurable observation (better/worse/no change; where; how severe).
When the test is good, run the full print and attach final photos and notes to the same log entry.
Save the successful slicer profile with a name that includes the material and nozzle size.

When documentation is missing, what goes wrong

Can’t reproduce a successful print

Likely cause: A hidden variable changed (different filament brand/batch, wet filament, nozzle size swap, temperatures, orientation, or a different bed surface)

Fix: Record filament identity + dry status, nozzle diameter, temps, orientation, and bed surface; save/export the exact slicer profile used

A previously good profile starts failing “randomly”

Likely cause: Machine state drift wasn’t logged (partial clog, nozzle wear, loose belt, different Z-offset after re-tramming, dirty bed)

Fix: Add machine-state notes (nozzle hours, last maintenance, bed cleaned/how); rerun a small baseline test to confirm the printer, not the model, changed

Tuning takes many iterations with no clear progress

Likely cause: Multiple settings were changed at once and the results weren’t tied to a single cause

Fix: Go back to a known baseline, change one variable per test, and keep each test result to one sentence plus a photo for side-by-side comparison