I am an idiot and sorry to waste anyone's time. After doing some testing, I have determined that I must create lead in/out paths to have one straight line in them. This gives the G41 a line move to start with. What I had before was a continuous arc from center of circle, to the outside cutpath. By just adjusting to 90*, it created a line move out, then into a nice lead in arc with G3. I am guessing this code will work much better. You guys have made my day!

WOW John, I don't know what to say at this point. Is there any settings to check in MCX that would force code like I posted above? Now I am really scratching, wondering where I am going wrong here. By the way John, did you get a chance to look at that Z+2.0" that is applied when using multi-offsets? I have been down and back in the post trying to to find that code.

WOW, that really makes me wonder why R code is even still in the picture. Answers seem unanimous.

John, I emailed you. Let me know if you get it. I am told that the older Haas we are running may be more forgiving than the newer controls so the code above that runs may still not work on a newer one because of the I J motion with the G41. Seems to come in fine for now but I also do not have any wear offset in my tables right now. Makes me wonder if these are all post issues or if there is a setting issue in MC. I have tried helix and contour paths. I was trying to use helix because it allows finish feed rate control at the bottom of the pass which contour does not have. It would sure be nice to have more adjustability in feed rates... Would be nice to say "hey, slow down for that corner up there" but maybe that is what look ahead is for....

I posted yesterday and we are still trying to figure this out so we can move on. We have one post we worked on some time ago and works fine but does not support subs. We have two other posts that support subs and look wonderful but when posting out any type of Helical path, and probably others for that matter, we end up with a G3 on the G41 line and the machine will not use it. I have tried just deleting the G3 on that line and it will just move to the next and error out. I am trying to determine if this is an MCX settings issue or a post issue. One post was specifically designed for a Haas but was given to us so no support for it. (this code does not work) N150 T03 M6 ( ) N160 N170 G0 G90 G54 X2.339 Y-1.3 S7500 M3 N180 G43 H03 Z1. N190 Z.6 N200 G17 G1 Z.5 F200. N210 G3 G41 D03 Z.32 R-.57 F90. N220 G3 Z.14 R-.57 N230 G3 X1.964 Y-1.8356 Z-.005 R-.57 N240 G3 X2.339 Y-1.3 R.57 N250 G3 X1.964 Y-1.8356 R-.57 N260 G3 X2.0363 Y-1.7494 R.1125 N270 G1 G40 X2.0364 Y-1.7485 N280 G0 Z1. (this code works great) N104 T3 M6 N106 G0 G90 G55 X2.339 Y-1.3 S7500 M3 N108 G43 H3 Z1. N110 Z.6 N112 G1 Z.5 F200. N114 G3 X1.199 Z.41 I-.57 J0. F50. N116 G41 D3 X2.339 Z.32 I.57 J0. N118 X1.199 Z.23 I-.57 J0. N120 X2.339 Z.14 I.57 J0. N122 X1.199 Z.05 I-.57 J0. N124 X1.964 Y-1.8356 Z-.005 I.57 J0. N126 X2.339 Y-1.3 R.57 N128 X1.199 R.57 N130 X1.964 Y-1.8356 R.57 N132 X2.0363 Y-1.7494 R.1125 N134 G1 G40 X2.0364 Y-1.7485 N136 G0 Z1. Both paths are identical. I am pretty sure each post will call up it's own machine definitions so thinking we have have something setup wrong but not sure.

We seem to be having issues getting R codes to work on a Haas VMC and keep getting 303 and 330 alarms. I think we can get I J to work but was curious if that is preferred or if there is any advantage of one or the other? I notice the R coding is shorter and I really like that because the machine we are working with is older and the process or is slow so we are trying about everything to get it to keep up. I figure, the less code, the better. Opinions?

Maybe a dumb question but how do you create a new puller for a lathe? there is nothing in the standard tool lists and see no easy way to add one. Do I need to create one in CAD and bring it in? I would be using a simple captive type that just pushes over the end of the bar.

OH, circle mill (helix) automatically puts a lead in and out on the path and starts at the center of the cut. I do not like how you cannot adjust much there but looked like a decent path for my application.

One of the posts we have tried is the mutli offset post available here. I have tried both circle mill and contour. I originally chose circle so I could easily change my feedrate at the bottom of the helix. There is not tool for this in contour. When I used contour, I put a very small lead out on. I have never had good luck with trying to ramp cut (helix) with contour and slow the feed at the bottom. Anyway, can someone recommend or show me what the corrected code should look like? Everyone has said just don't have the G3 on the G41 line but where do I put it?? I have also heard there are a few settings to adjust in MC that can help with this, is this true?

Oops. That second one is wrong. We are using subs for these. here is the correct code that is having the problem. The first string is correct. (SUB FOR T06 ) G98 G81 X2.519 Y-.725 Z.19 R.6 F40. Y-1.875 G80 ( counter bore pocket ) S7500 G0 Z1.1 X2.773 Y-1.875 G17 G1 Z.5 F200. G3 G41 D06 Z.4 R-.082 F90. G3 R-.082 G3 X2.7785 Y-1.8902 R.0236 G1 G40 X2.7861 Y-1.8992 G0 Z1. Z1.1 X2.773 Y-.725 G1 Z.5 F200. G3 G41 D06 Z.4 R-.082 F90. G3 R-.082 G3 X2.7785 Y-.7402 R.0236 G1 G40 X2.7861 Y-.7492 G0 Z1. ( PROFILE TRIM )

I will post two examples of code that does not work and I think only because the G41 and G3 land on the same line of code. However, We really need to know "where" to put it. There is not an X Y value above to put it on so not sure how to fix this. This code is being generated by the multi offset post from this site and one other post. Machine is a Haas VMC I would also like to know if there is any advantage to R code as opposed to I J? We have a serious lag issue on an older machine and I think it is having trouble keeping up so I would think the less data, the better but not sure on this one. Here is the example of what we are running now. This code runs the correct path but as soon as we enter a non-zero in the comp tables, the machine will error out. Indication is the G41 and G3 are on the same line. The "counterbore" is the area that will not execute (DEFINE TOOL NAMES - DRILL/CBORE) N100 G00 G90 X2.519 Y-.725 N110 Z1. N120 G98 G81 Z.19 R.6 F40. N130 Y-1.875 N140 G80 N150 (COUNTERBORE) N160 S7500 N170 G00 N180 X2.855 N190 Z.6 N200 G01 Z.5 F200. N210 G41 D6 G03 Y-1.793 I0. J.041 F90. N220 Y-1.957 Z.45 I0. J-.082 N230 Y-1.793 Z.4 I0. J.082 N240 Y-1.957 I0. J-.082 F63. N250 Y-1.793 I0. J.082 N260 G40 Y-1.875 I0. J-.041 N270 G00 Z1. N280 Y-.725 N290 Z.6 N300 G01 Z.5 F200. N310 G41 D6 G03 Y-.643 I0. J.041 F90. N320 Y-.807 Z.45 I0. J-.082 N330 Y-.643 Z.4 I0. J.082 N340 Y-.807 I0. J-.082 F63. N350 Y-.643 I0. J.082 N360 G40 Y-.725 I0. J-.041 N370 G00 Z1. N380 (PROFILE TRIM) Here is an example of the R code from another post and this will not run at all and will error out during the "counterbore" op. Tool will just start an arc and then error out. This one does not have the G41 on the G3 line but still will not run. N1270 ( Drill tool holes with EM ) N1280 T06 M6 ( ) N1290 M8 N1300 G0 G90 G54 X2.519 Y-.725 S3000 M3 N1310 G43 H06 Z1. N1320 G98 G81 X2.519 Y-.725 Z.19 R.6 F40. N1330 Y-1.875 N1340 G80 N1350 ( Counterbore ) N1360 S7500 N1370 G54 G0 X2.855 Y-1.834 N1380 Z.6 N1390 G17 G1 Z.5 F200. N1400 G41 D06 Y-1.875 F90. N1410 G3 Y-1.793 R.041 N1420 G3 Z.4 R-.082 N1430 G3 R-.082 F63. N1440 G3 G40 Y-1.875 R.041 N1450 G0 Z1. N1460 X2.855 Y-.684 N1470 Z.6 N1480 G1 Z.5 F200. N1490 G41 D06 Y-.725 F90. N1500 G3 Y-.643 R.041 N1510 G3 Z.4 R-.082 N1520 G3 R-.082 F63. N1530 G3 G40 Y-.725 R.041 N1540 G0 Z1. N1550 ( PROFILE TRIM ) Any help would be greatly appreciated. We are not sure if this is an MCX settings issue all the way or if this is a post issue. We are using X2MR2.

The Z 2.6 can go away all together. There are Z commands in the program. I am trying a multi offset post for the offsets so I am not using translate for this. However, there may be a setting I am missing that is causing this. Not sure. It is adding exactly 2" to every tool and op

We are horsing around with sub programming and cannot figure out why we are getting an extra 2" added to Z everytime it moves to another offset. Clearance is not turned on and should move at .6". I will post the example. ( Center drill ring ) N2 T02 M6 ( .25 DRILL ) M8 G0 G90 G57 X1.769 Y-1.3 S4000 M3 G43 H02 Z.6 M97 P200 G0 Z2.6 G56 X1.769 Y-1.3 Z.6 M97 P200 G0 Z2.6 G55 X1.769 Y-1.3 Z.6 M97 P200 G0 Z2.6 G54 X1.769 Y-1.3 Z.6 M97 P200 M9 G0 G28 G91 Z0 G90

Does inhouse have a post for my machine too?? Seems the old Hitachis are not as common as the NL Moris.

I am not sure what people are using but I know of one shop that is using Gibbs just because it is said to be better for lathe stuff. I would tend to agree though only that MC is lacking in several areas when comparing to their milling platforms. That being said, you really need a good mill "and" lathe CAM package to run a mill/turn well.

We have pretty much struck out finding a post for a sub spindle, Y axis, lathe. I am curious what is typically used to create a post or if this is all hand coding? Seems hand coding would surely be an exhaustive approach. A neighboring shop has X2MR2 so that is what we would build the post for. Thought about trying to merge a couple posts like a basic 2 axis/ live tool post, and a mill post but that may prove a disaster.

I have never been able to get this right. When I program a bar pull, I go to stock advance but when selecting a tool, there seems no easy way to add a bar puller to the tool list. When I try to post out with an OD tool, it errors out so I end up hand coding the pull. What is the easiest way to get a puller device in my tool list? If I need to draw one up, is there an easy around this? My books do not go into much detail at all on this. I am also unsure if this is even my problem regarding errors during posting. This is a basic Fanuc based Mori slant bed 2 axis.

Thanks for all your help Jay. You have been a LOT of help.

I noticed the in-house contact specifically says do not contact for posts. Who do I talk to?

I am not familiar with in-house. New here. Is this a reseller of posts? Is this what you are recommending? I am not sure if I can get the Dean to grant funds for a post just yet but possibly. Are none of the generics close enough to work with? I noticed you too have fought a very similar situation with mill/turn machines. Sounds like this is just MCX's short fall in lathe work.

We are playing around with a new to us lathe that is Fanuc based. Machine has X, Y, Z, C1, B ( sub motion), and the live tools. I cannot find anything close to this as a generic machine in X2 so curious how we get started learning to modify an existing post? Is this a mountain to climb? I have experience working on existing posts for mills to streamline code but that is about it. Does X2 have some sharp utilities to create a new machine like this?

Bryan, I really appreciate your help! That one works very slick indeed. One of the features I liked about the MPSUBREP post available here is it posts the tool, length, and dia offset and gives the Z max and min for each tool. I really liked how clean yours is. I like the spaces between ops for a better visual. I will have to mess with it more later this week. Thanks again Bryan.

I am trying to educate on multi-offsets. What we always did in the production world was copy/paste our posted file because we could never find a way to post G54-G58 with T1, G58-G54 with T2, etc, and run the table back and forth. I realize it is easy to multi-offsets in mastercam but how do we get it to do what is mentioned above? We are posting out for a Haas mill and using X2MR2 at the current time.

Is there a way to open Catia files in X2 and maintain geometry like Solidworks and X3? Would be SUPER nice to be able to change dims on a part if needed. We are pretty new to lathe ops. Wondering how you program a 3D part on a 2 axis machine in X2? We simply cannot select any geometry. Have to import 2D lines only. Also, when creating stock and chuck for lathe parts, they are always normal to the part body and never lay over the part correctly, how do you fix that?