2012/5/2 Michael Haberler <mai...@mah.priv.at>: > > Assuing that existed: when you hit 'Pause' and 'switch to MDI', the following > things need to happen: > > - The currently executing trajectory planner queue in motion is put to rest, > as is the executing task+interpreter instance (note I explored some of this > motion queue switching with the jog-while-paused code I recently posted, so > it seems doable) > > - a second instance of task+interpreter is cloned from the frozen > task+interpreter with all settings, parameters etc, and switched to MDI. > - motion now takes instructions from this second instance. you can now 'MDI > around'. > - when you hit 'Resume' a return move might be needed, and some copying back > any parameters which are possibly subject to change while paused. > - when done, switch back to primary task+interpreter combination, reactivate > the primary tp queue, and continue > > that's all ;) >
The way You explain it, it seems like a piece of cake for a small effort on one weekend :) About the 3rd point - restoring parameters. IMHO changing parameters would be the main goal to run MDI commands. User can already move machine during pause, so doing the same with MDI does not seem like a big improvement. But changing parameters is. Could You, please comment on this [silly] idea from the chambers in my head is: treat hitting "Resume" as a queuebuster operation, which updates all the changes of parameters in interpreter and continues the work with new parameters. I guess that I will get a lot of arguments for some parameters that are mandatory to be restored, so I thought that since different categories of parameters are meant to be introduced, I think that those parameters, affected by toolchange (and maybe probe) should remain - that way user could do emergency toolchange, probably measure the tool length on touch-off switch and then continue work. IMHO it does not make sense to implement such things like mdi-during-pause, if _all_ the created changes are reverted. Then only moving around stays as the benefit, which already is there. I think that if user does not want to change any parameters, then he/she should not run corresponding mdi commands in first place. 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 Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
