You are not logged in.
Pages: 1
Hi Everyone,
We will be getting into the simulation next year after we take the class. I feel from the little I know about all this that we have a lot of planning to do for all this. We are a pretty large company and use Pro-e. We also have Walters TDM for tooling.
My biggest question is how to handle tooling. We will need accurate 3D models of the tools, right? How is everyone doing this now?
Are you using Walters or what to manage tooling? How are you going about managing, constructing the tools in software.? Or what is the suggested way to do handle all this? How detailed is the tooling? Any and all other related info that I am not aware of is welcome.
Thank you,
Jeff Voegele
Solar Turbines Incorporated
Principal Manufacturing Engineer
Tel: 619 544-2820
Offline
We use Autotas and we generate complete assemblies from the cutterlists. Holders, stickout etc. It's great. Without it, most people would not take the time to build the complete assembly for collision checking.
First we use Oracle to read the data we need out of Autotas. Then we use custom perl routines to convert the data file into Vericut tool definitions. These are complete accurate assemblies.
Users can also save individual assemblies to a common directory. Ones they have customized. These are too complex for the standard conversion. Any cutterlist that references that tool in the future can pull in the customized definition of the tool.
When we installed Autotas we had a long range plan to do this. There were "standard" fields and user defined fields. About 1/2 of what you need for the shop and Vericut are in the user defined fields. This is were custom mapping is needed.
You should be able to do something similar with TDM.
Watch out for "sloppy" data. Integrity of the data in the tool management system is critical.
Offline
Hi Jeff,
Not sure if you were aware that TDM/CGTech have partnered to create a direct interface from TDM to VERICUT. With the "TDM Interface" you access TDM from VERICUT's Tool Manager, thus replacing the need for a Tool Library file with a link to your TDM database. When VERICUT needs a tool, it comes directly out of TDM. --Gene
Offline
Pages: 1