User avatar
BaronWilliams
Posts: 183
Joined: Tue Jul 15, 2014 8:30 pm

Ooze Shield Wipe Before Tool Change

To help prevent oozing when the current active tool head is done printing it's layer, it would begin to cool down (by having Cooldown extruder while idle enabled), and BEFORE the next tool head starts to finish the layer or start a new layer, the current tool head will trace the ooze shield it created as it cools down. This way, as it cools down, it's oozing back onto the ooze shield it printed.

The setting would be something like this:

Ooze Shield Wipe Before Tool Change
This is in millimeters, with the default 0 for the current behavior in Simplify3D. By setting it to 10 mm, before the tool change occurs, the current tool head will trace around the entire ooze shield it printed without printing for a maximum of 10 mm. This way, as the tool head is cooling down (by having Cooldown extruder while idle enabled), it is oozing back onto the ooze shield it printed. It would not trace ooze shields printed by another tool head. If 10 mm is not enough, it can be increased to whatever is needed. This way the tool head could cool down completely, and not have any oozing occur before switching to the other tool head.

Or another potential way, instead of specifying the setting in mm, it's specified in trace counts. Maybe this is easer. A default of 0 would do nothing. A value of 2 would make the tool head wipe it's ooze shield geometry 2 times, without actually extruding filament. Simplify3D already has the G-Code for making the ooze shield. In this way, it should just re-add that same G-Code X number of times, with the extrusion set at 0.

This will be a very useful feature for multiple head printers.

Currently, once the active tool head is done printing it's layer and it becomes inactive for the rest of the layer, it's time to cool it down and let the next tool head finish printing the layer, while it's cooling down, it is oozing filament. This is not ideal. I have struggled with this. There is currently no good solution to this. Especially when using PETG, which oozes like crazy.

Return to “Feature Requests”