I've not been keeping up to date with email lately so excuse me if this is a bit late. While the interpreter may have looked ahead EMC should know exactly where it is when Abort is hit, shouldn't it? If so it should be possible to set everything to the state it was in when Abort is hit and forget what state changes it seen down the path.
Jeff Epler wrote: > Yes, that is behavior you should expect from emc. > > Except in a few special cases, the code in the .ngc file may be > interpreted in advance, even up to the end of the file. Things like > variable assignments, modal g- and m- settings, and the like may reflect > the state of the interpreter hundreds of lines later than the one that > was executing when you hit abort. > > This is a consequence of the way emc "queues up" many motions so that > the real-time code is almost always guaranteed to have motion > information available. > > Jeff > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
