Sorry about that Colin, that if statement you were talking about is very different now but is still an inline statement. I changed the whole post block after finding the tool_type$ variable. But I still have the problem of it posting out the cut length on only the first end mill just as described above.

ptooltable      #Tooltable output
      sav_spc = spaces$
      spaces$ = 1
	  stoolrs = stoolrs1 + stoolrs2
      sopen_prn, no_spc$, *t$, *tldia$, *stoolsol, pstrtool, no_spc$, sclose_prn, e$
	  if tool_typ$ = 10,
	  [	  
	  sopen_prn, no_spc$,	  
	    if stoolrsis,
		[
	        stoolrs
		]
	  stoolcl, stoolcr, stoolcc, no_spc$, sclose_prn, e$ 	  
	  ] 
      spaces$ = sav_spc	 

The post I got was modified by someone else who started with the mpmaster, cleared all the misc and added their own. mi1, mi7 and mi8 were the only ones free. I just went with mi1 after checking to confirm that it was not in use. The sub programs are working great, that isn't really the issue, well, not the root of the issue. The issue is more on how they want it formatted. B axis must rotate out side of the sub if it does not end where it started inside of the sub. I have been reading about buffers and am becoming more confident that this is the path I will have to take if I want this to work the way they want it. 

Okay, I got it!

Wait...

*reads it for a third time*

okay, yeah I got it. 

Lots to learn. Didn't really think I was black listed. Okay, maybe a little. I just ask for so much help I worry that one day you guys are going to push me out of the nest and get me to fly on my own kinda thing. I truly appreciate the help and know I don't give back even 10% of what I learn from this forum. I have been working on learning buffers and have been taking lots of notes. I am going to post all of my notes and links, maybe it will save some one some time down the road.

Okay guys, it is very unusual for no one to even comment on a post all day. I am starting to worry I have been blacklisted. 

Looked for the class, I know I am about two years late but was thinking you might consider doing another one. 

So here is the plan. We post out a program using subout attached to mI1. mi1 is the number of times to sub. If mi1 = 4 then you get g54 g55 g56 & g57 posted out, each calling up the same sub program with the new position. All fine and dandy, until you try to do that on a rotary and the rotary rotates inside the sub. Because the g54-g57 are setup before the tool path is seen the post doesn't know that the sub has rotated. I know every ones first thought is the same as mine, ether end the sub before rotations or send the axis home at the end of a sub. That's not how the boss wants it. Simple as that. He does want the tool to go home if B rotates but only if B rotates. So, the big question is, can I get the post to read ahead and know if the tool B axis ends at a different place than it started? I assume this needs a buffer. Never done a buffer. Don't want to start.

So i found param 17435 in the mp documentation. It's the one I want, but just to double check I dumped my parameters and looked for it... Couldn't find it. So I figured I would just try it out. 

if prmcode$ = 17435, stck_sol = rpar(sparameter$, 1)

But I didn't get what I wanted... I didn't get anything actually. Debug said stck_sol was 0 the whole time.

stck_sol     :     0   #initialize for stock stick out.

What am I doing wrong?

Yeah, Param 20004 and 20007 are the numbers you can use to define a tool in the post.

Well, that didn't really work. He sent me the MPmaster   The one from X6, I have the one from X8 so yeah.

I guess I could force it but why did my relieved shank work?

Ok jlw, trying to one up your post. 

Here is what I have so far.

(T1 DIA=0.250 SOL=0.75  1/4 ENDMILL)
(RS=0.750 CL=0.500)

But when I call a finisher tool that is the same tool, different number I get this.

(T2 DIA=0.250 SOL=0.75  1/4 ENDMILL FINISHER)
(RS=0.750)

Where did my cut length go? 

------------------------------------------------------------

ptooltable      #Tooltable output

      sav_spc = spaces$
      spaces$ = 1
   stoolrs = stoolrs1 + stoolrs2
      sopen_prn, no_spc$, *t$, *tldia$, *stoolsol, pstrtool, no_spc$, sclose_prn, e$
   if stoolcr | stoolcc | stoolrsis,
   [  
   sopen_prn, no_spc$, stoolcr, stoolcc,
  
     if stoolrsis,
  [
     stoolrs
  ]
   stoolcl, no_spc$, sclose_prn, e$   
   ]

---------------------------------------------------

Also tried this at the end of my ptooltable

--------------------------------------------

stoolcr = 0
   stoolcc = 0
   stoolrs = 0
   stoolcl = 0
   stoolrsis = 0

still no joy.

Here is this so you get an idea of the variables.

---------------------------------------------------

stoolsol     : 0     #Tool SOL
stoolcr      : 0     #Tool radius
stoolcc      : 0     #Tool chamfer
stoolrs      : 0     #Tool relived shank
stoolcl      : 0     #Tool cut length
stoolrs1      : 0     #Tool relived shank math 1
stoolrs2      : 0     #Tool relived shank math 2
stoolrsis      : 0     #Is tool shank relived?

... just realized I have relived... not relieved 

Sweet! Thanks JParis, Was just getting back on to state that I found tool_type in MPmaster

Does any one know where I can get a more detailed Parameter Reference .PDF or something?

I have the mastercam x8 nci & param pdf but it only tells me a little info like

10090 | Tool type ID number.

I want to know what each number from Param 10090 means.

For now I am going to just dump my param for each tool.

Thanks

Indeed. Thanks Colin.

Well initializing worked... Thanks

Any one wanna take a guess at why I am getting this error?

RUN TIME -PST(2016)- 'subprg$' must be set to 1 (overwrite) or 2 (append) to open auxiliary file.

psubcall   # Sub Call

        force_wcs = one
        toolchng = one
        force_wcs = one
        toolchng = one
        while sreps < sub_out, pm98_call  # Output M98 Calls to Main
        subout$ = one
        subno_2 = subno
        *subno_2, e$   # Output program number for SUB --------------------------------------- Post line 2016
        scomm_str, no_spc$, "PN", snamenc$, scomm_end, e$
        scomm_str, no_spc$, "SUB PROGRAM", *subno_2, scomm_end, e$
        scomm_str, no_spc$, *strtool$, scomm_end, e$
        if scomm_sav <> snull,
        [
        scomm_str, no_spc$, *scomm_sav, scomm_end, e$
        scomm_sav = snull
        ]

I never explisitly change the subprg$ and subout$ never gets past one. The program its self looks fine. Just throws this warning every time I try to sub.

I'm stumped.

Okay, I figured out part of it. I wanted pindex and not my pcout or pfcout. Pindex has the cabs update I was looking for.

It would probably be simpler to attach this to your scoolant string, just use it in place of your m7 assuming you are not already using it. Having it come on in mid cycle under specific conditions would be a real pain but this would do what you needed. I don't know there was a Generic 5 axis post.

Sorry, that was the Mplmaster for the lathe.

Mpmaster for mills is here; http://www.emastercam.com/board/files/file/1088-mpmaster-master-g-code-post-version-x9/

It's here on the site.

Check in the downloads then click on posts on the left hand side.

Here is a link.

http://www.emastercam.com/board/files/file/1089-mplmaster-master-g-code-post-version-x9/

I agree with Richard, your rate of return is phenomenal with this man. Colin continually supports those in need. I of all people am very greatful.
 
I should have noted this in the original post. The first thing I did was tried a pfcout. In my program I am starting with a B35 then move to a B-35. Like I had said, if I program it out right it works (B35 change tplane B-35). If I use tool path transform and then rotate the single tool path the 70 degrees the post doesn't out put a B-35. It doesn't out put anything. So I tried a pfcout. It spit out B35? So I switched back to pcout and stuck a !cabs in my post (only to debug) and it spit out a B-35. I just can't figure out why it will not up date only in tool path transform. NCI must be good because !cabs works. It isn't a pfcout vs a pcout thing, definitely a cabs update thing. I am thinking I missed a block call prior to seeing the pcout and in what ever block I missed there is a call to update.

Note Colin; alot has changed in my post from the last time you looked at my Z2G, I don't know for sure that I had this problem back then because I wasn't testing all the tool paths at that time. If you want to see it for your self I may have to send a new Z2G.

Thanks guys and enjoy the weekend.   I will be on Saturday Roll Call.

Colin, if you read this I fear you will find your self shaking your head because I have a feeling this is related to the modality function you just explained to me in some way or another.

I am working on creating a post for a HMC and the base is the mpmasterx9 that just came out. I have made lots of changes along the way but for the most part the variable names are the same. I am having a problem with the pcout which I have set to work on my B axis. Program a part and things are great until you try to transform a tool path. When it hits the pcout I am getting the tool paths original cabs and not the new abs. I have found that I can force an update in my pcout and it will work but I don't understand why it isn't seeing the change with out a !cabs

I am not going to post the pcout here because it is the same as mpmaster but there is one thing in it i don't get.

if index = 0 do all the things.

index is set by rot_index

rot_index is set by param 17408

I don't know how to figure out what setting in mastercam runs the 17408, MP.pdf says: index axis true/false.

Am I barking up the wrong tree?

   Pretty much sums it up.

Thanks you Colin. I fixed my noob mistakes and every thing is working again.

I have the post back on my computer now. I checked my setting in the MD and it is on. Support for old posts or what ever. That is checked. I ran the debug... scoolant is still null. So I went back and rechecked everything. coolant is on, support is still checked, none of the misc are messing with it. I am stumped.

Thanks Colin for taking a few to look at this.

I got a post working, sent it to my co worker. First thing he says is there is no coolant. So I go look and sure enough no coolant. I check my original copy... coolant works. I file compare the two... he changed a few formatting things but nothing that looks like it would affect the coolant. So I have played around with it, put some watches on my debug and ran it. Got to a break point after my scoolant. Scoolant = 0, prv_scoolant = 0, coolant$ = 1, prv_coolant$ = 0... Why isn't my scoolant updating? Did it again with a !scoolant and then it worked... but why do I have to tell it to update? I don't remember needing that before.

Being still pretty new to post edits I would love a quick run down on how updates work. 

Looked over my fstrsel and it looks fine.

# Coolant M code selection

sm09    : "M9"      #Coolant Off (Use sm09_0 through sm09_2)

sm08    : "M8"      #Coolant Flood

sm08_1  : "M7"      #Coolant Mist

sm08_2  : "M8"      #Coolant Tool

sm09_0  : "M9"      #Coolant Flood Off

sm09_1  : "M9"      #Coolant Mist Off

sm09_2  : "M9"      #Coolant Tool Off

scoolant : ""        #Target for string

fstrsel sm09 coolant$ scoolant 7 -1