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

[Feature Request] Ability to set the current DRO coordinate to arbitrary value (G10 L20 Pn Xn) #5

Open
iceboundflame opened this issue Jun 16, 2016 · 1 comment

Comments

@iceboundflame
Copy link

It'd be great to be able to set the current tool position, i.e. if I've jogged the toolhead somewhere and would like to define the current position as (-50, -10, 10), I should be able to edit the coordinates and easily redefine the current coordinates. Right now I have to write G-code in the terminal to do so.

IMO, the "pencil" icon implies "editing/renaming" the current position rather than moving somewhere. We could change this function to behave like similar machine control interfaces (Mach3, bCNC), in which clicking the DRO and changing the number redefines the current WCS (rather than moving the tool). We should still have button (with different icon) for "going to" a specified coordinate - that is also useful functionality.

Here are some related requests/questions:

  • I'd also like to have a one-click button to "zero out" each axis, without clicking the little arrow and selecting "Zero Out Work X Axis", which is dangerously close to "Go To Work Zero", as noted in Feature Request: Move to and set buttons #3.
  • What do you think about getting rid of the dropdown options for "Zero Out Temporary X/Y/Z Axis"? Then we can treat G92 as a selectable WCS just like G54/etc - if they click on that layer icon, only then G92 gets activated.

Let me know what you think. I'm happy to help with changes if we agree on the desired design.

@chilipeppr
Copy link
Owner

Absolutely 100% feel free to fork and modify. I agree with everything
you're saying. I think this widget was a progression of ideas through the
months and the layers widget only got added way later in the process, so it
makes sense to do all the things you're suggesting. Just keep in mind the
differences from TinyG to Grbl since it sounds like you're using Grbl.

On Thu, Jun 16, 2016 at 12:43 AM, David Liu [email protected]
wrote:

It'd be great to be able to set the current tool position, i.e. if I've
jogged the toolhead somewhere and would like to define the current position
as (-50, -10, 10), I should be able to edit the coordinates and easily
redefine the current coordinates. Right now I have to write G-code in the
terminal to do so.

IMO, the "pencil" icon implies "editing/renaming" the current position
rather than moving somewhere. We could change this function to behave like
similar machine control interfaces (Mach3, bCNC), in which clicking the DRO
and changing the number redefines the current WCS (rather than moving the
tool). We should still have button (with different icon) for "going to" a
specified coordinate - that is also useful functionality.

Here are some related requests/questions:

  • I'd also like to have a one-click button to "zero out" each axis,
    without clicking the little arrow and selecting "Zero Out Work X Axis",
    which is dangerously close to "Go To Work Zero", as noted in Feature Request: Move to and set buttons #3
    Feature Request: Move to and set buttons #3.
  • What do you think about getting rid of the dropdown options for
    "Zero Out Temporary X/Y/Z Axis"? Then we can treat G92 as a selectable WCS
    just like G54/etc - if they click on that layer icon, only then G92 gets
    activated.

Let me know what you think. I'm happy to help with changes if we agree on
the desired design.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#5, or mute the thread
https://github.com/notifications/unsubscribe/AHidbdcEQzOV-w0P3x95Q3bIXelafCuwks5qMP6YgaJpZM4I3G-C
.

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

No branches or pull requests

2 participants