Continue to Site

Welcome to MCAD Central

Join our MCAD Central community forums, the largest resource for MCAD (Mechanical Computer-Aided Design) professionals, including files, forums, jobs, articles, calendar, and more.

Instances of large assemblies in drawings

bobmann

New member
I've got some large assemblies that I want to simplify and show in drawings. They aren't the largest in the world and I'm sure many of you have worked on ones much bigger, but they are big enough to become annoying. Problem is, they come in many different sizes, and thus have Family Tables.


I want to create a drawing that shows all the sizes side-by-side. This drawing is just something simple that we want to provide for our customers, so they don't need to be terribly detailed, and we'd like to simplify them to save regen time.


I've tried using Simplified Reps, and in theory it seems as though this should work just fine. But it seems to me that Simplified Reps and Family Tables don't work nicely together. When I add each model to the drawing and try to use Simplified Reps for each view, the views always revert to the generic of each component, and thus the views all look messed up. Is there any way to use Simplified Reps to show multiple instances in one drawing?


Or are there other methods that could help here? I've tried using Shrinkwrap models, but those aren't associative to the originals, are they? I would like to have something that would automatically update if there's an Engineering Change. Is there anything else? Envelopes, Merge, Inheritance, etc?


I can't believe we're the first company that's tried to do something like this. Any help would be greatly appreciated. Thanks!
 
You can either use shrinkwraps or envelopes. I personally hate them both especially when using them as background data in a cross section...they fail alot. But if your just using them as a pictorial representation, they will work just fine.
 
A "general" rule for working in family tables is for the generic to have most, if not all, of the features or components present. Similarly if you have a multiple level assembly that you are swapping components via family tables, the components at ALL levels should "ideally" be the generics themselves as opposed to instances.

Then by defining your simplified reps and/or exploded views in the top level generic with "all" components present you will have the greatest chance of getting it to work all the way down the chain.

If however you are swapping components through the use of interchange assemblies then you will have far less control over the simplified reps.


Have you tried using layers to filter out minor components to reduce the regen time?


DB
 
hi CPiotrowski...
my friend..
the link you gave for jpg files directs to a wrong web can you check them please ...than you..
 

Sponsor

Back
Top