On 10/12/2015 08:54 AM, Chris Lesiak wrote: > On 10/12/2015 08:08 AM, andy pugh wrote: >> I think we need to consider whether we want arbitrary arcs or >> arbitrary working planes. They are not really the same thing. Out of >> interest, with the Heidenhain code, what happens to the apparent XYZ >> when you change plane? Are XYZ still in machine cartesian space, or >> does the entire coordinate system shift? > > If you decide that arbitrary working plane is the way to go, you might > also consider the Fanuc model. > > G68 X Y Z I J K R > > X, Y, and Z specify the origin of the transformed coordinate system. I, > J, and K specify a vector about which the coordinate system is rotated > by angle R. It is possible to have two G68 transformations active at > once, the second applied on top of the first. > > G69 cancels all G68 coordinate transformations. > yes consider these as models not the final implementation, the PMAC and Aerotech solutions are also different but Roberts suggestion that its an underlying translation that rules the way the standard interpreter acts afterwards is a good idea. The user interface is separate from the benefit/action TomP tjtr33
BTW when a simple ROTATE (not the 3D titl plane ) is used on Heidenhain, theres a machine parm that allows the DRO to show the new X' and Y' so radial moves make more sense. ------------------------------------------------------------------------------ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
