Thanks guys. I did a forum search after I posted that last night and came across another post where John helped with a similar issue. The sav_tldia$ worked like a charm.

All,

I'm working with MPMaster to try and get broken tool detection for our Makino PS95. I'm using Misc Integers to do so. I have it down, but the only part that's hanging me up is outputting the tool diameter. The disc for the tool setter on the Renishaw is only 10 mm or so. SO if the tool is bigger than that, it has to be offset half the diameter. In the pretract section of the post I have this:

pbld, n$, sgabsinc, sgcode, [if gcode$ = 1, sgfeed], *sg28, "Z0.", [if gcode$ = 1, feed], scoolant, e$

if sav_mi1 = 1,

[

if tool_typ$ <> 3,

n$, "G65 P9858", prv_t$, (if tldia$ > .375, *tldia$) "H.005", e$

else,

n$, "G65 P9858", prv_t$, "H.005", e$

]

# if lock_codes = one & rot_on_x, pbld, n$, *sunlock, sunlockcomm, e$

# pbld, n$, *sg28, "X0.", "Y0.", protretinc, e$

# if lock_codes = one & rot_on_x & cuttype = 0, pbld, n$, *slock, slockcomm, e$

But all I can get out of that is the NEXT ops tldia$ value. For example, If I have a 1.25" shell mill followed by a 1/2" endmill, at the end of the shell mill, I can get the right macro call, but with the next ops tldia$:

(1.25 SHEAR HOG TOOL - 12 DIA. OFF. - 12 LEN. - 12 DIA. - 1.25)

(COMPENSATION TYPE - COMPUTER)

N12

T12 M06

G00 G90 G54 X-1.375 Y-.25 S10000 M03

G43 H12 Z2. M08 T1

G17 Z.21

G94 G01 Z-.01 F40.

X2.375 F60.

G00 Z2. M09

M05

G91 G28 Z0.

G65 P9858 T12 D0.5000 H.005

M01

(1/2 DIA 1 1/2 2 FLUTE PLASTIC CARBIDE TOOL - 1 DIA. OFF. - 1 LEN. - 1 DIA. - .5)

(COMPENSATION TYPE - WEAR COMP)

N1

T1 M06

G00 G90 G54 X.55 Y-.86 S7500 M03

G43 H1 Z2. M08 T19

G17 Z.21

G94 G01 Z-.3333 F25.

G41 D1 Y-.81 F80.

G03 X.5 Y-.76 I-.05 J0.

I've tried using the prv_tldia$, but it's not happening. What am I missing?

AFAIK, there is no way to do this with the "stock" tools. I believe you have to draw your own to get it comped to where you want. I am in the same situation. Using the edge of the tool for the Z axis. I usually just program to the depth I need, and let verify show a crash. I know the code is good.

I just did a bunch of back chamfering with one of those. I had to end up using a 2D contour toolpath and fart around with the depths until it came out right. I don't see why one couldn't use a chamfer toolpath, I just couldn't/wouldn't make it work.

Very well. I've farted around with the mpfan before, so I am somewhat familiar with it. I can probably give you a hand if you run into trouble. You can PM me here or email me. sbarner (at) wsu (dot) edu.

Russh, Did you get this problem resolved or are you still tackling it? I've been away from the forum a few days. I can try to lend assistance if you're still at it.

Peck tapping on the Haas isn't as simple as simply adding a peck value. You need a line of code for each depth you wanna go. I've eedited my mill post to do it, but haven't done the lathe one yet. There is a considerable amount of post editing that needs to be done.

If you get stuck, you can PM me here or email me at sbarner (at) wsu (dot) edu

I check that more often.

Good. THAT looks like some good code. That TL post is a turd. Nice work.

Closer. Looks like you're missing the depth. Can you paste the code you posted into the ltap section?

Also on the Mill when you select the canned cycle for tapping the Speeds and feeds values become relative to each other. The lathe doesn't seem to be working in the same fashion. Is there a way to fix this?

No.

I'm running an SL-20, but the code should be the same. This is what my tapping section looks like:

ltap$        	#Canned tap cycle, lathe
 	pdrlcommonb

 	if use_pitch = 0, #Feed/Min mode, feed divided by spindle speed is equal to thread lead 
   	[
  	if rigid_tap, pbld, n$, sg9697, sm03, speed, e$   		#Rigid Tapping	Can use G84/G88 with M29 or just G84.2
   	pcan1, pbld, n$, *sgdrlref, pgdrlout, pxout, pyout, pzout, prdrlout, *feed, strcantext, e$
  	]
 	else, #Feed/Rev mode, feed is equal to thread lead 
   	[
   	if rigid_tap, pbld, n$, sg9697, sm03, speed, e$   		#Rigid Tapping	Can use G84/G88 with M29 or just G84.2
   	if met_tool$, pitch = n_tap_thds$  # Tap pitch (mm  per thread)
   	else, pitch = 1/n_tap_thds$   	# Tap pitch (inches per thread)
       	, pbld, n$, *sgdrlref, pgdrlout, pxout, pyout, pzout, prdrlout, *pitch, strcantext, e$
   	]
	pcom_movea
	pcanceldcl

The use_pitch thing is a switch in the post to output feed/rev or inches per minute. It doesn't look like the TL post has that switch, so that may be something that we would have to add. That TL tapping section is dog doo. And you can probably disregard the "if rigid_tap" thing as well (you are rigid tapping right? Not using a floating holder?) If so, your code may look like this:

ltap$        	#Canned tap cycle, lathe
 	pdrlcommonb

 	if use_pitch = 0, #Feed/Min mode, feed divided by spindle speed is equal to thread lead 
   	[
   	pbld, n$, sg9697, sm03, speed, e$   		#Rigid Tapping	Can use G84/G88 with M29 or just G84.2
   	pcan1, pbld, n$, *sgdrlref, pgdrlout, pxout, pyout, pzout, prdrlout, *feed, strcantext, e$
  	]
 	else, #Feed/Rev mode, feed is equal to thread lead 
   	[
   	if rigid_tap, pbld, n$, sg9697, sm03, speed, e$   		#Rigid Tapping	Can use G84/G88 with M29 or just G84.2
   	if met_tool$, pitch = n_tap_thds$  # Tap pitch (mm  per thread)
   	else, pitch = 1/n_tap_thds$   	# Tap pitch (inches per thread)
   	pbld, n$, *sgdrlref, pgdrlout, pxout, pyout, pzout, prdrlout, *pitch, strcantext, e$
   	]
	pcom_movea
	pcanceldcl

See where that gets you.

Actually, now that I read your post more thoroughly, you'll probably have to make a few more edits after that one to stop the M05 and M04 codes from being output. FWIW, I use the MPLmaster post, and it works great.

It looks like the canned cycle is setup to call a G32 no matter what. In the post in the "ltap" section:

 pbld, n$, *sthdg32, pfzout, pffr, pnullstop, e$

I don't know what your post editing skills are like. T'were it me, I'd probably start by changing the *sthdg32 to a *sg83_f

I realize that the tapping code is G84, but the format table that defines the G codes for the canned cycles is messed up I think. Or you could eliminate the *sthdg32 and put in a "G84" including the quotes. I'm not sure off the top of my head if the Haas will need a retract amount in the canned block, so it may alarm out when doing the cycle. I probably wouldn't run a part after modifying something like this until I was sure that the code works. As always, make a backup of the post before you start monkeying around with it.

This wouldn't happen to be a Haas would it? I recently went through the same thing trying to dump the NC files on the Haas hard drive. IT is possible in Windows 7. This link here is the steps we follwed to get it working.

Thanks all. Extremely helpful. WHat diameter are you initially threadmilling to before comping the tool? The handtight diameter?

So currently we are tapping NPT threads on our VMC. It seems to work well for threads from 1/16 NPT to about 3/8. I've got to do a couple 3/4 NPT threads and I want to threadmill them. Threadmilling NPTs is kind of a new area for me, so I have a couple questions:

First off, what is the preferred practice regarding the taper of the hole before threadmilling? Taper or no? If yes, then what is the diameter that is at the top of the hole? Is the tapdrill size the big part of the taper or the small end?

Secondly, I've got a chart that says for a 3/4 NPT tap, one would go 15/16" deep. Would I want to threadmill that deep, or more specifically, what is the depth that one would go using a threadmill? The handtight engagement?

Thanks in advance.

As far as your depths go, Thoob, I think there is another factor at work there. Do you have something in the "allowances" fields on the parameters? What if you post the code longhand instead of canned? Do you still get the .065-.07 instead of what your depth value is? As far as the number of passes, what does it do in backplot? Does it take the 20 you want or the 40 that your code gives you? I'd check the control definition (if you feel comfortable) and see if there is something in there that could be doing it. It could be a post thing too.

Thoob,

FWIW depending on the material, those look good to me. Where I have the most trouble is the depth of the thread. Using the software's tables or standard values for threads gets me results ranging from perfect with no cutter comp to having to comp up to .018. An 8 pitch 60 degree? I think I'd be going with about .081 depth on that. I realize that's not what you were asking, but that's my 2 cents.

I'm pretty sure Brendan is right on this one. It's in the config. If you click the + next to verify interface, and click on verify settings, there is a variety of options there. I had pretty much the same problem as you...a particular STL getting locked in as the stock setup file. SO if you pull the dropdown down, and select file, then delete whatever file path is in the "File name" box, then switch back to box or cylinder or whatever you should be golden. Make sure the "Initial Stock Size Source" dropdown is selected appropriately as well. Also, be sure stock settings in your operation defaults are correct. That should do it.

I've got a two year degree from a community college in CNC Manufacturing Technology or something like that. I don't know if it was truly worth the money I borrowed for it, but it certainly has some value. Now I have a job where I've climbed the ladder pretty fast, and pretty much have peaked. There's no getting new equipment here, or buying a multi axis license. I take that back. We do get new(er) equipment every now and then but my requests for live tooling or a trunnion are overridden. *Sigh*. I have a wife that likes to spend money, a three year old son, and 2 month old twin daughters. I have no prospects of any raise after my last step increase in March. So....

I decided to go back to school and enroll in the ME program. One of my perks is taking up to six credits for five bucks a semester. It's gonna take seven years (literally) to earn the two full time years of credits, but it'll be worth it. Even if I make 20 grand more a year, all it will have cost me is like 70 bucks in tuition and whatever books cost. Of course making up the work hours and the homework equates to time away from my loved ones, but when I bring home that paycheck that has 1800 more dollars in it, I think they'll understand.

I think you probably have "Lock Feedrates" enabled (checked) in the configuration. If you uncheck this, it'll probably update next time you do it.

I think there is several ways to get around this. There may be a setting in the post to change, or one can edit their machine definition to an appropriate home position then use "From machine" as your home position. You can also edit each tool's home position and use "From tool", or use "User defined" as the home position and set it how you want.

I did mine through a custom drill cycle. It really works nice. Actually, I did a drill cycle for stock over 1/2" diameter and stock under 1/2" diameter because of the way the puller engages stock differently. Figure out the Z coordinate, figure out the pull amount (input into the peck box) and huzzah. JParis had an example of a post mod to make to do it, so all props go to him. It's a fairly easy post mod to make if you know what you're doing. Do a forum search for it, and you should find it.

Mine was pulling a 6" diameter piece of aluminum Holobar out of the chuck at 4000 RPM. I nearly had to change my shorts.

+1 to JParis. Reference points also work. They're on the first page of your toolpath parameters...where you set your feeds and speeds. Just define a Z position for your approach and exit and you'll be golden.