On 2 August 2010 17:50, Schooner <schoone...@tiscali.co.uk> wrote: > I wrote a G Code sub routine called <m6> which takes 2 parameters, > current_tool and required_tool.
> Using G Code overcomes all the problems of trying to move a previously > defined axis during a M6 command. I can't help thinking that using a G-code routine (and, in fact, having the ATC defined as an axis) is sub-optimal. As you are using a homebrew HAL component, it might as well have an output that goes directly to a stepgen input, with no need for that stepgen to have anything at all to do with an axis. I think that the comp file was the right approach. One useful and easy modification to that would have been a pin that could be linked to the X-axis homing state, so that it would do a full rotation while watching a micoswitch linked to a knob on the toolholder, so that it could determine which tool was loaded. (of course three switches/optos if you could spare the input pins would mean that it could always know the loaded tool) -- atp ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
