With Level 2 I can use that toolpath, but with only a single surface. I am sure this would be a cake walk with Level 3, but I gotta use what I've got. I can use parallel finish multisurface, but I believe there are better paths out ther for this application (probably on Level 3!).

Bump - If the description is confusing, take a look at the file on the ftp. Thanks again

I posted a file onto the ftp in the MCX folder called TIMRAD.mcx. The file shows a toolpath that I am having trouble creating. No laughing, but I only have Level 2 and I am trying to create a .050" Fillet on the corner of pocket that is milled from the top view through a radius that is milled from the front view. I tried using a 3D swept toolpath, but wasn't satisified with the results. On the file I have posted I created a 2D swpt toolpath and then projected that on the surface. Looks like it would work, but the Z is off. I would appreciate it if someone could take a look and come up with a better idea. Thanks

If you don't want to have a lot of "air" passes, take some measurements of your stock and draw it on a seperate layer. Define that chain as your stock. Lathe has stock recognition so it will only cut where the material is. Roger hit it too. You can define your cutting direction (face, OD, ID) on your roughing parameters page. Or use the pattern roughing cycle.

Why don't you just print to a PDF. I can select Adobe PDF as a printer and it makes a PDF. I've never tried it in Mastercam, but it works out of every other software on my computer.

Slick, Didn't mean for it to be a harsh welcome. I just noticed that the original was a pretty old post. Welcome to the Forum.

I hope that Jason isn't still trying to figure this out 10 months later.

Don, You're right. Maybe crash wasn't the right term to use, but an Overtravel alarm could happen. Edit: A crash could happen if the tool you are indexing to is longer than 6". [ 07-31-2006, 09:51 AM: Message edited by: Tim Simmermon ]

quote: Why not? Just want to know becouse I'm new to the whole "lathe thing". Let's say for this job you have a boring bar that sticks out 5", so you program clearance moves to Z6.0 and make a tool change. Next set up has a boring bar sticking out 6.5". Go to Z6.0, make a tool change and CRASH! Better to change in Ref Return for each operation.

I always radius into the part on a contour. There is no way to ramp up the feed gradually, but when you program a radius in it will gradully increase the spindle load. HTH

Glad I could help. With the amount of knowledge on this website, most questions are over my head so I rarely get to contribute.

RocketRay, I followed the instructions from this thread: http://www.emastercam.com/ubb/ultimatebb.p...t=010292#000008

Rocket Ray, Add the #25 format as shown below # Format statements - n=nonmodal, l=leading, t=trailing, i=inc, d=delta # -------------------------------------------------------------------------- #Default english/metric position format statements fs2 1 0.7 0.6 #Decimal, absolute, 7 place, default for initialize fs2 2 0.4 0.3 #Decimal, absolute, 4/3 place fs2 3 0.4 0.3d #Decimal, delta, 4/3 place #Common format statements fs2 4 1 0 1 0 #Integer, not leading fs2 5 2 0 2 0l #Integer, force two leading fs2 6 3 0 3 0l #Integer, force three leading fs2 7 4 0 4 0l #Integer, force four leading fs2 9 0.1 0.1 #Decimal, absolute, 1 place fs2 10 0.2 0.2 #Decimal, absolute, 2 place fs2 11 0.3 0.3 #Decimal, absolute, 3 place fs2 12 0.4 0.4 #Decimal, absolute, 4 place fs2 13 0.5 0.5 #Decimal, absolute, 5 place fs2 14 0.3 0.3d #Decimal, delta, 3 place fs2 15 0.2 0.1 #Decimal, absolute, 2/1 place fs2 16 0 4 0 4t #No decimal, absolute, 4 trailing #Default english/metric feed format statements fs2 17 0.2 0.1 #Decimal, absolute, 2/1 place fs2 18 0.4 0.3 #Decimal, absolute, 4/3 place fs2 19 0.5 0.4 #Decimal, absolute, 5/4 place fs2 20 1 0 1 0n #Integer, forced output # These formats used for 'Date' & 'Time' fs2 21 2.2 2.2lt #Decimal, force two leading & two trailing (time2) fs2 22 2 0 2 0t #Integer, force trailing (hour) fs2 23 0 2 0 2lt #Integer, force leading & trailing (min) fs2 25 0 4 0 4tl # G76 Cycle -----ADD THIS ONE Then make the following changes in the body of your post: # Thread output # -------------------------------------------------------------------------- fmt P 2 thddepth$ #Thread height absolute fmt Q 2 thdfirst$ #First depth cut in thread fmt Q 2 thdlast$ #Last depth cut in thread -----Change all the 2's to 25's in the above and then change this also #Setup for old or new style canned cycles if old_new_sw = one, [ result = newfs (16, thddepth) ----Change 16 to 25 result = newfs (16, thdfirst) ----Change 16 to 25 Hope that helps!

Chris, I talked to my reseller and you were right. In the area that you showed: #Setup for old or new style canned cycles if old_new_sw = one, [ result = newfs (16, thddepth) result = newfs (16, thdfirst) The 16 forced the format. The # 16 format was 4 places with no decimals, but it only allowed for trailing zeros and not leading. He wrote a new format that allowed leading and trailing zeros, then we changed it in both places. Thanks for helping!

I searched for "newfs" and along with what you show above, I only come across mill cycles.

Chris, This is the canned cycle in the post. I don't see anything in here to change. I am a rookie when it comes to post mods, so if I am leaving out any info , I apologize. pg76new #G76 threading new style pbld, n$, *sthdgcode, *nspring$, *thdpull, *thdang, *thdlast$, *thdfinish$, e$ pbld, n$, *sthdgcode, pfxout, pfzout, *thddepth$, *thdfirst$, *thdrdlt, pffr, e$ I don't see any format statements here.

Hey guys, I am trying to modify my G76 post to output numbers without decimals for my Q, R, P & Q values. The post turns out G76 P011829 Q.008 R.001 G76 X.5649 Z-1.1 P301 Q80 R0. F.0556 I want it to look like: G76 P011829 Q0080 R0010 G76 X.5649 Z-1.1 P0301 Q0080 R0. F.0556 I have tried changing the the first four variables on this to have a 16 format, but it is not changing the posted values. # Thread output # -------------------------------------------------------------------------- fmt P 2 thddepth$ #Thread height absolute fmt Q 2 thdfirst$ #First depth cut in thread fmt Q 2 thdlast$ #Last depth cut in thread fmt R 2 thdfinish$ #G76 thread finish allowance fmt R 3 thdrdlt #Thread R delta G92 and G76 fmt U 3 thd_dirx #Incremental X move for G76 mult starts fmt W 3 thd_dirz #Incremental Z move for G76 mult starts fmt P 5 nspring$ #Number of spring cuts fmt 5 thdpull #G76 thread pull off fmt 5 thdang #G76 threading angle Any ideas on what I could be doing wrong? This post is a modified MPLFan post that came with X. Thanks in advance!

It would be a nice feature for X2, but right now there is no option in the toolpath parameters to leave stock on the cutoff side. I draw all of my lathe parts anyways, so I do just as Chris suggested. Parallel the line by the distance required, move it to another layer, create cutoff path. Takes only a minute longer. JM2C

Yeah, I'm using X. Don't even have 9 installed anymore. Sorry.

In the backplot Dialog Box, underneath the Cycle Time, there is a section for Path Length. It is broken down by Feed & Rapid. This should be what you are looking for.

Mike, Check out this thread (active today). They have some great info there. http://www.emastercam.com/ubb/ultimatebb.p...ic;f=1;t=021674 With a single point tool, the tool will engage to your major OD and then helix with a Z level change that equals your pitch (.0179"). So everytime that your tool goes around in a full circle it will move .0179" in the Z. You can either start at the bottom and work your way up, or start at the top and work your way down. The advantages of both are discussed in the other thread.

Mike, Have you threadmilled before?

You would have to go with a single point thread mill such as the one linked below. It would be the most economical way as I believe you would otherwise have to make a special. http://www1.mscdirect.com/CGI/NNSRIT?PMPXN...&PMT4NO=9474376

Wow you guys are fast. That worked! Thanks.