Very nice Greg. Thanks! Mike

Go to the Machine Group Properties and select the Tool Setting tab. It could be possible that you have "Use tools step, peck, coolant" selected and you have the coolant off on the tool. You can leave this selected and select the appropriate coolant on your tool and you should be good to go. If you are still having an issue, post the code out with a supplied post and then check Thanks

Sounds good. X+ works very well when you get used to it. Thanks

What he said Thanks Matt

Dave, IE: Lets say that you did not require "shldr length". Go up to the bar and grab the column line and drag it to the left so that the column is reduced in size to zero. Got it? Mike

You can use a Demo version. It's free. Thanks

Dave, To get rid of columns in the tool list, go to the top of the page and drag the unneeded column over until it's gone. It will not display or print. It also saves to registry so it will remember it next time you make a tool list. Mike

Mike, I would try this place. They have plug and bottom listed at $20.97. Look A-1 Supply

Hello Mick, I can't sleep tonight so I just checked out your file. Here are a few things I see: -The backplot seem fine to me. -If I measure a tool vector(saved as geometry)at roughly the smallest and largest B move, it appears to be about the same as the gcode. B51.427 to B75.009 -I posted the code two ways. The first way was with the TP origin set as supplied (as you had it) and the other way was with it set to zero. The code looks like it is considering the origin at post processing. gcode with origin as supplied: G00 G17 G90 G54 B51.427 X-107.646 Y-.004 S3000 M03 G43 H1 Z40.899 Z-54.101 G94 G01 X-102.789 Y-.003 Z-55.286 F300. X-102.808 Y2.919 Z-55.299 B51.428 F1000. X-102.859 Y5.882 Z-55.332 B51.431 gcode with origin set to zero: G00 G17 G90 G54 B51.427 X161.214 Y-.004 S3000 M03 G43 H1 Z824.055 Z729.055 G94 G01 X166.072 Y-.003 Z727.87 F300. X166.039 Y2.919 Z727.862 B51.428 F1000. X165.946 Y5.882 Z727.843 B51.431 X165.806 Y8.884 Z727.818 B51.436 X161.214 is about where it should be according to what I see. The WCS origin and TP origin should be set to the center of rotation from what I have seen in the past. I have never seen it work any other way. The software must know where center is in order to make the calcs. The backplot may have looked wrong in X3 due to the origin issue. Please let me know if you need any other help. I can run your code through Predator here if that's what it takes. My guess is that this will fix you up though. Mike

Mick, I will look at the file if you email it to me. edit: I only have X2MR2 Thanks

Mick, I just researched the post issue just in case that's the issue causing your problem. The "Generic Fanuc 4X Mill.pst" was missing an important line of code in the first X2 release. I believe it was fixed in X2 MR1. My guess is that mpmaster also needed the same line of code. The following below was copied from an old post I put up back then. The fix came from CNC for the "Generic Fanuc 4X Mill.pst" The additions are in bold. ------------------- # CNC 10/06/05 - Changed parameter read for min_speed, modified pspindle, pprep$ and pset_mach # - Modified pset_rot_label to use srot_y for horizontal machines # - Added call to pset_mach in pq$ to set rotaxtyp$ # CNC 11/18/05 - Added psynclath with call to pset_mach to set rotaxtyp$, removed call from pq$ # CNC 02/03/06 - Added logic for high-speed toolpath tool inspection (see prapidout & plinout) # CNC 06/26/06 - Initial post setup for Mastercam X2 # CNC 12/15/06 - Modified pset_mach for horizontal rotation when rotating about world Z axis. # # -------------------------------------------------------------------------- # Features: # -------------------------------------------------------------------------- # This post supports Generic Fanuc code for 3 and 4 axis milling. # It is designed to support the features of Mastercam X Mill. rd_mch_ent_no$ = syncaxis$ #Retrieve machine parameters based on current axis combination - read from .nci G950 line rd_md$ #Read machine definition parameters - calls pmachineinfo$ #We only need these set at toolchange (and start of file). No need to set them each time a user may call rd_md rot_on_x = rot_axis if not(vmc) & rot_on_x = 3, rot_on_x = 2 #If HMC and rotating about world Z axis (machine Y axis) rot_ccw_pos = rot_dir index = rot_index if rot_angle = zero, ctable = one #ctable zero will produce a divide by zero error, so force to one if zero in MD else, ctable = rot_angle if met_tool$ = 1, -------------------- Mike

Hello Mick, I have done several parts in X2MR2 that had quite a bit of 5ax cuts in 4ax format on HMC's. I have always set the TP to Front and used a standard mpmaster post. There was an issue in the mpfan based posts..maybe it was early X2 that would cause a serious issue. You can search for this if you want. I would suggest to just take a late model mpmaster post, set my TP to front and try it again. Thanks, Mike

I have seen this issue several times in X/X2 but I am thinking it was only in the advanced multiaxis. I think the work-around was to select the tool first, hit escape and then select the parameters. Mike

Hello, The easiest thing to do is to use the same stock view for every machine group. Just use System Top and it will work fine for you every time. Thanks

This is a very nice data as long as you don't mind spending a little money. If you do not want to spend money, just use google. http://www.cutdata.com/ Thanks, Mike

What toolpath?

Hello Bob, It depends on the toolpath you are using. You may be able to just filter it. If not, advanced multiaxis or axis substitution should/may do what you want. Thanks

I suppose the CNC software post that Mori is listing for the NT series is using the misc integer method. Is this correct? link to mori website Thanks in advance, Mike

One of the most important things you will need to do is study what type of high-speed/look-ahead software the machine has. I am not familiar with that particular machine but I know that some/all of the newer Matsuura's, as well as other brands, have the capability to adjust the accuracy/servo lag limits. Make a test program, start testing and document your results. You want to make sure that you loosen up the settings according to what you are doing. IOW, if you are roughing .030" away from finish, it's fine to have .005" inaccuracy. This will allow maximum material removal as well as a much smoother motion. I started working on some formulas for depth of cuts and feedrates but I have not been able to perfect them as I do not have a machine available. I wish I would have done it when I did. Here is the start of what I have done for Aluminum so far. The real issue is that everyone wants it different. The correct way, as RobbJack says is to run it till it blows, back off and document. This may give you some ideas. Abbreviations TDIA: Tool diameter OAL: Overall length / Stick out from holder OHR: Overhang ratio= OAL/TDI DOC: Depth of cut DIA: diameter CPT: Chip load per tooth (advance per tooth) Feedrate: CPT x no. of flutes x RPM 2 Flute standard length carbide end mills also stub length 30deg necked tools for roughing(Ford series 135) TDI/OHR x 1.8 = DOC CPT = .01% to .025% of TDIA (.013%-.02% is used most often according to holder length and tool length) 3 Flute standard length carbide end mills. (Also tools with large corner radius and ball mills) TDI/OHR x 1.5 = DOC CPT = .007% to .018% of TDIA (.01%-.014% is used most often according to holder length and tool length) Mike

I actually have not had my ops go dirty in X2MR2 SP1 (Mill seat). I had the "ops go dirty" issue in an older version which I think is irrelevant at this point. The only issue I was having in X2MR2 is the MD getting lost/corrupted. This mostly(98%)went away since(I believe) I do not use solid drive geometry anymore. I am wondering if there are some files left over or old files in Scotts machine that is causing this issue? Mike

Sounds like a real bummer. Maybe someone else will have other ideas. Thanks, Mike

Hello Scott, Are you using Solid Geometry to drive your toolpaths? If yes, you might try using surfaces for a while. It made a big difference for me. I didn't have time to fight it anymore. Mike

Hello Steve, Mill has a "user defined" option for the feed calcs. I am not sure about Lathe. The only issue is that you must start with it selected. It does seem to work well once you get used to it.

Hello AppsEng, Here is a very nice Video showing how to use the WCS and also includes the method tedly spoke of. http://eapprentice.net/samplevideos/vid42/vid42.htm Mike

If you are just doing 3ax milling then you should create/change a/the WCS(work coordinate system). There is some good help on it in the reference guide. If you are doing simultaneous milling or would like to use a work around(wcs is much better in the long term), then just move the part using the "Xform Translate 3D" function to move the model between views. You could also just use the "Xform rotate" function using the appropriate plane. If you have any other questions, please post again. Mike