Does MasterCAM not do this already? Check your "compensation type in the contour parameters, make sure it is set for wear or control

SSD's should not be used to hold data that is critical. It doesn't make much sense to RAID two drives that you may loose at any time. That is part of the reason that you don't see very large SSD drives, they are generally made to load an operating system and a software, It is still recomended to have a tradidtional disk drive to store and backup to. The SSD will give the OS the speed that you need and the disk drives give the reliability for storage.

I took a look at the file and made some changes in the geo. and changed the toolpath from pocket to open pocket. I don't normally machine wood but the usual best practice to machine steel is to avoid plunging into the material when ever possible, open pocket option allows for that. OVERLAP POCKETS.MCX-6

Hello Tom, the MPFAN post is somewhat of a tough post to work with, it may be easier to edit the MPMaster post that you can download from the emastercam website. The post is longer but all aspects of the post are there which makes it easier to edit.

Sounds like you need a macro that you can copy and paste into the final Mastercam post.

Chris, I have been following this thread because i'm interseted, just wondering if I missed something. The logic that you have put into the fixed cycle now checks for chip break and peck drill cycle... if drillcyc$ = 1 | drillcyc$ = 2 won't that mean if drillcyc$ = 0 in other words drill/ counterbore that it will bypass the logic to do the S5000 m04? which is what Rotary Ninja wanted.

You can also play with these values, they remove some of the spaces around the hyphens. I usually # out the originals and change them below to keep an original of the format and show my changes. ### if tcr$>0, scomm_str, *t$, ptspace, " - ", plistcomm, " - ", *tlngno$, phspace, " - ", *tloffno$, pdspace, " - ", *tldia$, punit, pdiamspc, " - ", *tcr$, punit, scomm_end, e$ ###turned off original ### if tcr$=0, scomm_str, *t$, ptspace, " - ", plistcomm, " - ", *tlngno$, phspace, " - ", *tloffno$, pdspace, " - ", *tldia$, punit, pdiamspc, scomm_end, e$ ###turned off original if tcr$>0, scomm_str, *t$, "-", plistcomm, "-", *tlngno$, "-", *tloffno$, pdspace, "-", *tldia$, punit, pdiamspc, "-", *tcr$, punit, scomm_end, e$ ###removed all spaces from - if tcr$=0, scomm_str, *t$, "-", plistcomm, "-", *tlngno$, "-", *tloffno$, pdspace, "-", *tldia$, punit, pdiamspc, scomm_end, e$ ###removed all spaces from -

removing spaces from tool coments can be a bit tricky because of the number of characters changes and the post likes to line everything up but if you can find this area in your post you can "play" with the values and it may help again I use 3# symbols to mark any of my changes. Try changing one value at a time to make sure you end up with the format you want. good luck ptoolcomm # Comments from tool library spaces$ = 0 strtool$=ucase(strtool$) if strtool$<>snull, pspc1, scomm_str, *strtool$, scomm_end else, pspc1, scomm_str, "DEFINE TOOL NAMES", scomm_end spaces$ = sav_spc plistcomm # Comments from tool library strtool$=ucase(strtool$) if strtool$=snull, strtool$ = snocomm *strtool$ nstrlen = strlen(strtool$) counter = 0 ###CHANGED from 1 while counter <= (17-nstrlen), pspace ###changed from 20 to give less spaces after tool comment pmetacomm # Comments from tool library strtool$=ucase(strtool$) if strtool$<>snull, *strtool$ else, "DEFINE TOOL NAMES" pspace # Creates spaces based on tool comment length " " counter = counter + 1 ptspace # Creates spaces based on tool number if t$ < 0, " " ###changed from 10 if t$ >= 10 & t$ < 100, " " phspace # Creates spaces based on length offset number if tlngno$ < 0, " " ###changed from 10 if tlngno$ >= 10 & tlngno$ < 100, " " pdspace # Creates spaces based on diameter offset number if tloffno$ < 0, " " ###changed from 10 if tloffno$ >= 10 & tloffno$ < 100, " " pdiamspc # Creates spaces based on diameter offset number #if tldia$ < 0, " " ###changed from 10 pspc # Creates spaces based tool level setting if sav_spc = one & omitseq$ = no$, " " pspc1 # Creates spaces based tool level setting if sav_spc = one, " " popnote # Operation note for tool table if opcode$ = 3 | opcode$ = 16, *sdrnote else, [ if opcode$ = 13 & hst_flg, *sopnotehst else, *sopnote hst_flg = 0 ]

this section of the post controls what gets posted. I have changed some myself, these are the notes I have made for my own records you can use them to help guide you through as well. I have a habit of putting 3pound signs to indicate my edits ### "%", e$ ###turns off percent sign at top of program ### " ", e$ ### added line space spaces$=0 ### *progno$, " ", scomm_str, sprogname$, scomm_end, e$ *progno$, scomm_str, sprogname$, scomm_end, e$ ###removed " " between prog. # and comment " ", e$ ### added line space spathnc$ = ucase(spathnc$) smcname$ = ucase(smcname$) comment$ # File descriptor spaces$=0 " ", e$ ### added line space between manual comment and header #scomm_str, "PROGRAM NAME - ", sprogname, scomm_end, e #scomm_str, "DATE=DD-MM-YY - ", date, " TIME=HH:MM - ", time, scomm_end, e #scomm_str, "MASTERCAM - V", *vers_no$, scomm_end, e$ # scomm_str, "MASTERCAM - X", scomm_end, e$ ### scomm_str, "MCX FILE - ", smcpath$, smcname$, smcext$, scomm_end, e$ ###turned off MCX comment if spostname_sav = snull, spostname_sav = spostname # scomm_str, "POST - ", snamepst$, scomm_end, e$ #scomm_str, "MP - V", *dll_vers$, scomm_end, e$ stck_matl$ = ucase(stck_matl$) scomm_str, "MATERIAL:", stck_matl$, scomm_end, e$ ###turned on MATERIAL ### scomm_str, "PROGRAM - ", sprogname$, sextnc$, scomm_end, e$ ###turned off PROGRAM comment scomm_str, "DATE:", *smonth, "/", *day$, "/", *year$, scomm_end, e$ # MON-DD-YYYY ###changed spacing and added : #scomm_str, "DATE - ", *year$, "/", *month$, "/", *day$, scomm_end, e$ # YYYY/MN/DD #scomm_str, "DATE - ", *day$, "/", *month$, "/", *year$, scomm_end, e$ # DD/MN/YYYY #scomm_str, "DATE - ", date$, scomm_end, e$ # DD-MM-YR scomm_str, "TIME:", *hour, ":", *min, [if time$ < 12, " AM"], [if time$ >= 12, " PM"], scomm_end, e$ # 12 hour ###changed format #scomm_str, "TIME - ", time$, scomm_end, e$ # 24 hour #scomm_str, "POST DEVELOPED BY:", *slicense, scomm_end, e$

If your Post won't convert properly you may be able to rewrite it using an MPMaster post for X5 and editing it using your old post as a guide.

Hello Darin, in the coolant settings you should have 3 options after you turn the coolant on; before, with, and after. try using the "with" option...it will move the M08 down. your other choice is to edit the Post to give you a different location of the M08. I prefer to have the coolant start on block N200 on its way down to Z3.0 (in this case) but I have seen it in the location you have indicated because it takes time to get coolant to the nozzle. Good luck

I had to do the same thing for my OKUMA post, on about line 971 you will find a line that looks like this fmt "G" 4 g_wcs #WCS G address change it to read: fmt "G15 H" 4 g_wcs #WCS G address you may have to change the 4 to 5 to allow for more integers also if you are using more than 1 work offsets in the program you may need to change a line somewhere around line 2280, it looks like this g_wcs = workofs$ + 54 change the 54 to 1 so it will give H2, H3... for the other work offsets. This should work but I have never needed more than one work offset in the programs I have made for this machine. when you change a post make sure that you document ALL changes so you have somthing to fall back on in case of errors in the post. Good luck Richard