Alex Zellner

I agree that would be a nice addition, if only klipper could generate the stuff inside ... You all forget that the current Implantation invokes the need to ssh in...

Could be handy to generate toggle switches inside the UI (Fluidd/Mainsail) und use them than as an enable feature insight other macros. Currently I recommend people using a Linux mcu...

@ckvsoft yes as klipper does not look in the future in the movement queue. So what you see is a up movement in z. That it might move down sometimes...

That code is working with mainline Klipper in a python3 env. So I am not sure why it should not work for you.

Never seen that before. .update is a base jinja function. ok ` {% set _dummy = filament_sensor.update({params.SENSOR|string: params.ENABLE|int}) %} ` The _dummy is a workaround here. Klipper needs a left...

So that is in my actual running printer I only shorten _dummy to have it equal in all configs

https://github.com/Klipper3d/klipper/pull/5149 That’s the old Klipper PR that explains a little better why we using this wotrkaround

@ColdBeer72 to clarify a few things here - you print never thru Mainsail. Mainsail ask klipper to load and print a file. After that Mainsail is a passenger looking what...

Yes it was I tried a lot to reproduce it but for me it works fine could you add a Pause before https://github.com/zellneralex/klipper_config/blob/master/input_shaper.cfg#L123 (G4 P2000) to insure that the files...

I will look in that again but since it runs on my machine it is really hard to debug.