Skip to content

LW-PLA travel and ooze

Test prints / LW-PLA: the foam is the calibration

Two towers with avoid-crossing-perimeters on: strings across the gap show travel and wipe, not retraction.

Render of the LW-PLA travel and ooze test print as it stands on the bed.
Rendered from the STL, standing as it prints.

Toolpaths

Every extrusion move in the G-code, layer by layer. Drag the layer slider, scrub through the top layer, or play the print.

Slice

Toolpaths load when you open this view.

–

Colour by
Show

Read from the G-code that the printer gets. The clock adds each move at its programmed speed, without acceleration or travel, so it is shorter than the slicer's estimate.

Settings

On top of the stack that the print jobs load. The printer tuning page shows that stack.

PrinterFileChanges
Prusa Core One+A: Profile as islw-ooze a (core-one-plus).bgcodeavoid_crossing_perimeters 1
Prusa Core One+B: Wipe onlw-ooze b (core-one-plus).bgcodeavoid_crossing_perimeters 1wipe 1retract_before_wipe 70%
Anycubic Kobra MaxA: Profile as islw-ooze a (kobra-max).gcodeavoid_crossing_perimeters 1
Anycubic Kobra MaxB: Wipe onlw-ooze b (kobra-max).gcodeavoid_crossing_perimeters 1wipe 1retract_before_wipe 70%

Procedure

What it is for. LW-PLA oozes on travel moves, and the strings add mass and spoil the surface. Retraction barely works on LW-PLA, so this test compares the profile as it is with a wipe.

Print. Print both files on each printer: A with the profile as it is, B with wipe on.

Measure. Count the strings between the towers. Pull off the hair and weigh it.

Pass. No pass mark: the file with fewer strings and less hair is better. What helps is a shorter travel and a wipe, not a longer retraction. This matters most on the Kobra Max’s Bowden extruder.

Record. The number of strings and the mass of the hair, for A and B on each printer.

In the tuning log

Comments on

    Comments are reviewed before they appear. Please leave out places, addresses and other personal details.

    A Supported Systems Flight

    This build log is written and kept by Supported Systems, a small studio that makes thoughtful, user-first technology. The airframe, the hangar and the simulation are ours.

    Visit supported.systems