If your parts are under 6 inch diameter, shoot me an email. It can't hurt to look.

I've had this same problem in the past. All other rotations will output fine. I just mirror the text and move on. If anyone figures it out, please post the fix.

Also, your rotary braking issue can be solved by just entering an "M11" manually to disengage the brake. An "M10" would engage the brake. Without the M11, your machine wants to brake the rotary after every block containing a rotary move. HTH

I will either create another arc, like you said. Or, I'll use the over-cut function to accomplish the same thing.

Usually, I will swipe a threading bar from one of the lathes and mount it in an endmill holder. It's not the most efficient method, but it works for odd-ball threads or small quantities.

It may be a problem somewhere else. I drip programs everyday with the MasterCam Editor. Make sure all settings are correct.

Unless I'm mistaken, this part would be a simple contour path, then transform rotate at 90 degree increments.

CNC Apps Guy, I would rather thread mill also, but this particular application requires a 3/8-24 thread over 4" deep. Without the four place feedrate, bad things happen unless the RPM's support a feedrate without a decimal. How can IPM be switched to IPR in the post?

Thanks everyone for your input. After some digging, I found this: code: pcanceldc$ #Cancel canned drill cycle result = newfs(12, feed) #WAS (9, FEED)<<<<<<<<<<<<<<<<<<<<<<< result = newfs(three, zinc) result = nwadrs(strq, peck1$) z$ = initht$ if cuttype = one, prv_zia = initht$ + (rotdia$/two) else, prv_zia = initht$ pxyzcout !zabs, !zinc prv_gcode$ = zero pcan pcan1, pbld, n$, sg80, strcantext, e$ pcan2 I changed the "(9, feed)" to "(12, feed)" and it seems to do what we want.

I was able to find this: code: fs2 17 0.2 0.3 #Decimal, absolute, 2/3 place (tapping feedrate) Still doesn't explain one decimal.

No, that doesn't affect the posted code at all. I'm thinking somewhere either in the control def, or in the post itself. I just can't find it.

Currently all linear feeds are posted with one decimal place precision. This isn't a problem for most operations, but operators are more comfortable seeing for places for tapping operations. How/where would I change this to post four decimal place feeds for tapping ops? Thanks.

I've always just used the Swarf 5-Axis toolpath output as 4-Axis, as Crazy^Millman says. Works well for our applications.

I've had the same problem. As stated, it seems to happen when the control def is changed or modified. I just make a copy of my stock solid on a separate level. That way, if it does wipe it out, I still have a "back up".

That seemed to work just fine. I knew there had to be an easier way! Thanks!!