MF Did you get my e-mails?

Are you checking the tools in your NCI or in the magazine itself? If you're checking tools in the NCI just create a setup sheet.

What control are you using? I have a rotation macro subprogram for a Fanuc 18I horizontal. It should be easy to convert it for a vertical. E-mail me if you would like to have it.

Make sure that edit text is set at "N". If it's set at "Y" you can edit the text but not move it.

That was already turned off. Under partner setup on the same screen I even selected "select partner" hoping that turning off Mastercam completely would help. Nope

MCU puts in stock & tool notes in my .nc file. How do I get them out? My post won't put them on when it's running on another seat so I'm thinkin it's a config thing but I can't find it.

Copy what you have from pdrlcst into pdrlcst_2. You will then be able to tap multiple holes.

James ~ Sandybar, Thanks for the tip. I always thought it was RAM (only 512k) and having 20 windows open.

The best thing to do is to use the speeds/feeds in the catalog from the makers of the tooling. If your using Niagra tooling use the Niagra speeds & feeds for starters.

I think it's a RAM issue. When I get that I save the .mc9 file then reopen it. No need to reboot. Sometimes I have to regen the toolpaths, sometimes not.

When you say filename are you talking about the file path (c:nc602-342 op1.nc) or nci name (602-342 OP1)? for nci name; code: pheader #Call before start of file if met_tool = one, #Metric constants and variable adjustments [ ltol = ltol_m vtol = vtol_m maxfeedpm = maxfeedpm_m ] result = nwadrs(srotary, cabs) result = nwadrs(srotary, cinc) result = nwadrs(srotary, indx_out) "%", e spaces=0 *progno,"(",sprogname,")", e #<<<<<< this will add nci name after program number I don't know how to put in the file path. (never tried)

With our fadals I try to limit my rpm's to 2000. The book says 3000 but I have better luck at 2000. Also it's better if you round your feedrate to three places when rigid tapping. 2000/24=83.333

change pcout to pfcout.

Joe, Your equations in the first post are correct.

quote: Are you using a solid thread mill or an indexable one?Are there indexable 1/4-20 thread mills? If so could you tell me where to find them?

If you're using Hardcopy for printing you can layout on E paper and still run through the printer though the layout and dims will be smaller.

Rekd, quote: Since I'm going to prolly give this away...Could you please send it my way?

Thanks Rekd, That will save me a lot of work.

If I get 25 lines per toolpath operation it sounds like I should be able to use the demo. If I get 25 lines per tool I Won't be able to. The main thing I need is to read manual macro input which is mostly in three areas (pheader, tlchng_com, and peof) but reading through postblocks in these areas. The toolpath numbers themselves is irrelevant.

How about merging nc files from non mc9 files?(c:nctemplates?.nc)

Keep playing with it. The problem is probably something so simple that you don't see it. Is there a chance that you turned off the finish pass after setting the parameters? (is finish grayed out?) Is there a cutter comp number with the tool you're finish pocketing with? (don't know if that matters or not)

I've just called Mike and he's going to have the office send one out today. (Mayday, you better jump on Joel B., Mike's making him look bad ) If I can rename the post I might be also able to rename the .mc9 file or just use the samples. Thank everyone for your help.

Rich, Can you stick a .mc9 file into the demo?

Rich, Are the machining numbers inaccurate or does it post out machine control errors? I could care less about actual cutting path numbers but I would need the results from post editing to be accurate.

Mayday, Mike Stevens is my rep.