Tony I had this happen during the beta and sent it in, the only way I was able to get rid of the "extra" coolant options was to regen.

Verisurf hole axis is free and works great

Declared these variables.... code: slowdrill_speed : 0 # Single Gundrill - Slow PRM for Gundrill Cycle slowdrill_feed : 0 # Single Gundrill - Slow feed for Gundgrill Cycle start_height : 0 # Single Gundrill - Z Start Position first_depth : 0 # Single Gundrill - Z depth for gundrill at slow speed/feed fastdrill_speed : 0 # Single Gundrill - Fast / Recommended RPM for Gundrill retract_feed : 0 # Single Gundrill - retract feedrate drill_speed : 0 # Gundrill Cycle - Drill RPM start_hgt : 0 # Gundrill Cycle - Z start height drill_feed : 0 # Gundrill Cycle - Drill Feedrate Build this postblock..... code: pgundrill #DLB--------Canned Gundrill Cycle Added 7-31-08 pdrlcommonb # works in conjunction with pmisc2$ and pmisc2_2$ pbld, *pdrlxy, e$ pbld, *start_height, e$ pbld, *slowdrill_speed, "M4", e$ pbld, *sg01, *first_depth, *slowdrill_feed, e$ pbld, n$, "G4", *dwell$, e$ pbld, *fastdrill_speed, "M3", e$ pbld, n$, "G4", *dwell$, e$ pcan1, pbld, *sg01, *pfzout, *feed, *strcantext, e$ pbld, n$, "G4", *dwell$, e$ pbld, *slowdrill_speed, "M3", e$ pbld, *sg01, *start_height, *retract_feed, e$ pbld, *sg00, *initht_a, e$ pcom_movea Modify these postblocks.... code: pmisc2$ #Canned Misc #2 Cycle #DLB--------Canned Gundrill Cycle Added 7-31-08 pgundrill code: pmisc2_2$ #Canned Misc #2 Cycle pgundrill #DLB--------Canned Gundrill Cycle Added 7-31-08 The variable names can be changed to suite, this should get ya started NOTE: This was built to gundrill with a pilot hole, the first Z depth is done with the spindle turning BACKWARDS, but its easy to change.

Yea it is. Its been covered prety well, do a search for custom drill cycles and I will look for the post where I did something similiar.

I set up a custom drill cycle for gundrilling and it's very similiar to what your trying to do.

I have used Active Editor Pro, which has all the OMV stuff plus more and it is really good stuff but a year after we bought it I heard a rumor that UG had bought it and Renishaw would not be developing it any further. Check out this thread THREAD I would be very cautious cause they ain't gonna tell you if they don't plan on developing it further. Renishaw makes great products, but they also want to empty the shelves of old products, they tried very hard last year to convince me that the MP700 was not going to be replaced by another model, I got the first two RMP600 probes put on the market instead and less the 2 months later the MP700 was removed from the website

No problem, it should be fine as I'm using X3 and the latest mpmaster also.

Ah thats an easy one, even though it took me awhile to figure it out. Just remark out the comment$ line in the pheader$ section and it will put it after the inital startup "safty" lines. code: pheader$ #Call before start of file hour = int(time$) min = int((time$ - hour)* 100) if hour > 12, hour = hour - 12 if hour = 0, hour = 12 year$ = year$ + 2000 "%", e$ spaces$=0 *progno$, " ", scomm_str, sprogname$, scomm_end, e$ spathnc$ = ucase(spathnc$) smcname$ = ucase(smcname$) #comment$ # File descriptor <------THIS MOVES FIRST MANUAL ENTRY BELOW SAFTY CODE spaces$=0 #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$ 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$ scomm_str, "PROGRAM - ", sprogname$, sextnc$, scomm_end, e$ scomm_str, "DATE - ", *smonth, "-", *day$, "-", *year$, scomm_end, e$ # MON-DD-YYYY #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 #scomm_str, "TIME - ", time$, scomm_end, e$ # 24 hour scomm_str, "POST DEV - ", *slicense, scomm_end, e$ spaces$=sav_spc

What version are you using and which post?

SECO R216.19-01.00-3L This is a 1.0" Dia. insert mill for doing slots.

Jarrett is correct. Only mazacam or griffo brothers can convert it. I have mazacam and have done a few conversions for friends and it is glitchy, definatly not something you just convert and run. going over it really well to ensure everything is fine is mandatory.

I've been doing just that for over two years without a single problem, it makes it super easy to bring work home and then take it back to the office in the morning keeping everything up to date.

make sure all operations have the same .nc file name

Chris, I use SyncToy & a USB thumb drive to sync my mcamx folders for X2, X3 between 3 different PCs without any problems, BUT since I'm the only user of all 3 systems there is no chance of having the same file open in 2 or more systems at the same time. This lets me keep my work PC, my laptop & home PC all perfectly synced.

I agree with James on this, get it no matter what. Sure you can manipulate a solid around in a CAD package and then import it, but what if that solid is part of an assembly and you go jacking around with the orientation, then the assembly is hosed. Yes I know you could make a copy of the solid but that breaks the associativity making change recoginition more tedious. I would rather leave my model as designed and manipulate ONLY IF I HAVE TO in MC, it's easy and getting easier

Look for the ptlchg_com section in your post....the comment$ controls the operation comment. code: ptlchg_com #Tool change common blocks if force_output | sof, [ result = force(ipr_type,ipr_type) result = force(absinc$,absinc$) result = force(plane$,plane$) ] pcom_moveb pcheckaxis #Check for valid rotary axis c_mmlt$ #Multiple tool subprogram call #ptoolcomment if sof & scomm_sav <> snull, [ spaces$ = 0 n$, pspc, scomm_str, *scomm_sav, scomm_end, e$ spaces$ = sav_spc ] if sof = 0, scomm_sav = snull comment$ <--------MOVE THIS pcomment3 pmisccheck pcan if stagetool >= zero, [ if omitseq$ = 1 & tseqno > 0, [ if tseqno = 2, n$ = t$ pbld, *n$, *t$, "M06", ptoolcomm, e$ pbld, n$, next_tool$, e$ ] else, pbld, n$, *t$, "M06", ptoolcomm, e$ pbld, n$, next_tool$, e$ ] code: ptlchg_com #Tool change common blocks if force_output | sof, [ result = force(ipr_type,ipr_type) result = force(absinc$,absinc$) result = force(plane$,plane$) ] pcom_moveb pcheckaxis #Check for valid rotary axis c_mmlt$ #Multiple tool subprogram call #ptoolcomment if sof & scomm_sav <> snull, [ spaces$ = 0 n$, pspc, scomm_str, *scomm_sav, scomm_end, e$ spaces$ = sav_spc ] if sof = 0, scomm_sav = snull pcomment3 pmisccheck pcan if stagetool >= zero, [ if omitseq$ = 1 & tseqno > 0, [ if tseqno = 2, n$ = t$ pbld, *n$, *t$, "M06", ptoolcomm, e$ comment$ <------TO HERE pbld, n$, next_tool$, e$ ] else, pbld, n$, *t$, "M06", ptoolcomm, e$ comment$ <------AND TO HERE pbld, n$, next_tool$, e$ ]

John, do a search for aggregate head, ther is some good info you should read. Your post isn't set up to do this, your going to need to call Todd or Alex to see if they can set you up with an aggreate post or better yet modify your current one.

If it's a 31 series control, I think it's parameter 5200 bit 5, 1 sets it to NOT use high-speed peck tapping which will give you the full retract.

Well then definatly get the FX-3700, it will serve you very well.

That depends on the type of programming you do, is it alot of 3D stuff or mainly 2D?

this type of clamp works very well for clamping inside diameters.

I didn't realize the ascii "inside" the quotes wouldn't work, thats meh learnin fer da day

In the ptlchg_com & ptlchg0$ post block replace *tlngno$ with "H#5199"

quote: Will MC be the first to venture into the Multi-Core CAD/CAM World? No, they are not the first.

This is the contents of an e-mail I recieved I thought those who don't get the e-mails might like to see: In case you are curious about what will be in Mastercam X4, here is a quick overview of just some of the new X4 functionality currently scheduled for release in the second Quarter 2009. Mill • Dynamic Mill is a new toolpath capable of utilizing the entire flute length of your cutting tools for increased tool life and efficiency • 2D toolpaths have been migrated to the new tree structure style • Multi-threading support for high speed and multiaxis toolpaths • Refine Toolpath features in surface machining for greater control and surface finish improvements Lathe • New multi-groove selection • Separate feeds and speeds for rough and finish grooving • Auto tool inspection to check tools for wear Wire • Custom support for Agie EDM with Agievision controls Router • Automatic nesting now with the ability to edit nested sheets using drag and drop • Vertical and/or horizontal cut-off operations now automatically generated in toolpath nesting Watch for more information on other Mastercam X4 features in upcoming Mastercam Newsflash issues!