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:

Leaderboard

Popular Content

Showing content with the highest reputation on 02/10/2023 in all areas

  1. Something like: DWO macro 4th axis Corresponding Youtube: To post out a custom gcode, you need to use: *tox$, *toy$, *toz$ or: *tox4$, *toy4$, *toz4$ For the macro you do need to know the rotation point. I am working on a similar project but i first have to make the fixtures for that machine.
    2 points
  2. He is correct he can do it that way, but on the machine he will need a new workoffset for each index angle that is the same distance from that center of rotation to the shift point he is using. He has 100 different angles he will need 100 different work offsets. In Mastercam every unique C-T Plane will also need that same work offset. Can't help the ignorant and proud ones that will not stop long enough to see the error in their ways. Now with G68.2 on the machine and a properly configured post that output the shifted distance from COR to each T-C Plane then he coudl get away with one workoffset, but is far and few between that I have seen a 4 Axis machine configured on a Fanuc Control to support it. Siemens will be CYCLE800 and on Heidnehain it will be TPLANE then OKUMA use CALLOO88 again if that has been setup correctly and configured for the machine and the post to correctly support that output.
    1 point
  3. Watch it people are going to start calling you a mean person for asking for such a thing.
    0 points
  4. 0 points
  5. No update. I pretty much gave up. We have a few production parts that run on the machine and we don't really iterate on process improvement like we could/ should. It is just too much of a pain and I'm tired of fighting the uphill battle. It never got fixed so we just hand edit the programs if there is a change. Usually we will isolate the toolpath that changed and cut and paste it into the existing program so there is less to prove out. It is really pathetic I know. On the mills we will iterate a program for process improvement every cycle until it is dialed. We will constantly repost to test new tool technology and offerings, etc... Not with the Mori, waaay too much work. Were probably getting 60% of what we could out of that machine and it pretty much boils down to the post issues and drama it causes.
    0 points

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