I had my toolpath disappear off the main ribbon tab also. Sent it in to my local support and it's been kicked up to CNC software..possible bug they say? Save the file and re-open it. That's what the work around is for now as suggested to me.

Set helix rad entry in dynamic pocket to "0". Then use the drill start hole op to create an operation to drill. Keep the circle as it will mark the start location of the pocket and you can delete the drill start op and make your own drill op if you want.

If it's a 2D spline then create a draft surface at 10 deg. Then create an edge curve at the top of the surface. Create equal number of points along the upper and lower spline then 3d lines from each corresponding point. Long way around but maybe it works for now.

Are you using the helical entry/exit at top of thread option? The tool should helix on and off the thread if there is a possibility of the cutting insert still being engaged in the material.

This was the first wire I ever prog.--- many years ago. Here is a site that may help http://www.cam-1.com/Agie_programming.htm

In the operation, tool parmeter tab, Change NCI, check force tool change

Vericut 6.2, Mastercam launch .dll's do not work with my patched Mastercam X2 SP1 Mastercam X2(11.0.3.25) SP1, build date Fri, Sept29, 2006 does not work with Vericut 6.2 launch. I tried it on 3 different PC's Mastercam X2(11.2.4.6) MR2 SP1 build date Wed, Dec 19, 2007 the latest full install from Mastercam download site worked with Vericut 6.2 launch

Mastercam won't know the curve is a constant needing only a single Z/C move to get to the end. Muti axis programming spits out all req. vectors within the step/chord tol settings. I cut very large threads and I end up deleting most of the output and sub in a W and H.(incrmental Z and C). Maybe a custom post is the answer.

I had the same problem running XP. Our IT guy had to turn off some MS internal firewall setting. Maybe check with your IT dept.

You might want to check out the post block "prcc_call_end" #Add the finish spindle speed to the first move speed = n1_ss pbld, *n, "G1", *string3, e #, *speed,"!!!" In my case using mplfan I added a "G1"

Looks like if all IF statements fail then this is the only time #148 and #149 will be assigned. Move the assignments down to after all the jumping is done. Just my WAG(wild a** guess)

check file: circle test2 on ftp It might be OK

"prv_" before any varabile is supposed to store any previous value (ie) prv_yinc or prv_yabs. Does not always work and you never know is it is the value you want. You don't need to define this varb. The best is to define your own varb (ie) last_y and capture it at the correct post block such as pfyout or pyout. The correct post block to capture the y value at the correct time is what you need to play with.

Yes. I just regn'd your op1. It did not cut in order but it did cut all the chains. I did a new op with the same chains and it cut them in order. (with window chain). I would say its the regen of your original op that causes it to go out of order. Did you load in the v8.1.1 patches from emastercam?

I loaded up the file in my 8.1.1 and regen'd it without any changes and it seemed OK. I would load up the latest pathches for 8.1.1 and see how that works

How about pocket(2d), use the true spirial cut pattern. You can go from the center out or from the outside wall to the center.

I am experimenting with this now. This has very limited wire frame to generate the preceived surfaces. The more wire frame the better. Can you provide more detail(wire frame) as to how the surface will blend in the various corners. In other words the "branch points"

I had a look at your file. I like your use of the flowline toolpath best because it will break the cuts into Z slices which will output arcs in your tape file. If you use the finish shallow and 3D collapse then you will not generate arcs through the filter due to the xy and z motion caused by the concave surface. Set your flowline param's to cut from the outside to the center and climb mill. A stepover of .005 to .007 will produce a scallop height of only appx .0003. You could try this bigger stepover to avoid "rubbing" of the tool. Other than that tool coatings, material, speed, feed, rigidity, zero cutting speed at the center of a ball mill will have an effect also.

I gave it a try. On the ftp as "rotary helix tech.mc9" . It's really an axis substitution type toolpath as you are sub'ing the y motion for angular. You can xform, unroll the helix and cut it 2d with depth cuts then roll it back up in the op, or cut the rolled line-- the helix, and unroll it in the op. Both are included, same results. Turn on your axis sub in the display settings when you back plot it. Have Fun!

You could put the lettering on a different layer, change colours and use xform, roll, to place the geo on OD. Then go into the side view and rotate the rolled letters about the origin to place them in the exact spot-- ultimate control. Then contour, window rolled letters, axis sub, unroll.

I gave it a try. Back on the ftp as "wheel side two tech". I usually define stock and then pay careful attention to my lead in/out vaules. I usually set my ops to update stock, and/or use it as a boundry and/or extend contour to stock etc.

For a horz type application I chained up my helix and set the rotary axis setting in the contour toolpath to 3axis, about z. I posted it out and obtained YZ and the rotary motion.

I had a look at it in v9. If you change the roughing angle to something like 45 deg all seems OK. I think this file needs to be sent to your dealer and or CNC for further testing

From v9 try to write out an IGES file and read it back into v8. No toolpaths of course

In general and without looking at your particular application you need to break up the upper and lower geomentry at points that you need the chains to be sync'd - called branch points. You can look at the chains in ISO view and draw lines in 3D cplane mode that define the sections of geomentry that you need to sync up between the upper and lower chains. When you chain them up in wirepaths, 4ax set the sync mode to branch.