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

[BUG] Spontaneous excessive homing feedrate #162

Closed
1 task
Ecky-Thump opened this issue Oct 6, 2024 · 2 comments
Closed
1 task

[BUG] Spontaneous excessive homing feedrate #162

Ecky-Thump opened this issue Oct 6, 2024 · 2 comments
Labels
duplicate This issue or pull request already exists

Comments

@Ecky-Thump
Copy link

Did you test the latest release build?

Yes, and the problem still exists.

Bug Description

After a period of time the homing feed rate will increase dramatically from a cold start. Only by resetting the settings can the original feed rate be re-acquired, but - again - after a cold start the excessive speeds return. M210 isn't enabled in the available builds, so I can't ascertain what the final actual excessive feed rates are.

Printer Model

Voxelab Aquila

Model Type

OG

Your Mainboard

Aquila GD32

Other Mainboard Type

No response

Add-ons that could be involved

No response

ProUI-EX | Extra Features?

Yes

Bed Leveling

UBL - Unified Bed Leveling

Did you include your own configuration files?

  • A ZIP file containing your Configuration.h and Configuration_adv.h.

Additional information & file uploads

No response

@Ecky-Thump Ecky-Thump added the bug Something isn't working label Oct 6, 2024
@classicrocker883
Copy link
Owner

I've uploaded a new release for October, the homing issue should be fixed, and some builds do have M210 enabled with a menu option to change these values.

you can find these values here in Configuration.h:
#define HOMING_FEEDRATE_MM_M { (60*60), (60*60), (8*60) }
X / Y: 3600
Z: 480

have you tried the new build?

@classicrocker883 classicrocker883 added the duplicate This issue or pull request already exists label Oct 10, 2024
@Ecky-Thump
Copy link
Author

Confirmed. I've been busy putting the the October 2024 build to use and can confirm that the issue is resolved. Thanks!

@github-actions github-actions bot removed the bug Something isn't working label Oct 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants