Ok, after spending the day trying to figure out what our problem was with the Axis reload pin that we added we accidentally discovered "axis-remote —reload”. Imagine that, an easy way to reload your file without modifying the Axis executable :-) However, in using that we discovered a bug in Axis. I can only say this bug was introduced sometime between 2.5.8 and 2.73 (that is the upgrade we just did). Here is the scenario that we can reproduce at will.
We have GladeVCP buttons for “Touch Off X,Y” as well as "Touch Off X", "Touch Off Y" and "Touch Off Z”. All of the buttons do essentially the same thing which is they call a *.ngc file which does the touch off (G10 L20 P1 X0, for example) and then executes M140 which now does "axis-remote —reload”. That’s it. If we press the glade button Touch Off X,Y it works great, every single time. The G10 executes immediately, the file reloads and bob’s your uncle. However, when we press the button for any of the single operations, "Touch Off X", or Y or Z, the G10 executes immediately the reload pauses for a long time, and then will complete but issues the error "window name "progress" already exists in parent” There is a video of the error happening here: https://youtu.be/eoaDq_Kz8rg These are three of the .ngc files that are called: touch_xy.ngc: o<touch_xy> sub G10 L20 P1 X0Y0 M140 o<touch_xy> endsub touch_x.ngc: o<touch_x> sub G10 L20 P1 X0 M140 o<touch_x> endsub M140: #!/bin/sh # Reloads the current file axis-remote --reload exit 0 ------------------------------------------------------------------------------ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
