Pressure Advance Calibration

Phaedrux

@devleon yes the wiki does mention that maps may form. It's like the slicers have been compensating for bulging line ends already. Try an additional 3-5%.

devleon

@Phaedrux

I changed the value from 25%, to 30% and to 40% with no difference.

Thinking more about it, I don't think it's Infill/Perimeter Overlap. Shouldn't it be the extrusion width for solid infill? After all the lines are now thinner on the first layer than before. This is what my config looks like in PrusaSlicer:

Printing the same G-Code with PA disabled, and I get a beautiful first and second layer with no gaps. As soon as PA is enabled, I get gaps in the first and second layer between the individual lines of filament.

Phaedrux

I don't let slic3r pick the extrusion width normally. All widths would either be same as nozzle size or a bit more. 200% for first layer is an old school hack for bed adhesion. Try with first layer at nozzle size and 0.2 layer height.

DanS79

@SnakeSP I feel your pain, as Ideamaker is the same way. It says i can put the seam anywhere, but it always puts it at a corner. I'm going to try this out with a large diameter cylinder instead of a square.

sunnywilson09

I know, but this is a bit silly.
I am using a cloned Titan extruder. A bad clone.

strips

Just want to share a few changes I made in the python script.

Prints a box instead of two walls
Tidied up the skirt generation as id did some strange moves
has a text block for starting gcode and end gcode

advance_cal_box.py.txt

MartinNYHC

May I ask for help interpreting the result? Looks like the higher PA is the better the result? I'm using a direct drive. Thanks.

MartinNYHC

This post is deleted!

Phaedrux

@MartinNYHC Yes it would appear that way buy you should also test with an actual print to check for any unintended behaviours of running with a high pressure advance value.

How long is your bowden tube? Have you tried the cube wall method shown here? https://duet3d.dozuki.com/Wiki/Pressure_advance#Section_Simplest_Method_Possible

MartinNYHC

@Phaedrux There's only a short PTFE tube between extruder and hotend. I think it's about 20mm. Will do some additional tests today.

avion23

I've updated the *.py file with

preamble
postamble
klipper compatibility
Marlin compatibility

advance_cal.py

These are my results:
Delta Fyling extruder PA 0 - 0.5 over 40mm PLA

Delta Fyling extruder PA 0 - 0.5 over 40mm PLA carbon fiber

duosvid

I have tuned PA according to the method in the wiki, not with the script, but by printing a 100mm cube and adjusting on the fly. I have settled on 0.7, with a bowden tube of around 480mm length.

duosvid

@duosvid said in Pressure Advance Calibration:

I have tuned PA according to the method in the wiki, not with the script, but by printing a 100mm cube and adjusting on the fly. I have settled on 0.7, with a bowden tube of around 480mm length.

overall surface and z-seam look better, I'm now getting gaps in the infill - not in the parameters though . .

Phaedrux

@duosvid said in Pressure Advance Calibration:

@duosvid said in Pressure Advance Calibration:

I have tuned PA according to the method in the wiki, not with the script, but by printing a 100mm cube and adjusting on the fly. I have settled on 0.7, with a bowden tube of around 480mm length.

overall surface and z-seam look better, I'm now getting gaps in the infill - not in the parameters though . .

It's not uncommon to need to increase perimeter overlap slightly after tuning pressure advance.

tmitch205

@dc42 said in Pressure Advance Calibration:

Yes that's a valid approach. It's on our list to add a generator of pressure advance tests scripts to reprapfirmware.org, but it hasn't happened yet.

I know this is a super old thread but wanted to check anyway. Has the generator been created and added? If so, could you provide the link, please?

jay_s_uk

@tmitch205 my version of the klipper one generated RRF compatible pressure advance tests https://jaysuk.github.io/Voron/PA/pressure_advance.html

sym

Couldn't get this working, turns out Powershell encodes terminal output as UTF16LE. It will crash the Duet when you try to start it. Convert to UTF8 and smooth sailing.

Thanks!