-
Notifications
You must be signed in to change notification settings - Fork 74
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
Automatic Tool Change #66
Comments
No, you should write your plugin to replace the current tool change code by claiming the function pointers early and setting Here are some code I have played with, a while back now, it may give you ideas of how to approach it:
|
Perfect! Exactly what I needed. Thank you Your approach seems very similar to mine, I'll be locking the drawbar mechanically and use the spindle motor to tighten/un-tighten it |
Hey! I'm writing a plugin for a DIY ATC.
When looking through the current tool change code, it doesn't seem like I can easily plug into the logic without modifying at least the tool_change.c logic to account for an ATC plugin (And adding an ATC entry in toolchange_mode_t)
Would this be the correct way to approach this?
The idea is to have GRBL move the Z axis out of the way, send a command either through UART or I2C to a different board that handles rotating of the tool umbrella, swapping the tool and giving control back to GRBL for probing once done.
I'd want this to result in an eventual pull request with example skeleton code in the near future hence I'm asking if my approach is right!
The text was updated successfully, but these errors were encountered: