Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Poor PVA bridging on the wipe tower. #2818

Closed
alientek opened this issue Aug 26, 2019 · 3 comments
Closed

Poor PVA bridging on the wipe tower. #2818

alientek opened this issue Aug 26, 2019 · 3 comments

Comments

@alientek
Copy link

So im very sure im not the only one that has this issue, PVA cannot bridge regardless of temperature.

This results in a wipe tower like this:

https://i.imgur.com/r7EG1Js.jpg

The solution: Since pva cannot brigde, the way to solve this the most effecient way is to have petg or another material do the bridging. The wipe tower logic need to be changed a bit for this to work.

I have tried to explain this fix to support but they don't seen to understand to core issue here.

@rtyr
Copy link
Collaborator

rtyr commented Aug 26, 2019

Starting with PrusaSlicer 2.1.0-alpha1 release, wipe tower was improved. Maximum volumetric speed of an active filament is respected to limit the print speed on the wipe tower. It should help with the PVA bridging problem.

@alientek
Copy link
Author

@rtyr This makes no difference, my "Maximal bridging distance" has to be set to 2mm for it to work.

Wipe tower logic needs to be changed, speed change to 15mm/s might help but is a lazy fix and increases total print time.

@rtyr rtyr changed the title Broken feature: PVA interface Poor PVA bridging on the wipe tower. Feb 3, 2021
@lukasmatena
Copy link
Collaborator

This issue should be fixed for 2.4.0 release ( 97c4c02 ). When soluble filament is wiped on a layer, the preceding layer does not print the sparse infill, but instead prints (almost) full layer so the soluble filament does not have to bridge.

I'll close the issue. Let us know if you consider the issue solved after first public 2.4 alpha is released (in several weeks probably). Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants