code: ( DRILL AT 135 DEG ) N56 M91 N58 M93 N60 M95 N62 X0. N64 G98 G81 Z.9 R1.1 F10. N66 X-1. N68 G80 ( DRILL AT 225 DEG ) N70 M92 N72 M92 N74 M95 N76 X0. N78 G98 G81 Z.9 R1.1 F10. N80 X-1. N82 G80 ( DRILL AT 180 DEG ) N84 M81 N86 M88 N88 M80 N90 X0. N92 G98 G81 Z.9 R1.1 F10. N94 X-1. N96 G80 ( DRILL AT 270 DEG ) N98 M92 N100 M97 N102 M90 N104 X0. N106 G98 G81 Z.9 R1.1 F10. N108 X-1. N110 G80 N112 M5 N114 G91 G28 Z0. N116 G28 X0. Y0. N118 M90 N120 M01 I'll put the post on the FTP. Like I said it's just the generic fanuc. It's under the text_post_misc folder Called it Heavy_post.zip If you want, and it wouldn't get you in trouble you could send me the file (or upload it) you're working on and I'll run my test using it. There may be something I'm over looking.

quote: getting just an m81 when i want to got to 270????? Uh-oh, Let me look into that. Did you add that second section of post that I had forgot from My first post?

Not, a problem. I'll be honest w/ you. I've never seen a rotary that requires code like that. I just thought it would be fun to try and figure out how to do it. But I'm guessing yes, you will need code for each angle. ex. our rotary requires a G120 before each rotation. but almost all rotaries and indexers required something different. Do you by any chance have a manual for the indexer you are using. That may have a better definition of exactly what is required at each rotation. Then if there is more, or less required than what you currently have we can probably find the answer.

I just realised i didn't have it set up for any angle over 180 so I changed this code: pindex #Index output if index & rot_on_x, [ if cabs <> prvcabs, [ spaces = 0 if indx_out = 0, n, " ", sindx_mc, "0", e if indx_out >= 300, [ n, " ", sindx_mc, "3", e indx_out = indx_out-300 if indx_out = 0, n, " ", sindx_mc, "0", e ] if indx_out >= 200, [ n, " ", sindx_mc, "2", e indx_out = indx_out-200 if indx_out = 0, n, " ", sindx_mc, "0", e ] if indx_out >= 100, [ n, " ", sindx_mc, "1", e indx_out = indx_out-100 if indx_out = 0, n, " ", sindx_mc, "0", e ] in the post and was able to get this nc output code: ( DRILL AT 45 DEG ) N30 M84 N32 M85 N34 X0. N36 G98 G81 Z.9 R1.1 F10. N38 X-1. N40 G80 ( DRILL AT 315 DEG ) N42 M83 N44 M81 N46 M85 N48 X0. N50 G98 G81 Z.9 R1.1 F10. N52 X-1. N54 G80 ( DRILL AT 135 DEG ) N56 M91 N58 M93 N60 M95 N62 X0. N64 G98 G81 Z.9 R1.1 F10. N66 X-1. N68 G80 ( DRILL AT 225 DEG ) N70 M92 N72 M92 N74 M95 N76 X0. N78 G98 G81 Z.9 R1.1 F10. N80 X-1. N82 G80 N84 M5 N86 G91 G28 Z0. also just so you are aware I have the post setup to always be positive between 0 and 360 deg here code: pindxcalc #Index move calculations, direction is shortest #Check if in tolerance cdelta = frac(abs(csav)/ctable) if cdelta > ixtol & cdelta < 1-ixtol, result = mprint(sindxerror) cdelta = prvcabs - cabs #Phase shift delta 10 revolutions, check odd/even if frac(int((cdelta + 3600)/180)/two), indx_mc = one else, indx_mc = zero #Set range 0-360 indx_out = csav while indx_out < 0, indx_out = indx_out + 360 while indx_out >= 360, indx_out = indx_out - 360

I don't know about a post nci. But I did try a few thing on the MC9 generic fanuc post And I was able to get it to output this code: % O1000 (PROGRAM NAME - TEST ) (DATE=DD-MM-YY - 19-01-06 TIME=HH:MM - 21:37 ) N2 G20 N4 G0 G17 G40 G49 G80 G90 ( 1/4 CENTERDRILL TOOL - 1 DIA. OFF. - 1 LEN. - 1 DIA. - .25 ) ( DRILL AT 0 DEG ) N6 T1 M6 N8 G0 G90 G54 X0. Y0. S3667 M3 N10 G43 H1 Z2. N12 G98 G81 Z.9 R1.1 F7.33 N14 X-1. N16 G80 ( DRILL AT 90 DEG ) N18 M99 N20 M90 N22 X0. N24 G98 G81 Z.9 R1.1 F7.33 N26 X-1. N28 G80 ( DRILL AT 45 DEG ) N30 M84 N32 M85 N34 X0. N36 G98 G81 Z.9 R1.1 F7.33 N38 X-1. N40 G80 ( DRILL AT 135 DEG ) N42 M91 N44 M93 N46 M95 N48 X0. N50 G98 G81 Z.9 R1.1 F7.33 N52 X-1. N54 G80 N56 M5 N58 G91 G28 Z0. N60 G28 X0. Y0. N62 M80 N64 M01 ( 1/8 FLAT ENDMILL TOOL - 2 DIA. OFF. - 2 LEN. - 2 DIA. - .125 ) ( MILL AT 0 DEG ) N66 T2 M6 N68 G0 G90 G54 X-.2625 Y-.025 S5000 M3 N70 G43 H2 Z2. N72 Z1.1 N74 G1 Z1. F50. N76 G41 D2 X-.2125 F9.6 N78 G3 X-.1875 Y0. R.025 N80 G2 X.1875 R.1875 N82 X-.1875 R.1875 N84 G3 X-.2125 Y.025 R.025 N86 G1 G40 X-.2625 N88 G0 Z2. N90 X-1.2625 Y-.025 N92 Z1.1 N94 G1 Z1. F50. N96 G41 D2 X-1.2125 F9.6 N98 G3 X-1.1875 Y0. R.025 N100 G2 X-.8125 R.1875 N102 X-1.1875 R.1875 N104 G3 X-1.2125 Y.025 R.025 N106 G1 G40 X-1.2625 N108 G0 Z2. ( MILL AT 135 DEG ) N110 M91 N112 M93 N114 M95 N116 X-.2625 Y-.025 N118 Z1.1 N120 G1 Z1. F50. N122 G41 D2 X-.2125 F9.6 N124 G3 X-.1875 Y0. R.025 N126 G2 X.1875 R.1875 N128 X-.1875 R.1875 N130 G3 X-.2125 Y.025 R.025 N132 G1 G40 X-.2625 N134 G0 Z2. N136 X-1.2625 Y-.025 N138 Z1.1 N140 G1 Z1. F50. N142 G41 D2 X-1.2125 F9.6 N144 G3 X-1.1875 Y0. R.025 N146 G2 X-.8125 R.1875 N148 X-1.1875 R.1875 N150 G3 X-1.2125 Y.025 R.025 N152 G1 G40 X-1.2625 N154 G0 Z2. N156 M5 N158 G91 G28 Z0. N160 G28 X0. Y0. N162 M80 N164 M30 % Here is what i changed in the post code: # Table rotation direction # Table rotation direction, index sindx_cw M8 #Rotate CW code sindx_ccw M9 #Rotate CCW code sindx_mc #Target for string fstrsel sindx_cw indx_mc sindx_mc code: pindex #Index output if index & rot_on_x, [ if cabs <> prvcabs, [ spaces = 0 if indx_out = 0, n, " ", sindx_mc, "0", e if indx_out >= 100, [ n, " ", sindx_mc, "1", e indx_out = indx_out-100 if indx_out = 0, n, " ", sindx_mc, "0", e ] if indx_out >= 90, [ if indx_out < 100, [ n, " ", sindx_mc, "9", e indx_out = indx_out-90 if indx_out = 0, n, " ", sindx_mc, "0", e ] ] if indx_out >= 80, [ if indx_out < 90, [ n, " ", sindx_mc, "8", e indx_out = indx_out-80 if indx_out = 0, n, " ", sindx_mc, "0", e ] ] if indx_out >= 70, [ if indx_out < 80, [ n, " ", sindx_mc, "7", e indx_out = indx_out-70 if indx_out = 0, n, " ", sindx_mc, "0", e ] ] if indx_out >= 60, [ if indx_out < 70, [ n, " ", sindx_mc, "6", e indx_out = indx_out-60 if indx_out = 0, n, " ", sindx_mc, "0", e ] ] if indx_out >= 50, [ if indx_out < 60, [ n, " ", sindx_mc, "5", e indx_out = indx_out-50 if indx_out = 0, n, " ", sindx_mc, "0", e ] ] if indx_out >= 40, [ if indx_out < 50, [ n, " ", sindx_mc, "4", e indx_out = indx_out-40 if indx_out = 0, n, " ", sindx_mc, "0", e ] ] if indx_out >= 30, [ if indx_out < 40, [ n, " ", sindx_mc, "3", e indx_out = indx_out-30 if indx_out = 0, n, " ", sindx_mc, "0", e ] ] if indx_out >= 20, [ if indx_out < 30, [ n, " ", sindx_mc, "2", e indx_out = indx_out-20 if indx_out = 0, n, " ", sindx_mc, "0", e ] ] if indx_out >= 10, [ if indx_out < 20, [ n, " ", sindx_mc, "1", e indx_out = indx_out-10 if indx_out = 0, n, " ", sindx_mc, "0", e ] ] if indx_out = 9, n, " ", sindx_mc, "9", e if indx_out = 8, n, " ", sindx_mc, "8", e if indx_out = 7, n, " ", sindx_mc, "7", e if indx_out = 6, n, " ", sindx_mc, "6", e if indx_out = 5, n, " ", sindx_mc, "5", e if indx_out = 4, n, " ", sindx_mc, "4", e if indx_out = 3, n, " ", sindx_mc, "3", e if indx_out = 2, n, " ", sindx_mc, "2", e if indx_out = 1, n, " ", sindx_mc, "1", e spaces = 1 ] ] Maybe someone else knows an easier way. But this is what worked for me in a couple test programs. However i was not able to get this to work in a program that I used transform rotate toolpath. Also, i only used whole numbers. I'm not sure how to go about doing it if you are rotating in less than 1 deg increments. HTH

Is this a post that was originally updated from 9 you could try to re-update your old mc9 post to see if it works right. You might just rename it as test or something and give it a try. that way it doesn't over right your current machine and control definition.

quote: right click in level menager and check contrast rows... Works fine in X but if you're still using ver 9 it'll stay all white. Even if you turn the contrast back on in x. But i can live w/ or w/out it. It is kinda neat though. I remember some people were saying it was causing them to experience vertigo.

Duh, I didn't think about that. I'll just stick to cimco til the fix is out. I've always liked that feature. Thanks, for the quick response.

Mick, You've got mail.

Sure Mick, I'll get it too you. Also this is from My program header. I have the post setup to output the travels... code: ( OVERALL MAX - X3.0808 Y23.7933 Z20. ) ( OVERALL MIN - X-10.6756 Y7.9467 Z3.75 ) ( TOTAL TRAVEL - X13.7564 Y15.8466 ) Notice how close they are to the cimco travels.

The XYZ extents in the mastercam editor are not accurate. Unless the minimum value is less than zero it shows up as zero. This throws off the total travel. Also the B travel is inaccurate too. Same file open in cimco. I realise this is minor, but I thought I'd mention it anyway because sometimes I have to rely on it to make sure my program will fit.

Don't forget for Johns code to work your post has to know code: ten : 10 #Define constant I think most generice post only went up to four.

Does it have to go all the way to Y HOME? If not just use a point toolpath w/ that tool using canned text to shut off spindle, coolant and put out the M00.

Question, Since I don't have an sld file to test this with is their any difference if you open the sld file w/ X, then save it back to ver 9 Verses just exporting it as an X_T file then bringing it into ver 9? Would it make any difference?

I forgot to mention. If it were me I'd have finished the floor w/ a 3/4 ball mill, Then have a project path around the inside w/ the 1/2 ball making 7 .015 mutli-passes to create the .25 rad. a 3/4 will give you a better finish that deep, not to mention your stepover wouldn't be as much. Just my 4 cents.

Well, i'm at work so I was able to open your file in a non-demo MCX. First suggestion, Don't finish the floor w/ the 3/4 bullmill .1875 rad, Too much step over to get a good finish, Second the 1/2 ballnose rough should be run before the finish floor op. Other wise you're cutting way too much air. Then use the 1/2 ball to finish everything since the fillet is a .260. You can use a diferent 1/2 for finish than for rough if you feel it neccesary. Also, if you can use some tolerance on your fillet to allow it to be .250 so your ballmill wont have to round up at the edges it might work better. Then you could stay off that walls about .01 and have a surface finish project path around the inside to have a smoother finish. Just my opinion.

Welcome to the forum...

Or you can highlight them and push "P" same as in V9

If I were a beta tester I would probably have to shoot myself.... Those guys go through a lot of trouble to try to get the rest of us good software. Logging all the bugs. Making sure they are bugs and not just their accidental screw up. Trying new patches. Finding new bugs caused by the patches...etc And then They have to listen to guys like you that have no idea what they're going through, xxxx and moan because something is a little different, or they missed a bug. Not to mention they do this for free. The only perk they get is seeing the next release alittle bit before you. And I know I was wasn't happy about the new interface at first. But the more I use it the more I like it and realize its not that bad. I also know that things will be alot better once MR1 is released thanks to them testing it out first. I thank them for what they do, but I could never do it. But if you think you can do better than them just let your reseller know and I'm sure he could get you set up with the people at 671 Old Post Road so you can be a beta tester too. Slepy teh I'm stepping down from my soapbox now.

The problem w/ the term Highspeed machining is that if you ask 10 different poeple their definition you're likely to get 10 different answers. Some people will tell you it means shallow cuts, I mean shallow like .050" deep But flying at 500 IPM and 20000 RPM w/ a .750 em. To me it just means maximum material removal as fast as possible. 1" deep 1/2" step over 15000 RPM 300 IPM. I'm probably wrong and someone else will have a better definition but that's mine. Anyway to go along w/ what John said you really don't want to use H.S.S. tools to acomplish this. You'll have to go all carbide or you will be having some major tool flex issues. For alum I would have to recommend 3 flute carbide for sure. There are alot of special made tools out there that will have some really high sfm recomendations, I usually start in the middle of what is advertised and work my way up if the machine is having no trouble. Odds are you will have tool salemen trying to push stuff on you. If they're good then they should have no problem giving you 1 or 2 to try out to see if the cutters are as good as they say. Not to mention they will probably be able to give you good feed and speeds to go w/ also. Good luck and Welcome to the forum

If you're using IE You have to uncheck the Use passive FTP under the advanced tab in internet options

quote: A software that can create a toolpath from a scanned image.How's that work? No programmer necessary? Crap we're going to be out of jobs.

linky There are still a few bugs left to work out. But it should be soon.

First post quote: Using mastercam 7.2 without any post support from reseller. at this time we need post for a mazak H630 with a Mazatrol 32 control. 2 days later... Second Post quote: Hey, I need a MaZAK POST. using mastercam 7.2 My third post prediction.. 2days after 2nd post quote: Since none of you were any help I'm going to kill myself if you don't give me a post.2days later quote: Headline: Marysville, Wa local idiot, Paul Soto, found unconcious. Attempted suicide by dropping 10 year old computer on self..More on page 2D

You would think someone that has been running the same software for all these years would know how to make their own post by now. What a j@ck0ff.