Skip to main content
R
Ramesh1-Visitor
1-Visitor
August 12, 2014
Question

Controlling Skeleton with Simplified Representation

  • August 12, 2014
  • 2 replies
  • 3902 views

Hi,

I created a top Level Machine assy which has more number of Optional sub assemblies, so I can create "N" number of different machine configurations with combination of these optional sub assemblies. I created skeleton also for controlling optional subassemblies placement based on the machine configuration.

Now i am creating simplified representations based on machine configurations, just to show that combination's optional sub assemblies alone.

I want to change the skeleton input values based on the current simplified representation to correct the sub assemblies placements. so i don't have to key in the skeleton input values whenever i switch to different simplified rep

Please any one can explain me, How can i control the skeleton input values with Simplified rep.?


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

2 replies

G
gkoch1-Visitor
1-Visitor
August 18, 2014

Hello Ramesh,

if the component placement changes based on the subset of components, then this looks more like a task for family tables than represenations. Representations are allowing to switch components on/off. However, if you want to change their placement, you need to modify dimensions/features (of skeleton, assembly, etc...) and hence it is better to use family tables or Pro/PROGRAM functionality.

Gunter

R
Ramesh1-VisitorAuthor
1-Visitor
August 22, 2014

Hi Gunter,

Could you please explain me how to use Pro/Program for scenario like mine...

Ramesh

D
dschenken1-Visitor
1-Visitor
August 23, 2014

Until Gunter can get back, have a read through of the documentation about Pro/Program.

It is like a text version of the Model Tree with some assignment.

There are no loops. There are conditional statements, which is what makes it more capable than Family tables.

You can start here: http://help.ptc.com/creo_hc/creo30_pma_hc/usascii/index.html#page/pma/fundamentals/About_Pro_PROGRAM.html

B
BillRyan16-Pearl
16-Pearl
August 26, 2014

Is it possible to make your skeleton a family table? If so and your variants are not unmanageable then the following strategy might work. (Note: this requires gathering assemblies(sub-assemblies) containing the systems as you will be overloading the top level assembly)

1) Top level assembly which will contain the simplified reps

2) Assemble all variants of skeleton instances into top assembly.

3) Assemble the applicable gathering assembly to the appropriate skeletons.

Notes:

  1. Since this model will have multiple skeletons and subassemblies, I recommend adding notes to the feature name column to define the conditions of use. This will make managing the reps easier.
  2. Do not use the simplfied rep to "substitute" the skeleton instance. (Use master rep of each skeleton in the model tree. The following areas have issues with this method: Creo model tree, Windchill structure tab, Windchill publisher, Creo View files, and I'm sure any visualization tool.) The reliable method is to include all the instances individually in the model tree!

4) Create simplfied reps as needed.

You don't have to have much programming knowledge to use this approach and it is reliable. In our case, we try to only do this if the variants are under 20. We had 60 skeletons in an assemlby and performance starting being an issue.

Terms & ConditionsAccessibility statement