2011/3/20 Michael Haberler <[email protected]>: > Options I see: > > a) do nothing and look in the other direction. > b) only restore the state saved at the global level if any > c) simulate a sequence of returns through all levels, restoring in turn > whatever valid state was preserved is found at that level > > The more I think about it, and heed the 'minimum surprise principle', I'd > prefer (different from what I proposed below): > > on abort: use b) only. This means only if either a M70 or M72 was executed in > the *main* program, that state is restored on abort. If no M70/72 was > present, nothing is restored at all. > > on program end: a) - do nothing (although same as 'on abort' would be an > option, higher suprise factor though).
My personal feeling is that both cases should be option A. In case the user wants to run a g-code file after abort and restore specific parameters, he can just insert appropriate command in the beginning of the file. This way there is less chance for some surprises, because I think that it poses a risk for injury or ruined part because of this. I think it is better to have it in a way - if something needs to be restored, then user should explicitly tell that with a command, because I got myself confused, trying to figure out, what happens, if user has aborted the execution of file. 1) if the g-code is correct, but there is some minor problem (coolant flow stopped, swarf has accumulated to much etc) user would just "pause", correct problem and resume. There is no need to abort whole process. 2) I think that abort is done, when there is either major problem with material/part or hardware or there is a mistake in g-code (which hopefully has not yet turned into problem with part). I think that mostly it would be wrong g-code, which would require editing it. And adding 3 more characters to restore parameters is not even a minor difficulty. So I am in favor of having user explicitly issuing "restore parameters" command. Note: this opinion is based on assumption, that parameters, saved at global level, are not erased, once program is aborted. Viesturs ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
