On Sat, 31 Mar 2012 16:04:24 -0500, Jon Elson wrote: > Well, I don't know this part of the code, but I don't see the real > conflict. > When in control of the motion system, meaning the G-code is > explicitly > commanding all aspects of the motion, then the S-curve should be in > force. When in spindle-synchronized motion, all the trajectory > planning > stuff is on hold, and the spindle rotation programs the movement of > the > synchronized axis. So, the S-curve code of the trajectory planner > would > not be in control of the motion. This is the way it is done now, as > far as I know. > > What I'm trying to express above is that I can't see how Yishin's > S-curve > causes a fundamental conflict with the spindle sync. It may be that > he > cut this > out of the code for expedience, of course.
I do not see that there is a problem either, but it will take time to write and integrate things properly. ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
