On Mar 16, 2010, at 4:25 PM, Przemek Klosowski wrote: > On Tue, Mar 16, 2010 at 4:45 PM, Steve Blackmore > <[email protected]> wrote: > >> Not quite - press Feed hold, stop spindle then jog -X to clear tool, >> then +Z to get out of bore, replace tip. Start spindle, press cycle >> start. Tool did a combined XZ move at current feed rate to where it >> stopped then continued from there. > > That's a great example how it might be tricky in general. In your > case, > a simultaneous XZ move was appropriate, as would be Z followed by X, > but not X followed by Z. In another configuration (e.g. facing) the > opposite > would have been true, and I can imagine cases where neither would work > (e.g. a center stub in an undercut bore hole, requiring a Z->X->Z->X > move). > > This doesn't mean that it isn't a desirable feature that should be > implemented, > just that it isn't as simple as you portray it to be. Since a full > interference detection > doesn't seem sensible, it'd have to be some big fat warning window > that it's your > responsibility to clear the tool path.
Could you not record the path you have been jogging out? Then change the tool, do your allignment yada yada since the computer knows the path you jogged-out, you can use that to jog back in. That way you don't have to 'know' or worry about any clearance paths. Ries ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
