I had the "S" problem only when trying to push S too soon.

Well I'm definately not an expert but we cut copper on an occasion here. I would start with speeds and feeds comparable to CRS and you shouldn't have any real problems. Also, copper tends to try to grab your tools, ecspecially drills, so make sure that the tool and part are held securely. I'm not sure about which material would be better. HTH

Yeah, it will definitely save some time.

Michael, I thought that was going to work but my tools aren't in order of the operations, meaning tool 5 runs before tool 3. Also, in this instance the job is already setup. Thanks for the help though.

OK, heres what I did. It was first programmed using a Haas machine definition that doesn't add the 50 to the comp, I then needed to change it to a Fanuc post and machine definition that DOES need the 50 added to it. When I went into the parameters I reclicked on the tool and it changed the dia. offset to 51. I guess my question now is, do I have to go through all off my operations and reclick on the tool to make the offset change? Thanks Jim.

Yeah, it's set to add to tool and I have it set to add 50. Like I said, it was working in MR1 and now it's not in MR2. Maybe a bug? Thanks for your help anyways.

Just installed MR2 and when I am posting with a Fanuc post it is not adding the "50" to the D value even though this is set in my MMD. It was working in MR1. Any suggestions would be appreciated. Thanks,

Worked great. Thanks again guys!!!

OK, I have finally made the transition from V9 to X2. Everything seems to be going pretty smooth so far. Right now I'm fine tuning my post and I ran into a problem with one of my Fanuc posts. It seems to be working fine except for drilling cycles, keeps putting some lines in the wrong spot. EX. O0000(NAME - TEST) G98G81Z-.05R.1F10. G80 G20 G0G40G80G17G90 T2 M60 M00(#1 CENTER DRILL ) G54X0.Y0. G43H2Z2.S3000M3 /M8 M5 M9 G91G28Z0. As you can see the drill cycle line is above the tool change. FYI, this post has been updated from V9, however, this is the only problem that I am having with this post and I really don't want to start over with a generic post if I don't have to. Any help would be appreciated. Thanks,

Thanks Pete! I tried bringing in the same surface with different surface deviation tolerances and they are actually different.

I suppose I could just try it and see if there's a difference.

I was wondering if your surface deviation tolerance settings will affect a surface that I brought in from another software. For example, if I brought a surface in with my tolerance set to .010 and then changed my tolerance to .0002 and brought in the exact same surface would my 2 surfaces be identical or different? Thanks, Jeromey

Thanks John!

Thanks guys, that did the trick!

After updating my post for X everything seems to be fine except for one thing. On the comment on the line with my tool call up "T1M6", the right parenthese ")" is missing. Any post gurus know where I can look in my post? Thanks, Jeromey

After I updated to MR1 my toolpath manager background color is now dark blue which makes it very hard to see the operations. I can't seem to find where to change this. Any suggestions? Thanks, Jeromey

Let's try again. http://www.emastercam.com/ubb/ultimatebb.p...6995;p=1#000000

I don't think the link work!

I have had this same problem and I have to download any updates from mastercam.com. See link below. http://www.emastercam.com/cgi-bin/ultimate...ic;t=016995;f=1

I've always used "wear" but would like to learn more about using "control". A few questions I have about "control". How would you program using a pocket operation? How would you program sweeping surfaces? What about speeds and feeds? I know that with some of our operators they would be in a lot of trouble if they had to calculate them theirselves. I guess programming with "wear" is the way I learned and unless someone can convince me otherwise, I will probably keep doing it the same way. Jeromey

I agree with John, let the operator adjust the depth. Then they can only blame themselves rather than the programmer(myself). Jeromey

quote: I disagree. It's been my experience that verify and the actual workpiece look exactly the same when surfacing. Sorry, I probably wasn't clear on what I was trying to say. I agree about look of the surface will be the same but I was referring to the stopping and starting of the cutter that I see when verifying at the slowest speed.

I agree with Slepydremr. Just curious, have you tried running the program on your machine yet? It stops in the verify because that is where the line or arc segment stops, however when you run it on your machine you probably won't see the "jitter" Jeromey

I use SolidWorks for designing and details, and Mastercam for programming only. I use Rhino for reverse engineering parts and some of our more complex molds. The way I look at it is Mastercams primary function is for programming and Solidworks primary function is for drawing. Just my opinion. Jeromey

Doug, I just used that feature for the first time. Awesome! Jeromey