Skip to main content
Mar 18, 2015 3:31 PM UTC
Question

Re: outdated component/feature

It's very simple. When I'm building an assembly, I have already created all my components based upon the assembly csys, so the component csys and the assembly csys are the same. When I add the first component to the assembly, I just snap the component csys to the assembly csys and it's fully constrained and very stable. Then I just repeat this with the remaining components. This is a common practice in the aerospace industry where entire aircraft are assembled this way, such as the H-60.

    2 replies

    Mar 18, 2015 3:37 PM UTC

    I sort of understand what you're saying. But can you clarify for me - a simplified example just so I can understand - if I have a model of a box and I needed to add screws to the holes in the box, instead of mating the screws to the holes, you would attach the screws to the csys instead? How would you know the exact coordinates of the screws? Or am I completely misunderstanding? I really appreciate your help.

    Mar 18, 2015 3:41 PM UTC

    Certainly has the potential to be a very stable approach, but arguably only applicable to certain types of assembly - specifically, those where components are unique to each assembly, and are used only once (to my way of thinking).

    In a gearbox where I might use the same bearing three times, and that same bearing is used in numerous completely different gearboxes, it sounds like a non-starter to me. Does the assembly csys go in the component? If so, you would have to revise it every time you use it in a new assembly, or change its position in an existing one! Or do you create hundreds of csyses within the assembly?

    For assembling the gearbox assembly within the car, OTOH, creating a vehicle csys in the gearbox assembly before exporting to the customer does often make sense - although on occasion I've created a new assembly for this purpose, in which the vehicle csys is the default and I create one to position the gearbox.

    Given the whole 'design intent' philosophy of Pro/E, the functional component constraints make a lot of sense. (My design intent is to have that bearing assembled in this bore, against this shoulder - not floating in space at (231, 57, 68.5). Personally I haven't experienced them collapsing in the way described by the OP, but if they do then that's pretty unhelpful...