Skip to main content
4-Participant
July 18, 2023
Question

Family Table Assembly: Generic of FT PART is not replaced by the called instance

  • July 18, 2023
  • 4 replies
  • 6461 views

To make a Family of an Assembly, I set up a Family Table Assembly. In this assembly, most parts are used just as they are. This reprents no issues.  Some parts are not used in one instance and are used the another instance. This too represents no issues. The Family Table of the Assembly presents a "Y" for one instance and a "N" for the other and this works fine.

 

One part in the Assy FT Generic is a FT part itself. In the Assy FT Generic the Part FT Generic is called. Again, so far, no problem.

 

In the Assy FT table, one Generic and two instances are defined. The Assy Generic calls the Part Generic. Instance 1 of the Assy FT calls part instance 1 of the Part FT and, you've guessed it, Instance 2 of the Assy FT calls part instance 2 of the Part FT Verfiying only brings angel songs and praise upon the creator (that would be me)

 

However, when opening the Assy FT instance 1, not instance 1 of the Part FT is loaded but the generic of the Part FT...... and the same for Assy FT instance 2... in this, Part FT Generic is loaded instead of Instance 1 of the Part FT.

 

So:

What is called and should:happen:

Assy FT Generic:                              Assy FT Inst.1                 Assy FT Inst 2

Part 1                                                   Part 1                               Part 1

Part 2                                                   Part 2                              Part 2

Part 3                                                   Part 3                              Part 3

Part 4                                                   Part 4                               -

Part 5                                                   Part 5                               Part 5

Part 6 FT Generic                              Part 6 FT Inst.1               Part 6 FT Inst.2

 

 

What actualy happens

Assy FT Generic:                               Assy FT Inst.1                Assy FT Inst 2

Part 1                                                   Part 1                               Part 1

Part 2                                                   Part 2                              Part 2

Part 3                                                   Part 3                              Part 3

Part 4                                                   Part 4                               -

Part 5                                                   Part 5                               Part 5

Part 6 FT Generic                              Part 6 FT Generic          Part 6 FT Generic

 

I have tried all kinds of different methods of including the instances in the FT both for the part as for the assy, but to no avail.I checked on possible variables within Creo (as in config.pro settings), but to no avail as well....

 

Can anyone provide me a clue as where I might be going wrong......

 

(CREO 8.0.8.0)

 

 

 

 

 

 

 

 

4 replies

RPN
18-Opal
July 18, 2023

Did you try to specify the name of an instance using the full path family_table_instance_name<generic_name>.PRT

like

 

BOLT-M10<BOLT>.PRT

 

Extension, I’m not sure, but may required. 

4-Participant
July 18, 2023

Dear RPN,

 

Thank you ever so much for your input. Appreciated !!!

 

The solution you prevent is not allowed by CREO (8.0.8.0 btw) in the Family Table Dialog Box. I did the input of the instance manually:

 

INSTANCE1

INSTANCE1.PRT

INSTANCE1<GENERIC>.PRT

 

The first and second inputs are allowed by Creo and provide no different result from eachother (both fail to place INSTANCE.PRT but do place GENERIC.PRT of the Part FT)

 

The third, as you provide in your feedback, is not allowed to be entered by Creo, returning the Error dialog box:

"You have either entered an invalid text string or a numberic velue for this cell. Please return to the cell and enter the date appopriately for the current column" <OK>

In the Family Table dialog box, I also used the "TOOLS>REPLACE USING>FAMILY MEMBER...". menu option. Choosing this, the Family Tree dialog box pops up and lets you choose the generic or appropriate instance. Of course I choose the correct instance for that Instance of the FT Assy. Creo inputs the name

 

NOT as "instance1.prt",

NOT as "instance1<generic>.prt"

but as "instance1"

 

Then saving the generic of the Assy with the FT, and opening it again, still the generic of the part is inserted into the assembly instead of the chosen instance of that FT part.

 

Of course, I tried the option in which I cleared the memory after saving the Assy FT and then reloading it, choosing the correct instance of the Assy FT. Still the GENERIC of the PartFT is loaded. Not the called instance.....

 

 

RPN
18-Opal
July 18, 2023

Only to be sure, you have through all tables unique names. For example you don’t have 

 

bolt-m10<bolt>

bolt-m10<chrombolt>

 

Can you share images of the Tabled?

KenFarley
21-Topaz II
July 18, 2023

If you look at the messages that are generated when you open one of the non-generic instances of your assembly, you'll probably see error messages telling you that it can't find whatever you put in the Part 6 column for that instance, and that it's using the generic.

 

I have used this type of structure a lot in the past and the "trick" is instead of "Y" or "N" in the column of the family table you put the name of the instance you want to use. Just the instance name, nothing about the generic.

Let's say I have a part called mypart.prt, which has two family table instances, mypart-small and mypart-large. To use one or the other of the instances in an assembly, instead of Y or N in the column I'd put mypart-small or mypart-large.

 

 

 

4-Participant
July 18, 2023

Hi there Ken!

 

Thanks for the response, very much appeciated!!

 

There are no error messages when opening the

- AssyFT-Generic,

- AssyFT-Instance1 

- AssyFT-Instance2

- PartFT-generic

- PartFT-Instance1

- PartFT-Instance2

 

All verifications provide "Success"

There are no error messages when regenerating, saving or opening any of the files mentioned above.

 

I have both manually entered the instances using "INSTANCE1.PRT" and "INSTANCE1" which both did not present error at the moment of entering it in the Family Table menu. Entering "INSTANCE1<GENERIC>.PRT" (as it shows in the Model tree) is not allowed at all (tried that after being asked to in a former answer on my post).

 

I did the FT cell input through the menu option "TOOLS > REPLACE USING > FAMILY MEMBER .,," which makes the Family Tree menu pop up and lets you choose the instance you want to use. Creo fills in the cell itself (and does it in the format "INSTANCE1")

 

I have been acquainted with this AssyFT buildup (worked from Pro/Engineer 2000) and it has never failed me on this. If FT's failed me I could always trace the error I did myself. Hope we can find my error here as well.... ..

 

 

KenFarley
21-Topaz II
July 18, 2023
4-Participant
July 18, 2023

Thanks Ken,

 

No, I did find this one on my internet Search too, but that does not provide an answer. So thanks, but unfortunately, it aint the solution.... 😞

 

 

16-Pearl
July 18, 2023

Did you try to close all parts and assemblies an then Erase memory?

 

aa.png

 

Then open again and see what happens... sometimes family tables have something wrong in RAM and that is the problem...

24-Ruby III
July 18, 2023

Hi,

test my models created in Creo 8.0.4.0.

4-Participant
July 18, 2023

Hi there Martin! Thanks for the response,

 

As suspected, your models work perfect. No issues at all. Other FTs here work fine too.. that is why it is kinda frustrating for me....

 

24-Ruby III
July 18, 2023

@MV_10003361 wrote:

Hi there Martin! Thanks for the response,

 

As suspected, your models work perfect. No issues at all. Other FTs here work fine too.. that is why it is kinda frustrating for me....

 


Hi,

OK ... so this means that the problem is data dependent. If you upload your files then you will enable others to investigate them. If you cannot upload your files then ... it is up to you.