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

Request - Wipe Tower per-filament settings #556

Closed
gregspruce opened this issue Oct 28, 2017 · 13 comments
Closed

Request - Wipe Tower per-filament settings #556

gregspruce opened this issue Oct 28, 2017 · 13 comments

Comments

@gregspruce
Copy link

Per-filament settings in the wipe tower could help dramatically reduce waste and reduce print time.

For example, Fillamentum Nobble Blue needs significantly more purging than Rapunzel Silver to prevent bleeding into the next color in the model. If we could specify that Extruder 4 needs a depth of 20, while the rest need a depth of 10, that would reduce time and filament spent in the tower portion.

@bubnikv
Copy link
Collaborator

bubnikv commented Nov 6, 2017

that is another one on my list

I know Peter wrote his own post processor, providing richer configuration options.
http://www.kisslicertalk.com/viewtopic.php?f=27&t=1988

@cosmith71
Copy link

This is #1 on my wish list. There are some filaments I won't use simply because of the wipe required. Being able to adjust them individually would be great!

@gregspruce
Copy link
Author

gregspruce commented Nov 22, 2017

that is another one on my list

I know Peter wrote his own post processor, providing richer configuration options.
http://www.kisslicertalk.com/viewtopic.php?f=27&t=1988

I recently bought KISSlicer Pro, in large part for Peter's post processor and also for their automatic variable layers. Slic3r would benefit greatly from both of those features IMO.

@bubnikv
Copy link
Collaborator

bubnikv commented Nov 23, 2017

We have a new hire, Lukas Matena. He is now getting up to speed with the wipe tower code, he will try to integrate Peter's work into Slic3r.

@cosmith71
Copy link

That's good news! Welcome, Lukas.

@srepmub
Copy link

srepmub commented Nov 29, 2017

Yes, please! I love the MMU so far, but printing with common black is really painful..

@Blizzke
Copy link

Blizzke commented Feb 11, 2018

Yes please! With white in it I have to use at least 25mm to avoid color bleeding and that makes the print time a whole lot longer!
img_20180208_081735_818

@lukasmatena
Copy link
Collaborator

lukasmatena commented May 10, 2018

This has been implemented as part of the changes done on the wipe tower code recently. The amount of wipe can be adjusted for each filament pair separately, the ramming can be customized, wipe tower rotated, etc. Also, variable layer height is now enabled for MM prints.

The changes are already merged in the current master, public release Slic3r PE 1.40 is expected in several days. Please, give us feedback after you have the chance to test it.

I'm closing the issue now.

@Heinz-Loepmeier
Copy link

Where do I find per color change depth in 1.40.1?

@bubnikv
Copy link
Collaborator

bubnikv commented Jul 4, 2018

image

@Heinz-Loepmeier
Copy link

Is there a reason why these settings can't be found in Multiple Extruders->Wipe Tower settings?
I can't access 'purging volumes.." because of using alot of virtual extruders and slic3r won't let you scroll down.
slic3r

@Blizzke
Copy link

Blizzke commented Jul 5, 2018

because of using alot of virtual extruders

A bit off topic, but what system of filament mixing are you using if I may ask? (I assume that's the reason of the virtual extruders)

@Heinz-Loepmeier
Copy link

Heinz-Loepmeier commented Jul 5, 2018

@Blizzke
Diamond Hotend with Repetier firmware.
Repetier only allows for 16 virtual extruders, so you to overwrite mixing ratios of existing extruders via postprocessing to get more mixing ratios.
Slic3r and Slic3rPE let you define as many tools as you want fortunately, otherwise you would have a hard time replacing those tool change commands with the correct mixing ratio.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants