-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
Feature: Inputfields for undefined GRBL IDs #39
Comments
you can override this today if you'd like by a simple edit to grbl_settings.txt |
Works for me :) |
just keep in mind every time I push a new release any customization you've applied to I'm thinking through how to manage this better. |
well, by making it an inputfield for the 'none' values :) |
lol.... yeah, that covers it functionally... I still have to figure out how to actually manage it behind the scenes. I keep grbl_settings.txt in sync with GRBL. Allowing it to be editable deviates from the protocol (purist perspective). So yeah, it's a bit of refactoring for something I never expected to pop up as an enhancement request. GRBL is so loosely implemented though, I have to say at this point I'm not all that surprised. |
So that means you will implement this feature? :) |
For me, these additional $ settings are pure gibberish and incoherent. I honestly have no idea what the firmware author was thinking and he will not provide any explanations as to what he was thinking / trying to accomplish. |
there should no longer be ANY grbl flavor errors, alarms, and/or settings that are not captured by the plugin. At this point I have synced up all known variations across core Grbl 1.1, Grbl_Esp32, GrblHAL, and FluidNC. |
See enclosed picture; GRBL setting ID 33 is in my case the triggervalue for the G-shock.
However, in other systems, this can be a different value, thats why it is uncommented by default.
It would be a great feature if it was an inputfield, so people can manually document these exceptions for their setup
The text was updated successfully, but these errors were encountered: