Skip to content

Releases: grant0013/KAMP-K2

Release list

v1.1.0 - Fix Orca change_filament_gcode Z=0 nozzle drag

v1.1.0 - Fix Orca change_filament_gcode Z=0 nozzle drag Latest
Latest

Choose a tag to compare

View all tags
@grant0013 grant0013 released this 18 May 13:29
v1.1.0
fd24447

Fix: nozzle drag at print start (Orca change_filament_gcode Z=0)

Orca's K2 profile injects a change_filament_gcode template that runs after LINE_PURGE at print start. The template uses {z_after_toolchange}, which is 0 before any layer has printed, so the slicer emits G1 Z0 F600 — dropping the nozzle to the bed and dragging it diagonally across to the first print object.

Upstream KAMP's 0.4 mm Z hop after the purge isn't enough to escape this, and modifying the Orca template would require every KAMP-K2 user to change their slicer config.

Fix (entirely in-firmware)

  • New variable_purge_z_hop in KAMP_Settings.cfg (default 2.0 mm) — controls the post-purge clearance.
  • LINE_PURGE now lifts to purge_z_hop and applies SET_GCODE_OFFSET Z=purge_z_hop so Orca's subsequent G1 Z0 lands safely at the hop height instead of the bed.
  • New G92 override (rename_existing: G92.1) clears the offset on the slicer's first post-purge G92 E0 — emitted in the layer-change block, between the bad Z=0 line and the first real layer Z move — so the first-layer height is unaffected.

No slicer config changes required. Existing users just git pull and restart Klipper.

Upgrading

cd ~/KAMP-K2
git pull
# then on the printer:
/etc/init.d/klipper restart

Tested on K2 Combo (CR0CN200400C10) with OrcaSlicer 2.4.0-dev.

Assets 2
Loading

v1.0.0 - K2 & K2 Plus confirmed working

v1.0.0 - K2 & K2 Plus confirmed working

Choose a tag to compare

View all tags
@grant0013 grant0013 released this 21 Apr 19:21
v1.0.0
38ffc17

First stable release. Verified working on K2 / K2 Combo / K2 Pro (F021) and K2 Plus (F008).

What you get

  • Adaptive bed mesh — probes only the area your current print actually covers, scales proportionally from your [bed_mesh] probe_count. Typical mesh time cut by 50-70% on small-to-medium parts.
  • Adaptive line purge — purge line sized to your print area, positioned at its edge. No more fixed front-corner purges that waste filament.
  • Board auto-detection — installer recognises K2 / K2 Plus / Combo / Pro and applies the right config per board (K2 Plus needs forced_leveling: false, K2 doesn't).
  • One-click Windows installer — PowerShell one-liner, no manual SSH, auto-installs Python via winget if missing.
  • Local PC backups — survive Creality firmware updates (their OTA wipes /mnt/UDISK).
  • Clean reinstall option — automated wipe + fresh install for anyone recovering from duplicated configs.

Install

Windows (recommended for most users):

iwr -useb https://raw.githubusercontent.com/grant0013/KAMP-K2/main/bootstrap.ps1 | iex

macOS / Linux / manual:

git clone https://github.com/grant0013/KAMP-K2
cd KAMP-K2
pip install paramiko
python install_k2.py --host <printer_ip>

Slicer setup (OrcaSlicer)

Replace your Machine start G-code with:

START_PRINT EXTRUDER_TEMP=[nozzle_temperature_initial_layer] BED_TEMP=[bed_temperature_initial_layer_single]
T[initial_no_support_extruder]
M204 S2000
M83

See README for other slicers.

Thanks

Huge thanks to Reddit user /u/nur00 who patiently tested through four different failure modes on K2 Plus, sending logs and tracebacks until we found the klippy:connect race condition that was halting the printer with key57.

Known issues

  • Chamber light off during Orca-uploaded mesh/purge — Creality's new firmware gates the LED on print_stats == "printing" state. Fix identified (inject SET_PIN PIN=LED VALUE=1 at top of START_PRINT), not yet rolled into installer. Cosmetic, not functional.
  • K1 / K1C / K1 Max — same architecture, should work, untested. Open an issue if you try.

Upgrade from prior install

iwr -useb https://raw.githubusercontent.com/grant0013/KAMP-K2/main/bootstrap.ps1 | iex

Pick option 1 (Update) or option 3 (Clean reinstall if you're recovering from issues).

Loading