hai...
I have to convert a V4 sheetmetal model to V5.
my question is....
Is there any possibiity to get sheetmetal features in the specification tree while converting as spec?
thanks in advance
Maayan
Daniel Pavon
RE: migration v4 sheetmetal to v5
July 22, 2010 08:48 AM
(in response to Ashok kumar SV)
Hi Maayan!
This post is old and probably you found the solution, but my company is going through this "Migration V4-V5" right now.
We had a big support from DS to create the methods and ways of working during the migration process, and the answer to your question is "NO".
In fact, their recommendation is: "migrate all as result". But sometimes you want to keep the reference elements in the tree, so don't run the command "Delete Useless Elements" after migrating as spec.
Even if the original V4 was designed in sheet metal V4, V5 doesn't recognize the features, nor creates equivalent V5 features.
When you migrate as spec, the tree will be full of pads, pockets, ribs and boolean operations. And probably deactivated filets and chamfers.
As you can imagine, editing this tree is a nightmare, so a redesign is much easier in case of modification.
In our case, we chose to migrate to V5 because of VPM. Selecting only V5 files in VPM can save a lot of time and avoid some problems in the future. Besides, not having V4 files is a good way to kill Catia V4, even if the V5 is not as good as a redesign.
Daniel Pavon
This post is old and probably you found the solution, but my company is going through this "Migration V4-V5" right now.
We had a big support from DS to create the methods and ways of working during the migration process, and the answer to your question is "NO".
In fact, their recommendation is: "migrate all as result". But sometimes you want to keep the reference elements in the tree, so don't run the command "Delete Useless Elements" after migrating as spec.
Even if the original V4 was designed in sheet metal V4, V5 doesn't recognize the features, nor creates equivalent V5 features.
When you migrate as spec, the tree will be full of pads, pockets, ribs and boolean operations. And probably deactivated filets and chamfers.
As you can imagine, editing this tree is a nightmare, so a redesign is much easier in case of modification.
In our case, we chose to migrate to V5 because of VPM. Selecting only V5 files in VPM can save a lot of time and avoid some problems in the future. Besides, not having V4 files is a good way to kill Catia V4, even if the V5 is not as good as a redesign.
Daniel Pavon