cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

The PTC Community email address has changed to community-mailer@ptc.com. Learn more.

Generic information in the model tree

Generic information in the model tree

Hello Community

In the model tree it is possible to indentify family table member by the generic name between smaller+bigger signs.

Like "member_name<generic_name.prt>"

 

Now we would like to have similar information about the generic name, if we have the generic itself assembled.

in this way we can easily identify, whether a normal part or a generic part is assembled.

e.g. "generic_name<generic_name.prt>".

 

Thanks in advanced for your votes!

 

7 Comments
BenLoosli
23-Emerald II

You should NEVER assembly a generic into an assembly!

There is a ModelCheck setting for this check.

Roman-Gnoth
3-Visitor

Hello BenLoosli,

thanks for this hint. I know this. We do not use modelcheck and unfortunately our reality is different than the theory. Therefore I would like to see these situations in the model tree.

Best, Roman

BenLoosli
23-Emerald II

My point is if the software coders say to not do something, even if the code allows it, why risk possible corruption of parts or the coders closing the 'loop hole' at some future release?

PTC has repeatedly stated that the generic model should not be used in assemblies. If you want the generic-sized model make that your first instance and then add the other instances with their changes.

 

Just because something can be done, doesn't mean it should be done!

DomenicLaritz
16-Pearl

@BenLoosli, your statement that generics should never be used only applies to standard parts.
But e.g. for bent sheet metal parts it is usually the case that the instance represents the developed state and then of course the Generic (bent state) must be used in assemblies.

HamsterNL
18-Opal
@BenLoosli  wrote:

You should NEVER assembly a generic into an assembly!


That's the general rule...but there are exceptions 🙂

 

In our case, we have one model where the generic has been placed in the assembly, because we use PRO/PROGRAM drive the INPUT PARAMETERS for that Family Table (and as you might know, you can only drive the generic, not the instances).

Roman-Gnoth
3-Visitor

Thanks for the answers and comments.

But....Please vote for my request 😉

avinashmahajan
2-Guest

for complex assemblies generic is must, it gives flexibility to handle/check different versions of product in assembly itself, also lot of time is saved in assembly by putting generic parts (my opinion is related to switch gear industry and it is very usefull for us)