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

SEMM: wipe tower sparse infill speed adjustment #5415

Conversation

igiannakas
Copy link
Contributor

@igiannakas igiannakas commented May 21, 2024

Description

This is a follow on PR from #5304. After extensive testing with my ERCF + wipe tower I'm raising this PR to extend the use of the wipe tower maximum purge print speed to the sparse layers of the tower.

Increasing this speed again offers a significant time saving compared to the stock 90mm/sec especially in layers where there is no tool change as they are slowed down for no reason at all.

My testing with the V2.4 + ERCF shows speeds in the region of 180-200mm/sec are reliable as long as nozzle ooze is adequately controlled during the tool changes. If it isn't, the default 90mm/sec speed should be used throughout the wipe tower anyway to reduce the impact of nozzle collisions with the nozzle ooze.

Updated tool tip reflects the above recommendation.

image

With these two changes in this and the previous PR I've managed to shave off around 5 hours from a 24 hour print

Before these 2 pr's
image

After:
image

Tests

2x 24 hour+ MMU prints over the past week. No nozzle collisions at 180mm/sec and a significantly reduced print duration.

Purge tower was flawless:

IMG_3706

Copy link
Owner

@SoftFever SoftFever left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good
Thanks

@SoftFever SoftFever merged commit 43d7ac6 into SoftFever:main May 22, 2024
12 checks passed
@igiannakas igiannakas deleted the SEMM-Wipe-tower-sparse-infill-speed-parameter branch May 22, 2024 08:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants