Skip to main content
1-Visitor
August 28, 2018
Solved

Reference Viewer

  • August 28, 2018
  • 2 replies
  • 7984 views

Hello;

I'm new into Creo. I have created an assembly structure and some parts with geometry reference(project) from other parts. In Reference viewer it shows the root assembly as a children for the parts which have reference, Why? see attached image/

Can I set the creo options to not to have this logic?

 

Thanks.

BR.

 

 

Best answer by dgschaefer

The parent assy defines the relationship between your source part and the target. That's why it's in the reference chain.  Without it Creo wouldn't know where to put the geometry from the source in the target.

 

The way to avoid this is to use an external copy geometry feature to copy directly from one part to another by aligning coordinate systems instead of using an assy.

 

A more robust way is to use skeleton driven top down design techniques. The skeleton defines shared geometry and that geometry is passed down by copy geometry (still creates an assy reference) or external copy geometry (no assy reference) to the parts.

2 replies

23-Emerald III
August 28, 2018

You have to be careful what you use for references when you work with parts in an assembly. 

There is an option to eliminate or warn when you are making references to other parts/assemblies.

In the config under file - options configuration editor, set

default_ext_ref_scope and change the setting to NONE

 

Beau19981-VisitorAuthor
1-Visitor
August 28, 2018

Thanks @StephenW

Why I should be careful about using these references? what is long or short term issues?

21-Topaz II
August 28, 2018

The parent assy defines the relationship between your source part and the target. That's why it's in the reference chain.  Without it Creo wouldn't know where to put the geometry from the source in the target.

 

The way to avoid this is to use an external copy geometry feature to copy directly from one part to another by aligning coordinate systems instead of using an assy.

 

A more robust way is to use skeleton driven top down design techniques. The skeleton defines shared geometry and that geometry is passed down by copy geometry (still creates an assy reference) or external copy geometry (no assy reference) to the parts.

Beau19981-VisitorAuthor
1-Visitor
August 28, 2018

@dgschaefer

Thanks so much.

Does this Skeleton method solve the issue of external references?

Where can I find some of these practices about skeleton driven methodology? Any book or reference guide?

Generally speaking, is it practical to use references from other parts (without defining skeleton env) in complex products?

 

BR.

23-Emerald III
August 28, 2018
If you don't have some plan to control your references, your assemblies (and parts) will quickly become unmanage-able.
I don't use skeletons. I design my parts/sub-assemblies initially using references as I work through the design process. It makes making design changes along the way easier. Then as I am finalizing my design/project/drawings, I break all the external references as I go. In the end, all my parts and assemblies end up as stand-alone components that can be re-used in other assemblies as needed. This is the nature of my product and it works well. Part / assembly reuse is key to my process so it is important to me to end up with clean structures that don't have external references.
These other guys will have to elaborate on skeleton usage.