Calibration Log
Drop a sliced G-code, a slicer profile or a 3MF project and the printer, spool and settings are read from it. Drop a tuning tower and its bands are laid out so you set the height of the best one and get the value. Each printer and spool keeps the values you landed on, shows where your slicer disagrees, and goes to the machine as a spool label, a firmware G-code block, or the slicer fields to type in.
1 Profiles
This browser will not keep saved work — storage is blocked, or this is a private window.
2 Test log
Every test you ran, newest first. The latest landed value for each test is the one in force; earlier runs stay as the evidence behind it.
This browser will not keep saved work — storage is blocked, or this is a private window.
3 Printers and spools
Read from your slicer files, or added here. A spool, not a brand: two spools of the same filament calibrate differently, and that difference is what this log is for.
This browser will not keep saved work — storage is blocked, or this is a private window.
4 Label and export
Print the spool label, copy the firmware block, or take the slicer field list to the machine.
This browser will not keep saved work — storage is blocked, or this is a private window.
Every value here is one you measured. This log ships no reference profiles, no "good starting points" and no per-filament defaults, because a profile is true for one printer, one nozzle, one spool and one room, and a copied one is worth nothing.
What the export does ship is where each value is entered. Marlin commands are
M92 E (steps/mm), M221 S (flow percentage), M900 K (linear advance),
M207 S/F (firmware retraction length and feedrate, in mm and mm/min),
M851 Z (probe Z offset) and M104/M140 (temperatures) — see the Marlin
G-code reference at marlinfw.org/meta/gcode/. Klipper equivalents are
SET_PRESSURE_ADVANCE, SET_RETRACTION (requires [firmware_retraction]),
SET_GCODE_OFFSET and, for extruder steps, rotation_distance in
printer.cfg rather than a runtime command — see klipper3d.org. Values set
by a command are live for the session; persisting them is M500 on Marlin
and SAVE_CONFIG or Z_OFFSET_APPLY_PROBE on Klipper, and the export says
so rather than implying a command is permanent.
Files you drop are read in this browser and never uploaded. Sliced G-code from PrusaSlicer, SuperSlicer, OrcaSlicer and Bambu Studio carries the whole configuration; Cura writes only the settings changed from its own defaults. A slicer profile holds defaults as well as calibrations, so a value is recorded only when you tick it. The slicer's own Z offset is not read as the printer's probe offset, because they are different settings.
Flow ratio and maximum volumetric speed have no firmware command at all. They are slicer fields, and the export names the field instead of inventing a G-code line for them.
Slicer profile files (.ini, .json, .curaprofile) are deliberately not
generated. Their keys change between slicer versions and are specific to a
printer preset, so a generated file would look right and fail to load. The
export lists the field names to type instead.
Saved work stays in this browser unless you sign in. Download a backup before clearing browser data or moving to another device.
Your copy
Download everything saved in this browser, or restore a backup on this device.