Hi
I have been testing Creo 4.0 for suitability before the whole office switches over, as my role controls the whole process, If we can’t use it with the manufacturing, the design team don’t get it.
I have a couple of issues with the dumping of Vericut and the replacement with Module works, that is preventing the office from switching over.
Our process has tight QA procedures and accreditation that needs to be meet, and part of that is design verification with Vericut, where we run the simulation of the program and then full dimension check , and gouge tolerance calculation of the model in Vericut to verify that the program is correct to the design.
Module works can’t do that.
We do have the full license for Vericut 8.0 and can run it as a stand alone program, we now have more work to do as Creo now won’t put out the default files to start with.
Is there a way to out put the part as .DSN and the stock as .STK, if so we can work with a template to achieve what we need to do.
Maybe having the option to save part and stock files in these formats would help business like ours that still have to rely on Vericut.
Also, when running Module works, I can section the stock piece, but the part isn’t sectioned, this needs to be fixed.
and when saving the cut model as a part, and reusing it in the 2nd operation, ( a big plus for module works ), the next time I tried to simulate the 2nd operation, it locked up on Memory (98% usage). when saving the cut part, Creo needs to convert it into a PART format that isn’t so large for the memory to manage.
I see a lot of benefits in using Module works, but PTC needs to make an effort to support business that still rely on Vericut.
Save option for the required file formats will be a big help please…
Peter
The post CREO 4.0 F000 – vericut and Moduleworks appeared first on Statii News.
source http://news.statii.co.uk/creo-4-0-f000-vericut-and-moduleworks/
No comments:
Post a Comment