Thanks for your submission--the patches applied without trouble.
Unfortunately, I ran into some problems when testing it.
I modified smartprobe.ngc to be a gcode subroutine, used the
servo_sim.ini sample configuration (but modified to use the AXIS GUI)
and then called smartprobe from mdi:
o<smartprobe> call [-1] [.1] [21] [-1] [.1] [21] [1.2] [-.1]
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.
on one occasion, I saw the message
USRMOT: ERROR: invalid command
which I am not familiar with seeing.
I also encountered
Probe is already tripped when starting G38.2 or G38.3 move
and
Probe tripped during non-probe MDI command.
but before I attribute them to your patch, I think I need to see whether
this happens in the unmodified version as well -- I suspect they do, and
they relate to not going to an appropriate safety height in smartprobe.ngc.
Jeff
------------------------------------------------------------------------------
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
