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:

CNCGUY

Verified Members
  • Posts

    485
  • Joined

  • Last visited

Everything posted by CNCGUY

  1. Is it possible you are, un-knowingly, filtering for a specific size drill? One that may not be in your library.
  2. Removing the brackets didnt make difference. This is the only way I could get it to work. code: ldrill$ #Canned G81 drill cycle, lathe pdrlcommonb if feed > 0.008, feed = 0.008, else, feed = feed pcan1, pbld, n$, *sg80_f, "G99", prdrlout, pfzout, pffr, strcantext, e$ if initht$ > refht$, pbld, n$, sg00, "Z.1", e$ pcom_movea
  3. Man John, youre on it. Now I'm more confused. It works me in V9 and for you X3, but not for me X2. I dont see whats wrong. Any other ideas.
  4. O.K. You have forced me to dig deeper (thats a good thing). It does work for anything over .008 but will not work for .008 or less. code: N5 (.718 SPADE DRILL - HSS) G00 G53 X0. Z-30. G54 G97 S652 M03 T5 G00 X0. Z.1 M09 I guess my question now is - How do I get it to post properly if the value is .008 or less?
  5. John, It works for me too, as long as the feed rate is .008 or less. If its over .008, nothing is posted.
  6. John, Unless Im misunderstanding you, thats not the problem. I want to use canned drill cycles - they are checked. I just need to limit the feed rate on any drill with to high a feed (no more than .008).
  7. Hey all, I need to limit the feed rate on drills for a specific machine. Here is what I did in ldrill in the post (modified fanuc). code: ldrill$ #Canned G81 drill cycle, lathe pdrlcommonb if feed > 0.008, feed = 0.008 [ pcan1, pbld, n$, *sg80_f, "G99", prdrlout, pfzout, pffr, strcantext, e$ ] if initht$ > refht$, pbld, n$, sg00, "Z.1", e$ pcom_movea It worked in V9 but wont work in X. Infact, the drill cycle wont even post. Any ideas on what I need to change?
  8. quote: added a bit of logic at ptoolend to output M89 if it was Thru tool and not flood Jimmy, Can you go into more detail on the changes? I have been working on this and cant get it to turn off. Thank's
  9. Taper angle should be 1.78333. That will get the code I posted above. BTW-I am running X2, not X3. HTH
  10. John, What are your screen colors set to? Might give that a try.
  11. quote: MC will not do this correctly The only thing we thread mill with is MC. Here's the code for 1/4-18 NPTF in 316 stainless. . .HTH code: N16 T16 M06 H16 (VARDEX 0250-18 NPTF-F THREAD MILL) G54 G00 G90 X0. Y0. S4439 M03 M08 G43 Z.63 G01 Z.0044 F75. G41 D16 X.0556 F3.46 G03 X0. Y.0756 Z.0183 I-.0556 J.0174 Y-.0765 Z.0461 I0. J-.076 Y.0773 Z.0738 I0. J.0769 X-.0573 Y0. Z.0877 I0. J-.0599 G01 G40 X0. Z.0044 F75. G41 X.0711 F4.23 G03 X0. Y.0911 Z.0183 I-.0711 J.0178 Y-.0919 Z.0461 I0. J-.0915 Y.0928 Z.0738 I0. J.0923 X-.0728 Y0. Z.0877 I0. J-.075 G01 G40 X0. G00 Z.63 M09 G53 G00 Z0. G129 X0. Y0. M30
  12. Yes, this is true!! quote: The taper is built into the cutter.. However, this is not. quote: A circle toolpath is all that is required. Quote from post in practical machinist. FWIW - I agree!! We cut nptf every day. quote: I threadmill NPT threads all the time, and yes, you DO have to taper the helical move to cut the correct form, even though the threadmill has the taper ground in already. Obviously, since you are moving upwards as you cut, you also need to move outwards to maintain the correct engagement on the taper.
  13. quote: Had to re-pick the boring tool geometry in order for the boring bar to work. Why? You are only importing the tool parameters - not the geometry.
  14. Ron, Pretty sure I followed your steps, but I dont see any place to change the location.
  15. Is there a way to config. where mcam looks for the thread table? So far it appears that mcam looks at the install directory. In V9 there was a way, but in X I cant figure it out. Thank you.
  16. Ron, We have Nakamura TW-20's as well as HAAS TL-15 and your right, the a TL-15 is far from the Nak. I agree, they are small and not for complex parts. quote: You want to do the impossible on a HAAS sync two spindles together running. Sorry HAAS Lathes will not do this call them they will tell you as much.Yes and No. They dont have any way built into the machine (for a true sync). I spoke with the lathe prod. mgr. at IMTS who said they cant due to different size motors, which makes sense. Its a sub-spindle machine, not a twin spindle. I have developed a way to sync. both spindles using G96 for cutoff. According to HAAS, the way I do it, is the only way it can be done. FWIW, they are working on a twin spindle lathe. quote: M143P3000 is spindle speed and the sub does not support G96 only G97 types of RPM's. . . . . . . . . . .I do not use the G14 preferred method of HAAS for the sub I program it just like a real sub spindle If you use the G14 method for the sub, G96 is available. (However that wont work when trying to sync the spindles) Im not trying to defend the HAAS. Accept them for what they are - 30% of the cost and we all know, you get what you pay for. I had a hard time with this since we had the Nak's first. I assumed every machine that had 2 spindles worked like these. Fortunatly I have been able to work around and add (part eject confirmation) to get this machine to the point of producing parts as it should [automated]. Unfortunalty it has taken app. 6 monthes. Just another point of view!!
  17. Wannabe, quote: M143 S00 (SUBSPINDLE ON) Sub-Spindle RPM commands use P. Dont dwell before starting the Sub either. Try this: M110 G04 P1. G97 S100 M04 P100 M143
  18. Hey guys, Any body have a source in Cambridge Ontario for spindle re-grind. We have an old fadal in our Cambridge facility that had a tool come loose and needs to be reworked. A new spindle is over $5K and the machine is hardly worth that. Thanks for the help.
  19. I want to copy a good MD & CD then rename them and change the post. When I try this, as soon as I change the post all the file path's are screwed up. Is there a better way to do this?
  20. quote: It looks more like tool plane numbers (all the tool planes are lathe upper left they just have different numbers) which have never been an issue for me. Phil, Youre correct. The only issue I have is its cluttered, not clean like mill. It has never been a problem as far as function though. quote: I've tried reassigning all the OPS to the same plane but it doesn't stick.. Me too, with the same result. I guess as long as it works What about the tool offset numbers? Is that a MD issue?
  21. Hey all, We are just starting to use X2 for lathe programming. Everytime we open a V9 file in X2, we get multiple levels in the view manager. See photos below. Everything is programmed with one W/C and C/P so I dont understand what is going on. I cant change them in X either. Also the tool numbers come in with the wrong offset. They start at 1 and increment by 1. ie: 101, 102, 503, 604, 205, etc. Any help is appreciated.
  22. I do that - but they still dispaly when the file is opened. We have another seat that works right, but I cant find the difference.
  23. Everytime I open a file, the toolpath is displayed. I know how to get rid of it once its there, but would like to not have it show up everytime I open a file. Ive looked for a setting, but cant seem to find what to change. Is this possible??

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...