-
Notifications
You must be signed in to change notification settings - Fork 70
Lathe mode #458
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
Comments
|
I'll keep exploring this and report here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi Terje,
Thanks for this wonderful piece of software. It's really a great tool.
I spotted a few of "issues" (or things I cant make sense of). Tested on ioSender Edge 2.0.46p8, but I observed the same behaviour on 2.0.45
I selected "diameter mode" in the App settings (using a CNC lathe), but this does not seem to change anything.
The text above the DRO still reads Radius and X movements do not seem to be divided by 2.
When using the lathe wizards, it would be very useful to have the option to specify the spindle direction. At the moment, the output spins the spindle clockwise, which may be an issue if the lathe is setup as a conventional manual lathe.
I tried to edit the text output from the command generation (changing
M3
intoM4
), and pressed Tab (or enter). This results into an error message and the app crashed:"DispatcherException Unhandled expection occured: The method or operation is not implemented."
Not specific to lathe mode, but I am struggling to tweak the feedrate on continuous jogging. I run the app with the command line flag
-jogmode 1
. The wiki says the slow, normal and fast feedrates are then inherited from the keypad plugin. The feedrates I get seem fixed (normal 200, fast 500mm/min), and do not match GRBL parameters $50, $51, $52.I find the keyboard continuous jogging super useful and it could be useful to have the option to enable it in the App settings.
Last one, and probably a bit a detail, but would it be possible to validate a number entry in the DRO with Tab as well as with Enter?
The text was updated successfully, but these errors were encountered: