I am using the generic HAAS 3x post.

I have gone through this thread and checked all the things they said to check. I don't need this today, I'll get my notes from my other job and do the dame to convert it. I just thought there's be a way to unlock it in the operations and set it there.

Well, I thought this would have been simple... but guess not. I guess I have to tap with RPM and IPM in the operations and have the post calculate/convert it to IPR for the G code output.

There has to be something in the Config that toggles this. A switch somewhere that unlocks the tap feedrate and spindle speed so I can set each individually. I'll keep looking and if I have to modify the post, I will. Thanks

So I have gotten along pretty good with the MAZAK post converted from the HAAS post. Another problem ( hopefully last ) the MAZAK reads tapping feedrate in IPR and the HAAS in IPM. changing either the feedrate or RPM of the tap changes the other accordingly. How do I unlock this feedrate thing? I have in the past made a *feed and *feeds in the post because we had 2 FADAL machines, one that took IPM and the other IPR. so I just didi a calculation in the post to toggle, that way in the operations box, both programmed the same. I assume I don't have to go through all that trouble for this. Again, greatly appreciate your help Dan

Nice, so I can set individual operations to different smooth settings. I just looked at that. Up to this point, I never had to do anything under that tab. About the time I'm ready to retire, I'll know it all. Haha Thanks again for the help.

Yep, its in the MISC. tab. Looks like you have to pick a smoothness number for the entire program.

Hello everyone, thanks for reading through and giving me your input... I have a HAAS post that I have modified for MAZAK use and all is working great. I had to just omit the line ( with a # ) that posts out the HAAS G187 P* smoothness settings. well, we now need to use the MAZAK G61.1 smoothness settings. so I changed the callout to G61.1 P* from G187 P*. That is working fine. My question is how does the P* get changed? there are P0 "OFF", P1 "rough", P2 " Medium" and P3 " Finish" Where do these P values get set from? Is it in each operation as in I can set rough off and finish for each one? or is it in the post? I have no experience with this so any help is greatly appreciated. Dan

Yep, that got me where I want to be. Thanks for the quick reply Dan

I believe this can be done, but I have a part programmed and I want to just translate the same toolpath operations with just a new work offset. I want to use the toolpath translate because any change I do in the original, I want that same change to be in all four parts without having to change four operations. Any help getting me going is greatly appreciated, as usual. Dan

Okay, set by CD meant set by Control Definition. I'll remember that.

There it is, that was simple. under "Tool" "Enable staged tool routines" Thanks for the help. Dan

I have asked several questions and have gotten great help, now I have a tougher one for you. I am modifying a HAAS post to use in our Mazak mill and mostly are simple modifications. Removing "%" at the beginning and end, same with "M05" as it will sit until the spindle stops them go to toolchange but with it removed, it decels while moving to toolchange position. So, things like that. I do not know C programming but I notice patterns and have figured a lot of things out where it posts correctly without any errors to report. ( not bad eh? ) So I am wanting to get the prestagged tool functioning but cannot get it working. I am modifying the Generic Haas 3X mill.pst file and it looks as if no one has ever messed with it so it started at it comes usually with MCam. Here's where I'm at... These are the settings. at the top. stagetool : 1 #SET_BY_CD 0 = Do not pre-stage tools, 1 = Stage tools stagetltype : 0 #0 = Do not stage 1st tool #1 = Stage 1st tool at last tool change #2 = Stage 1st tool at end of file (peof) Tool change code... pstagetool is in the code and if I change it to "DAN", it does output "DAN" in the G code ptlchg$ #Tool change pcuttype toolchng = one if mi1$ = one, #Local Work coordinate system [ pfbld, n$, *sg28ref, "X0.", "Y0.", e$ pfbld, n$, sg92, *xh$, *yh$, *zh$, e$ ] inhibit_probe$ if mi1$ = three | mi1$ = four, #Work coordinate shift [ pfbld, n$, *sg28ref, "Z0.", e$ pbld, n$, sg52, *xh$, *yh$, *zh$, e$ if xh$ | yh$ | zh$, shft_flg = one else, shft_flg = zero ] if prog_stop = 1, pbld, n$, *sm01, e$ if prog_stop = 2, pbld, n$, *sm00, e$ pcom_moveb pcheckaxis c_mmlt$ #Multiple tool subprogram call ptoolcomment comment$ pcan pbld, n$, *t$, sm06, e$ pindex phsm_accuracy # Output G187 line for high speed machining accuracy control sav_absinc = absinc$ if mi1$ > one, absinc$ = zero if use_rot_lock & (cuttype <> zero | (index = zero & prv_cabs <> fmtrnd(cabs))), prot_unlock if convert_rpd$, pconvert_rpd pcan1, pbld, n$, [if gcode$, *sgfeed], *sgcode, *sgabsinc, pwcs, pfxout, pfyout, pfcout, *speed, *spindle, pgear, [if gcode$, *feed], strcantext, e$ if use_rot_lock & cuttype = zero, prot_lock pbld, n$, sg43, *tlngno$, pfzout, pstagetool, e$ pbld, n$, pscool,e$ absinc$ = sav_absinc pbld, n$, sgabsinc, e$ pcom_movea toolchng = zero c_msng$ #Single tool subprogram call !xnci$, !ynci$, !znci$ This is down further in the post... pstagetool #Pre-stage tools if stagetool = 1, [ if ttblend$, #Check for last toolchange [ if stagetltype = 1, *next_tool$ #stage first tool at last toolchange ] else, *next_tool$ #stage tool at every toolchange ] If you can help, let me know where to start looking to get this feature going. Remember I am a C code dummy so you'll have to use layman's terms. Thanks. Dan

ha, it did drop in, I tried that but apparently I need to drag it into the center. I moved it around but didn't notice the flicker when I had it in the center. Thanks, much appreciated Dan

Same as usual, I managed to hit some sort of shortcut and deleted my levels manager from the box on the left with "toolpaths", "Solids", "Planes"... I found out ALT-Z opened the level manager, but how do I get it back with the other in that box? Thanks again as you all are a great benefit to my career. Dan

Thanks, all good now.

So I hit something that re-organized the planes but I like it where all the default planes are on top, then my added planes are all below the standard planes. Anyone know how to set it back? I haven't figured it out yet. Thanks. Dan

Thanks for those other options. They may come in handy some day too.

So, I do File, Merge. it asks "Scale current part to metric?" which I say NO because I want to leave the current part in English. Then it switches Mcam to metric. I then switch back to English and it asks "Scale current part to English?" I just tried all combinations... I got it to work correctly by choosing Yes for the first and No for the second. I can't say I understand it but I only had 4 possible combinations so that one happened to work. Both the original model stayed in English and the new metric one is correct in English. Thanks for taking time out of your day to help me out. Dan

I have a part already toolpathed in English. We have a similar part to make and when I try to merge it into the old part, I cannot get it to come in without changing my current program to metric ( which will take forever to regenerate ) What is the easiest way to bring this in without changing the current program to metric? As usual, thanks for your help. Dan

File is a .mcam but it might have been a 2017 file. I re-did the operation with the points and chains and It worked fine. Was just scratching my head, thanks for the help. Dan

So, I am taking a similar program and converting it over to a new part ( same holes and taps, just different locations ) and I get to this pocket program. In the geometry, I have 4 chains for the two pockets. I have "Chain Point 1 " , " Chain 2", "Chain Point 3" and " Chain 4". I can only assume the Chain Point 1 and 3 are the two points set for the entry. Problem I am having is setting the points again. I can re-chain the geometry but cannot seem to find where I reset the entry points. I even tried to do a new pocket toolpath thinking it might prompt me after choosing "Center on Entry Point" but I get nothing. Using Mcam 2018 As always, I greatly appreciate you help.

Yep, worked like it used to. Thanks for pointing me in the right direction everyone. I was using X4 but now using 2018. Quite a bit of difference between the two.

Great. It was so simple before, was hoping it was still that way. Thanks.

So I'm roughing out a large pocket, Highspeed toolpath with small stepover and deep cut. I want to rough 1.9" deep then, because I have 2" flute length, make another operation to cut to the remaining 3.8" deep. Figured I'd copy the operations and on the first, I'd draw a surface at 1.9 and add it to the geometry so that op would only go 1.9 deep. Then adding more to the wall and floor stock for the remaining depth to keep from rubbing the shank. Problem is, how do I start this operation 1.9" deep? I'm used to the older Mcam where I can set min and max cut depth so I can control when the pocketing starts and stops both the top and bottom. Any help again is greatly appreciated. . Dan