You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Grbl 1.1 - which seems the most common version - does not support canned drilling cycles. However, by default, that is what the post-processor will output.
One can add --translate_drill which alters the output back to G0/G1, but it seems undesirable that by default, it produces code that will not run. Especially as it is not at all obvious without fortuitously finding the information that this is what you need to do.
As there is already an option to turn canned drilling on, being --notranslate_drill, all that would have to be done is to alter the initial default in the code.
Full version info
0.22
Subproject(s) affected?
None
Anything else?
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
luzpaz
changed the title
Path grbl post processor produces unsupported canned drill cycles
CAM: grbl post processor produces unsupported canned drill cycles
Mar 16, 2024
Is there an existing issue for this?
Problem description
Grbl 1.1 - which seems the most common version - does not support canned drilling cycles. However, by default, that is what the post-processor will output.
One can add --translate_drill which alters the output back to G0/G1, but it seems undesirable that by default, it produces code that will not run. Especially as it is not at all obvious without fortuitously finding the information that this is what you need to do.
As there is already an option to turn canned drilling on, being --notranslate_drill, all that would have to be done is to alter the initial default in the code.
Full version info
Subproject(s) affected?
None
Anything else?
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: