Closed garethky closed 10 months ago
Made some progress:
SET_VELOCITY_LIMIT SQUARE_CORNER_VELOCITY=1
gcode required for PA testing. Right now its at the end of the start gcode.Implementing a parser for Prusa's start Gcode language is not something I think I have time for right now.
This needs to be verified with testing but klipper should be supported now.
I implemented a minimal variable templating engine for the prusa gcode templates so the start_gcode
can be re-evaluated. A very minimal set of values is provided, just temperatures and print location and size. If you used anything else more exotic its going to fail with an exception.
Object markers have also been added if the emitted gcode had an object marker present. This dive the plugin version of adaptive bed meshing.
I'm closing this for now. If klipper users have issues with their start gcode being processed we can open a new issue about the specifics.
Klipper is largely Marlin compatible and I already have code to emit the
PRESSURE_ADVANCE
gcode. But its not working with the function that updates the last M109 call's temperature.Klipper machines are usually configured with a custom
PRINT_START
macro. Its common to pass this macro the bed and nozzle temps for the print. e.g. this is my print start gcode from my Voron 2.4:This raw code is in the config that Prusa Slicer emits. I think I could parse that and substitute in the required variables. It doesn't have any of the lanugage features like conditionals, loops, expressions etc. This is simple
s/[first_layer_temperature]/240/
stuff that should be quick to prototype.Also, the checking for/modifying of
M109
needs to not result in an exception if its not found for klipper machines.