Using Pro/Program with assembly

[the shaunfather]

I am working on a part that is generated with a program. There are some simple parameters that are inserted to generate each version of the part. I plan on using that generated part in an assembly that will call other parts based upon geometry that is specified in the first program.


Is there away to use what is generated in a part to determine what parts to use in an assembly based off of the dimensions? I'm trying to call one of my dimensions, but Program doesn't seem to like that too much.

 

[FishNut]

Its not a good idea to have an assembly or other parts dependant on another part. If the part with dimensions it suppressed or replaced, it all blows up in your face. Or lets say someone reorders the model tree. There are too many pitfalls this way.


Top down design is what you want to do. Use a layout. In the layout create parameters that controls the size(or features)of the part, or even parameters that control components, ieproduct options. Declare the parts and assemblies to this layout and they all read the same set of params, all independant of each other.

 

[the shaunfather]

The part that is "programmed" is the base partin the assembly, so there won't be any suppression, replacement, or reordering of the tree. All other parts depend on this one being there, and the assembly was designed that way. The geometry doesn't change, just dimensions to fit different parts, and these parts are essentially the same, just with different dimensions to fit different configurations of the first part. The customization of the first part comes from the parameters set by a customer, and based off of those parameters,i need some way to make Pro/E pick the parts that it needs in the assembly based off of the dimensions that are set in the program. Thus, Ineed a way to bring in dimensions from a part to be accessed by the assembly. Would an EXECUTE command be the way to go, or am i just stuck?


Fish - is there another way? we don't have Pro/NOTEBOOK here. at least, that's what Pro/E tells me i need to have.

 

[csusie]

So based on the dimensions of the base part you are going to bring in different parts to assemble next, are they totally different parts or parts from a family table? Is it the same part but with different dimensions? When working with Program with assemblies you can calculated and pass values down to parts you are assembling. You can also use If statements to assemble different parts into the assembly. You can also search family table parts for certain sizes and pull specific instances in to your assemby.


What are you trying to do?


In the first post it sounds you want to do something like this.


If d12:1>10
ADD PART 001406
INTERNAL COMPONENT ID 417
END ADD
ELSE
ADD PART 001407
INTERNAL COMPONENT ID 418
END ADD
ENDIF

 

[the shaunfather]

that's pretty much it. i have all of the parts that i would use in any version of the assembly already there. i plan on using add in conjunction with if..endif to suppress/resume parts. the parts weren't generated using a family table, as they were initially all created custom to a customer's needs. i am trying to standardize the design with a central piece that can be customized, and only having two options for the rest of the assembly. the first part has a dimension OVERALL_OD that will determine what parts to use.


ex:
IF OVERALL_OD == 8.5
ADD PART....
END ADD
ENDIF


IF OVERALL_OD == 7.25
ADD PART...
END ADD
ENDIF


this dimension is based off of parameters that are put in to determine the male and female connections of the part. i'm going to try and to stumble my way through the whole passing values for dims down from the assembly and see if that works. let me know if anyone

 

[csusie]

that should work


are you limiting Overall_OD to certain values or giving it a free range of values to use?

 

[the shaunfather]

OVERALL_OD is limited to 2 values. if the design and customer needs provethe need to eventually need more options than the 2 thathave been determined, then i may add to it. but for now, it will only be the 2.