-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Add arbitrary G-Code at defined Z heights (in this case for nozzle cooling fan control) #4261
Comments
Slic3r supports "Conditional Gcode", a preprocessor function that covers your needs. In earlier versions of Slic3r the same functionality could be gotten with some clever use of markers and a post process script. Fan cooling already is able to be turned off for the first number of layers. |
Hi and thanks for the links, that is pretty much what I am looking for. Re the fan, I did not realize the settings for auto-cooling were for the additional fan, thanks for pointing out that it is already there. I just did not realize it, my mistake! |
Export a config.ini from Slic3r. That will get you started. |
Before layer change and after layer change would be your likely candidates. |
ok, so before and after layer change mean any time before or after and not 'directly before / after' (adding g-code somewhere in the file is not in the scope of my original question though)? |
Exactly as it says on the tooltip: before layer change inserts that gcode before every layer's print. After puts it after that specific layer. B0AB1AB2AB3A... where # is a layer's gcode, B is the before layer gcode, and A is the after layer gcode. |
As a feature request, I would like to be able to input arbitrary G-Code at defined Z heights. The need is there because I have a second fan to cool the nozzle. If the print is running, I could enter M106 P0 S128 (P1 is the main fan for the cooling block) for a half speed nozzle cooling fan as an example but I do not want to sit there and watch to enter it when necessary.
This would be good for several things;
It could be integrated with the layer height settings that already exist per object but it would probably be more flexible using its own tab so it would be independent of the layer height settings (or toggleable 'bound to layer height settings: on/off').
The text was updated successfully, but these errors were encountered: