Skip to content
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

With start_gcode_manual, some prologue is omitted that is hard for custom gcode to recreate #2916

Closed
bjj opened this issue Jul 9, 2022 · 2 comments
Labels
fix is live in the last release Please download /build the last release and try to reproduce. problem

Comments

@bjj
Copy link

bjj commented Jul 9, 2022

What happened?

I turned on start_gcode_manual because I'm using klipper and I wanted to avoid generated M109 etc.

That code suppresses other things, in particular the initial retraction. The corresponding deretraction is still emitted in the code as usual. There is no variable with retraction length, so the custom start gcode must know the retraction length and must know it needs to have a retraction to balance the following gcode.

There are other things that are suppressed by that option which are important defaults (units: mm, absolute positioning) or are controlled by other slicer settings (such as relative E) that must occur in the custom start gcode for proper operation.

Project file & How to reproduce

20mm-box.zip

Version

2.4.58.2

Operating system

windows 20

Printer model

makergear m2 v3a with klipper

@supermerill
Copy link
Owner

Add that:

G21 ; set units to millimeters
G90 ; use absolute coordinates
{if use_relative_e_distances}M83{else}M82{endif}; use {if use_relative_e_distances}relative{else}absolute{endif} distances for extrusion
G92 E0 ; reset extrusion distance

for the retraction, i'll look of what may be the best option.

@rstanislav
Copy link

I have noticed this too, in print start i have purge sequence, but deretraction at start causes gaps on first layer, any solution to this ?

@supermerill supermerill added the fixed for the next version That means that you should be able to test it in the latest nightly build label Sep 7, 2022
@supermerill supermerill added fix is live in the last release Please download /build the last release and try to reproduce. and removed fixed for the next version That means that you should be able to test it in the latest nightly build labels Dec 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fix is live in the last release Please download /build the last release and try to reproduce. problem
Projects
None yet
Development

No branches or pull requests

3 participants