Nozzle stops at perimeter change

Royce

@phaedrux
No wipe or coast is used (wipe + coast gave me worse results).
PA is disabled, Firmware version 1.21

dc42

It will be easier for us to work out what is going wrong if you share a GCode file that exhibits the symptom.

Royce

@dc42
Good idea.
Gcode file added to the Google Drive link from above

dc42

@royce said in Nozzle stops at perimeter change:

Additionally, the nozzle stops for a split second when it changes to the next perimeter(s) which also results in additional blobbing.
Does anyone have a clue why this stopping occurs?

Retracting 6.5mm of filament with speed 60mm/sec and acceleration/deceleration 2000mm/sec^2 will take 0.14sec. So will re-priming. Is this the "split second" that you observe?

Royce

Well, when changing perimeter lanes (from inner to mid to outer), there is no retraction. It just changes the lanes.
So I dont think the stop has something to so with the retraction.

dc42

I'm sorry, I misunderstood. Here is a sample perimeter change from your file:

G1 X168.762 Y144.337 E0.0357
; feature outer perimeter
G1 X169.050 Y143.953 F7200
G1 X169.534 Y144.346 E0.0231 F1800

It should complete the last extrusion of the inner perimeter (coming to a stop at the end of the move), execute the ~0.5mm travel move, then start the new perimeter. The time it takes to do all that will depend on your acceleration settings. If you are using a Bowden extruder and no pressure advance, then there will be some over-extrusion at the end of the inner perimeter, some oozing during the short travel move, and perhaps a little under-extrusion at the start of the outer perimeter. The fix for that is to use pressure advance.

Royce

That's good to know.
So I need to dig into the PA feature a little more, I didnt use it so far.
Any point to start?

dc42

For a non-Bowden extruder, try 0.05. For a Bowden extruder, try 0.2. For best results, search this forum for threads on calibrating pressure advance.

Royce

Thank you, I'll read it up
Very much appreciated!

Royce

@dc42
Do I need to set M572 in the config or in the slicer's start code?

dc42

It doesn't matter. I set it in config.g. If you find that you get best results using different values for different filaments, you can put it in the slicer start GCode instead.

You can change it on-the-fly by sending the M572 D0 Snn command from the GCode Console of DWC, or over USB, or from PanelDue. It takes a few seconds for the new value to take effect.

Note, if you use high values of pressure advance (e.g. above 0.4) then you may need to reduce retraction, to avoid over-retraction.