-
Notifications
You must be signed in to change notification settings - Fork 6
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
Homing setup suggestion #29
Comments
I will have to look at this again, but according to the documentation there should be default values for those parameters. And if you don't change the default value the parameter will not be included in the config. The only parameter that needs to be overridden is the |
Good morning,
I had started with a very bare bones config, I think it was the "testing"
one that was generated for 6x from the grblHal firmware compiler web site.
The question is, if you only have cycle in your homing and then activate
homing, will your installer analyse what is there and add enough parameters
to allow homing to function?
I'm suggesting some idiot proofing.
I do realize that there are potentially many different maybe configs, but
assuming it's a Cartesian type...
Cheers!
…On Wed, Mar 12, 2025, 05:51 Joacim Breiler ***@***.***> wrote:
I will have to look at this again, but according to the documentation
there should be default values for those parameters. And if you don't
change the default value the parameter will not be included in the config.
The only parameter that needs to be overridden is the cycle.
—
Reply to this email directly, view it on GitHub
<#29 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGUKYUTKZIGMRW5VGA2J3WD2T77SJAVCNFSM6AAAAABY2DNSZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJXGI4TCNBSGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
[image: breiler]*breiler* left a comment (breiler/fluid-installer#29)
<#29 (comment)>
I will have to look at this again, but according to the documentation
there should be default values for those parameters. And if you don't
change the default value the parameter will not be included in the config.
The only parameter that needs to be overridden is the cycle.
—
Reply to this email directly, view it on GitHub
<#29 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGUKYUTKZIGMRW5VGA2J3WD2T77SJAVCNFSM6AAAAABY2DNSZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJXGI4TCNBSGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi folks,
The web installer is amazing! Thanks for making it!
In the spirit of making it easier for a non-programmer to get started with FluidNC, I'd like to suggest the following improvements:
After tweaking my new machine to get all axis working, limit switches, etc. I activated homing, hard limits and homing would not work. After looking at the source config here is what was under homing for all axis:
homing:
cycle: 2
That's it. This is inadequate to get a machine to home. I had to manually add the following to each homing section:
positive_direction: false
mpos_mm: 0
seek_mm_per_min: 1500
feed_mm_per_min: 50
settle_ms: 250
seek_scaler: 1.1
feed_scaler: 1.1
These parameters should be in the Axis tabs in the homing section, yes? And perhaps defaults added to the config by simply toggling homing to on. Luckily I have another machine here that I could look at for reference. I'm sure I could have found this information in the wiki or another forum, but it would be amazing if you could simply toggle homing to on to make it easier to get started.
Perhaps there's a reason this isn't possible?
Cheers,
Tyler
The text was updated successfully, but these errors were encountered: