On Mon, Jan 23, 2017, at 12:29 PM, Gene Heskett wrote:
> > The catch-22. :) In your case & similar fixed speed no encoder situations > John, could you do an s number in your gcode 10% faster than the > nameplate speed for that belt position? I have an encoder. An encoder (at least a single pulse per rev) is an absolute must for threading. What I don't have is a VFD or other computer-controllable speed changer. > Otoh, I see this is becoming quite complex, trying to cover ALL > possibilities. Trying to save us from our own idiocy is frequently an > arduous task. Indeed. At some point the complexity introduced by trying to detect bugs in the g-code will wind up introducing bugs of its own. > So how about a halui button to check the file for > violations based on the s-word value at the time the g33/G76 code was > encountered in the file? Perhaps that would be easier? No halui button needed. The preview can do the violation check. As you say, it would use the s-word in effect at the point the G33 is encountered. John Kasunich [email protected] ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
