VF2 keeps stopping

[gar]

050723-1631 EST USA

donj1:

It is very important to know if the program fails at exactly the same point if you remove part of the program preceeding the failure point.

Can you run this experiment?

.

[jwarren]

The code fragment where the machine froze up is as follows:

N5661 X16.6424Y12.3676
N5662 X16.6437Y12.3679
N5663 X16.6761Y12.3755
N5664 G3X16.6784Y12.3791I-.0006J.0029
N5665 G1X16.6782Y12.3801
N5666 G0Z.1
N5667 X17.0729
N5668 Z-.2124
N5669 G1Z-.3324F10.
N5670 X17.0727Y12.3791F30.
N5671 G3X17.0749Y12.3755I.0029J-.0007

The program would consistanty stop at line N5665. If you to remove the N5665 line from the program, the program would run properly with no stop in motion. I got an email from Haas on Fri. that they are still testing the problem.

As for the problems Geof mentioned: The potential crash using G70 only occured between M12.09 and M13.02. Using the wrong tool when performing a program restart with block deletes has been fixed from M13.08 and up.

[miljnor]

just to point something that someone else mentioned out.

You said you werent using line numbers and here they are?????

is this just for our benefit?

you should at least try it with no line numbers

[jwarren]

I never said anything about not using line numbers. The origional program that the problem occured in had line numbers.
Of corse, when I was troubleshooting the problem I removed the line numbers, but it made no differance. Haas has tested this in serveral different software versions and processor configurations, and found the bug occurs in some software versions but not in others. Its been submitted to the programming dept. and will be looked at to be fixed for the next version.

[crayner]

I've had a similar issue with my '04 vf2ss - was machining an outside radius curve say r=1" with a .375 endmill, the coolant shut off, the alarm light came on and the feed kept moving right along. I caught it (was on a finish pass) The error message said I was trying to cut too tight an inside radius (like a .125") with the .375 mill. reset the program and ran that toolpath again - same issue - rebooted the mill, problem was gone. It sounds like memory corruption to me - makes me wonder what kind of ram/flash is used and what the physical layout of the controller board looks like, but thats the EE in me...