Hmm, okay so the tool changes are basically replaced with a work offset change and a y0 (or x0 as I plan) move to get the tool on center. Any chance I would be able to use tool comp on the control (running in lathe mode) to work? I could always do tool comp at post, but it would save a lot of back and forth being able to do it on the control. The newer Tormach PathPilot is Linux CNC (EMC) based, and the other option I was looking at would also be Linux CNC. My SB lathe is not CNC sadly. It is the "Fourteen" model in very nice condition. At some point I may do a CNC conversion on it, but in all reality, I wouldn't use it to it's fullest capacity. It is a much larger machine than I really need as it is.

Whatever mill I get, rigid tapping is a requirement. I figured the work offsets could be used for tools, but not having done it I have no idea what it would look like. Do you have a simple g-code program you could post as an example? Not having ever programmed for a Swiss machine, I have no idea how tools are handled.

So I've been away for a while.... I did the school thing and now i'm all edjumucated and spend the past 6 years working in the real world as a controls engineer. I'm contemplating the purchase of a small CNC mill like the Tormach offerings or something similar. I have a 14" South Bend lathe for turning, but I find the need to be able to make small parts that are more complicated than I have the patience to make manually. Since I am planning to get a reasonably sided CNC mill I would like to be able to do some CNC turning on it. I know there are videos of it being done and I know it is possible, but I do not want to screw around manually editing G-code to do it. I realize it isn't optimal, but it would only be for non-ferrous metals and short parts. Is there a way I can create a valid machine definition and matching post to use the milling spindle as a lathe spindle? I would mount tools in a gang fixture on the table and likely have 5-10 tools set up. My preference would be to be able to call tools and have it move the x axis and y offset to the correct position, similar to how a Swiss type machine would. I haven't looked at the mpmaster posts in forever, but that was my next step.

Just to add my .02 Pocket Facing is what I normally use. Like Jay shows above, it works very well and its efficient. No trimming or extra geometry required....

RE: Ostop It seems to work fine but when i turn on the Ostop on the control the coolant does not come back on. Also, is there a way in mastercam to tell the machine to go home on an M01 instead of just sitting over the part?

Greg: The post was set up to use G116 by default but I definitely find it more convenient. Also, the is optional block delete. I am using this to toggle on off the first two operations. It is an outer contour and a facing operation that only needs to be done once. I am running the same program for a 6 sided part so all i have to do is run the program once, then flip the part and turn on block delete. Superman: The G41 is called, D(X) and then at the bottom of the program it cancels with G40(not shown). Looks good to me.... quote: If using cut-comp in the "Control", the lead in/out lines must be bigger than the tool radius, arcs also. Will mastercam warn you if you dont have large enough arcs/lines? Colin: I Have Ostop set for on before. I need to look at the post and play around with mastercam a bit more posting simple operations to see what each setting does.

I got it now I think. I did a few searches after pinpointing the error and realized that a linear move is all I need. Lead in/out is not necessary for this path but this is good to know for future reference. I prefer to use Ramp instead of depth cuts.... I guess it makes me feel better about choosing to do something CNC instead of manually. Off topc but deffinately due to being new to mastercam x.... I use canned text to put an M01 before each operation.... it puts it before EVERY pass on depth cuts. While this is good for proving out a program, it sucks if i just wnat to use an M01 to stop for clamp swaps and such. Any ideas?

The first operation is a Ramp Contour. It will run around a 1.5" square part at .05 depth until 1.51" with a .01" finish cut. G41 is not turned on anywhere else in the program. I managed to get comp to post on the first move and it gives me the "cutter comp applied on arc move" error message. I had it set to us entry/exit but it was not necessary. After turning it off it posted without error and i got the following. It seems that ive answered my own question here??? code: (OVERALL MAX - Z1.) (OVERALL MIN - Z-1.51) N10 G00 G17 G20 G40 G80 G90 N12 G30 P1 / N14 M01 / N16 S7334 M03 / N18 G116 T4 ( 1/2 FLAT ENDMILL) N20 (MAX - Z.25) N22 (MIN - Z-1.51) / N24 G15 H1 / N26 G00 G17 G90 X-.26 Y-1.5 S7334 M03 / N28 G56 H4 Z.25 T1 / N30 Z.1 / N32 G94 G01 Z0. F6.42 / N34 G41 D4 Y0. Z-.0196 F58.67 / N36 X-.2592 Y.0199 Z-.0199 / N38 X-.257 Y.0397 Z-.0202 / N40 X-.2532 Y.0592 Z-.0204

Well i understand that... but now I'm trying to figure out why its not there I think I may be onto something here... Browsing through the mpmaster post I found this in the user-defined variables : code: comp_type : 0 #Cutter compensation type - 0=computer, 1=control, 2=wear, 3=reverse wear, 4=off Now my question is.. do i have to set this manually the toolpath parameters do this automatically?

Ok, so I'm finally getting the hang of mastercam and the mpokuma post. Ive gotten everything i need to work except for in-machine tool comp. I have changed the tool comp options in mastercam from "computer" to "wear" with no change in the posted code. Changing the D offset on the machine has no effect on the part dimensions. The code and below is a snippet of what is produced when posting. (no tool comp, block delete on) Your insight is very much appreciated. code: $CUBE.MIN% (MASTERCAM - X) (MCX FILE - G:MY DOCUMENTSCUBE.MCX) (POST - MPMASTER_OKUMA) (MATERIAL - ALUMINUM INCH - 2024) (PROGRAM - CUBE.MIN) (DATE - JUN-18-2009) (TIME - 9:31 PM) (POST DEV - IN-HOUSE SOLUTIONS) (T4 - 1/2 FLAT ENDMILL - H4 - D4 - D0.5000") (T1 - 1/4 FLAT ENDMILL - H1 - D1 - D0.2500") (T3 - 1/4 BALL ENDMILL - H3 - D3 - D0.2500" - R0.1250") (T2 - 1/8 BALL ENDMILL - H2 - D2 - D0.1250" - R0.0625") (OVERALL MAX - Z1.) (OVERALL MIN - Z-1.51) N10 G00 G17 G20 G40 G80 G90 N12 G30 P1 / N14 M01 / N16 S7334 M03 / N18 G116 T4 ( 1/2 FLAT ENDMILL) N20 (MAX - Z.25) N22 (MIN - Z-1.51) / N24 G15 H1 / N26 G00 G17 G90 X-.3912 Y-1.3417 S7334 M03 / N28 G56 H4 Z.25 T1 / N30 Z.1 / N32 G94 G01 Z0. F6.42 / N34 G03 X-.26 Y-.75 I-1.2688 J.5917 F58.67 / N36 G01 Y0. Z-.0098 / N38 X-.2592 Y.0199 Z-.0101 / N40 X-.257 Y.0397 Z-.0103 / N42 X-.2532 Y.0592 Z-.0106 / N44 X-.2479 Y.0784 Z-.0109 / N46 X-.2412 Y.0972 Z-.0111 / N48 X-.233 Y.1154 Z-.0114 / N50 X-.2235 Y.1329 Z-.0117

Ah... i understand. I did not know i needed to turn it off after I was done with it. Worked like a charm. Thank you once again Colin.

Thanks guys, i just ran a program today with the edited post, everything works perfectly. Now i just need to figure out how to use the canned text and make that work properly. I want to turn on Block Delete for only two operations but when i turn it on it puts optional block delete on for the entire program. Is there any way to do this without using subprograms?

Thanks Colin, this morning i took a look at the post again and realized that i had misread the description in that thread. I read the "was XXXX" to be the change to be made not the other way around. I changed the parameters and everything works perfectly. Thank you all for your help. If anyone needs a working post/machine def. for x2 or x3 for an okuma MA-400HA let me know....

No biggie I figured it was something simple that i missed. I was so used to 9 its hard adjusting. Still confused about the feedrate thing, ive googled a bunch and havent turned up any more info. Oh, and Colin, I know a couple of people that just started at Boeing within the past couple of weeks. Not sure what dept. they are with though. [ 06-11-2009, 10:15 PM: Message edited by: Brian L. ]

GREAT!!! Got it guys, turns out i'm just noobish when it comes to programming. Setting the offset numbers in the tool files fixed it immediately. Unfortunately, after modifying the post according to the stick recommended by gcode, it still outputs F99999. Here is the most recent output, not that it tells you much... code: (MCX FILE - C:USERSBRIANDOWNLOADSBRACKETS PAIR.MCX) (POST - MPMASTER_OKUMA) (MATERIAL - ALUMINUM INCH - 2024) (PROGRAM - BRACKETS PAIR.MIN) (DATE - JUN-11-2009) (TIME - 9:19 PM) (POST DEV - IN-HOUSE SOLUTIONS) (T3 - 1/2 FLAT ENDMILL - H3 - D3 - D0.5000") (T1 - 1.22" KEYSEAT CUTTER - H1 - D1 - D1.2200") (T2 - 1/4 CENTERDRILL - H2 - D2 - D0.2500") (T6 - 25/64 DRILL - H6 - D6 - D0.3906") (T5 - 1/4 FLAT ENDMILL - H5 - D5 - D0.2500") (T4 - 1/4 BALL ENDMILL - H4 - D4 - D0.2500" - R0.1250") (OVERALL MAX - Z3.2) (OVERALL MIN - Z.2) N100 G00 G17 G20 G40 G80 G90 N110 G30 P1 N120 G116 T3 ( 1/2 FLAT ENDMILL) N130 (MAX - Z2.537) N140 (MIN - Z.7) N150 G15 H2 N160 G00 G17 G90 B0. X-1.9999 Y-3.7501 S12224 M03 N170 G56 H3 Z2.537 T1 N180 Z2.037 N190 G94 G01 Z1.8462 F999999. N200 Y-1.9999 N210 Y-1.7095 N220 G02 X-1.8463 Y-1.5559 I.1536 J0. N230 X-1.6928 Y-1.7095 I0. J-.1536 [ 06-11-2009, 09:20 PM: Message edited by: Brian L. ]