sktcorp_Karen
New member
Hello All,
I am a fairly new user of Pro/E (Wildfire 3.0), and I have no experience with Trail files or Family Tables, but I hear they may be useful for my application. I need to make approximately 500 identical parts, give each a unique nameand placeeach ata unique location (x,y,z coordinates) within the same assembly.
I'm thinkingI couldedit aTrail file to retrievea unique namefrom an exterior .txt or .dat file and thenmodel the part.Iam hopefulthat the Trail file can be edited with a "do loop" so that it will continue to retrieve data and modelparts until one part for each unique namehas been modeled.I have no idea how to go about locating parts automatically within an assembly. Is it possible to utilize a Family Table or a Trail file for the assemblyto meet this need?
I would very much appreciate any instructions, linksorbook titles on the following topics: (1) editing Trail files, (2) writing "do loops" for Trail files, (3) automatically locating parts in assemblies via Trail files, (4) using Family Tables, or (5) any other topicthatwould be useful in my application.
Thanks,
Karen
I am a fairly new user of Pro/E (Wildfire 3.0), and I have no experience with Trail files or Family Tables, but I hear they may be useful for my application. I need to make approximately 500 identical parts, give each a unique nameand placeeach ata unique location (x,y,z coordinates) within the same assembly.
I'm thinkingI couldedit aTrail file to retrievea unique namefrom an exterior .txt or .dat file and thenmodel the part.Iam hopefulthat the Trail file can be edited with a "do loop" so that it will continue to retrieve data and modelparts until one part for each unique namehas been modeled.I have no idea how to go about locating parts automatically within an assembly. Is it possible to utilize a Family Table or a Trail file for the assemblyto meet this need?
I would very much appreciate any instructions, linksorbook titles on the following topics: (1) editing Trail files, (2) writing "do loops" for Trail files, (3) automatically locating parts in assemblies via Trail files, (4) using Family Tables, or (5) any other topicthatwould be useful in my application.
Thanks,
Karen