Tool libiary 7.2.1

MARTY · 2013-03-26 14:19:16

When You do multiply set ups. The tool list from opp#1 is carried to opp#2 and so on. So when you only have a few tools or all the tools are different. You have to delete or modify all existing tools from libiary for that particular opperation in project. it would be nice to have it not carry thruout project or be able to do a mass edit of tools ctl delete or somthing to hyighlight and delete multple tools.

MARTY · 2013-04-08 16:13:22

None else has a problem with this when doing multiple setups

paehv · 2013-04-10 12:25:12

You can specify a separate tool library for each setup.
With 7.2.1 you can also create a part or machine specific library by linking some tools from a master library file. This is the method we use and it works beautifully.

MARTY · 2013-04-15 17:17:07

We never cut same part allways new tools 10-20% are repeats on tools. I do use seperate tool opps libiary's for each set up. Problem is if I have 50 tools in one set up. It is carried to set up #2 automaticly so you have to go thru and delete all tools that do not apply to the opperation and plug in good ones to run. Now it does no harm to have them in there other than when there is a issue with a particular tool you have to go thru all tools to find the one to edit. 5 tools in a setup is nice easy to find But we have 70 tools somtime per opperation 300 per project.

paehv · 2013-04-16 06:50:38

Do not understand the problem. Why delete tools that aren't used in a setup?
There are a few options on how to use libraries and perhaps this helps you to get what works for you.

Option 1: a Library per part/setup :cry:
for every job a separate library is created
+ ?
- nightmare for maintenance. (what happens if a common tool used in a lot of jobs gets modified or replaced for some reason)

Option 2: One master library per machine (or holding system)
All vericut projects for this machine/holding system refer to this library
+ easy to maintain, tool is defined only in this library.
- this requires fixed tool numbers

Option 3: Linking to Master library
definition of all tools for all machines/holding systems
You can use a "Linked" library per machine/holding system a library with appropriate tools linked from master
You can use a "Linked" library per job/part number/setup a library with used tools linked from master
+ easy to maintain
+ tool numbers can be changed without affecting the master tool.
+ very flexible, you can have all tools from a machine, or get only those tools needed for the job.
- ? have not found any disadvantages so fare.

I'm been using Vericut since 1996 (V4.3) and I have always hated the 1st option. During the introduction of a new part on the shop floor you will end up adding/changing tools in your library and -especially if there's more than one programmer- this tends to get mistakes.

Until Vericut V7 we have always used option 2. This way the definition/maintenance of tools can easily be supervised. (in the past we had 3 full time programmers -that maintained tools- and 23 contract programmers with varying skills -you don't want everyone to define all sorts of tools-)

With Vericut V7 the linked tools were introduced and this is by far the best and most flexible way to deal with tools.
In our current environment we have:

* one master library (containing about 3000 tools)
* a library for each machine containing linked tools applicable for that machine
* the option to create a job specific vericut library -with linked tools- directly from NX CAM

VERICUT Users' Forum

#1 2013-03-26 14:19:16

Tool libiary 7.2.1

#2 2013-04-08 16:13:22

Re: Tool libiary 7.2.1

#3 2013-04-10 12:25:12

Re: Tool libiary 7.2.1

#4 2013-04-15 17:17:07

Re: Tool libiary 7.2.1

#5 2013-04-16 06:50:38

Re: Tool libiary 7.2.1

Board footer