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:

NoobiusMaximus

Members
  • Posts

    4
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

NoobiusMaximus's Achievements

Newbie

Newbie (1/14)

  • One Year In
  • Week One Done
  • One Month Later

Recent Badges

0

Reputation

  1. My only concern with ignoring the TMS software is that the alternative seems to be managing two locations for tooling models. One in Zoller to ensure tools are set properly, and the other in Mcam for programming use and to ensure Vericut is correct.
  2. Is the main issue in building tools or in building assemblies? Are all tools built manually or can CAD models be imported for things like face mills? I assume you are taking tools built in the Zoller software and importing into Mastercam. How easy or difficult is that process?
  3. I've searched the forums but I didn't find a whole lot of recent information on the topic. We have a Zoller presetter and by the looks of it we should be able to build a database that can interface with mastercam for tool libraries. Workflow would look something like build tool in Zoller, then import into mcam. The tool guy would have to hit a specified tolerance when setting stickouts and such on the tool when it's built. We haven't upgraded software packages from Zoller yet because we want to make sure it will meet all our needs before we spend the extra $$ on the bronze software package. It feels like the company was a little too eager to throw money at our tooling issue right away without full research and planning, but the shop culture is right to get the tooling monster tackled properly. For the guys who run Zoller stuff, how do you handle a tooling database? Does the Zoller tooling information handle feeds and speeds as well as the geometry? The end goal is to have a single database that houses all the tooling info including location, geometry, default feeds and speeds, coolant info, etc. Ideally, that database would talk to Mcam and our matrix toolcrib so programmers are all working off the same data, and it'll pop drawers in the tool crib for our tooling guy.
  4. I would like to import a tool from a tool library, and replace a tool in use by the current program. For example, A program is built using a 1/4" endmill and for whatever reason I want to change it to a 3/8". Is there a way I can import the new tool and replace the old tool in all toolpaths it's used instead of individually changing it per toolpath?

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