What are you trying to achieve might I ask? I remember reading WAAAAAAAY back when in a really nice speed and feed book, when drilling holes, after a certain depth / diam ratio, the speed and feed should be decreased by a certain amount. Is "this" what your a tempting to do? Looking at your output though, I dont understand why you would feed part way out of hole, then rapid all the way out.....is this to give time for chips to evacuate before rapiding out(possibly causing drill to bind up in hole)?

How about drill peck depth. How nice it would be to have the dialog populate with calculated values based on drill size. A dynamic numeric feature would be very powerful if it could poll info from other fields.

Thread resurrected!! So with X9 and now 2017, has there been a way to actually draw a non rotating form/broaching tool in mastercam and use it for verify / stock updating?

Well I think I figured it out, if anyone might need it and or want to see if what I did was correct. I added fmt 4 g_speed in the format section because g_speed is being matched against prv_speed which is also formatted 4. I added in the last line of "pspindle" a forced update of g_speed, forcing it to not be decimal point if css_actv$ = zero, g_speed = speedrpm, !g_speed This seems "atm" to be working for me. I will need to test multiple tool paths and see if I broke something. If anyone sees a glaring error I made, please inform me

Thats interesting. Thanks for the example. I was planing on doing something like that for deep hole drilling, but was going to tackle that after I figured this strangeness out. I have narrowed it down to if CSS is enabled or not. If It is enabled it seems to duplicate the spindle output many times, if G97 is used, it works fine. Just have to track down the flawed logic now.

I have disabled the "Use Canned Cycles" in my machine def drill cycles. I am trying to tweak the post to output correctly. There may be times I wish to not use a canned drill cycle. At any rate, with the MD disabled for them cycles, and I create a standard peck drill cycle, the post outputs the correct Z coordinates. If I however put a value in for the dwell, it outputs a spindle start and speed command after each peck. I tracked it down to the "pnullspindle" which gets called from "pdwl_spd$". #Toolchange setup, spindle output, pspindle must be called first pnullspindle #Null toolchange and dwell spindle change, g_speed is input if prv_css_actv$<>css_actv$ | prv_g_spdir<>g_spdir | prv_speed<>g_speed, [ #(1/10/2003) - test for coolant OFF (with 'cool_w_spd' mode enabled) if posttype$ = two & cool_w_spd <> zero & coolant$ = zero & prv_coolant$ > zero, pbld, n$, pscool, e$ #Switch G97/G96 or direction at null or dwell #Stop the spindle if direction changes if (prv_g_spdir <> g_spdir) & abs(prv_g_spdir - g_spdir) <> three, pbld, n$, pnullstop, e$ if css_actv$, [ speed = g_speed pnullg50 if prv_speed <> speed | prv_g_spdir<>g_spdir | prv_css_actv$<>css_actv$, pcss #(09/05/01) ] else, [ if (prv_speed<>g_speed | prv_g_spdir<>g_spdir | prv_css_actv$<>css_actv$) & g_speed, prpmnull #(09/05/01) ] ] else, pnullg50 I am not really sure what is going on here, or why its being called from inside the dwell, but i tracked it down to the second to last "ELSE" statement. A search the post doesn't find any "prv_speed" anywhere but in here. Perhaps left over from a older post? This is a mplmaster_x9 post. If I suppress this, does anyone know what else I may be effecting that I might not be aware of? Thanks.

Not sure if this is the best place to post this: Is it possible to put a formula in a field and have it updated based on other fields? For example, a dwell based on revs instead of seconds. So for example, in a dwell field, you would put a formula in that would calculate the time in seconds it would take to have the spindle revolve so many times, and have it auto change based on your spindle speed you set. I am talking about in the dialog boxes when you create a tool path and enter the parameters. Anything like this possible?

Thank you, commenting out that line worked and output the code as I would expect. Anybody know why that might have been on there?

Sorry, yes sorry, my original post shows C address output. I did make some tweaks to the original mplmaster for a few other things, and so to test to make sure "I" didn't butcher something, I used the stock mplmaster post which still has the "A" address output. The feed rate issue is the same in both cases though. The Y-Axis error i also get. The bottom turret of my machine does not have a y-axis, but the top turret does. I just click ok and it continues on. Anyways, thanks for the tip on the result=force(feed,feed), I will look into that and see what I can modify.

I double checked the retract federates, they are different that the feed rates, but I also have Rapid retract enabled. Attached is the z2g file. Its my first z2g file so I hope I got it all in there Post_Test_2.Z2G

Hi, I am using the mplmaster post for x9. Simple tool path using g112 and IPR enabled. This is a bottom Turret - Right Spindle tool G3 X.1395 C.9323 R.1975 X0. C.9348 R.9349 G1 Z-.1 F.0267 G1 X-.75 C-.9348 F.0267 F.0267 Z0. Z.065 F.0056 X0. F.004 This is a sample from the output. I know it doesn't effect how it runs, but I just wanted to clean it up a bit. You will notice the feedrate on the first retract is set at F.0267 IPR, and then again its output again on the next line, and then yet again on its own empty line. I was trying to trace it, but I still need to learn much more on post modification. I didnt see a *feed anywhere. I thought maybe it was being forced. I only seen a `feed, which when I read what the MP Doc said about the `, which says A numeric variable prefixed with the grave accent character ( ` ), which will be output only if there is other output on the current line of NC code. Well the one has no other output on it, so not sure why its outputting anything. Anyone want to lend a hand on suppressing these unneeded feedrate outputs?

Thanks again! I missed the section "pprep$ " changing that "rd_mch_ent_no$" from zero to one worked as I needed. Thanks again. And thanks for telling me how to obtain the MP documentation

This is what I am looking for. It worked for me in X3 but doesnt work in X9. I will add what you suggested and see if I can get it to work. By chance, where can I opbtain this MP documentation?

I have what seems to be an out dated X3 post reference from somewhere on line. I have X9, and I am trying to get the stock position. In the X3 reference, it lists the stock portion I am looking for as "prmcode$ = 17435" it seems 17435 is no longer used for stock? In my X3 post, I was able to use the line "if prmcode$ = 17435, stock_out = rpar(sparameter$,1)" under the pmachineinfo$ function. This doesnt work anymore in in X9. Can anyone lend a hand?

MPLMaster post, X9. I have the control definition set to use "Home Position" as the work coordinate selection. When using constant surface speed, at the end of the tool, it sets the spindle RPM to prepare for the next tool. The value its outputting is incorrect. Because I am using the "Home Position" as my coordinate selection, it want to go to the position set by the machine. The Post is using this value to set the RPM, and not the next tools starting X value. Can someone lend a hand with this?