Pressure Advance messing with travel moves

deckingman

@johnocfii Glad it worked out for you.

gnydick

But by @JohnOCFII changing his configuration, the problem is just being avoided, not fixed. The fact that PA makes any changes on a wipe, a move with no extrusion, but may have retraction, is incorrect.

bot

@gnydick said in Pressure Advance messing with travel moves:

@deckingman

But by @JohnOCFII changing his configuration, the problem is just being avoided, not fixed. The fact that PA makes any changes on a wipe, a move with no extrusion, but may have retraction, is incorrect.

PA is not a perfect system. For that matter, wipe-while-retract, and all the other slicer tricks are even FARTHER from perfect... so which do we prioritize? Generalized PA algorithm wins every time for me. Please don't change a thing

deckingman

@gnydick said in Pressure Advance messing with travel moves:

@deckingman

But by @JohnOCFII changing his configuration, the problem is just being avoided, not fixed. The fact that PA makes any changes on a wipe, a move with no extrusion, but may have retraction, is incorrect.

I'm not arguing with the fact that if PA is being applied to non extrusion wipe moves, then it ought not too. Take that up with the firmware author, not me - I'm just an end user like you.

But @JohnOCFII s extruder jerk setting was much too low regardless of whether PA was being used or not.

Having said that, many settings interact with each other. So for example, too low an extruder jerk will have adverse effects when using PA. Also, you may run into problems with too much retraction after enabling PA (because the two things do much the same) and should reduce retraction. That's just the way things interact with each other.

gnydick

@deckingman gotcha, just making sure

dc42

The next firmware release will ensure that pressure advance is not applied to wipe-while-retract moves. I didn't consider them when I wrote the original pressure advance code.

gnydick

@dc42 cool, thanks for clearing it up.

dc42

Should be fixed now in 2.03beta2.