Well, It may have not helped rick, but it certainly helped me... We just got all our licenses converted to nethasp, and I wasn't picking up a solids license when starting mill9. Thank You.

Oh, and tool width can be same as groove width but not more.

You need to set roughing stock to zero, change "rough step" to "number of steps" and set it to 1, also disable finishing pass. This works every time.

BTW i agree with you, eeyore. Conventional cutting does wonders SOMETIMES.

I have been asked to change my programming methods from one of the machinist on the floor(imagine that) ~~~~~~~~~~~~~~~~~~~~ ssssso What ? He is from the low race creature ? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Actually, while this machinist makes a good point, a lot of them don't. A lot of them ask for things that don't make sense. I had guys ask me to stop putting comments in the program "cause it looks more uniform that way". I think he just didn't want anybody else to be able to run jobs he set-up, but who am i to question him.

OK, to force output of feedrate you have to do following go to "Motion NC Output" of postproc. In paragraphs plinout and pcirout change pfr to pffr. it should look like this plinout #Output to NC, linear movement - feed pcan1, pbld, n, psgplane, sgfeed, pexct, psgcode, psccomp, pxout, pyout, pzout, pcout, pffr, pscool, strcantext, e pcirout #Output to NC, circular interpolation pcan1, pbld, n, psgplane, sgfeed, pexct, psgcode, psccomp, pxout, pyout, pzout, pcout, parc, pffr, pscool, strcantext, e This will output feedrate on every line.

Whoops, I'm sorry, I forgot, To get the spaces you have to do this sg00 "G94 G01 F5000" #Rapid

There are many guys on here that know way more about this than i do. Hopefully one of them will chime in soon.

By putting * in front of a code you force PP to output it every time it comes across it. For example pbld, n, *sgcode, pfxout, pfyout, pfzout, e sgcode will be posted every time post comes across it.

Thanks Jim. Overlap and stepdown are not zero, and no you're not being a wise guy. Sometimes something as simple as that works, but unfortunately not this time. I tried updating the V9 post a few more times, just to make sure it wasn't a freak occurence. Right now I'm making a few more tweaks to the V9 post; When I'm done I'll update it and send it to Mastercam guys. Maybe I get lucky and the issue dissappears on its own.

BUMP Anyone? Help please? Is this something that our distributor should / could help me with?

Done all that, still no change...

I searched for it, and did everything as described in one of the posts, but it didn't do anything. I copied the whole section with updated parameter numbers, and double checked mapping. This is what I'm using fprmtbl 1 5 #Rough cut parameters 13343 depthcc #Was 10200 10407 clearcc #Was 10201 10202 xstckcc 10203 zstckcc 10214 directcc fprmtbl 2 4 #Finish cut parameters 13341 ncutscc #Was 10100 10101 depthcc 10102 xstckcc 10103 zstckcc fprmtbl 3 5 #Groove cut parameters 13358 stepcc #Was 10301 13138 directcc #Was 10306 13352 dopeckcc #Was 10312 10316 depthcc 13364 clearcc #Was 10320 fprmtbl 104 4 #Thread cut parameters 10811 xmaj_thd #Was 10411 10813 zstrt_thd #Was 10413 10814 zend_thd #Was 10414 10819 face_thd #Was 10419

Thank You.

I finally got my post tweaked to perfection, with a lot of help from you guys, and I ran it thru post updater thingy. The problem I'm having now is that it posts depth of cut and retraction in a canned cycle with values of zero, no matter whats set in the actual operation. Here's an example: ( ROUGH OD ) G0 X4.2266 Z.0616 X4.02 G71 U0. R0. G71 P120 Q130 U.02 W.01 F.01 N120 G0 X2.9703 S200 G1 X3.1717 Z-.0392 It should be: G71 U.13 R.01 Anybody else ran into this problem?