2012/5/2 Michael Haberler <[email protected]>: > > The background was the following: we discussed changes which would permit > changing tool offset and cutter radius during a pause operation. > > Under the current scheme, this would mean: > > - the handling of parameters 5400-5413 needs to be changed in the > interpreter; something which wasnt considered a 'queuebuster' so far since it > wasnt possible anyway suddenly looks like a queuebuster. > > - changing a tool and its parameters during pause has no corresponding > underlying g-code operation, so I dont see any clean way to do this in the > current scheme since this is keyed to an *operation*
Thank You! I _think_ that executing appropriate toolchange command in MDI would tell interpreter, which entry from tooltable should be used further on. Does it answer Your question of a clean way to do it? Speaking of MDI, I somehow feel that executing MDI commands during pause might be a way to adjust some modal conditions without interrupting execution of code (unless they are reapplied in the code later on). Unfortunately I cannot think of an useful example :) How does this proposal affects ability to run MDI commands, when paused? Viesturs ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
