-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can support Firmware Klipper ? #8312
Comments
Duplicate of #3452. We will likely add separate Klipper gcode flavor, but you can use Marlin legacy flavor for printer with Klipper FW (as recommended by Klipper author). I am closing this as a duplicate. |
We can do this, but only if you don't add some extra-code automatically, asuming that we are missing some thing. With macros on Klipper that don't exists on Marlin, we can simplify code on slicer, customizing it from printer configured macros. But if you consider that ower start_gcode must have a M140, M104, M190 or M109 and auto-added for me, you are adding something unwanted. Or like in this case, forcing me to add duplicated gcode because your slicer be sure that I'm not missing something important. For me, this two start_gcode must do the same from PrusaSlicer, and you can verify that result is diferent:
If you try to print ABS with bed to 90, the first start_gcode will be modified by PrusaSlicer to auto-add a prehead of bed to 90, when the second was to explicitly added. In both cases, my macro was yet controlling that, and result unnecesary if you don't add something unwanted. But because PrusaSlicer decided to add my bed was doing:
More power and time consuming that really was needed, only because you think that I miss something. Please only put the gcode that is really needed, one start_gcode or other, but not a third attemp trying to add something than can be missed without at least a warning. |
Can support Firmware Klipper ?
The text was updated successfully, but these errors were encountered: