firmware/docs/toolchange.md

The toolchanger mod

FlashForge Creator 5 Pro — native toolchanger for Klipper/Mainsail.

Makes the Creator 5 Pro's 4-tool toolchanger and print lifecycle work for prints started from Mainsail/Moonraker (e.g. sliced in OrcaSlicer), without the stock touchscreen app in the loop. Based on reverse-engineering the stock firmwareExe binary (addresses referenced in the source comments), with some behaviour improved along the way — deliberate divergences are documented in the file headers.

Not yet run on hardware. Everything here has been exercised against a mock Klipper harness only. The design it replaced read calibration live from firmwareExe's JSON and had been used on a real printer; in this one all per-unit numbers live in ordinary Klipper config, and the touchscreen's nozzle-offset calibration is reimplemented as Klipper commands. See hardware-testing.md before flashing.

What's in here

File	Goes to (on the printer)	What it does
payload/klipper/extras/ff_toolchange.py	/usr/prog/klipper/klippy/extras/	The toolchanger: T0..T3, dock/grab state machine with sensor polling and retries, per-tool G-code offsets (the absolute ~3.2 mm bed-frame Z is applied at every grab), TOOLCHANGE_SET_PRINT_OFFSET (the print-start thermal/bed/layer Z terms), TOOL_Z_ADJUST (per-tool persistent babystep), TOOLCHANGE_STATUS, TOOLCHANGE_PARK
payload/helixscreen/printer_database.d/flashforge_creator5.json	HelixScreen config/printer_database.d/	Printer-database entry so HelixScreen auto-detects both Creator 5 models as tool changers (the Pro and the non-Pro differ only by the chamber heater)
payload/klipper/extras/ff_tool.py	/usr/prog/klipper/klippy/extras/	[ff_tool n] — one section per tool; dock_x/dock_y, nozzle_x/y/z and z_adjust are all autosaved (import or calibration + SAVE_CONFIG)
payload/klipper/extras/ff_tool_offset.py	/usr/prog/klipper/klippy/extras/	TOOL_OFFSET_CALIBRATE / STATION_CALIBRATE / TOOL_OFFSET_STATUS — the touchscreen's nozzle XY/Z offset calibration, recovered from the binary and reimplemented in Klipper
payload/klipper/extras/ff_legacy.py	/usr/prog/klipper/klippy/extras/	FF_IMPORT_FIRMWARE_CONFIG — one-shot import of the factory/touchscreen JSON into Klipper config. Needed once, at install
payload/klipper/config/ff-toolchange.cfg	/usr/data/config/	empty [ff_tool 0..3] sections (the per-unit dock/nozzle data is autosaved, nothing unit-specific ships), [ff_toolchange] feeds/geometry, SDCARD_PRINT_FILE wrapper
payload/klipper/config/ff-tool-offset.cfg	/usr/data/config/	[ff_tool_offset] — probe geometry and guards for the calibration commands
payload/klipper/config/ff-legacy.cfg	/usr/data/config/	[ff_legacy] — include only for the import step, then remove
payload/klipper/config/ff-print-macros.cfg	/usr/data/config/	START_PRINT / END_PRINT / PAUSE / RESUME / CANCEL_PRINT, reconstructed from the app's sequences, plus the calibration gate
payload/klipper/config/ff-filament.cfg	/usr/data/config/	LOAD_FILAMENT / UNLOAD_FILAMENT / PURGE — the touchscreen's filament-load sequence (grab tool, purge chute, feed) recovered from the binary; unload is a designed retract (the stock app has none)
payload/klipper/config/ff-runout.cfg	/usr/data/config/	Runout / clog handling: gives the stock fd_ex* / fm_ex* sensors a runout_gcode that pauses a Mainsail print when the mounted tool runs out or clogs (the app's E0162 / E0163), optionally after printing through the PTFE buffer (runout_distance); ff_toolchange arms only the mounted tool's sensors
payload/klipper/config/printer.base.cfg	/usr/prog/klipper/config/	FlashForge's printer.base.cfg with the chamber block replaced by [include printer.chamber.cfg]. Klipper can override an option but cannot un-declare a section, and the plain Creator 5 has no chamber heating element, so its heater must be absent rather than neutralised. bin/unpack.sh compares this against each stock package it unpacks and warns if FlashForge's has changed
printer.chamber.cfg.creator5 · .creator5pro	/usr/prog/klipper/config/printer.chamber.cfg	The one per-model difference: the Pro gets [heater_generic chamber_heater] + [verify_heater] verbatim from FlashForge, the Creator 5 gets only [temperature_sensor chamber] on the same pin. Anything that differs between models exists once per model with a .creator5 / .creator5pro suffix and is installed under its real name — nothing is edited at build time
payload/klipper/config/ff-chamber.cfg	/usr/data/config/	M141 / M191 for the chamber heater (Klipper has neither, and the stock app drove the chamber only from its own UI), plus the gate: the macros ask Klipper whether heater_generic chamber_heater exists, so a non-zero chamber target is refused on a machine that does not declare one. Nothing to keep in sync; identical in every package
docs/notes/	(reference only)	Condensed reverse-engineering notes: what the stock app actually does, with binary addresses

⚠️ Use at your own risk

This is unofficial, reverse-engineered firmware modification. It is not endorsed by FlashForge, it voids whatever warranty you had, and you alone are responsible for what happens to your printer. Mistakes here are not hypothetical — a wrong Z offset drives the nozzle through the build plate, and a failed grab or missing check can end like this:

Read the warnings below, run the Verify section before the first print, and stay next to the machine until you trust it.

⚠️ Before you start

• The eddy probe's Z home is ~3.2 mm below the real bed plane. The stock app compensates with an absolute SET_GCODE_OFFSET Z=+3.2xx at print start. Here every T<n> grab applies that tool's gap (nozzle_z − station_z + z_adjust) as the Z offset, so Z=0 is the bed whenever a tool is mounted; START_PRINT's TOOLCHANGE_SET_PRINT_OFFSET only adds the thermal/bed/thin-layer terms (< 0.1 mm). With no tool mounted, or on an uncalibrated machine, Z=0 is still ~3.2 mm below the plate — the print gate refuses to start in that state.
• Where the numbers live. Nothing is read from firmwareExe's JSON at runtime any more. Feeds and staging positions ([ff_toolchange]) are plain config in ff-toolchange.cfg. Per-unit values — dock_x/dock_y, nozzle_x/y/z and z_adjust per tool, station_x/y/z, cylinder_x/y — are written by the import/calibration commands (configfile.set) and persisted with SAVE_CONFIG into the #*# block at the end of printer.cfg, exactly like PID or input-shaper results. Never put those autosaved options into an included .cfg: this Klipper fork's SAVE_CONFIG refuses with "conflicts with included value" and the calibration cannot be saved.
• Still never edit the JSON under /usr/data/firmwareRes/config/. This module no longer reads it, but the touchscreen app still does and rewrites those files wholesale — leave it alone.
• Klipper lives on the firmware partition. A FlashForge OTA update will overwrite /usr/prog/klipper/, deleting the extras. Keep this repo and re-run step 1 after every firmware update. The #*# block in printer.cfg is on the data partition and survives.

Install by hand

A package built from this repo installs all of this for you — see building.md. What follows is the manual route, for dropping a single edited file onto a printer that is already modded.

On the printer (ssh as pwned — this assumes a jailbroken printer; how to get root/ssh access is covered in the community Discord):

# 1. the klippy extras (firmware partition — may need remount rw)
scp payload/klipper/extras/ff_*.py \
    pwned@PRINTER:/usr/prog/klipper/klippy/extras/

# 2. the config files (data partition — survives OTA)
scp payload/klipper/config/ff-*.cfg \
    pwned@PRINTER:/usr/data/config/

3. Append to /usr/data/config/printer.cfg. All of these are required — they are not optional drop-ins, and without them Klipper comes up as a plain printer with no toolchanger. Order matters: they must come AFTER [virtual_sdcard] is defined, and must not go in printer.override.cfg, which is included first:

[include ff-toolchange.cfg]
[include ff-tool-offset.cfg]
[include ff-filament.cfg]
[include ff-print-macros.cfg]  ; after ff-filament.cfg (the nozzle clean uses it)
[include ff-runout.cfg]        ; after printer.base.cfg (overrides its sensor sections)
[include ff-chamber.cfg]       ; M141/M191; follows whatever printer.chamber.cfg declared
[include ff-legacy.cfg]        ; temporary — only for step 5

4. RESTART (or reboot).

5. Import the factory/touchscreen calibration once:

   FF_IMPORT_FIRMWARE_CONFIG
   

   This reads extruder.json / test.json / zoffset.json and stages your unit's dock coordinates, nozzle and station values, station start point and any per-tool Z tune for SAVE_CONFIG. Nothing to paste; it only prints an [ff_toolchange] snippet if a feed in the JSON differs from the running config (it does not on a stock unit).

6. SAVE_CONFIG — persists the imported values into printer.cfg's #*# block and restarts.

7. TOOLCHANGE_STATUS and TOOL_OFFSET_STATUS — every tool should show a nozzle triple and a dock position, the station z must be present; nothing should say NOT CALIBRATED, "no dock position" or "unsaved calibration pending".

8. Remove the [include ff-legacy.cfg] line and RESTART. The import is one-shot; the touchscreen's JSON is not consulted again.

Verify

Before moving anything:

• TOOLCHANGE_STATUS — current tool as derived from the dock sensors, every sensor's state, each tool's nozzle position and z_adjust, station_z, dock coordinates and the derived offsets (offset_z is each tool's absolute bed-frame gap, ~3.2). Check the dock_x/dock_y rows are numbers, not nan.

• TOOL_OFFSET_STATUS — saved calibration per tool and for the station, and a warning if anything is staged but not yet SAVE_CONFIG'd.

• Physical Z check (clean bed, nothing on it):

  G28
  T0
  TOOLCHANGE_SET_PRINT_OFFSET NOZZLE=220 BED=80 LAYER=0.25 TOOL=0
  G1 X150 Y150 F6000
  G1 Z0.1 F600
  

  T0 already applies the ~+3.2 mm gap (watch the gcode Z offset in the UI); the offset command reports the full Z with a term-by-term breakdown, and the nozzle should end up a paper-thickness above the bed at the center. If it presses into the plate instead, STOP — the offset is not being applied; do not print until TOOLCHANGE_STATUS and TOOL_OFFSET_STATUS are clean. Afterwards restore the idle state:

  G1 Z10 F1200
  TOOLCHANGE_PARK
  SET_GCODE_OFFSET X=0 Y=0 Z=0 MOVE=1
  

A touchscreen recalibration no longer affects this module. Recalibrate from Klipper instead (next section), or repeat the import step if you really want the touchscreen's numbers.

Calibration

The nozzle XY/Z offset calibration is the touchscreen's own sequence (testEddyExtruderOffsetForwardTwoCheck, recovered from the binary — see docs/notes/45-tool-offset-calibration.md and 46-offset-calibration-recovered.md), constants included. Take the PEI sheet off first — the calibration station sits below the bed plane. PLATE_REMOVED=1 is your promise; both commands also verify it: with the empty carriage they probe the station Z (must be within 0.8 mm of the calibrated station_z) and sweep sideways for the circle's edge — a plate left on lands the Z probe high and has no edge, and the command refuses before any nozzle descends (PLATE_CHECK=0 or plate_check: False skips it). Home, then:

STATION_CALIBRATE PLATE_REMOVED=1              ; empty carriage, no tool mounted
TOOL_OFFSET_CALIBRATE TOOL=ALL PLATE_REMOVED=1 ; or TOOL=<0..3> for one tool
SAVE_CONFIG

STATION_CALIBRATE probes the fixed under-bed station with the empty carriage (eddy frame) and stores station_x/y/z; TOOL_OFFSET_CALIBRATE then picks up each tool, touches the station's cylinder in four directions with the nozzle, fits a circle, repeats the pass centred on that fit and stores the nozzle's absolute nozzle_x/y/z. Results are station-frame absolutes per tool, so recalibrating one tool leaves the others valid; nozzle_z − station_z is the ~3.2 mm gap the print-start Z offset uses. Re-run STATION_CALIBRATE whenever the station or bed is disturbed.

Per-tool first-layer tuning: Klipper's SET_GCODE_OFFSET Z_ADJUST= babystep is one global number. Use

TOOL_Z_ADJUST TOOL=2 ADJUST=-0.02   ; relative, or VALUE=<mm> absolute
SAVE_CONFIG                         ; when you are happy with it

instead: it edits [ff_tool 2] z_adjust, re-applies immediately if that tool is mounted, is added on every later grab of that tool, and persists.

Safety

• G28 docks a mounted tool before homing Z. Z homes on the carriage's eddy sensor, whose trigger height is ~3.2 mm below the nozzle tip — with a head on, the nozzle hits the plate first. The G28 wrapper in ff-toolchange.cfg homes X/Y (endstops at 0, away from the docks), runs TOOLCHANGE_PARK, then homes as asked; G28 X/G28 Y alone are untouched. If the dock sensors can't say whether a head is on, Z homing is refused.
• Prints refuse to start while uncalibrated. START_PRINT runs _FF_REQUIRE_CALIBRATION first, and the Mainsail entry point (the SDCARD_PRINT_FILE wrapper) checks printer.ff_toolchange.print_offset_ready: if any tool's nozzle_z or the station_z is missing, the job is refused before anything heats, homes or grabs, with the fix spelled out. Override only for bench tests: SET_GCODE_VARIABLE MACRO=_FF_JOB VARIABLE=allow_uncalibrated VALUE=1.
• Calibration moves are bounded. Both calibration commands require PLATE_REMOVED=1; the Z probe targets −3 by default (the app's own station value) and, once a trigger height is known, stops 2 mm below it instead of driving on.
• Implausible results are not saved. A circle-fit residual above 0.05 mm, or a nozzle-to-station gap (nozzle_z − station_z) outside 1.5–5 mm, aborts the command with nothing staged. Thresholds are in ff-tool-offset.cfg.
• A T<n> on an unhomed machine aborts instead of homing silently (auto_home: False) — a remote G28 with a tool mounted rams the nozzle into whatever is on the bed.
• Missing tools are caught before anything moves. START_PRINT TOOLS=… runs _FF_REQUIRE_TOOLS: every tool the file uses must be sitting in its dock (switch pressed) or be the mounted one, else the job is refused with the list of what is missing (the app's E0165 — which only checked the first tool and let the others fail mid-print at their grab).
• Runout and clogs pause the print. See Runout / clog.

Filament load / unload

payload/klipper/config/ff-filament.cfg reproduces the touchscreen's FilamentLoad page (recovered from the binary — docs/notes/47-filament-load-recovered.md): each tool has its own direct-drive extruder, so loading means grab the tool, drive it to the purge chute at the back right (X275 Y254), heat to material temperature + 30, push 150 + 145 mm at F240, park the tool, heater off.

LOAD_FILAMENT TOOL=1 TEMP=220          ; or MATERIAL=PETG (app's temperature table)
UNLOAD_FILAMENT TOOL=1 TEMP=220        ; prime 10 mm, then pull 80 mm out (LENGTH= to tune)
PURGE TOOL=1 PURGE_TEMP=220 LENGTH=50  ; app's clearNozzlePrint purge + cold wipe (WIPE=0 to skip)

• TOOL defaults to the mounted tool; RELEASE=0 keeps the tool on the carriage afterwards, HEAT_OFF=0 leaves the heater on.
• PURGE ends the way the app's pre-print clean does: the nozzle rests on the front-right wipe spot (266.5, 13.8) 1 mm above the eddy trigger height while the hotend cools by 100 °C, then lifts — the purge string freezes and tears off instead of riding back to the dock. WIPE=0 skips it. LOAD_FILAMENT has no wipe, as in the app (its guide tells you to pull the string off).
• While a print is paused the macros only act on the mounted tool, use the app's in-print lengths (100 mm then −5), and leave tool and heater for RESUME. While printing they refuse.
• The stock app has no retract-unload — its "unload" is the same forward push and the on-screen guide tells you to cut and pull. UNLOAD_FILAMENT is therefore designed, not ported; unload_length (80 mm) in [gcode_macro _FF_FILAMENT] is a first guess — shorten it once you have measured the nozzle-to-above-gears path.
• All geometry, feeds, the temperature table and the per-tool chute nudges are variables of [gcode_macro _FF_FILAMENT].

Runout / clog

The stock config ships all eight filament sensors with pause_on_runout: False and a runout_gcode that only prints wheel runout:Tn — the touchscreen app did the rest (polled the mounted channel's switch sensor from its print loop, kept only the mounted tool's motion sensor enabled). Without the app nothing would happen. payload/klipper/config/ff-runout.cfg restates the sensor sections (Klipper merges repeated sections, later options win — the stock printer.filament.cfg stays untouched and OTA-safe) so that runout_gcode calls _FF_RUNOUT, and ff_toolchange arms the mounted tool's two sensors on every grab, disarms everything on release, and re-arms on RESUME (the app's setFilamentWheelManager).

Flow: sensor fires while an SD print is running and the sensor belongs to the mounted tool → PAUSE, E0162 filament runout / E0163 clog on the display and console → fix the filament → LOAD_FILAMENT TOOL=n (its paused path is the app's in-print feed: 100 mm, then 5 mm back) → RESUME. Sensors of tools that are not mounted never fire, and nothing fires outside a print. TOOLCHANGE_STATUS shows which sensors are armed; FF_RUNOUT_ARM [TOOL=n] / FF_RUNOUT_DISARM do it by hand. Clog pausing can be made report-only, as the app's plugCheck toggle did: SET_GCODE_VARIABLE MACRO=_FF_RUNOUT_CFG VARIABLE=clog_pause VALUE=0.

The runout switch is upstream of the extruder gear with a long PTFE run in between (~600 mm here), so when it opens the head still holds that much printable filament; the app paused at once and wasted it. Set variable_runout_distance in [gcode_macro _FF_RUNOUT_CFG] to the measured switch-to-gear length minus a margin (e.g. 500) and the print carries on, a 1 s watcher counts the mounted tool's extrusion and pauses with E0162 once that much has been used — extrusion by other tools in between does not count, a manual PAUSE freezes the countdown. 0 (the default) pauses immediately. No endless-spool: another tool is another head, not another spool of the same material. Untested on hardware: whether the motion sensors (detection_length 50, event_delay 3) stay quiet through LOAD_FILAMENT.

OrcaSlicer setup

Leave the profile stock. An untouched FlashForge Orca profile works as shipped: nothing to paste into Machine start or end G-code, and files sliced before the mod keep printing. [ff_print] wraps SDCARD_PRINT_FILE/M23, reads the bed, nozzle, initial tool and first-layer height out of the file itself, and runs START_PRINT before the file's first line -- which the stock block needs, because it has no G28 (its first motion, G1 Z5 F2400, assumes a homed machine) and no M190 (nothing waits for the bed). At the other end its ;end_gcode is a single move that turns nothing off, so FF_AFTER_PRINT_END runs the exit sequence when the job leaves the printing state.

To drive the sequence from the slicer instead, put an explicit START_PRINT call in Machine start G-code and set SET_GCODE_VARIABLE MACRO=FF_BEFORE_PRINT_START VARIABLE=prepare VALUE=0 so the machine is not prepared twice.

Leave Change filament G-code empty. With no custom block Orca emits its own bare Tn at each tool change, which reaches ff_toolchange.py directly. Older instructions here asked for a T[next_extruder] ; ff-toolchange line to dodge a trap in FlashForge's Klipper fork; we ship upstream virtual_sdcard now and that trap is gone, so clear the field if it still holds anything. Files already sliced with the old marker keep printing correctly — the G-code parser discards the comment and T2 arrives either way, so no re-slice is needed for that.

No re-slicing is needed: [ff_print] applies the print Z offset for any file, including ones sliced before the mod existed.

START_PRINT options, for the explicit path: TOOLS=0:220,2:240 every tool the file uses with its clean temperature (Orca: is_extruder_used[n]; a bare TOOLS=0,2 also works and falls back to NOZZLE=) — presence gate and pre-print nozzle clean; without explicit temperatures each tool is cleaned at the temperature its _FF_FILAMENT.tool_material maps to; CLEAN=0 skips the clean (default on: each used tool is grabbed, heated, purged 50 mm at the chute with the part fan on, wiped at the station, cooled by 100 °C and docked while the bed heats — the app's clearNozzlePrint); LEVEL=1 probes a fresh mesh (recommended for the first print); SOAK=<seconds> dwells after the bed reaches target (the app waits 5 min; default 0).

Design notes

• Per-tool X/Y offsets are differences vs a base tool (T0), applied on each grab the way CommMgr::setGrabGcodeOffsetMgr computes them. Z is absolute on every grab: nozzle_z − station_z + z_adjust, the bed-frame gap the app only sets once per print (BuildPage::startPrint). This departs from the app deliberately — with the app's scheme a tool picked up outside a print sits in the raw eddy frame and a manual G1 Z0.1 drives it 3 mm into the plate. TOOLCHANGE_SET_PRINT_OFFSET adds only the job terms (thermal, bed ≥ 100 °C, thin first layer) and those, plus mid-print babysteps, are carried across toolchanges as in the app. A print may start on any tool.
• Calibration is stored the way Klipper's own calibrators store theirs: absolute nozzle_x/y/z per [ff_tool n] section (modelled on [bed_mesh <profile>] / klipper-toolchanger's [tool Tn]) plus [ff_tool_offset] station_x/y/z, written with configfile.set() and persisted by SAVE_CONFIG; dock positions and the station start point are imported the same way. The offsets are derived at load. [save_variables] is deliberately not used. The stock touchscreen cannot see Klipper-side results — it keeps using its own JSON.
• Everything is a Python extra (not gcode_macro) because the grab sequence polls the grab sensor and retries up to 3 times, and the calibration drives the fork's e_stop probe objects directly — a macro renders its whole template before executing and cannot poll.

Input shaper

SHAPER_CALIBRATE, TEST_RESONANCES and MEASURE_AXES_NOISE are wrapped (ff-toolchange.cfg): they home if needed and grab a head first when the carriage is empty, so the measured moving mass is the real one (the app's grabVibration). Works the same from Mainsail, HelixScreen or the console; the original parameters pass through. Which head: variable_shaper_tool in [gcode_macro _FF_SHAPER_PREP] (default T0). The tool stays mounted afterwards; TOOLCHANGE_PARK docks it.

Roadmap

Fool-proofing, in rough priority order:

• Run this branch on hardware. Calibration sequence, import and the safety gates are mock-tested only.
• Z-height / clearance check after picking a tool, before leaving the dock area — catch a bad grab early instead of dragging or breaking the tool on the way out.
• Block the stock touchscreen UI during Mainsail prints. The app doesn't know a print is running (it only tracks jobs it started itself), so the screen stays fully live — a stray tap can home, move the carriage, start a filament load, or fire its own toolchange into the middle of a running job. The module should lock the UI out (or at least its motion commands) while a Mainsail-started print is active.

HelixScreen / tool-changer-aware UIs

ff_toolchange also registers the Klipper objects that UIs written for klipper-toolchanger look for — toolchanger (status, tool_number, tool_numbers, tool_names) and tool T0..T3 (active, mounted, detect_state = present|absent from the tool's grab sensor, extruder, fan, gcode_x/y/z_offset) — and the commands they send: SELECT_TOOL T=<n> (= T<n>), UNSELECT_TOOL [T=<n>] (= TOOLCHANGE_PARK), INITIALIZE_TOOLCHANGER (state check, no motion). status is changing from before the first move until the sensors confirm the swap, error when the dock sensors disagree, else ready. ASSIGN_TOOL is refused — remap tools in the slicer. Nothing to enable; it is always on. part_fan in [ff_toolchange] is what gets reported as each tool's fan (shared fan_generic fanM106 on this machine). ff_toolchange itself stays (the printer-database fingerprint keys on it); the new objects sit alongside.

Verify from any machine that can reach Moonraker (port 7125):

curl -s http://PRINTER:7125/printer/objects/list | grep -o '"toolchanger"\|"tool T[0-3]"'
# expect all five names
curl -s 'http://PRINTER:7125/printer/objects/query?toolchanger&tool%20T0'
# toolchanger.status "ready", tool_number -1 (parked) or 0..3;
# tool T0: mounted/active false, detect_state "absent" while docked

Then SELECT_TOOL T=0 from the console and poll the query again: status goes changing, then ready with tool_number: 0 and tool T0 detect_state: "present". HelixScreen's log on connect should read [Moonraker Client] Subscribing to toolchanger + 4 tool objects, and its tool panel shows the mounted head and Park/Select per tool. The resonance commands are wrapped so they grab a head first (see Input shaper).

HelixScreen then runs its Tool Changer backend: tool slots in the sidebar and print status, per-tool temperatures and offsets, Spoolman per tool, the plain single-extruder runout dialog. Drop payload/helixscreen/printer_database.d/flashforge_creator5.json into HelixScreen's config/printer_database.d/ for auto-detection (ams_type: tool_changer, z_offset_calibration_strategy: firmware_managed). Its default Load/Unload buttons only mount/unmount the tool (SELECT_TOOL / UNSELECT_TOOL); to actually feed or pull filament assign LOAD_FILAMENT, UNLOAD_FILAMENT and PURGE from payload/klipper/config/ff-filament.cfg in Settings → Macro Buttons — a user-assigned macro outranks the backend, and the parameter dialog picks up TOOL / TEMP / PURGE_TEMP from the macros.

Reverse-engineering notes

Condensed notes from the firmwareExe analysis — recovered sequences, binary addresses, JSON semantics — live in docs/notes/: architecture overview, the Klipper-fork delta (including the Tn interception), who decides what — app vs Klipper (heaters, runout, doors, calibration; which "features" are dead code), the verified grab/release sequences, the offset model, the recovered nozzle-offset calibration and its Klipper port, and the full print lifecycle with the deliberate divergences listed.

Support

If this saved your build plate (or your sanity), you can buy me a coffee new hotend.