If you're using 2 chains with syncing set, try turning the sync'ing off...generally it means that you have a sync type setup and it can be as simple as 1 chain has 12 points and the other has 14.... With "ugly" geometry, I will sometimes chain them and turn them into a spline There's a couple things there to check

Lathe...I surfed right over that detail...

Haas offers a broaching add-on...short of that, I don't know any other way....

Mostly, you don't.. There are starting settings in some paths on the Parameters page but beyond that...the algorithm just does it thing. You can cut them seprately and chain them in the order you want to get around it

I don't currently get a call for much metric tapping at this point....I have probably done 2 or 3 metric taps in the past year +

I'm not 100% sure this is it, I can't find the original zip file I made but the file name is found in Dropbox, I had it backed up.. looks like it was 2018 so it'll need to be updated https://www.dropbox.com/s/181cukkkofwo2rq/inch_mm taps.tooldb?dl=0

Hmmm, let me see if I still have it

As pointed out above, if a post is needed, through your both IHS and Postability work through your reseller. You're not getting around them whichever way you decide to go

Resellers are "required" to provide a certain level of support even without a contract..that would seems like a real easy question to ask them.

AM I the only one that my ears perk up when someone is reseller averse? Big red flag to me

If it's thre "MT Product", get with your reseller there isn't muich you can do on the post end.....if it's Lathe/Mill combined for a mill turn, get with your post writer... You have to chase this upstream

I'll mess with this when I get into the office later on but I don't think you're going to be able to use C Axis contour for that.....going to take a MIll path I believe

Happy to be of assistance

Just one more reason I don't drive toolpaths from solid geometry

format your own variable tl_dia fmt " " 17 tl_dia then above your output line tl_dia = tldia$ That should get you closer

You could certainly add a post check for it.. I did something similar for planes...seems this could be edited to serve use_wcs_chk : no$ #Set to turn on/off wcs checking stplanewarn : "ERROR - TPLANE CONFLICT WARNING, TPLANE DIFFERENT, VERIFY OUTPUT" if use_wcs_chk, [ !wcs_id, !op_id$, !tplane_id #04/12/18 sav_wcs_id = wcs_id #04/17/18 sav_tplane_id = tplane_id #04/12/18 ] if use_wcs_chk, [ !wcs_id, !op_id$, !tplane_id #04/12/18 if sav_wcs_id <> wcs_id, pwcs_check #04/18/18 if sav_tplane_id <> tplane_id & not(rot_on_x), pwcs_check #04/12/18 ] pwcs_check if sav_wcs_id <> wcs_id, #04/12/18 [ op_number = opnumber pbld, n$, sopen_prn, "WCS DOES NOT MATCH INITIAL WCS SETTING", sclose_prn, e$ pbld, n$, sopen_prn, "OPERATION", no_spc$, "#", sspace, op_number, sclose_prn, e$ if compwarnflg = 0, result = mprint(swcswarn) spaces$ = 0 n$, pspc, *sm00, " ", sopen_prn, swcswarn, sclose_prn, e$ n$, pbld, exitpost$, e$ spaces$ = sav_spc compwarnflg = 1 ] if sav_tplane_id <> tplane_id, #04/17/18 [ op_number = opnumber pbld, n$, sopen_prn, "T-PLANE DOES NOT MATCH INITIAL T-PLANE SETTING", sclose_prn, e$ pbld, n$, sopen_prn, "OPERATION", no_spc$, "#", sspace, op_number, sclose_prn, e$ if compwarnflg = 0, result = mprint(stplanewarn) spaces$ = 0 n$, pspc, *sm00, " ", sopen_prn, stplanewarn, sclose_prn, e$ n$, pbld, exitpost$, e$ spaces$ = sav_spc compwarnflg = 1 ]

Microsoft .NET has caused many issues that I have seen over the years, Several times I have had to uninstall it as far back as it will let and then reinstall startoing with older to newer versions... Can't say for certain "that's it" but I have seen some strange issues with it over theyears.

something like pbld, n$, "#101", no_spc$, 61, no_spc$, tldia$, e$ or pbld, n$, 35, no_spc$, "101", no_spc$, 61, no_spc$, tldia$, e$

Effective I believe Which amounts to how long is the effective thread length

fmt "D#" 4 maz_doff #Mazak Pallet Tech Diameter offset number #added 02/10/2020 fmt "H#" 4 maz_hoff #Mazak Pallet Tech Height offset number #added 02/10/2020 maz_doff = 51999 #modified 02/10/2020 maz_hoff = 51999 #modified 02/10/2020 pccdia #Cutter Compensation #Force Dxx# if prv_cc_pos$ <> cc_pos$ & cc_pos$, prv_maz_doff = c9k ##modified 02/10/2020 sccomp if cc_pos$, maz_doff #modified 02/10/2020

I actually just signed out of it....for me, problem solved...it's there, just ain't doing nuttin'

Turn it off it is restoring the original everytime you alter the config

God that bite me hard...drove me crazy for a few hours until I figured it out

Did you ask your reseller?

Contact your reseller is best idea