Jump to content

Welcome to eMastercam

Register now to participate in the forums, access the download area, buy Mastercam training materials, post processors and more. This message will be removed once you have signed in.

Use your display name or email address to sign in:

Sbarner

Verified Members
  • Posts

    267
  • Joined

  • Last visited

About Sbarner

  • Birthday 04/29/1982

Uncategorized

  • Location
    Pullman, WA

Recent Profile Visitors

2,321 profile views

Sbarner's Achievements

Newbie

Newbie (1/14)

4

Reputation

  1. 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.
  2. 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?
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. 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.
  8. Good. THAT looks like some good code. That TL post is a turd. Nice work.
  9. Closer. Looks like you're missing the depth. Can you paste the code you posted into the ltap section?
  10. 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.
  11. 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.
  12. 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.
  13. 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.
  14. Thanks all. Extremely helpful. WHat diameter are you initially threadmilling to before comping the tool? The handtight diameter?

Join us!

eMastercam - your online source for all things Mastercam.

Together, we are the strongest Mastercam community on the web with over 56,000 members, and our online store offers a wide selection of training materials for all applications and skill levels.

Follow us

×
×
  • Create New...