-
Website
http://www.solidsmack.com/ -
Original page
http://www.solidsmack.com/solidworks-top-down-modeling-challenge-tips/2008-08-12/ -
Subscribe
All Comments -
Community
-
Top Commenters
-
Charles Culp
34 comments · 2 points
-
Brian
51 comments · 9 points
-
MatthewWest
32 comments · 2 points
-
Bruce Buck
72 comments · 6 points
-
Dave Moore
49 comments · 1 points
-
-
Popular Threads
-
Friday Smackdown: Mechtronic Melee
2 days ago · 2 comments
-
Ask The Reader: Are You Upgrading to Windows 7? {Poll}
1 week ago · 21 comments
-
The Rockin’est LED PocketWatch Mod EVER, Designed With a lil’ SolidWorks
3 days ago · 4 comments
-
FreshFiber’s 3D Printed iPhone Case Puts the Fancy in Your Pants
2 days ago · 2 comments
-
Get Into SolidWorks World 2010 for Free. No Beet Throwing Required. #SWW10
6 days ago · 5 comments
-
Friday Smackdown: Mechtronic Melee
Toasters are always fun design exercises. (No really, I'm being serious) A few nice parting lines in the shell, plenty of sliding/lever relationships for parts, and all driven by the dimensions of a slice of bread!
So design a DIY (do it yourself) bbq!
I always finish up with bottom-up assemblies, but sometimes I'll start with top-down designs. If I need a bunch of parts and subassemblies to fit into a small space, top-down is the way to go. But once that design is perfected, I convert it to bottom-up. When dealing with configuration management and ECR/ECNs, the last thing you want is one part to auto-update another.
How about an assembly that shows the dangers of leaving in context relations, ie circular relations, broken relations, too many relations, etc.?
Daniel
Bottom Up is my preference. Why? Because In Context External References don't belong in our universe. Ever Checked In a Part file with these References into an electronic vault? A worm hole opens up and you're transported to the 4th dimension.
Devon
For example: If you go to the Wolfram Demonstrations Project ( http://demonstrations.wolfram.com/ ) and search for "Hoberman" you'll find some examples of mechanisms where the design of one part is very much dependent on the design of other parts, and also the overall results of motion for the mechanism as a whole are difficult to forsee without constantly simulating the motion during the design process.
Here's the sort of thing you could do with these mechanisms: Watch the web preview of the "Ring of Hoberman Rings" example. Can't you just see how you're really looking down on a new type of connected parasols for sun terraces suspended overhead that does away with those annoying poles that either get in your way as you walk around or else go right through your table?
That said, I would like to know more about the pitfalls of TDD that Jeff B refers to.
and will definitely go over the 'pitfalls', the do's and don't's of top-down
and bottom-up. Thanks for letting me know what you're interested in seeing.
with the top down method:
if a part references another one then the part is fixed and i cant mate it.
im a new user.is there a way to avoid this ?
thnx
However, keeping parts unfixed can be used while conceptualizing to test out different ideas.