Chris Radek wrote: > I have two gears on my lathe. The gear change is done with M codes > instead of belts/levers, but that's not important. > > The important thing is the feedback to EMC is the resulting spindle > speed. If the gcode requests a speed that can't be reached for > whatever reason, spindle-at-speed never gets asserted, so the motion > won't start. YES, excellent! I knew about this signal, but hadn't made the connection that it was what I was looking for! > spindle-at-speed won't let the program cut at a wrong speed, > whatever the cause. I don't know if this is a full solution but it > seems good enough for me - maybe this can be part of your answer. > It would be better to have a program actually tell you what gear would be best for the requested speed, but using the at-speed signal is plenty good enough for me! Thanks very much!
(I still have to figure how hoe to get an encoder on my spindle, but that's purely a mechanical problem.) Jon ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
