Got it. Thanks for the help guys. HJ

I'm having a problem getting a helix entry on a rough pocket, constant overlap surface program in V8. I keep getting just a regular plunge and no ramp or helix. Now, I know I'm missing something, but I've tried several things and am not seeing it. Any suggestions? Thanks, HJ

So how does Mastercam's HSM version rate? Is it a decent program or is it just for show? I've used it on a few of my programs, but since it added time to them I opted not to use them. Anyone use it frequently and have any speed secrets? HJ

If I choose to run a 3-D program that is actually slower with High Speed Machining in V8 as far as run time, my only benefit then would be that the progam optimization would give me a better finish and be less stressful on the tooling. Am I correct in my thinking? HJ

Thanks lovell110 for your help. I ended up using a single flute carbide thread cutter that I had ground to the BSPT spec's. V8's thread milling operation worked great. HJ

Thanks for the response guys. lovell110, from what I can tell it's a BSPT. I'm using a Haas vertical mill. And it looks like we got 4 pieces to do. gmenzies, I like the idea of cutting it with one pass, I think my problem now is that the thread is 55 degrees. The off the shelf cutters look to be 60. So, if I'm going to get one ground, I kinda have my choice of which type to use. HJ

I'm challenged with the task of cutting some internal Whitworth threads (British Standard pipe thread) in Delrin. I think I can handle programming it in v8, but I'm not sure what the best tool would be to use- thread mill, threading tool, or like a custom ground double angle milling cutter. The major diameter of the threads is 2" and I only need about a 1/2" of threads. Anyone have any suggestions? HJ

Thanks for your help guys.....I'm on the trail. Shawn

I keep getting this error: Program Error MILL.EXE has generated errors and will be closed by windows. An error log is being created. I'm running V8 Mill with Windows 2000 working on 3-D data imported from Solid Works as a para-solid. I tried bumping up the toolpath allocation, but it didn't help. Anyone have any ideas? Can't take it much more. Thanks, Shawn

Dave, Thanks for your reply. My problem is actually in my "operations library" (.op8 files). I had compressed them originally when I imported them in from V7, but just to make sure I compressed them again and still the same result even with the info you gave me. The tools are all there for the operation, but the feed and speed data is lost. Maybe I need to re-import them in and try again?! Shawn

When we upgraded from V7 to V8 I imported my tool library from V7. Now when I insert my library info in to my operations manager, the speed and feed info drops back to the defaults. The tools are correct, they just lose their parameters. Am I missing something? Thanks. Shawn

Thanks Guys, That was it. I don't recall ever having that happen in v7, but I can see now that I'll have to keep an eye on that, especially when I import toolpaths. Thanks again, Shawn

Hi. I'm running v8 and my Mazak Post Processor is separating my program into two programs, tool 1 and then the rest of the program. It actually asks me twice to "enter name of the NC file to write" and if I don't give the second program a name, it uses the default "T". Why won't it post the program as one? Anyone seen this before? Thanks, Shawn

Dean, That was it! I shortened the file name and re-posted it and it went away. The last word in the file name was "panel" so that's where the "nel.mc8" was coming from. I wonder if Mastercam knows about that? Thanks a bunch Dean. If I had a Christmas Card List, I put you on it! Shawn

Dean, This is how my program begins: O0000 PROG (4900.NC) G90 G80 G40 G00 G54 N10 T1 T0M6 S4500 M03 NEL.MC8 X11.8185 Y-.4408 G43 H1 Z6.5 It doesn't do it on the smaller 2D programs, just the larger 3D. Could it be something in the data? Shawn