×
INTELLIGENT WORK FORUMS
FOR ENGINEERING PROFESSIONALS

Log In

Come Join Us!

Are you an
Engineering professional?
Join Eng-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Eng-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

CATia 5 Model Tree Structure and Modeling

CATia 5 Model Tree Structure and Modeling

CATia 5 Model Tree Structure and Modeling

(OP)
I am relatively new to Catia 5 and the thing that I find somehow confusing is "suggested" model organization using bodies and than assemble them using Boolean operations.
So I would like to ask experienced CATIA users what is the benefit of making model tree that complex creating a new body for almost any modeling entity when you can do it much more simpler in one body.
In that tutorial "suggested" technique I even found  a bizarre thing such as putting a single hole in a separate body and than assemble it after.
If holes and pockets automatically remove the material what is the meaning of using the Boolean operations?

Thanks

RE: CATia 5 Model Tree Structure and Modeling

That is absolutely the wrong way to use CATIA V5.

Where did you find this "suggested" techinque?

V5 is FEATURE BASED. A hole will perform better than a removed cylinder. A pocket will perform better than a removed prism.

If I were you, I wouldn't put much stock in whatever document you are reading. It was probably written by a V4 user. If it came from Dassault, I'll be extremely surprised.

RE: CATia 5 Model Tree Structure and Modeling

(OP)
I haven’t obviously made myself clear enough. Suggested technique does use the hole and not cylinder. However it puts the hole in a new body in  which btw the hole is only feature. In the and it assembles the "hole" body to the main one.
My question is: Why they suggest to separate the features in the separate bodies when you can use only one.
This way you get complex model tree structure even for the simple part? What is the benefit if any?

This suggested techniques: http://www.amazon.com/exec/obidos/tg/detail/-/140181994X/qid=1110834043/sr=8-3/ref=pd_csp_3/002-1416714-5822403?v=glance&s=books&n=507846is the source for

RE: CATia 5 Model Tree Structure and Modeling

Hi,

I hope we can meet 1 of the 2 authors in Phoenix and ask them about that.

Also I am surprised they would suggest 1 feature per body. This is not the best way to use CATIA V5.

A lot of people ask me about how I would build a solid, my answer is still the same : Make it easy to understand and to modify. Then think about optimizing update...

A Tree to long (more than 100 features in 1 body) might not be easy to 'read'. Even if I don't need to use boolean operations to build my solid I will use some to make it easier to understand.

...also, I almost forgot, the geometry got to be exact. A 10" pad is not a 10" 1/16 ... Even if the tree looks good your geometry is not.

After the COE topgun, the 5 best users should explain how they built their solid... and why...

indocti discant et ament meminisse periti
Eric N.

RE: CATia 5 Model Tree Structure and Modeling

^^ Agreed. Assembling a few bodies here and there just to make navigating the tree easier is a reasonable thing to do. I can't think of any reason why anyone would impose a one feature per body limitation. I can understand monodetail sketches, but putting a hole into a seperate body and assembling it to the solid is a waste of time (and probably resources), plus it would make the tree harder to read.


If you read the reviews of the book, one of the two authors isn't even a V5 guy.

RE: CATia 5 Model Tree Structure and Modeling

(OP)
Thank you for responses
It wasn’t suggested 1 feature per body, however  in one particular  example it was suggested to put  a simple hole in a separate body.
Most of the other bodies had a few features.
But one or a few does it really make difference?
I don’t think so.

RE: CATia 5 Model Tree Structure and Modeling

There is some power to putting together bodies, not only in Model Organization, but in terms of creating PowerCopies and UserFeatures, as well as Knowledgeware Applications. I might give someone an example of a single hole in a separate body.  But only to show the difference between a "negative" and a "positive" body, and what the Assemble operation does as opposed to the Add or Subtract operation. I would not tell them that that is any way to work in normal circumstances.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Eng-Tips Forums free from inappropriate posts.
The Eng-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Eng-Tips forums is a member-only feature.

Click Here to join Eng-Tips and talk with other members!


Resources