Replies: 1 comment 2 replies
-
In the CAM software. ioSender will also need radius input when wrapping X or Y to a rotary axis.
I am not sure I understand. It is possible to compile grblHAL with a tool table that keeps the tool offsets in non-volatile storage. And it is possible to specify tool offsets for all axes unless a compatibility mode limits it to one as for legacy Grbl. And tool offsets can be changed programmatically at all times. See G10 L1, G10 L10, G10 L12 and G43.x. Note the |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I have a basic question:
If I configure grbl with 4 linear axes (XYZA) and one rotary axis (B), how do I specify the radius of my workpiece that is mounted on B?
How does grbl know which linear axes are affected by the radius?
Think of this as a lathe with 2 sledges. X and Z are moving in B's radial direction. Y and A are parallel to the B-axis.
So my first question is: If I'm only using X,Y and B and I want to mill on the surface of a cylinder, X can be constant. When grbl calculates the velocity of the path, it has to be aware of the radius. How do I define this radius? Is this the tool length offset?
And second question: Can I define two different tool length offsets for the same machine?
Thanks!!
Beta Was this translation helpful? Give feedback.
All reactions