On Mon, Jul 22, 2019 at 12:07 PM John Dammeyer <[email protected]> wrote:
> > So how is this solved? How would the A axis know the diameter and be > able to translate that a request of F14.7 should really be F360 when Z is > being moved at the same time? Odds are I've configured the CAM software > wrong but if I was going to just manually write some G-Code that involved > simultaneous motion what would I do? The math is not hard. Assume you are tracking the position of X,Y,Z. SO the cutter is at (x, y, z). Assume the A axis is parallel to the X axis and interectest the YZ plan at (Ya, Za) The distance fromt cutter to the A axis is just the pythagoriam formula = square root( (y-Ya)^2 + (z-Za)^2 ) Then you always divide the roation rate by the above distance and you get a constant cut rate. But (x, y, z) constantly changes you you need to re-compute the distance continously before every g-code command. Good thing you have a computer. I'd hate to have to write 4-axis code by hand. The above might by done by a g-code interpeter or the CAM software or a human coder. It gets slightly harder if the rotation axis is not parallel to either X, Y or Z axis. and even worse when three or four rotary tale are stacked as in say a robot shoulder joint -- Chris Albertson Redondo Beach, California _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
