Originally Posted by Vern Smith  I'm glad to hear that an eminent authority like yourself also believes in Gremlins. They have been a constant companion of mine for 60 plus years. My CAM software always puts M30 at the end of a program but this brings up an interesting point, I did not let the program complete, rather I interrupted it when the control developed a mind of it's own and hit reset so the control never had a chance to see the M30. This was also the first time through for this program so I had used feed hold several times before coming to the comp problem. I do have G40 in my safety line.
Between the interruptions and resetting without the control seeing M30 you may have found the problem, excluding the most probable cause.....Gremlins 
Vern |
Did you do a program restart from a specific line number after changing the value? If so this might be pertinent; we where told in school that a program restart would use the last values picked up from the offset registries. It is suppose to be part of the restart routine that unless processing an M30 or starting at the beginning of the program where the controller has to actually process the proceeding lines of code, I assume making a call to the memory address where they are stored, it just performs a true not true check on them and that this could happen.