Originally Posted by
mflux_gamblej
this it turns out isnt right. the work offset updates do work via DNC. it only appeared that they did not because nothing changed each time I ran it via DNC. what's troubling is that when you run the program from the control's internal memory, the results change everytime in terms of the found center. and it appears to begin to oscillate and get more variability the more you run it. that seems to me that either I am having some kind of variable initialization problem? or the control is doing something very unexpected / difficult to track down.
I verified that the DNC program does actually execute all macro statements and updates the work offsets by running it after i had run the program many times from internal memory. the work offset changed. then I ran the DNC program again, and No change. so that was confusing, and I ran it again over DNC, and it did change but only by 0.0001" in Y , 0 in x. I ran the program many times over DNC, and the results didn't change by more than +/-0.0001" each time I ran it.
Not believing what was going on, I went back to running the program from internal memory, and bam! the result changed by 0.0002 x, 0.0005 y, then -0.0002x, -0.0002y, and it began to oscillate again.
so I ran it via DNC again, and again the first change was large because it was vs. running from internal memory. Then the second DNC run: 0.0000 x, 0.0001 y.
unbelievable. any thoughts? why might there be some kind of lurking variable value when run via the internal memory, but not when run over DNC? (i verified that every single character of the program in memory is the same as the DNC - so it's not that).