Bad E-stop switch maybe?
hello all,
I am a newb, but trying. I am having a problem with my new 440. I bought deluxe package440 with stand directly from Tormach about two months ago. I will call Tormach tomorrow morning but this is bothering me and would like to fix it tonight if possible. I was cutting a part out and ended up hitting the Estop. So I removed the part I was machining and followed shut down procedures. Now to the problem, when trying to reset the machine, after manually releasing the estop and hitting the green button (lights up) I receive an error stating failed to bring machine out of estop. Check power or db cable. Checked and everything seems ok, it had been working flawlessly up until that last estop. Power cycled path pilot, problem remains. Reinstalled path pilot with the disk and the problem persists. PLEASE help me
Similar Threads:
Bad E-stop switch maybe?
Jim Dawson
Sandy, Oregon, USA
Normally I would say go check the troubleshooting section of the manual (Tormach writes good manuals)... except they haven't gotten around to releasing that section yet.
Others have posted similar issues with the 440. e-stop followed by "can't come out of e-stop". The first version of the Leadshine MX3660 had some issues with burning up when e-stopped, but those were supposedly fixed.
There is an anomaly with the driver, where sometimes it seems to set a flag that won't clear when e-stop is activated. Try this: turn the barrel switch off for several minutes, verify e-stop switch is released, then do a normal power on. Coffeetek posted a similar thread were the condition cleared itself overnight.
Tim
Tormach 1100-3 mill, Grizzly G0709 lathe, PM935 mill, SolidWorks, HSMWorks.
Thank you for such quick responses! I am trying the recommendation of cycling the barrel switch. I did notice the troubleshooting is missing from the manual lol. I also saw the other thread regarding a similar issue. I will report back with any news. Thanks again!
No luck yet...
Ok problem identified. Tormach support walked me through a little trouble shooting and found that the driver failed. A new one is being sent out.
So in new machine bought two months ago and this hasn't been fixed yet??? WOW. This is bad if you can't use the E-Stop without frying your Leadshine drive. I know I have stayed heck away from e-stop button on my 440...
Dennis
I try to never hit the Estop when possible. Under Path Pilot, the space bar on the keyboard stops all motion. It is the first thing I reach for.
On the lathe and my Pulsar mill, hitting the estop also means rehoming the machine. The spacebar stops motion instantly.
Lee
ESC will stop the spindle. I start with space bar though, thats been enough
I too only hit the estop as a last resort (hasnt happened yet)
This paper explains why it happens:
http://www.cnczone.com/forums/leadsh...ml#post1785874
Gerry
UCCNC 2017 Screenset
[URL]http://www.thecncwoodworker.com/2017.html[/URL]
Mach3 2010 Screenset
[URL]http://www.thecncwoodworker.com/2010.html[/URL]
JointCAM - CNC Dovetails & Box Joints
[URL]http://www.g-forcecnc.com/jointcam.html[/URL]
(Note: The opinions expressed in this post are my own and are not necessarily those of CNCzone and its management)
Yup pretty disappointing
That is a great tip. Thank You!
Hitting the onscreen stop button also stops the spindle as does the spindle stop button.
I was not aware that the ESC worked too. Thanks for that. That saves grabbing the mouse.
I do have a touch screen on the Pulsar, which is also pretty handy.
Lee
UPDATE: received new driver, now the Y axis is acting up. When I go to reference, the motor just spins. If I try to jog it slowly, it moves. If I turn off limits, it moves. If I move it regularly, not overly fast or slow I get an error stating machine is in estop. Also when I reference the y axis, the picture on the main screen shows the yellow line moving well outside of the box. Called Tormach, awaiting a call back now. Maybe I'm wrong but I find this extremely frustrating.
I recently had the same errors setting on my Pulsar that runs under Path Pilot. It wound up being a limit switch.
Lee
Ok, hopefully last update on this issue. It was ... user error. I failed to set the numbered switches on the driver to the correct orientation. After a power cycle everything seems to be working again.