Just seen you already tried that, and you were not able to find your values?

If you want to see all the prmcodes put this in your pparameter$ post block "pparameter", ~prmcode$, ~sparameter$, e$ It may already be there, if so then just unblock it. It will show you everything the post sees. Alot more than whats shown in the nci file. Make your angles something unique like "22.2222" and "33.3333" so you can search for them. Post out the nc code and see what prmcodes they are. Also some prmcodes are accessed the fprmtbl function. Search for fprmtbl in the documentation to see how that works.

For tool length/offset equalling tool # I have this in our haas posts at psof and ptlchg before tool call: ..... tlngno$ = t$ tloffno$ = t$ pbld, n$, *t$, sm06, e$ ........ For on the fly coolant commands while posting you can do this: Declare these: test_cool_1 : 0 test_cool_2 : 0 fq 1 test_cool_2 "Turn coolant on? 0=no 1=flood 2=mist 3=tool" s_1st "Coolant not on for op " s_2nd scomm_sav In psof and ptlchg: if coolant$ = 0,[ s_2nd = s_1st + scomm_sav test_cool_1 = mprint(s_2nd) q1 coolant$ = test_cool_2 ] And to capture operation comment (must have a comment for each op) put this in pcomment2: pcomment2 #Output Comment from manual entry scomm$ = ucase (scomm$) scomm_sav = scomm$ It will tell you what op coolant is not turned on in, then asks what coolant you'd like. I tried getting it to change the question string, but was unable to do it, thats why it tells then asks. This will allow you to keep posting and let you go back and fix op coolant settings afterward.

Check your linking parameters. Most likely you have a retract and a clearance set, and these are the values your seeing in the code. (Could also be the feedplane and retract values)

Go to your control def, files, under message options set it to all error msgs to file. That will keep the non-fatal errors from popping up. You can look at the err file to see what is causing the concern as well. The msg your getting may be coming from the post itself or the machine def. Does it pop up before posting starts or while its posting?

Wakefest should be near the end of July. Will have to hook up at o'Cleary's with us in howell:)

Jim, I tried scalex$ with fastmode 0 and nothing. I haven't used it in forever, but thought it still worked. I tested it with mpfan.pst. Also tried inverting the x axis in machdef under componet properties.

One word Storkie.... Inhouse Posts. Well actually two words, but sounds better when you say "one word". Send me some sample code to look at.

Okay, I'd tried it and its broke. Not recomended, but this will flip X pfxout #Force X axis output xabs = xabs * -1 xinc = xinc * -1 if absinc$ = zero, *xabs, !xinc else, *xinc, !xabs pxout #X output xabs = xabs * -1 xinc = xinc * -1 if absinc$ = zero, xabs, !xinc else, xinc, !xabs I changed those two post blocks to get it to work, also need to swap G02 and G03. I say not recomended cause I don't know what post your using. You can try it and see if it breaks anything on your post.

yes, you can just type it in: scalex$ = -1

You can set the variable scalex$ to -1 to reverse/mirror the x

Thanks Jesse. Glad to see you back at adex. Jeremy is going to come to office for a techday to take a look at that post. Problem is he's waiting for you guys to slow down, and you guys keep speeding up

If the after is what you changed to make it work: I don't think the B placement is the issue, just the decimal in the B. Is the machine only capable of indexing, say in 1 degree increments? If so try just reformatting B to be an integer.

David, I can't attach a file to the forum emailer. Send me your email.

I got a sample file from okuma and fowarded it to inhouse.

Travis, Check under your control by lines and set "relative to direction". Was it the tool tilting or path fish tailing?

Getting back on topic... I have been talking with Inhouse for awhile as well as CNC Software. The goal of this partnership is to provide solid posts at an affordable price. Posts have gotten to be overly complex thru the years and taken away some of the end users ability to make simple edits to their posts. I have almost 20years experience writing posts and am definatley simple. Another new thing to be watching for is a post specific forum. Along with the post forum there are many other things we are doing to streamline the development and maintenance of posts. Kicking around the idea of having a standard post library on the ftp. I have been talking to customers and resellers for input on what direction they think posts should go in, and the general consenus is that they need to be simplified. There will still be posts that are paid for and maybe even some form of post maintenance. In the end though if we can give the end users the ability to tweak or write their own posts and share their knowledge with other users we will all benefit. I think this is going to be a great thing for Mastercam posts. Would like to here your thoughts on what we can do to make posts better for you.

I have several customers that have been using the inhouse post for quite awhile succesfully. As the machines evolve the post has to as well and inhouse has been keeping up. (Just seen Jeremy's post above

YOu could have the post raise Z by the tool corner rad, but I wouldn't. Verify would then be inaccurate. Instead, on 2d paths set your top of stock and depth + tool rad. I know its a pain, but the verify and code will then match up.

Check the math on post lines 236 and 237 (use edit-goto line) The postlines 242,245 and 300 have dollar signs where they should not be. HTH

Should work with either one, but I prefer using curve5ax on tuesdays

Try using comp to surface in your 5ax settings to keep from gouging the other surfs.

Depends on what material your cutting. The onsrud 5 axis is very hard to beat. There are cheaper ones on the market for cutting "light" and more expensive ones that have the same capabilities. Value for the dollar though they are great.

Harry, move the mastercam.kmp, mastercam.mtb and mcamx.config from mcamx/config folder to one you make up for safekeeping (incase this don't work). Then start Mastercam, it should recreate these files putting the status bar back in place. (If it doesn't work then put files back.)

You can do it either way. If you want to use toolplanes over wcs the post should pick up the total C rotation. If you use WCS then the post calculates the rotations from that plane only, this method usually requires you also set an appropriate work offset values in machine. Being on a horizontal does make the post logic different depending on how you want program it. (Mainly the fact that the Z axis is already perpendicular to the front plane.)