Go to Post But that is not all-FIRST is about teaching mentors what kids are like all over again. It's about closing the generation gap, creating bonds, life time friends, and skills that will last everyone involved a lifetime. - Team0 [more]
Home
Go Back   Chief Delphi > Technical > CAD > Inventor
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
 
 
Thread Tools Rate Thread Display Modes
Prev Previous Post   Next Post Next
  #5   Spotlight this post!  
Unread 31-01-2005, 12:32
Tristan Lall's Avatar
Tristan Lall Tristan Lall is offline
Registered User
FRC #0188 (Woburn Robotics)
 
Join Date: Aug 2001
Rookie Year: 1999
Location: Toronto, ON
Posts: 2,484
Tristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond repute
Re: ProE Assembly Editing

Quote:
Originally Posted by Dzdconfusd
DO NOT USE ASSEMBLY CUTS OR FEATURES IN PRO/E

They cause all sorts of reference issues and if you select the wrong options when creating them you can cause all sorts of problems. This is more of an issue when multiple people are working on an assembly but the consequences are sitll the same. This is the easiest way to cause a cicular reference and should only be done as a last resort.
This is where design intent, manufacturing intent and program functionality clash. If the intent is for a cut to be made through the assembly, and not individually on each part, the assembly cut seems logical--but for the reasons you describe, things can get a little crazy when chasing the references later on, because of Pro/E's need to maintain dependencies. (Note that for the same manufacturing intent reasons, assembly protrusions don't make much sense at all, in most cases.)

If you're going to be putting the parts in other assemblies, definitely treat it like the second case, or the third case (if you're very careful about what assemblies it will belong to). If you're going to leave it all in one assembly, occasional use of the assembly cut should be fine--but it isn't intended to replace individual part features. I would avoid other sorts of assembly features, if they aren't sensibly grounded in either design or manufacturing intent.

Most importantly, whichever technique is used, good practices should always be followed when choosing references: don't pick features that are prone to disappearing or changing, as the model evolves; try to use as few references as possible to constrain the sketch; avoid references on separate models in an assembly, if a single model will do (mostly for Insert Feature).

In short, "never" is probably too strong, but if in doubt, you can still take the safer route, and modify the underlying model. With a little experience in choosing references, you shouldn't have too much trouble making a good decision.
 


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Drive Assembly Sprockets are Custom Bored Mark Pettit Kit & Additional Hardware 35 09-03-2005 19:05
Assembly? Astronouth7303 Programming 2 12-08-2004 11:30
Importing assembly into an assembly... James Green Inventor 8 22-01-2004 22:17
How much can the window assembly lift? archiver 2000 9 23-06-2002 22:59
Driving constraints in assembly Jan Olligs Inventor 0 25-02-2002 07:11


All times are GMT -5. The time now is 16:06.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi