Update: I setup my machine to assert motion.feed-inhibit when the spindle falls below the target RPM. This saved a tool immediately. Within minutes of starting the test, there was a power surge that caused the spindle controller to go off-line and the machine stopped feed, saving the tool. There is one major downside to this, it added 26 minutes to the program I am currently running. The problem is that the machine does not jog to the next position until the spindle comes up to speed as it did with motion.spindle-at-speed, which allows the spindle to come up to speed while it is jogging to the next cut location. I am thinking that there needs to be a new pin that behaves like motion.spindle-at-speed with the exception that it stops unsynchronized feed should the condition become false again. Or at least a configuration variable that changes the behavior of the existing pin. Also, another problem that I discovered. During a tap cycle, if the spindle stops for whatever reason, all is sort of ok... The problem is that you can not manually back out the spindle because the Z axis will not back up! The Z axis will only reverse once the tap reaches the programmed depth. Or if the programmed depth has been reached, the Z axis will only reverse. I am not sure about the reasoning behind this, but it seems to me that any time that there is a spindle synchronized movement like the tap cycle, the axis should be slaved to the spindle no matter which direction it is turning. I am assuming that the reason that the slaved axis does not reverse is that it is permitted to use a pulse instead of a quadrature on the spindle. This seems broken. Maybe there should be an option to indicate that you are using a quadrature on the spindle so that direction is accounted for when slaving to the spindle. -Neil-
On Tue, Mar 29, 2016 at 10:18 AM, Neil Whelchel <neilwhelc...@gmail.com> wrote: > Hello, > ... > The problem I have with my machine is that the spindle motor is 65 > horsepower, and unlike the computer and servos, it is not on a UPS. > Sometimes when there is a power surge, it causes the spindle controller to > fault, so even though the power is back on, the spindle coasts to a stop. I > just need a good way of dealing with this. Today, I am going to use a > combination of the controller fault output and the spindle RPM compared > with the near function to drive the motion.feed-inhibit pin and see how > this works. > -Neil- > > > On Tue, Mar 29, 2016 at 1:40 AM, Gene Heskett <ghesk...@wdtv.com> wrote: > >> On Tuesday 29 March 2016 03:25:55 Neil Whelchel wrote: >> >> I agree with 90% of that. Restarting the operation here at the >> WOWElectronics shop has generally not been practical because the tap has >> slipped in the chuck, or the whole chuck holding the tap has turned in >> the boring bar type holder I use to hold taps on the carriage of my toy >> lathe. I lack the ability in a tap holder to grab the square rear end >> of the tap in a tool holder and positively prevent its moving. If I had >> that problem solved, and I drive the tap to the starting position in my >> G33.1 wrapper, then a rehoming of the lathe should put it close enough >> to restart the hole if the spindle faults because the tap is bigger than >> the spindle can do w/o bogging down. Editing the wrapper for a smaller >> peck so it doesn't trip off again of course. >> >> Cheers, Gene Heskett >> > ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140 _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
