Hi TPS/all
Sorry for the delay in response- been working on a 4th axis trunnion, and fighting with some control weirdness there.
Following up on this thread- I did look in M6Start and M6Send and see nothing there of interest (I believe it is only spindle start/stop).
But, I do see one legacy problem- first op on first run of the day can still runaway a bit. None of the others do. So, I wonder if there is some macro called, or a state in place, that would explain that.
Something else which is strange- noticed only with the change to a trunnion on the table now- is that Im seeing the coordinate system move on occasion, for no reason I can think of.
Example, I have my 000 at left center of the trunnion axis of rotation. And, that works. So, I may cut a part on the table- and all goes well. Then, I change ops to run say some finishing/drill op, and magically, X is now biased 0.1”. It is still G54, and when I see the cutter is clearly going to be in the wrong place on reposition- Ill stop the op, throw in an edge finder, and check the zero against the trunnion as was done initially. And for no obvious reason, X at 0 (where it might read 0.1 with the indicator being 0.2 dia) is now reading 0.2… And that is strange, because I don’t ever need to reset the WCS/G54 values in this setup; the part is on jig which was zeroed and proved previously.
Last night, I had a random change in Y by 0.3”. Yea, it sounds like a stall, but it isn’t; I don’t run unattended, and the op in question was supervised carefully. And, in years of using the system, I haven’t seen anything like this ‘until’ I started with 4 axis. Since this is random, it seems more a software thing than a post error or some inherent WCS problem.
Any ideas? I only operate in G54, so hard to know if this is a bug, or some weird implementation of a gcode call, or some macro I don’t know about.
Any help is very much appreciated.
Best regards
Rob