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:

mgsanchez

Verified Members
  • Posts

    120
  • Joined

  • Last visited

Posts posted by mgsanchez

  1. Hmm... that is interesting. I run one also, but I program everything G43 in 3 axis or as gage length programming. I normally do not use G143 because of all the restrictions (more trouble that it is worth). I fixed my post to output all of the Haas 5 axis G-Code canned cycles (i.e. G161, G162, G163, G164, G165, G 166, G169). I'm not sure if the 5 axis G-code canned cycles are compatible with G143.

     

    I set my tools off of the tool setter. I use the OAL (over all length) for the tools in MasterCam. I use a spreadsheet to calculate the overall length from the tool setter value.

     

    Just curious, which post are you using? I was digging around in an old post that was here when I arrived which I do not use (I wrote mine using the Generic 5 axis post). In the old post is ppivotcomm post block that you might be able to add for a different G43/G143 that would change the gage lenght output.

     

    Such as

    pivot : 0.0000 # G43 Distance from tilt pivot point to gauge line

    pivot1 : 13.4571 #G143 Distance from tilt pivot point to gauge line

     

    Here is the rest of the post info:

     

    pt_shftmx : 0. #Offset tilt pivot point - mm

    pt_shftmy : 0. #Offset tilt pivot point - mm

    pt_shftmz : 0. #Offset tilt pivot point - mm

    pt_shftix : 0. #Offset tilt pivot point - inch

    pt_shftiy : 0. #Offset tilt pivot point - inch

    pt_shftiz : 0. #Offset tilt pivot point - inch

     

    fmt 2 pivot #Pivot length - rotary centre to gauge line

     

    ppivotcomm

    #Haas G143 only handles the tool length, post must handle the pivot distance calc

    #we're moving the code up by the pivot length then back fown in Z by that amount

     

    if fiveax_comp | rot_feed,

    [

    spaces$ = 0

    rc2 = t$

    gauge = rbuf(2,rc2)

    if fiveax_comp = 0, gauge = 0

    vtlng1z = pivot + gauge

    pbld, n$, pspc, scomm_str, "POSTED WITH ", *pivot, " PIVOT DISTANCE", scomm_end, e$

    pbld, n$, pspc, scomm_str, "POSTED WITH ", *gauge, " TOOL GAUGE LENGTH", scomm_end, e$

    #if tdef_fq_sw, pbld, n$, pspc, scomm_str, "GAUGE LENGTH FROM USER INPUT", scomm_end, e$

    #else, pbld, n$, pspc, scomm_str, "GAUGE LENGTH FROM TOOL DEFINITION", scomm_end, e$

    #if fiveax_comp, pbld, n$, pspc, scomm_str, "VALUES USED FOR 5-AXIS LENGTH COMP", scomm_end, e$

    #if rot_feed, pbld, n$, pspc, scomm_str, "VALUES USED FOR 5-AXIS FEEDRATE CALCULATIONS", scomm_end, e$

     

     

     

  2. Hmm... that is interesting. I run one also, but I program everything G43 in 3 axis or as gage length programming. I normally do not use G143 because of all the restrictions (more trouble that it is worth). I fixed my post to output all of the Haas 5 axis G-Code canned cycles (i.e. G161, G162, G163, G164, G165, G 166, G169). I'm not sure if the 5 axis G-code canned cycles are compatible with G143.

     

    Sorry, I know that wasn't much help.

  3. This is what i did; just add *n$ in the ptoolcomm post block.

     

    ptoolcomm # Comments from tool library

    spaces$ = 0

    strtool$=ucase(strtool$)

    if strtool$<>snull, pspc1, *n$, "(", *strtool$, ")", e$ <------------ (add *n$ in this line.)

    else, pspc1, "(", "DEFINE TOOL NAMES", ")", e$

    spaces$ = sav_spc

     

    Hope that helps.

  4. So... what you are saying is that it is now longer available for download? I thought I had downloaded a MPGen5x post a few years ago from Mastercams site(?), just can't find it now. Just trying to save some time by downloading instead of playing phone tag with my reseller.

  5. Where can I download MPGen5x for MasterCam X5 or do I have to contact my reseller?

     

    I have been using the "Sample" 5x post from V9 5axis tutorials. I have been able to use this post for numerous 5 axis combinations, so modifing a 5x post is not an issue for me. I have had to add funtions and logic to the "Sample" 5x post to get it to work under different machine conditions. X2 was the last version that I updated and used the "Sample" post with. Due to IT Security we missed X3 and X4. Now I would just like to start fresh with the most current MPGen5x logic with X5.

     

    Thanks in advance.

    Mike

  6. James, Chris, and Thad, your letters are very well witten.

     

    quote:

    The truth is that nowadays not many youngsters want to be machinist/cnc programmer/mold designer/mold maker.

    That is so true. The high school that I attended (back when we carved wheels in stone) suffered the same problem. The class size and funding decreased. They changed the course title from "Metals" to Pre-engineering. What a difference a title makes. Soon after the title change, enrollment increased and more money became available.

     

     

    Mike

  7. MPMASTER is a great starting point and I agree that if you don't like MPMASTER's output, then fix it to your liking. That's what I have done.

     

    I have modified my posts to output code in order and not having redundant code. Part of the reason I do it that way stems from the "old" days before Mastercam. I was taught about the "grammer" of code writing and the limitations of machine memory (some habits are good). Placing code in order also made it easier to find mistakes when proofing a program back then.

  8. quote:

    those are metric hours since he's from canada.
    biggrin.gif

    Del, that's some funny stuff.

    quote:

    When it comes to $9/hr that's what I was paid when I started...

    Everyone has to start somewhere. When I started in this business I was making minimum wage at the time. I got my first pay increase when they raised the minimum wage.

    quote:

    ...did I work any less hard this year then the years before?

    It's not about working harder than the years before, it's about working smarter than the years before.

     

    [ 07-14-2009, 09:51 PM: Message edited by: mgsanchez ]

  9. Here is John Paris' peck tapping (Thanks John!) with a slight modification for a Haas machine.

     

    This will output "G84", "Z" and "R" on each line.

     

    Sorry, I'm not at work so I can't post the output.

     

    code:

    #-------------------------------------------------------------------------

    # ADDED FORMATS FOR PECK TAPPING CYCLE

    fmt 4 count # timing counter

    fmt 4 peck_cnt #remaining no. of pecks

    fmt 4 numpeck # No. of pecks

    fmt 4 pass # pass counter use to calculate depths

    fmt Z 2 sub_depth #subsequent depths

    fmt Z 2 calc_depth # The total caculated cutting depth

    fmt Z 2 calc_peck # the calculated peck amount

    fmt Z 2 strt_depth # the first tap depth

    fmt Z 2 initial_calc # calculate the initial depth cut

    fmt 3 stepeck #Inital step peck down increment from top of stock

     

    #------------------------------------------------------------------------

    pdrlcst$ #Custom drill cycles 8 - 19 (user option)

     

    if drillcyc$ = 13,

    [

    numpeck = peck2$,

    stepeck = peck1$,

    if stepeck = 0,

    [

    peck_cnt = numpeck

    initial_calc = (depth$ - tosz$) / peck_cnt

    strt_depth = (tosz$ + initial_calc)

    calc_depth = (depth$ - tosz$)

    calc_peck = calc_depth / numpeck

    "(PECK TAPPING CYCLE)", e$

    pcan1, pbld, n$, *sgdrlref, *sg84, pdrlxy, *strt_depth, pcout, prdrlout, *feed, strcantext, e$

    count = peck_cnt - 1

    ]

    else,

    [

    peck_cnt = numpeck

    strt_depth = (tosz$ + stepeck)

    calc_depth = (depth$ - (tosz$ + stepeck))

    calc_peck = calc_depth / numpeck

    "(PECK TAPPING CYCLE)", e$

    pcan1, pbld, n$, *sgdrlref, *sg84, pdrlxy, *strt_depth, pcout, prdrlout, *feed, strcantext, e$

    count = peck_cnt

    ]

    pass = 1

    WHILE count > 1,

    [

    sub_depth = strt_depth + (calc_peck * pass)

    pbld, n$, *sg84, *sub_depth, *refht_a, e$

    pass = pass + 1

    count = count - 1

    ]

    pbld, n$, sg84, pfzout, *refht_a, e$

    pcom_movea

    ]

     

     

    pdrlcst_2$ #Custom drill cycles 8 - 19, additional points (user option)

     

    if drillcyc$ = 13,

    [

    numpeck = peck2$,

    stepeck = peck1$,

    if stepeck = 0,

    [

    peck_cnt = numpeck

    initial_calc = (depth$ - tosz$) / peck_cnt

    strt_depth = (tosz$ + initial_calc)

    calc_depth = (depth$ - tosz$)

    calc_peck = calc_depth / numpeck

    "(PECK TAPPING CYCLE)", e$

    pcan1, pbld, n$, *sgdrlref, *sg84, pdrlxy, pfxout, pfyout, pcout, *strt_depth, *prdrlout, *refht_a, *feed, strcantext, e$

    count = peck_cnt - 1

    ]

    else,

    [

    peck_cnt = numpeck

    strt_depth = (tosz$ + stepeck)

    calc_depth = (depth$ - (tosz$ + stepeck))

    calc_peck = calc_depth / numpeck

    "(PECK TAPPING CYCLE)", e$

    pcan1, pbld, n$, *sgdrlref, *sg84, pdrlxy, pfxout, pfyout, pcout, *strt_depth, *prdrlout, *refht_a, *feed, strcantext, e$

    count = peck_cnt

    ]

    pass = 1

    WHILE count > 1,

    [

    sub_depth = strt_depth + (calc_peck * pass)

    pbld, n$, *sg84, *sub_depth, *refht_a, e$

    pass = pass + 1

    count = count - 1

    ]

    pbld, n$, sg84, pfzout, *refht_a, e$

    pcom_movea

    ]

     

    #---------------------------------------------------------------------------------

    [drill cycle 14]

    1. "Peck Tap cycle"

    2. ""

    3. ""

    4. ""

    5. ""

    6. ""

    7. "INC. 1st Step from TOS"

    8. "# of PECKS"

    9. ""

    10. ""

    11. ""

    #---------------------------------------------------------------------------------

     

    [ 05-29-2009, 08:34 PM: Message edited by: mgsanchez ]

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