My machine started moving on its own!!

[chipsahoy]

Anyone have there machine start up and cycle start on its own?? My previous problem was that it moved off location and cut a big round arc.. I have since disconnected my RS 232 while im runing.. Is there a groind fault that happens or do I need some kind of isolation product to fix this??

Chips

[Neal]

Are you saying the the machine tripped into AUTO mode by it self or did the axes start moving by them self? If it actually tripped into auto mode,i.e. start to run the program with spindle, coolant, and axes running per program, I would supect either a keyboard and/or 1090 interface problem.
I have NEVER heard of this happening in 50,000 plus machine out in the field.

Neal

[carbidecraters]

Light a candle and boil some water "the power of Christ compells you"..Be gone demon!

[chipsahoy]

Originally Posted by carbidecraters Light a candle and boil some water "the power of Christ compells you"..Be gone demon!

Thanks a bunch !!!

Im nailing this down to a comminucation issue.. I'll work off of neal's advise first.. Hopefully carbidecraters words of wisdom can be put on hold..

I did the "Keyboard test' and seems ok..


I did pull the cove on the monitor which is the "Membrane Keyboard".. Checked all the connections and re tightened for better connection.

I did experience the spindle RPM going from 7000 to roughly half again today. Which seems to be when it wants to loose position.. So im pulling covers and looking at the possibility of encoders and or a broken wire somewhere.

What else should I look for???

No Demons please !!

[kentsui]

You mentioned the "cutting an arc" on its own. One of my Fadals (a 2000 model 3016) has displayed a y-axis rapid move 6-8 times in the past 6 months on its own where it starts into a cutter comp arc (G2) and when it reaches the final arc point it just shoots the table back and hits the limits. The operator usually catches it but not always. Just last Thursday I was tweaking a program we have run for years and as it was making a G2 again in comp it fired the table off to the left in X and crashed the tool and cut a 10 grand hydraulic fixture ( not too bad but like one of your kids getting a chipped tooth bad). Fadal said 1) check the code for errors and (2) reseat the XYZ boards and one other and then pray. "Any way to diagnose it?" I ask.... "nope",. They mentioned resolvers too, but being a Y and X problem sort of takes that out.
It really does leave you gun shy. I have tooling hanging WAY out of tools now hoping that if it happens it'll only wipe the tooling and not the fixture and spindle. Now that its happened in X and Y on a program that has run literally thousands of times..I can hardly wait till it happens one day in Z!
The saga continues.....