Skip to main content
O
oflou1-Visitor
1-Visitor
February 21, 2017
Question

Family Table and aassembly configuration

  • February 21, 2017
  • 2 replies
  • 9152 views

Hello,

I have a new question and i don't see it on the others post ...

In an assembly model, when i will place a part on an another part i need 3 restrictions of placement. These 3 restrictions make a placement game.

I have also the possibility to create some others placements games.

My Question :

Is it possible to to create many instance in a familly table with the placements games ??

Thanks and have a nice day

Olivier

2 replies

B
BrianMartin13-Aquamarine
13-Aquamarine
February 24, 2017

Hi Oliver...

If I understand your question correctly, no, the family table is not the best way to achieve this. You can save sets of assembly constraints though and toggle which one is active at any given time. I don't know how to do this toggling via family table, however.

You can have different placement schemes, though. You can even save different interface definitions and recall them or leverage them for "automatic" assembly options.

If you have an example or can explain a bit further, we might be able to give a better answer.

Thank you!

-Brian

M
MartinHanak24-Ruby III
24-Ruby III
February 25, 2017

Hi,

in assembly you can define several constraint sets for specific component (only one of them is enabled). Creo creates special parameter named PTC_CONSTRAINT_SET for this component. In assembly you can create family table and add this component parameter into it. Then you can set parameter value differently for different instances.

See

http://support.ptc.com/help/creo/creo_pma/usascii/#page/assembly%2Fasm%2Fasm_four_sub%2FAbout_the_PTC_CONSTRAINT_SET_Parameter.html

MH

    B
    BrianMartin13-Aquamarine
    13-Aquamarine
    February 27, 2017

    Ah great catch, Martin. I forgot this existed - I never use family tables to control constraint sets but it's a great tool for the few times it's necessary!

    Thanks for the excellent addition!

    Terms & ConditionsCookie settingsAccessibility statement