It does on our machines. Looks like he's running a Haas though. I never ran a Haas, so maybe it's M89

Yes, look ahead in many macros is a no-no. The G04 X0, is an excellent suggestion. I've also seen G53 used for the same thing. Just look at some Renishaw probing code and you'll see what I mean.

Look in your general machine parameters. Under the coolant tab

Just change the '0' to a '1' on this line haas : 0 #Haas style peck drill and extended offsets, 0=no, 1=yes

You'll have to look and see how it's configured in the post. Seach for the variable haas

What do C and R signify? And are you initializing C and R?

Are you wanting to check for 'NIL' or are you checking for a '0'

Because the chain will stop at the duplicates. It basically won't highlight the duplicate. Gaps, it all depends on where the gap is, Gaps are a little tougher to see using this method.

I'm sure this has been mentioned a thousand times, but just in case, I use the "SHIFT" and click on a chain will hi-light the entire chain. I also use this to look for duplicate geometry and small gaps in the chain.

Cool tool. Thanks.

Here is the complete code for our Makino NX51. Keep in mind that this particular one is for a horizontal, but the math is the same no matter if you want to find the centerline of -A-, -B-, or -C- The #900 is the size of the ball being probed. (*************************) N4 ( THIS PROGRAM WILL MEASURE ROTARY CENTERLINE AND ADJUST ) ( YOU SHOULD ALWAYS CALIBRATE PROBE FIRST AT N2) ( SET B AXIS BALL TOWARDS SPINDLE ) ( SET G10 LINE TO CENTERLINE OF TOOLING BALL) M00(CHANGE G10 LINE) G10G90L2P1X-.025Y11.125Z5.475B90. G11 T90000000M6 ( PROBE ) G0G90G54 G65P9999A1.B0. X0.Y0. G43H1D2Z5. IF[#900LT.499]GOTO900 IF[#900GT1.40]GOTO901 G65P9532 G65P9510Z[#900] G65P9514D[#900]Z0.S1. G65P9510X0.Y0. G90 G65P9511Z[#900/2]S1. G01G90Z5.F100. G65P9999A1.B0. X0.Y0. G65P9510Z[#900] G65P9514D[#900]Z0.S2. G1G91X-[#135]Y-[#136] G90 G65P9511Z[#900/2]S2. G01G90Z5.F100. ( STORE G55 XYZ AT B0 ) #750=#5241 #751=#5243 ( NOW ROTATE 270 DEGREES ) () G65P9999A1.B270. X0.Y0. G65P9510Z[#900] G65P9514D[#900]Z0.S2. G1G91X-[#135]Y-[#136] G90 G65P9511Z[#900/2]S2. G65P9510Z20. ( STORE G55 XYZ AT B270 ) #752=#5241 #753=#5243 ( NOW ROTATE 90 DEGREES ) () G65P9999A1.B90. X0.Y0. G65P9510Z[#900] G65P9514D[#900]Z0.S2. G1G91X-[#135]Y-[#136] G90 G65P9511Z[#900/2]S2. G65P9510Z20. ( STORE G55 XYZ AT B90 ) #754=#5241 #755=#5243 G65P9533 M98P8800 #761=[#752+#754]/2 #761=#761*100000 M00( PRESS START TO UPDATE X CENTER) G10G90L52 N19700R#761 G11 M00 N20 (MATH TO CALCULATE CL OF X WITH 3 POINTS) #101=[[#750*#750]+[#751*#751]]*[#753-#755] #102=[[#752*#752]+[#753*#753]]*[#755-#751] #103=[[#754*#754]+[#755*#755]]*[#751-#753] #104=#101+#102+#103 #105=#750*[#753-#755] #106=#751*[#752-#754] #107=#752*#755 #108=#754*#753 #109=2*[#105-#106+#107-#108] #763=#104/#109( CALCULATE X CENTERLINE) #763=#763*100000 #101=[[#750*#750]+[#751*#751]]*[#754-#752] #102=[[#752*#752]+[#753*#753]]*[#750-#754] #103=[[#754*#754]+[#755*#755]]*[#752-#750] #104=#101+#102+#103 #105=#750*[#753-#755] #106=#751*[#752-#754] #107=#752*#755 #108=#754*#753 #109=2*[#105-#106+#107-#108] #764=#104/#109( CALCULATE Z CENTERLINE) #764=#764*100000 M00( PRESS START AGAIN TO UPDATE 19700 ETC) (UPDATE 19700) G10G90L52 N19700R#763 G11 G10G90L52 N19702R#764 G11 M30

BTW, if you have Vericut, you can preload the variables for #750 thru #755 and run the code. That's what I did. I drew a circle in MasterCam going through 3 points, and used the point locations for my variable. Then ran it and the solution should come out the Z and Y of the center of the circle that intersects the 3 points.

I start with the ball at 12 o'clock position and the table at -A- zero, -B- zero and take the first Y and Z. Then I tilt to A45 deg and take the second set of numbers. Then I tilt to A90 and take the third set. The actual -A- angle doesn't matter. Of course the further apart the angles, the more accurate your solution will turn out. But it is important NOT to move you -B- axis. That must stay at the same -B- as you started or else the math will not work. Let me know if you need a better explanation.

What version of MasterCam?

If anyone cares, I created a similar program to find the -Y- and -Z- centerline based on 3 points. Basically, store the following variables then run the below code. It will set your 19700's. #750= 1st Y position #751= 1st Z position #752= 2nd Y position #753= 2nd Z position #754= 3rd Y position #755= 3rd Z position (MATH TO CALCULATE CL OF Y IS WITH 3 POINTS) #101=[[#750*#750]+[#751*#751]]*[#753-#755] #102=[[#752*#752]+[#753*#753]]*[#755-#751] #103=[[#754*#754]+[#755*#755]]*[#751-#753] #104=#101+#102+#103 #105=#750*[#753-#755] #106=#751*[#752-#754] #107=#752*#755 #108=#754*#753 #109=2*[#105-#106+#107-#108] #763=#104/#109( CALCULATE Y CENTERLINE) #763=#763*100000 (MATH TO CALCULATE CL OF Z IS WITH 3 POINTS) #101=[[#750*#750]+[#751*#751]]*[#754-#752] #102=[[#752*#752]+[#753*#753]]*[#750-#754] #103=[[#754*#754]+[#755*#755]]*[#752-#750] #104=#101+#102+#103 #105=#750*[#753-#755] #106=#751*[#752-#754] #107=#752*#755 #108=#754*#753 #109=2*[#105-#106+#107-#108] #764=#104/#109( CALCULATE Z CENTERLINE) #764=#764*100000 M00( PRESS START AGAIN TO UPDATE 19700 ETC) ( PRESS START AGAIN TO UPDATE 19700 ETC) (UPDATE 19700) G10G90L52 N19701R#763 G11 G10G90L52 N19702R#764 G11

Did you try using the system variable or did you try pulling the parameter using pparameter$ and a line similar to this; if prmcode$ = 1013, temp1 = rpar(sparameter$, 4)

I know nothing about wire, but the post documentation shows it's Parameter 1013 bit 4 - "overburn$" There's another section that mentions Parameter 20019 bit 5 - "overburn$" I don't have a wire post to try it out, but i'd try just pulling 'overburn$' Hope that helps. Good luck

Some posts have a "bias angle" is the misc variables. I don't have much success with them, but you can try.

Whenever I see someone using 9.1, or X3 I start thinking the same thing. Maybe I'm just an untrusting sort.

Ok, sent you an email. Thanks again for the help.

I figured it out. I ended up emailing our rep, and as soon as he said 'what's your -A- limits set to?" I realized I never opened up the limit to allow a +A. Now I feel dumb. LOL Thanks for the help. And Millman, no I don't believe I have that documentation.

We just purchased another 5 axis machine and I am building a post for it using one of our other 5 axis machine post that has the same setup. The only difference is that the -A- axis is reversed. I have tried every combination of rotaxis and rotdir but the -A- axis always post out A-. is there another section I should be looking at? Here's the secion I'm messing with. #Assign axis address str_pri_axis : "B" str_sec_axis : "A" str_dum_axis : "C" #Toolplane mapped to top angle position strings str_n_a_axis : "A" str_n_b_axis : "B" str_n_c_axis : "C" #Machine rotary routine settings mtype : 0 #Machine type (Define base and rotation plane below) #0 = Table/Table #1 = Tilt Head/Table #2 = Head/Head #3 = Nutator Table/Table #4 = Nutator Tilt Head/Table #5 = Nutator Head/Head head_is_sec : 1 #Set with mtype 1 and 4 to indicate head is on secondary #Preferred setup is pri. zero matches sec. zero/direction #Zero machine and determine the planes perp. to axis rotations #These plane combinations are valid: #Primary plane XY XZ YZ #Secondary or XZ XY XY #Secondary YZ YZ XZ #Primary axis angle description (in machine base terms) #With nutating (mtype 3-5) the nutating axis must be the XY plane rotaxis1$ = -vecy #Zero -y rotdir1$ = vecx #Direction +x #Secondary axis angle description (in machine base terms) #With nutating (mtype 3-5) the nutating axis and this plane normal #are aligned to calculate the secondary angle rotaxis2$ = vecz #Zero +z rotdir2$ = vecy #Direction was +y #NOTE: Use of 'top_map' requires the dealer match the # above settings below. These must match initial settings!!! p_nut_restore #Postblock, restores original axis settings result = updgbl(rotaxis1$, "-vecy")#Zero was +y result = updgbl(rotdir1$, "vecx")#Direction was -x result = updgbl(rotaxis2$, "vecz")#Zero was +z result = updgbl(rotdir2$, "vecY")#Direction was -x Thanks

It's in the MP documentation. I think it's in MP ref guide - Vol 1. You have to ask your reseller for it. Not even sure if they have an updated one. Mine is old.

I don't have that issue, but try searching the post for #CNC, when something in the post fails it tags it (see below the 2x #CNC lines) bug1$ : 1 # 1 = Output post to screen, 2 = output leader to screen bug2$ : 0 # Append postline labels, non-zero is column position? #CNC<<FAIL>>bug3$ : 0 # Append whatline no. to each NC line? #CNC<<MSG-ERROR(38)>> The variable, postblock, or other keyword is no longer supported

I change my limits on the A axis to force it where I want. So If you tell MC that the -A- negative limit is -80 it will have to position to the positive. In my post it's this section. #Rotary axis travel limits, always in terms of normal angle output #Set the absolute angles for axis travel on primary pri_limlo$ : -9999 pri_limhi$ : 9999 #Set intermediate angle, in limits, for post to reposition machine pri_intlo$ : -9999 pri_inthi$ : 9999 #Set the absolute angles for axis travel on secondary sec_limlo$ : -120 sec_limhi$ : 30 #was 30 #Set intermediate angle, in limits, for post to reposition machine sec_intlo$ : -120 sec_inthi$ : 30 #was 30