Different confugiration of Design Table in Differnt CATPorduct

[justs]

I have a CATPart with 3 configuration in Design Table.
I want to use this Part in 2 differt Porducts with differnt configuration. If i change configuration in 1 product it makes change in all the files.
How to do this?

Tahnks

 

[Azrael]

Why don't you resolve the part into three different parts?

 

[justs]

The Part is Rubber hose. In assembly it is fixed to a nippel, so i have to show the hose as deformed in the assembly. While releasing the drawing for production there should be no deformation. should have same part number both in Part dwg and Assy Dwg.
Is there any ohther way to do this???????

 

[catiajim]

Nope. You will need to use "bogus" part numbers, or some other way to differentiate the files. One file will have the undeformed shape, the other will have the deformed shape. The undeformed shape will not feed the Product, and the deformed one will.

 

[Runz]

Other cad packages such as Pro/E allow these configurations to be created and stored within the assy file and not affect the part file.

Hopefully this is something that Catia is looking to incorporate in the future. It would definitely to beneficial for springs!

 

[itsmyjob]

Runz... Did you ask Dassault about that ? What was the answer ?

Eric N.
indocti discant et ament meminisse periti ​

 

[catiajim]

Don't hold your breath.

The only thing that DS currently supports is Flexible Sub-Assemblies, where the components within a sub-assembly are in different positions in one assembly than they are in another. And that isn't supported if you are in VPM or LCA. I don't hold much help of them ever supporting flexible parts.

 

[DBezaire]

Runz - how would Pro/E handle 30 instances of these parts?

 

[Runz]

DBezaire - It should handle 30 instances with no trouble (And all 30 instances could be different).

I've seen assemblies with the same spring model (10 instances) placed into an assembly, but at different installed length. The flexible model info is stored within the assembly model, but still references the original spring model. If the original spring od should change, the instances update.

Here is a link to help you better understand this functionality.

This is a very useful and powerful tool.

http://www.ptc.com/appserver/wcms/standards/textmultitextimg.jsp?im_dbkey=13764&icg_dbkey=382

 

[PeterGuy]

DS could do something quite easily if assemblies remembered which, of any number of alternate representations was active on a particular instance of a part. Where as what it actually does is default to the default representation on opening.

 

[solid7]

It can also cause some terrible problems if any of the configurations fail to update properly.

-----------------------------------------------------------
Catia Design|Catia Design News|Catia V5 blog

 

[Runz]

Which is true about anything that fails to update properly.

Its a powerful and very useful tool and something that would be very beneficial in all cad systems, including Catia. The purpose of the thread was to state that other platforms are doing this successfully! Don't bash it because Catia doesn't have the functionality.

I've used it and seen it used many times with no issues!

 

[solid7]

I'm not bashing it because Catia doesn't have it. On the contrary, it may have been a tongue-in-cheek suggestion as to why it's NOT included...

Of course, the real reason it's probably not included, is because nobody has written a "business case". (rolling my eyes)

-----------------------------------------------------------
Catia Design|Catia Design News|Catia V5 blog

 

[DBezaire]

Thanks Runz - that would be useful in Catia.

Regards,
Derek