SAVE_GCODE_STATE NAME=PAUSE ; save current print position for resume BASE_PAUSE ; pause print {% if (printer.gcode_move.position.z + z) < printer.toolhead.axis_maximum.z %} ; check that zhop doesn't exceed z max G91 ; relative positioning G1 Z{z} F900 ; raise Z up by z ...
SAVE_GCODE_STATE NAME=PAUSE ; save current print position for resume BASE_PAUSE ; pause print {% if (printer.gcode_move.position.z + z) < printer.toolhead.axis_maximum.z %} ; check that zhop doesn't exceed z max G91 ; relative positioning G1 Z{z} F900 ; raise Z up by z hop...
{%setspeed_steps=ns_speed_steps.arr%}SAVE_GCODE_STATENAME=speed_testing_macro{%settestRunCounter=namespace(value=0)%}RESPONDPREFIX="Speed-Test-" MSG="使用以下参数进行测试:"RESPONDPREFIX="-" MSG="distance_steps={distance_steps}"RESPONDPREFIX="-" MSG="speed_steps={speed_steps}"RESPONDPREFIX...
gcode: {% if printer.toolhead.homed_axes !='xyz'%} { action_raise_error("Must home axis first.") } {% endif %} SAVE_GCODE_STATENAME=_LIFT_M700 G91 G0 Z{params.Z} RESTORE_GCODE_STATENAME=_LIFT_M700 [gcode_macro m701]
I changed to a different switch, changed the logic from normally closed to normally open, and removed the "RESTORE_GCODE_STATE" and "SAVE_GCODE_STATE" from my macro. I don't know which of these changes to attribute the improvement to. I have two printers running the macro I posted ...
printer.state == "ready": script = {"script": "SAVE_CONFIG"} self._confirm_send_action( None, _("Save configuration?") + "\n\n" + _("Klipper will reboot"), "printer.gcode.script", script ) self.process_update(action, data) def process_update(self, *args): self...
gcode: TURN_OFF_HEATERS CLEAR_PAUSE SDCARD_RESET_FILE BASE_CANCEL_PRINT ### ### END of manual config ### ### ## <--- SAVE_CONFIG ---
If you want that, add this in your slicer layer cahnge instead [gcode_macro TIMELAPSE_TAKE_PARKED_FRAME] gcode: SAVE_GCODE_STATE NAME=SNAPSHOT G1 E-10 F2100 ;Retract G91 ;Relative G1 Z5 ;move up 5 G90 ;Absolute coordinates G1 X5 Y205 F6000 ;Move away from the print G4 P500 ;...
gcode: ;SAVE_gcODE_STATE NAME=SNAPSHOT ;M117 move your head/bed here, do retracts and so on ;G4 P500 ;dwell _TIMELAPSE_NEW_FRAME ;G4 P500 ;moar dwelling ;M117 don't forget to un-retract! ;RESTORE_gcODE_STATE NAME=SNAPSHOT
Prefix any sort of global state with _KM_ (e.g. _KM_SAVE_GCODE_STATE) Commit Messages These are the rules for commit messages, but you can also just look at the commit log and follow the observed pattern: Use the 50/72 rule for commit messages: No more than 50 characters in the ...