secondary assemblies

Hi all,
names have been changed to protect the innocent,
I have a part called 'ring segment' I insert it into an assembly called 'temp ring'
In the assembly I pattern the ring segment then insert a new part called 'fused ring' with a join feature than joins all of the patterned 'ring segments'. This part 'fused ring' has multiple configurations i.e. small extrusions added after the join feature that change it's shape
I have another assembly: 'master assembly', I insert several instances of the part called 'fused ring' into this assembly and carry on.
Later I need to create a copy of 'master assembly' and all it's components. This is difficult to do because neither find references or sw explorer will 'see' the connection to the 'temp ring' assembly. I have to manually manage this relationship by copying and renaming files.
If you have a better technique or some other insight into this issue I would be pleased to hear about it!
Thanks,
Zander
Add pictures here
<% if( /^image/.test(type) ){ %>
<% } %>
<%-name%>
Add image file
Upload
Just a thought. You could break the link of the joined part by saving it out as a parasolid and then back in.
WT

of
components.
will
manage
would
Add pictures here
<% if( /^image/.test(type) ){ %>
<% } %>
<%-name%>
Add image file
Upload
Another idea is insert temp ring.sldasm in Master Assembly.sldasm. Then temp ring.sldasm could be hidden and would export with the rest of it. As long as you don't add references to temp ring.sldasm in Master Assembly.sldasm you shouldn't encounter any circular references.
You could set the mass of the origional parts to 0.0 or whatever the lowest mass possible is to make sure that your mass props are not screwed up.
Corey

of
components.
will
manage
would
Add pictures here
<% if( /^image/.test(type) ){ %>
<% } %>
<%-name%>
Add image file
Upload
Thanks guys, both good ideas that I hadn't thought of....
Zander

Add pictures here
<% if( /^image/.test(type) ){ %>
<% } %>
<%-name%>
Add image file
Upload

Polytechforum.com is a website by engineers for engineers. It is not affiliated with any of manufacturers or vendors discussed here. All logos and trade names are the property of their respective owners.