Program and Machine Stop Running

[Awhite]

Sometimes i will be running a program that has been perfectly fine running for several days, it will just stop.
No error messages will pop up, the timer will still be counting down, just won't move.
I click to stop everything and try to move the probe with the jog box but it doesn't do anything.
I can still do things in the program but the machine itself will not run and cant get it to move.
The only way i can get it to work again is to power down the computer and then shut down the machine itself, then once i power it back up and everything is loaded back up it will run.
Just today I had this happen to me 4 times and it always stopped in the same spot.
Other times that it has done this its been different spots.
Please help as this is really annoying and a big waste of time. Thank you.

[RandomJerk]

If it's always in the same spot, you could have crap on the scales in that location which is throwing an error that isn't popping up. There's no chance there's something in the execution mode window that says something like E033 or 033, 034?

Anyway, that's my guess.

[Awhite]

I have not seen anything like E033, 033, or 034.

[louisd]

So there's some vagueness in the post. What is the spot? the "spot" = specific xyz coordinate location on the machine? "spot" = specific line of code within the routine?
When it does stop, how does your probe sensor react?
Will it still detect a hit?
Is the probe "damped"?
Are the motor drives active?
How does the machine respond to cycling a red e-stop when it occurs?

[Awhite]

It never seems to be specific spot on the XYZ coordinate on the machine and it happens on different parts randomly within the code.
The prob will not have taken any hit its usually moving to go to the next hit, nothing is hitting anything.
What do you mean about the probe damped or the motor drives active.
if the e-stop is hit a message pops up locking the machine and it wont unlock until you release the e-stop and press the message to open the machine back up.

[louisd]

Just today I had this happen to me 4 times and it always stopped in the same spot.
Other times that it has done this its been different spots.

These spots.. Your response above compounds the confusion, is it in the same spot on the machine, or the same spot in the code? You just said no to both, but somehow it always stopped in the same spot? what spot?

If you touch the probe while it is stalled/stopped what is the response of the probe?
If probe is damped (or machine drives are off, your status indicators will show an alert (solid red light on tp20/tp200 bodies, PH10 illumination lights are off, Jogbox "active" light on or off?) additionally, if your machine drives are off, you should be able to physically push/move the machine by hand with little force. if you give it a nudge and it doesn't move, then your motor drives are still active.

so at least you don't need to reboot the whole system, if e-stop fixes the issue, yeah?

[gibsonridge]

kinda sounds like a computer issue,, like there is something running in the background. or lack of memory
be sure you are meeting the minimum computer requirements.

[Awhite]

When the machine was bought the computer was supplied to us as well so i imagine that everything should be correct from the computer end.

[gibsonridge]

is this a new machine, how many software upgrades? windows version, how much spare memory is left?
is anti virus interrupting slowing things down ?
just saying there are so many things to consider. what changed ?

[Awhite]

It has been doing this randomly since it was bought. The machine is about 3-4 years old.
I was recently moved into my position and went to the training and am the first one to try and figure out why this is doing it.
We have not had any software updates yet. We are running windows 10. I am not sure exactly on the other things.

[louisd]

what probe sensor do you have? following the pulse of gibsonridge, if you open thask manager, do any resource restrictions surface when it does the stalling? (RAM or Processor consumption rates?)

[Cumofo]

IGNORE MOTION ERRORS = ON or OFF?
If you have an FDC controller, open up the URL: FDC Web Interface

now you may analyze and reset the error more effectively. Sounds like false triggers or motion errors.

unbalanced z axis, or a dirty air bearing etc.


FDC Interface.png

[Peter Fuller]

Sounds like a communications issue to me. Does this CMM drive through a network connection or a serial port?