Stephen Wille Padnos wrote: > My understanding of run from line is that it does execute the entire > program up to the selected line, simply not issuing NML commands for > motion or I/O (machine state). Yes, that WAS my understanding until this all came up! > Another point that I think Steve B quoted from the manual - the machine > moves to the endpoint of the previous line, and then executes the > selected line. In Jon's case, the previous line happened to be a > subroutine call. I think that shouldn't matter, and it's a bug if it > does. The observation that the program seems to start a few dozen lines > away from the selected start point is troubling, and may also indicate a > bug. It's possible that this is an observation error though - changes > in offsets could make the earlier lines execute in the machine position > that the later lines would have. (this is all irrelevant if the display > showed the later lines being executed. > Yes, in the example I provided, there are a series of lines like this : G01 X-- Y-- O100 call
I pointed to one of the G01 lines and did the run from line. It appeared to skip ALL of these lines, and went to the first G01 after that whole section of G01/call pairs. If it had a problem with the calls, I might have expected it to position to each of the G01's, but it appeared to skip them all. I was totally baffled by this behavior. It may have something to do with the state when the program was interrupted, and that's where the interpreter had left the queue, or something. I had a big chunk of aluminum in the machine, and was trying to get some parts made, so I didn't want to experiment too much when odd behavior was observed. If you or anybody else wants to try this program out, it is at http://pastebin.com/embed_js.php?i=QyjpZUD9 What it is supposed to do should be pretty obvious from the preview, machine 24 identical slots in a 1/8" thick panel, then one more rectangular cutout, then 2 round holes, and finally 8 oval patterns at the edges. I tried to restart at line # 41 which would be the 4th slot, but it did two linear moves in air and then appeared to go to line 113 and continue normally. I manually did a G54 and started the spindle with MDI commands, that made no difference. I am not sure I checked the Axis display, so I can't say for sure whether it was following what the machine did, but the fact that I did the G54 in MDI and that it appeared to go to the exact right starting point for the code from line 113 seems to indicate it was not fouled up with a wrong offset. I didn't let it actually cut metal in this condition, I restarted from the top and let it run the whole program without disturbing it. Jon ------------------------------------------------------------------------------ _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
