On Wed, Sep 28, 2016, at 09:35 PM, Robert Ellenberg wrote: > That would certainly be convenient. What if we took it one step further and > automatically limit the maximum spindle speed for each G33 segment? It > would be ugly, but we may be able to stuff a spindle speed command into the > queue before adding the line segment. Combined with a message to the user > than this is occurring, it would be both safe and convenient for the user.
That assumes that the machine has active control over the spindle speed. Which is NOT necessary for threading and other G33 work. For example, my lathe has 16 spindle speeds which are determined by how you set the belts on the pulleys. The S-word has absolutely no effect on the speed. It doesn't matter whether you write M3S100 or M3S10000, the spindle is going to start and run at the speed determined by the belts. The spindle encoder tells LinuxCNC how fast the spindle is going and thus allows for synchronized moves, but: 1) LinuxCNC can't change the speed if it doesn't like it 2) LinuxCNC doesn't know the speed at the interp level, because the S-word means nothing. Only the encoder feedback can tell it the spindle speed. -- John Kasunich [email protected] ------------------------------------------------------------------------------ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
