On Sun, Sep 26, 2010 at 03:58:24PM -0500, Jeff Epler wrote:
> I found that trying to interrupt the gcode, for instance by hitting ESC
> to abort, or F3 to switch to manual mode, the GUI would become
> unresponsive and the terminal would still show lines like
> LOG(G1 X0.300000 Y-0.660000 Z0.907000)
> after waiting a bit, and/or hitting F5 to return to MDI mode, the MDI
> that I had attempted to interrupt seemed to continue.
I've fixed aborting in next patch. So mode switch/task abort/command errors
all lead to stopping task. I've tested with this file (probe.ngc):
O<probe> sub
G38.2 Z-1 F10
G0 Z[#5063+1]
O<probe> endsub
M2
When hitting ESC it complains about probing
G38.2 move finished without making contact.
But it's not related to my patch since also appears in HEAD
> I also encountered
> Probe is already tripped when starting G38.2 or G38.3 move
> and
> Probe tripped during non-probe MDI command.
Theese seem to be fixed.
Pavel
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
