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:

MIL-TFP-41

Verified Members
  • Posts

    1,239
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by MIL-TFP-41

  1. 25+ years ago in my 3 axis days I  would of sided with the operator, or at least sided with the people saying it does not make any difference. Now, with functions like TWP and TCPC being the norm rather than the outlier I would strongly insist people to adjust  wear offsets and leave the commons alone.

    On our Toyoda bridge mill with a right angle head the macros write values to the common offsets depending on the orientation of the head. Not sure why Toyoda/Wele decided on that method, but it is effective. It did throw the operator for a loop, he came from a large 3 axis vertical and had the using common offsets method so long it was etched into muscle memory.

     

    • Like 4
  2. On 2/17/2024 at 9:10 AM, Colin Gilchrist said:

    If you do this > you'll want to alert the Fire Department beforehand, and DO NOT do this at night. Ask me how I know. :ph34r:Something, something, 2nd shift, something, something, bored machinists, I think you get the picture.

    One of the things I though about doing was collect a hefty bag full of the chips, then somehow hike up a mountain that overlooks our town, (its 2500 vertical ft up to the top) and light a campfire, dump the chips, and run. I imagine it would light up half the valley. Doing it at night in the snow would complicate the effort, but minimize the fire danger.

    It would be a bitch of a hike in the summer during the day. Winter at night....gotta be more devoted to pyro than I am to do this.

  3. As stated before, it will destroy any water soluble coolant, causing it to separate and become worthless. Plan on draining your tank & putting new coolant in every couple of weeks. There are some makes of coolant which supposedly tolerates the magnesium better, but I have yet to try. We have a reoccurring job once a year that runs for about a month, we add in a couple of days of cleaning and a new drum of coolant into the cost of the job. You gotta get all the magnesium out of the machine or you will be fighting coolant issues till you do.

    The fire hazard is a real thing. One of the few jobs in the shop where we do not run lights out.

    • Like 5
  4. On 1/24/2024 at 10:36 AM, riverhunter said:

    Bringing this old thread back to life.  My old handle was @dforsythe and i no longer have that email to retrieve it.  so I'm now @riverhunter some 15 years later and am now back on mastercam so I'm trying to duplicate something i did back in 2009.  looks like @Rob @ Target Machinehasnt been around lately so ill ask the rest of the group.

     

    the code below works great for getting the code D#517.  my question is how do i do this for  tlngno$ so i can get G43 H#517.  the tlngno$ is buirred in the ptlchg_com so im not sure how to approch it.

     

    #pbld, n$, "G43", *tlngno$, pfzout, scoolant, e$
    pbld, n$, "G43", "H#517", pfzout, scoolant, e$  This forced it, but throws an exception error.  

     

     

    Try this:

    pbld, n$, "G43", "H", no_spc$, 35, no_spc$, "517", pfzout, e$

    35 is the ascii code for "#". I know newer versions allow the use of the # sign, mine have been updated from versions that did not allow it. It works, so I never bothered changing.

    • Like 1
  5. On 12/26/2023 at 10:15 AM, Kyle F said:

    For those keeping up with the matsuura saga at my shop,.... while awaiting our precious brand new MAM my boss picked up a very lightly used MX-330 PC10

    came with 6x 5th axis risers + mini 4 part pyramid dovetail fixtures which is a nice little bonus lol.

    We are storing it until we get a few machines moved and another proper foundation poured. Should be getting install + training around late jan/early feb if I had to guess.

     

     

    Nice machine. I've got a few hours on those.

    • Thanks 1
    • Like 1
  6. A large percentage of our parts require our CMM's to duplicate what the customer CMM's read. This presents a huge challenge to on machine inspection, Sure, it might be possible, but the cost would be enormous.  It would require multiple probe heads with multiple configurations of styli. I have yet to see a machine tool that can change styli...so figure on some of our parts 6 or more different probe heads. Then say you have a couple of different operations on the part you are working on, it would be impossible to measure features that workholding would restrict access to. So then you would have to come up with a whole separate operation just for inspection, fixture the part like you would on a CMM so you can access all the features from both operations.

    All the time you are doing that you are losing the main thing a spindle is supposed to be doing, making chips. The cost of that downtime would pay for another CMM, nevermind the hardware cost.

    Now for doing a quick check, something like measuring a bore or position on a first article part, yes, we will do on machine.

    • Like 1
  7. 23 hours ago, JParis said:

    This doesn't answer your question, sorry about that, it does though prompt a question....

    Why use iges?

    It's technically not outdated but it is an old process that is fraught with issues and limitations, I'm just curious.

    Like I said, we try to use .stp, but the cmm software converts those into surfaces and sometimes flips the normals on those models. At least with an iguess file one can open it in mastercam & see if the normals are flipped.  Next step is to try their parasolid translator & see if that gives us better results.

  8. Ok, this should not be tough, but it is giving me fits. When I save the attached revolved solid as an iges it flips the normals on half the surfaces. Plays hell with a cmm program that is looking for the top of a surface.

    We try as a .stp file also, we get the same result in the cmm program (it apparently converts the solid into surfaces)

    What really sucks is you can fix all the surfaces in the .iges file, resave as an iges, and it will still open up bad. I suspect this is because of the untrimmed surfaces that are hidden.

    Just wondering if anyone else has seen this behavior ever...and if there is a fix.

    test.mcam

  9. Regard the CAT40 & BT40, on that machine with the tool matrix, it does make a difference. The BT racks are different from the CAT racks. If it was a chain style all that would be different would be the claws or fingers on the tool change arm.  I have priced out changing the matrix racks from CAT to BT...and the price per rack is steep. That being said, on a new machine, Matsuura has always changed them out for us at no charge. (Note, we are primarily a BT shop & have picked up a few used CAT Matsuura's over the years. Every time I price out changing over a matrix from CAT to BT, the sticker shock stops me)

    As far as holders, see above about getting a voucher from Kennametal. Theirs is by far the easiest to get and use. ER holders and "standard" stuff from them are a very good deal with the voucher. And seriously look into heat shrink. Once again, with the Kennametal stuff, the heat shrink are very reasonable. For the shrinking unit, look at the Haas offering (or Mari-Tool). A very economical way to get your feet wet.

    I am a fan of Lyndex SK collets for more picky stuff. Pioneer also has them (they call it an SX collet, they are the same thing)

    • Like 3
  10. This is still an unresolved bug & is easy to recreate if anyone wants to try.

    Open a control definition that you are already using & add a post (something like MPFAN will work fine)

    Save your control definition & close.

    Now, once again open your control definition. Delete the post you added. Save & close.

    Open control definition again...and the post you deleted is still there.

     

    • Like 1
  11. I believe you have to play with these settings:

     

    #Primary axis angle description (in machine base terms)
    #With nutating (mtype 3-5) the nutating axis must be the XY plane
    rotaxis1$ = vecx  #Zero
    rotdir1$  = vecy  #Direction

    #Secondary axis angle description (in machine base terms)
    #With nutating (mtype 3-5) the nutating axis and this plane normal
    #are aligned to calculate the secondary angle
    rotaxis2$ = vecz  #Zero
    rotdir2$  = vecx  #Direction

     

    The above settings are for a table that tilts around Y. Depending on which way it tilts you will have to adjust.

  12. I am seeing this in 2024 also (Update 2). Open machine definition manager from the ribbon bar, then open control def from the machine def manager. Delete the unwanted post. save the control def, close that window. Open control def again, the post I supposedly deleted is still listed.

    I get the same result if I open the control def directly from the ribbon bar,

    The file location for the old post doesn't even exist anymore, so who knows what or where it is coming up with the one I am trying to delete.

  13. 26 minutes ago, gcode said:

    Could it have something to do with the origin of the tool holder model

     

    For the fun of it I tried creating a new holder in 2024. (Toolpath parameters/holder page/new holder) Result was the same as the screenshot I posted. Really strange the sample file I posted is behaving differently for you.

    12 minutes ago, Span said:

    As a quick work around save the profile to a level and link, it will then verify correctly.

     

    That works nicely, thank you.

  14. 4 minutes ago, gcode said:

    The 2024 tool was acting weird so I opened the Too, Manager and elected Edit Tool Assembly

    Everything looked OK and the 2024 tool functioned correctly

    Did you change the projection or anything? I tried doing what you described and get the same crash.

    Were you able to get the 2023 tools to work?

  15. We do this all the time. Productivity+ writes the "X" error to #140. Knowing that, you can now populate whatever Z axis offset you want.

    Example - #5203 = #140 would write the X axis error to the Z axis common offset

    The above would work on a fanuc controller.

     

    All of the cycle outputs are listed in the Productivity+ manual.

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