cutting stainless can be a pain on a haas, I know I cut 304L on one all the time. Spend the money on the good tooling and it greatly eases the pain. I dont dry cut just good coolant flow, and Blaser coolant helps also.

it is on a haas though.

Im sorry that they gave you a hard time. I have had people quit on me and it does feel like the are betaying you, but I know that they found a better job. So i can not hold that against them, I have quit jobs also. Its hard on both parties most of the time, and your old boss turns into arshole mode. I hope the new job works out and you have some good people and equipment to work with, that goes alongway in enjoying the job.

defining stock has no affect on that problem, you can play with min. distant approach and lead out and lead in, sometimes that fixes it. It's just faster to use ref. points.

I found that if the boring tool you are using is close to the same size of the bore, the tool does not have enough space to do a retract move, and then it just goes home after the toolpath. I have had that problem and I use ref. point return, or just hand code the approach and retract moves.

its in the lead in/out menu at the bottom. You can extend or shorten your tool path. I use it almost everyday.

I think it simplified it for ya.

I remeber that someone had a test file time your computer, it was a mc file and you had to refresh the tool paths and record the time. The computers with the 10000rpm raptor drive were faster with the refresh, some alot faster. Im not saying that the hard drives made all the difference in the world, but the combination of high speed parts as a whole made the difference. It sound like you have an awsome system on the way, but for a small amount more you could wring out just some more performance from the combo. I would hate to get the computer and say I wish I had bought this or that for it. Most people forget that this is a tool, and you want the best tool to do the job, a workstation is alot less than a new seat of MCX level 3, or that new Yasda machining center . Hope this helps.

Everything looks good but the hard drive, to small. I would go with 2 36gig in raid 0, or 2 74gig in raid 0. They also have a 150gig 10000 rpm model also, I think it has a larger memory buffer for faster performance.

what controller is on it.

it is easier to see your drive surfaces with surface machine over solids, most of the time its easier to modify a solid than surfaces. You also have the boolean tools and history tree.

I use a tolerance of .0005 and 2:1 filter never had a crash with it.

did it work for you?

try a four flute.

If I see the grave icon on my computer it means instant death of my computer!!!! NO!!!!!!

if you were to put a pause in the program before the bar puller, would it repeat enough.

if you are still worried about the path get some scrap alum. and make some test cuts, just to be on the safeside. Im sure it'll come out just fine.

In this day and age service and support is just as important as the machine is in most respects. I sure that most companys understand that, also the supply of repair parts and technical support is a very good selling point.

thats alot of ram, I bet your parts move smooth as silk. How is your verify time? Mean video card also.

can you tighten up your tolerances in your filter maybe 2:1 and total tolerance of .0005. It could be in your graphics also. Do you have Metacut, I would look at the code in that if you have it.

Or if the crash is on that one file you could Ziptogo it.

If I have along program, I sometimes use M97 to jump to certain part in the program. I would do like htm said and use M98 and use a seperate sub program like M98 P101 L2 and dont forget to put a M99 at the end of the sub.

I had some info on M2 and it looked ok also.

I have used the mpsubs.pst and it works very well. Not much hand editing for verticals, but on hori. you have to ad rotation codes and maybe some clearance values. I always used Mics#1 on the first tool used.

I know of a place using Image software, I dont know the ver. the sad thing is they have MC9.1 mill and dont use it at all. It is sad, I used to work for them. Now I have my own shop and use MCX and I dont have any problems getting good code, it is a nightmare working for them. It takes them forever to make program changes and then it is very poor code. Has anyone ever used Image before? I never heard of it till that place.