Igor Chudov wrote: > I have a program that makes a special toothed adaptor. > > To do so, based on yesterday's suggestion, I change a coordinate system > changes to G54 with G10 L2 P1. (move and rotation). > > It even sort of worked the first time (cutting in the air). and works great > in simulation mill_sim. > > However, after I stopped the program and on restarts of the mill, when the > program starts it immediately moves far away from the part. > > Yes, this is the problem with G10. Based on some document somewhere, Ray Henry declared that workpiece offsets must be reset to zero after the program ends. When they changed this behavior, it used to drive me NUTS, as it was also reset on every abort. I had to write down the offsets between machine and workpiece coords on a piece of paper in case I needed to restart.
Anyway, Axis glosses over most of these details by resetting the workpiece offsets on every start. EMC2 has a G92.3 that puts the old offsets back in force, but usually Axis does that automatically. It may be due to your using the coordinate rotation that there is some interference with the restoration of the coordinate offsets. I have not used the rotation feature, so I haven't run into this. I think you may have to set up a simple experiment, and record the offset between coordinate system before and after running a tiny G-code program to figure out what is happening. Either the @ or # keys allow you to select between displaying machine and current workpiece coord system (one switches between commanded and actual pos, the other between machine and workpiece, I forget which and couldn't find it in the docs). I think what may be going on here is that if you use the touch-off feature in Axis, then Axis knows about the offset and can restore it as needed. But you have to use MDI to get the same result with the rotation, Axis probably doesn't know about the workpiece offset. Especially if you are coding the G10 L2 P1 into your G-code program, then what you might need to do is put a G91.1 before setting up your offsets. This zeroes out the workpiece offset first. Jon ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
