What's new
What's new

weird problem while running a program on my TM1P

ansoknives

Aluminum
Joined
Jul 31, 2005
Location
Denmark
ning a Haas TM1P and every now and then I run into a problem. In a specific line in the program the machine will stop moving....the spindle still runs but feed is zero...there is no error message or anything.....an excample below:

N2756 G0Z12.
N2757 X177.883Y-85.426
N2758 G1Z-3.63 F120.
N2759 X177.882Y-85.424
N2760 X177.848Y-85.359Z-3.643
N2761 X177.812Y-85.295Z-3.656
N2762 X177.775Y-85.232Z-3.669
N2763 X177.736Y-85.17Z-3.682
N2764 X177.695Y-85.109Z-3.695
N2765 X177.653Y-85.049Z-3.708
N2766 X177.609Y-84.99Z-3.721
N2767 X177.564Y-84.933Z-3.734
N2768 X177.327Y-84.642Z-3.8
N2769 X177.08Y-84.347Z-3.868


Program stops in line 2759....I found that manually changing the parameter from X177.882Y-85.424 to X177.89Y-85.43 will make the machine run with no problem.

This is metric, I use Rhino 3D and Rhino Cam ....I have contacted Haas in Denmark and they have no idea whats going on....

Any ideas? Anyone experienced the same?
 
Try having a different feed for x, y than z. It should add a F x.xx to first x,y line. I know the z line feed is modal and should carry over. Weird that changing y coordinate will start it. Not a overtravel issue is it?
 
Hmmm.. that's interesting!
Wonder if it has to do with the small amount of movement, which is below the programmable amount?
In imperial mode, the smallest programmable move is .0001. You're moving from X177.882 to X177.883 and from Y-85.426 to Y-85.424.
The total movement is .00223mm = .000088"

Not saying it's correct, but the control mighgt not be able to interpret it and stalls.
In FeatureCAM there is a parameter to set the smallest increment for motion by specifying 3.4 for the outputted coordinate values.
That means 3 digits before and 4 digits after the decimal. Anything smaller will result in either no motion output or 0.
For metric, the format is 4.3, meaning it would output a move in increments of .001mm, which is below the threashold.
Never ran across it, but perhaps it would be worth a try.

Just for giggles, see if you can change the 2759 block to represent a zero distance move.
IOW enter:
N2759 X177.883 Y-85.426

If that works, then the issue is likely a bug in the HAAS control.
 
Hmmm.. that's interesting!
Wonder if it has to do with the small amount of movement, which is below the programmable amount?
In imperial mode, the smallest programmable move is .0001. You're moving from X177.882 to X177.883 and from Y-85.426 to Y-85.424.
The total movement is .00223mm = .000088"

Not saying it's correct, but the control mighgt not be able to interpret it and stalls.
In FeatureCAM there is a parameter to set the smallest increment for motion by specifying 3.4 for the outputted coordinate values.
That means 3 digits before and 4 digits after the decimal. Anything smaller will result in either no motion output or 0.
For metric, the format is 4.3, meaning it would output a move in increments of .001mm, which is below the threashold.
Never ran across it, but perhaps it would be worth a try.

Just for giggles, see if you can change the 2759 block to represent a zero distance move.
IOW enter:
N2759 X177.883 Y-85.426

If that works, then the issue is likely a bug in the HAAS control.

+1 Agree with everything stated.
 
I had the same issue with a program, on my 2011 DT1 ran to a certain point, and stopped. put the same program in the VM2 and it ran right through. Graphics showed not issues which in the past had always been a good to test code before it was ran. Here is the video of it on you tube.Haas-DT1-Stops.3GP - YouTube
 








 
Back
Top