Kirk Wallace wrote: >> > > > The only reason I put the G4's in was to try attenuate the low > acceleration problem. I wonder if it is worth fixing. > > I am getting the impression that the spindle index is what starts the > selected axis movement. No, I think there has to be more to it than that. If you can do multi-start threads, then the other starts would not commence movement at the spindle index, but offset from it by some angle.
Anyway, once spindle index has been achieved, the spindle encoder starts counting up or down from zero, and the index is not looked at again. The spindle encoder count then will count MORE than one revolution's worth of counts during the move, and not keep resetting to zero. > > - In my graph, the movement correction over shot the (wrong) target on > both sides over the course of one second. With decent PID settings, I > would have thought that the movement would have been a brief ramp to the > target with small corrections from the bottom towards the target line. > This suggest a different feedback loop being used? > > - How could subsequent G33's latch onto the last index of the previous > G33 before the current G33 is invoked? What persists between G33 calls? > I don't think they do - that wouldn't work, because the transition from one Z move to the next may not be ocurring exactly on a full revolution. If the movement needs to be continuous from one G33 into the next, then it would not re-sync to the spindle, but calculate the encoder count at which the transition would be made. Jon ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
