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:

mr801

Verified Members
  • Posts

    121
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by mr801

  1. I'm going to play around with it some more to see if I can get it working correctly. I will get back with any results that I come up with. I failed to mention that you would really only want to do this with milling operations and omit the variables in drill cycles. One other reason that I would find this useful would be for R&D testing on new cutters with feeds and speeds. Thanks for the replies. I am going to go shove my nose back in the post for more editing.

  2. I have been messing around with my post on making it post out macro variables for feeds. Little success, close, but no cigar. Has anyone used a post in this manner. Sample code:

     

     

    O1000 (HORIZONTAL MACRO)

    G00 G17 G20 G40 G80 G94 G90

    G91 G30 Z0.

    M01

    (COMPENSATION TYPE - COMPUTER)

    N53 T53 M06 ( 1/2 FLAT ENDMILL 3 FLT FINISH)

    (MAX - Z2.)

    (MIN - Z-.5)

    #100=25.(PLUNGE FEED)

    #101=80.(FEED)

    #102=1969.(BACK FEEDRATE)

    #103=1000.(RETRACT)

    M11 (UNLOCK)

    G00 G17 G90 G54 X-1.51 Y-.125 B0. S14000 M03

    M10 (LOCK)

    G43 H53 Z2. M08

    G94

    G332 R3.

    G05 P10000

    Z.2

    G01 Z-.5 F#100

    X-1.385 F#101

    G03 X-1.26 Y0. I0. J.125

    G01 Y1.

    G02 X-1. Y1.26 I.26 J0.

    G01 X1.

    G02 X1.26 Y1. I0. J-.26

    G01 Y-1.

    G02 X1. Y-1.26 I-.26 J0.

    G01 X-1.

    G02 X-1.26 Y-1. I0. J.26

    G01 Y0.

    G03 X-1.385 Y.125 I-.125 J0.

    G01 X-1.51

    Z-.3 F#103

    G00 Z2.

    X-1.5 Y-.125

    Z.2

    G01 Z-.5 F#100

    X-1.375 F#101

    G03 X-1.25 Y0. I0. J.125

    G01 Y1.

    G02 X-1. Y1.25 I.25 J0.

    G01 X1.

    G02 X1.25 Y1. I0. J-.25

    G01 Y-1.

    G02 X1. Y-1.25 I-.25 J0.

    G01 X-1.

    G02 X-1.25 Y-1. I0. J.25

    G01 Y0.

    G03 X-1.375 Y.125 I-.125 J0.

    G01 X-1.5

    Z-.3 F#103

    G00 Z2. M09

    G05 P0

    M05 G91 G30 Z0.

    M01

    M11 (UNLOCK)

    G91 G28 X0. Y0. B0.

    M10 (LOCK)

    M30

     

    This is just a simple program of what I would like it to do. I would like to replace the plunge,feed, backfeedrate, and retract with macro variables. This way I could change one number and that affects the whole toolpath for that tool. A lot of the high speed toolpaths are pretty large files. I have a fanuc 31iA control that is fairly fast at finding and replacing but for those that have older controllers this would help out. If anyone has done this before I would be interested in how they implemented it into their post.

  3. Here is what it takes.

     

    first, initialize the new variable....

     

    # Common User-defined Variable Initializations (not switches!)
    # --------------------------------------------------------------------------
    drillnum : 0 #number of points

     

    Then format it with your custom prefix....(last one below...)

     

    # Toolchange / NC output Variable Formats
    # --------------------------------------------------------------------------
    fmt T 4 t$ #Tool No
    fmt T 4 first_tool$ #First Tool Used
    fmt T 4 next_tool$ #Next Tool Used
    fmt D 4 tloffno$ #Diameter Offset No
    fmt H 4 tlngno$ #Length Offset No
    fmt G 4 g_wcs #WCS G address
    fmt P 4 p_wcs #WCS P address
    fmt S 4 speed #Spindle Speed
    fmt M 4 gear #Gear range
    fmt "HOLE COUNT = " 4 drillnum #

     

    Then you need to have the NCI give your new variable (drillnum) a value...

     

    pparameter$ # Run parameter table
    if prmcode$ = 15083, drillnum = rpar(sparameter$,1)

     

    Now output it wherever you want... (I chose right at the top of the toolchange common postblock)

     

    ptlchg_com #Tool change common blocks
    if opcode$ = 3, pbld, n$, "(", *drillnum, ")", e$
    if force_output | sof,
    [
    result = force(ipr_type,ipr_type)
    result = force(absinc$,absinc$)
    result = force(plane$,plane$)
    ]

     

    Here is what I get for code....

     

    N232 G91 G00 G28 Z0.
    N234 M00
    N236 ( HOLE COUNT = 17 )
    N238 ( LOAD T2 M06 )
    N240 M00
    N242 M11 (UNLOCK C)
    N244 M13 (UNLOCK 
    N246 G00 G17 G90 G54 C30. B0. X5.4218 Y0. S983 M03
    N248 M12 (LOCK 
    N250 G43 H2 Z8.419
    N252 M08
    N254 G94
    N256 G98 G81 Z6.169 R6.519 F4.25

    For some reason I cant get the indentation to work correctly here.... just follow along with the lines of code in your post.

    HTH!

    I was starting to go about it with a switch, but I like how you have done it. I have added it and it works awesome! Thanks a ton. The new syntax highlighting and format on the forum is nice for the post editing section!!
  4. I have been using SpaceClaim for the last two week as a trial. I am blown away at it's capability for design and modeling. I have used Mastercam since version 8. I feel like I am just as proficient drawing with SpaceClaim as I am in Mastercam or more so. It is very intuitive and easy to navigate. You will be stunned at how fast you can start working with it on a level to your Mastercam abilities. My VAR got me a demo. We have a seat on the way!! It would be nice if Mastercam dropped its 2d drawing, solid and surface modeling and integrated SpaceClaim for those needs. The layout for drawings and sheet metal design is just so easy to use and user friendly. And NO I'm not a reseller for them, just a happy customer.

    • Like 1
  5. I don't think this would be trivial. You are saying you would like a comment stating the number of drill points prior to the drill operation. The NCI file is linear and so the only way to find out that piece of information is to suspend all code output until after all the points are drilled while counting the number of points. Then the number of points could be output, and then release all the "buffered" code. It would be a bit of a pain to set up, but I doubt it would be impossible. You should contact your reseller and see what they suggest.

     

    M30

     

     

    Would it be possible to pull the variable # from the opps manager in that operation instead of using a buffer. I could call my reseller and have him do it, but I like the challenge of making it work and being able to do it my self.

  6. Very easy. Just add the desired comment into the comment box of the corresponding drill toolpath. See attached.DRILL.pdf

     

    That works, and I have done it that way, But I was talking about modifying the post so it would post out all the drill type opps with the number of points in that operation in (). I know that I would like to put a switch in the post and build the variables, but just curios if it's an easy add to the post.

  7. Find the following sections in your post:

     

    pfcout           #C axis output
         cabs = 0   #ADD THIS LINE TO ALWAYS MAKE B0.0 OUTPUT
         if index = zero & rot_on_x,
           [
           if absinc$ = zero, *cabs, !cinc
           else, *cinc, !cabs
           ]
    pcout           #C axis output
         cabs = 0   #ADD THIS LINE TO ALWAYS MAKE B0.0 OUTPUT
         if index = zero & rot_on_x,
           [
           if absinc$ = zero, cabs, !cinc
           else, cinc, !cabs
           ]
    

     

    HTH (This came from a post for NH5000 btw)

     

    Awesome! Thanks EX!

  8. I did a search and couldn't find anything, But I remember reading about it somewhere. I am using the horizontal MPmaster post slightly modified for a Mori NH5000. I am wanting to have the post, post out B0.0 at every WCS, so for top WCS and T/Cplane right I want it to post "B0.0" in stead of "B90.0". I am using different workoffset numbers for each T/Cplane and control the B axis offset with machine. Just so I have a little more control on positioning if I need it. If anyone can point me in the right direction to mod the post or to the thread that covered this, that would be great! TIA.

  9. Feed back for X6 MU2. I'm getting a consistent crashing on Xform scale on Geometry. Someone else want to confirm.

     

    It just BSOD'ed when I tried to send a crash report, and won't even let me open Mastercam at all. Hope I don't have to do a complete reinstall.

  10. I recently bought a seat of Spaceclaim and it includes a chook that lets you

    send models back and forth between Mastercam and Spaceclaim.

    It's pretty cool, but Spaceclaim running inside Mastercam???? sounds cool but I havn't heard anything like that

     

    The Chook would be a nice feature!

  11. Here is a portion of a file to do a simple contour around a 10" X 8" Rectangle with a 5/8" tool

     

    Thanks for that. I talked to my reseller to see if we could get a trial on a post for 60 days. It is some of the wierdest code I have ever seen.

  12. I have a friend that just picked up a new Weeke Vantech 510 router. I was wondering if someone with a weeke/homag post could just post out some code so I can try to wrap my head around it. I am pretty familiar with G-code,Heidenhain,Mazatrol,Mapps,Macro B, User Task, but this .MPR code is just outta this world. Who knows if this topic will ever get any attention, seeing as how I could only find a few posts with the search. Anyway, Thanks in Advance. I'll see if my vAr can find something too.

  13. +1 to what Joe said about spindle orientation. You would need to come up with some mechanism to lock the spindle. Something similar to what keeps a angle head oriented should work.

     

    Mike

    We have bigplus with the spindle orientation slot for tool holders. Thats what made me think of it. The only thing I could think of is what the finish would look like and get the part of in a decent amount of time. The Part is a 8in. Dia. 15in long with some faces, pockets, tapped holes in different orienting positions. Just trying to do the "done in one" approach.

  14. The first one is not new it happens in every version, its the old

    'unhandled exception error' ... different new look...

     

    The other was supposed to be resolved with the re- release of X 6.

     

    Are you using the first or 2nd release?

    I believe the date it came out was Dec 28th

     

    Follow this link if you are using the initial dload or disc release

     

     

    http://www.emasterca...showtopic=65612

     

    regards

    Rick

     

    Yes it is the latest version X6 V15.0.4.3

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