On 9/28/2016 9:35 PM, andy pugh wrote: > On 29 September 2016 at 02:32, Jeff Epler <[email protected]> wrote: > >> Besides the social aspects, some of my goals are to >> - take a look at some of the things in our github tracker that are >> languishing >> > One thing that I find myself coming back to, and is looking increasingly > like the real answer to "jog while paused" is extending the 'position.txt" > file, or a close relative, to include "last G-code line completed' and a > collection of states such as tool and spindle speed. > > Some users have said that mains power is unreliable where they are. If the > power goes off mid-job, then they want a pop-up next restart saying so. > > Is is possible that we have over-complicated the whole jog-while-paused > thing? Could it really be as easy as "re-start unfinished job" ? > On a similar note. I have wondered why we could not have another option for run from line "X" where the interpreter actually reads all of the previous lines but does not act on them just to make sure all of the persistent codes are set correctly for the program to run from the line without having to worry about the units, coordinate system, spindle speed, feedrate, etc.
Just a thought as sometimes restarting a program partially thorough can be a hair raising experience. Jim ------------------------------------------------------------------------------ _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
