Am 10.11.2011 um 08:38 schrieb Chris Morley: > > > > > This would work in any mode (auto, manual, mdi) and would be a queuebuster > > like toolchange, HAL pin read, and probe - readahead would stop, interp is > > synched at end of jog, readahead continues > > > > note this has much narrower applications than jog-during-pause, but it > > looks humanly doable (i.e. for me) > > > > Is it worth doing such a restricted jog mode? It would solve my problem but > > I'd be interested to here what other folks think about it > > > > -Michael > > > > Would you be able to manually touch off in this mode? Lots of people want to > touch off new tool at tool change for non repeatable tools.
It would be part of the process, when using a remapped M6. The remap procedure would look like so (assuming manual toolchange): G30 (move to TC position) Mxxx (enable jog - this code terminates when a, say, 'continue' button is pressed) g38.3 ... (touchoff tool at tool length switch) so you cant touchoff *in* this mode, but it leads up to the steps to do it > Also would this be an idea that some day may pave the road to jog while > paused? If so it may be worth doing just for that reason. Only insofar as I'll understand motion a bit better after this I guess I've been discussing this with Andy a bit offline, but I dont see the light yet. There's a lot more involved in this than just doing what I proposed in this thread, like switching a motion context (snapshotting motion and tp queues), cover the reentry problem on context restore for cycles as well as plain moves, probably another offset managed in motion, and a truely instantiable interpreter to start with (what I proposed, buts that just the first 10% I guess) -m ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
