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.

Sign up for GitHub

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

Jump to bottom

Wipe tower starting speed as % generates incorrect speed #4251

Closed
dpeart opened this issue May 3, 2024 · 1 comment
Closed

Wipe tower starting speed as % generates incorrect speed #4251

dpeart opened this issue May 3, 2024 · 1 comment
Labels
bug Something isn't working as intended fix is live in the last release Please download /build the last release and try to reproduce.

Comments

@dpeart
Copy link

dpeart commented May 3, 2024

What happened?

When I used the defaults wipe tower speed of 80mm/s and wipe tower starting speed of 33% (should be 26.6mms/s) I got 594mm/s.
; CP TOOLCHANGE WIPE G1 X75.552 E3.2299 F35640

When I changed 33% to 26.64 I got the proper value
; CP TOOLCHANGE WIPE G1 X75.552 E3.2299 F1598

Project file & How to reproduce

First_Layer_Square_0.25.debug.zip

Version

2.5.59.6

Operating system

windows 11

Printer model

voron 2.4 with stealthburner
@supermerill supermerill added bug Something isn't working as intended fixed for the next version That means that you should be able to test it in the latest nightly build labels May 15, 2024
@supermerill
Copy link
Owner

When using a %, it was multiplied by 60 twice.
so you need to put 1.8% to get 33%

fixed in next nightly & release

supermerill added a commit that referenced this issue May 15, 2024
@supermerill
Fix Wipe tower starting wipe speed as %
57e2cd1 
#4251
supermerill added a commit that referenced this issue May 20, 2024
@supermerill
Fix Wipe tower starting wipe speed as %
e848103 
#4251
@supermerill supermerill added fix is live in the last release Please download /build the last release and try to reproduce. and removed fixed for the next version That means that you should be able to test it in the latest nightly build labels May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working as intended fix is live in the last release Please download /build the last release and try to reproduce.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dpeart @supermerill